Welcome to the Tinted Theming project! This document outlines the governance structure and procedures for maintaining and contributing to this theming driven community.
The Tinted Theming project is currently governed by three admins:
- [@belak], who has been actively involved in the community since the original base16 theming project.
- @JamyGolden, who has been actively involved in the formation of base16-project and tinted-theming.
- @FredHappyface, who created base24 and recently joined the administration team.
Final Say: The admins collectively have the final say on all matters related to the overall direction, policies, and major decisions concerning the project. This ensures that the project remains true to its core values and goals while also allowing for flexibility and community input.
Project-wide decisions are typically made through consensus among the admins. In cases where consensus cannot be reached, a majority vote among the admins will determine the final decision.
In cases where the admins are unresponsive (e.g., no response for 4 weeks on an escalated issue or PR), the community can take the following steps:
- Community Discussion: Open a discussion issue or use the project's designated communication channel to gather input from other contributors and maintainers.
- Community Consensus: If a clear consensus is reached within the community (with input from other maintainers), the decision can be acted upon by those involved in the discussion.
- Request Admin Intervention: If possible, attempt to contact admins through other channels (email, social media, etc.) to notify them of the situation.
- Temporary Action: In the absence of admin response, maintainers or active contributors may make temporary decisions, such as merging a critical PR, until the admins return.
Note: If an admin remains unresponsive, the other admins will continue to carry out their responsibilities and may make decisions on behalf of the project as necessary. If all admins become unresponsive, the community should follow the steps outlined above.
Note: If maintainers or admins expect to be unavailable for an extended period, they are encouraged to notify the community in advance, if possible, to arrange for temporary coverage or decision-making processes.
If a template maintainer does not respond to an issue or pull request (PR) within a reasonable timeframe (typically 3 weeks), the admins may step in to make a decision on behalf of the maintainer. This ensures that the project continues to move forward and that contributions are not stalled unnecessarily.
The process in such cases will be as follows:
- Initial Attempt: Contributors should first try to contact the maintainer via the issue or PR thread.
- Escalation: If there is no response after 3 weeks, the issue or PR can be escalated by tagging the admins in a comment; @tinted-theming/admins to tag all admins.
- Admin Decision: Admins will review the situation and may:
- Reach out to the maintainer through other means.
- Make a decision on the issue or PR if the maintainer remains unresponsive.
- Appoint a temporary or new maintainer if the original maintainer is no longer active.
To ensure the smooth operation of the project and prevent prolonged unresponsiveness, it is important to periodically review the activity of admins and maintainers. When an admin becomes permanently inactive, steps must be taken to maintain effective leadership. This may involve appointing a replacement from active community members or making other necessary changes.
Admins may also step down voluntarily or be asked to step down by a majority of the other admins. In either case, the following process will be followed:
The other admins and the community should be notified as soon as possible.
The remaining admins, with input welcome from the community, will select a new admin. Candidates should be contributors who have shown commitment to the project.
The selection process will involve consensus or a majority vote among the remaining admins.
During the transition, the outgoing admin will be offboarded by having admin access removed from GitHub and other services.
Once the new admin is appointed and the transition is complete, the outgoing admin will officially step down. The change should be documented, and the community will be informed.
Former admins are welcome to remain involved in the project in any capacity they choose, whether as contributors, advisors, or in another role.
Each project within Tinted Theming is managed by a dedicated maintainer or maintainers. These maintainers are responsible for overseeing the development, updates, and quality of their respective templates.
Final Say on Templates: Maintainers generally have the final say regarding their specific templates, as they possess the most intimate knowledge and expertise concerning their design and functionality. However, admins reserve the right to intervene if a template decision:
- Significantly affects the broader project or community.
- Conflicts with the project's core principles or guidelines.
- Introduces potential security or usability concerns.
In such cases, admins may discuss the issue with the template maintainer to reach a resolution, and if necessary, admins may have the final say.
To ensure the continued quality and consistency of the Tinted Theming project, all contributions are reviewed against the following acceptance criteria:
- Alignment with Project Goals: The PR should align with the overall goals and philosophy of the Tinted Theming organization.
- Code Quality: The code should be clean, well-documented, and follow the project's coding standards.
- No Breaking Changes: PRs should not introduce breaking changes for users unless absolutely necessary. If a breaking change is required, it must be well-documented, and a clear migration path should be provided.
- Community Feedback: PRs should consider feedback from the community where appropriate. If significant concerns are raised by the community, they should be addressed before the PR is merged.
- Consistency: The PR should maintain the stylistic and functional consistency of the template.
- Testing: PRs should include appropriate testing to ensure the template functions as expected across different environments and use cases.
- Backward Compatibility: As much as possible, changes should be backward compatible with previous versions of the template.
- Initial Review: The template maintainer or designated reviewers will conduct an initial review of the PR.
- Feedback Loop: If changes or improvements are required, the contributor will receive feedback and have the opportunity to address it.
- Final Approval: Once the PR meets all criteria and any feedback has been addressed, the maintainer or admins will give final approval for merging.
For larger changes or additions, maintainers or contributors are encouraged to open a discussion issue before submitting a PR to gauge interest and gather early feedback.
For more detailed instructions on how to contribute, please refer to our CONTRIBUTING.md file.
We hope this document provides clarity on the governance and contribution processes within the Tinted Theming organization. Thank you for your involvement and contributions!
For any further questions, please feel free to reach out to the admins [@belak], @JamyGolden and @FredHappyface on Github or on Matrix Chat.