Re: Developing Open Source Software

Josh Sled <[email protected]> Fri, 01 Aug 2008 09:22:42 -0400
Newsgroups gmane.comp.programming.language-of-the-year
Message-ID <[email protected]>
"Tushar Joshi" <[email protected]> writes:
> * When you work on an Open Source project after your usual job hours
> is this approved by the employer?

Why should they care or even know about what you do on your own time?

> * If you develop a open source project with license like LGPL is it
> allowed by the Employer to use that LGPL library in commercial project
> you are working?

Why wouldn't it be, if the project was otherwise suitable for use in the
project (i.e., not because you are associated with it, but because it's
otherwise an appropriate choice)?

> * What is the recommended practice followed by most software
> professionals who contribute to Open Source projects in terms of
> working hours?

I think the question is more about intent and conceptual overlap.  If you're
working in a certain domain for your employer (let's say … working on a
custom CMS solution), and in your free time you're writing a different CMS
app, it's at least going to be suspicious, and at worst there might actually
be something improper going on.  If you're getting paid to produce something,
then you should probably devote your efforts to producing that thing, not
producing two of that thing.

I guess the question gets a bit more muddled if the open-source thing is a
library or framework that the employer is using, but isn't directly related
to their domain. Then it's probably handy to work on an explicit
understanding with the employer about how time is spent helping the two
projects.  If you need to fix a bug in the library during work hours, &c.

Of course, if there are other concerns (non-compete contracts,
Copyright-assignment contracts, &c.) then those will trump philosophy … but
those can also be modified as necessary.

If there's doubt, it's probably best to have an explicit (and
legally-recognized) memorandum of understanding with your employer about
your particular situation.

-- 
...jsled
http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
signature.asc (application/pgp-signature, 196 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkiTDiMACgkQXze2dBAuga1MYACfUCFF1LVeI06a8Ed9ZxeuZQQg
N9gAoIlKBDyum5S38UMTZVK4vDIwpXfH
=Pv37
-----END PGP SIGNATURE-----