Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .gitvote.yml
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ profiles:
# days | day | d
# weeks | week | w
#
duration: 4w
duration: 2w

# Pass threshold (required)
#
Expand Down Expand Up @@ -181,7 +181,7 @@ profiles:
# default values when they are not provided on other profiles.
#
governance:
duration: 4w
duration: 2w
pass_threshold: 66
close_on_passing: true
announcements:
Expand Down
24 changes: 24 additions & 0 deletions CODEOWNERS
Original file line number Diff line number Diff line change
@@ -1 +1,25 @@
# CloudNativePG governance repository CODEOWNERS.
#
# See GOVERNANCE.md and subprojects/README.md for what these teams are and
# how they roll out.
* @cloudnative-pg/governance-owners @cloudnative-pg/admins

# GOVERNANCE.md, MAINTAINERS.md, and CONTRIBUTOR_LADDER.md are Steering
# Committee-owned documents (see GOVERNANCE.md's Voting section); until the
# Steering Committee and its GitHub team exist, they fall back to the
# default rule above.
/GOVERNANCE.md @cloudnative-pg/governance-owners @cloudnative-pg/admins
/MAINTAINERS.md @cloudnative-pg/governance-owners @cloudnative-pg/admins
/CONTRIBUTOR_LADDER.md @cloudnative-pg/governance-owners @cloudnative-pg/admins

# Each subproject's own component listing is scoped to that subproject's
# maintainer committee team, which now exists on GitHub but still has
# placeholder membership and no granted repo access (see note above), so
# `admins` is listed alongside each as a working fallback. The subprojects
# index itself stays on the `governance-owners` fallback, since it isn't
# owned by any single subproject.
/subprojects/README.md @cloudnative-pg/governance-owners @cloudnative-pg/admins
/subprojects/core.md @cloudnative-pg/core-maintainers @cloudnative-pg/admins
/subprojects/supply-chain.md @cloudnative-pg/supply-chain-maintainers @cloudnative-pg/admins
/subprojects/community-ecosystem.md @cloudnative-pg/community-ecosystem-maintainers @cloudnative-pg/admins
/subprojects/extensibility.md @cloudnative-pg/extensibility-maintainers @cloudnative-pg/admins
173 changes: 0 additions & 173 deletions COMPONENT-OWNERS.md

This file was deleted.

40 changes: 20 additions & 20 deletions CONTRIBUTORS.md
Original file line number Diff line number Diff line change
@@ -1,32 +1,32 @@
# CloudNativePG Contributors

This document identifies the individuals who have been formally recognized as
**Contributors** or **Component Owners** to the CloudNativePG project, as
defined in [GOVERNANCE.md](GOVERNANCE.md).
This document lists individuals holding the **Contributor** tier specifically,
the entry rung of the ladder in [CONTRIBUTOR_LADDER.md](CONTRIBUTOR_LADDER.md),
with no repository-scoped access yet. It is not a roster of everyone active in
the project: Component Owners are listed by repository in the
[subprojects/](subprojects/README.md) folder, and Subproject Maintainers and
Steering Committee members in [MAINTAINERS.md](MAINTAINERS.md), rather than
repeated here. A Contributor who is later promoted to Component Owner moves
to that listing and is removed from this one. A Contributor may also be
tagged in a repository's `CODEOWNERS` file for review-routing without
leaving this list: that's an operational choice by the repository's
Component Owners, not a promotion (see
[CONTRIBUTOR_LADDER.md's Component Owner section](CONTRIBUTOR_LADDER.md#component-owner)).

Contributors and Component Owners are listed in alphabetical order by last
name.
The project is grateful for their ongoing dedication to the community,
documentation, and technical excellence.
Contributors are listed in alphabetical order by last name. The project is
grateful for their ongoing dedication to the community, documentation, and
technical excellence.

| Name | GitHub Handle | Country |
| :--- | :--- | :--- |
| Yash Agarwal | [@XploY04](https://github.com/XploY04) | India |
| Jonathan Battiato | [@jbattiato](https://github.com/jbattiato) | Italy |
| Floor Drees | [@FloorD](https://github.com/FloorD) | Netherlands |
| Niccolò Fei | [@NiccoloFei](https://github.com/NiccoloFei) | Italy |
| Itay Grudev | [@itay-grudev](https://github.com/itay-grudev) | Bulgaria |
| Tao Li | [@litaocdl](https://github.com/litaocdl) | China |
| Gabriele Quaresima | [@gabriele-wolfox](https://github.com/gabriele-wolfox) | Italy |
| Anushka Saxena | [@SaxenaAnushka102](https://github.com/SaxenaAnushka102) | India |
| Jaime Silvela | [@jsilvela](https://github.com/jsilvela) | Spain |
| Yoshiyuki Tabata | [@y-tabata](https://github.com/y-tabata) | Japan |

---

## How to become a Contributor

Formal Contributor status is awarded through a nomination by an existing
Maintainer and a simple majority vote.
For more information on the requirements and the nomination process, please
refer to the **Project Roles** section in our [Governance document](GOVERNANCE.md).
Formal Contributor status is awarded through a nomination by, and a simple
majority vote of, the relevant repository's existing Component Owners. For
the full requirements and process, see the
[Contributor section](CONTRIBUTOR_LADDER.md#contributor) of
[CONTRIBUTOR_LADDER.md](CONTRIBUTOR_LADDER.md).
Loading