From Fedora Project Wiki
No edit summary |
|||
| Line 3: | Line 3: | ||
= Introduction = | = Introduction = | ||
Fedora Mindshare | The Fedora Mindshare Committee represents the outreach leadership in Fedora. Mindshare aims to help outreach teams to reach their targets in a more effective way, by unifying and sharing their working process through an optimized and standardized communication. It consists of mostly appointed, but also elected members. | ||
= Responsibilities = | = Responsibilities = | ||
Mindshare | Mindshare takes care of some responsibilities hold actually by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed. | ||
These include: | These include: | ||
* Communication between teams (outreach teams rely on the work of other groups). Mindshare | * Communication between teams (outreach teams rely on the work of other groups). Mindshare ensures all information from technical teams will get out in time to all outreach teams, working out also a common strategy with Marketing of how to communicate them outside and how to manage them within all outreach teams. | ||
* Ambassadors activity: Mindshare will create templates to help ambassadors to work more effectively. Not only by providing report templates, but also by asking them once a year to compile a short survey. This can help to get real information whether an ambassador is active or not and will not result too binding. | * Ambassadors activity: Mindshare will create templates to help ambassadors to work more effectively. Not only by providing report templates, but also by asking them once a year to compile a short survey. This can help to get real information whether an ambassador is active or not and will not result too binding. | ||
* Motivate contributors to work also in other groups, providing easier access to funding and more autonomy. This challenging part will need some verifying tools (TBD) | * Motivate contributors to work also in other groups, providing easier access to funding and more autonomy. This challenging part will need some verifying tools (TBD) | ||
* Mindshare | * Mindshare takes over all decisional responsibilities left on FAmSCo. Administrative responsibilities will be handled by FAmA, which will consist mainly by treasurers and FAmA admins. | ||
* CommOps | * CommOps which is part of Mindshare takes care of the ''operations'' inside Fedora. CommOps will lead the communication between technical and outreach teams. | ||
* Sharing best practices: Mindshare | * Sharing best practices: one of the Mindshare's goals is to take down barriers or whatever is blocking sharing best practices. All teams and all regions can learn from each other and apply successful practices to their local community. | ||
* Mindshare will | * Mindshare will also try to unify ambassadors more and more, also by dropping the actual Regions. They are not helping communication and were created mostly for organizational aspects. FAmA (with treasurers) will help to sort out regional aspects and meetings, but having a unique ambassadors group will help in several ways to be more effective again. | ||
* Budget: Without regions also the (ex-)regional budgeting process | * Budget: Without regions also the (ex-)regional budgeting process changes. Mindshare will, in collaboration with the FCAIC and consequently with the Council, take care of the Fedora outreach budget (sum of the 4 regional budgets). Minor funding requests can be handled directly by FAmA and treasurers, more important expenses will go through Mindshare, in order to be able and track even necessary reports the Council needs. | ||
* Marketing as part of Mindshare will drive the other teams by providing messages, strategies and talking points for ambassadors. A good collaboration with the other teams is necessary. | * Marketing as part of Mindshare will drive the other teams by providing messages, strategies and talking points for ambassadors. A good collaboration with the other teams is necessary. | ||
= | = Making Decisions = | ||
{{side box| | |||
Consensus decision-making aims to be: | |||
* | *'''Agreement Seeking:''' A consensus decision-making process attempts to help everyone get what they need. | ||
* | *'''Collaborative:''' Participants contribute to a shared proposal and shape it into a decision that meets the concerns of all group members as much as possible. | ||
* | *'''Cooperative:''' Participants in an effective consensus process should strive to reach the best possible decision for the group and all of its members, rather than competing for personal preferences. | ||
* | *'''Egalitarian:''' All members of a consensus decision-making body should be afforded, as much as possible, equal input into the process. All members have the opportunity to present, and amend proposals. | ||
* | *'''Inclusive:''' As many [[wiktionary:stakeholder|stakeholders]] as possible should be involved in the consensus decision-making process. | ||
*'''Participatory:''' The consensus process should actively solicit the input and participation of all decision-makers | |||
— from [https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives Wikipedia on Consensus decision-making] | |||
}} | |||
Many basic decisions are made through a process known as "'''lazy approval'''", in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus. | |||
More significant decisions are made through a process of '''full consensus'''. In order to pass, these decisions need three positive votes (+3) and ''no'' negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the poposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of "0" is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation. | |||
This model matches Fedora's "Friends" foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree. | |||
In general, Mindsharel conducts business in public discussion, and any Fedora project member can add more opinions and thoughts. It is the duty of the Mindshare Committee to take concerns raised in this way into serious consideration, but only Mindshare members' votes are binding in the final tally. | |||
{{clear}} | |||
= Composition = | |||
[[File:Screenshot_from_2017-09-22_23-33-02.png|400px]] | [[File:Screenshot_from_2017-09-22_23-33-02.png|400px]] | ||
Mindshare has appointed and elected members, and initially | Mindshare has appointed and elected members, and initially there will be 9 seats: | ||
* FCAIC | * FCAIC (chair) | ||
* Ambassadors (2 appointed members) | * Ambassadors (2 appointed members) | ||
* Design & Web (appointed) | * Design & Web (appointed) | ||
| Line 52: | Line 56: | ||
* Marketing (appointed) | * Marketing (appointed) | ||
* Commops (appointed) | * Commops (appointed) | ||
* 2 | * 2 elected seats | ||
'''Note''': The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even. | '''Note''': The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even. | ||
= | == Current Members == | ||
* Elected Representative: ''(f27-f28)'' | |||
* Elected Representative: ''(f27)'' | |||
* FCAIC: '''Brian Exelbierd''' | |||
* Ambassador Representative: | |||
* Ambassador Representative: | |||
* Marketing Representative: | |||
* CommOps Representative: | |||
* Design & Web Representative: | |||
* Docs Representative: | |||
== Contact Info == | |||
TBD | |||
Mindshare will probably use a public Mailing List only. | |||
== Meetings == | |||
Mindshare | The Fedora Mindshare Committee does hold regular public IRC meetings to discuss current issues, to clear through anything outstanding which can be quickly resolved, and to ensure that nothing important is left in limbo. All members are be expected to regularly communicate what's going on in their area, through blog posts or other public updates. | ||
Revision as of 20:32, 25 October 2017
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
It is still under construction and content may change. Do not rely on the information on this page.
Introduction
The Fedora Mindshare Committee represents the outreach leadership in Fedora. Mindshare aims to help outreach teams to reach their targets in a more effective way, by unifying and sharing their working process through an optimized and standardized communication. It consists of mostly appointed, but also elected members.
Responsibilities
Mindshare takes care of some responsibilities hold actually by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed. These include:
- Communication between teams (outreach teams rely on the work of other groups). Mindshare ensures all information from technical teams will get out in time to all outreach teams, working out also a common strategy with Marketing of how to communicate them outside and how to manage them within all outreach teams.
- Ambassadors activity: Mindshare will create templates to help ambassadors to work more effectively. Not only by providing report templates, but also by asking them once a year to compile a short survey. This can help to get real information whether an ambassador is active or not and will not result too binding.
- Motivate contributors to work also in other groups, providing easier access to funding and more autonomy. This challenging part will need some verifying tools (TBD)
- Mindshare takes over all decisional responsibilities left on FAmSCo. Administrative responsibilities will be handled by FAmA, which will consist mainly by treasurers and FAmA admins.
- CommOps which is part of Mindshare takes care of the operations inside Fedora. CommOps will lead the communication between technical and outreach teams.
- Sharing best practices: one of the Mindshare's goals is to take down barriers or whatever is blocking sharing best practices. All teams and all regions can learn from each other and apply successful practices to their local community.
- Mindshare will also try to unify ambassadors more and more, also by dropping the actual Regions. They are not helping communication and were created mostly for organizational aspects. FAmA (with treasurers) will help to sort out regional aspects and meetings, but having a unique ambassadors group will help in several ways to be more effective again.
- Budget: Without regions also the (ex-)regional budgeting process changes. Mindshare will, in collaboration with the FCAIC and consequently with the Council, take care of the Fedora outreach budget (sum of the 4 regional budgets). Minor funding requests can be handled directly by FAmA and treasurers, more important expenses will go through Mindshare, in order to be able and track even necessary reports the Council needs.
- Marketing as part of Mindshare will drive the other teams by providing messages, strategies and talking points for ambassadors. A good collaboration with the other teams is necessary.
Making Decisions
 Consensus decision-making aims to be:
