You can always fork the project, put your own branding on it and make money off your contributions still :) It's just not possible to make money under their brand, or in a closed source product.
> You can always fork the project, put your own branding on it and make money off your contributions still :) It's just not possible to make money under their brand.
This doesn't sound right. You'd be forbidden from selling non-GPLv3 access to any of the existing code, even under a new brand, and any plugins that you created would either be GPLv3, or not distributable at all.
Yes, because running a project, mentoring, moderation and releasing in an orderly fashion is far more work then most people expect.
You can definitely sell GPLv3 software. As long as the source is available and you abide by the terms of the licence.
Yes sorry, I realised my omission and edited my post just before you commented. You are right that you wouldn't be able to sell your code under a different license than GPLv3, whilst the person you signed the copyright to would.
> But in a few years, we could imagine that the majority of contributions come donated for free from volunteers. Would it still be fair then?
I would hope that by that time, all significant contributions would be in the form of plugins, which are not required to be GPLv3 as far as I'm aware, or even require a sign away of copyright. The question would then be, do you want to sell your plugin through their system, or distribute it on your own.
Chris said in the thread that plugins would be "infected" by GPLv3: https://groups.google.com/forum/#!msg/light-table-discussion...
If someone contributes code and licenses their copyright to LightTable, knowing full well that the product they support and invested time in may acquire some funds because of it, gosh, I just don't see how that's a bad thing. And if they believe that their patch is significant enough to demand reimbursement, that they would like to charge LightTable for a copyright license, they are free to negotiate such a trade. And if LightTable actually makes money from relicensing, they'll probably be happy to pay for such things.
I do, however, hope that they ask for copyright licenses rather than copyright assignment. Copyright assignment turns the author into a person powerless to use their own work. See harmonyagreements.org.
Perhaps they are not aware of this and it matters to them; this makes it useful information.
If they don't care (or care but have other, more compelling reasons, for their choices) then fine. But at least they can make a more informed decision.
I do have a question about the licensing -- will you be requiring copyright on code contributions to be assigned to you?
If not, you can't then sell those contributions outside of the terms of GPLv3, because you have to own them before you can relicense them, or obtain the owner's permission.
(If so, it's a little distasteful for the people contributing to know that their code is being used to make money for other people and they won't receive any of it.)