4 ms·
Potentially interesting, but my interest waned considerably when I saw it's GPLv3.
by tjaerv 13y ago
Potentially interesting, but my interest waned considerably when I saw it's GPLv3.
- welly 13y agoReally? Because of the license, you're not interested in this project? I find that very, very bizarre. Can you explain your thinking?
- levosmetalo 13y agoCan _you_ explain why do _you_ think someone loosing interest in the project because of its license choice is bizarre? What makes _your_ "I don't care about licensing, and neither should you" opinion not bizarre, and his "I don't care about projects with wrong license" bizarre? I agree that parent comment didn't add much to the discussion, but that's not the reason to imply bizarreness of it.
- welly 13y ago> Can _you_ explain why do _you_ think someone loosing interest in the project because of its license choice is bizarre If it's a project that interests or is useful to me, then personally that trumps the license. If I discover a project useful to my workflow then I'll find a way to work with it, despite the license. > What makes _your_ "I don't care about licensing, and neither should you" opinion not bizarre Because it's my opinion and I generally don't find my opinions bizarre, otherwise I wouldn't hold them. And I didn't say "I don't care about licensing, and neither should you" or even insinuate that. He's more than welcome to care more about a license over a usefulness of piece of software and I'll still find it odd.
- euank 13y agoNot him, but I can see a few good reasons. GPL is rather limiting in how you can use the code. A large company (e.g. Apple) won't let something gpl be used heavily internally if they can help it since they won't be able to apply patches or modify it without releasing these changes ... this obligation adds significant legal burden and, furthermore, releasing the changes could reveal private details about the companies internals. I don't think that the commentor's reason is a good one, but I can understand the viewpoint; GPLv3 is quite limiting for some uses.
- chrj 13y agoAs long as it's only used and distributed internally, I don't believe the GPL has a problem with them modifying it without disclosing their changes. That's my understanding.
- indeyets 13y agonot really. they won't be able to publish product which incorporates GPL library without releasing this product under compatible license. they can use and patch GPL product internally as long as they want.
- wazoox 13y agoIndeed, AGPL v3 would have been way better.
- jewel 13y agoWe're changing to LGPLv3. See https://github.com/jewel/clearskies/blob/master/license-change.md https://github.com/jewel/clearskies/blob/master/license-chan.... The C++ implementation is also LGPL.
- alexchamberlain 13y agoHow did you reach this decision? IMHO such licences actually hold free software back.
- jewel 13y agoYou can read the entire thread here: https://groups.google.com/forum/#!msg/clearskies-dev/sTlXzBO4IUY/yoeQHGDwbjEJ https://groups.google.com/forum/#!msg/clearskies-dev/sTlXzBO... For the sync app itself GPL would have worked great, but we want to have an easy-to-integrate sync library. Hopefully this will reduce the number of apps that require a cloud service to be able to synchronize the user data between devices.