3 ms·
I don't see how that's practical. If a project requires "contributing back" and then doesn't accept the changes, the fork can't exist?
by rustc 5y ago
I don't see how that's practical. If a project requires "contributing back" and then doesn't accept the changes, the fork can't exist?
- 2Gkashmiri 5y agoi said, AGPL does not require contributing back. there is no clause demanding that. a fork can be independent of changes to upstream as long as they provide source to its customers/users.