-
Notifications
You must be signed in to change notification settings - Fork 848
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
Introduce governance documentation #1118
Changes from 8 commits
90bf0bd
0de1076
5c6ca8d
67380b3
541aa3d
2165f18
77c4da3
803946d
e11674d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,80 @@ | ||
# Varying Vagrant Vagrants Governance | ||
|
||
## Overview | ||
|
||
The [VVV core project](https://github.com/Varying-Vagrant-Vagrants/VVV/) and its individual modules, collectively organized as [Varying Vagrant Vagrants](https://github.com/Varying-Vagrant-Vagrants/) (VVV), are governed with a [benevolent dictator governance model](http://producingoss.com/en/benevolent-dictator.html). | ||
|
||
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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We shouldn't let copyright expire in 2017, we may want to continue the project in 2018 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's true - I'll remove the dates so that we don't have to worry about it in this doc. |
||
|
||
## Roles and Responsibilities | ||
|
||
### Project Lead | ||
|
||
The project lead is trusted to set an overall strategic direction and, as necessary, to provide a final say in any arguments or disputes. They have full access to repositories, servers, and other services associated with project management. With the input of lead developers, they coordinate project maintenance and assign roles within the community. | ||
|
||
Current project lead: | ||
|
||
* [Jeremy Felt](https://jeremyfelt.com/) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point, that's more consistent. |
||
|
||
The current project lead assumed the role as founder of the project. When they transition out of the project lead role, a steering committee will be formed of trusted stakeholders and community members. This committee will select a new project lead or leads. When this committee is formed, 10up will be offered at least one seat on that group. | ||
|
||
### Lead Developers | ||
|
||
Lead developers are trusted to make changes to all project code by merging their own pull requests and the pull requests of contributors. They have full access to all project repositories. They have the authority and ability to close issues and pull requests. As necessary, they will help in providing guidance to new contributors and committers. | ||
|
||
Current lead developers: | ||
|
||
* [Lorelei Aurora](https://github.com/lorelieaurora) | ||
|
||
Lead developers are selected by the project lead. | ||
|
||
### Committers | ||
|
||
Committers are trusted to make changes to project code by merging the pull requests of contributors. They have push access to one or more project repositories. They have the authority and ability to close issues and pull requests. Pull requests submitted by committers should be reviewed by another committer before merge. As necessary, they will help in providing guidance to new contributors. | ||
|
||
Current committers: | ||
|
||
* [Weston Ruter](https://github.com/westonruter) | ||
* [Simon Wheatley](https://github.com/simonwheatley) | ||
* [Luke Woodward](https://github.com/lkwdwrd) | ||
* [Christian Foellman](https://github.com/cfoellmann) | ||
|
||
Contributors who [show good judgement](http://producingoss.com/en/committers.html#choosing-committers) may be selected as committers for one or more project repositories. The decision to promote a contributor to a committer will be made by consensus between the project lead and lead developers. This decision should be based on meritocratic criteria including, but not limited to, consistent and quality pull requests, bug gardening, support answers, and general community participation. | ||
|
||
### Contributors | ||
|
||
Contributors are vital to the success of open source software. VVV is fortunate to have a large community of contributors that have provided support in one way or another over the last several years. Please see the [contributing guide](https://github.com/Varying-Vagrant-Vagrants/VVV/blob/develop/.github/CONTRIBUTING.md) for information on how you can become a contributor. | ||
|
||
A list of [people who have contributed code to VVV](https://github.com/Varying-Vagrant-Vagrants/VVV/graphs/contributors) is maintained by GitHub. | ||
|
||
## Project Founders | ||
|
||
VVV is a [10up](https://10up.com) creation. [Jeremy Felt](https://jeremyfelt.com/) is the founding developer. [VVV transitioned](http://10up.com/blog/varying-vagrant-vagrants-future/) to a community organization in 2014. The [first draft of VVV](https://jeremyfelt.com/2012/12/11/varying-vagrant-vagrants/) was released on December 11, 2012. | ||
|
||
## Project Administration | ||
|
||
### GitHub organization | ||
|
||
The [Varying Vagrant Vagrants GitHub organization](https://github.com/Varying-Vagrant-Vagrants) is owned by Jeremy Felt in that it's his email address that is assigned as the "Billing email". Lorelei Aurora's membership level is also set to "Owner". All lead developers and committers have permissions to create new repositories. The organization is currently configured under the free plan and there are no private repositories. | ||
|
||
### VVV Website | ||
|
||
The VVV website is located at [https://varyingvagrantvagrants.org](https://varyingvagrantvagrants.org). | ||
|
||
#### Domain name | ||
|
||
The `varyingvagrantvagrants.org` and `varyingvagrantvagrants.com` domains are owned by Jeremy Felt. | ||
|
||
#### Server | ||
|
||
The `varyingvagrantvagrants.org` domain is assigned to a virtual machine, hosted with Linode. That server is managed and paid for by Jeremy Felt. | ||
|
||
#### S3 account | ||
|
||
Documentation from VVV's repositories is deployed directly to an S3 bucket. That bucket is managed and paid for by Jeremy Felt. | ||
|
||
#### Google Analytics | ||
|
||
Google Analytics is used to track visitors on the `varyingvagrantvagrants.org` domain. That account is managed by Jeremy Felt. |
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.
The Varying Vagrant Vagrants in the title is redundant