|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
Do I need to inform my employer before contributing to an Open Source Project?there are two scenarios.
1. i am contributing to an open source project from my home. the project is in no way related to my job. (at work, i am involved with telecommunication software, where as i am contributing to linux kernel). do I need to inform my employer before working on this open source project, so that all my contributions can remain open source? 2. same as above, but this time my contribution to open source and my work for employer is related. (writing a proprietary shell and contributing to the open source bash) 3. i am creating an open source project during my spare time and planning to release it under GPL v3. work and my projects are not related. 4. same as above but my project is closely related to a product of my company that i work for. ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail |
|
|
RE: Do I need to inform my employer before contributing to an Open Source Project?> DeĀ : Joseph Hick [mailto:leet16y@...]
> 1. i am contributing to an open source project from my > home. the project is in no way related to my job. (at > work, i am involved with telecommunication software, > where as i am contributing to linux kernel). do I need > to inform my employer before working on this open > source project, so that all my contributions can > remain open source? > > 3. i am creating an open source project during my > spare time and planning to release it under GPL v3. > work and my projects are not related. You should inform your employer, that should be able to provide you with a disclaimer for these projects. > 2. same as above, but this time my contribution to > open source and my work for employer is related. > (writing a proprietary shell and contributing to the > open source bash) Bash is widely used by lots of companies, some of them may even be competitors to your company, but I don't think that this will change something in the competition of your company. But really, if you think it has some relation with your work, first ask to your company, so that it can accept to give you a disclaimer. But your company may want to appear as the author even if your company formally accepts the GPL licence for it. > 4. same as above but my project is closely related to > a product of my company that i work for. Really, I think you must not create this project and release it before getting a formal authorization from your employer. You must inform it because this closely related job may be a competitive risk for your company, andyour company may want to see exactly which terms will be acceptable for the licencing. Your company will not steal your legal authorship rights, but be careful as this may depend on your job contract that may prohibit you to work for other competitors during your contract, and your personal work may be perceived as an unfair competition with your company's products. So negociate this with your employer! In all cases, for any project you want to do that may contain some elements for which your company may be working on or that may be part of its activities (even if your personnal work is not closely related to one of the current projects of your company), it costs you nothing to ask andnegociate with it before risking your job, or other penalties. |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?Joseph Hick scripsit:
> 1. i am contributing to an open source project from my > home. the project is in no way related to my job. (at > work, i am involved with telecommunication software, > where as i am contributing to linux kernel). do I need > to inform my employer before working on this open > source project, so that all my contributions can > remain open source? It depends on local law. Under California law, you need not inform your employer at all. Under New York law, everything you do belongs to your employer unless you have agreed otherwise in writing. YMMV. IANAL; TINLA. > 4. same as above but my project is closely related to > a product of my company that i work for. This is a very dangerous case, and I wouldn't go anywhere near it. -- John Cowan cowan@... http://ccil.org/~cowan If he has seen farther than others, it is because he is standing on a stack of dwarves. --Mike Champion, describing Tim Berners-Lee (adapted) |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?On Jul 7, 2007, at 14:01, Joseph Hick wrote: > there are two scenarios. > > 1. i am contributing to an open source project from my > home. the project is in no way related to my job. (at > work, i am involved with telecommunication software, > where as i am contributing to linux kernel). do I need > to inform my employer before working on this open > source project, so that all my contributions can > remain open source? > > 2. same as above, but this time my contribution to > open source and my work for employer is related. > (writing a proprietary shell and contributing to the > open source bash) > > 3. i am creating an open source project during my > spare time and planning to release it under GPL v3. > work and my projects are not related. > > 4. same as above but my project is closely related to > a product of my company that i work for. your employer's policy on open source software to answer these questions. While members of this list can speculate, this is the only way to start your deliberations. S. |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?> It depends on local law. Under California law, you > need not > inform your employer at all. Under New York law, > everything > you do belongs to your employer unless you have > agreed otherwise > in writing. YMMV. IANAL; TINLA. > i don't understand how can the law allow my employer encroach on my personal life? what i do in my spare time is my personal life. if i want to write a software that doesn't compete with my employer's products and i want to give it to my friends and other people on net for free, why should the law allow my employer to stop me from doing so? i don't need the permission of my employer to have sex in my spare time. then why does the law require that i take permission to write code i want to give away to others for free? please help me understand this. ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?Quoting Joseph Hick (leet16y@...):
> i don't understand how can the law allow my employer encroach on my > personal life? USA law in general permits you to stupidly sign away (most) rights you would otherwise enjoy via one-sided contracts, and the burden is on you to realise that they're not in your interest, and that you shouldn't sign them. However, there are exceptions (abusive contract provisions that are automatically void by statute) in some areas including employment law; as John Cowan says, the amount of statutory protection against predatory employment contracts depends on on state jurisdiction. For California, here's a reference on proprietary inventions agreements, covered in Labor Code section 2870-2872 (i.e., by statute law): http://caselaw.lp.findlaw.com/cacodes/lab/2870-2872.html In brief: Regardless of what anything you sign purports to establish to the contrary, whatever you create entirely on your own time with your own resources is YOURS, not your employer's. Caveat: The burden of proof that you meet those conditions is on you. (Keep diaries and changelogs, for example.) Here are references on non-compete clauses, covered in California by Business and Professions Code section 16600 (another body of statute law): http://caselaw.lp.findlaw.com/cacodes/bpc/16600-16607.html http://www.fed.org/onlinemag/Feb00/tips.htm In brief: No employment-related covenant not to compete can shut you out of your trade or profession, regardless of what you signed (except where you owned the business that "employed" you and are now selling it, or are dissolving a partnership and making such an agreement with your fellow partners). Those covenants are legally void. Often quite different regimes apply in other states. > what i do in my spare time is my personal life. [...] > please help me understand this. As one of my personal heroes, the late Rep. Barbara Jordan (D-TX) used to say, "If you want to play the game properly, you'd better know every rule." (By the way, the shift key's on your left.) -- "Zees American words are too much. Zen our culture you'll wrench; With 'le parking' 'le weekend' & such. Wiz our children we'll be out of touch." Eef you anglicize French, -- L'Academie Francaise in a nutshell |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?Joseph,
IANAL, but I've been working with big companies for many years to make Open Source possible inside. It's an unfortunate part of "at will" employment in America that many states support an employer's rights to all your inventions while under employ. This is a long- standing rule. So for instance when Steve Wozniak made the first Apple motherboard in the late 1970s, he had to take it in to his employers at HP to ask if they wanted to exercise their rights to it. They said, "No Thanks" and the rest is history...but he was legally required to ask. More recently in some states this right has been successfully challenged (California happens to be one of them). In California you can (thanks to a couple of lawsuits) now work on whatever you want on your private time (although you are well advised to document the fact that you have expended none of your employer resources...not even the copy machine...while working on your private invention). So you *can* work on an open source project without your employers consent in California, but you would be wise to use use your own computer, your own internet connection, your own email account, etc. and of course you can't expose your company's trade secrets as part of your after hours work. Responsible project communities (like Apache) will require you to sign a consent form that documents that you have the right to participate. At Sun we decided that since the bulk of employees worked in California, any employee should have the right to pursue Open Source and we wrote a company guideline to this effect. Yet several years later, we were still having individual employees come to us with complaints about their managers (outside of California). The right to all your work is a deep-seated concept in the minds of bosses who want to make sure they are getting every scrap of productive work out of you. Companies like Google and 3M who allow "personal projects" during work are in theory more enlightened. During times of very low unemployment in the technology sector (like 2000 in Silicon Valley) there is opportunity for workers to push back on draconian employment policies. As I always say, nothing ever changes without somebody throwing their body in front of the train...but whether you are that body or not is up to you, ultimately. Nobody can give you that advice. Danese On Jul 7, 2007, at 1:59 PM, Joseph Hick wrote: > >> It depends on local law. Under California law, you >> need not >> inform your employer at all. Under New York law, >> everything >> you do belongs to your employer unless you have >> agreed otherwise >> in writing. YMMV. IANAL; TINLA. >> > > i don't understand how can the law allow my employer > encroach on my personal life? what i do in my spare > time is my personal life. if i want to write a > software that doesn't compete with my employer's > products and i want to give it to my friends and other > people on net for free, why should the law allow my > employer to stop me from doing so? > > i don't need the permission of my employer to have sex > in my spare time. then why does the law require that i > take permission to write code i want to give away to > others for free? > > please help me understand this. > > > > ______________________________________________________________________ > ______________ > Park yourself in front of a world of choices in alternative > vehicles. Visit the Yahoo! Auto Green Center. > http://autos.yahoo.com/green_center/ |
|
|
Re: Do I need to inform my employer before contributing to an Open Source Project?Rick Moen scripsit:
> USA law in general permits you to stupidly sign away (most) rights you > would otherwise enjoy via one-sided contracts, Worse than that: in most U.S. states other than California, *whatever* work a professional employee does belongs to his employer unless there is an explicit agreement otherwise. > as John Cowan says, the amount of statutory protection > against predatory employment contracts depends on on state jurisdiction. Rather, I say that some states make employment contracts predatory even if the contract doesn't say so. -- You annoy me, Rattray! You disgust me! John Cowan You irritate me unspeakably! Thank Heaven, cowan@... I am a man of equable temper, or I should http://www.ccil.org/~cowan scarcely be able to contain myself before your mocking visage. --Stalky imitating Macrea |
| Free Forum Powered by Nabble | Forum Help |