Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update AUTHORS list to reflect new contributions. #11533

Closed
wants to merge 4 commits into from

Conversation

aashil
Copy link
Contributor

@aashil aashil commented Feb 24, 2017

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

Update the AUTHORS list.
Fixes #11526
Fixes #6403

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Feb 24, 2017
@Trott
Copy link
Member

Trott commented Feb 24, 2017

It seems like this adds many duplicate entries (I immediately noticed Ron Korving, Anna Henningsen, Michaël Zasso, and there are probably others...)

EDIT: Imran Iqbal, Minqi Pan/P.S.V.R., ChALkeR and no doubt many more duplicates....

Trott
Trott previously requested changes Feb 24, 2017
Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many duplicates....

@mscdex mscdex added the doc Issues and PRs related to the documentations. label Feb 24, 2017
@targos
Copy link
Member

targos commented Feb 24, 2017

See #9352 for some duplicate resolutions.

@jasnell
Copy link
Member

jasnell commented Feb 24, 2017

Many of the changes to the existing names should also be reverted. The update should only include the newly added entries that are not duplicates.

Copy link
Contributor

@silverwind silverwind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use .mailmap to reduce duplicates and ask users with bogus names/adresses how they want to be represented.

@aashil
Copy link
Contributor Author

aashil commented Feb 25, 2017

@jasnell Thanks. Will do it asap.

@jasnell
Copy link
Member

jasnell commented Feb 25, 2017

Thank you @aashil. It is quite helpful for you to do this and very much appreciated.

@aashil
Copy link
Contributor Author

aashil commented Feb 25, 2017

@jasnell No problem. Should I consider email changes for existing authors? For example, Ron Korving <rkorving@wizcorp.jp> to Ron Korving <ron@ronkorving.nl>

@jasnell
Copy link
Member

jasnell commented Feb 25, 2017

For those, it's best to at-mention the person in question and ask what they would prefer.

@aashil
Copy link
Contributor Author

aashil commented Feb 25, 2017

The below users might want to use a different name or email. Also, check if you have a duplicate entry with a different name or email in the list. Please let me know and I will update the .mailmap

@ChALkeR
@Alexis374
@atstojanov
@lrlna
@matt-in-a-hat
@delvedor
@oogz
@mpmckenna8
@nohmapp
@ss22ever
@larissayvette
@solebox
@marzelin
@maasencioh
@anu0012
@jseagull
@kobelb
@coderaiser
@jedireza
@timathon
@zzzzBov
@ikasumiwt
@atrioom
@mkamakura
@brad-decker
@makenova
@scalkpdev
@shiya
@stokingerl
@rajatkumar
@bjdelro
@davidmarkclements
@anoff
@k3kathy
@michael6
@CodeTheInternet
@sxa555
@fmizzell
@cdnadmin
@blugavere
@hirabhullar
@codeVana
@eudaimos
@pallxk
@mfhan
@weyj4
@misterpoe
@sivaprs
@malenesok007
@sarahmeyer

@aashil
Copy link
Contributor Author

aashil commented Feb 25, 2017

I guess there is a limit to tag people. Please look at the above comment.

@jBarz
@vitkarpov
@istinson
@richnologies
@legalcodes
@nanxiongchao
@toboid
@jobala
@asafdav2

AUTHORS Outdated
Oscar Morrison <me@oscarmorrison.com>
Jaideep Bajwa <bjaideep@ca.ibm.com>
timathon <timathon@outlook.com>
Timothy <zzzzBov@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Timothy Leverett <zzzzBov@gmail.com>

Thanks

AUTHORS Outdated
kobelb <brandon.kobel@elastic.co>
coderaiser <mnemonic.enemy@gmail.com>
Pedro Victor <pvsousalima@gmail.com>
jedireza <reza@akhavan.me>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reza Akhavan reza@akhavan.me

