-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Migrate to MIT License #347
Comments
@marclaporte yes, definetely to do next. |
@marclaporte what are the requirements for this issue to be completed? |
@marclaporte can you help us? |
Sure! Big picture steps: 1- Announce intention: all new commits have to be dual-licensed MIT and current license. Done 2- Identify aliases: https://www.openhub.net/p/bootstrap-switch/aliases 3- Contact all the code committers, which still have code in the current master. Template example here: https://tiki.org/Bootstrap+License+change+request 4- Get them all to agree (The best is to vote +1 on this thread. An email works as well ) 5- If some refuse or are unreachable, rewrite their contributions 6- Release new version as MIT Thanks! |
Here is template mail: Title: Bootstrap Switch License Change: Please add your +1 for a license change from Apache to MIT Hi! I hope you are well. I am volunteering for Bootstrap Switch (http://www.bootstrap-switch.org/) on changing the license from Apache to MIT (like Bootstrap did) and am asking for your confirmation. Short version: Long version: Bootstrap was reported to be "Now Styling 1% of Websites" and we wanted to increase this :-) There are various interpretations. Some say that this change is not necessary. According to http://www.dwheeler.com/essays/floss-license-slide.html and according to the FSF The safest/simplest for Bootstrap Switch is just to change the license, which is what Bootstrap did (hundreds of people accepted). It opens the door to becoming bundled as an official component in Bootstrap down the road. You are, of course, entitled to saying "no" to the proposed license change. Nobody likes it when the rules of the game have changed after the game started. However, we really want to keep your contributions, so please go ahead and support the change :-) So please find the link above and confirm that you accept this change. For the people whom we can't reach or for the commits of the people who say no, we will have to remove their code, and rewrite. So please do save us that extra work :-) Thanks and best regards! Related links: |
+1 |
BREAKING NEWS: something in the world isn't compatible with the GPL. +1 |
👍 for moving to MIT. :) |
@frapontillo i don't get your point. If you wanna change the license of the project you need approval by all the contributors. GPL or not it does not change anything. |
Since when? I thought the project owner can change the licence whenever they want to whatever they feel like? People can object if they don't like it afterwards, and can request to have their contributions removed. |
This is not directed towards you or anyone who contributed in this project. I completely get the move towards MIT license, I accept it and embrace it. |
@GrahamCampbell since forever. If you contribute to my project I cannot take your contributions and for example make them proprietary, unless you agree on it. Your contribution is still your IP, not mine (unless you specifically give IP rights to me when you contribute). Now I'm not a lawyer and I might be wrong, but the Internet says so https://stackoverflow.com/questions/9122969/change-open-source-license-of-my-own-software @frapontillo we are moving from Apache to MIT, where is GPL involved? Where are we supporting GPL? Sorry but I don't get your point |
@volpino as I understand it, this license migration is subsequent to Bootstrap changing its license due to "unclear" integration possibility with Drupal, which is released under GPLv2. |
@frapontillo oh I see! The problem is more Drupal using GPLv2 and not GPLv3. But yeah I get your point. However I think it's really important to care about all this "legal fuckery", you will never know when it will become useful for not being fucked. Examples: |
As a contributor I support the licensing change 👍 Go ahead and check my name off. |
+1 |
1 similar comment
+1 |
time to start sending out emails. shall I make a list? I'm think just link to this issue# |
+1 |
1 similar comment
+1 |
Please guys! MIT is coming! |
I'm sending email / tweets / pigeons to these people... |
+1 (pigeon worked out) |
Good idea about the pigeons :-) |
+1 |
Sorry guys I didn't follow my github notifications lately. The mail worked out ! :-) |
I checked what the missing people did for this library and... @pauloortins: https://github.com/nostalgiaz/bootstrap-switch/commits?author=pauloortins @BdMdesigN : https://github.com/nostalgiaz/bootstrap-switch/commits?author=BdMdesigN I think that we are blocked by @BdMdesigN . @marclaporte can you check what i said? |
+1 Sorry, I was traveling and away from the PC. |
Ok, we are definitively blocked by @BdMdesigN (I'm spamming him a little bit today, I know) |
+1 good idea |
@nostalgiaz It seems that the account |
@cvsguimaraes I wrote with him a lot in the past, but the email was |
@nostalgiaz : "They wrote code that was replaced over the ages" ok, so let's skip these. @nostalgiaz : about @pauloortins and the commit which is documentation -> Let's not worry about it as it's not code. If this person requests it in the future, we can remove. So once @BdMdesigN (who does have quite a few commits) approves, we are good to go! Thanks! |
I've tried to reach @BdMdesigN via |
I tried as well... |
News? |
@LostCrew have you tried to call him at home? |
Do it ! |
yeeeeeeeeeeeeeeeeeeeeeeeeeeeeee @marclaporte we are ready! |
Sorry for the long wait, but im working on a game now, so i don't have many time |
his alive!1!1!!1 |
Yes i'm alive. |
My fork is uptodate now, send me if you update the master branch a pull request please |
Fantastic! Thank you @BdMdesigN @nostalgiaz @LostCrew and all! |
Hi!
I suggest to change to the same license as Bootstrap:
twbs/bootstrap#2054
Thanks!
The text was updated successfully, but these errors were encountered: