#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2018-12-08 14:45-0200\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr ""

#. (itstool) path: info/title
#: article.translate.xml:4
msgid "Contributing to FreeBSD"
msgstr ""

#. (itstool) path: abstract/para
#: article.translate.xml:8
msgid ""
"This article describes the different ways in which an individual or "
"organization may contribute to the FreeBSD Project."
msgstr ""

#. (itstool) path: authorgroup/author
#: article.translate.xml:14
msgid ""
"<personname><firstname>Jordan</firstname><surname>Hubbard</surname></"
"personname>"
msgstr ""

#. (itstool) path: authorgroup/author
#: article.translate.xml:15
msgid ""
"<personname><firstname>Sam</firstname><surname>Lawrance</surname></"
"personname>"
msgstr ""

#. (itstool) path: authorgroup/author
#: article.translate.xml:16
msgid ""
"<personname><firstname>Mark</firstname><surname>Linimon</surname></"
"personname>"
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:20
msgid "FreeBSD is a registered trademark of the FreeBSD Foundation."
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:22
msgid ""
"IEEE, POSIX, and 802 are registered trademarks of Institute of Electrical "
"and Electronics Engineers, Inc. in the United States."
msgstr ""

#. (itstool) path: legalnotice/para
#: article.translate.xml:25
msgid ""
"Many of the designations used by manufacturers and sellers to distinguish "
"their products are claimed as trademarks. Where those designations appear in "
"this document, and the FreeBSD Project was aware of the trademark claim, the "
"designations have been followed by the <quote>™</quote> or the <quote>®</"
"quote> symbol."
msgstr ""

#. (itstool) path: info/pubdate
#. (itstool) path: info/releaseinfo
#: article.translate.xml:33 article.translate.xml:35
msgid ""
"$FreeBSD: head/en_US.ISO8859-1/articles/contributing/article.xml 52228 2018-"
"09-06 01:39:04Z ebrandi $"
msgstr ""

#. (itstool) path: article/indexterm
#: article.translate.xml:38
msgid "<primary>contributing</primary>"
msgstr ""

#. (itstool) path: article/para
#: article.translate.xml:40
msgid ""
"So you want to contribute to FreeBSD? That is great! FreeBSD "
"<emphasis>relies</emphasis> on the contributions of its user base to survive."
" Your contributions are not only appreciated, they are vital to FreeBSD's "
"continued growth."
msgstr ""

#. (itstool) path: article/para
#: article.translate.xml:45
msgid ""
"A large and growing number of international contributors, of greatly varying "
"ages and areas of technical expertise, develop FreeBSD. There is always more "
"work to be done than there are people available to do it, and more help is "
"always appreciated."
msgstr ""

#. (itstool) path: article/para
#: article.translate.xml:50
msgid ""
"As a volunteer, what you do is limited only by what you want to do. However, "
"we do ask that you are aware of what other members of the FreeBSD community "
"will expect of you. You may want to take this into account before deciding "
"to volunteer."
msgstr ""

#. (itstool) path: article/para
#: article.translate.xml:55
msgid ""
"The FreeBSD project is responsible for an entire operating system "
"environment, rather than just a kernel or a few scattered utilities. As "
"such, our <filename>TODO</filename> lists span a very wide range of tasks: "
"from documentation, beta testing and presentation, to the system installer "
"and highly specialized types of kernel development. People of any skill "
"level, in almost any area, can almost certainly help the project."
msgstr ""

