fedora-docs-l10n/council/master/pages/procedures/team_directory — Ukrainian @ Fedora Weblate: Responsibilities

Zen

Translation

English type: Title ==

Ukrainian

Needs editing

Skip

	English	Ukrainian	Actions
	Fedora is a large community with many different activities, and the directory will help existing and potential community members find the team they are looking for. Having periodic checks helps to ensure that the information is accurate and that we do not point people toward teams that are no longer active.
	The intent is _not_ to increase the administrative burden on teams or the barriers to starting a team. The intent is _not_ to say "if you are not listed, you are not allowed to be a team in Fedora". However, presence in the directory may be used by other teams to evaluate funding or work requests (e.g. website work or design assets).
	Content
	Teams should list the following information in the format specified by the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[template]:
	Team name
	Team summary
	Team website
	Team status (active or inactive)
	Team's preferred asynchronous communication channel (e.g. mailing list, forum category, etc)
	Team's preferred synchronous communication channel (e.g. IRC channel, Telegram room, etc)
	Team's issue tracker
	Team's meeting (preferably a link to a Fedocal event, alternatively a static day and time)
	Additional information the team desires to publish in the directory
	It is expected that not all teams will have answers for the above. They should be provided when they exist.
	Content may be stored in the https://pagure.io/Fedora-Council/council-docs[council-docs] repo if the team does not have its own docs repo. If a team has its own docs repo, the content can be kept in that repo so that it can be used to render the team's own documentation. This allows for a single source of truth and prevents content from diverging.
	Responsibilities
	Teams are responsible for ensuring their entries are up to date.
	The DEI, Engineering, and Mindshare representatives to the {team_name} are responsible for ensuring that the team that falls under their area keeps the information up-to-date and removes teams that do not appear to be active. They are _not_ responsible for _providing_ the information. Representatives may delegate sections of their area as they see fit. Checks can be done at any time, but should be done around the branch date for each release at a minimum.
	Mechanism
	Team information files
	The directory requires a file that contains the information about the team. The suggested naming convention is `NAME_team_info.adoc`, but any valid file name is acceptable. The file may be stored in the team's own documentation repository or in the https://pagure.io/Fedora-Council/council-docs/[council-docs repository]. See the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[example template] for format and structure.
	Rendering the directory
	Teams will appear in the directory if the team info file is included in the `{engineering,mindshare}/modules/ROOT/pages/index.adoc` directory of the https://pagure.io/Fedora-Council/council-docs/[council-docs repo]. After `include`-ing the info file, the index page must include the `team_render.adoc` file that defines the rendering.
	Reusing the data on team pages
	Teams can include their `NAME_team_info.adoc` file on their page(s), and then use `{team_name}`, `{team_summary}` etc. anywhere on the page.

Loading…

anonymous

Suggestion added

English

Ukrainian 9 characters edited

a year ago

None

String updated in the repository

English

Ukrainian 0 characters edited Current translation Empty

a year ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Ukrainian
No related strings found in the glossary.

15279318 String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

pages/procedures/team_directory.adoc:53

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

po/uk/master/pages/procedures/team_directory.po, string 22

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.