Source string Read only

(itstool) path: sect2/title
12/120
Context English State
doceng@
doc/, ports/, src/ documentation
ports
portmgr@
ports/
Commit bits allocated prior to the development of the notion of areas of authority may be appropriate for use in many parts of the tree. However, common sense dictates that a committer who has not previously worked in an area of the tree seek review prior to committing, seek approval from the appropriate responsible party, and/or work with a mentor. Since the rules regarding code maintenance differ by area of the tree, this is as much for the benefit of the committer working in an area of less familiarity as it is for others working on the tree.
Committers are encouraged to seek review for their work as part of the normal development process, regardless of the area of the tree where the work is occurring.
Policy for Committer Activity in Other Trees
All committers may modify <filename>base/head/share/misc/committers-*.dot</filename>, <filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>, and <filename>ports/head/astro/xearth/files</filename>.
doc committers may commit documentation changes to <filename>src</filename> files, such as man pages, READMEs, fortune databases, calendar files, and comment fixes without approval from a src committer, subject to the normal care and tending of commits.
Any committer may make changes to any other tree with an "Approved by" from a non-mentored committer with the appropriate bit.
Committers can acquire an additional bit by the usual process of finding a mentor who will propose them to core, doceng, or portmgr, as appropriate. When approved, they will be added to 'access' and the normal mentoring period will ensue, which will involve a continuing of <quote>Approved by</quote> for some period.
"Approved by" is only acceptable from non-mentored src committers -- mentored committers can provide a "Reviewed by" but not an "Approved by".
Subversion Primer
New committers are assumed to already be familiar with the basic operation of Subversion. If not, start by reading the <link xlink:href="http://svnbook.red-bean.com/">Subversion Book</link>.
Introduction
The FreeBSD source repository switched from <acronym>CVS</acronym> to Subversion on May 31st, 2008. The first real <acronym>SVN</acronym> commit is <emphasis>r179447</emphasis>.
The FreeBSD <literal>doc/www</literal> repository switched from <acronym>CVS</acronym> to Subversion on May 19th, 2012. The first real <acronym>SVN</acronym> commit is <emphasis>r38821</emphasis>.
The FreeBSD <literal>ports</literal> repository switched from <acronym>CVS</acronym> to Subversion on July 14th, 2012. The first real <acronym>SVN</acronym> commit is <emphasis>r300894</emphasis>.
Subversion can be installed from the FreeBSD Ports Collection by issuing these commands:
<prompt>#</prompt> <userinput>pkg install subversion</userinput>
Getting Started
There are a few ways to obtain a working copy of the tree from Subversion. This section will explain them.
Direct Checkout
The first is to check out directly from the main repository. For the <literal>src</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh://repo.freebsd.org/base/head /usr/src</userinput>
For the <literal>doc</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh://repo.freebsd.org/doc/head /usr/doc</userinput>
For the <literal>ports</literal> tree, use:
<prompt>%</prompt> <userinput>svn checkout svn+ssh://repo.freebsd.org/ports/head /usr/ports</userinput>
Though the remaining examples in this document are written with the workflow of working with the <literal>src</literal> tree in mind, the underlying concepts are the same for working with the <literal>doc</literal> and the <literal>ports</literal> tree. Ports related Subversion operations are listed in <xref linkend="ports"/>.

Showing only subset of the strings as there were too many matches.

Component Translation Difference to current string
This translation Translated FreeBSD Doc/articles_committers-guide
The following strings have the same context and source.
Translated FreeBSD Doc/articles_building-products
Translated FreeBSD Doc/articles_freebsd-questions
Translated FreeBSD Doc/articles_geom-class
Translated FreeBSD Doc/articles_mailing-list-faq
Translated FreeBSD Doc/articles_gjournal-desktop
Translated FreeBSD Doc/articles_leap-seconds
Translated FreeBSD Doc/articles_linux-emulation
Translated FreeBSD Doc/articles_linux-users
Translated FreeBSD Doc/articles_vm-design
Translated FreeBSD Doc/articles_pr-guidelines
Translated FreeBSD Doc/articles_fonts
Translated FreeBSD Doc/articles_problem-reports
Translated FreeBSD Doc/articles_freebsd-update-server
Translated FreeBSD Doc/articles_pam
Translated FreeBSD Doc/articles_rc-scripting
Translated FreeBSD Doc/articles_releng
Translated FreeBSD Doc/books_porters-handbook
Translated FreeBSD Doc/articles_remote-install
Translated FreeBSD Doc/books_faq

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/title
Flags
read-only
Source string location
article.translate.xml:493
String age
a year ago
Source string age
a year ago
Translation file
articles/committers-guide.pot, string 90