FreeBSD Docmgr Team Charter
===========================

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
  commit bits: translator commit bit, which is limited to translations
  in a particular language and full commit bit, which is only granted
  to aspirants, who have shown enough English technical writing
  skills,

- To maintain the sanctity of the FreeBSD doc tree. Due to the
  visibility of these files and documents to the outside world,
  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 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.

Membership
==========

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 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, docmgr@
sends out an acceptance email to the mentor and the new committer with
core@ and accounts@ CC'ed.

Doc Committers Commit Bit Policy
================================

Doc Committers that have not made a commit in 18 months will be
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, 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.

[EOF]