Maybe an easy way to come out of this endless discussion is the following solution:
- Ask the rockbox founders to change the policy to "We only give cvs write access to people with real names, and an e-mail address we can verify." - And: "Everybody is responsible for what he or she commits to CVS." - Plus: "Only real names get into to CONTRIBUTORS file." Then they can refuse to commit anything from someone anonymous. But people like gl and John can ask someone else to take responsibility for their code, and commit it. They would not get credited on their nickname, but as far as I can tell from this discussion, that's not their main concern? I think there are enough people who are more liberal in these matters with cvs write access, so these people can just read a patch, and decide that they will take responsibility for it. I would for example have no problem at all with checking a wps viewport patch, and committing that on my own name. Tomas Salfischberger Kjell Ericson wrote: > On Fri, 10 Mar 2006, Paul Louden wrote: > > Very wise word written! > >> So, my perspective is that they should be allowed the identify of their >> choice as long as the chosen name is not in some way intentionally >> (or even >> hopefully accidentally) offensive to others, and that they're willing to >> stand behind that identity. > > > In this project I get offended by names like "eLiTEhAcker", and > "gl.tter". > > I don't get offended by names I can't separate from real names, like > for example "John Glitter". > > In other projects I may have different opinion. > > If 95% uses their real names (the poll right now) and some of the 5% > uses a fake real name, then the pseudo-wanted names will have to > understand the "culture" (even if it isn't written). > > Discussing with an anonymous person is also uncomfortable. I've > experienced where anonymous person really goes crazy after a while and > tries to destroy works for other. They feel they can do that because > no one knows who they are. That experience make me support the > real-name-policy. > > // Kjell Ericson
