Skip to content

Commit

Permalink
Merge pull request #762 from microwavables/update-gov-doc
Browse files Browse the repository at this point in the history
updated link for mailing list
  • Loading branch information
joaopapereira authored May 8, 2024
2 parents 71421b4 + 232132c commit fb58cfa
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Once we have maintainers from other companies, votes by maintainers belonging to
The proposal process, including a [Proposal Template](https://github.com/carvel-dev/carvel/tree/develop/proposals#proposal-template), is covered at length within the [proposal directory](https://github.com/carvel-dev/carvel/tree/develop/proposals).

# Lazy Consensus
To maintain velocity in a project as busy as Carvel, the concept of [Lazy Consensus](http://en.osswiki.info/concepts/lazy_consensus) is practiced. Ideas and / or proposals should be shared by maintainers via GitHub. Out of respect for other contributors, major changes should also be accompanied by a ping on the Kubernetes Slack in [#Carvel](https://kubernetes.slack.com/archives/CH8KCCKA5) or a note on the [Carvel mailing list](carvel-dev@googlegroups.com) as appropriate. Author(s) of proposals, Pull Requests, issues, etc., will give a time period of no less than five (5) working days for comment and remain cognizant of popular observed world holidays.
To maintain velocity in a project as busy as Carvel, the concept of [Lazy Consensus](http://en.osswiki.info/concepts/lazy_consensus) is practiced. Ideas and / or proposals should be shared by maintainers via GitHub. Out of respect for other contributors, major changes should also be accompanied by a ping on the Kubernetes Slack in [#Carvel](https://kubernetes.slack.com/archives/CH8KCCKA5) or a note on the [Carvel mailing list](cncf-carvel-users@lists.cncf.io) as appropriate. Author(s) of proposals, Pull Requests, issues, etc., will give a time period of no less than five (5) working days for comment and remain cognizant of popular observed world holidays.

Other maintainers may chime in and request additional time for review, but should remain cognizant of blocking progress and abstain from delaying progress unless absolutely needed. The expectation is that blocking progress is accompanied by a guarantee to review and respond to the relevant action(s) (proposals, PRs, issues, etc.) in short order.

Expand Down

0 comments on commit fb58cfa

Please sign in to comment.