> There have been multiple incidents where someone has gotten very angry about being
> “doxed” when their real name has ended up in the whatsnew file, even when it was
> scraped from the “name” field on their own commits. After a couple of those
> incidents, I’ve become reluctant to use people’s real names if they’ve been credited
> under an alias in the past or if their GitHub username or profile display name aren’t
> their real name (or some kind of abbreviation of it). I figure it’s better safe than
> sorry.
I understand, but when I was asked what name I wanted to be credited as, I chose that one on purpose. I use it on Twitter, it's on the bottom of my website, and it's on my MobyGames dev profile. I am 100% fine with being credited with my name.
> I can’t change whatsnew for 0.222 now because if I did it would no longer match the
> SHA1SUMS/SHA256SUMS. But going forward I can use your real name.
If I understand this correctly, you mean that the name won't be changed in the 0.222 readme - but any future contributions I make (if any) will be credited as I requested? That's okay, I understand how MAME readme files work so it's allright.
I dunno if my name is present in the source code, though (I've checked it a few times over the years and have noticed driver history info with names) so if it is, I would appreciate it if you could change the name there. If it's not, no biggie.
|
Index 
Flat 
Re: MAME 0.222
Reply
