14 ms·
decided they should be paid for their work. There is one slight problem however. Growl is Open Source Software. So? You can sell open source software. Just bec
by rmc 15y ago
decided they should be paid for their work. There is one slight problem however. Growl is Open Source Software.
So? You can sell open source software. Just because software is GPL/BSD licenced doesn't mean you can't sell it. Open Source ≠ Non-commerical. Closed Source ≠ Commmerical. You can change for open source software. If something is open source you can't complain if someone sells it.
Obviously if the software is open source, everyone who buys a copy is allowed to sell the software themselves and they don't have to give the original author any money. They also cannot stop someone taking an older version of the code and distributing it.
- _ak 15y agoTo my knowledge, the source to the 1.3.x release isn't public. I wonder whether it's a complete rewrite from scratch or whether 1.3.x still contains patches from external contributors and whether they agreed that their work be sold for money.
- masklinn 15y agoYour knowledge is incorrect. The 1.3.0 source is available[0], and 1.3.1 should be soon[1], they have not dumped them in the public repository is all. > I wonder whether it's a complete rewrite from scratch or whether 1.3.x still contains patches from external contributors and whether they agreed that their work be sold for money. I'm not sure that has any relevance. It would if Growl had changed its license (they have to agree to license changes to their contributions, unless they ceded their copyright to the project or project owner), but selling the product is independent of that. It can be seen as a dick move, but it's still independent. [0] http://code.google.com/p/growl/source/detail?r=9831a92b05b20af461bf4fc77ec7b7b052831ccf http://code.google.com/p/growl/source/detail?r=9831a92b05b20... [1] http://groups.google.com/group/growldiscuss/msg/0793d15920faf093 http://groups.google.com/group/growldiscuss/msg/0793d15920fa...
- masklinn 15y agoAnd the 1.3.1 source has now been added to the public repository.
- p0ckets 15y agoThey agreed that their work would be sold for money when they contributed to a BSD licensed project. If they cared, they could release their patches.
- rmc 15y agoBSD is irrelevant here. If it was a GPLv3 licenced work it could still be sold. The agreeded to their work begin sellable when they contributed to an open source project.
- p0ckets 15y agoThat is correct. The only difference a GPL license would make is that Growl would be forced to release the source code for any version that they sell. And that they wouldn't be able to sell it through the App Store.
- patrickod 15y agoIt's not public yet but as per their BSD licence terms they will be releasing it. This, according to http://www.macworld.com/article/162208/2011/10/growl_shows_that_open_source_and_the_mac_app_store_mix.html http://www.macworld.com/article/162208/2011/10/growl_shows_t...
- eis 15y agoIf something is open source you can't complain if someone sells it. Obviously if the software is open source, everyone who buys a copy is allowed to sell the software themselves and they don't have to give the original author any money. They also cannot stop someone taking an older version of the code and distributing it. What? I really don't get why so many people don't understand that "Open Source" does not mean you can't sell it, nor does it mean you can sell it at will or whatever. It just means you can view the source. The term "Open Source" does not make any claims about monetization, it does not even say which kind of license is at play. You can publish your code open source, charge for it and still forbid people to sell it or even redistribute the source. "Open Source" is not a license. GPL, BSD, MIT, Apache etc. are all open source licenses with very different rules. Here's a list of licenses many people consider "open source licenses": http://www.opensource.org/licenses/alphabetical http://www.opensource.org/licenses/alphabetical Conversely, you can have closed source applications which allow you to redistribute them or even sell at will. Closed source software is just more likely to have a license which is very strict about redistribution, that's all.
- rmc 15y agoYou can publish your code open source, charge for it and still forbid people to sell it or even redistribute the source. Not really. It depends on the exact licence but just about every 'open source' licence, and the Open Source Definition from the OSI and the Free Software Defintion from the FSF will requite that the licence lets the people who get the software to be allowed to redistribute it. Just look at the link you provided for 'open source definition': "Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:", and №1 being: "The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale."
- cromulent 15y agoThe OSI was founded in 1998, but companies such as SAP provided their ERP systems with full readable source code much earlier than that, and it was called "open source" (as opposed to "closed source" which was more common with COTS). However, it is explicitly forbidden in the licence to re-sell it or re-distribute it. The term pre-dates the organisation's re-definition of it for their own purposes.
- dedward 15y agoDisregarding all the banter about what "open source" means -there are separate issues at hand. One is the actual license terms the older versions were distributed under. Those matter. Another is how the project itself was run, specifically how copyright assignment worked. If contributors were required to assign copyright to the project maintainer (or whatever) in order to commit to his main branch, as is the case with many projects, then he can likely do whatever he wants in terms of re-licensing. If that wasn't addressed clearly, there might be wiggle room for closing it off - contributors may have some kind of copyright claim if their work was taken and used under terms they didn't agree to. Another is PR - that one is obvious. As for the "Open source means you give back" - let's get over it - that's not what it was originally about - you have no "duty" to contribute - it's just a fantastic, common side effect that lots of people like to take advantage of. End of story - if you are contributing code to someone elses project, be sure you understand where you sit in terms of copyright.
- doki_pen 15y agoYou are confusing open source and free. You don't have the right to redistribute open source software. Free software guarantees this right.