#213 docs(council): Amend Charter for Community Initiative Leads
Merged 3 months ago by jflory7. Opened 5 months ago by jflory7.
Fedora-Council/ jflory7/council-docs change/charter-exec-sponsors  into  main

@@ -16,13 +16,19 @@ 

  == Responsibilities

  

  The {team_name} is responsible for issues of strategic importance for Fedora that require leadership and coordination across the various teams and sub-projects to achieve.

- 

  *Its primary role 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*.

  This is done in consultation with the entire Fedora community through transparent, public discussion.

  

- The {team_name} *governs Fedora's financial resources*, working with our sponsor(s) to establish an annual budget allocated to support Fedora initiatives, including Fedora Ambassadors, Fedora-managed events, and other activities which advance the project's goals.

+ {team_name} members engage with people across the community to make sure Fedora is functioning smoothly and that teams are empowered to do interesting and meaningful things.

+ They decide on issues regarding use of the Fedora *trademarks*, are responsible for final *arbitration of complaints* related to project policies and for *settling disputes* escalated from other committees or subgroups.

+ They may handle *sensitive legal or personnel issues* which require research and discussion to protect the interests of the Fedora Project or its sponsors.

+ 

+ To support project efforts with more ambitious scope, the {team_name} sponsors xref:project::initiatives.adoc[Community Initiatives] proposed by the community.

+ {team_name} members serve as xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsors] for these Initiatives, working personally to ensure that the <<composition\--initiative-leads,Leads>> have everything they need to succeed.

  

- The {team_name} also decides on issues regarding use of the Fedora *trademarks*, is responsible for final *arbitration of complaints* related to project policies and for *settling disputes* escalated from other committees or subgroups, and may handle *sensitive legal or personnel issues* which require research and discussion to protect the interests of the Fedora Project or its sponsor(s).

+ The {team_name} *governs Fedora’s financial resources*, working with our sponsor to establish an annual budget allocated to support these Initiatives, various Fedora teams and programs, Fedora-managed events, and other activities which advance the Fedora Strategy.

+ 

+ The {team_name} is also responsible for developing, tracking, and updating the Fedora Strategy.

  

  

  [[decisions]]
@@ -75,10 +81,25 @@ 

  [[composition--initiative-leads]]

  === Community Initiative Leads

  

- On an ongoing basis, including sessions at Flock and in public online meetings, the {team_name} will identify two to four key xref:project::initiatives.adoc[Community Initiatives] with a timeframe of approximately eighteen months, and appoint *Community Initiative Leads* for each goal.

- These will serve as {team_name} members.

+ Each xref:project::initiatives.adoc[Community Initiative] is represented by one {team_name} seat.

+ Typically, this seat is filled by the Lead of the Initiative, although it is possible for two people (at most) to share a single {team_name} seat as Co-Leads.

+ While naturally the people in these roles will focus primarily on their own Initiative, this is a full {team_name} position and Community Initiative Leads are invited to participate in all {team_name} activities and decisions.

+ 

+ [NOTE]

+ ====

+ This policy may be surprising, but we have found that this wider engagement connects the specific work to everything going on in Fedora, leading to greater success for the Initiative.

+ Community Initiative Leads may even serve as Executive Sponsors for other Initiatives.

+ ====

+ 

+ Community Initiative Leads typically serve on the {team_name} for the duration of their Initiative.

+ When the Initiative concludes, the {team_name} term also expires.

+ 

+ Each Community Initiative Lead is paired with an xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsor], who is another member of the {team_name}.

+ 

+ Community Initiatives must be documented with measurable goals.

+ The Community Initiative Leads are responsible for coordinating efforts to reach those goals, evaluating and reporting on progress, and working regularly with all relevant groups in Fedora to ensure that progress is made.

+ xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsors] are responsible for making sure the Initiative is on track and for removing blockers.

  

- Each Community Initiative will be documented with measurable goals, and the Community Initiative Lead is responsible for coordinating efforts to reach those goals, evaluating and reporting on progress, and working regularly with all relevant groups in Fedora to ensure that progress is made.

  

  [[composition-representatives]]

  === Representatives

This commit amends the Fedora Council Charter in the following ways:

  • Responsibilities: Add note about Executive Sponsor role and that a Fedora Council member is expected to become a Sponsor as a part of their term on the Council.
  • Community Initiative Leads: Clarify the role amid recent changes to Community Initiatives, especially around the composition of the seat and the fact that Initiatives are not hand-appointed by the Council, but actually driven by community consensus and momentum.

Closes Fedora-Council/tickets#412.

rebased onto 2bda8de

5 months ago

Metadata Update from @jflory7:
- Pull-request tagged with: needs feedback, type - existing docs
- Request assigned

5 months ago

1 new commit added

  • docs(council): Implement feedback to Community Initiatives role
5 months ago

I integrated feedback from @mattdm in commit ce352c7.

Metadata Update from @jflory7:
- Pull-request untagged with: needs feedback

3 months ago

rebased onto 06a59e1

3 months ago

Over two months have passed since my last commit addressing feedback, so I am going to merge this. :clapper:

Pull-Request has been merged by jflory7

3 months ago