If it's on company time it's All Rights Reserved and will never see the light of day. Way too many lawyers over here. Anyways it looks for my perticular case I'll probably end up with just a BSD header (was most likely overthinking/overparanoid), but as I keep repeating, and which Rob pointed out, it would be a good thing to a have a documented guideline (based on consensus) about what can be accepted into the repo. Key questions like is-gpl-compatability a must? Not all OSI licenses are IIRC.
On Tue, Nov 8, 2011 at 12:50 PM, Platonides <[email protected]> wrote: > On 08/11/11 02:52, Olivier Beaton wrote: >> What do I gain by not using gpl? Commercial use and forking under a license >> of your choice. The only thing that concerns me using bsd is how to accept >> contributions that im not merging in safely. Is zend framework concern with >> bsd and their use of a contrib agreement ? >> >> My employer asked me to make modifications to mw for their use, i chose >> instead to spend my free time so i can share them with others. I cant use >> gpl even if i wanted to. > > GPL doesn't preclude commercial usage. > It requires you give others the ability to give the same (freedom) > rights you gave them, but if the extension is going to be published in > our svn, that doesn't seem a problem. > Depending on your employer, you may be able to develop it in company > time releasing the result under a free license (if the collaborative > method results in having a better extension, your company will benefit > from having the FOSS developers improve it, and reduce the time you'll > need to maintain it as a fork). > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
