#1653 [Meta] Better communicating roles and responsibilities of FESCo for elections
Closed: Fixed 3 years ago Opened 4 years ago by jflory7.

Summary

It was noted in the past that there was a desire for community participation and interest in nominations and voting for FESCo members in Elections. Better communicating the common tasks and responsibilities of FESCo members and what roles there are to play will help this process.

Analysis

CommOps has been trying to brainstorm ways to improve engagement and interest in the elections cycles by the community. There are many parts to this, including the nominations (open now for the December 2016 elections), interviews, and the actual voting. While this ticket likely isn't in time to have a direct impact on this election cycle, this is mostly about building a solution for after this run.

Part of the idea is that people who are running for FESCo should be aware of these kinds of responsibilities ahead of time by being active in the developer community, which is likely true. But there is the problem of impostor syndrome too. Clearly communicating what kinds of things FESCo members are expected to do should help alleviate any doubts and help motivate qualified contributors to decide to run. This also helps community members who are maybe not heavily involved, but know a good candidate they would like to nominate. The summary of the roles and responsibilities would be especially helpful for someone who might cast a nomination for a qualified individual as well.

I mostly looked at the main wiki page and some of the pages in the FESCo wiki category, but I was unable to find this info clearly communicated either. It would be helpful to have this displayed in a prominent place, which would be especially helpful during the elections.

Implementation

  1. FESCo meets, brainstorm bulletpoint list of common tasks / what things are expected of FESCo members
  2. Review and polish anything necessary
  3. Add a new section to main wiki page (e.g. Roles and responsibilities), add bulletpoints / descriptions there
  4. During election seasons, use link to that information in official election communications / use the info there for other posts in the election

Discussed in 2017-01-24 meeting:

We're shifting control of this ticket away from CommOps. We strongly believe that an improvement can be made and we are leaving this for FESCo to decide on what is best to describe the roles and operations.

Adding meeting keyword here.

Metadata Update from @kevin:
- Issue tagged with: meeting

3 years ago

In todays meeting we agreed I would try and draft something we could then look at and improve. Here's my attempt:

FESCo is responsible for technical issues and coordination of technical resources for the project.

Issues FESCo handles include:

  • Approval and coordination of "changes" for traditional Fedora releases.
  • Package maintainer disputes
  • Larger changes to the Fedora Package collection
  • Guidance and technical direction for other parts of the project
  • Setting the schedule for Fedora development cycles.
  • Reviewing and approving technical content from Fedora Working groups (Product Requirement Docs, deliverables, processes).
  • Responsible for what software is offered to end users under what conditions.
  • Oversight and approval of new spins and other media that doesn't fit under a working group.

FESCo has empowered the FPC (Fedora Packaging Comittee) to handle mangement of packaging guidelines, so those items are usually deferred to them with occasional FESCo oversight.

FESCo has a designate for each Working Group that coordinates with that Group and communicates back to FESCo any issues or concerns. Currently there are: Workstation, Server and Atomic Working groups.

@kevin I'd also add something like: "Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole and who understand how the many different pieces fit together. Ideal candidates should also have a history of fostering inter-team coordination."

Just wanted to give a +1 that this gives a lot of clarity to me as an outsider to the role and responsibilities of FESCo. Thanks!

FESCo is responsible for technical issues and coordination of technical resources for the project.

Issues FESCo handles include:

  • Approval and coordination of "changes" for Fedora releases.
  • Package maintainer disputes
  • Larger changes to the Fedora Package collection
  • Guidance and technical direction for other parts of the project
  • Setting the schedule for Fedora development cycles.
  • Reviewing and approving technical content from Fedora Working groups (Product Requirement Docs, deliverables, processes).
  • Responsible for what software is offered to end users under what conditions.
  • Oversight and approval of new spins and other media that doesn't fit under a working group.

FESCo has empowered the FPC (Fedora Packaging Comittee) to handle mangement of packaging guidelines, so those items are usually deferred to them with occasional FESCo oversight.

Candidates for FESCo should be people who have a wide breadth of knowledge about the Fedora Project as a whole and who understand how the many different pieces fit together. Ideal candidates should also have a history of fostering inter-team coordination.

FESCo has a designate for each Working Group that coordinates with that Group and communicates back to FESCo any issues or concerns. Currently there are: Workstation, Server and Atomic Working groups.

*agreed The updated statement in comments will be added to the FESCo wiki page (+6,0,-0)

(Leaving open until the wiki can be edited)

Added to wiki.

:aquarius:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata