-
Notifications
You must be signed in to change notification settings - Fork 106
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 list of Editors/Authors for spec. #675
Comments
I did a lot of the early architecture, initially as part of the Oasis XDI on blockchain project with Drummond, later at early #RWOT meetings, and in the google doc. I hope to continue to be considered one of the authors. |
"Author" has a very specific meaning in W3C land and the bar to be listed there is quite high. It is typically that you contributed a large chunk of substantive text or design to this specification. You will definitely be listed in the Acknowledgements section, and we could mention RWoT, IIW, and other organizations as being vital to the development of the work. Would that work for you? |
Yes, for the VC-data-model the acknowledgement and mentions of organizations driving it is acceptable. There will be a similar problem with DID as some of the work was done pre-W3C, but in that case I definitely qualify as "Author". |
Ok, I'll prep a PR so you and others requesting to be listed in different areas have a chance to review before we go into the Proposed Recommendation stage.
Yes, and you're listed as such (Author) on that specific document. |
I ran a few tools to determine who has contributed to the specification and in what ways. We need to be careful with these numbers because they don't tell the entire story. For example, there is a ton of work that goes into initial design, offline discussions, implementations, etc. It's also dangerous to count quantity over quality. So, take these numbers with a grain of salt.
The first statistic is lines of code, commits, and file changes. I used a tool called git-fame to do the calculation. The sorting matches GitHubs algorithm pretty closely. The sorted order is below for the top contributors:
I also wrote a tool to pull every single comment from the specification repository and tally the results. The score is the number of comments, plus the number of bytes written divided by 1024. Yes, that's arbitrary, but the arbitrary rule seemed somewhat fair in calculating a final score as it was applied equally across every contributor. Again, the top rankings are shown below:
My suggestion is that we use these numbers to guide who is listed as an Editor and as an Author. Anyone remaining will be specifically called out and thanked above and beyond the typical "Acknowledgements" section.
The text was updated successfully, but these errors were encountered: