Who Owns Your Weblog?
An anonymous reader asks: "If you're a weblogger, have you read the fine print of your employment agreement? Many webloggers are techies and many tech employers have highly restrictive IP clauses in their employment contracts - the employers owns you and everything you do whether at work or at home or anywhere else. Are you sure you own your weblog? You may not be allowed to take it with you when you change jobs." As always, please remember to look over those employment contracts before you sign. With that point mentioned however, are employers still likely to employ someone who is willing to argue points on their contract, especially in this economic climate?
There are no karma whores, only moderation johns
I never let anyone have my ideas. I always disclose that I have the rights to all my work, and my employer has no rights at all, unless I implicitly assign them. I usually do, but hey, still, I'm not going to sell out. I have yet to run into any issues in the past, and this was for a government contractor.
They barely have any idea what to do by themselves. It's not the economy it's the desperation of the employer to get the document finished.
The message on the other side of this sig is false.
Adding the word "Weblogging" hardly makes this news. If they own "everything" then surely that encompasses "weblog", no?
All I know is I can't ever sign anything like this. I can't afford to potentially taint my external
I work in california.us, where we have laws about this kind of thing, for example:
Larry
The doc was much like previous ones, but contained a total assignment of all copyrights. I thought that was over-reaching, and modified the language to read exactly like for inventions and patents "in the course of or resulting from employment". Signed and sent the form in two years ago. No probs. They won't look at it unless they want to fire me, and even then, likely will not notice because the language is totally innocuous.
Still posted as AC for obvious reasons.
My experience was at the American Red Cross. I was responsible for maintaining our local list of ineligible blood donors (positive infectious disease test results and the like). One day, everyone in the place was presented with a new "employment agreement" which we were supposed to sign. One of the provisions indicated just what is described in this story; specifically, anything I happened to create, invent, design, etc. - whether during work hours or not - belonged to the American Red Cross unless they decided to relinquish those rights. Now, I'm no kind of inventor but I was 23 years old with few responsibilities beyond myself and so I was the perfect person to protest this agreement on pure principle. I adamantly refused to sign the paper because I felt that it gave too much power over my life to my employer, not to mention the fact that a non-profit corporation specializing in disaster relief and blood collection/distribution shouldn't have an interest in anything that I create (assuming it has nothing to do with disaster relief, blood collection, etc.).
At first, I was told that if I didn't sign the paper I was risking the loss of my job. I maintained that this was a chance I was willing to take (and encouraged others to do the same). About a month later, the new employment agreement was revised into a more palatable format. Though I can't recall if it specified inventions/creations relating specifically to my employment or if the clause was taken out completely, the document was acceptable and I signed.
My advice is pretty simple: Check your state/local laws - as in a post above, an overly restrictive clause of this nature could be invalid on its face. If it IS valid, then you have to decide if a) you're willing (and financially able) to leave the job on principle to hopefully find one where you're not forced to sign such an odious document, b) you're going to create/design/invent something in which your company would want to claim an interest or c) you know you're not going to create something that you will want to sell (or release, a la open source) to which you could lose your rights. After all, while a company could theoretically lay claim to, for example, your David Hasselhoff fan site, they probably won't. On the other hand, if you create brand new database software in your free time while working for [any] software company, they could potentially strip it from you and from anyone else to whom you have given or sold it.
At the risk of going too long, remember too that Steve Wozniak worked for HP when he created the Apple computer. He offered it to them because as part of his contract he was required to do so. They had no interest at all, which I'm sure they regretted for a long time.
The question doesn't make sense. Is the poster asking about weblog software developed on company time, or weblog entries made from home? If I fix a friend's computer, the company I happen to work for don't suddenly own it, nor can they send said friend a bill -- that's just silly. My weblog used to live on my own personal bit of webspace given to me as part of my private dial-up account, in no way funded by any company I've ever worked for. I might have been concerned about some cow-orkers reading it, but not the company owning it. Would they own any letters I post to a newspaper? No, again, silly.
I had a huge fight with my weblog host. They locked me out of my blog, and refused to relinquish control when I migrated to a new host, leaving my old dead blog to compete with my new blog. I had to file a DMCA complaint to get back control. The asshole webhost still doesn't realize how close they came to having their entire system disconnected, just because they decided to be vindictive and fuck with me. I felt really bad about considering a DMCA complaint until I finally came to the conclusion they were just being plain malicious assholes and the DMCA was my only recourse without hiring a lawyer. So I filed, they drug their feet but finally caved in, only an hour before their upstream was going to pull the plug.
The quoted name is my spin-off...
and - it's been a so long since I
first read about it - that I may
have the number of team members
wrong...
But the idea is something like this:
It's a business model for database-based
web system design that brings [4 or] 5
talents together to work on a stream of
projects, rotating "hats" (ie, Project
Manage, Programmer, Customer Liason,
Graphic Designer, et al.) as they move
from one project to another.
As the number of projects grows to be
more than one "Gang of [4 or] Five"
can handle, another "Gang" forms to
handle the overload.
I suppose there could be a loose coupling
between the various, independent "Gangs"
(eg, to enable "load balancing" to happen),
but they could just as well remain separate
entities & control their own destinies...
a bit like music bands.
Thus, if you control your own destiny,
you can write your own IP clauses...
to encourage members' creativity,
while still protecting Clients' rights
to their IP & sensitive business info.
I can see a contract (akin to the GPL),
- incorporating these IP terms - that
each "Gang of [4 or] Five" would find
acceptable.
Of course, I can also see a family of
such contracts (like those that have
been embraced by one or more developers
of various flavors of Open Source S/W),
that new "Gangs" could choose, accord-
ing to their &/or their current Client's
preferences & needs.
IMO this problem has an easy solution!
Who says you can't make a deal ($ for use)
like that, but which doesn't force you to
give away something you value?
Such a deal might save you travel time,
eg if you're (otherwise) on-call, ie
when you're needed back at the office
(you might aleady be there, doing your
own thing on contracted gear, using a
fast 'net connection you've contracted
to use on a strictly after-hours basis;
walk over, fix their glitch [quicker than
you would if you had to drive in first]
& later resume your own project work...)
It might help put a bit of pressure on employers,
eg if their contractual IP terms were -listed- on
a well-known web site, that people could consult,
just before job-hopping...
If it were -also- suggested that -less- creative
people (ie those with little to lose by signing
a -bad- IP contract) were more likely to be the
ones working at one category of company, than
the other category...
well, those companies concerned about their
reputations in the market (eg, as being very
innovative), might re-think their IP terms,
etc.
At the risk of going too long, remember too that Steve Wozniak worked for HP when he created the Apple computer. He offered it to them because as part of his contract he was required to do so. They had no interest at all, which I'm sure they regretted for a long time.
And I'm sure they won't make *that* mistake again.
I always argue whatever points I feel unfair on my contract. The last 3 jobs I have had, I have had them change that clause so it only includes what I do in my working hours.
I find that clause so completely unacceptable, and I think any workplace who would not concede to change it, are a bunch of nasty buggers anyway.
I argue that I partake in open source projects and free/shareware. That's usually ample argument.
Give me liberty or give me kill -s 9
Your employer typically has no interest in your weblog, or he novel you write in your free time (unless they're a publisher), or anything that's not related to their business.
Simply ask them to exclude anything that is done entirely in your free time without use of company equipment, and most companies will accept. It doesn't cost them anything, and even though the market is in decline, they still don't want to get rid of employees over trivial disputes over contractual clauses.
"They had no interest at all, which I'm sure they regretted for a long time."
As such, companies now are trying to retain rights to _everything_ rather than let anyone catch a break from them.
Although the temptation is to argue the toss, I think it tends to depend on what's being talked about...if you develop a competing product at work, then there's no doubt that you owe them, but there isn't a chance in hell that I'd let my company have any part of my life outside hours or the front doors unless they plan on paying for them. Start on that slippery slope and they'll take, and take, and take...
It's important to note that anyone being told that their job is on the line if they don't sign a contract is _specifically_ disallowed by pretty much all employment law in the western world, and a threat like that would be worth a mint in litigation court.
The correct answer to such a threat is 'Can I have that in writing?'
Oddly Draconis
Too cynical to live, too stubborn to die.
Either you walk away or:
;) ).
a) Negotiate. (if you have good rapport)
OR
b) Change the contract explicitly - strike out paragraphs. (if you have good bargaining power or couldn't be bothered).
OR
c) Write a new contract that looks almost the same and use it.
(if you don't have bargaining power).
Yes. Change it to suit yourself. Print it out again make it look almost exactly the same - fonts, layout etc.
If both parties sign it, then it's agreed then. Hey they entered into it with their eyes opened right?
Just tell them you need time to think about it. Go home, pick the right fonts, similar paper and reproduce the whole thing with a few custom changes.
Remember keep a straight face, sign it, give it to them and they'll probably sign it without reading the fine print (idiots
If they notice, well you've proven one thing to them at least:
1) you're resourceful.
2) you're one of the few who treat what they sign seriously. Not one of the sheeple.
I've successfully done a similar thing before on a so called NDA. Took me a couple of hours to retype the thing and get the font sizes right.
But let me put it this way - the new NDA didn't restrict my rights at all...
Of course in the US you might come under the DMCA for reverse engineering the contract document or some other dumb US law. But I'm not in the US.
I've been asked to sign that kind of agreement about three times in my career, and every time I have declined on the grounds that it would give them rights to my web site, any code that I wrote to update Opensource projects, and even personal emails that I write to my family while at home.
In no case I have ever seen was a person actually fired for not signing one of these. On the other hand, I've never been in a situation where I had to sign one of those to get hired in the first place. Are there any actual experiences out there in that direction?
Wake up - the future is arriving faster than you think.
I know mine has very few details of my work life, primarily because I have no interest in writing about work when I'm not at work. If I were to post some details about my work that my employer might consider theirs, I'd be more afraid of losing my job, rather than taking that information with me and facing the consequences.
Does anyone know people that actually post copyrighted code, inside stock information, blueprints, etc. on their weblog??
Children in the backseats don't cause accidents. Accidents in the back seats cause children.
My contract has the usual sort of clause assigning rights to my employer for things I create. It also has a specific exemption (that they put in, not me) for anything created outside my normal working hours and unconnected with my employment.
I asked to see a copy of the full contract before accepting the job, precisely to check whether such a clause was there. If it hadn't been, and they hadn't been prepared to insert one, they wouldn't have got me.
No, the employment market is not so bad that I will sign away potentially life-changing rights before I even know I have them. If I'm going to work for a company that wants that sort of control over my soul, I'll do it flipping burgers or stacking store shelves, not for someone who's bottom-feeding off my hard-earned expertise.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
Don't use your real name; use a pseudonym. Seems pretty straightforward.
That lack of interest can disappear very quickly if your part-time project becomes a commercial success. Greed is a great motivator.
Mea navis aericumbens anguillis abundat
Where do you stop the slippery slope?
IANAL but write like a drunk one.
It wasn't presented as an arguable point. It's more like refusing to give a SIN (Canada's version of SSN) or something. The contract is done and now you're just fulfilling the legal necessities of implementing it. Welcome to non-competition docs, global intellectual property agreements etc. I believe prior to that in interviews all I ever agreed to was making myself available to travel at the drop of a hat. Then a few months later after my work became critical I found carrying a pager and cell phone and being accessible 24/7 to any of 150 people ranging from co-workers to customers to suddenly be a new job requirement. That one still pisses me off. We're having huge disagreements about whether I need to be carrying a cell phone on *_vacations_*.
This doesn't make sense. A web log is akin to a journal or diary. How many employers assert ownership of employees' diaries? How many IP clauses in employment agreements could reasonably be construed as applying to diaries? Do you really think the IP ownership clause in your contact would be applied to a note you write in a mother's day card?
Now if you are a journalist, reporter, or employed in a fashion along those lines as an employee and not a free-lance contributor, then I could see personal writings made public as in a web log getting some scrutiny.
Actually there's an entirely different issue which is more realistic, more likely, and more probably a practical concern. It occurred to me before I finished reading the article and is alluded to by another post regarding moving a web log from one host to another.
Does your web log host own your log? What's in your hosting agreement? Can the hosting company repackage/reprint/redistribute entries from your log in whole or editing without your permission or knowledge?
That's the real story.
I think the point is read the contract, take what you sign seriously. Don't make assumptions. Chances are the clauses are worded as broadly as possible.
Last year, I took a job at a large company, and based on all of the scuttlebutt that flies around Slashdot, I feared that I would be subject to the type of employee contract that the original poster talks about. In the past, I had worked for a number of smaller firms. While they each had a contract for me to sign with regards to assignment of copyrights and patents, they were all limited. Now that I was about to embark on a career in the Fortune 500, I was afraid that they would make me sign a onerous contract without any flexibility to change it.
Boy was I wrong.
When I received the paperwork in the mail (they wanted me to fill out forms before I started, in order to speed the process along), I immediately flipped to a document entitled "Employee Proprietary Information and Innovation Agreement". I scanned it to see how many vials of blood they wanted to extract. To my delight, it was quite fair. Basically, it said that I had to assign rights to work that fell into three categories:
1. Work that related to the business of the company (i.e. I couldn't develop a competing product on my own time and profit from it).
2. Work the resulted from or was suggested by work that I had done for the company (i.e. I couldn't develop of product based on something that I had done with the company).
3. Work that was done using company time, equipment, or facilities (i.e. something that I did on company time or property).
In addition, in bold letters there was an additional paragraph stating, in clear language, that I am NOT required to assign rights to anything that I did on my own time and equipment, and that didn't relate to the companies business, and wasn't conceived based on something I did at work.
If that weren't enough, there was a section that I could declare works that were developed prior to my employment at this company, and these would be specifically excluded from assignment. That way, there would be no confusion about what I retained the rights to.
Personally, I thought this was a very fair agreement, and it made me feel good about the company I was going to work for. Also, it shows that, unlike what the original (paranoid) poster implies, companies are out to screw you out of your weblog rantings!
------
www.moneybythenumbers.com