Slashdot Mirror
Real Name For Open Source Development?
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?"
An open source project is an unlikely target for a patent troll. Trolls by definition are not in business actually implementing the technology that is the subject of their patents, so your open source project doesn't hurt them directly. Unless you're making lots of money selling your open source software, there's not much they can hope to sue you for.
If you are looking to for personal liability protection then you should create a corporation under which you do all your software development, which might even include hobby or GPL work. This is probably overkill, but it may be a good idea if you think that there's any possibility of building a business around your hobby work in the future. In that case you might be able to claim some tax breaks for the cost of your computer, internet connection etc.
Hiding behind a pseudonym is only helpful in the case where you are doing something very illegal or commercially disruptive, in which case you need to do a lot more than just choose a handle, eg offshoring, money laundering etc. See online casinos, spammers, and porn sites for ideas...
you should always use your real name when publishing online!
As long as I sign my code as Blue Salad, they'll never guess I'm really "Green Salad." Muh haha
I bothered to read every letter of a contract I signed with a company I once worked for and it had the peculiar verbage something to the effect of "... every idea or product developed by the employee during their employment at CompanyX is intellectual property of CompanyX." I got some clarification which resulted in the understanding that that particular phrase was left open so that if I went home and wrote an NLP engine from scratch while I was employed, it was their intellectual property. Let's just say at that time I needed the money and my foot in the door so I did take that temporary position.
From that early moment on, all contributions have been pretty darn anonymous. Remember, you're not just protecting yourself, you're protecting other OSS developers, other OSS companies and more importantly the users.
I've never had any problems submitting my code as Bill_Gates55, but RMS1953 can sometimes get me into trouble. Of course, nobody would believe me if I used my real name; Girls don't program.
#fuckbeta #iamslashdot #dicemustdie
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.
Either as a user or developer, if you have enough money/influence that the patent holder cares to sue you, it won't matter much if you post anonymously: your real name in all likelihood will be discovered in due course.