|
2 | 2 |
|
3 | 3 | Welcome, and thank you for your interest in contributing to Vortex! We are delighted to receive all forms of community contributions (issues, pull requests, questions). |
4 | 4 |
|
5 | | -We ask that you read the guidelines below in order to |
6 | | -make the process as streamlined as possible. |
| 5 | +We ask that you read the guidelines below in order to make the process as streamlined as possible. |
7 | 6 |
|
8 | 7 | ## Governance |
9 | 8 |
|
10 | 9 | Vortex is an independent open-source project and not controlled by any single company. The Vortex Project is a sub-project of the Linux Foundation Projects. As such, the governance is subject to the terms of the [Technical Charter](https://vortex.dev/charter.pdf). |
11 | 10 |
|
12 | 11 | ## Project Roles |
| 12 | + |
13 | 13 | * Contributor: anyone who contributes intellectual property to the common endeavor of the project under the project license. |
14 | | -* Committer: a subset of Contributors, who collectively determine the project's technical direction. Committers have permissions to review & merge code contributions. |
15 | | -* Maintainer: a subset of Committers, who are additionally responsible for appointing new Committers. |
| 14 | +* Committer: a subset of Contributors, who collectively determine the project's technical direction. Committers have permissions to review & merge code contributions. Unless they are also Maintainers, Committers are non-voting members of the Technical Steering Committee (TSC). |
| 15 | +* Maintainer: a subset of Committers, who are also *voting* members of the Technical Steering Committee (TSC). In practice, Maintainers' primary responsibility is to manage membership of the Committers/Maintainers group over time and ensure the long-term health of the project. |
| 16 | + |
| 17 | +### Committers |
| 18 | + |
| 19 | +At the time of writing, the following individuals serve as Committers (non-voting TSC members) on the project: |
| 20 | + |
| 21 | +1. Adam Gutglick |
| 22 | +2. Alexander Droste |
| 23 | +3. Andy Pavlo |
| 24 | +4. Connor Tsui |
| 25 | +5. Daniel King |
| 26 | +6. Dmitrii Blaginin |
| 27 | +7. Joseph Isaacs |
| 28 | +8. Marko Bakovic |
| 29 | +9. Onur Satici |
| 30 | +10. Xinyu Zeng |
| 31 | + |
| 32 | +### Maintainers |
| 33 | + |
| 34 | +At the time of writing, the following individuals serve as Committers & Maintainers (voting TSC members) on the project: |
| 35 | + |
| 36 | +1. Andrew Duffy |
| 37 | +2. Carlo Curino |
| 38 | +3. Nicholas Gates |
| 39 | +4. Robert Kruszewski |
| 40 | +5. Wes McKinney |
| 41 | +6. Will Manning (chair) |
16 | 42 |
|
17 | 43 | ## Coding style |
18 | 44 |
|
19 | | -Our CI process enforces an extensive set of linter (e.g., `clippy`) rules, as well as language-specific formatters (e.g., `cargo fmt`). Beyond that, |
20 | | -we document additional style guidelines in [STYLE.md](STYLE.md). |
| 45 | +Our CI process enforces an extensive set of linter (e.g., `clippy`) rules, as well as language-specific formatters (e.g., `cargo fmt`). Beyond that, we document additional style guidelines in [STYLE.md](STYLE.md). |
21 | 46 |
|
22 | 47 | ## Reporting Issues |
23 | 48 |
|
|
0 commit comments