The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: varlistentry/term
Context English State
Change your <application>Phabricator</application> account email to your <systemitem class="domainname"></systemitem> email.
Open new bug on our bug tracker using your <systemitem class="domainname"></systemitem> account, see <xref linkend="bugzilla"/> for more information. Choose <literal>Services</literal> as the Product, and <literal>Code Review</literal> as the Component. In bug description request that your <application>Phabricator</application> account be renamed, and provide a link to your <application>Phabricator</application> user. For example, <literal><replaceable></replaceable>/</literal>
<application>Phabricator</application> accounts cannot be merged, please do not open a new account.
Who's Who
Besides the repository meisters, there are other FreeBSD project members and teams whom you will probably get to know in your role as a committer. Briefly, and by no means all-inclusively, these are:
Documentation Engineering Team <email></email>
doceng is the group responsible for the documentation build infrastructure, approving new documentation committers, and ensuring that the FreeBSD website and documentation on the FTP site is up to date with respect to the <application>subversion</application> tree. It is not a conflict resolution body. The vast majority of documentation related discussion takes place on the <link xlink:href="">FreeBSD documentation project mailing list</link>. More details regarding the doceng team can be found in its <link xlink:href="">charter</link>. Committers interested in contributing to the documentation should familiarize themselves with the <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/fdp-primer/index.html">Documentation Project Primer</link>.
Glen Barber <email></email>, Konstantin Belousov <email></email>, Bryan Drewery <email></email>, Marc Fonvieille <email></email>, Xin Li <email></email>, Colin Percival <email></email> Hiroki Sato <email></email>, Gleb Smirnoff <email></email>
These are the members of the Release Engineering Team <email></email>. This team is responsible for setting release deadlines and controlling the release process. During code freezes, the release engineers have final authority on all changes to the system for whichever branch is pending release status. If there is something you want merged from FreeBSD-CURRENT to FreeBSD-STABLE (whatever values those may have at any given time), these are the people to talk to about it.
Gordon Tetlow <email></email>
Gordon Tetlow is the <link xlink:href="@@URL_RELPREFIX@@/security/">FreeBSD Security Officer</link> and oversees the Security Officer Team <email></email>.
Garrett Wollman <email></email>
If you need advice on obscure network internals or are not sure of some potential change to the networking subsystem you have in mind, Garrett is someone to talk to. Garrett is also very knowledgeable on the various standards applicable to FreeBSD.
FreeBSD committer's mailing list
<link xlink:href="">svn-src-all</link>, <link xlink:href="">svn-ports-all</link> and <link xlink:href="">svn-doc-all</link> are the mailing lists that the version control system uses to send commit messages to. <emphasis>Never</emphasis> send email directly to these lists. Only send replies to this list when they are short and are directly related to a commit.
FreeBSD developers mailing list
All committers are subscribed to -developers. This list was created to be a forum for the committers <quote>community</quote> issues. Examples are Core voting, announcements, etc.
The FreeBSD developers mailing list is for the exclusive use of FreeBSD committers. To develop FreeBSD, committers must have the ability to openly discuss matters that will be resolved before they are publicly announced. Frank discussions of work in progress are not suitable for open publication and may harm FreeBSD.
All FreeBSD committers are expected not to not publish or forward messages from the FreeBSD developers mailing list outside the list membership without permission of all of the authors. Violators will be removed from the FreeBSD developers mailing list, resulting in a suspension of commit privileges. Repeated or flagrant violations may result in permanent revocation of commit privileges.
This list is <emphasis>not</emphasis> intended as a place for code reviews or for any technical discussion. In fact using it as such hurts the FreeBSD Project as it gives a sense of a closed list where general decisions affecting all of the FreeBSD using community are made without being <quote>open</quote>. Last, but not least <emphasis>never, never ever, email the FreeBSD developers mailing list and CC:/BCC: another FreeBSD list</emphasis>. Never, ever email another FreeBSD email list and CC:/BCC: the FreeBSD developers mailing list. Doing so can greatly diminish the benefits of this list.
SSH Quick-Start Guide
If you do not wish to type your password in every time you use <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry>, and you use keys to authenticate, <citerefentry><refentrytitle>ssh-agent</refentrytitle><manvolnum>1</manvolnum></citerefentry> is there for your convenience. If you want to use <citerefentry><refentrytitle>ssh-agent</refentrytitle><manvolnum>1</manvolnum></citerefentry>, make sure that you run it before running other applications. X users, for example, usually do this from their <filename>.xsession</filename> or <filename>.xinitrc</filename>. See <citerefentry><refentrytitle>ssh-agent</refentrytitle><manvolnum>1</manvolnum></citerefentry> for details.
Generate a key pair using <citerefentry><refentrytitle>ssh-keygen</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The key pair will wind up in your <filename>$HOME/.ssh/</filename> directory.
Only <acronym>ECDSA</acronym>, <acronym>Ed25519</acronym> or <acronym>RSA</acronym> keys are supported.
Send your public key (<filename>$HOME/.ssh/</filename>, <filename>$HOME/.ssh/</filename>, or <filename>$HOME/.ssh/</filename>) to the person setting you up as a committer so it can be put into <filename><replaceable>yourlogin</replaceable></filename> in <filename>/etc/ssh-keys/</filename> on <systemitem>freefall</systemitem>.
Now <citerefentry><refentrytitle>ssh-add</refentrytitle><manvolnum>1</manvolnum></citerefentry> can be used for authentication once per session. It prompts for the private key's pass phrase, and then stores it in the authentication agent (<citerefentry><refentrytitle>ssh-agent</refentrytitle><manvolnum>1</manvolnum></citerefentry>). Use <command>ssh-add -d</command> to remove keys stored in the agent.
Test with a simple remote command: <command>ssh ls /usr</command>.
For more information, see <package>security/openssh-portable</package>, <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>ssh-add</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>ssh-agent</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>ssh-keygen</refentrytitle><manvolnum>1</manvolnum></citerefentry>, and <citerefentry><refentrytitle>scp</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
For information on adding, changing, or removing <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> keys, see <uri xlink:href="">this article</uri>.
<trademark class="registered">Coverity</trademark> Availability for FreeBSD Committers
All FreeBSD developers can obtain access to <application>Coverity</application> analysis results of all FreeBSD Project software. All who are interested in obtaining access to the analysis results of the automated <application>Coverity</application> runs, can sign up at <uri xlink:href="">Coverity Scan</uri>.


No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: varlistentry/term
Source string location
String age
a year ago
Source string age
a year ago
Translation file
articles/committers-guide.pot, string 634