Language Translated Untranslated Untranslated words Checks Suggestions Comments
English This translation is used for source strings. This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 2
Chinese (Simplified) (zh_CN) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 2% 37 987
Chinese (Traditional) (zh_TW) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
Dutch (nl_NL) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
French (fr_FR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
German (de_DE) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
Italian (it_IT) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
Norwegian Bokmål This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 60% 15 760 12
Persian This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
Portuguese (Brazil) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 63% 14 759 11
Spanish This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 63% 14 759 10
Turkish (tr_TR) This component is linked to the Documentation/articles/bsdl-gpl repository. BSD-2-Clause 0% 38 988
Please sign in to see the alerts.
Project website docs.freebsd.org/en
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
Translation license BSD 2-Clause "Simplified" License
Filemask documentation/content/*/articles/port-mentor-guidelines/_index.po
Languages 12
Source strings 38
Source words 988
Source characters 6,137
Hosted strings 456
Hosted words 11,856
Hosted characters 73,644
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.
Vi advarer mentees om at noe av kritikken de mottar, kan være mindre <quote>konstruktiv</quote> enn andre (enten gjennom språkkommunikasjonsproblemer eller overdreven flisespikking), og at det å håndtere dette grasiøst bare er en del av å være i et stort samfunn. I tilfelle det er konkrete problemer med bestemte personer eller spørsmål, håper vi at de vil nærme seg et portmgr-medlem på IRC eller via e-post.
yesterday
New contributor yesterday
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.
Vi forventer at mentees skal være forberedt på konstruktiv kritikk fra samfunnet. Det er fortsatt mye <quote>kjennskap</quote> som ikke er direkteskrevet ned. Å svare godt på konstruktiv kritikk er det vi håper vi velger etter ved å først gjennomgå deres eksisterende bidrag på IRC og postlister.
yesterday
New contributor yesterday
Some reprobate, whose name shall be withheld, made the https://lists.freebsd.org/pipermail/cvs-ports/2007-September/134614.html[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.
Noen klandrede, hvis navn skal holdes tilbake, gjorde <link xlink:href="https://lists.freebsd.org/pipermail/cvs-ports/2007-September/134614.html">første registrerte co-mentor commit</link>. Lignende co-mentorforbindelser har også blitt oppdaget i src-treet. Gjøres dette det riktig? Gjøres dette feil? Det ser ut til å være en del av utviklingen av hvordan ting gjøres.
yesterday
New contributor yesterday
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.
Når en forespørsel kommer til portmgr, leses den vanligvis som, <quote> Jeg foreslår 'foo' for en portforbindelse, jeg vil være co-mentor med 'bar' </quote>. Forslag mottatt, stemt og tatt videre.
yesterday
New contributor yesterday
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.
Akkurat som vi er alle forskjellige individer, har hver mentee forskjellige læringskurver, tidsforpliktelser og andre påvirkningsfaktorer som vil bidra til tiden som kreves før de kan <quote>jobbe solo</quote>. Empirisk bør en mentee observeres i minst 3 måneder. 90-100 commits er et annet mål som en mentor kan bruke før du frigjør en mentee. Andre faktorer for å vurdere tidligere utgivelse av en mentee er antall feil de måtte ha gjort, QATs mottatt etc. Hvis de fortsatt gjør nybegynnerfeil, krever de fortsatt mentorveiledning.
yesterday
New contributor yesterday
Browse all component changes

Daily activity

Daily activity

Weekly activity

Weekly activity