f) convoluted build process which is impossible to recreate outside NVidia
g) some code is licenced from somebody else
h) obvious NSA backdoor built in
f) convoluted build process which is impossible to recreate outside NVidia
g) some code is licenced from somebody else
h) obvious NSA backdoor built in
However, that same type of stuff may not reflect other organizations and members of those organizations in a good light. So there are definitely concerns there.
I'm a developer, and my company's closed source code definitely has its share of profanity and "WTF"s. But that would not fly for things we make available on GitHub, just due to concerns of our image. Most developers wouldn't give two shits about the comment...
Unless your fellow developers are posting extremely obscene racial slurs and threatening rape on the interns. In which case your company has bigger issues to worry about.
> When we created mozilla.org and released (most of) the source code to Netscape Confusicator 4.x, Netscape's lawyers made us go through a big "sanitization" process on the source code. Largely this consisted of making sure we had the legal rights to all the code we were releasing, and making sure every file had proper and accurate copyright statements; but they also made us take out all the dirty words. Specifically, "any text containing vulgar or offensive words or expressions; any text that might be slanderous or libelous to individuals and/or institutions."
http://www.jwz.org/doc/censorzilla.html
Even John Carmack was pressured by the lawyers when he open-sourced Doom 3.
http://www.techspot.com/news/46391-john-carmack-releases-doo...