Council/council-docs
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

Remove mindshare and fesco they are in other repos

Browse source
This commit is contained in:
Brian (bex) Exelbierd 2018-09-27 12:47:22 +02:00
parent f86710336f
commit 9f57eefa6d
10 changed files with 0 additions and 263 deletions
Download patch file Download diff file Expand all files Collapse all files

16
fesco/antora.yml
View file

@ -1,16 +0,0 @@
# Name will be mostly visible in the URL. Treat it as an indentifier.
# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page)
name: fesco
# Title will be visible on the page.
title: FESCo
# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version.
version: master
# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise.
start_page: ROOT:index
# This lists all the menu definitions of your component.
nav:
- modules/ROOT/nav.adoc

1
fesco/modules/ROOT/nav.adoc
View file

@ -1 +0,0 @@
* xref:teams.adoc[Technical Teams]

37
fesco/modules/ROOT/pages/index.adoc
View file

@ -1,37 +0,0 @@
Fedora Engineering Steering Committee
=====================================
[.lead]
FESCo is the Fedora Engineering Steering Committee. It is a fully community
elected body and represents the technical leadership in Fedora.
Overall Mission
---------------
FESCo handles the process of accepting new features, the acceptance of new
packaging sponsors, Special Interest Groups (SIGs) and SIG Oversight, the
packaging process, handling and enforcement of maintainer issues and other
technical matters related to the distribution and its construction.
Common tasks and responsibilities
---------------------------------
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
* 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
More Info
---------
You can find further information about FESCo, its members, and its policies
on the
https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo wiki pages]

3
fesco/modules/ROOT/pages/teams.adoc
View file

@ -1,3 +0,0 @@
= Technical Teams in Fedora
* xref:modularity:ROOT:index.adoc[**Fedora Modularity**] — Modularity introduces an optional Modular repository that provides additional versions of software on independent lifecycles.

16
mindshare/antora.yml
View file

@ -1,16 +0,0 @@
# Name will be mostly visible in the URL. Treat it as an indentifier.
# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page)
name: mindshare
# Title will be visible on the page.
title: Fedora Mindshare
# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version.
version: master
# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise.
start_page: ROOT:index
# This lists all the menu definitions of your component.
nav:
- modules/ROOT/nav.adoc

BIN
mindshare/modules/ROOT/assets/images/Screenshot_from_2017-09-22_23-33-02.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 77 KiB

2
mindshare/modules/ROOT/nav.adoc
View file

@ -1,2 +0,0 @@
* xref:teams.adoc[Mindshare Teams]
* xref:advocate.adoc[Advocate]

96
mindshare/modules/ROOT/pages/advocate.adoc
View file