#. (itstool) path: article/para
#: article.translate.xml:63
msgid ""
"Commercial entities engaged in FreeBSD-related enterprises are also "
"encouraged to contact us. Do you need a special extension to make your "
"product work? You will find us receptive to your requests, given that they "
"are not too outlandish. Are you working on a value-added product? Please let "
"us know! We may be able to work cooperatively on some aspect of it. The free "
"software world is challenging many existing assumptions about how software "
"is developed, sold, and maintained, and we urge you to at least give it a "
"second look."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:74
msgid "What Is Needed"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:76
msgid ""
"The following list of tasks and sub-projects represents something of an "
"amalgam of various <filename>TODO</filename> lists and user requests."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:81
msgid "Ongoing Non-Programmer Tasks"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:83
msgid ""
"Many people who are involved in FreeBSD are not programmers. The Project "
"includes documentation writers, Web designers, and support people. All that "
"these people need to contribute is an investment of time and a willingness "
"to learn."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:91
msgid ""
"Read through the FAQ and Handbook periodically. If anything is poorly "
"explained, ambiguous, out of date or incorrect, let us know. Even better, "
"send us a fix (Docbook is not difficult to learn, but there is no objection "
"to ASCII submissions)."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:99
msgid ""
"Help translate FreeBSD documentation into your native language. If "
"documentation already exists for your language, you can help translate "
"additional documents or verify that the translations are up-to-date and "
"correct. First take a look at the <link xlink:href=\"@@URL_RELPREFIX@@/doc/"
"en_US.ISO8859-1/books/fdp-primer/translations.html\">Translations FAQ</link> "
"in the FreeBSD Documentation Project Primer. You are not committing yourself "
"to translating every single FreeBSD document by doing this — as a volunteer, "
"you can do as much or as little translation as you desire. Once someone "
"begins translating, others almost always join the effort. If you only have "
"the time or energy to translate one part of the documentation, please "
"translate the installation instructions."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:115
msgid ""
"Read the <link xlink:href=\"http://lists.FreeBSD.org/mailman/listinfo/"
"freebsd-questions\">FreeBSD general questions mailing list</link> "
"occasionally (or even regularly). It can be very satisfying to share your "
"expertise and help people solve their problems; sometimes you may even learn "
"something new yourself! These forums can also be a source of ideas for "
"things to improve upon."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:126
msgid "Ongoing Programmer Tasks"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:128
msgid ""
"Most of the tasks listed here may require a considerable investment of time, "
"an in-depth knowledge of the FreeBSD kernel, or both. However, there are "
"also many useful tasks which are suitable for <quote>weekend hackers</quote>."
""
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:136
msgid ""
"If you run FreeBSD-CURRENT and have a good Internet connection, there is a "
"machine <systemitem class=\"fqdomainname\">current.FreeBSD.org</systemitem> "
"which builds a full release once a day—every now and again, try to install "
"the latest release from it and report any failures in the process."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:145
msgid ""
"Read the <link xlink:href=\"http://lists.FreeBSD.org/mailman/listinfo/"
"freebsd-bugs\">FreeBSD problem reports mailing list</link>. There may be a "
"problem you can comment constructively on or with patches you can test. Or "
"you could even try to fix one of the problems yourself."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:152
msgid ""
"If you know of any bug fixes which have been successfully applied to -"
"CURRENT but have not been merged into -STABLE after a decent interval "
"(normally a couple of weeks), send the committer a polite reminder."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:159
msgid ""
"Move contributed software to <filename>src/contrib</filename> in the source "
"tree."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:165
msgid "Make sure code in <filename>src/contrib</filename> is up to date."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:171
msgid ""
"Build the source tree (or just part of it) with extra warnings enabled and "
"clean up the warnings."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:176
msgid ""
"Fix warnings for ports which do deprecated things like using "
"<function>gets()</function> or including <filename>malloc.h</filename>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:182
msgid ""
"If you have contributed any ports and you had to make FreeBSD-specific "
"changes, send your patches back to the original authors (this will make your "
"life easier when they bring out the next version)."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:189
msgid ""
"Get copies of formal standards like <trademark class=\"registered\">POSIX</"
"trademark>. Compare FreeBSD's behavior to that required by the standard. If "
"the behavior differs, particularly in subtle or obscure corners of the "
"specification, send in a PR about it. If you are able, figure out how to fix "
"it and include a patch in the PR. If you think the standard is wrong, ask "
"the standards body to consider the question."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:200
msgid "Suggest further tasks for this list!"
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:206
msgid "Work through the PR Database"
msgstr ""

#. (itstool) path: sect2/indexterm
#: article.translate.xml:208
msgid "<primary>problem reports database</primary>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:212
msgid ""
"The <link xlink:href=\"https://bugs.FreeBSD.org/search/\">FreeBSD PR list</"
"link> shows all the current active problem reports and requests for "
"enhancement that have been submitted by FreeBSD users. The PR database "
"includes both programmer and non-programmer tasks. Look through the open "
"PRs, and see if anything there takes your interest. Some of these might be "
"very simple tasks that just need an extra pair of eyes to look over them and "
"confirm that the fix in the PR is a good one. Others might be much more "
"complex, or might not even have a fix included at all."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:223
msgid ""
"Start with the PRs that have not been assigned to anyone else. If a PR is "
"assigned to someone else, but it looks like something you can handle, email "
"the person it is assigned to and ask if you can work on it—they might "
"already have a patch ready to be tested, or further ideas that you can "
"discuss with them."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:232
msgid "Ongoing Ports Tasks"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:234
msgid ""
"The Ports Collection is a perpetual work in progress. We want to provide our "
"users with an easy to use, up to date, high quality repository of third "
"party software. We need people to donate some of their time and effort to "
"help us achieve this goal."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:240
msgid ""
"Anyone can get involved, and there are lots of different ways to do so. "
"Contributing to ports is an excellent way to help <quote>give back</quote> "
"something to the project. Whether you are looking for an ongoing role, or a "
"fun challenge for a rainy day, we would love to have your help!"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:246
msgid ""
"There are a number of easy ways you can contribute to keeping the ports tree "
"up to date and in good working order:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:252
msgid ""
"Find some cool or useful software and <link xlink:href=\"@@URL_RELPREFIX@@/"
"doc/en_US.ISO8859-1/books/porters-handbook\">create a port</link> for it."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:258
msgid ""
"There are a large number of ports that have no maintainer. Become a "
"maintainer and <link linkend=\"adopt-port\">adopt a port</link>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:264
msgid ""
"If you have created or adopted a port, be aware of <link linkend=\"maintain-"
"port\">what you need to do as a maintainer</link>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:270
msgid ""
"When you are looking for a quick challenge you could <link linkend=\"fix-"
"broken\">fix a bug or a broken port</link>."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:278
msgid "Pick one of the items from the Ideas page"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:280
msgid ""
"The <link xlink:href=\"https://wiki.freebsd.org/IdeasPage\">FreeBSD list of "
"projects and ideas for volunteers</link> is also available for people "
"willing to contribute to the FreeBSD project. The list is being regularly "
"updated and contains items for both programmers and non-programmers with "
"information about each project."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:290
msgid "How to Contribute"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:292
msgid ""
"Contributions to the system generally fall into one or more of the following "
"5 categories:"
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:296
msgid "Bug Reports and General Commentary"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:298
msgid ""
"An idea or suggestion of <emphasis>general</emphasis> technical interest "
"should be mailed to the <link xlink:href=\"http://lists.FreeBSD.org/mailman/"
"listinfo/freebsd-hackers\">FreeBSD technical discussions mailing list</link>."
" Likewise, people with an interest in such things (and a tolerance for a "
"<emphasis>high</emphasis> volume of mail!) may subscribe to the <link xlink:"
"href=\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-hackers\">FreeBSD "
"technical discussions mailing list</link>. See <link xlink:href="
"\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/eresources."
"html#ERESOURCES-MAIL\">The FreeBSD Handbook</link> for more information "
"about this and other mailing lists."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:306
msgid ""
"If you find a bug or are submitting a specific change, please report it "
"using the <link xlink:href=\"https://bugs.FreeBSD.org/submit/\">bug "
"submission form</link>. Try to fill-in each field of the bug report. Unless "
"they exceed 65KB, include any patches directly in the report. If the patch "
"is suitable to be applied to the source tree put <literal>[PATCH]</literal> "
"in the synopsis of the report. When including patches, <emphasis>do not</"
"emphasis> use cut-and-paste because cut-and-paste turns tabs into spaces and "
"makes them unusable. When patches are a lot larger than 20KB, consider "
"compressing them (eg. with <citerefentry><refentrytitle>gzip</"
"refentrytitle><manvolnum>1</manvolnum></citerefentry> or "
"<citerefentry><refentrytitle>bzip2</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry>) prior to uploading them."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:319
msgid ""
"After filing a report, you should receive confirmation along with a tracking "
"number. Keep this tracking number so that you can update us with details "
"about the problem."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:323
msgid ""
"See also <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/"
"problem-reports/article.html\">this article</link> on how to write good "
"problem reports."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:329
msgid "Changes to the Documentation"
msgstr ""

