📝 index.adoc: Introduce partials, refresh for 2023
This commit is contained in:
parent
dac295a32e
commit
82d5005373
2 changed files with 129 additions and 98 deletions
|
|
@ -1,38 +1,40 @@
|
|||
= Fedora Mindshare Committee
|
||||
include::ROOT:partial$attributes.adoc[]
|
||||
|
||||
image::mindshare-logo.png[Mindshare Logo,75%,float=right]
|
||||
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 optimized and standardized communication.
|
||||
It consists of mostly appointed, but also elected members.
|
||||
= {team_name}
|
||||
|
||||
image::mindshare-logo.png[{team_name} logo,75%,float=right]
|
||||
|
||||
{team_summary}
|
||||
|
||||
|
||||
[[responsibilities]]
|
||||
== Responsibilities
|
||||
|
||||
Mindshare takes care of some responsibilities held by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed.
|
||||
These include:
|
||||
{team_name} takes care of some responsibilities held by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed.
|
||||
We track link:{team_issue_tracker}/-/issues[ongoing work] through *Issues*.
|
||||
This ongoing work includes the following:
|
||||
|
||||
* 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.
|
||||
{team_name} 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.
|
||||
{team_name} 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.
|
||||
* {team_name} takes over all decisional responsibilities left on FAmSCo.
|
||||
Administrative responsibilities will be handled by FAmA, which will consist mainly by treasurers and FAmA admins.
|
||||
* xref:commops::index.adoc[CommOps] leads the communication between technical and outreach teams.
|
||||
* Sharing best practices:
|
||||
One of the Mindshare Committee's goals is to take down barriers or whatever is blocking sharing best practices.
|
||||
One of the {team_name}'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.
|
||||
* {team_name} 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 xref:council::fca.adoc[FCA] 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.
|
||||
{team_name} will, in collaboration with the xref:council::fca.adoc[FCA] 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 {team_name}, in order to be able and track even necessary reports the Council needs.
|
||||
|
||||
|
||||
[[decisions]]
|
||||
|
|
@ -51,23 +53,66 @@ A vote of "0" is sometimes used to indicate a disagreement but willingness to st
|
|||
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, Mindshare 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.
|
||||
In general, {team_name} conducts business in public discussion, and any Fedora project member can add more opinions and thoughts.
|
||||
It is the duty of the {team_name} to take concerns raised in this way into serious consideration, but only {team_name} members' votes are binding in the final tally.
|
||||
|
||||
|
||||
[[find-team]]
|
||||
== Where to find {team_name}
|
||||
|
||||
The {team_name} uses the following communication platforms:
|
||||
|
||||
Asynchronous:: link:{team_asynch_communication}[{team_asynch_communication}]
|
||||
Synchronous:: link:{team_synch_communication}[{team_synch_communication}]
|
||||
|
||||
The Discourse forum is best for _asynchronous_ communication.
|
||||
This means it is best for questions or topics that someone may respond to later.
|
||||
It is better for longer, threaded discussions.
|
||||
|
||||
The {team_name} Matrix room is best for _synchronous_ communication.
|
||||
This means it is best for quick feedback, like a conversation.
|
||||
It is helpful for real-time discussions or getting someone's attention more quickly.
|
||||
For convenience, the Matrix room is also bridged to an IRC channel on the LiberaChat network:
|
||||
|
||||
LiberaChat IRC web chat:: link:https://web.libera.chat/?channels=#fedora-mindshare[#fedora-mindshare]
|
||||
|
||||
|
||||
[[tickets]]
|
||||
== Ticket-based task management
|
||||
|
||||
The {team_name} operates in a ticket-based workflow.
|
||||
Our open tickets are in our link:{team_issue_tracker}[GitLab repository].
|
||||
New tasks are added as "issues" into GitLab.
|
||||
|
||||
*This is a public issue tracker*.
|
||||
If you have a privacy- or security-sensitive issue, check the _This issue is confidential_ box when creating the issue.
|
||||
|
||||
|
||||
[[meetings]]
|
||||
== Meetings
|
||||
|
||||
The {team_name} holds regular text-based meetings in a Matrix room to discuss current issues, clear through anything outstanding which can be quickly resolved, and ensure that nothing important is left in limbo.
|
||||
The meeting format is intended to be quick updates and long discussion.
|
||||
It is a good opportunity to check in with other members of the team in real-time and understand what is going on in their area, while allowing anyone in the public to observe how the {team_name} operate.
|
||||
|
||||
link:{team_meetings}[**Find our next meeting on our calendar!**]
|
||||
|
||||
The meeting minutes are published automatically https://meetbot.fedoraproject.org/[on Fedora Meetbot Logs].
|
||||
|
||||
|
||||
[[composition]]
|
||||
== Composition
|
||||
|
||||
image::Screenshot_from_2017-09-22_23-33-02.png[Mindshare Structure,100%,]
|
||||
image::Screenshot_from_2017-09-22_23-33-02.png[{team_name} Structure,100%,]
|
||||
|
||||
Mindshare has appointed and elected members, and initially there will be 9 seats:
|
||||
{team_name} has appointed and elected members, and initially there will be 9 seats:
|
||||
|
||||
* xref:council::fca.adoc[FCA] (chair)
|
||||
* Ambassadors (2 appointed members)
|
||||
* Web (appointed)
|
||||
* Website & Apps (appointed)
|
||||
* Design (appointed)
|
||||
* Docs (appointed)
|
||||
* Commops (appointed)
|
||||
* CommOps (appointed)
|
||||
* 2 elected seats
|
||||
* Mentored Project Rep
|
||||
|
||||
|
|
@ -75,114 +120,67 @@ Mindshare has appointed and elected members, and initially there will be 9 seats
|
|||
The minimum of elected representatives is two.
|
||||
Three representatives are elected when the number of seats would otherwise be even.
|
||||
|
||||
|
||||
[[members]]
|
||||
== Current members
|
||||
[[composition-members]]
|
||||
=== Current members
|
||||
|
||||
* xref:council::fca.adoc[Fedora Community Architect] (FCA):
|
||||
*Justin W. Flory* (https://fedoraproject.org/wiki/User:Jflory7[jflory7])
|
||||
*Justin W. Flory* (link:{FWIKI}/User:Jflory7[jflory7])
|
||||
* Ambassador Representative:
|
||||
*TBD*
|
||||
* Ambassador Representative:
|
||||
FAmA *Nick Bebout* (https://fedoraproject.org/wiki/User:Nb[nb])
|
||||
FAmA *Nick Bebout* (link:{FWIKI}/User:Nb[nb])
|
||||
* CommOps Representative:
|
||||
*Alberto Rodríguez Sánchez* (https://fedoraproject.org/wiki/User:Bt0dotninja[bt0dotninja / bt0])
|
||||
* Web & Apps Representative:
|
||||
*Onuralp Sezer* (https://fedoraproject.org/wiki/User:Thunderbirdtr[thunderbirdtr])
|
||||
*Alberto Rodríguez Sánchez* (link:{FWIKI}/User:Bt0dotninja[bt0dotninja / bt0])
|
||||
* Website & Apps Representative:
|
||||
*Onuralp Sezer* (link:{FWIKI}/User:Thunderbirdtr[thunderbirdtr])
|
||||
* Design Representative:
|
||||
*Máirín Duffy* (https://fedoraproject.org/wiki/User:Duffy[Duffy])
|
||||
*Máirín Duffy* (link:{FWIKI}/User:Duffy[Duffy])
|
||||
* Docs Representative:
|
||||
*Petr Bokoč* (https://fedoraproject.org/wiki/User:Pbokoc[pbokoc])
|
||||
*Petr Bokoč* (link:{FWIKI}/User:Pbokoc[pbokoc])
|
||||
* Mentored Project Representative:
|
||||
*Smera Goel* (https://fedoraproject.org/wiki/User:smeragoel[smeragoel])
|
||||
*Smera Goel* (link:{FWIKI}/User:smeragoel[smeragoel])
|
||||
* Elected Representative:
|
||||
*Madeline Peck* (https://fedoraproject.org/wiki/User:Madelinepeck[madelinepeck]) (_f37-f38_)
|
||||
*Madeline Peck* (link:{FWIKI}/User:Madelinepeck[madelinepeck]) (_f37-f38_)
|
||||
* Elected Representative:
|
||||
*Fernando F. Mancera* (https://fedoraproject.org/wiki/user:Ffmancera[ffmancera]) (_f38-f39_)
|
||||
*Fernando F. Mancera* (link:{FWIKI}/User:Ffmancera[ffmancera]) (_f38-f39_)
|
||||
|
||||
[[members-former]]
|
||||
=== Former members
|
||||
[[composition--members-former]]
|
||||
==== Former members
|
||||
|
||||
[[members-former-appointed]]
|
||||
==== Appointed
|
||||
[[composition--members-former-appointed]]
|
||||
===== Appointed
|
||||
|
||||
* CommOps
|
||||
** *F27-F28*:
|
||||
Justin W. Flory (https://fedoraproject.org/wiki/User:Jflory7[jflory7 / jwf])
|
||||
Justin W. Flory (link:{FWIKI}/User:Jflory7[jflory7 / jwf])
|
||||
* Design
|
||||
** *F27-F29*:
|
||||
Maria Leonova (https://fedoraproject.org/wiki/User:Mleonova[mleonova])
|
||||
Maria Leonova (link:{FWIKI}/User:Mleonova[mleonova])
|
||||
* Docs
|
||||
** *F27-F31*:
|
||||
Brian Exelbierd (https://fedoraproject.org/wiki/User:Bex[bex])
|
||||
Brian Exelbierd (link:{FWIKI}/User:Bex[bex])
|
||||
* xref:council::fca.adoc[FCA]
|
||||
** *F31-F37*:
|
||||
Marie Nordin (https://fedoraproject.org/wiki/User:Riecatnor[riecatnor])
|
||||
Marie Nordin (link:{FWIKI}/User:Riecatnor[riecatnor])
|
||||
* Marketing
|
||||
** *F30-F33*:
|
||||
Eduard Lucena (https://fedoraproject.org/wiki/User:X3mboy[x3mboy])
|
||||
* Web & Apps
|
||||
Eduard Lucena (link:{FWIKI}/User:X3mboy[x3mboy])
|
||||
* Website & Apps
|
||||
** *F27-F36*:
|
||||
Rick Elrod (https://fedoraproject.org/wiki/User:Codeblock[codeblock])
|
||||
Rick Elrod (link:{FWIKI}/User:Codeblock[codeblock])
|
||||
|
||||
[[members-former-elected]]
|
||||
==== Elected
|
||||
[[composition--members-former-elected]]
|
||||
===== Elected
|
||||
|
||||
** *F27-F31*:
|
||||
Jared Smith (https://fedoraproject.org/wiki/User:Jsmith[jsmith])
|
||||
Jared Smith (link:{FWIKI}/User:Jsmith[jsmith])
|
||||
** *F29-F32*:
|
||||
Sumantro Mukherjee (https://fedoraproject.org/wiki/User:Sumantrom[sumantrom])
|
||||
Sumantro Mukherjee (link:{FWIKI}/User:Sumantrom[sumantrom])
|
||||
** *F32-F33*:
|
||||
Héctor Louzao (https://fedoraproject.org/wiki/User:Hhlp[hhlp])
|
||||
Héctor Louzao (link:{FWIKI}/User:Hhlp[hhlp])
|
||||
** *F33-F34*:
|
||||
Maria Leandro (https://fedoraproject.org/wiki/User:Tatica[tatica])
|
||||
Maria Leandro (link:{FWIKI}/User:Tatica[tatica])
|
||||
** *F34-F36*:
|
||||
Till Maas (https://fedoraproject.org/wiki/User:Till[till])
|
||||
Till Maas (link:{FWIKI}/User:Till[till])
|
||||
** *F37*:
|
||||
David Duncan (https://fedoraproject.org/wiki/User:Davdunc[davdunc])
|
||||
|
||||
|
||||
[[contact]]
|
||||
== Contact info
|
||||
|
||||
There are a few different ways to get in touch with the Fedora Mindshare Committee.
|
||||
|
||||
[[contact-async]]
|
||||
=== Mailing lists
|
||||
|
||||
The Mindshare Committee uses two mailing lists: a regular discussion list and an announcement-only mailing list.
|
||||
|
||||
*https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[mindshare]* is a public discussion list.
|
||||
This is the main discussion point for the Mindshare Committee.
|
||||
The goal of the list is to either reach a decision or delegate a thread to a more appropriate location.
|
||||
|
||||
*https://lists.fedoraproject.org/admin/lists/mindshare-announce@lists.fedoraproject.org/[mindshare-announce]* is a low-traffic, announcement-only mailing list.
|
||||
This list is used for occasional updates, news, and announcements from the Committee.
|
||||
Posting privileges are limited to Mindshare Committee members.
|
||||
Consider subscribing to this list if you want to stay informed about ongoing activities within the Mindshare Committee.
|
||||
|
||||
[[contact-chat]]
|
||||
=== IRC / Telegram
|
||||
|
||||
Mindshare Committee members are present in the *#fedora-mindshare* IRC channel on the Libera.chat IRC network.
|
||||
This IRC channel is also bridged to a Telegram group for convenience.
|
||||
Messages are synchronized between the two.
|
||||
Telegram users can join https://t.me/fedoramindshare[here].
|
||||
|
||||
[[contact-tickets]]
|
||||
=== Pagure (tickets)
|
||||
|
||||
The Mindshare Committee operates in a ticket-based workflow.
|
||||
If you have an issue or task for the Mindshare Committee, open a ticket on the https://pagure.io/mindshare/issues[Pagure instance].
|
||||
This is a public issue tracker.
|
||||
If you have a privacy- or security-sensitive issue, check the _Private_ box when creating the ticket.
|
||||
|
||||
[[contact-meetings]]
|
||||
=== 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.
|
||||
|
||||
The meeting's actual schedule is every Wednesday at 17:30 UTC on https://web.libera.chat/?channels=#fedora-mindshare[IRC] and https://t.me/fedoramindshare[Telegram].
|
||||
|
||||
The meeting minutes are published automatically https://meetbot.fedoraproject.org/sresults/?group_id=mindshare&type=team[here].
|
||||
David Duncan (link:{FWIKI}/User:Davdunc[davdunc])
|
||||
|
|
|
|||
33
modules/ROOT/partials/attributes.adoc
Normal file
33
modules/ROOT/partials/attributes.adoc
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
// This is a data store of information about the Fedora Mindshare Committee.
|
||||
|
||||
// Team name:
|
||||
:team_name: Fedora Mindshare Committee
|
||||
|
||||
// Team summary:
|
||||
:team_summary: The {team_name} 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 optimized and standardized communication. It consists of mostly appointed, but also elected members.
|
||||
|
||||
// Team page URL:
|
||||
:team_url: https://docs.fedoraproject.org/en-US/mindshare-committee/
|
||||
|
||||
// Team activity status.
|
||||
// Choose from: Active, Inactive
|
||||
:team_status: Active
|
||||
|
||||
// Preferred asynchronous communication channel
|
||||
:team_asynch_communication: https://discussion.fedoraproject.org/tag/mindshare
|
||||
|
||||
// Preferred synchronous communication channel
|
||||
:team_synch_communication: https://matrix.to/#/#mindshare:fedoraproject.org
|
||||
|
||||
// Issue tracker
|
||||
:team_issue_tracker: https://gitlab.com/fedora/mindshare/home
|
||||
|
||||
// Meetings
|
||||
:team_meetings: https://apps.fedoraproject.org/calendar/mindshare/
|
||||
|
||||
// Imported from our old attributes file.
|
||||
:COMMBLOG: https://communityblog.fedoraproject.org
|
||||
:FISCALYEAR: CY23
|
||||
:FWIKI: https://fedoraproject.org/wiki
|
||||
:YEAR: 2023
|
||||
:MAJOROSVER: 37
|
||||
Loading…
Add table
Add a link
Reference in a new issue