@ -1,96 +0,0 @@
== WHAT IS A FEDORA ADVOCATE?
Advocates are passionate contributors who want to participate in community events, represent Fedora and help grow the user and contributor community. Advocates are people who love spreading knowledge about their area of interest in Fedora. Many advocates also organize release parties where they share information about *What's new in Fedora* . Advocates also help new contributors join and hack on any of the subprojects at meetups and Fedora Activity Days (FADs).. Advocates come from all parts of the project and represent contributors from all areas, technical and non-technical.
== WHAT PURPOSE DO THEY SOLVE?
Organize Fedora participation at events
* Foster Fedora contributors and encourage contribution and usage
* Promote Fedora and cross-community interaction
* Hold calendar events like release parties
* Promote Fedora technology at local user groups with talks etc…
== WHAT TO MAKES A GREAT FEDORA ADVOCATE?
Fedora Advocates tend to be people who are:
* people who are already contributors and users of Fedora. Advocates are adding to their current contribution, not starting out with Fedora. This allows you to focus on community building in your area of expertise and interest. If you’re brand new to the project, becoming an Advocate is most likely not a good first step. Start with contribution in other areas first.
* friendly and approachable. They like working with and talking to others, especially in person or 1:1 electronically. People are the key. Everything that we do -- events, budgets, swag, blogging -- it's all done as an attempt to make personal connections with folks who either want to use or contribute to Fedora.
* wanting to lead a regional or locally focused community or start one. You should be eager and happy to work with Fedora Ambassadors to learn more about the project.
* the fabric of the community outreach effort. You are expected to collaborate and work with people in your local area, including colleges, universities, professional groups or meetups, and other places where like-minded individuals tend to congregate. You are the face of Fedora in your area.
== JOINING
Joining the Advocates is super-easy. Just hold an event. Really, that’s it. Details on how to do that and advice for getting started are below.
You should seriously consider joining two mailing lists.
* The Ambassadors Mailing list. This list is where the ambassador and advocate groups talk and plan events. Events are announced, planned and improved on this list. This list helps you know what is going on that you might want to help with and shares ideas you might want to copy and modify for your area. Talking to a local Ambassador directly although a nice approach puts you in contact with one person who can be busy. By talking to the whole community you increase your chance of help and collaboration.
* The mindshare-announce list. This low volume list will help you know what is going on in Fedora that relates to marketing and community growth. The Mindshare committee, which approves event requests also posts their meeting minutes here.
Once you’ve done your first event, we’ll add you to the list of advocates by putting you into the advocates FAS group.
== GETTING STARTED
Make your first projects small ones that are well-defined. Many advocates start out by:
* Start with a Fedora Calendar Event such as a Release Party. This will give you the chance to learn the process of hosting events and communicating with the Ambassadors and Mindshare.
* Joining an existing event and helping out. This is easy to do if your monitoring the mailing list.
* Teaming up with a Fedora Ambassador. It's great to have Ambassadors by your side, they can help you plan and execute your event. They also have lots of experience with what works and what doesn’t and they may be familiar with different parts of the project than you are.
In all cases, thing about what your community is interested in and focused on. Fedora has multiple editions and objectives and they are all great stories to tell and great technology. Pick the one that makes the most sense to your and your community. For some people, focussing on the work of a specific subproject makes the most sense. If your community is focused on a specific language stack, etc. talk about that.
== HOLDING AN EVENT
When you’re ready to hold an event, you need to do a few simple things:
. Open a ticket in the Mindshare Issue Tracker and let people know about your event. If your event needs financial or swag support (see below) this is a crucial (and mandatory) first step.
. Send an email to the ambassadors mailing list and let the world know what you’re planning. Ambassadors and others may have suggestions or advice that can improve your event. This also lets you find others who may want to help you with your event.
. Hold your event. Be awesome!
. Write an event report. An event report lets the community know what happened and how it went. Ideally your report will be shared on the Fedora Community Blog, but posting it on your own blog and the Fedora Planet is fine too. If your even requires financial or swag support (see below), this is mandatory.
. "Lather. Rinse. Repeat." as your shampoo bottle says. Do it again and again and keep the momentum going.
== GETTING FINANCIAL OR SWAG SUPPORT
The goal of an event is the spread knowledge and attract users and contributors to Fedora. We realize that sometimes you need swag (such as stickers) or money to help make this possible. The Advocate role is designed with the idea of easy to accomplish events in mind. Our Fedora Ambassadors (which you are free to join) also do the larger more involved events.
Therefore, Advocates are limited in what they can request. When you are planning for an event you should think about using Fedora Stickers (we have lots of designs and will typically send 50 stickers) and a budget of $100 or less. If you need more, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for the larger budget. We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event, however we tend to restrict the money to no more than $25 being spent on travel and none being used to produced swag. The balance is typically spent on food,meeting space charges, etc.
To request support do this:
. Make sure the ticket you opened with Mindshare above contains your budget request and is detailed as to how you want to use it. There is a https://pagure.io/mindshare/new_issue?title=[Event%20Name]at[Place]&content=Change%20%22type%22%20to%20advocate%20and%20start%20filling[template] in the repository to help you. Use it.
. Wait for Mindshare to make a decision. Our goal is to decide on events within one calendar week. However, you should have as much lead time as possible as there may be questions from the committee or unforeseeable delays. Mindshare will typically respond with:
.. Approved: GO FOR IT! Your event is approved. We want you to be successful.
.. Questions/Suggestions: We are a bit confused or have some questions and ideas. We may also suggest different ways to use your budget or that you work with an Ambassador. In some cases we will want to make sure you’re well versed in the technology you want to represent. Respond to these concerns to get a final decision.
.. Declined: There are various reasons why we can’t support your event. We hope to never have to decline an event and instead that we can work with you to make it a success.
. Do It! Hold the event and save your receipts.
. Write your report. Link your report to your ticket.
. Submit a reimbursement request to the Fedora Budget Pagure. Upload your receipts in PDF format and fill in the reimbursement details requested in the template. Reimbursements are typically paid within 2 weeks.
== WRITING YOUR EVENT REPORT
The work of Advocates is often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance. The report is a general walkthrough of an event which gives the region an idea of what's new and any problems which may have happened.
Reporting can be done in many ways. Here's are a couple of commonly used methods for sharing the event report with the community:
. *Community Blog* : Advocates can sign in to the Wordpress instance of Community Blog using your FAS Credentials by following this http://communityblog.fedoraproject.org/wp-admin/[link^]. Once inside, you can create a new post where you can draft your experience. After you are done, subscribe to https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/[ CommOps list^] and share the link of your draft. Politely ask if somebody can approve your post after a review. Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[ Release Party Blog post^].
. *Your own Blog* : If you have been maintaining your own blog, you can post it there as well. To extend the reach of audience, Advocates may syndicate their blog to Fedora Planet. For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check this^]
Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.^]

88
mindshare/modules/ROOT/pages/index.adoc
View file

@ -1,88 +0,0 @@
= 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
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
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
image::Screenshot_from_2017-09-22_23-33-02.png[Mindshare Structure,100%,]
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: *Jared Smith* (https://fedoraproject.org/wiki/User:Jsmith[jsmith]) (_f27-f28_)
* Elected Representative: *Sumantro Mukherjee* (https://fedoraproject.org/wiki/User:Sumantrom[sumantrom])(_f28-f29_)
* FCAIC: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex])
* Ambassador Representative: FAmA *Robert Mayr* (https://fedoraproject.org/wiki/User:Robyduck[robyduck]) - _ad interim_
* Ambassador Representative: FAmA *Nick Bebout* (https://fedoraproject.org/wiki/User:Nb[nb]) - _ad interim_
* Marketing Representative: *Eduard Lucena* (https://fedoraproject.org/wiki/User:X3mboy[x3mboy])
* CommOps Representative: *Justin W. Flory* (https://fedoraproject.org/wiki/User:Jflory7[jflory7])
* Design & Web Representative: *Maria Leonova* (https://fedoraproject.org/wiki/User:Mleonova[mleonova])
* Docs Representative: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex]) - _ad interim_
== Contact Info
=== 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.
== IRC / Telegram
Mindshare Committee members are present in the *#fedora-mindshare* IRC channel on the Freenode 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].
== Pagure ==
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.
== 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.

4
mindshare/modules/ROOT/pages/teams.adoc
View file

@ -1,4 +0,0 @@
= Outreach Teams in Fedora
* xref:commops:ROOT:index.adoc[**Fedora Community Operations (CommOps)**] — Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.
* xref:fedora-docs:ROOT:index.adoc[**Fedora Docs**] — The group behind this very documentation site. Includes contributors' guidelines to Fedora Docs.