AUTHORS Outdated
Yann Pringault <yann@cinq-s.com>
Evan Torrie <evant@yahoo-inc.com>
Michael Lefkowitz <lefkowitz.michael@gmail.com>
vitkarpov <viktor.s.karpov@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AUTHORS Outdated
toboid <toboid@users.noreply.github.com>
Shubheksha Jalan <jshubheksha@gmail.com>
jobala <japheth.obala@andela.com>
asafdav2 <asafdav2@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Asaf David asafdav2@gmail.com

AUTHORS Outdated
Daiki Arai <darai0512@yahoo.co.jp>
ALJCepeda <AlfredJCepeda@gmail.com>
Sebastian Roeder <afk@Sebastians-iMac.local>
toboid <toboid@users.noreply.github.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Toby Stableford tobytronics@gmail.com

AUTHORS Outdated
Michael Macherey <macherey@gmx.net>
Sudaraka Wijesinghe <sudaraka@sudaraka.org>
Miguel Angel Asencio Hurtado <maasencioh@gmail.com>
ss22ever <ss22ever@users.noreply.github.com>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AUTHORS Outdated
sarahmeyer <sarahsaltrick@gmail.com>
Fumiya KARASAWA <krswfmy@gmail.com>
Jesús Leganés-Combarro 'piranna <piranna@gmail.com>
jBarz <jBarz@users.noreply.github.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

John Barboza jbarboza@ca.ibm.com

AUTHORS Outdated
Jay Brownlee <jay.brownlee@help.com>
Outsider <outsideris@gmail.com>
Sarah Meyer <sarahsaltrick@gmail.com>
anoff <offenhaeuser@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Andreas Offenhaeuser <offenhaeuser@gmail.com>

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ben Lugavere b.lugavere@gmail.com

AUTHORS Outdated
Aaron Bieber <aaron@bolddaemon.com>
Gerges Beshay <gerges@beshay.xyz>
Isobel Redelmeier <iredelmeier@gmail.com>
kobelb <brandon.kobel@elastic.co>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brandon Kobel kobelb@gmail.com

AUTHORS Outdated
Yosuke Saito <yosuke.saito1202@gmail.com>
mkamakura <kamakura.masaya@gmail.com>
kalrover <kal@zigexn.co.jp>
brad-decker <bhdecker84@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Brad Decker bhdecker84@gmail.com

AUTHORS Outdated
solebox <solekiller@gmail.com>
John Vilk <jvilk@cs.umass.edu>
Tyler Brazier <tyler@tylerbrazier.com>
marzelin <marzelin@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Marcin Zielinski marzelin@gmail.com

@ChALkeR
Copy link
Member

ChALkeR commented Feb 27, 2017

The below users might want to use a different name or email. Also, check if you have a duplicate entry with a different name or email in the list. Please let me know and I will update the .mailmap

My entry in the AUTHORS file seems correct. 😆

AUTHORS Outdated
Sarah Meyer <sarahsaltrick@gmail.com>
anoff <offenhaeuser@gmail.com>
Sean Villars <stvillars8@gmail.com>
k3kathy <kathy.yvy.truong@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AUTHORS Outdated
Vinícius do Carmo <vinicius.m.do.carmo@gmail.com>
Birunthan Mohanathas <birunthan@mohanathas.com>
John Barboza <jbarboza@ca.ibm.com>
richnologies <me@richnologies.io>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ricardo Sánchez Gregorio me@richnologies.io

Thanks

@legalcodes
Copy link
Contributor

Jon Tippens

jwtippens@gmail.com

Thanks

AUTHORS Outdated
Dan Fabulich <dan.fabulich@redfin.com>
Mike Ralphson <mike.ralphson@gmail.com>
Alexis374 <879736822@qq.com>
atstojanov <atstojanov@gmail.com>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Angel Stoyanov atstojanov@gmail.com

@aashil
Copy link
Contributor Author

aashil commented Apr 17, 2017

@fhinkel On taking a close look at the script, I found that it is designed to exclude all users with @chromium.org email address. @Trott @jasnell @ChALkeR Is there a reason for this?

https://github.com/nodejs/node/blob/master/tools/update-authors.sh#L11

PS. Who is erik.corry@gmail.com and why is he excluded? Just curious.

