Skip to content
Merged
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
90 changes: 90 additions & 0 deletions GOVERNANCE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
# Project Governance

This document defines governance policies for the the projects under the Devfile organization.

- [Maintainers](#maintainers)
- [Becoming a Maintainer](#becoming-a-maintainer)
- [Meetings](#meetings)
- [CNCF Resources](#cncf-resources)
- [Code of Conduct Enforcement](#code-of-conduct)
- [Voting](#voting)

## Maintainers

Devfile Maintainers have write access to the [Devile GitHub organization repositories](https://github.com/devfile).
They can merge their own patches or patches from others. The current maintainers
can be found in [MAINTAINERS](./MAINTAINERS). Maintainers collectively manage the project's
resources and contributors.

This privilege is granted with some expectation of responsibility: maintainers
are people who care about the Devfile project and want to help it grow and
improve. A maintainer is not just someone who can make changes, but someone who
has demonstrated their ability to collaborate with the team, get the most
knowledgeable people to review code and docs, contribute high-quality code, and
follow through to fix issues (in code or tests).

A maintainer is a contributor to the project's success and a citizen helping
the project succeed.

## Becoming a Maintainer

To become a Maintainer you need to demonstrate the following:

* commitment to the project:
* participate in discussions, contributions, code and documentation reviews
for 3 months or more,
* perform reviews for 5 non-trivial pull requests,
* contribute 5 non-trivial pull requests and have them merged,
* ability to write quality code and/or documentation,
* ability to collaborate with the team,
* understanding of how the team works (policies, processes for testing and code review, etc),
* understanding of the project's code base and coding and documentation style.

A new Maintainer must be proposed by an existing maintainer by submitting a new post to the
[Devfile API discussion board](https://github.com/devfile/api/discussions). A simple majority vote of existing Maintainers
approves the application.

Maintainers who are selected will be granted the necessary GitHub rights,
and invited to the [private maintainer mailing list](https://lists.cncf.io/g/cncf-devfile-maintainers).

## Meetings

Time zones permitting, Maintainers are expected to participate in the public
developer meeting, which occurs

Every Tuesday at 9am EST ([video call link](https://meet.google.com/trx-vqbw-ekb))
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, these calls are cancelled once every three weeks due to conflicts in the current attendee's schedules. Should we note this or move the meeting to a more stable time?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a good point. In general I would like to have a confirmation from non Red Hat maintainers that current call schedule is ok for them and they do not have recurrent conflicts. Then, if we keep current schedule, we need to decide if we should make the every 3 weeks "pause" official and update the calendar invites. Sending an email to the new maintainers mailing list to discuss that.


Maintainers will also have closed meetings in order to discuss security reports
or Code of Conduct violations. Such meetings should be scheduled by any
Maintainer on receipt of a security issue or CoC report. All current Maintainers
must be invited to such closed meetings, except for any Maintainer who is
accused of a CoC violation.

## CNCF Resources

Any Maintainer may suggest a request for CNCF resources, either in the
[mailing list](TODO: link to developer/maintainer mailing list), or during a
meeting. A simple majority of Maintainers approves the request. The Maintainers
may also choose to delegate working with the CNCF to non-Maintainer community
members.

## Code of Conduct

[Code of Conduct](./code-of-conduct.md)
violations by community members will be discussed and resolved
on the [private Maintainer mailing list](https://lists.cncf.io/g/cncf-devfile-maintainers). If the reported CoC violator
is a Maintainer, the Maintainers will instead designate two Maintainers to work
with CNCF staff in resolving the report.

## Voting

While most business in Devfile is conducted by "lazy consensus", periodically
the Maintainers may need to vote on specific actions or changes.
A vote can be taken on [Devfile API discussion board](https://github.com/devfile/api/discussions) or
[the private Maintainer mailing list](https://lists.cncf.io/g/cncf-devfile-maintainers) for security or conduct matters.
Votes may also be taken on [Devfile API discussion board](https://github.com/devfile/api/discussions). Any Maintainer may
demand a vote be taken.

Most votes require a simple majority of all Maintainers to succeed. Maintainers
can be removed by a 2/3 majority vote of all Maintainers, and changes to this
Governance require a 2/3 vote of all Maintainers.
17 changes: 17 additions & 0 deletions MAINTAINERS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Devfile Maintainers

Official list of Devfile projects maintainers.

Please keep the below list sorted in ascending order.

## Maintainers

| Maintainer | GitHub ID | Affiliation |
| --------------- | --------- | ----------- |
| Andreas Resios | @resios | AWS |
| Angel Misevski | @amisevsk | Red Hat |
| Elson Yuen | @elsony | Red Hat |
| Ida Olsen | @miaida | AWS |
| Mario Loriedo | @l0rd | Red Hat |
| Stevan Le Meur | @slemeur | Red Hat |
| Tomas Kral | @kadel | Red Hat |