#. (itstool) path: sect2/indexterm
#: article.translate.xml:331
msgid "<primary>documentation submissions</primary>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:335
msgid ""
"Changes to the documentation are overseen by the <link xlink:href=\"http://"
"lists.FreeBSD.org/mailman/listinfo/freebsd-doc\">FreeBSD documentation "
"project mailing list</link>. Please look at the <link xlink:href="
"\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/fdp-primer/index."
"html\">FreeBSD Documentation Project Primer</link> for complete instructions."
" Send submissions and changes (even small ones are welcome!) using the same "
"method any other bug report."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:345
msgid "Changes to Existing Source Code"
msgstr ""

#. (itstool) path: sect2/indexterm
#: article.translate.xml:347
msgid "<primary>FreeBSD-CURRENT</primary>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:349
msgid ""
"An addition or change to the existing source code is a somewhat trickier "
"affair and depends a lot on how far out of date you are with the current "
"state of FreeBSD development. There is a special on-going release of FreeBSD "
"known as <quote>FreeBSD-CURRENT</quote> which is made available in a variety "
"of ways for the convenience of developers working actively on the system. "
"See <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/"
"current-stable.html\">The FreeBSD Handbook</link> for more information about "
"getting and using FreeBSD-CURRENT."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:359
msgid ""
"Working from older sources unfortunately means that your changes may "
"sometimes be too obsolete or too divergent for easy re-integration into "
"FreeBSD. Chances of this can be minimized somewhat by subscribing to the "
"<link xlink:href=\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-"
"announce\">FreeBSD announcements mailing list</link> and the <link xlink:"
"href=\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-current\">FreeBSD-"
"CURRENT mailing list</link> lists, where discussions on the current state of "
"the system take place."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:366
msgid ""
"Assuming that you can manage to secure fairly up-to-date sources to base "
"your changes on, the next step is to produce a set of diffs to send to the "
"FreeBSD maintainers. This is done with the "
"<citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry> command."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:371
msgid ""
"The preferred <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</"
"manvolnum></citerefentry> format for submitting patches is the unified "
"output format generated by <command>diff -u</command>."
msgstr ""

#. (itstool) path: sect2/indexterm
#: article.translate.xml:375
msgid "<primary><command>diff</command></primary>"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:379
#, no-wrap
msgid "<prompt>%</prompt> <userinput>diff -u oldfile newfile</userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:381
msgid "or"
msgstr ""

