pyopenssl should document explicit permission for name from the OpenSSL project
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 944
- Forks
- 440
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Description
forwarding https://bugs.launchpad.net/pyopenssl/+bug/457795 as it seems to be missing:
The OpenSSL license states:
* 5. Products derived from this software may not be called "OpenSSL"
* nor may "OpenSSL" appear in their names without prior written
* permission of the OpenSSL Project.
Since pyopenssl contains "OpenSSL" in its name, i'm assuming that such permission has been explicitly granted at some point in the past. If this is the case, it would be good to document this explicitly. If such permission hasn't been explicitly granted, it would be good to respect the license and ask for it, and then document it (assuming that it's granted, of course).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by verifying the OpenSSL naming requirement and whether pyOpenSSL has explicit written permission, then identify the project's appropriate licensing or documentation location. Done means the permission status and supporting documentation are recorded, or the issue is resolved after permission is obtained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100