Putting our names on our work (incase of misunderstanding)

[thePalindrome]

I'm thinking we should start using our names on the files that we write, maybe as part of the function comments, just as some form of "in case of issue, please contact..." sort of thing...

I mention this because I pull some voodoo in my STDIO, and not everybody gets it, so having that sort of thing makes it easier on everybody.

Any thoughts?

~thePalindrome

[M52]

Seems like a valid idea. I am for it.

[thePalindrome]

Maybe we could try putting it in the @see thing?

[M52]

That could work yes, seeing (no pun intended) as we won't likely refer to other sources THAT often (which is what @see was intended for originally).

[thePalindrome]

Especially when you consider that library calls should be obvious, @see starts to lose some if its charm

[thePalindrome]

Alright, I guess that's it!

Please use the @see to say who wrote it!

[viccuad]

My opinion with this: clearly I don't like this.

As said in this google's advice video about open source communities (really good one!) : https://www.youtube.com/watch?v=Q52kFL8zVoM

bad things:

• people tend to mark the territory: this is mine and you can't touch it unless you talk to me. that's bad. this is a community. the idea of being a community is just to be able to share and improve as easily as possible. and, after all, if you need to see who has made what code, you are not going to check the name on top of it (because maybe someone has changed it), you just check who commited it (you can use "git blame" command)
• it gets people nervous: if you see a name on the top, you ask yourself: should I be stepping here in someone's toes just to try to fix this bug? . that's bad, its not agile, and a detriment also.
• if everything is anonymous, it encourages people to share.
• and when do you start to put your name on the file? only when I create a new file? is it when I do 2 lines changes, or 4 line changes? can or should I put it if I reformat the code but I don't add more features? or if do I add comments? this is loss of focus, time, and energy.
• and also (as they say in the video and I have seen it in real life): blackmail. when people put their names in the file they tend to think they own the code. they start saying things like: I'm the contributor for that module, if you want to make this interface, you need to make it look like bla bla bla (even if it is worse that way). in that moment, you're losing again the team's point of view, and getting a worse made project in general.

well, that's all :D

you get the same functionality with seeing who commited what, and not all that poison.