#. (itstool) path: sect2/screen
#: article.translate.xml:383
#, no-wrap
msgid "<prompt>%</prompt> <userinput>diff -u -r -N olddir newdir</userinput>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:385
msgid ""
"would generate a set of unified diffs for the given source file or directory "
"hierarchy."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:388
msgid ""
"See <citerefentry><refentrytitle>diff</refentrytitle><manvolnum>1</"
"manvolnum></citerefentry> for more information."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:390
msgid ""
"Once you have a set of diffs (which you may test with the "
"<citerefentry><refentrytitle>patch</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry> command), you should submit them for inclusion with FreeBSD as "
"a bug report. <emphasis>Do not</emphasis> just send the diffs to the <link "
"xlink:href=\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-"
"hackers\">FreeBSD technical discussions mailing list</link> or they will get "
"lost! We greatly appreciate your submission (this is a volunteer project!); "
"because we are busy, we may not be able to address it immediately, but it "
"will remain in the PR database until we do. Indicate your submission by "
"including <literal>[PATCH]</literal> in the synopsis of the report."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:402
msgid ""
"If you feel it appropriate (e.g. you have added, deleted, or renamed files), "
"bundle your changes into a <command>tar</command> file. Archives created "
"with <citerefentry><refentrytitle>shar</refentrytitle><manvolnum>1</"
"manvolnum></citerefentry> are also welcome."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:408
msgid ""
"If your change is of a potentially sensitive nature, such as if you are "
"unsure of copyright issues governing its further distribution then you "
"should send it to Core Team <email>core@FreeBSD.org</email> directly rather "
"than submitting as a bug report. The Core Team <email>core@FreeBSD.org</"
"email> reaches a much smaller group of people who do much of the day-to-day "
"work on FreeBSD. Note that this group is also <emphasis>very busy</emphasis> "
"and so you should only send mail to them where it is truly necessary."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:417
msgid ""
"Please refer to <citerefentry><refentrytitle>intro</"
"refentrytitle><manvolnum>9</manvolnum></citerefentry> and "
"<citerefentry><refentrytitle>style</refentrytitle><manvolnum>9</manvolnum></"
"citerefentry> for some information on coding style. We would appreciate it "
"if you were at least aware of this information before submitting code."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:424
msgid "New Code or Major Value-Added Packages"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:426
msgid ""
"In the case of a significant contribution of a large body work, or the "
"addition of an important new feature to FreeBSD, it becomes almost always "
"necessary to either send changes as tar files or upload them to a web or FTP "
"site for other people to access. If you do not have access to a web or FTP "
"site, ask on an appropriate FreeBSD mailing list for someone to host the "
"changes for you."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:434
msgid ""
"When working with large amounts of code, the touchy subject of copyrights "
"also invariably comes up. FreeBSD prefers free software licenses such as BSD "
"or ISC. Copyleft licenses such as GPLv2 are sometimes permitted. The "
"complete listing can be found on the <link xlink:href=\"@@URL_RELPREFIX@@/"
"internal/software-license.html\">core team licensing policy</link> page."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:443
msgid "Money or Hardware"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:445
msgid ""
"We are always very happy to accept donations to further the cause of the "
"FreeBSD Project and, in a volunteer effort like ours, a little can go a long "
"way! Donations of hardware are also very important to expanding our list of "
"supported peripherals since we generally lack the funds to buy such items "
"ourselves."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:453
msgid "Donating Funds"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:455
msgid ""
"The FreeBSD Foundation is a non-profit, tax-exempt foundation established to "
"further the goals of the FreeBSD Project. As a 501(c)3 entity, the "
"Foundation is generally exempt from US federal income tax as well as "
"Colorado State income tax. Donations to a tax-exempt entity are often "
"deductible from taxable federal income."
msgstr ""

#. (itstool) path: para/address
#: article.translate.xml:463
#, no-wrap
msgid ""
"\n"
"	    The FreeBSD Foundation\n"
"	    <street>P.O. Box 20247</street>,\n"
"	    <city>Boulder</city>,\n"
"	    <state>CO</state> <postcode>80308</postcode>\n"
"	    <country>USA</country>\n"
"	  "
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:462
msgid "Donations may be sent in check form to: <_:address-1/>"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:471
msgid ""
"The FreeBSD Foundation is now able to accept donations through the web with "
"PayPal. To place a donation, please visit the Foundation <link xlink:href="
"\"https://www.freebsdfoundation.org\">web site</link>."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:477
msgid ""
"More information about the FreeBSD Foundation can be found in <link xlink:"
"href=\"https://people.FreeBSD.org/~jdp/foundation/announcement.html\">The "
"FreeBSD Foundation -- an Introduction</link>. To contact the Foundation by "
"email, write to <email>info@FreeBSDFoundation.org</email>."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:485
msgid "Donating Hardware"
msgstr ""

#. (itstool) path: sect3/indexterm
#: article.translate.xml:487
msgid "<primary>donations</primary>"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:489
msgid ""
"The FreeBSD Project happily accepts donations of hardware that it can find "
"good use for. If you are interested in donating hardware, please contact the "
"<link xlink:href=\"@@URL_RELPREFIX@@/donations/\">Donations Liaison Office</"
"link>."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:499
msgid "Contributing to ports"
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:502
msgid "Adopting an unmaintained port"
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:505
msgid "Choosing an unmaintained port"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:507
msgid ""
"Taking over maintainership of ports that are unmaintained is a great way to "
"get involved. Unmaintained ports are only updated and fixed when somebody "
"volunteers to work on them. There are a large number of unmaintained ports. "
"It is a good idea to start with adopting a port that you use regularly."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:514
msgid ""
"Unmaintained ports have their <varname>MAINTAINER</varname> set to "
"<literal>ports@FreeBSD.org</literal>. A list of unmaintained ports and their "
"current errors and problem reports can be seen at the <link xlink:href="
"\"http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py?maintainer="
"ports%40FreeBSD.org\">FreeBSD Ports Monitoring System</link>."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:521
msgid ""
"Some ports affect a large number of others due to dependencies and slave "
"port relationships. Generally, we want people to have some experience before "
"they maintain such ports."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:526
msgid ""
"You can find out whether or not a port has dependencies or slave ports by "
"looking at a master index of ports called <filename>INDEX</filename>. (The "
"name of the file varies by release of FreeBSD; for instance, <filename>INDEX-"
"8</filename>.) Some ports have conditional dependencies that are not "
"included in a default <filename>INDEX</filename> build. We expect you to be "
"able to recognize such ports by looking through other ports' "
"<filename>Makefile</filename>s."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:538
msgid "How to adopt the port"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:540
msgid ""
"First make sure you understand your <link linkend=\"maintain-"
"port\">responsibilities as a maintainer</link>. Also read the <link xlink:"
"href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-"
"handbook\">Porter's Handbook</link>. <emphasis>Please do not commit yourself "
"to more than you feel you can comfortably handle.</emphasis>"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:548
msgid ""
"You may request maintainership of any unmaintained port as soon as you wish. "
"Simply set <varname>MAINTAINER</varname> to your own email address and send "
"a PR (Problem Report) with the change. If the port has build errors or needs "
"updating, you may wish to include any other changes in the same PR. This "
"will help because many committers are less willing to assign maintainership "
"to someone who does not have a known track record with FreeBSD. Submitting "
"PRs that fix build errors or update ports are the best ways to establish one."
""
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:558
msgid ""
"File your PR with category <literal>ports</literal> and class "
"<literal>change-request</literal>. A committer will examine your PR, commit "
"the changes, and finally close the PR. Sometimes this process can take a "
"little while (committers are volunteers, too :)."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:567
msgid "The challenge for port maintainers"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:569
msgid ""
"This section will give you an idea of why ports need to be maintained and "
"outline the responsibilities of a port maintainer."
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:574
msgid "Why ports require maintenance"
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:576
msgid ""
"Creating a port is a once-off task. Ensuring that a port is up to date and "
"continues to build and run requires an ongoing maintenance effort. "
"Maintainers are the people who dedicate some of their time to meeting these "
"goals."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:581
msgid ""
"The foremost reason ports need maintenance is to bring the latest and "
"greatest in third party software to the FreeBSD community. An additional "
"challenge is to keep individual ports working within the Ports Collection "
"framework as it evolves."
msgstr ""

