That'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!
The 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.
But you can still host a GPL'd codebase as a service and use 'outside' contributions without copyright assignment.
Re:Why the GNU Affero GPL
by bretthoerner on Saturday April 17, 2010 @02:19PM
(#1273439)
Sure, I'm curious what they do and why. It's not often I get to ask someone with an open source actual product.
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.)