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

Source string Read only

(itstool) path: sect2/indexterm
Context English State
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.
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.
Ongoing Programmer Tasks
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>.
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.
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.
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.
Move contributed software to <filename>src/contrib</filename> in the source tree.
Make sure code in <filename>src/contrib</filename> is up to date.
Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. A list of build warnings can also be found from our <link xlink:href="https://ci.freebsd.org">CI</link> by selecting a build and checking "LLVM/Clang Warnings".
Fix warnings for ports which do deprecated things like using <function>gets()</function> or including <filename>malloc.h</filename>.
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).
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.
Suggest further tasks for this list!
Work through the PR Database
<primary>problem reports database</primary>
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.
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.
Ongoing Ports Tasks
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.
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!
There are a number of easy ways you can contribute to keeping the ports tree up to date and in good working order:
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.
There are a large number of ports that have no maintainer. Become a maintainer and <link linkend="adopt-port">adopt a port</link>.
If you have created or adopted a port, be aware of <link linkend="maintain-port">what you need to do as a maintainer</link>.
When you are looking for a quick challenge you could <link linkend="fix-broken">fix a bug or a broken port</link>.
Pick one of the items from the Ideas page
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.
How to Contribute
Contributions to the system generally fall into one or more of the following 5 categories:
Bug Reports and General Commentary

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: sect2/indexterm
Flags
read-only
Source string location
article.translate.xml:211
String age
a year ago
Source string age
a year ago
Translation file
articles/contributing.pot, string 37