was redundant with text in the Porter's Handbook. Add text about what
portmgr is supposed to do. Provide links to documentation that needs
to be changed. Mention the CVSup examples.
Reviewed for content by: pav
a bit more than "an hour or two".
- The explenation of what needs approval and what not, during
a freeze was ambiguous, so clarify that all patches need
approval during a freeze.
While here:
- Add some links to the Portmgr Quality Assurance page.
- Use "the ports management team" instead of "the ports
manager" as we're more than one person and have been
for quite a while.
Reviewed by: marcus, krion
Approved by: remko
informaltable element properly, unless the pgwide attribute is
explicitly set to 1. Use this consistently within the (en) tree, and
update the FDP accordingly. This should finally silence the demons in:
PR: docs/73095
Submitted by: Hilko Meyer <Hilko dot Meyer at gmx dot de>
speed up commits, avoid locking parts of the CVS tree for a very
long time and lets the committer take his time when writing the
commit message.
Hopefully, this way the quality of commit messages is easier to
control and we'll save ourselves some of the problems that can
result from hickups of the CVS repo-locking mechanism.
Approved by: re (Hiroki Sato)
Currently we have articles.ent and books.ent, and
for example, articles.ent can be used by putting the
following lines in the doctype declaration:
<!ENTITY % articles.ent PUBLIC
"-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
This pulls all of the necessary entities via share/sgml/articles.ent.
The translation teams can customize these entities by redefining
the articles.ent file in <langcode>/share/sgml. See
ja_JP.eucJP/share/sgml for example.
is not defined.
- URL_RELPREFIX must always point the top page's URL
(http://www.FreeBSD.org) in relative form, defined in Makefile.
- &url.base; can be used in doc/<langcode>/*. It will be
replaced with the real URL which points the top page.
For translators: Please make sure to define URL_RELPREFIX to
point the top page. The localized docs have different directory
hierarchy in its URL from the English version.
Tested by: den
Ihis entity auto-replaced with ../../../.. by default
and with http://www.FreeBSD.org/ when URLS_ABSOLUTE is set
(used for mirrors and for release building accordingly)
ports collection. One step is not yet defined; hopefully this will be
resolved soon.
PR: docs/64144
Reviewed by: eik and many others
Approved by: ceri (mentor)
- Remove the requirement for mentors to send PGP keys of new
committers to admins@.
committers-guide/article.sgml:
- Update copyright year.
- Emphasize that new committers should add their PGP key to the
Handbook, since it might be needed for identification, e.g. for
account recovery.
teams.ent:
- Add an entiry for admins@.
Discussed with: admins (joe, kensmith)
- Add trademark tags as needed, generally on first use in each
article.
- Add an attribution to the legal section mentioning all trademarks
referenced.
- Always use correct case for trademarks.
- Don't join trademarks with other words, e.g. using hyphens.
trademark.ent:
- Commonly used trademarks are defined as entities for ease of use.
- All trademark attributions are defined as entities for ease of use.
Approved by: ceri (mentor)
CVS operations, where it fits slightly better.
Note to translators: I have tried to be sensitive to whitespace here, but it
has proved to be quite difficult in both this and the last revision. Apologies
in advance.
In reality, it is pretty close to Tier-1, but there are still a few
loose ends that need to be taken care of before locking down ABIs etc.
It was actually included in 5.1-RELEASE and it now has pre-built ports
packages etc.
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
o doc committers are also the group primarily responsible for www/
o Update an outdated example GNATS categories file
o Point a link to the Staff list at the Staff list
o Remove the text associated with the "Don't Touch The Repo" Rule
o Update references within the Big List of Rules
Repository Copy question on Porter's FAQ
o Reviewers wrote the committed version
Reviewed by: adamw, ceri, steve, tom,
"Gary W. Swearingen" <swear@attbi.com>,
Warren Block <wblock@wonkity.com>
Describe how to commit on ncvs.FreeBSD.org using remote CVS.
Add a note to NOT use the main repository host as your personal
cvs server, as inspired by peter's mail to developers@ a while back.
Refer to the cvsup distribution method and cvsup-master instead and
give an example of an "fcvs" alias, as suggested by many committers.
Reword or remove various paragraphs about not modifiying the repository
yourself, which is no longer possible, since only repomeisters have
access to ncvs.FreeBSD.org.
Remove the paragraph about CVSUMASK, which no longer applies.
FreeBSD implementation on it at production quality, and x86-64-specific
code is in progress in a combination of the main FreeBSD CVS repository
and Perforce. Once x86-64 native support is appropriately improved, we
can migrate it to Tier 2.
Requested by: obrien
Approved by: core
status of various architectural platforms and requirements for
support and development of those platforms. This policy distinguishes
systems into four tiers:
Tier 1: Fully Supported Architectures
Tier 2: Developmental Architectures
Tier 3: Experimental Architectures
Tier 4: Unsupported Architectures
In addition, the Core Team has also approved a policy regarding how
the status of a hardware architecture may be formally changed. This
policy is new, and subject to review, comment, and modification as
appropriate. The details of this policy are implemented in this
change to the FreeBSD Committer's Handbook, which all committers
are encouraged to read and review.
Note: Although sparc64 is currently listed as a 'Developmental
Architecture', it is expected that it will become a 'Fully Supported
Architecture' prior to FreeBSD 5.0. Likewise, it is likely that
ia64 will become a 'Fully Supported Architecture' prior to the
release.
as follows:
RELENG_3 no longer a noteworthy tag.
Refer to repository meisters and SO team more consistently, less
dependence on individuals.
Don't refer to core as "we".
Comment to help out doc translation teams.
Move myself to RE team and consolidate "Who's Who" listings accordingly.
Security branch changes need to be approved by SO or RE teams.
Add mentions of developers list, where appropriate.
Wording tweaks.
Approved by: jhb
There is one remaining place in the fdp-primer, but that needs
a bit more work.
Inspired by: docs/36462 (Gary W. Swearingen <swear@blarg.net>)
Reviewed by: ceri, trhodes
which discusses the notion of areas of authority for the CVS repository,
the parties responsible for each area and allocating commit rights for it,
and general practices for expanding the scope of a commit bit to new
areas of the tree. Throw in some text reminding everyone that review
of source code is always a good idea.
Approved by: core@
instructions. The potentially conflicting instructions could be taken
to encourage less than ideal commit logs. Explicitly say that we're
after a clear, concise and reasonable summary of the change.
Reviewed by: obrien
