fedora-docs-l10n/project/master/pages/initiatives — Dutch @ Fedora Weblate: How are Community Initiatives Finalized?

Translation

English type: Title ==

Dutch

Needs editing

Skip

	English	Dutch	Actions
	What are Community Initiatives?
	Want to do something big? Have an idea that won’t fit in a single release cycle? Perhaps an improvement broader than the technical scope covered by the Changes policy? Want to make sure the community is aligned behind your goal, and that you have the resources and access you need to make it happen? A Community Initiative may be the framework for you!
	Fedora Community Initiatives (formerly "Objectives") are projects which do not fall neatly into the biannual Fedora Linux release cycle. Typically they require longer to complete (e.g. 8-18 months) and are not limited to engineering projects. Other key areas are administration; documentations; outreach; motivation; communications; budgets and best practice. Within the Project these are grouped under a heading of xref:mindshare-committee::index.adoc[Mindshare]. The Council looks to achieve a balance between engineering projects and those aligned with Mindshare.
	The primary role of the xref:council::index.adoc[Fedora Council] is to identify the short-, medium-, and long-term goals of the Fedora community and to organize and enable the project to best achieve them. Anyone can propose a Community Initiative to the Council. To be accepted, it should align with Fedora’s xref:project::index.adoc#_our_mission[mission statement] and long-term goals.
	Each Community Initiative has a designated Community Initiative Lead. This Lead sits on the Council for the duration of the Initiative and is responsible for coordinating efforts to reach the Community Initiative’s goals, as well as evaluating and reporting on progress. The Initiative Lead works regularly with all relevant groups in Fedora to ensure that progress is made.
	Proposing a Community Initiative
	To propose a Community Initiative to the Council, the Lead should first discuss on the https://discussion.fedoraproject.org/tag/council[#council tag on Fedora Discussion]. Next, if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket]. Of course, people need to be ready to do the actual work required — a Community Initiative without passionate bottom-liners will not get far.
	To succeed, Community Initiatives require a leadership team with division of responsibility. For example separating roles of project leadership, engineering, marketing and documentation, depending on the size and scope of the Initiative. The Council can assist a proposer in finding the right people to work on the project if required.
	Executive Sponsors
	Every Community Initiative must have an Executive Sponsor. This can be any current member of the Council – even, possibly, the Lead of another Initiative. You should find a sponsor as part of community discussion before filing a ticket. Once someone has agreed to the responsibility, the proposal can move forward.
	Role of the Executive Sponsor
	A Fedora Council member becomes an Executive Sponsor until completion of the Community Initiative or for the duration of their Council term (whichever comes first). The Executive Sponsor is responsible for partnering with the Lead as a connection point to the Fedora Project at a high-level. The Executive Sponsor represents a wider view of what the Fedora Project is focused on, whether that is in terms of the Fedora strategy or a specific area of interest (e.g. DEI, Engineering, Mindshare). The Executive Sponsor is not responsible for doing the work directly, but rather as an advocate for the initiative and can help by unlocking resources, help unblock work, act as a consultant on Council and Project perspectives and generally supporting the initiative to allow the work to succeed.
	An Executive Sponsor may find that they are no longer able to fill this role for a Community Initiative, whether due to an expiring Council term or that they do not have the capacity to continue. In this event, the Executive Sponsor and the Lead must work together to identify another Fedora Council member who can be the Executive Sponsor.
	Relationship between Lead and Executive Sponsor
	How the Community Initiative Lead and the Executive Sponsor collaborate is largely up to them. However, it is suggested that the Lead and Sponsor have a regular meeting cadence (e.g. weekly or fortnightly) to check in on progress and identify challenges. The Lead should provide updates to the Executive Sponsor on the work, engagement with the community, and requests for help in order to succeed. The Lead should expect the Executive Sponsor to ask them questions, suggest other teams or people to collaborate with, and give suggestions on how to acquire the needed resources to succeed. Periodically, the Executive Sponsor will ask the Lead to share progress or milestones back to the wider Fedora Council.
	How are Community Initiatives Finalized?
	At the end of the expected duration of the Initiative (as specified at the proposal / acceptance stage), the Council will assess the progress of the Initiative. If all of the aims or the most significant of them are achieved, the Initiative will be terminated. If the aims are nearly complete and further work substantially increases the impact, it may be allowed to continue for a further agreed period. After that, it will be terminated. Initiatives will not be allowed to run indefinitely.
	Current 12-18 Month Community Initiatives
	This section documents the current Initiatives we, the Council, have accepted for implementation in alignment with the medium-term goals of the Project, (as explained in the xref:council::index.adoc[Council Charter]).
	Mentored Projects Initiative
	Goal
	We envision a future where mentors and mentees know what is expected of them when entering a Fedora Mentored Project and have a smooth onboarding process. There is also a culture of recognition for all the effort they put into the projects to be successful.
	Community Initiative Leads
	Fernando Fernandez Mancera (link:{FWIKI}/User:ffmancera[@ffmancera]), Smera Goel (link:{FWIKI}/wiki/User:Smeragoel[@smeragoel])
	Executive Sponsor
	Jona Azizaj (link:{FWIKI}/User:Jonatoni[@jonatoni])
	Timeframe
	8-12 months
	Community Initiative Details
	See the link:{FWIKI}/Initiatives/Mentored_Projects_2024[wiki page].
	Community Operations 2.0 Initiative

Loading…

None

String updated in the repository

English

Dutch 0 characters edited Current translation Empty

a year ago

Browse all string changes

Glossary

English	Dutch
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap

Source string location

pages/initiatives.adoc:66

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

po/nl/master/pages/initiatives.po, string 16

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.