Zen

Source string Source string

26/10000 · 26

The string is read only.

English Actions
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
Vision
The Fedora Community Operations Team enables a highly-collaborative Fedora community ecosystem, where contributors thrive in achieving objectives of the Fedora 2028 strategy and friction in the contribution process can be identified and addressed for Fedora contributors.
Mission
The Fedora Community Operations Team achieves a highly-collaborative Fedora community ecosystem through two key areas: *process improvement*, to partner with others in making the contribution process more open and transparent, and *community social analysis*, to better understand contribution pathways without prescribing a specific journey.
Robert Wright (link:{FWIKI}/User:Rwright[@rwright]), Justin W. Flory (link:{FWIKI}/wiki/User:Jflory7[@jflory7])
Aoife Moloney (link:{FWIKI}/User:Jonatoni[@amoloney])
10 months

Loading…

User avatar None

String added in the repository
Community Initiative Leads
Community Initiative Leads
3 months ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched question mark: Czech, Spanish, Indonesian

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Labeled list
Flags
no-wrap, read-only
Source string location
./pages/initiatives.adoc:87 • ./pages/initiatives.adoc:108
String age
3 months ago
Last updated
3 months ago
Source string age
3 months ago
Translation file
pot/master/pages/initiatives.pot, string 23