Important Governance Updates for the Daft Project #6271
everettVT
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As the Daft community has grown, from a handful of contributors to a community of developers, users, and organizations, we've reached a point where our informal processes no longer match the scale of what we're building together.
Full Details can be found the Contributing Guide
As of PR 6117, the project is adopting a tiered governance structure with three distinct roles:
We've also improved codeownership to make it easier for contributors to push changes into the main branch. With this change most of the daft codebase is now reviewable by community maintainers.
Finally, in order to ensure a uniform issue triage process, all non-trivial PRs are required to be linked to an issue that has been approved by a maintainer. This also means, non-trivial PRs that do not meet the requirements may be closed without review. Trivial PRs (docs, typos, small test fixes, clearly scoped bugfixes) may bypass the issue requirement, but must be labeled no-issue-needed by a maintainer. See the Contributing Code for what counts as non-trivial.
Beta Was this translation helpful? Give feedback.
All reactions