Should an Apache 2 licensed project include so many reference to an AGPL library?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 34.3k
- Forks
- 4.3k
- PR merge metrics
- No merged PRs in 30d
Description
FYI.
The WareHouse/BookBreeze example included with ChatDev relies on ebooklib, https://github.com/aerkalov/ebooklib, with is AGPL licensed.
I recommend you split the WareHouse/BookBreeze example into it's own AGPL licensed repo (or replace the current bookbreeze example with one that doesn't rely on an AGPL library).
At a minimum, I think the LICENSE should include a warning that the BookBreeze example is licensed differently (AGPL) from the rest of ChatDev (Apache 2).
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the LICENSE and the WareHouse/BookBreeze example's use of the ebooklib dependency. Confirm how the example's AGPL licensing relates to ChatDev's Apache 2 license; done when the licensing treatment and any required warning or separation are documented.
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
- Mostly clear
- Newbie friendliness
- 25/100