Real Name For Open Source Development? 262
An anonymous reader writes "Do you contribute to open source projects under your real name or a nickname? The openness of open source can be encouraging, but software patents you have never heard of can become a nightmare if a patent troll sues for implementing 'their' scroll bar. A real name also means you end up in the big index we call search engines. An assumed name could be an additional layer of protection, but what are its pros and cons and is it worth the hassle when asked to participate in a meatspace meeting?"
Under my real name, for the most part (Score:4, Insightful)
Right now the only project I actively contribute to is my own. Of course I have my real name on the project site and in the copyright headers. However, my username (on the site and the repository logs) is more of an online nick. The downside of this is that I get lots of e-mails and forum posts where people assume that nick is my real name.
Of course once I'm at the point where I care about liability protection, I'd rather form some sort of LLC to contain my efforts. I really do want to contribute in a way that people know its me, since what's the point of contributing to a project you can't personally claim credit for?
Real, of course. (Score:5, Insightful)
> Do you contribute to open source projects under your real name or a nickname?
Real, of course. Why would I want to hide?
> The openness of open source can be encouraging, but software patents you have never
> heard of can become a nightmare if a patent troll sues for implementing 'their' scroll
> bar.
As a pure unpaid contributor of source code you have no patent liability.
> A real name also means you end up in the big index we call search engines.
I've been using my real name on the Net for more than twenty years. I don't see the problem.
Comment removed (Score:3, Insightful)
For Employment Purposes (Score:5, Insightful)
I never use my real name online, or at least as little as possible. The reason is I don't want future potential employers to be able to Google up any dirt - real or perceived - on me. If I want to bring some of my OSS work to a prospective employer's attention I can do that. I can also pretty much prove that I am responsible for this feature on that program, or that my contributions are legit.
Having you real name associated online with just about anything is IMO a bad idea. The risks are high and the benefits are almost nonexistent. The odds are 10-1 (I just pulled that number out of my ass) that dirt will outrank achievments if you use your real name and someone Googles for you. That one time you got drunk and went off on some insane rant 5 years ago WILL come back to haunt you no matter how many other positive things there are.
Re:Another Con (Score:5, Insightful)
And to the answer...it probably doesn't matter (Score:5, Insightful)
Re:Another Con (Score:1, Insightful)
In that situation, you should not contribute to open source projects, especially not anonymously. The code you write is intellectual property of your employer and unless said employer agrees to contribute it under the license chosen by the open source project, the presence of the code in the open source code base is a major liability for the project. It doesn't help that the project can not shift blame to you when your employer finds out about it because you inadvertently used insider knowledge in your design. That's why big projects will not accept patches unless the author identifies himself and declares full authorship.
Re:Really? (Score:2, Insightful)
Well, that's easy enough to ignore. ._. It's easier to get people to look at the code if they think you're a guy... They don't patronize then.
Either one is fine (Score:5, Insightful)
That's strictly in the online sphere, though. If you're sitting in someone's office working out a consulting contract to build some open source software then yeah, your business card had better have your birth name on it if you want to be taken seriously.
Re:Pffft... (Score:3, Insightful)
I use my first name and my initial, as well as my email, that way you can still reference it when applying for a job (whereas you'd look like an idiot claiming that you did excellent coding work but never gave a real name or used your regular email)
Security Through Obscurity (Score:4, Insightful)
From that early moment on, all contributions have been pretty darn anonymous
But what happens if someone finds out? The project is still in just as much risk. That's honestly not very kind either.
Far better is to clarify and modify that contract you are about to sign. Even the lowliest peon can easily ask to have a clause put in along the lines of "The IP section does not cover inventions made using my own equipment outside of company time" (have a lawyer write the real thing). Because otherwise by blindly agreeing, even your posts here on Slashdot are owned by your employer under the typical agreement.
ALmost any company will let you add an addendum like that to your employment contract. Do not be overawed by contracts, they are simply a starting point.
Re:Another Con (Score:1, Insightful)
of course one should check to make sure that such clauses aren't negated by their state laws.
such as non-compete clauses in california.
Re:probably overkill (Score:4, Insightful)
Of course, if you use the same alias everywhere it is only a matter of time before someone can put two-and-two together. :)
Re:Another Con (Score:3, Insightful)
Just because you sign a contract doesn't mean you can be legally held to it. You can't be legally held to kill someone after signing a contract to carry out murder.
Employers may think that they have dominion over an employee's life simply because they're paying them, but they actually don't. If they aren't directly paying you for the work, there's a reasonable expectation that it is yours. Does the company also own part of your house if you did repairs on it yourself?
Not funny. (Score:1, Insightful)
Reiser brutally murdered his wife. That's not funny at all.
Re:Security Through Obscurity (Score:3, Insightful)
My experience has been that I have gotten an exclusion all three times this has come up. The key is to be reasonable.
Re:Embed your real name in your fake (Score:4, Insightful)
Heck, you could use the SHA1 hash of most near anything. The fact that you have the correct input string to yield that SHA1 hash should be enough to convince just about anyone, provided it's not something stupid like "password1".
That said, your name would be easy to remember...
Re:Let it slip out (Score:3, Insightful)
Not reliably - all that proves is I'm someone with commit access.
with a particular username
Re:For Employment Purposes (Score:2, Insightful)
I use my real name online, almost exclusively. The reason is that I want future employers to be able to Google about me and find out what my views and contributions are.
Having my real name associated online with almost everything I do also helps keep me from ranting like a little kid, because I think clearly before I post something and consider whether I will want to read, in 10 years, that I wrote that. It encourages responsible behavior--a good thing.