4 ms·
Do you have open source contributers sign changes over to you, or do you consider their contributions a "loss"? In other words, you can't take AGPL contributio
by bretthoerner 17y ago
Do you have open source contributers sign changes over to you, or do you consider their contributions a "loss"?
In other words, you can't take AGPL contributions and dual license them in your product, right?
(I don't mean to imply this is bad, I'm glad you helped explain a use of the AGPL and I'm just curious.)
- Maro 17y agoThe same problem exists if you try to sell a commercial license to a GPL'd codebase. I think if you plan to sell commercial licenses, you can't accept "outside' contributions without having the contributors sign them over.
- bretthoerner 17y agoSure, I'm curious what they do and why. It's not often I get to ask someone with an open source actual product.
- blasdel 17y agoBut you can still host a GPL'd codebase as a service and use 'outside' contributions without copyright assignment.
- blasdel 17y agoThat's something I hadn't considered! I'd thought about how you could use the AGPL as a scarlet letter: "I'm the only one that can profit from this", since as the author you still retain full copyright and can do whatever you want with closed modifications. tptacek appears to be using it this way, to keep other companies from selling it, even if he doesn't care much about selling it himself. But I hadn't realized that in such a situation, the author would be completely unable to take contributions from others without full copyright assignment!