aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/htdocs/internal/doceng.sgml
blob: 72466cb068fe9ea3fdf1d52aa47f9d1dde8df46e (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/internal/doceng.sgml,v 1.13 2008/04/12 12:28:37 blackend Exp $">
<!ENTITY title "FreeBSD Doceng Team Charter">
<!ENTITY % navinclude.docs "INCLUDE">
<!ENTITY % developers PUBLIC "-//FreeBSD//ENTITIES FreeBSD Developers Entities//EN"> %developers;
]>
<html>
  &header;

<p>The doceng@ team is a new body to handle some of the meta-project
  issues associated with the FreeBSD Documentation Project.  The main
  responsibilities of this team are :</p>

<ul>
  <li>To grant approval for new doc/, www/, release documentation, and
      manual page committers.</li>

  <li>To maintain the doc project primer, which documents best
      practices for the FreeBSD Documentation Project.</li>

  <li>To manage the doc/ 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.</li>

  <li>To ensure that the generated documentation (PDF, HTML, etc.) on
      the Web site and FTP site are up to date with respect to the
      versions of the documents in the CVS tree.  This includes making
      sure the Web site build is functioning correctly, and also
      involves working with the admin team to ensure that the primary
      Web server has all of the requisite software installed
      (including build scripts).</li>

  <li>To act as MAINTAINER (when necessary) or to work in coordination
      with existing MAINTAINERs, to ensure that the documentation
      toolchains (DocBook, groff, etc.) are in good working order.</li>

  <li>To maintain the sanctity of the FreeBSD doc/ and www/ trees.
      Due to the visibility of these files and documents to the
      outside world, doceng@ reserves the right to immediately backout
      (or fix without waiting for response from the original
      committer) changes that introduce broken links, cause the Web
      site build to break, or otherwise degrade the accessibility of
      the FreeBSD Web site and documentation.</li>
</ul>

<p>It is specifically noted here that doceng@ is *not* a conflict
resolution body for the FreeBSD Documentation Project.  Discussion and
consensus on the freebsd-doc mailing list is how the project has
conducted itself, and how it is expected to conduct itself in the
future.</p>

<h2>Current Membership</h2>

The current members of this team are Nik Clayton, Marc
Fonvieille, Hiroki Sato, and Giorgos Keramidas.  It is expected that the
membership of this list will increase as additional members from the
various translation teams are added.

<h2>New Doc Committers</h2>

New doc committers are approved by doceng@ with a vote through email
and a 1 week timeout.  A committer is approved if at least 1 doceng@
member votes yes, and no doceng@ members vote no.

core@ is CCed on the message to accounts@ about the new account.

<h2>Idle Doc Committers</h2>

Doc Committers that have not made a commit in 12 months will be
contacted by a doceng@ 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@
about the idle committers.

  &footer;
  </body>
</html>