4 ms·

I write and release open source code. I also write and release closed source code. Gpl takes that choice away. Us bsd developers use this license so we can work

I write and release open source code. I also write and release closed source code. Gpl takes that choice away. Us bsd developers use this license so we can work together to improve our individual end projects through sharing our knowledge and time with each other. I am very regularly contributing to open source projects that I use. For the benefit of other developers and for the benefit of myself (its more convenient for a bug fix or new feature to be pushed upstream so I don't have to recode my changes)

belorn 12y ago
If you write and release open source code, the license will have no impact on your ability to do so. You can write and release your contributions as BSD, and include others BSD or GPL licensed code. You can write and release your contributions as GPL, and include others BSD and GPL licensed code. If your intention is to release source code and share your knowledge and time with others, the license is not going to effect you. If your intention is add restrictions on other peoples work, then you are taking away the choice from others who want to read and modify the work. This won't benefit other developers, nor will it share knowledge or contribute to developers projects. Making it closed source closes any sharing, modification and redistributing of the work. You demand to have the choice to take away choices from people. I choose to have the choice to take away the choice of taking away choices from others. That is my choice, and you are not allowed to restricting me from having it. If you don't take away the choice, I won't either. My usage of GPL is only needed for as long others want to make proprietary software and remove choices from people.
- ASneakyFox 12y ago
  Your mistaken. Gpl restrictions prevent me from using it in bsd projects. Bsd code can be used in gpl projects. But gpl restrictions prevent the other way around.

belorn 12y ago

If you write and release open source code, the license will have no impact on your ability to do so. You can write and release your contributions as BSD, and include others BSD or GPL licensed code. You can write and release your contributions as GPL, and include others BSD and GPL licensed code. If your intention is to release source code and share your knowledge and time with others, the license is not going to effect you. If your intention is add restrictions on other peoples work, then you are taking away the choice from others who want to read and modify the work. This won't benefit other developers, nor will it share knowledge or contribute to developers projects. Making it closed source closes any sharing, modification and redistributing of the work. You demand to have the choice to take away choices from people. I choose to have the choice to take away the choice of taking away choices from others. That is my choice, and you are not allowed to restricting me from having it. If you don't take away the choice, I won't either. My usage of GPL is only needed for as long others want to make proprietary software and remove choices from people.

ASneakyFox 12y ago
Your mistaken. Gpl restrictions prevent me from using it in bsd projects. Bsd code can be used in gpl projects. But gpl restrictions prevent the other way around.