-
-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
URGENT: Dear PlatformIO 2.0 contributors... #510
Comments
AGREE. I'm really excited to see this! Looking forward to an awesome 3.0! |
AGREE. I don't really like the GPL but I like this project. Have at it. 2016-02-11 18:30 GMT+01:00 Christopher [email protected]:
|
@ivankravets, is there a reason you didn't do gplv2 or later (aka gplv2+)? it would make platformio more compatible with free software ecosystem and still be gpl2 like you want |
also the FSF doesn't find GPL 2.0 and ANY Apache 2 licensed code to used together. However GPL 3.0 is compatible with Apache 2.0. Certainly there's no problem with this relicensing, but it would affect potential code reuse. In any case, you might actually wanna consider the AGPL instead, because some people might build a platform.io builder rest API, and under the GPL they wouldn't be required to share any of the non-GPL modifications they make to it, but with the AGPL they would be. |
AGREE. Looking forward to help out again once I'm done with these classes I'm taking. |
Agree. It's my pleasure to help this great project move forward. On Thu, Feb 11, 2016 at 9:20 AM, Ivan Kravets [email protected]
Patrick Leugue |
I disagree with URGENT, a license decision should not be rushed. Cheers |
AGREE |
1 similar comment
AGREE |
Agree |
Agree. Glad to help! |
Dear @TimJay, @mogorman and @jrobeson, Sorry for the misunderstanding. I've just update this issue with
The main idea is to move the code which are interesting for contributors to the separate repos and keep FULL control on the PlatformIO Core. If you know the situation where PlatformIO 3.0 under GPL 2.0 will no be compatible with something (I don't know with what), please explain here. Thanks. |
This quote from the Wikipedia page on license compatibility sums it up quite well: |
@rue-mogorman In my experience you have a better chance of establishing a lively ecosystem with a business friendly 2-clause/apache license as you suggested. EPL tends to be even better at that because it enforces code feedback while still being open to commercial endeavours. |
@TimJay PlatformIO isn't a framework or a SDK. I don't see problems for the end users. We are discussing here PlatformIO Core. What is more, I received 0 contributions to PlatformIO Core for the latest 20 months. It means, that no one is interested in developing PlatformIO for FREE. I'll write additional comment to #490 with our decision. PlatformIO is dear for me and I'll apply maximum efforts to keep it FREE and Open Source. However, each of us should understand that we live in real life where each work should be paid. To have full influence to the PlatformIO project will allow PlatformIO Team to work on it for the full time. |
I agree with @TimJay that using gpl makes it more likely that you just need to use gpl everywhere. Which is why I am for changing to gplv2 or later for max compatibility that way. otherwise i think a simpler 2 clause bsd like apache or mit is what you want. Personally I am for keeping things as free for the users as possible so gpl v2 or later works well sorry made from work account submitting again |
Please explain me where THE END USER will have problems with PlatformIO under GPL 2.0. |
@ivankravets: there are no problems with that. I do think you should consider adopting the AGPL instead of the GPL though. This way you don't have to worry about folks building closed source hosted build systems on top of platformio and getting around the GPL that way. |
@ivankravets : also GPL 2 and GPL 3 are not compatible with each other, so platformio extensions that allow GPL 3.0 code would not be allowed. Neither would Apache 2.0 based extensions (if GPL 2) |
Thanks guys, Ok, I see that GPL 3.0 is good candidate for all of us. See With which licenses is the GPLv3 compatible? In this case, we can keep PlatformIO Core under GPL 3.0 and you will have ability to write own development platforms, extensions without any problems using these compatible licenses. @TimJay what do you think? |
@ivankravets : any reasons not to consider the AGPL 3? |
@jrobeson You are right. With AGPL v3 all of us will have access to all modified versions of PlatformIO http://choosealicense.com/licenses/. Thanks! |
@rue-mogorman thanks that using PlatformIO 🍺 Let's wait for @franciscoruiz, @floretan, @dh1tw, @dkuku |
@ivankravets awesome! and thanks for all hard work on project. it has been very useful to me |
I've just updated comment with AGPL v3.0 #510 (comment) |
I think we should repeat the agreement for good measure: all who agreed so So: I agree (with a move to AGPL v3). As an aside, I'm pretty sure my vote
|
You are right! Friends, @ZachMassia @mplewis @franciscoruiz @WillemMali @twpayne @floretan @TimJay @sticilface @dh1tw @bkudria @ctag @Lutino @jrobeson @dkuku , please repeat the agreement as for AGPL v3.0. Looks like it is the best candidate for all of us.
You are the contributor of PlatformIO 2.0 and it doesn't matter how many lines you are contributed and to which part of PlatformIO. I appreciate each PlatformIO's contributor. Nevertheless, I've not written this post to say that "IF YOU ARE NOT AGREE, I WILL DO WHAT I WANT". I like our community and it's valuable for me. As you can see, we have started from GPL 2.0 and finished on AGPL 3.0 😊 |
I agree regarding AGPL v3.0. |
i agree regarding AGPL v3.0. |
I agree WRT AGPL as well. On Fri, Feb 12, 2016 at 3:29 PM, Johnny Robeson [email protected]
|
I agree with AGPL v3.0 license On Feb 12, 2016 7:07 PM, "Benjamin Kudria" [email protected] wrote:
|
I agree with AGPL v3.0 as well. |
I agree to with changing to any of the license changes mentioned in this thread so far. |
I agree regarding the use of the AGPL v3.0 license. |
I agree. Francisco Ruiz
|
AGREE for AGPL v3.0 |
Dear @twpayne, @sticilface, @dh1tw and @dkuku, Are you agree with #510 (comment) and UPDATE 2 (The license above is updated to AGPL v3.0) ? Thanks! |
agree |
Agree Am Donnerstag, 18. Februar 2016 schrieb Daniel Kuku :
|
Dear Contributors, You will be surprised... but we have decided to keep current PlatformIO 2.0 license in PlatformIO 3.0. We will be maximum permissive to our PlatformIO ecosystem and our Partners. MORE OPEN SOURCE TO PLATFORMIOPlatformIO 3.0 (as 2.0) will be released under Please sorry that disturb you. Sincerely, PlatformIO Organization. We want to thank @TimJay and @eclipse Foundation for the great discussion and professional consultation. Tweet: https://twitter.com/platformio_org/status/702981769985966087 |
Thanks for keeping us updated. |
<3 the Apache + MIT licenses, thanks @ivankravets! |
* develop: Fix incorrect line order when converting from INO to CPP and pointer is used Fix unit test Notify about `version` field when creating library Add support for SparkFun Blynk Board Return valid exit code from ``plaformio test`` command Disable SSL Server-Name-Indication for Python < 2.7.9 Version bump to 3.0.1 (issue #772) Disable temporary SSL for PlatformIO services // Resolve #772 Version bump to 3.0.0 (issues #770, #766, #747, #730, #765, #640, #659, #742, #459, #542, #763, #759, #753, #757, #749, #748, #745, #519, #709, #743, #413, #498, #410, #740, #361, #414, #554, #732, #588, #475, #461, #101, #719, #721, #537, #415, #522, #289, #556, #570, #456, #617, #432, #408, #479, #667, #510) Fix menu height for docs Fix issue with multiple archives when linking firmware Add migration guide for PIO2 to PIO3 Search libraries by headers/includes with ``platformio lib search --header`` option Update pio run command examples Add Unit Testing Demo Update PIO Plus badge title and link Add PlatformIO Plus badge Add links to PlatformIO Plus
MORE OPEN SOURCE TO PLATFORMIO AND NO GPL
#510 (comment)
Dear,
Thanks a lot for your contributions. We are going to continue work on PlatformIO 3.0. According to #490 we decided to keep FREE & OPEN SOURCE PlatformIO 3.0. However, the license will be changed
form Apache v2.0
to AGPL v3.0
In this situation, we would ask you to transfer all copyrights for your
code/modification/fix
to Ivan Kravets @ivankravets. Please post here your comment with you decision: AGREE or NOT AGREE.If you are not agree with the next changes your
code/modification/fix
will be removed from PlatformIO 3.0.UPDATE: The license will be changed THE ONLY for PlatformIO Core. The all source code which has relation to build scripts, boards and frameworks will be moved to separated repositories under Apache 2.0 license. More details #479
UPDATE 2: The license above is updated to AGPL v3.0
UPDATE 3: The license will be not changed in PlatformIO 3.0 #510 (comment)
Sincerely, PlatformIO Organization.
The text was updated successfully, but these errors were encountered: