Recent Features
| |||||||||||||
Crowding out OpenBSDCrowding out OpenBSDPosted Dec 6, 2012 1:13 UTC (Thu) by raven667 (subscriber, #5198)In reply to: Crowding out OpenBSD by marcH Parent article: Crowding out OpenBSD
>> GPL projects reusing BSD code very rarely contribute anything back.
>... to the original, BSD-licensed project.
That seems a little crazy. IIUC any patches to BSD licensed code in a GPL project can be distributed under the BSD license back to the BSD project by the original patch author. The author can always license code to different parties under any license they wish. What's stopping people from contributing code back to BSD projects?
(Log in to post comments)
Crowding out OpenBSD Posted Dec 6, 2012 1:51 UTC (Thu) by dlang (✭ supporter ✭, #313) [Link]
Once the BSD code is part of a GPL project, any new patches are by default GPL (the default license of the project). It takes extra thought and effort to make the patches be BSD
In addition, many GPL people believe that it's a much better license than BSD, and so they _really_ want their work under the GPL.
If either of these are the case, then the patches don't get contributed back under BSD
Crowding out OpenBSD Posted Dec 6, 2012 2:39 UTC (Thu) by raven667 (subscriber, #5198) [Link]
> Once the BSD code is part of a GPL project, any new patches are by default GPL (the default license of the project). It takes extra thought and effort to make the patches be BSD
I realize that, it seems like a poor reason. Maybe git needs an "export as bsd" option for ones own code 8-)
|
|||||||||||||