Introduce governance documentation #1118
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This contains almost everything for project leadership. We still need an explanation of the contributor role and a breakdown of the various project administration pieces.
I wish there was more we could do to automatically highlight the many contributors we've had. We may want to consider ways to do this in the future.
We're using the governance model, but I like "project lead" as a better term.
LoreleiAurora
approved these changes
Mar 6, 2017
tomjn
reviewed
Mar 7, 2017
docs/en-US/governance.md
Outdated
| @@ -0,0 +1,80 @@ | |||
| # Varying Vagrant Vagrants Governance | |||
There was a problem hiding this comment.
The Varying Vagrant Vagrants in the title is redundant
tomjn
reviewed
Mar 7, 2017
docs/en-US/governance.md
Outdated
|
|
||
| In general, this means that VVV is maintained by a community of active contributors. Most decisions are made in this context and contributions are always welcome. The project lead performs a role of project leadership and architectural oversight. | ||
|
|
||
| VVV is copyright (c) 2014-2017 the contributors of the VVV project under the [MIT License](https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/LICENSE). A [guide to contributing](https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/.github/CONTRIBUTING.md) is also available. |
There was a problem hiding this comment.
We shouldn't let copyright expire in 2017, we may want to continue the project in 2018
There was a problem hiding this comment.
That's true - I'll remove the dates so that we don't have to worry about it in this doc.
tomjn
reviewed
Mar 7, 2017
docs/en-US/governance.md
Outdated
|
|
||
| Current project lead: | ||
|
|
||
| * [Jeremy Felt](https://jeremyfelt.com/) |
There was a problem hiding this comment.
It might be better to link to GitHub profiles, with personal sites being a second link, e.g.
There was a problem hiding this comment.
Good point, that's more consistent.
|
I left a comment or two, but I agree with the content |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From http://oss-watch.ac.uk/resources/governancemodels:
A governance model is a healthy thing for any open source project to have. For VVV, I'd like this to be a "living reflection of the group's intentions".
This first draft is my attempt to describe the structure of the project from my perspective. Please feel free to suggest any changes or request clarifications.
I also wrote up the process of creating this document to provide some more context.
Let's leave this open for a few days for visibility and comment. 🏖