You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -448,6 +448,49 @@ Please see our [Security Policy](SECURITY.md) for responsible disclosure procedu
448
448
-**Issues**: GitHub Issues for bug reports and feature requests
449
449
-**Discussions**: Community discussions and questions
450
450
451
+
## Governance
452
+
453
+
### Roles
454
+
455
+
The project community consists of Contributors and Maintainers:
456
+
* A **Contributor** is anyone who submits a contribution to the project. (Contributions may include code, issues, comments, documentation, media, or any combination of the above.)
457
+
* A **Maintainer** is a Contributor who, by virtue of their contribution history, has been given write access to project repositories and may merge approved contributions.
458
+
* The **Lead Maintainer** is the project's interface with the FINOS team and Board. They are responsible for approving [quarterly project reports](https://community.finos.org/docs/governance/#project-governing-board-reporting) and communicating on behalf of the project. The Lead Maintainer is elected by a vote of the Maintainers.
459
+
460
+
### Contribution Rules
461
+
462
+
Anyone is welcome to submit a contribution to the project. The rules below apply to all contributions. (The key words "MUST", "SHALL", "SHOULD", "MAY", etc. in this document are to be interpreted as described in [IETF RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).)
463
+
464
+
* All contributions MUST be submitted as pull requests, including contributions by Maintainers.
465
+
* All pull requests SHOULD be reviewed by a Maintainer (other than the Contributor) before being merged.
466
+
* Pull requests for non-trivial contributions SHOULD remain open for a review period sufficient to give all Maintainers a sufficient opportunity to review and comment on them.
467
+
* After the review period, if no Maintainer has an objection to the pull request, any Maintainer MAY merge it.
468
+
* If any Maintainer objects to a pull request, the Maintainers SHOULD try to come to consensus through discussion. If not consensus can be reached, any Maintainer MAY call for a vote on the contribution.
469
+
470
+
### Maintainer Voting
471
+
472
+
The Maintainers MAY hold votes only when they are unable to reach consensus on an issue. Any Maintainer MAY call a vote on a contested issue, after which Maintainers SHALL have 36 hours to register their votes. Votes SHALL take the form of "+1" (agree), "-1" (disagree), "+0" (abstain). Issues SHALL be decided by the majority of votes cast. If there is only one Maintainer, they SHALL decide any issue otherwise requiring a Maintainer vote. If a vote is tied, the Lead Maintainer MAY cast an additional tie-breaker vote.
473
+
474
+
The Maintainers SHALL decide the following matters by consensus or, if necessary, a vote:
475
+
* Contested pull requests
476
+
* Election and removal of the Lead Maintainer
477
+
* Election and removal of Maintainers
478
+
479
+
All Maintainer votes MUST be carried out transparently, with all discussion and voting occurring in public, either:
480
+
* in comments associated with the relevant issue or pull request, if applicable;
481
+
* on the project mailing list or other official public communication channel; or
482
+
* during a regular, minuted project meeting.
483
+
484
+
### Maintainer Qualifications
485
+
486
+
Any Contributor who has made a substantial contribution to the project MAY apply (or be nominated) to become a Maintainer. The existing Maintainers SHALL decide whether to approve the nomination according to the Maintainer Voting process above.
487
+
488
+
### Changes to this Document
489
+
490
+
This document MAY be amended by a vote of the Maintainers according to the Maintainer Voting process above.
491
+
492
+
The current list of maintainers is in [MAINTAINERS.md](MAINTAINERS.md).
493
+
451
494
## Code of Conduct
452
495
453
496
This project follows the [AWS Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
This file lists the maintainers of this repository.
4
+
5
+
## Current maintainers
6
+
7
+
| GitHub Username | Name | Organization | Email |
8
+
|----------------|------|--------------|-------|
9
+
|@fgogolli| Flamur Gogolli | Amazon Web Services (AWS) |flamurg@amazon.co.uk|
10
+
|@kirillsc| Kirill Bogdanov | Amazon Web Services (AWS) |kirillb@amazon.ch|
11
+
|@cyriaquem| Cyriaque Millot | Morgan Stanley |cyriaque.millot@morganstanley.com|
12
+
13
+
For information about maintainer responsibilities and resources, see the [FINOS Maintainers Cheatsheet](https://community.finos.org/docs/finos-maintainers-cheatsheet).
14
+
15
+
## Updating this file
16
+
17
+
All changes to the maintainer list are managed openly:
18
+
19
+
-**Submit a Pull Request** to this file for any addition, removal, or update.
20
+
-**If your project's governance requires a vote**, document or link to the vote outcome in the PR description or comments.
21
+
- This process creates a public audit trail of project leadership over time.
22
+
23
+
Please email **help@finos.org** whenever this file is updated with a change to maintainership.
0 commit comments