--- charter-doceng.txt 2025-07-28 03:32:22.948759000 +0900 +++ charter-docmgr.txt 2025-07-28 15:59:56.017603000 +0900 @@ -1,9 +1,24 @@ -FreeBSD Doceng Team Charter +FreeBSD Docmgr Team Charter =========================== -The doceng@ team is a body to oversee the FreeBSD Documentation -Project. The main responsibilities of this team are: +The docmgr@ team is the body that plans and oversees the FreeBSD +Documentation Project. This has been organized since 2025 by +dissolving the doceng@ team, which was responsible primarily for the +commit bit approval and engineering works. +The responsibilities of this team are: + +- To organize and prioritize ongoing efforts and proposed future + directions about the documentation set and build infrastructure, and + publish summaries of them as "roadmap," + +- To appoint people who work on specific engineering works based on + the roadmap, including the doc tree release process, ensuring the + documentation published on the Internet by the project is up to date + with respect to the source files in the repository, documentation + toolchains in the FreeBSD Ports Collection to build the doc tree, + but not limited to them, + - To grant approval for new documentation committers. Documentation includes articles and books, website pages, manual pages, release notes and translations of the above. There are two kinds of doc @@ -12,70 +27,59 @@ to aspirants, who have shown enough English technical writing skills, -- To prioritize and steer future directions for the documentation set - and documentation infrastructure in the project, - -- To maintain the doc project primer, which documents best practices - for the FreeBSD Documentation Project, - -- To manage the doc tree release process. This includes coordinating - the release documentation updates with the various translation - teams, coordinating with the release engineering team to tag the doc - tree during the release cycle, and documenting these procedures, - -- To ensure that the documentation published on the Internet by the - project is up to date with respect to the source files in the - repository. This includes making sure the project's infrastructure - to build them is functioning correctly, and also involves working - with the clusteradm team to get access to the project's machine and - network resources, - -- To act as MAINTAINER or to work in coordination with existing - MAINTAINERs of the documentation toolchains in the FreeBSD Ports - Collection to ensure them are in good working order, - - To maintain the sanctity of the FreeBSD doc tree. Due to the visibility of these files and documents to the outside world, - doceng@ reserves the right to immediately backout (or fix without + docmgr@ reserves the right to immediately backout (or fix without waiting for response from the original committer) changes that introduce degradations of the quality or the accessibility of the FreeBSD documentation, -- To appoint and oversee a FreeBSD Webmaster Team that carries out - daily maintenance of the project web servers in collaboration with - other teams, - - To act as first arbiter in the case of technical disputes related to the documentation and the doc tree. This charter has been appointed by the FreeBSD Core Team since [When]. Any changes to it requires an approval from the FreeBSD Core Team. -Current Membership -================== +Membership +========== -The current members of this team are Glen Barber, Warren Block, Marc -Fonvieille, Gabor Kovesdan, Benedict Reuschling, Hiroki Sato, and -Ryusuke SUZUKI. Mateusz Piotrowski has been appointed as the doceng -secretary. +The team consists of voting and non-voting members. The voting +members shall be at least three full doc-committers. They shall serve +terms of two years and are responsible for selecting replacements for +members whose terms have expired. A term-completed member or a member +who resigned during a term will be eligible for another term after a +half-term break. To avoid the situation where everyone is replaced at +once, existing members must conduct a selection process at least every +half-term boundary. The term of office for new members begins with +the month following the month in which they are appointed. +Non-voting members are expected to contribute to roadmap +discussions. They are not responsible for final decision-making or +organizational maintenance duties. The rules governing the term for +voting members also apply to non-voting members, except that the +voting members may set the term for non-voting members and must be no +longer than two years. + +The Core Team shall select the initial team members. At its +discretion, the Core Team reserves the right to alter the membership. + New Doc Committers ================== -New doc committers are approved by doceng@ with a vote through email. +New doc committers are approved by docmgr@ with a vote through email. This voting is conducted basically based on the rules of Core's voting procedure (https://www.freebsd.org/internal/core-vote.html) except for -a two-week timeout. When a commit bit proposal is accepted, doceng@ +a two-week timeout. When a commit bit proposal is accepted, docmgr@ sends out an acceptance email to the mentor and the new committer with core@ and accounts@ CC'ed. -Idle Doc Committers -=================== +Doc Committers Commit Bit Policy +================================ Doc Committers that have not made a commit in 18 months will be -contacted by a doceng@ member and without a response after a delay of +contacted by a docmgr@ member and without a response after a delay of 2 weeks, these committers will be automatically removed from the -access file. In case of no response, doceng@ will also contact core@ +access file. In case of no response, docmgr@ will also contact core@ about the idle committers. Committers that wish to get back their commit bits will have to reapply with the appropriate authority.