1 |
On Fri, Dec 21, 2012 at 12:01:00AM -0500, Rich Freeman wrote: |
2 |
> On Thu, Dec 20, 2012 at 11:08 PM, Greg KH <gregkh@g.o> wrote: |
3 |
> > On Fri, Dec 21, 2012 at 02:32:25AM +0000, Robin H. Johnson wrote: |
4 |
> >> 1. Are you party to any *copyright assignment* (eg FSF copyright assignment)? |
5 |
> > |
6 |
> > You need to rephrase this to be (in order for it to make any sense): |
7 |
> > Are you party to any *copyright assignment* that is not part of your |
8 |
> > employment agreement? |
9 |
> > |
10 |
> > Otherwise, everyone in the US, and most other countries, would almost |
11 |
> > always have to just say "yes" to this, as their employer owns the |
12 |
> > copyright for their work no matter what it is done on (open source or |
13 |
> > not.) |
14 |
> |
15 |
> Work done for hire is certainly owned by the employer, unless an |
16 |
> agreement to the contrary is explicitly documented, but employment |
17 |
> agreements that purport to assign copyright for works unrelated to |
18 |
> employment to the employer are rare. Maybe they're not as rare in the |
19 |
> software industry, but most people aren't employed in the software |
20 |
> industry (even if most Gentoo developers might be - though perhaps not |
21 |
> as a big a majority as you might expect). |
22 |
> |
23 |
> Certainly I haven't signed any kind of document that assigns ownership |
24 |
> of works created on my own time to my employer, and the legality of |
25 |
> any contract I did sign to that effect would be dubious. |
26 |
|
27 |
That's not true in the US, in fact, it's the exact opposite. Your |
28 |
employer has ownership of all of your work, even done on your own time, |
29 |
unless you explicitly have permission otherwise, if it is done in an |
30 |
industry that is related to your employer. Read the traditional US |
31 |
employment agreement for details about this. |
32 |
|
33 |
Yes, some states allow for exceptions to this rule, but those are the |
34 |
exceptions (California has some unique changes here). |
35 |
|
36 |
You might have signed these types of agreements when you were hired by a |
37 |
company, and didn't realize it, it's usually quite well hidden in the |
38 |
agreement. |
39 |
|
40 |
Now this is all for the US, Europe has other types of laws, but they |
41 |
still assign ownership/copyright of what you do while being paid by |
42 |
those companies, to the company, and not to you. Again, there are |
43 |
exceptions, but traditionally that is how they work. |
44 |
|
45 |
> > Remember, in the US, individuals who actually own the copyright on the |
46 |
> > work they do is quite rare once they get out of college, and even then, |
47 |
> > while in college, the school does have the right to assert copyright |
48 |
> > ownership of the work, depending on what it was done on/for (who |
49 |
> > provided the equipment, tasks, etc.) |
50 |
> |
51 |
> Ownership of "work" in the sense of something you're paid to do |
52 |
> usually does tend to reside with whoever is paying you to do the work, |
53 |
> unless you're a consultant of some kind or otherwise paid by the |
54 |
> engagement (in which case it is usually spelled out). Ownership of |
55 |
> stuff like the photos everybody will be taking next week with family |
56 |
> rarely ends up belonging to an employer. |
57 |
|
58 |
Photos, yes, but all joking aside, go read the agreement, they are |
59 |
incredibly broad. As numerous "inventors" have found out the hard way |
60 |
over the years when their companies end up owning the rights to things |
61 |
they have created "on their own time". Again, some states have rules to |
62 |
try to give rights back to the individuals (like CA), but those are |
63 |
rare, and only cover limited things. |
64 |
|
65 |
I speak from person experience about this. I used to work for IBM, and |
66 |
IBM's employment agreement is so broad, the joke used to be, "the only |
67 |
thing you could do on your own time that isn't owned by IBM would be to |
68 |
mow people's lawns for them." That joke turned into reality when a |
69 |
coworker of mine started a landscaping company and eventually quit to |
70 |
run it full time. |
71 |
|
72 |
The rules involved here are complex, and usually never in an |
73 |
individual's favor for they don't get to write the rules. |
74 |
|
75 |
Be mindful that if Gentoo is to go down a "assign copyright to the |
76 |
Foundation" type of arrangement, they are going to run smack into a |
77 |
whole range of people's employment agreements, almost all of them which |
78 |
will prevent them from participating unless they get explicit agreement |
79 |
from their employer. |
80 |
|
81 |
Just ask anyone who has had to get their company to sign the FSF |
82 |
copyright assignment paperwork, for just how hard that was, and how long |
83 |
it took. |
84 |
|
85 |
thanks, |
86 |
|
87 |
greg k-h |