— from Wikipedia on Consensus decision-making |
Many basic decisions are made through a process known as "lazy approval", in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus.
More significant decisions are made through a process of full consensus. In order to pass, these decisions need three positive votes (+3) and no negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the poposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of "0" is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation.
This model matches Fedora's "Friends" foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree.
In general, Mindsharel conducts business in public discussion, and any Fedora project member can add more opinions and thoughts. It is the duty of the Mindshare Committee to take concerns raised in this way into serious consideration, but only Mindshare members' votes are binding in the final tally.
Composition
Mindshare has appointed and elected members, and initially there will be 9 seats:
- FCAIC (chair)
- Ambassadors (2 appointed members)
- Design & Web (appointed)
- Docs (appointed)
- Marketing (appointed)
- Commops (appointed)
- 2 elected seats
Note: The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even.
Current Members
- Elected Representative: (f27-f28)
- Elected Representative: (f27)
- FCAIC: Brian Exelbierd
- Ambassador Representative:
- Ambassador Representative:
- Marketing Representative:
- CommOps Representative:
- Design & Web Representative:
- Docs Representative:
Contact Info
TBD Mindshare will probably use a public Mailing List only.
Meetings
The Fedora Mindshare Committee does hold regular public IRC meetings to discuss current issues, to clear through anything outstanding which can be quickly resolved, and to ensure that nothing important is left in limbo. All members are be expected to regularly communicate what's going on in their area, through blog posts or other public updates.