Define the governance model for the project

Created on 6 October 2023, over 1 year ago
Updated 7 October 2023, over 1 year ago

Problem/Motivation

Having an explicit decision making process can bring transparency to the project and make collaborating smoother, especially when difficult decisions need to be made.

Proposed resolution

Have maintainers and active contributors draft a governance model, get community feedback and then have maintainers finalize it.

Draft Governance Doc

Comment Notify is governed by its maintainers who maintain the vision and quality of the module, with large input from the wider community of users.

Decisions are made by lazy consensus, meaning that a decision as long as there are no serious objections raised by a maintainer. Anyone, including non-maintainers, can raise an issue by filing it in the issue queue. Maintainers strive to reply to all issues in a timely manner.

Anyone can request to become a maintainer. They are granted maintainer status as long as none of the existing maintainers object after reading their request.

A current maintainer can be step down as a maintainer at any time, though communication ahead of time is strongly encouraged. If a maintainer violates the Drupal Code of Conduct or becomes absent, anyone can request they be removed. That maintainer is removed if there is no objection from the other maintainers after they've read the request and heard any defense from the accused maintainer.

Remaining tasks

  1. ✅ Draft a governance plan
  2. ❌ Get community feedback
  3. ❌ Revise based on feedback
  4. ❌ Finalize governance plan
  5. ❌ Document the plan in a GOVERNANCE.md file
📌 Task
Status

Needs review

Version

1.0

Component

Miscellaneous

Created by

🇺🇸United States cedewey Denver, CO

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024