Read the GPL carefully. Read your employment contract carefully. Remember you can't un-GPL source code; all you need is a GPL'ed "core" that you can build on, that can be produced by anybody. Perhaps yourself if works created in your own time are your own property. Then just make sure you're not specifically prohibited from sharing the changes.
My opinion is that this is acceptable except where the changes you are making need to be kept secret for competitive advantage, in which case you need permission. Sam. On Tue, 19 Mar 2002 09:20:22 -0000 "Clayton, Nik [IT]" <[EMAIL PROTECTED]> wrote: > Morning, > > [ Apologies if there's any misformatting, or a horrendous disclaimer at the> end. ENOCHOICE about using Outlook. . .] > > So I'm writing some (hopefully) fairly useful Perl modules at $dayjob, and> want to release them to the outside world. I suspect this is going to be > a novelty to the corporate lawyers. > > Has anyone here had experience of doing this sort of thing at large > companies, > and making the arguments for open source'ing your code? Any war stories, or> tips you can pass on? > > N ([EMAIL PROTECTED], for those of you that know me there. . .) > > > -- Sam Vilain, [EMAIL PROTECTED] WWW: http://sam.vilain.net/ 7D74 2A09 B2D3 C30F F78E GPG: http://sam.vilain.net/sam.asc 278A A425 30A9 05B5 2F13 Hi, I'm a .signature virus! Copy me into your ~/.signature, please!