#. (itstool) path: sect3/para
#: article.translate.xml:587
msgid "As a maintainer, you will need to manage the following challenges:"
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:593
msgid "New software versions and updates."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:595
msgid ""
"New versions and updates of existing ported software become available all "
"the time, and these need to be incorporated into the Ports Collection in "
"order to provide up-to-date software."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:604
msgid "Changes to dependencies."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:606
msgid ""
"If significant changes are made to the dependencies of your port, it may "
"need to be updated so that it will continue to work correctly."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:614
msgid "Changes affecting dependent ports."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:616
msgid ""
"If other ports depend on a port that you maintain, changes to your port may "
"require coordination with other maintainers."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:624
msgid "Interaction with other users, maintainers and developers."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:627
msgid ""
"Part of being a maintainer is taking on a support role. You are not expected "
"to provide general support (but we welcome it if you choose to do so). What "
"you should provide is a point of coordination for FreeBSD-specific issues "
"regarding your ports."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:637
msgid "Bug hunting."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:639
msgid ""
"A port may be affected by bugs which are specific to FreeBSD. You will need "
"to investigate, find, and fix these bugs when they are reported. Thoroughly "
"testing a port to identify problems before they make their way into the "
"Ports Collection is even better."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:649
msgid "Changes to ports infrastructure and policy."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:651
msgid ""
"Occasionally the systems that are used to build ports and packages are "
"updated or a new recommendation affecting the infrastructure is made. You "
"should be aware of these changes in case your ports are affected and require "
"updating."
msgstr ""

#. (itstool) path: formalpara/title
#: article.translate.xml:661
msgid "Changes to the base system."
msgstr ""

#. (itstool) path: formalpara/para
#: article.translate.xml:663
msgid ""
"FreeBSD is under constant development. Changes to software, libraries, the "
"kernel or even policy changes can cause flow-on change requirements to ports."
""
msgstr ""

#. (itstool) path: sect3/title
#: article.translate.xml:672
msgid "Maintainer responsibilities"
msgstr ""

#. (itstool) path: sect4/title
#: article.translate.xml:675
msgid "Keep your ports up to date"
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:677
msgid ""
"This section outlines the process to follow to keep your ports up to date."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:680
msgid ""
"This is an overview. More information about upgrading a port is available in "
"the <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-"
"handbook\"> Porter's Handbook</link>."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:687
msgid "Watch for updates"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:689
msgid ""
"Monitor the upstream vendor for new versions, updates and security fixes for "
"the software. Announcement mailing lists or news web pages are useful for "
"doing this. Sometimes users will contact you and ask when your port will be "
"updated. If you are busy with other things or for any reason just cannot "
"update it at the moment, ask if they will help you by submitting an update."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:698
msgid ""
"You may also receive automated email from the <literal>FreeBSD Ports Version "
"Check</literal> informing you that a newer version of your port's distfile "
"is available. More information about that system (including how to stop "
"future emails) will be provided in the message."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:707
msgid "Incorporate changes"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:709
msgid ""
"When they become available, incorporate the changes into the port. You need "
"to be able to generate a patch between the original port and your updated "
"port."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:715
msgid "Review and test"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:717
msgid "Thoroughly review and test your changes:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:721
msgid ""
"Build, install and test your port on as many platforms and architectures as "
"you can. It is common for a port to work on one branch or platform and fail "
"on another."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:728
msgid ""
"Make sure your port's dependencies are complete. The recommended way of "
"doing this is by installing your own ports <application>tinderbox</"
"application>. See <link linkend=\"resources\">resources</link> for more "
"information."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:736
msgid ""
"Check that the packing list is up to date. This involves adding in any new "
"files and directories and removing unused entries."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:742
msgid ""
"Verify your port using <citerefentry vendor="
"\"ports\"><refentrytitle>portlint</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry> as a guide. See <link linkend=\"resources\">resources</link> "
"for important information about using <application>portlint</application>."
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:749
msgid ""
"Consider whether changes to your port might cause any other ports to break. "
"If this is the case, coordinate the changes with the maintainers of those "
"ports. This is especially important if your update changes the shared "
"library version; in this case, at the very least, the dependent ports will "
"need to get a <varname>PORTREVISION</varname> bump so that they will "
"automatically be upgraded by automated tools such as "
"<application>portmaster</application> or <citerefentry vendor="
"\"ports\"><refentrytitle>portupgrade</refentrytitle><manvolnum>1</"
"manvolnum></citerefentry>."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:765 article.translate.xml:915
msgid "Submit changes"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:767
msgid ""
"Send your update by submitting a PR with an explanation of the changes and a "
"patch containing the differences between the original port and the updated "
"one. Please refer to <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-"
"1/articles/problem-reports\">Writing FreeBSD Problem Reports</link> for "
"information on how to write a really good PR."
msgstr ""

