Earlier quoted context omitted.
I think most people would imagine a project called " Twitter Bootstrap" that was developed by people "employed at twitter on twitter hardware" would be property of Twitter. Does Twitter own the copyright?
right now it's under the Apache License v2 – but we're working to move it to MIT for 3.0.0 I think of the community as owning bootstrap at this point… maybe that's cheesy? Or naive… I also think twitter played a larger roll than just hardware. Mark and I were both deeply embedded into the twitter culture (with access to great resources and really smart engineers to bounce ideas off of) and i think bootstrap has a ver…
What I Learned Building Twitter Bootstrap
11–20 of 72 posts
Re: What I Learned Building Twitter Bootstrap
#12Re: What I Learned Building Twitter Bootstrap
#13Earlier quoted context omitted.
right now it's under the Apache License v2 – but we're working to move it to MIT for 3.0.0 I think of the community as owning bootstrap at this point… maybe that's cheesy? Or naive… I also think twitter played a larger roll than just hardware. Mark and I were both deeply embedded into the twitter culture (with access to great resources and really smart engineers to bounce ideas off of) and i think bootstrap has a ver…
(speaking of cheesy) Those who just create awesome tools and release them into the ecosystem free of charge add immeasurable value to the community. I really want to thank you for how much easier you two have made my life with bootstrap on numerous occasions.
Re: What I Learned Building Twitter Bootstrap
#14Earlier quoted context omitted.
(speaking of cheesy) Those who just create awesome tools and release them into the ecosystem free of charge add immeasurable value to the community. I really want to thank you for how much easier you two have made my life with bootstrap on numerous occasions.
aww <3
Re: What I Learned Building Twitter Bootstrap
#15Also, was it put on Twitter's GitHub account in order to increase visibility?
Re: What I Learned Building Twitter Bootstrap
#16Interesting... For some reason I had always assumed that Bootstrap was associated more closely with Twitter because it had the word "twitter" in the name. Now I understand why some business are so concerned with preventing other websites and people from using their name. I'm not saying that Twitter should have demanded that these guys change the name of their framework to something else, but this is a good object les…
I think the message the blog post is conveying is that Bootstrap grew out of two developers wanting to build something, not out of a manager wanting to setup an internal project and assemblying a team being instructed to work on the project.
Re: What I Learned Building Twitter Bootstrap
#17Earlier quoted context omitted.
(speaking of cheesy) Those who just create awesome tools and release them into the ecosystem free of charge add immeasurable value to the community. I really want to thank you for how much easier you two have made my life with bootstrap on numerous occasions.
aww <3
Re: What I Learned Building Twitter Bootstrap
#18I push it and nothing happens.
Re: What I Learned Building Twitter Bootstrap
#19Re: What I Learned Building Twitter Bootstrap
#20Earlier quoted context omitted.
I think most people would imagine a project called " Twitter Bootstrap" that was developed by people "employed at twitter on twitter hardware" would be property of Twitter. Does Twitter own the copyright?
right now it's under the Apache License v2 – but we're working to move it to MIT for 3.0.0 I think of the community as owning bootstrap at this point… maybe that's cheesy? Or naive… I also think twitter played a larger roll than just hardware. Mark and I were both deeply embedded into the twitter culture (with access to great resources and really smart engineers to bounce ideas off of) and i think bootstrap has a ver…
From what I see, the best you have is: "By contributing your code, you agree to license your contribution under the terms of the APLv2: https://github.com/twitter/bootstrap/blob/master/LICENSE
(which isn't really that helpful)
Speaking as an corporate IP/open source lawyer, doing this wrong can hurt you very badly in the long run.