> Before working for a commercial organization, one usually has to sign a
> contract which makes all the work done during the period of employment
> (including innovations, "hobby" coding done during "after hours")
> copyrighted by the employer. This introduces various problems when one
> wishes to do open source development, especially as a hobby.
>
> I am not talking about companies that do open source contributions as
> institutions (e.g., JFS, XFS, and numerous device drivers). But if one
> wants to do something as a hobby and host it somewhere (say
> sourceforge), or if one wants to send a substantial patch, then it is a
> different story.
>
> For example, if I do some changes and send a patch, and hopefully if it
> is accepted into the kernel, that code becomes GPL. But this doesn't
> prevent the employer from later questioning my right to do so, because
> the patch was never under my copyright according to the contract, and my
> applying of GPL (or whatever the lisence I used) is void.
>
> Obviously, there are many folks who work for commercial organizations,
> but still actively get involved in the kernel development. I am keen to
> know how they get around with copyright issues and contracts.
I suggest you ask your employer for a written waiver to that contract
for GPL'ed work, and make sure it's signed by the right people. They may
want it more restricted, in which case, falling back to the position
of just covering submissions to the Linux kernel.
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:45 EST