@jasnell
Copy link
Member

jasnell commented Apr 18, 2017

Ping @rvagg ... he may have the context for the @chromium.org exclusion.

@fhinkel
Copy link
Member

fhinkel commented Apr 18, 2017

I'm assuming we didn't want to count V8 commits (looks like they were imported differently at some point?), AFAIK Erik was on the V8 team. I can change my email address. Sorry for causing confusion by reviewing and committing with different addresses.

@fhinkel
Copy link
Member

fhinkel commented Apr 18, 2017

I think @eugeneo and @hashseed use a chromium account, too.

@gibfahn
Copy link
Member

gibfahn commented Apr 18, 2017

Sorry for causing confusion by reviewing and committing with different addresses.

@fhinkel looking at the .mailmap I think that's pretty common 😄

@aashil
Copy link
Contributor Author

aashil commented Apr 24, 2017

@Trott @jasnell @ChALkeR All the authors have been included without duplicates. Please approve and merge this PR.

Vincent Voyer <v@fasterize.com>
Vladimir de Turckheim <vlad2t@hotmail.com>
vsemozhetbyt <vsemozhetbyt@gmail.com> Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using Vse's real name would probably be preferred.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or maybe not the real name 😉, but at least spelled out is better than a network handle

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if I should change that. The original author list had it this way. cc @vsemozhetbyt

Copy link
Contributor

@vsemozhetbyt vsemozhetbyt Apr 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not a real name, it's a nickname, something like 'anything is possible', 'anything can happen', 'you never know', 'you never can tell' in Russian :) I am OK with either variant, but 'Vse' would be a bit arrogant of me :) — it is actually 'everything, all, everybody' in Russian ) Sorry for the mess) I think it is OK as it is)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[off topic] what is .mailmap used for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sometimes people use different name and/or email address in their commits. Mailmap is a way to keep track of that person's preferred username and email address and all the other usernames and email addresses used.

https://git-scm.com/docs/git-shortlog#_mapping_authors

@Trott Trott dismissed their stale review April 25, 2017 03:05

Wow! Thanks for sticking with this! (Was this a NodeTodo thing? I can't remember that far back! :-D)

@aashil
Copy link
Contributor Author

aashil commented Apr 25, 2017

@Trott No problem! This was actually the first issue/work I found myself after the NodeTodo thing. Looking forward to major contributions in the future. Thanks for all the help.

@jasnell
Copy link
Member

jasnell commented Apr 25, 2017

I'll get this landed

jasnell pushed a commit that referenced this pull request Apr 25, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@jasnell
Copy link
Member

jasnell commented Apr 25, 2017

Landed in 9d3c06c

@jasnell jasnell closed this Apr 25, 2017
@aashil
Copy link
Contributor Author

aashil commented Apr 25, 2017

@jasnell Just wanted to understand what you did for merging. Did you squashed all my commits and then cherry-picked to origin/master?

@jasnell
Copy link
Member

jasnell commented Apr 25, 2017

The workflow is fairly straightforward... I use git am to apply the PR to master, the git rebase -i to squash and edit the commit message so that it includes the appropriate metadata. After that I do a quick make lint followed by git push origin master.

evanlucas pushed a commit that referenced this pull request Apr 25, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@TimothyGu
Copy link
Member

@aashil, we have a nice step-by-step patch application process documented in COLLABORATOR_GUIDE.md.

@evanlucas evanlucas mentioned this pull request May 1, 2017
evanlucas pushed a commit that referenced this pull request May 1, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@aashil aashil deleted the update-authors branch May 1, 2017 19:40
evanlucas pushed a commit that referenced this pull request May 2, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
gibfahn pushed a commit that referenced this pull request May 16, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
MylesBorins pushed a commit that referenced this pull request May 18, 2017
PR-URL: #11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
@MylesBorins MylesBorins mentioned this pull request May 23, 2017
andrew749 pushed a commit to michielbaird/node that referenced this pull request Jul 19, 2017
PR-URL: nodejs/node#11533
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update the authors list Remove duplicate entries from the AUTHORS file