change to agpl
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
i got amazed at how searching for "agpl" brings zero issues!
as you know, we should always carefully choose the license before creating any software.
lbry and odyssey already got very big with MIT, and you probably haven't faced many issues yet...
and we have plenty of instances of free software using several different kinds of license...
but, imho, if we want to get real and serious about freedom, we need to go with agpl today. nothing less.
think about it. why no big corp ever picks agpl? what really lies on the bottom of the fuss against it?
i have (for now) zero affiliation with gnu or fsf... but i will get in because i truly believe in this. and i will get out once something better comes up, if ever. history, so far, showed zero better promises.
heads up, and..
cheers! 😁
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
No files, tests, or entry points are identified in the issue. Start by reviewing the repository's current license and project policy, then determine whether maintainers have agreed to the proposed license change. Done would require a documented decision and any resulting repository-wide updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100