Translation Information

Project website pagure.io/fedora-docs-l10n/council
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>

Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Source code repository ssh://pagure.io/fedora-docs-l10n/council.git
Repository branch master
Last remote commit Translated using Weblate (Swedish) c4de2cc1e
User avatar goeran authored 21 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-council/nav/
Filemask po/*/master/pages/policy/coc-response-policy.po
Translation file Download po/fur/master/pages/policy/coc-response-policy.po
The FCAIC is empowered to take action on Code of Conduct reports with an additional +1 from another core Council member or the Diversity & Inclusion Advisor and report back to Council.
Il FCAIC al à il podê di procedi su lis segnalazion sul codiç di condote cuntun +1 adizionâl che al rive di un altri membri centrâl dal consei o dal consulent pe diversitât e inclusion e dopo riferî al consei.
3 months ago
Teams within Fedora have the freedom to decide what is on- and off-topic for their fora (IRC channel, mailing list, Telegram channel, et cetera). Moderators may ban participants for repeatedly engaging in off-topic discussion in contributor channels, however they must file a ticket with the Council's https://pagure.io/CoC/issues[Code of Conduct issue tracker] to report the ban. Bans for being off-topic in one channel may not be extended to other channels unless the behavior is displayed in that channel as well. In this case, each ban should be treated as a separate issue with its own ticket. Community members who wish to appeal the ban may file a https://pagure.io/Fedora-Council/tickets/issues[ticket with the Council].
I grups inFedora a àn la libertât di decidi che che al è o nol è in argoment tai lôr ambients di discussion (canâl IRC, mailing list, canâl Telegram e v.i.). I moderadôrs a puedin bandî i partecipants se, tai canâi di colaborazion, a jentrin in maniere ripetude in discussions fûr argoment, dut câs, par segnalâ il bant, a àn di vierzi un cartelin cul https://pagure.io/CoC/issues[Segnadôr di problemis pal codiç di condote] dal consei, par segnalâ il bant. I. Al podarès jessi che i bants par jessi lâts fûr argoment intun canâl al podarès no jessino vegnedin pandûts su ducj i canâi, fûr che nol sedi vignût fûr chel compuartament ancje in chel canâlancje in chei canâi chel compuartament. In chest câs, ogni bant al à di vignî tratât come probleme separât, cul so cartelin. I membris de comunitât che a desiderin apelâsi al bant a puedin vierzi un https://pagure.io/Fedora-Council/tickets/issues[cartelin cul consei].
3 months ago
Teams within Fedora have the freedom to decide what is on- and off-topic for their fora (IRC channel, mailing list, Telegram channel, et cetera). Moderators may ban participants for repeatedly engaging in off-topic discussion in contributor channels, however they must file a ticket with the Council's https://pagure.io/CoC/issues[Code of Conduct issue tracker] to report the ban. Bans for being off-topic in one channel may not be extended to other channels unless the behavior is displayed in that channel as well. In this case, each ban should be treated as a separate issue with its own ticket. Community members who wish to appeal the ban may file a https://pagure.io/Fedora-Council/tickets/issues[ticket with the Council].
I grups inFedora a àn la libertât di decidi che che al è o nol è in argoment tai lôr ambients di discussion (canâl IRC, mailing list, canâl Telegram e v.i.). I moderadôrs a puedin bandî i partecipants se tai canâi di colaborazion a jentrin in maniere ripetude in discussions fûr argoment, dut câs a àn di vierzi un cartelin cul https://pagure.io/CoC/issues[Segnadôr di problemis pal codiç di condote] dal consei, par segnalâ il bant. I bants par jessi lâts fûr argoment intun canâl al podarès no jessi pandût su ducj i canâi, fûr che nol sedi vignût fûr chel compuartament ancje in chel canâl. In chest câs, ogni bant al à di vignî tratât come probleme separât cul so cartelin. I membris de comunitât che a desiderin apelâsi al bant a puedin vierzi un https://pagure.io/Fedora-Council/tickets/issues[cartelin cul consei].
3 months ago
(Fedora Council IRC meeting, 2018-05-23)
(Riunion IRC dal consei di Fedora, 23-05-2018)
3 months ago
Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response.
Une volte che nus ven notificât cuntun cartelin che al è stât compilât un probleme di codiç di condote, il consei al rispuindarà cuntun messaç iniziâl di contat jenfri une setemane. Chest al rivarà cuntune richieste di rispueste e azions sucessivis a rivaran jenfri une setemane de rispueste iniziâl dal consei.
3 months ago
Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response.
Une volte che nus ven notificât cuntun cartelin che al è stât compilât un probleme di codiç di condote, il consei al rispuindarà cuntun messaç iniziâl di contat jenfri une setemane. Chest al rivarà cuntune richieste di rispueste e azions sucessivis a rivaran jenfri une setemane de rispueste iniziâl dal consei.
3 months ago
Code of Conduct response policy
Politiche di rispueste al codiç di condote
3 months ago
New contributor 3 months ago
Resource update 3 months ago
New strings to translate 3 months ago
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 5 199 1,252
Translated 100% 5 199 1,252
Needs editing 0% 0 0 0
Failing checks 0% 0 0 0

Last activity

Last change Jan. 5, 2021, 8:48 p.m.
Last author Fabio Tomat

Daily activity

Daily activity

Weekly activity

Weekly activity