-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 #1105
Update authors #1105
Conversation
I'm feeling some pull to do a next step on this. So, no super rush, but might end up merging in a day or two just the same. |
.github/PULL_REQUEST_TEMPLATE.md
Outdated
@@ -18,6 +20,8 @@ | |||
|
|||
<!-- | |||
|
|||
I no issue exists that you're aware of. The maintainers should be able to figure out if it's a duplicate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I no issue
should be If no issue
I think.
AUTHORS.md
Outdated
@@ -50,18 +53,80 @@ To be listed: Admins are usually selected from the pool of committers who demons | |||
|
|||
To be removed: You can remove yourself through the [GitHub UI](https://help.github.com/articles/removing-yourself-from-a-collaborator-s-repository/). | |||
|
|||
[Details on badges](#badges) | |||
|
|||
## Publishers | |||
|
|||
Publishers are admins who also have the responsibility, privilege, and burden of publishing the new releases to NPMJS and performing outreach and external stakeholder communications. Further, when things go pear-shaped, they're the ones taking most of the heat. Finally, when things go well, they're the primary ones praising the contributors who made it possible. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NPMJS
should be just npm
AUTHORS.md
Outdated
<dd> | ||
<p>Someone who understands and contributes to improving the developer experience and flow of Marked into the world.</p> | ||
<blockquote> | ||
"The main characteristic of the DevOps movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management. DevOps aims at shorter development cycles, increased deployment frequency, more dependable releases, in close alignment with business objectives." ~[Wikipedia](https://en.wikipedia.org/wiki/DevOps) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link isn't working, Maybe try a space after the ~
.
Merging to begin working on the next collaboration game. |
Update authors
Marked version: 0.3.17
Description
We haven't addressed a formal governance pattern yet, having said that, since inception, Marked has been operating under something that looks like the benevolent dictator for life model, which can work pretty well when the dictator is active and available (product owners, so to speak, must be responsive).
The project seems to have tried to move, not explicitly, toward liberal and consensus-based models. Which can also work, when all the committers are active and responsive in the reviews. (However, getting 100% consensus can cause so much pain and delay over a single word on a page...I've literally been in a meeting where we had a 45 minute debate over whether to use a word and comma in a four page document...in order to gain 100% consensus.)
Think by adding game dynamics to the AUTHORS and badges we can cover a lot of ground. Meritocracy - community driven. Those who contribute more should end up being the ones who end up with authority. And so on.
If you have questions or comments about the game dynamics or maybe something you think isn't covered, say the word. Otherwise, it's easy to change in future, but I think this covers a lot of ground.
Contributor
Committer
In most cases, this should be a different person than the contributor.