-
Notifications
You must be signed in to change notification settings - Fork 167
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
Review acknowledgments and editors list #706
Comments
+1 to alphabetize the editors. I also would propose we move some of the editors who've not been involved recently to 'former editors'. |
@levangongPayPal has already told me he's fine with being listed as "contributor". |
We should add Akshay as a current editor. |
@selfissued @jcjones @equalsJeffH I will make a call for additional editors on next weeks call so we are all in agreement |
Summary: In case it is helpful, I've extracted the names/userids of all webauthn committers from the webauthn git repo. Here is the list along with a commit count for each (note: some commits by various folks were to various ancilliary items in the repo, such as README.md, the travis & bikeshed stuff, etc):
Note: there's also the github webauthn repo "contributors" page: https://github.com/w3c/webauthn/graphs/contributors tl;dr: I did an initial extraction from the git hist output of any line containing a substring matching "[.*]" using: ..which output all committer names/userids plus various spurious noise since some commit comments have text containing square brackets. I extracted the committer names/userids from that output by hand, and created the
|
In terms of acknowledging folks who've provided feedback on the spec and/or submitted issues, I wonder if there is a means to do something similar to the committer info extraction in #706 (comment), and generate a list of names/userids that have submitted issues? |
Let's review the acknowledgments to get them in shape for CR.
Shall we alphabetize the list of editors?
The text was updated successfully, but these errors were encountered: