Path: blob/main/documentation/content/en/articles/contributing/_index.po
18096 views
# SOME DESCRIPTIVE TITLE # Copyright (C) YEAR The FreeBSD Project # This file is distributed under the same license as the FreeBSD Documentation package. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: FreeBSD Documentation VERSION\n" "POT-Creation-Date: 2026-02-22 15:58+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <[email protected]>\n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: YAML Front Matter: description #: documentation/content/en/articles/contributing/_index.adoc:1 #, no-wrap msgid "How to contribute to the FreeBSD Project" msgstr "" #. type: Title = #: documentation/content/en/articles/contributing/_index.adoc:1 #: documentation/content/en/articles/contributing/_index.adoc:13 #, no-wrap msgid "Contributing to FreeBSD" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:45 msgid "pass:[<!-- vale FreeBSD.Pronouns = NO -->]" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:48 msgid "Abstract" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:50 msgid "" "This article describes the different ways in which an individual or " "organization may contribute to the FreeBSD Project." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:52 msgid "'''" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:59 msgid "" "So you want to contribute to FreeBSD? That is great! FreeBSD _relies_ on the " "contributions of its user base to survive. Your contributions are not only " "appreciated, they are vital to FreeBSD's continued growth." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:62 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:66 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:70 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# 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:78 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 "" #. type: Title == #: documentation/content/en/articles/contributing/_index.adoc:80 #, no-wrap msgid "What Is Needed" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:83 msgid "" "The following list of tasks and sub-projects represents something of an " "amalgam of various [.filename]#TODO# lists and user requests." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:85 #, no-wrap msgid "Ongoing Non-Programmer Tasks" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:90 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:94 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 (AsciiDoc is not difficult to learn, but there is no objection " "to plain text submissions)." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:100 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 extref:{fdp-primer}" "translations[Translations FAQ, translations] 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:103 msgid "" "Read the {freebsd-questions} 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:105 #, no-wrap msgid "Ongoing Programmer Tasks" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:109 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 \"weekend hackers\"." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:111 msgid "" "If you run FreeBSD-CURRENT and have a good Internet connection, there is a " "machine `current.FreeBSD.org` 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:114 msgid "" "Learn about changes or problems that have already been proposed. 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:115 msgid "" "One way is to read the {freebsd-bugs} (for issues submitted through " "Bugzilla)." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:116 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:117 msgid "" "Move contributed software to [.filename]#src/contrib# in the source tree." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:118 msgid "Make sure code in [.filename]#src/contrib# is up to date." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:120 msgid "" "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 " "https://ci.freebsd.org[CI] by selecting a build and checking \"LLVM/Clang " "Warnings\"." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:121 msgid "" "Fix warnings for ports which do deprecated things like using `gets()` or " "including [.filename]#malloc.h#." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:122 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:127 msgid "" "Get copies of formal standards like POSIX(R). 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:128 msgid "Suggest further tasks for this list!" msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:129 #, no-wrap msgid "Work through the Bugzilla Problem Report Database" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:136 msgid "" "The https://bugs.FreeBSD.org/search/[FreeBSD Problem Report list] shows all " "the current active problem reports and requests for enhancement that have " "been submitted by FreeBSD users via Bugzilla. This 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 is a good one. Others might be much more complex, or might not " "even have a fix included at all." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:139 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:140 #, no-wrap msgid "Ongoing Ports Tasks" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:145 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:149 msgid "" "Anyone can get involved, and there are lots of different ways to do so. " "Contributing to ports is an excellent way to help \"give back\" 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:151 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:153 msgid "" "Find some cool or useful software and extref:{porters-handbook}[create a " "port] for it." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:155 msgid "" "There are a large number of ports that have no maintainer. Become a " "maintainer and crossref:contributing[adopt-port, Adopting an unmaintained " "port]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:156 msgid "" "If you have created or adopted a port, be aware of " "crossref:contributing[maintain-port, The challenge for port maintainers]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:157 msgid "" "When you are looking for a quick challenge you could " "crossref:contributing[fix-broken, Finding and fixing a broken port]." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:158 #, no-wrap msgid "Pick one of the items from the Ideas page" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:162 msgid "" "The https://wiki.freebsd.org/IdeasPage[FreeBSD list of projects and ideas " "for volunteers] 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 "" #. type: Title == #: documentation/content/en/articles/contributing/_index.adoc:164 #, no-wrap msgid "How to Contribute" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:167 msgid "" "Contributions to the system generally fall into one or more of the following " "5 categories:" msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:169 #, no-wrap msgid "Bug Reports and General Commentary" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:174 msgid "" "An idea or suggestion of _general_ technical interest should be mailed to " "the {freebsd-hackers}. Likewise, people with an interest in such things " "(and a tolerance for a _high_ volume of mail!) may subscribe to the {freebsd-" "hackers}. See extref:{handbook}eresources[The FreeBSD Handbook, eresources-" "mail] for more information about this and other mailing lists." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:177 msgid "" "If you are submitting a simple patch to the src repo, please consider " "submitting it to the project's GitHub mirror as https://github.com/freebsd/" "freebsd-src/pulls[a pull request]. Suitable submissions should:" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:180 msgid "" "It is ready or nearly ready to be committed. A committer should be able to " "land this patch with less than 10 minutes of additional work." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:181 msgid "It passes all the GitHub CI jobs." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:182 msgid "You can respond to feedback quickly." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:184 msgid "" "It touches fewer than about 10 files and the changes are less than about 200 " "lines. Changes larger than this may be OK, or you may be asked to submit " "multiple pull requests of a more manageable size." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:186 msgid "" "Each logical change is a separate commit within the pull request. Commit " "messages for each change should follow extref:{committers-guide}#commit-log-" "message[commit log guide]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:188 msgid "" "All commits have your name and valid email address as you'd like to see them " "in the FreeBSD repository as the author. Fake github.com addresses cannot " "be used." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:190 msgid "" "The scope of the pull request should not change during review. If the " "review suggests changes that expand the scope, please create an independent " "pull request." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:192 msgid "" "Fixup commits should be squashed with the commit they are fixing. Each " "commit in your branch should be suitable for FreeBSD's repository." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:193 msgid "" "Commits should include one or more `Signed-off-by:` lines with full name and " "email address certifying https://developercertificate.org/[Developer " "Certificate of Origin]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:198 msgid "" "When updating pull request, please rebase with a forced push rather than a " "merge commit. More complex changes may be submitted as pull requests, but " "they may be closed if they are too large, too unwieldy, become inactive, " "need further discussion in the community, or need extensive revision. " "Please avoid creating large, wide-ranging cleanup patches: they are too " "large and lack the focus needed for a good review. Misdirected patches may " "be redirected to a more appropriate forum for the patch to be resolved." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:202 msgid "" "Pull requests submitted to the ports repository may or may not see action, " "based on the whims of developers. For now, you will have a better " "experience if you follow the ports submission process " "crossref:contributing[ports-contributing, Contributing to ports]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:204 msgid "" "The docs team also accepts pull requests via GitHub, but has not established " "any policy for them yet." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:211 msgid "" "If you find a bug or are submitting a specific change, please report it " "using the https://bugs.FreeBSD.org/submit/[Bugzilla bug submission form]. " "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 `[PATCH]` in the synopsis of the report. " "When including patches, _do not_ 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 (for example with man:gzip[1] or " "man:bzip2[1]) prior to uploading them." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:214 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:216 msgid "" "See also extref:{problem-reports}[this article] on how to write good problem " "reports." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:217 #, no-wrap msgid "Changes to the Documentation" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:222 msgid "" "Changes to the documentation are overseen by the {freebsd-doc}. Please look " "at the extref:{fdp-primer}[FreeBSD Documentation Project Primer] for " "complete instructions. Send submissions and changes (even small ones are " "welcome!) using the same method as any other bug report." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:223 #, no-wrap msgid "Changes to Existing Source Code" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:228 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 \"FreeBSD-CURRENT\" which is made available in a variety of " "ways for the convenience of developers working actively on the system. See " "extref:{handbook}cutting-edge[The FreeBSD Handbook, current-stable] for more " "information about getting and using FreeBSD-CURRENT." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:231 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 " "{freebsd-announce} and the {freebsd-current} lists, where discussions on the " "current state of the system take place." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:234 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 man:diff[1] command." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:236 msgid "" "The preferred man:diff[1] format for submitting patches is the unified " "output format generated by `diff -u`." msgstr "" #. type: delimited block . 4 #: documentation/content/en/articles/contributing/_index.adoc:240 #, no-wrap msgid "% diff -u oldfile newfile\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:243 msgid "or" msgstr "" #. type: delimited block . 4 #: documentation/content/en/articles/contributing/_index.adoc:247 #, no-wrap msgid "% diff -u -r -N olddir newdir\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:250 msgid "" "would generate a set of unified diffs for the given source file or directory " "hierarchy." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:252 msgid "See man:diff[1] for more information." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:256 msgid "" "Once you have a set of diffs (which you may test with the man:patch[1] " "command), you may submit them for inclusion with FreeBSD as a Bugzilla " "problem report. _Do not_ just send the diffs to the {freebsd-hackers} 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 `[PATCH]` in the synopsis of the report." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:258 msgid "" "If you feel it appropriate (for example you have added, deleted, or renamed " "files), bundle your changes into a `tar` file." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:262 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-email} directly rather than submitting as a bug " "report. The {core-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 _very busy_ " "and so you should only send mail to them where it is truly necessary." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:265 msgid "" "Please refer to man:intro[9] and man:style[9] for some information on coding " "style. We would appreciate it if you were at least aware of this " "information before submitting code." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:266 #, no-wrap msgid "New Code or Major Value-Added Packages" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:270 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:275 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:https://www.FreeBSD.org/internal/" "software-license/[core team licensing policy] page." msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:276 #, no-wrap msgid "Money or Hardware" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:280 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 "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:282 #, no-wrap msgid "Donating Funds" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:287 msgid "" "The https://www.freebsdfoundation.org[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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:289 msgid "Donations may be sent in check form to:" msgstr "" #. type: delimited block * 4 #: documentation/content/en/articles/contributing/_index.adoc:297 #, no-wrap msgid "" "The FreeBSD Foundation\n" "3980 Broadway Street\n" "STE #103-107\n" "Boulder CO 80304\n" "USA" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:300 msgid "" "The FreeBSD Foundation is also able to accept https://" "www.freebsdfoundation.org/donate/[online donations] through various payment " "options." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:303 msgid "" "More information about the FreeBSD Foundation can be found in https://" "people.FreeBSD.org/~jdp/foundation/announcement.html[The FreeBSD Foundation " "-- an Introduction]. To contact the Foundation by email, write to " "mailto:[email protected][[email protected]]." msgstr "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:304 #, no-wrap msgid "Donating Hardware" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:308 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:https://www.FreeBSD.org/donations/[Donations Liaison Office]." msgstr "" #. type: Title == #: documentation/content/en/articles/contributing/_index.adoc:310 #, no-wrap msgid "Contributing to ports" msgstr "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:313 #, no-wrap msgid "Adopting an unmaintained port" msgstr "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:315 #, no-wrap msgid "Choosing an unmaintained port" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:321 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:324 msgid "" "Unmaintained ports have their `MAINTAINER` set to `[email protected]`. Many " "unmaintained ports can have pending updates, this can be seen at the https://" "portscout.freebsd.org/[email protected][FreeBSD Ports distfile scanner]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:326 msgid "" "On https://portsfallout.com/fallout?" "port=&maintainer=ports%40FreeBSD.org[PortsFallout] can be seen a list of " "unmaintained ports with errors." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:329 msgid "" "Some ports affect a large number of others due to dependencies and secondary " "port relationships. Generally, we want people to have some experience " "before they maintain such ports." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:333 msgid "" "You can find out whether or not a port has dependencies or secondary ports " "by looking at a primary index of ports called [.filename]#INDEX#. (The name " "of the file varies by release of FreeBSD; for instance, " "[.filename]#INDEX-13#.) Some ports have conditional dependencies that are " "not included in a default [.filename]#INDEX# build. We expect you to be " "able to recognize such ports by looking through other ports' " "[.filename]#Makefile#'s." msgstr "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:334 #, no-wrap msgid "How to adopt the port" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:339 msgid "" "First make sure you understand your crossref:contributing[maintain-port, The " "challenge for port maintainers]. Also read the extref:{porters-handbook}" "[Porter's Handbook]. _Please do not commit yourself to more than you feel " "you can comfortably handle._" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:345 msgid "" "You may request maintainership of any unmaintained port as soon as you " "wish. Simply set `MAINTAINER` to your own email address and send a 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:349 msgid "" "File your PR with Product `Ports & Packages`. 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:351 #, no-wrap msgid "The challenge for port maintainers" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:354 msgid "" "This section will give you an idea of why ports need to be maintained and " "outline the responsibilities of a port maintainer." msgstr "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:356 #, no-wrap msgid "Why ports require maintenance" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:361 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:364 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:366 msgid "As a maintainer, you will need to manage the following challenges:" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:368 #, no-wrap msgid "*New software versions and updates.* New versions and updates of existing ported software become available all the time, and these need to be incorporated into the Ports Collection to provide up-to-date software.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:370 #, no-wrap msgid "*Changes to dependencies.* 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.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:372 #, no-wrap msgid "*Changes affecting dependent ports.* If other ports depend on a port that you maintain, changes to your port may require coordination with other maintainers.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:375 #, no-wrap msgid "" "*Interaction with other users, maintainers and developers.* Part of being a maintainer is taking on a support role.\n" "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.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:379 #, no-wrap msgid "" "*Bug hunting.* A port may be affected by bugs which are specific to FreeBSD.\n" "You will need to investigate, find, and fix these bugs when they are reported.\n" "Thoroughly testing a port to identify problems before they make their way into the Ports Collection is even better.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:382 #, no-wrap msgid "" "*Changes to ports infrastructure and policy.* Occasionally the systems that are used to build ports and packages are updated or a new recommendation affecting the infrastructure is made.\n" "You should be aware of these changes in case your ports are affected and require updating.\n" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:385 #, no-wrap msgid "" "*Changes to the base system.* FreeBSD is under constant development.\n" "Changes to software, libraries, the kernel or even policy changes can cause flow-on change requirements to ports.\n" msgstr "" #. type: Title ==== #: documentation/content/en/articles/contributing/_index.adoc:386 #, no-wrap msgid "Maintainer responsibilities" msgstr "" #. type: Title ===== #: documentation/content/en/articles/contributing/_index.adoc:388 #, no-wrap msgid "Keep your ports up to date" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:391 msgid "" "This section outlines the process to follow to keep your ports up to date." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:394 msgid "" "This is an overview. More information about upgrading a port is available " "in the extref:{porters-handbook}[Porter's Handbook]." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:398 msgid "Watch for updates" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:403 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:406 msgid "" "You may also receive automated email from the `FreeBSD Ports Version Check` " "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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:407 msgid "Incorporate changes" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:410 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:411 msgid "Review and test" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:413 msgid "Thoroughly review and test your changes:" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:416 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:419 msgid "" "Make sure your port's dependencies are complete. The recommended way of " "doing this is by installing your own ports tinderbox. See " "crossref:contributing[resources, Resources for ports maintainers and " "contributors] for more information." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:421 msgid "" "Check that the packing list is up to date. This involves adding in any new " "files and directories and removing unused entries." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:423 msgid "" "Verify your port using man:portlint[1] as a guide. See " "crossref:contributing[resources, Resources for ports maintainers and " "contributors] for important information about using portlint." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:426 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 `PORTREVISION` bump so that they will automatically be " "upgraded by automated tools such as package:ports-mgmt/poudriere[]." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:428 #: documentation/content/en/articles/contributing/_index.adoc:497 msgid "Submit changes" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:431 msgid "" "Send your update by submitting a Problem Report with an explanation of the " "changes and a patch containing the differences between the original port and " "the updated one. Please refer to extref:{problem-reports}[Writing FreeBSD " "Problem Reports] for information on how to write a really good PR." msgstr "" #. type: delimited block = 6 #: documentation/content/en/articles/contributing/_index.adoc:437 msgid "" "Please do not submit a man:shar[1] archive of the entire port; instead, use " "man:git-format-patch[1] or man:diff[1] `-ruN`. In this way, committers can " "much more easily see exactly what changes are being made. The Porter's " "Handbook section on extref:{porters-handbook}upgrading[Upgrading, port-" "upgrading] has more information." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:439 msgid "Wait" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:443 msgid "" "At some stage a committer will deal with your PR. It may take minutes, or " "it may take one or two weeks - so please be patient. If it takes any " "longer, please seek for help on mailing lists ({freebsd-ports}), IRC: " "#bsdports on EFNet or #freebsd-ports on Libera for example." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:444 msgid "Give feedback" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:447 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:448 msgid "And Finally" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:452 msgid "" "Your changes will be committed and your port will have been updated. The PR " "will then be closed by the committer. That is it!" msgstr "" #. type: Title ===== #: documentation/content/en/articles/contributing/_index.adoc:454 #, no-wrap msgid "Ensure your ports continue to build correctly" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:457 msgid "" "This section is about discovering and fixing problems that stop your ports " "from building correctly." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:460 msgid "" "FreeBSD only guarantees that the Ports Collection works on the `-STABLE` " "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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:464 msgid "" "Since the majority of FreeBSD installations run on PC-compatible machines " "(what is termed the `i386` architecture), we expect you to keep the port " "working on that architecture. We prefer that ports also work on the `amd64` " "architecture running native. It is completely fair to ask for help if you " "do not have one of these machines." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:469 msgid "" "The usual failure modes for non-`x86` machines are that the original " "programmers assumed that, for instance, pointers are `int`-s, or that a " "relatively lax older gcc 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:472 msgid "" "These are the tasks you need to perform to ensure your port is able to be " "built:" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:476 msgid "Watch for build failures" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:478 msgid "" "Check your mail for mail from `[email protected]` and the http://" "portscout.FreeBSD.org[distfiles scanner] to see if any of the port which are " "failing to build are out of date." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:479 #: documentation/content/en/articles/contributing/_index.adoc:528 msgid "Collect information" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:483 msgid "" "Once you are aware of a problem, collect information to help you fix it. " "Build errors reported by `pkg-fallout` 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:485 msgid "Build logs" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:486 msgid "" "The commands and options used to build the port (including options set in " "[.filename]#/etc/make.conf#)" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:487 msgid "" "A list of packages installed on their system as shown by man:pkg-info[8]" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:488 msgid "The version of FreeBSD they are running as shown by man:uname[1] `-a`" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:489 msgid "When their ports collection was last updated" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:490 msgid "When their ports tree and [.filename]#INDEX# was last updated" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:492 msgid "Investigate and find a solution" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:496 msgid "" "Unfortunately there is no straightforward process to follow to do this. " "Remember, though: if you are stuck, ask for help! The {freebsd-ports} is a " "good place to start, and the upstream developers are often very helpful." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:499 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:500 msgid "Send patches to upstream authors" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:505 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 "" #. type: Title ===== #: documentation/content/en/articles/contributing/_index.adoc:507 #, no-wrap msgid "Investigate bug reports and Bugzilla Problem Reports related to your port" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:510 msgid "This section is about discovering and fixing bugs." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:513 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:515 msgid "" "These are the tasks you need to perform to ensure your port continues to " "work as intended:" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:519 msgid "Respond to bug reports" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:522 msgid "" "Bugs may be reported to you through email via the https://bugs.FreeBSD.org/" "search/[Bugzilla Problem Report database]. Bugs may also be reported " "directly to you by users." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:525 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:527 msgid "" "If you have not responded after 14 days, any committer may commit from a PR " "that you have not responded to via a `maintainer-timeout`." msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:530 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:533 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:535 msgid "" "A detailed description of their actions, expected program behavior and " "actual behavior" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:536 msgid "Copies of input data used to trigger the bug" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:537 msgid "" "Information about their build and execution environment - for example, a " "list of installed packages and the output of man:env[1]" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:538 msgid "Core dumps" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:539 msgid "Stack traces" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:541 msgid "Eliminate incorrect reports" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:547 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:548 msgid "Find a solution" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:551 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 "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:552 msgid "Submit or approve changes" msgstr "" #. type: Plain text #: documentation/content/en/articles/contributing/_index.adoc:555 msgid "" "Just as with updating a port, you should now incorporate changes, review and " "test, and submit your changes in a Bugzilla 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 "" #. type: Title ===== #: documentation/content/en/articles/contributing/_index.adoc:557 #, no-wrap msgid "Providing support" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:562 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:566 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 `RPMS` 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:569 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:571 msgid "submit a Bugzilla PR or send you patches to update your port," msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:572 msgid "investigate and perhaps provide a fix to a PR, or" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:573 msgid "otherwise submit changes to your port." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:579 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:581 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:583 #, no-wrap msgid "Finding and fixing a broken port" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:586 msgid "" "There are some really good places to find a port that needs some attention." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:589 msgid "" "You can use the https://bugs.freebsd.org/search[web interface] to the " "Problem Report database to search through and view unresolved Bugzilla 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." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:591 msgid "" "https://portsfallout.com/[PortsFallout] shows port issues gathered from the " "FreeBSD package building." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:593 msgid "" "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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:598 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:600 #, no-wrap msgid "When to call it quits" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:607 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:611 msgid "" "In any case, the Ports Management Team (`portmgr`) 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 "" #. type: Title === #: documentation/content/en/articles/contributing/_index.adoc:613 #, no-wrap msgid "Resources for ports maintainers and contributors" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:617 msgid "" "The extref:{porters-handbook}[Porter's Handbook] is your hitchhiker's guide " "to the ports system. Keep it handy!" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:620 msgid "" "extref:{problem-reports}[Writing FreeBSD Problem Reports] describes how to " "best formulate and submit a Problem Report. Following this article will " "greatly assist us in reducing the time needed to handle your PRs." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:622 msgid "" "The https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla Problem Report " "database]." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:625 msgid "" "The http://portscout.FreeBSD.org[FreeBSD Ports distfile scanner (portscout)] " "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 `MASTER_SITES` " "updated." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:628 msgid "" "package:ports-mgmt/poudriere[] is the most thorough way to test a port " "through the entire cycle of installation, packaging, and deinstallation. " "Documentation is located at the https://github.com/freebsd/" "poudriere[poudriere GitHub repository]" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:632 msgid "" "man:portlint[1] is an application which can be used to verify that your port " "conforms to many important stylistic and functional guidelines. portlint is " "a simple heuristic application, so you should use it __only as a guide__. " "If portlint suggests changes which seem unreasonable, consult the extref:" "{porters-handbook}[Porter's Handbook] or ask for advice." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:637 msgid "" "The {freebsd-ports} is for general ports-related discussion. It is a good " "place to ask for help. You can link:https://lists.freebsd.org/[subscribe, " "or read and search the list archives]. Reading the archives of the {freebsd-" "ports-bugs} and the {svn-ports-head} may also be of interest." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:639 msgid "" "https://portsfallout.com/[PortsFallout] is a place to help in searching for " "the https://lists.freebsd.org/archives/freebsd-pkg-fallout/[FreeBSD package-" "fallout archive]." msgstr "" #. type: Title == #: documentation/content/en/articles/contributing/_index.adoc:641 #, no-wrap msgid "Getting Started in Other Areas" msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:645 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:647 msgid "" "The https://wiki.freebsd.org/JuniorJobs[Junior Jobs] 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 "" #. type: delimited block = 4 #: documentation/content/en/articles/contributing/_index.adoc:648 msgid "" "The https://wiki.freebsd.org/IdeasPage[Ideas Page] contains various \"nice " "to have\" or \"interesting\" things to work on in the Project." msgstr ""