#$FreeBSD$ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2020-06-06 11:08-0300\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: en_US\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 , YEAR1, YEAR2 msgctxt "_" msgid "translator-credits" msgstr "" #. (itstool) path: info/title #: article.translate.xml:5 msgid "Port Mentor Guidelines" msgstr "" #. (itstool) path: authorgroup/author #: article.translate.xml:8 msgid "The FreeBSD Ports Management Team" msgstr "" #. (itstool) path: info/pubdate #. (itstool) path: info/releaseinfo #: article.translate.xml:13 article.translate.xml:15 msgid "" "$FreeBSD: head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml " "51348 2017-12-30 22:56:56Z eadler $" msgstr "" #. (itstool) path: info/copyright #: article.translate.xml:17 msgid "" "2011 Thomas " "Abthorpe Chris Rees" msgstr "" #. (itstool) path: sect1/title #: article.translate.xml:26 msgid "Guideline for Mentor/Mentee Relationships" msgstr "" #. (itstool) path: sect1/para #: article.translate.xml:28 msgid "" "This section is intended to help demystify the mentoring process, as well as " "a way to openly promote a constructive discussion to adapt and grow the " "guidelines. In our lives we have too many rules; we are not a government " "organization that inflicts regulation, but rather a collective of like " "minded individuals working toward a common goal, maintaining the quality " "assurance of the product we call the Ports Tree." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:38 msgid "Why Mentor?" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:42 msgid "" "For most of us, we were mentored into the Project, so return the favor by " "offering to mentor somebody else in." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:48 msgid "You have an irresistible urge to inflict knowledge on others." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:53 msgid "" "The usual punishment applies because you are sick and tired of committing " "somebody else's good work!" msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:60 msgid "Mentor/Co-Mentor" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:62 msgid "Reasons for a co-mentorship:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:66 msgid "" "Significant timezone differential. Accessible, interactive mentor(s) " "available via IM is extremely helpful!" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:72 msgid "" "Potential language barrier. Yes, FreeBSD is very English oriented, as is " "most software development, however, having a mentor who can speak a native " "language can be very useful." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:79 msgid "" "ENOTIME! Until there is a 30 hour day, and an 8 day week, some of us only " "have so much time to give. Sharing the load with somebody else will make it " "easier." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:86 msgid "" "A rookie mentor can benefit from the experience of a senior committer/mentor." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:91 msgid "Two heads are better than one." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:95 msgid "Reasons for sole mentorship:" msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:99 msgid "You do not play nicely with others." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:103 msgid "You prefer to have a one-on-one relationship." msgstr "" #. (itstool) path: listitem/para #: article.translate.xml:107 msgid "The reasons for co-mentorship do not apply to you." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:114 article.translate.xml:222 msgid "Expectations" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:116 msgid "" "We expect mentors to review and test-build all proposed patches, at least " "for an initial period lasting more than a week or two." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:120 msgid "" "We expect that mentors should take responsibility for the actions of their " "mentee. A mentor should follow up with all commits the mentee makes, both " "approved and implicit." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:124 msgid "" "We expect mentors to make sure their mentees read the Porter's " "Handbook, the PR handling guide, and the Committer's Guide. While it is not necessary to memorize all the " "details, every committer needs to have an overview of these things to be an " "effective part of the community (and avoid as many rookie mistakes as " "possible)." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:135 msgid "Selecting a Mentee" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:137 msgid "" "There is no defined rule for what makes a candidate ready; it can be a " "combination of number of PRs they have submitted, the number of ports " "maintained, frequency of ports updates and/or level of participation in a " "particular area of interest like GNOME, " "KDE, Gecko or others." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:146 msgid "" "A candidate should have almost no timeouts, be responsive to requests, and " "generally helpful in supporting their ports." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:150 msgid "" "There must be a history of commitment, as it is widely understood that " "training a committer requires time and effort. If somebody has been around " "longer, and spent the time observing how things are done, there is some " "anticipation of accumulated knowledge. All too often we have seen a " "maintainer submit a few PRs, show up in IRC and ask when they will be given " "a commit bit." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:158 msgid "" "Being subscribed to, and following the mailing lists is very beneficial. " "There is no real expectation that submitting posts on the lists will make " "somebody a committer, but it demonstrates a commitment. Some mails offer " "insights into the knowledge of a candidate as well how they interact with " "others. Similarly participating in IRC can give somebody a higher profile." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:166 msgid "" "Ask six different committers how many PRs a maintainer should submit prior " "to being nominated, and you will get six different answers. Ask those same " "individuals how long somebody should have been participating, same dilemma. " "How many ports should they have at a minimum? Now we have a bikeshed! Some " "things are just hard to quantify, a mentor will just have to use their best " "judgement, and hope that portmgr agrees." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:177 msgid "Mentorship Duration" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:179 msgid "" "As the trust level develops and grows, the mentee may be granted " "implicit commit rights. This can include trivial changes to a " "Makefile, pkg-descr etc. " "Similarly, it may include PORTVERSION updates that do not " "include plist changes. Other circumstances may be " "formulated at the discretion of the Mentor. However, during the period of " "mentorship, a port version bump that affects dependent ports should be " "checked by a mentor." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:189 msgid "" "Just as we are all varied individuals, each mentee has different learning " "curves, time commitments, and other influencing factors that will contribute " "to the time required before they can fly solo. Empirically, a " "mentee should be observed for at least 3 months. 90-100 commits is another " "target that a mentor could use before releasing a mentee. Other factors to " "consider prior releasing a mentee are the number of mistakes they may have " "made, QATs received etc. If they are still making rookie mistakes, they " "still require mentor guidance." msgstr "" #. (itstool) path: sect2/title #: article.translate.xml:202 msgid "Mentor/Co-Mentor Debate" msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:204 msgid "" "When a request gets to portmgr, it usually reads as, I propose 'foo' " "for a ports commit bit, I will co-mentor with 'bar'. Proposal " "received, voted, and carried." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:209 msgid "" "The mentor is the primary point of contact or the first among equals, the co-mentor is the backup." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:213 msgid "" "Some reprobate, whose name shall be withheld, made the first recorded co-mentor commit. Similar co-mentor commits have " "also been spotted in the src tree. Does this make it right? Does this make " "it wrong? It seems to be part of the evolution of how things are done." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:224 msgid "" "We expect mentees to be prepared for constructive criticism from the " "community. There's still a lot of lore that is not written " "down. Responding well to constructive criticism is what we hope we are " "selecting for by first reviewing their existing contributions on IRC and " "mailing lists." msgstr "" #. (itstool) path: sect2/para #: article.translate.xml:231 msgid "" "We warn mentees that some of the criticism they receive may be less " "constructive than others, (whether through language " "communication problems, or excessive nit-picking), and that dealing with " "this gracefully is just part of being in a large community. In case of " "specific problems with specific people, or any questions, we hope that they " "will approach a portmgr member on IRC or by email." msgstr ""