Changes to Committee Charter
Initiation of Charter Change:
Any member of the committee can propose changes to the charter. Before any changes are made, the proposal should be discussed and refined among the committee members. Voting on the
Charter Change:
All proposed changes to the charter must be voted upon by the committee. A simple majority is usually sufficient to pass the changes unless otherwise specified in the original charter or bylaws.
Ratification by the Community:
Once the changes have been approved by the committee, they should be presented to the community for ratification. The community should be given ample time to review and discuss the proposed changes before voting. The method of collecting votes from the community should be transparent, accessible, and verifiable.
Archiving the Old Charter:
After the changes have been ratified by the community, the old charter must be preserved for historical reference. The old charter should be moved to the "charter archive" section on the GitHub repository.
Updating the GitHub Repository:
The newly ratified charter should be prominently displayed for easy access. Paste the new charter into the README.md file located in the top level of the GitHub repository. This ensures that visitors to the repository are immediately aware of the current charter's contents.
Announcement and Communication:
After the new charter is in place, an announcement should be made to the committee, the community, and any other relevant stakeholders. This can be done via email, forums, community meetings, or any other communication channel that is commonly used.
Regular Review:
It's good practice to regularly review the charter, at least annually, to ensure that it remains relevant and serves the needs of the committee and the community.
Documentation:
Ensure that all discussions, votes, and ratifications are well-documented. This transparency will help in building trust with the community and provides a clear record for future reference.
Last updated