What is FOSCo?
Fedora Outreach Steering Committee (FOSCo) strives to be a group for cross-team collaboration on all user facing efforts, with representation from any interested groups, Special Interest Groups (SIGs), or individuals.
FOSCo has a remit to track efforts in all project areas against a commonly agreed set of goals, with an remit of communicating these efforts with the larger community in an easy to follow manner.
FOSCo works towards improving internal cooperation and wishes to make outward-facing efforts more effective and develop a stronger sense of community.
FOSCo functions are:
Primary channel of communication amongst groups
- shares mainstream communications, news and other stuff related to the Project outreach:
- each group shares their concerning part with their contributors;
- lead discussions about the above mentioned communications.
Proposes budget and its allotment (in place of FAmSCo)
- verifies the respect of the budgeting rules;
- according to the budgeting rules presents the regional budgets to the Council and reports the results to the regions;
- nominates the regional treasures;
- works in accordance with OSAS for the tickets approval and reimbursement;
- approves funding and swag requests (outside the accountability of each group).
proposes marketing strategies
- keeps contacts with the press;
- nominates the regional responsive for the press.
- plans the strategies for the growth of Fedora;
- long term actions to be undertaken;
- set points to be reached in a medium period (a couple of releases);
- manages swag production;
- decides which kind of swag will be product;
- analyze the estimates cost of production.
- nominates the regional logistician delegate responsive for the swag;
- improves the rules for the swag requests;
proposes documentation strategies
- evaluates the documentation to be ready at new Fedora release;
- organizes efforts to be done for being ready.
- plans the common strategies to bring new people;
- monitors the state of documentation.
proposes design strategies
- organize the Design FAD for the long term strategies;
- improves the design guidelines;
- get in touch with the Design team for the over groups requests.
proposes ambassadors strategies
- coordinates Marketing and Ambassador to get more focused strategies;
- nominates the regional Storyteller which takes care of event reports;
- coordinates regional groups;
- monitors the regional Ambassadors groups.
solves over groups issues
- tracks and solve each issue due to a overlay work flow;
- tracks and solve issues amongst people.
coordinates groups tasks
- tracks and follows the outreach release tasks;
- nominates the representative for the outreach at readiness meetings;
finds solutions for sharing people amongst groups when workloads required
- when needed organizes a team of users assigned to a task;
- nominates the representative of that working group;
- sets a deadline within which the work has to be done.
- manages priorities amongst groups that need to share resources;
- monitors the work in progress.
requires and analyze metrics for the outreach activities
- selects which metrics are needed to track the work flow;
- gets the people aware of the results of the metrics;
- reports the results of the activity to the Council;
- nominates the Council representative;
- documents the state of the OS;
- establishes which tools are helpful to reach this goal;
- keeps updated the results by period.
proposes groups improvements and coordinates them
- evaluates improvements coming fro the base of the contributors;
- creates the tasks for the ones accepted;
- sets a deadline for the final results;
- nominates a coordinator for the task;
leads outreach efforts
- if requested FOSCo representative (one or more than one) leads the efforts towards a main target(s);
- assign a part of the budget (over groups) for reaching target(s);
- nominates one of the regional treasurers to check and keep expenses within the budget;
- asks to the responsive the state of the task.
brings up engineering strategies (Engineering is FESCo's business and the overall strategy is up to the council)
- keeps the groups updated about the Engineering strategies and plans.
- get regulars report from FESCo and Council about the Engineering part of the Project;
- nominates the wrangler.
gets in touch with the Council for over outreach issues
- asks to the Council for each question in which FOSCo has not any mandate.
- in the case Council gives a mandate to FOSCo, opening a task to regulate it;
- nominates a representative for the task;
- give a deadline for the task to be done;
- track the status of the task.
supports Fedora worldwide
- In the case it needed a over group coordination at any event, one of the members of FOSCo will be appointed for leading the efforts.
organizes a FAD with team leaders to be held once per year
- Select which kind of FAD will be held (hangouts, IRC, face to face);
- assign an organizer;
- allocates a budget;
coordinates the Ambassadors program and Mentors programs
- Because of the FAMSCo dissolution FOSCo will keep all the FAmSCo tasks:
- ticketing system (until it will be ported to pagure);
- mentoring program;
- actual open tickets.
keeps updated, clear and simple all the groups policies
- checks and keeps updated policies of all the groups;
- acts towards the harmonization of the policies.
verifies conditions to bring on board other groups
- checks availability of websites;
- checks availability of G11n;
- checks availability of other groups and SIGs;
- integrates the committee making available the seats as needed.
The first committee is composed by:
- Appointed members
- Fedora Community Action and Impact Coordinator
- Fedora Project Leader (only if necessary and he/she wants to)
- 4 from the regions (appointed by the regional ambassadors communities)
- 1 from the design team
- 1 from marketing
- 1 from CommOps
- 1 from docs
|Group||Coordinator||Typology||duration of the appointment|
|FPL||representative||duration of the FPL appointment|
|FCAIC||representative||duration of the FCAIC appointment|
|Ambassadors||EMEA representative||four releases|
|Ambassadors||LATAM representative||four releases|
The first committee (only this time nominated by FAmSCo) is composed by few groups with the task of fixing the starting issue and getting ready to integrate other groups (at first G11n and Websites at first which signed up already) spreading the invitation in the Mailing Lists and following the discussions will ensue.
In the case of lack of quorum, decisions in FOSCo can be made through a process known as "lazy approval", in which general consent is assumed unless valid objections are raised.
Decision making is done on a +1 / +0 / -1 system in FOSCo meetings or trac tickets. Votes casted in a meeting will be aggregated and added to the trac ticket by the minutes keeper.
The timeframe for voting is seven days. If no negative votes (-1) are recorded within this timeframe, the proposal passed, even if there was no quorum.
In the event that there IS a negative vote by any member, that member must explain their thinking or logic behind their vote within the seven days timeframe.
FOSCo will revisit the topic again and decide how to proceed. FOSCo members are free to change their earlier votes if they consider the concerns that have been brought up valid. This time, simple majority is required, that means at least six positive votes (+6), or less positive votes with no negative votes (-1).
When consensus can't be reached, FOSCo may ask the Fedora Council to decide on a resolution. Such a request can be made when issues leading to negative votes are outstanding and all FOSCo members agree that the FOSCo itself is deadlocked, or if the dispute is unresolved after fourteen days and a simple majority of FOSCo members are in favor of the request.
- Nominates a Chair and a vice-chair as regulated in the FAmSCo rules;
- nominates its representative to get in touch with the Council;
- nominates its representative to get in touch with FESCo;
- Keeps updated the FOSCo-related pages of the wiki;
- Bring other goups on board;
- use the channel #fedora-outreach for the IRC communications;
- opens a ticket in infra for its own Mailing list and ticketing system;
- meets each week and makes aware of the logs.