#. (itstool) path: note/para
#: article.translate.xml:775
msgid ""
"Please do not submit a <citerefentry><refentrytitle>shar</"
"refentrytitle><manvolnum>1</manvolnum></citerefentry> archive of the entire "
"port; instead, use <citerefentry><refentrytitle>diff</"
"refentrytitle><manvolnum>1</manvolnum></citerefentry> <literal>-ruN</"
"literal>. In this way, committers can much more easily see exactly what "
"changes are being made. The Porter's Handbook section on <link xlink:href="
"\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-handbook/port-"
"upgrading.html\">Upgrading</link> has more information."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:785
msgid "Wait"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:787
msgid ""
"At some stage a committer will deal with your PR. It may take minutes, or it "
"may take weeks — so please be patient."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:793
msgid "Give feedback"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:795
msgid ""
"If a committer finds a problem with your changes, they will most likely "
"refer it back to you. A prompt response will help get your PR committed "
"faster, and is better for maintaining a thread of conversation when trying "
"to resolve any problems."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:803
msgid "And Finally"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:805
msgid ""
"Your changes will be committed and your port will have been updated. The PR "
"will then be closed by the committer. That's it!"
msgstr ""

#. (itstool) path: sect4/title
#: article.translate.xml:813
msgid "Ensure your ports continue to build correctly"
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:815
msgid ""
"This section is about discovering and fixing problems that stop your ports "
"from building correctly."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:818
msgid ""
"FreeBSD only guarantees that the Ports Collection works on the <literal>-"
"STABLE</literal> branches. In theory, you should be able to get by with "
"running the latest release of each stable branch (since the ABIs are not "
"supposed to change) but if you can run the branch, that is even better."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:826
msgid ""
"Since the majority of FreeBSD installations run on PC-compatible machines "
"(what is termed the <literal>i386</literal> architecture), we expect you to "
"keep the port working on that architecture. We prefer that ports also work "
"on the <literal>amd64</literal> architecture running native. It is "
"completely fair to ask for help if you do not have one of these machines."
msgstr ""

#. (itstool) path: note/para
#: article.translate.xml:835
msgid ""
"The usual failure modes for non-<literal>x86</literal> machines are that the "
"original programmers assumed that, for instance, pointers are <literal>int</"
"literal>s, or that a relatively lax older <application>gcc</application> "
"compiler was being used. More and more, application authors are reworking "
"their code to remove these assumptions — but if the author is not actively "
"maintaining their code, you may need to do this yourself."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:846
msgid ""
"These are the tasks you need to perform to ensure your port is able to be "
"built:"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:851
msgid "Watch for build failures"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:853
msgid ""
"Check your mail for mail from <literal>pkg-fallout@FreeBSD.org</literal> and "
"the <link xlink:href=\"http://portscout.FreeBSD.org\">distfiles scanner</"
"link> to see if any of the port which are failing to build are out of date."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:861 article.translate.xml:977
msgid "Collect information"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:863
msgid ""
"Once you are aware of a problem, collect information to help you fix it. "
"Build errors reported by <literal>pkg-fallout</literal> are accompanied by "
"logs which will show you where the build failed. If the failure was reported "
"to you by a user, ask them to send you information which may help in "
"diagnosing the problem, such as:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:873
msgid "Build logs"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:877
msgid ""
"The commands and options used to build the port (including options set in "
"<filename>/etc/make.conf</filename>)"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:883
msgid ""
"A list of packages installed on their system as shown by "
"<citerefentry><refentrytitle>pkg-info</refentrytitle><manvolnum>8</"
"manvolnum></citerefentry>"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:888
msgid ""
"The version of FreeBSD they are running as shown by "
"<citerefentry><refentrytitle>uname</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry><command> -a</command>"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:893
msgid "When their ports collection was last updated"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:898
msgid "When their ports tree and <filename>INDEX</filename> was last updated"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:905
msgid "Investigate and find a solution"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:907
msgid ""
"Unfortunately there is no straightforward process to follow to do this. "
"Remember, though: if you are stuck, ask for help! The <link xlink:href="
"\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports\">FreeBSD ports "
"mailing list</link> is a good place to start, and the upstream developers "
"are often very helpful."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:917
msgid ""
"Just as with updating a port, you should now incorporate changes, review and "
"test, submit your changes in a PR, and provide feedback if required."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:924
msgid "Send patches to upstream authors"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:926
msgid ""
"In some cases, you will have to make patches to the port to make it run on "
"FreeBSD. Some (but not all) upstream authors will accept such patches back "
"into their code for the next release. If so, this may even help their users "
"on other BSD-based systems as well and perhaps save duplicated effort. "
"Please consider sending any applicable patches to the authors as a courtesy."
msgstr ""

#. (itstool) path: sect4/title
#: article.translate.xml:940
msgid "Investigate bug reports and PRs related to your port"
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:943
msgid "This section is about discovering and fixing bugs."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:946
msgid ""
"FreeBSD-specific bugs are generally caused by assumptions about the build "
"and runtime environments that do not apply to FreeBSD. You are less likely "
"to encounter a problem of this type, but it can be more subtle and difficult "
"to diagnose."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:952
msgid ""
"These are the tasks you need to perform to ensure your port continues to "
"work as intended:"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:957
msgid "Respond to bug reports"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:959
msgid ""
"Bugs may be reported to you through email via the <link xlink:href=\"https://"
"bugs.FreeBSD.org/search/\"> Problem Report database</link>. Bugs may also be "
"reported directly to you by users."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:964
msgid ""
"You should respond to PRs and other reports within 14 days, but please try "
"not to take that long. Try to respond as soon as possible, even if it is "
"just to say you need some more time before you can work on the PR."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:970
msgid ""
"If you have not responded after 14 days, any committer may commit from a PR "
"that you have not responded to via a <literal>maintainer-timeout</literal>."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:979
msgid ""
"If the person reporting the bug has not also provided a fix, you need to "
"collect the information that will allow you to generate one."
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:983
msgid ""
"If the bug is reproducible, you can collect most of the required information "
"yourself. If not, ask the person who reported the bug to collect the "
"information for you, such as:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:990
msgid ""
"A detailed description of their actions, expected program behavior and "
"actual behavior"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:995
msgid "Copies of input data used to trigger the bug"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1000
msgid ""
"Information about their build and execution environment — for example, a "
"list of installed packages and the output of "
"<citerefentry><refentrytitle>env</refentrytitle><manvolnum>1</manvolnum></"
"citerefentry>"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1006
msgid "Core dumps"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1010
msgid "Stack traces"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:1016
msgid "Eliminate incorrect reports"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1018
msgid ""
"Some bug reports may be incorrect. For example, the user may have simply "
"misused the program; or their installed packages may be out of date and "
"require updating. Sometimes a reported bug is not specific to FreeBSD. In "
"this case report the bug to the upstream developers. If the bug is within "
"your capabilities to fix, you can also patch the port so that the fix is "
"applied before the next upstream release."
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:1029
msgid "Find a solution"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1031
msgid ""
"As with build errors, you will need to sort out a fix to the problem. Again, "
"remember to ask if you are stuck!"
msgstr ""

#. (itstool) path: step/title
#: article.translate.xml:1037
msgid "Submit or approve changes"
msgstr ""

#. (itstool) path: step/para
#: article.translate.xml:1039
msgid ""
"Just as with updating a port, you should now incorporate changes, review and "
"test, and submit your changes in a PR (or send a follow-up if a PR already "
"exists for the problem). If another user has submitted changes in the PR, "
"you can also send a follow-up saying whether or not you approve the changes."
msgstr ""

#. (itstool) path: sect4/title
#: article.translate.xml:1050
msgid "Providing support"
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:1052
msgid ""
"Part of being a maintainer is providing support — not for the software in "
"general — but for the port and any FreeBSD-specific quirks and problems. "
"Users may contact you with questions, suggestions, problems and patches. "
"Most of the time their correspondence will be specific to FreeBSD."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:1059
msgid ""
"Occasionally you may have to invoke your skills in diplomacy, and kindly "
"point users seeking general support to the appropriate resources. Less "
"frequently you will encounter a person asking why the <literal>RPM</"
"literal>s are not up to date or how can they get the software to run under "
"Foo Linux. Take the opportunity to tell them that your port is up to date "
"(if it is, of course!), and suggest that they try FreeBSD."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:1068
msgid ""
"Sometimes users and developers will decide that you are a busy person whose "
"time is valuable and do some of the work for you. For example, they might:"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1074
msgid "submit a PR or send you patches to update your port,"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1079
msgid "investigate and perhaps provide a fix to a PR, or"
msgstr ""

#. (itstool) path: listitem/para
#: article.translate.xml:1084
msgid "otherwise submit changes to your port."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:1088
msgid ""
"In these cases your main obligation is to respond in a timely manner. Again, "
"the timeout for non-responsive maintainers is 14 days. After this period "
"changes may be committed unapproved. They have taken the trouble to do this "
"for you; so please try to at least respond promptly. Then review, approve, "
"modify or discuss their changes with them as soon as possible."
msgstr ""

#. (itstool) path: sect4/para
#: article.translate.xml:1096
msgid ""
"If you can make them feel that their contribution is appreciated (and it "
"should be) you will have a better chance persuading them to do more things "
"for you in the future :-)."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:1105
msgid "Finding and fixing a broken port"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1107
msgid ""
"There are two really good places to find a port that needs some attention."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1110
msgid ""
"You can use the <link xlink:href=\"https://bugs.freebsd.org/search\">web "
"interface</link> to the Problem Report database to search through and view "
"unresolved PRs. The majority of ports PRs are updates, but with a little "
"searching and skimming over synopses you should be able to find something "
"interesting to work on (the <literal>sw-bug</literal> class is a good place "
"to start)."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1118
msgid ""
"The other place is the <link xlink:href=\"http://portsmon.FreeBSD.org/"
"\">FreeBSD Ports Monitoring System</link>. In particular look for "
"unmaintained ports with build errors and ports that are marked "
"<varname>BROKEN</varname>. It is OK to send changes for a maintained port as "
"well, but remember to ask the maintainer in case they are already working on "
"the problem."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1125
msgid ""
"Once you have found a bug or problem, collect information, investigate and "
"fix! If there is an existing PR, follow up to that. Otherwise create a new "
"PR. Your changes will be reviewed and, if everything checks out, committed."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:1132
msgid "When to call it quits"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1134
msgid ""
"As your interests and commitments change, you may find that you no longer "
"have time to continue some (or all) of your ports contributions. That is "
"fine! Please let us know if you are no longer using a port or have otherwise "
"lost time or interest in being a maintainer. In this way we can go ahead and "
"allow other people to try to work on existing problems with the port without "
"waiting for your response. Remember, FreeBSD is a volunteer project, so if "
"maintaining a port is no fun any more, it is probably time to let someone "
"else do it!"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1144
msgid ""
"In any case, the Ports Management Team (<literal>portmgr</literal>) reserves "
"the right to reset your maintainership if you have not actively maintained "
"your port in some time. (Currently, this is set to 3 months.) By this, we "
"mean that there are unresolved problems or pending updates that have not "
"been worked on during that time."
msgstr ""

#. (itstool) path: sect2/title
#: article.translate.xml:1153
msgid "Resources for ports maintainers and contributors"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1155
msgid ""
"The <link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/porters-"
"handbook\">Porter's Handbook</link> is your hitchhiker's guide to the ports "
"system. Keep it handy!"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1159
msgid ""
"<link xlink:href=\"@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/articles/problem-"
"reports\">Writing FreeBSD Problem Reports</link> describes how to best "
"formulate and submit a PR. In 2005 more than eleven thousand ports PRs were "
"submitted! Following this article will greatly assist us in reducing the "
"time needed to handle your PRs."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1165
msgid ""
"The <link xlink:href=\"https://bugs.freebsd.org/bugzilla/query.cgi\"> "
"Problem Report database</link>."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1168
msgid ""
"The <link xlink:href=\"http://portsmon.FreeBSD.org/\">FreeBSD Ports "
"Monitoring System</link> can show you cross-referenced information about "
"ports such as build errors and problem reports. If you are a maintainer you "
"can use it to check on the build status of your ports. As a contributor you "
"can use it to find broken and unmaintained ports that need to be fixed."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1175
msgid ""
"The <link xlink:href=\"http://portscout.FreeBSD.org\">FreeBSD Ports distfile "
"scanner</link> can show you ports for which the distfiles are not fetchable. "
"You can check on your own ports or use it to find ports that need their "
"<varname>MASTER_SITES</varname> updated."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1181
msgid ""
"<package>ports-mgmt/poudriere</package> is the most thorough way to test a "
"port through the entire cycle of installation, packaging, and deinstallation."
" Documentation is located at the <link xlink:href=\"https://github.com/"
"freebsd/poudriere\"> poudriere github repository</link>"
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1188
msgid ""
"<citerefentry vendor=\"ports\"><refentrytitle>portlint</"
"refentrytitle><manvolnum>1</manvolnum></citerefentry> is an application "
"which can be used to verify that your port conforms to many important "
"stylistic and functional guidelines. <application>portlint</application> is "
"a simple heuristic application, so you should use it <emphasis>only as a "
"guide</emphasis>. If <application>portlint</application> suggests changes "
"which seem unreasonable, consult the <link xlink:href=\"@@URL_RELPREFIX@@/"
"doc/en_US.ISO8859-1/books/porters-handbook\">Porter's Handbook</link> or ask "
"for advice."
msgstr ""

#. (itstool) path: sect2/para
#: article.translate.xml:1197
msgid ""
"The <link xlink:href=\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-"
"ports\">FreeBSD ports mailing list</link> is for general ports-related "
"discussion. It is a good place to ask for help. You can <link xlink:href="
"\"https://lists.freebsd.org/mailman/listinfo\">subscribe, or read and search "
"the list archives</link>. Reading the archives of the <link xlink:href="
"\"http://lists.FreeBSD.org/mailman/listinfo/freebsd-ports-bugs\">FreeBSD "
"ports bugs mailing list</link> and the <link xlink:href=\"http://lists."
"FreeBSD.org/mailman/listinfo/svn-ports-head\">SVN commit messages for the "
"ports tree for head/</link> may also be of interest."
msgstr ""

#. (itstool) path: sect1/title
#: article.translate.xml:1206
msgid "Getting Started in Other Areas"
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:1208
msgid ""
"Looking for something interesting to get started that is not mentioned "
"elsewhere in this article? The FreeBSD Project has several Wiki pages "
"containing areas within which new contributors can get ideas on how to get "
"started."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:1213
msgid ""
"The <link xlink:href=\"https://wiki.freebsd.org/JuniorJobs\">Junior Jobs</"
"link> page has a list of projects that might be of interest to people just "
"getting started in FreeBSD, and want to work on interesting things to get "
"their feet wet."
msgstr ""

#. (itstool) path: sect1/para
#: article.translate.xml:1218
msgid ""
"The <link xlink:href=\"https://wiki.freebsd.org/IdeasPage\">Ideas Page</"
"link> contains various \"nice to have\" or \"interesting\" things to work on "
"in the Project."
msgstr ""