mindshare/tickets
mindshare/tickets
6
1
Fork 0
Code Issues 19 Pull requests 1 Projects Activity

🔥 Remove Fedora Docs, update README instructions

Browse source 
This commit makes two significant changes:

1. Remove all Fedora Docs files, scripts, and assets, since this is
   managed in a new repo: https://gitlab.com/fedora/mindshare/docs
2. Update `README.md` to explain the purpose of this repo, fix the link
   to the Committee documentation, use GitLab links instead of Pagure
   links, and minor restructuring for easier reading.

It also adds a `LICENSE.txt` file to make the implicit CC BY-SA 4.0
license per the Fedora Project Contributor Agreement (FPCA) an explicit
license.

Signed-off-by: Justin W. Flory (he/him) <jwf@redhat.com>
This commit is contained in:
Justin Wheeler 2023-04-12 00:09:14 -04:00
commit 1184547dbb
Signed by: jflory7
GPG key ID: 7748B15FA8FA4C7E
37 changed files with 456 additions and 1959 deletions
Download patch file Download diff file Expand all files Collapse all files

3
.gitignore vendored
View file

@ -1,3 +0,0 @@
build
cache
public

428
LICENSE.txt Normal file
View file

@ -0,0 +1,428 @@
Attribution-ShareAlike 4.0 International
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution-ShareAlike 4.0 International Public
License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution-ShareAlike 4.0 International Public License ("Public
License"). To the extent this Public License may be interpreted as a
contract, You are granted the Licensed Rights in consideration of Your
acceptance of these terms and conditions, and the Licensor grants You
such rights in consideration of benefits the Licensor receives from
making the Licensed Material available under these terms and
conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. BY-SA Compatible License means a license listed at
creativecommons.org/compatiblelicenses, approved by Creative
Commons as essentially the equivalent of this Public License.
d. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
e. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
f. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
g. License Elements means the license attributes listed in the name
of a Creative Commons Public License. The License Elements of this
Public License are Attribution and ShareAlike.
h. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
i. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
j. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
k. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
l. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
m. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part; and
b. produce, reproduce, and Share Adapted Material.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. Additional offer from the Licensor -- Adapted Material.
Every recipient of Adapted Material from You
automatically receives an offer from the Licensor to
exercise the Licensed Rights in the Adapted Material
under the conditions of the Adapter's License You apply.
c. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
b. ShareAlike.
In addition to the conditions in Section 3(a), if You Share
Adapted Material You produce, the following conditions also apply.
1. The Adapter's License You apply must be a Creative Commons
license with the same License Elements, this version or
later, or a BY-SA Compatible License.
2. You must include the text of, or the URI or hyperlink to, the
Adapter's License You apply. You may satisfy this condition
in any reasonable manner based on the medium, means, and
context in which You Share Adapted Material.
3. You may not offer or impose any additional or different terms
or conditions on, or apply any Effective Technological
Measures to, Adapted Material that restrict exercise of the
rights granted under the Adapter's License You apply.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material,
including for purposes of Section 3(b); and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the “Licensor.” The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.
Creative Commons may be contacted at creativecommons.org.

44
README.md
View file

@ -1,23 +1,39 @@
# Fedora Mindshare Committee
Fedora Mindshare Committee
==========================
This repository is the project management and task tracker tool for the Fedora Mindshare Committee.
Ongoing work that need a resolution are tracked as **Issues** in this repository.
You can make a request to the Fedora Mindshare Committee here (issue templates are there to guide you).
Tickets are normally discussed during the Committee's regular meetings.
## [_Open a new issue here_](https://gitlab.com/fedora/mindshare/home/-/issues/new)
## What is the Fedora Mindshare Committee?
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.
You can read more about the Fedora Mindshare Committee in the [Fedora documentation](https://docs.fedoraproject.org/en-US/mindshare-committee/).
## What is this place?
The Fedora Mindshare Committee uses this repository to record ongoing work and to track issues which need a specific resolution.
Tickets are normally discussed during weekly meetings.
You can read more about the Fedora Mindshare Committee on the [Mindshare's docs' page](https://docs.fedoraproject.org/en-US/mindshare/)
## File a new ticket
To file a new ticket, open a [new issue](https://pagure.io/mindshare/new_issue).
## How to contact the Mindshare Committee
Other than this repository, you can also find the members of the Fedora Mindshare Committee in the following places:
The Fedora Mindshare Committee uses the following communication platforms:
* Mailing list: mindshare@lists.fedoraproject.org
* IRC channel: #fedora-mindshare on Libera.chat ([webchat](https://web.libera.chat/?channels=#fedora-mindshare))
* _Asynchronous_:
[discussion.fedoraproject.org/tag/mindshare](https://discussion.fedoraproject.org/tag/mindshare)
* _Synchronous_:
[matrix.to/#/#mindshare:fedoraproject.org](https://matrix.to/#/#mindshare:fedoraproject.org)
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 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_: [#fedora-mindshare](https://web.libera.chat/?channels=#fedora-mindshare)

46
build.sh
View file

@ -1,46 +0,0 @@
#!/bin/sh
image="docker.io/antora/antora"
cmd="--html-url-extension-style=indexify site.yml"
if [ "$(uname)" = "Darwin" ]; then
# Running on macOS.
# Let's assume that the user has the Docker CE installed
# which doesn't require a root password.
echo ""
echo "This build script is using Docker container runtime to run the build in an isolated environment."
echo ""
docker run --rm -it -v "$(pwd):/antora" $image $cmd
elif [ "$(expr substr "$(uname -s)" 1 5)" = "Linux" ]; then
# Running on Linux.
# Check whether podman is available, else faill back to docker
# which requires root.
if [ -f /usr/bin/podman ]; then
echo ""
echo "This build script is using Podman to run the build in an isolated environment."
echo ""
podman run --rm -it -v "$(pwd):/antora:z" $image $cmd
elif [ -f /usr/bin/docker ]; then
echo ""
echo "This build script is using Docker to run the build in an isolated environment."
echo ""
if groups | grep -wq "docker"; then
docker run --rm -it -v "$(pwd):/antora:z" $image $cmd
else
echo ""
echo "This build script is using $runtime to run the build in an isolated environment. You might be asked for your password."
echo "You can avoid this by adding your user to the 'docker' group, but be aware of the security implications. See https://docs.docker.com/install/linux/linux-postinstall/."
echo ""
sudo docker run --rm -it -v "$(pwd):/antora:z" $image $cmd
fi
else
echo ""
echo "Error: Container runtime haven't been found on your system. Fix it by:"
echo "$ sudo dnf install podman"
exit 1
fi
fi

BIN
logo/fedora-mindshare-logo-fullcolor-withtype.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 30 KiB

BIN
logo/fedora-mindshare-logo-fullcolor.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 17 KiB

BIN
logo/old/old-mindshare-logo-256-transparent.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 21 KiB

BIN
logo/old/old-mindshare-logo-256-white.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 21 KiB

830
logo/old/old-mindshare-logo.svg
View file

File diff suppressed because one or more lines are too long
Side by side

Before

Width:  |  Height:  |  Size: 103 KiB

14
nginx.conf
View file

@ -1,14 +0,0 @@
server {
listen 80;
server_name localhost;
location / {
root /antora/public;
index index.html index.htm;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}
}

18
preview.sh
View file

@ -1,18 +0,0 @@
#!/bin/sh
if [ "$(uname)" = "Darwin" ]; then
# Running on macOS.
# Let's assume that the user has the Docker CE installed
# which doesn't require a root password.
echo "The preview will be available at http://localhost:8080/"
docker run --rm -v "$(pwd):/antora:ro" -v "$(pwd)/nginx.conf:/etc/nginx/conf.d/default.conf:ro" -p 8080:80 nginx
elif [ "$(expr substr "$(uname -s)" 1 5)" = "Linux" ]; then
# Running on Linux.
# Fedora Workstation has python3 installed as a default, so using that
echo ""
echo "The preview is available at http://localhost:8080"
echo ""
cd ./public
python3 -m http.server 8080
fi

21
site.yml
View file

@ -1,21 +0,0 @@
site:
title: Mindshare Local Preview
start_page: mindshare-committee::index
content:
sources:
- url: .
branches: HEAD
start_path: website
ui:
bundle:
url: https://asamalik.fedorapeople.org/ui-bundle.zip
snapshot: true
default_layout: with_menu
output:
clean: true
dir: ./public
destinations:
- provider: archive
runtime:
fetch: true
cache_dir: ./cache

16
website/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-committee
# Title will be visible on the page.
title: Mindshare Committee
# 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
website/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

BIN
website/modules/ROOT/assets/images/infographics/2019-achievements.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 255 KiB

BIN
website/modules/ROOT/assets/images/mindshare-logo.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 30 KiB

21
website/modules/ROOT/nav.adoc
View file

@ -1,21 +0,0 @@
* xref:teams.adoc[Mindshare Teams]
* xref:advocate.adoc[Advocate Program]
* xref:contributor_recruitment/index.adoc[Contributor Recruitment]
* Attending and Holding Events
** xref:release-parties.adoc[Holding a Release Party]
** xref:covid19-guidance.adoc[COVID-19 Guidance]
** xref:small-events.adoc[Small Events ($150)]
** xref:medium-events.adoc[Medium Events ($1000)]
** xref:large-events.adoc[Large Events]
** xref:swag-only-requests.adoc[Swag-only Events]
** xref:event-report-policy.adoc[Event Report Policy]
* Committee Procedures
** xref:procedures/swag.adoc[Creating and Ordering Swag]
** xref:procedures/meetbot.adoc[Meetbot Script]
** xref:procedures/new-member.adoc[Membership Changes]
** xref:procedures/mentored_project_rep.adoc[Mentored Project Representative]
** xref:procedures/quarterly_report.adoc[Quarterly Report]
** xref:procedures/council_rep.adoc[Council Representative]
** xref:procedures/limesurvey.adoc[LimeSurvey]
* Infographics
** xref:infographics/2019.adoc[2019]

188
website/modules/ROOT/pages/advocate.adoc
View file

@ -1,188 +0,0 @@
= Advocate Program
== 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 Makes A Great Fedora Advocate?
Fedora Advocates tend to be 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 one-on-one in person or electronically.
They realize that people are the key element of successful Open Source projects.
Everything that we do -- events, budgets, swag, blogging -- it's all done 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 which you may not have contributed to before.
* 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 also consider joining these two mailing lists:
* The link:https://lists.fedoraproject.org/archives/list/ambassadors@lists.fedoraproject.org/[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 link:https://lists.fedoraproject.org/archives/list/mindshare-announce@lists.fedoraproject.org/[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.
[NOTE]
Once you’ve done your first event, we’ll add you to the list of advocates by putting you into the advocate's FAS group, and you will be awarded with the fabulous link:https://badges.fedoraproject.org/badge/fedora-advocate[Fedora Advocate Badge].
== Getting Started
Make your first projects small ones that are well-defined.
Many advocates start out by:
* holding 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, think about what your community is interested in and focused on.
Fedora has multiple editions and objectives and they are all great technologies and great stories to tell.
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 link:https://pagure.io/mindshare/issues[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 event requires financial or swag support (see below), this is mandatory.
Update your event ticket with the link of the event report.
. "Lather. Rinse. Repeat." as your shampoo bottle says.
Do it again and again and keep the momentum going.
== Getting Swag or Financial 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, buttons and pins) 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 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 a 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, 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 template in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository] to help you.
You need to select it from the `Type` drop down.
The template is named **advocate**.
Please 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.
Shipping also takes time, so allow a lot of it, especially if the import process in your country is long.
+
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.
. If you've asked for swag, please submit a **swag-shipment** request in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Do It! Hold the event and save your receipts.
. Write your report.
Link your report to your ticket.
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided 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 summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
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* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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 out this 'how to'.]
Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

52
website/modules/ROOT/pages/contributor_recruitment/current_focus.adoc
View file

@ -1,52 +0,0 @@
= Current contributor recruitment focus
Fedora always welcomes new contributors in any capacity, but there are certain areas we focus on at a particular time.
This serves two purposes: it gives existing contributors a focused set of areas to keep in mind and it helps drive people who want to contribute _somehow_ a guided suggestion.
== Diversity & Inclusion team
*What they do:*
The https://docs.fedoraproject.org/en-US/diversity-inclusion/[Diversity & Inclusion] team works across the project to help foster diversity and inclusion in the community. They work toward this by:
* Creating content and organizing events
* Supporting community-building and engagement activities
* Supporting programs that build diversity & inclusion in FOSS communities
*What they need:*
The D&I team needs:
* Stuff
* Other stuff
*How to contact them:*
* *IRC:* `#fedora-diversity` on Libera.chat
* *Telegram*: https://t.me/fedoradiversity[fedoradiversity] (bridged to IRC)
* *Mailing list:* https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/[diversity@lists.fedoraproject.org]
== Design team
*What they do:*
The https://fedoraproject.org/wiki/Design[Design] team is Fedora's in-house design agency.
They provide arwork, UX, usability, and general design services to the Fedora project.
*What they need:*
The Design team needs:
* Things
* More things
*How to contact them:*
* *IRC:* `#fedora-design` on Libera.chat
* *Mailing list:* https://lists.fedoraproject.org/archives/list/design-team@lists.fedoraproject.org/[design-team]
== What about other teams?
If the teams above aren't a good fit for someone you're talking to, there are a few other resources:
* https://fedoraproject.org/easyfix/[Easyfix]
* https://whatcanidoforfedora.org/[What can I do for Fedora?]
WARNING: These resources are not actively updated at the moment, so the information may be out-of-date.

25
website/modules/ROOT/pages/contributor_recruitment/index.adoc
View file

@ -1,25 +0,0 @@
= Contributor Recruitment
Part of keeping Fedora a vibrant, healthy community is bringing new contributors on board.
One way we can do this is to have our presence at events focus on recruiting contributors.
Open source events are a great way to reach people who are interested in joining a project.
The idea behind this plan is not to replace the https://communityblog.fedoraproject.org/fedora-join-is-trying-a-new-people-focused-workflow-for-newcomers/[people-focused workflow] that the Fedora Join SIG uses.
What we want is to create a "funnel" of potential contributors that the Join SIG can help bring into the Fedora community.
In order to give people a focused area, we highlight a few teams that are a link:current_focus[current area of focus].
== Events
The primary goal of Fedora's presence at conferences and other large events should be contributor recruitment.
This does not mean that we can't do general messaging, but that will not be the focus or how success is measured.
We should, of course, continue to speak to existing users about the shiny new technical features in the latest release.
The "How to organize an event" page will soon be updated with specific guidance.
== Online campaigns
We encourage teams that are looking for new contributors to submit Fedora Magazine articles describing their current work, and areas they need help with.
As an example, see Adam Šamalík's https://fedoramagazine.org/contribute-to-fedora-magazine-2/[Contribute to Fedora Magazine article].
In addition we can use social media channels to promote these articles.
Teams can work with the https://pagure.io/design[Fedora Design team] to create images that can be used to promote recruitment.

69
website/modules/ROOT/pages/covid19-guidance.adoc
View file

@ -1,69 +0,0 @@
= In Person Event Guidance Related to Covid-19
== Overview
NOTE: SUBJECT TO CHANGE
This page holds COVID-19 related guidance for in person events. This applies to Fedorans who are receiving Fedora funding related to events. By receiving funds related in in person events, you are agreeing to the Terms posted at the bottom of this page. The state of the virus is ever changing, so take this information as a general guideline and not hard fact. Feel free to direct any questions to the Mindshare Committee. Contact the Mindshare Committee through chat in https://matrix.to/#/#mindshare:fedoraproject.org[#fedora-mindshare] or by https://pagure.io/mindshare/new_issue[opening a ticket] on the Mindshare repo.
To learn more about requesting funds for Fedora related events, take a look at the https://docs.fedoraproject.org/en-US/mindshare-committee[Mindshare Committee docs].
== What you need to know
=== What is an event?
For the purpose of this page, an event is any internal (Fedora contributors), external (collaborations, partners, neighbor communities), or a mix of both internal/external gathering of people that takes place in person.
This is for all Fedora related events regardless of size, location/region, audience (internal, external), or type (Fedora hosted events or third party events).
=== How will Mindshare evaluate what events to fund?
This is the part that is ever-changing. As we have witnessed, COVID-19 seems to spread, and then we suppress it some, and then evolves and spreads again. Hopefully we will soon see developments that can neutralize COVID-19, or significantly decrease the severity. Until that time, we have to remain flexible.
This means evaluating event funding requests on a case-by-case basis. The Fedora Project must comply with all applicable laws and regulations for events that we sponsor and/or fund.
In order for the Mindshare Committee to make a decision about event related funding the following information will be required along with usual info. Please submit this information when https://pagure.io/mindshare/new_issue[opening an event related ticket] on the Mindshare Committee repo. See below for details.
. Event website
. Specific COVID-19 safety measures that the Event will be implementing
. Approximate number of attendees
. Country where event is taking place
. Will your travel to/from the event bring you across a Country border?
. Local official COVID-19 guidance
=== Safety requirements
Every event is encouraged to follow the highest possible safety standards for the protection of all participants. For example:
* Adherence to third party or venue safety measures that are required.
* Understanding of and adherence to government requirements.
* Vaccination requirements.
* Communication of link:Terms[Terms] to participants of Fedora organized events
Every individual should be aware of and are encouraged to follow the highest possible safety standards for the protection of all participants. For example:
* Adherence to requirements related to traveling and any costs associated(i.e. testing, isolation periods, documentation etc).
* If you become sick with COVID-19 near the time of the funded event, you must test negative before traveling to or participating in any Fedora related events.
== Terms
By receiving funding related to in person events, you agree to the following:
While onsite, you agree to comply with all laws and rules with regard to public health including social distancing protocols and face mask requirements. You acknowledge the health risks associated with the novel coronavirus (COVID-19) outbreak, and the risk of exposure or infection by COVID-19.
Neither Fedora, the event venue, the event organizer, or any of their respective parents, affiliates, sponsors, shareholders, employees, agents, officers, directors, successors, or assignees will be liable for any injury or illness, however caused, arising from, or in any way relate to COVID-19 in connection with the event.
You assume any and all risk, whatsoever, related to any Fedora or Fedora-related event, and release and discharge Fedora, their sponsors, and their agents from any liability to the fullest extent allowed by the law.

44
website/modules/ROOT/pages/event-report-policy.adoc
View file

@ -1,44 +0,0 @@
= Event Report Policy
This page documents the Event Report Policy for any event funded by the Fedora Project.
Every funded event requires an event report.
This page documents expected outcomes and consequences when an event organizer does not write an event report.
== After 30 days
Event reports more than 30 days (about a month) late result in the following:
. The contributor is not reimbursed for any event expenses until the report is complete.
. The contributor is unable to solely sponsor any additional events or request swag.
== After 90 days
Event reports more than 90 days (about 3 months) late result in the following:
. All 30-day consequences listed previously
. The contributor is not allowed to take a leadership position in organizing events until they provide the missing event report and xref:reestablish-activity[re-establish their activity].
. The contributor is ineligible for any advance funding for travel funding/requests until this is resolved.
== After 120 days
After 120 days, the event report is no longer required as it probably has limited value.
Event reports more than 120 days (about four months) late result in the following:
. All 90-day consequences listed previously
. The contributor is not allowed to take a leadership position in organizing events until they xref:reestablish-activity[re-establish their activity].
. The contributor is ineligible for any advance funding for travel funding/requests for one of the following, whichever is longer:
.. 14 months from the date of the original event, *OR*
.. 6 months from the date they have re-established their activity in the project.
. The contributor is removed from the roster of active xref::advocate.adoc[Advocates], if applicable.
They are not allowed to officially represent the Fedora Project until they re-establish their activity in the project, described above.
[[reestablish-activity]]
== Re-establish project activity
Re-establishing activity is a conversation, not an algorithm.
It is generally met by being a helper at other people's events or otherwise showing the Mindshare Committee they are actively involved in Fedora SIGs or other online events.
Mindshare strongly considers a person's history and unique circumstances.

120
website/modules/ROOT/pages/index.adoc
View file

@ -1,120 +0,0 @@
= Mindshare
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.
== 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:
* 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.
* xref:commops:ROOT:index.adoc[CommOps] leads 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.
== 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)
* Web (appointed)
* Design (appointed)
* Docs (appointed)
* Commops (appointed)
* 2 elected seats
* Mentored Project Rep
*Note:* The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even.
== Current members
* Fedora Community Action & Impact Coordinator (FCAIC): *Justin W. Flory* (https://fedoraproject.org/wiki/User:Jflory7[jflory7])
* Ambassador Representative: *TBD*
* Ambassador Representative: FAmA *Nick Bebout* (https://fedoraproject.org/wiki/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])
* Design Representative: *Máirín Duffy* (https://fedoraproject.org/wiki/User:Duffy[Duffy])
* Docs Representative: *Petr Bokoč* (https://fedoraproject.org/wiki/User:Pbokoc[pbokoc])
* Mentored Project Representative: *Smera Goel* (https://fedoraproject.org/wiki/User:smeragoel[smeragoel])
* Elected Representative: *Madeline Peck* (https://fedoraproject.org/wiki/User:Madelinepeck[madelinepeck]) (_f37-f38_)
* Elected Representative: *Fernando F. Mancera* (https://fedoraproject.org/wiki/user:Ffmancera[ffmancera]) (_f38-f39_)
=== Former members
* Marketing
** *F30-F33* Eduard Lucena (https://fedoraproject.org/wiki/User:X3mboy[x3mboy])
* Docs
** *F27-F31*: Brian Exelbierd (https://fedoraproject.org/wiki/User:Bex[bex])
* CommOps
** *F27-F28*: Justin W. Flory (https://fedoraproject.org/wiki/User:Jflory7[jflory7 / jwf])
** *F27-F29*: Maria Leonova (https://fedoraproject.org/wiki/User:Mleonova[mleonova])
* Web & Apps
** *F27-F36*: Rick Elrod (https://fedoraproject.org/wiki/User:Codeblock[codeblock])
* Elected
** *F27-F31*: Jared Smith (https://fedoraproject.org/wiki/User:Jsmith[jsmith])
** *F29-F32*: Sumantro Mukherjee (https://fedoraproject.org/wiki/User:Sumantrom[sumantrom])
** *F32-F33*: Héctor Louzao (https://fedoraproject.org/wiki/User:Hhlp[hhlp])
** *F33-F34*: Maria Leandro (https://fedoraproject.org/wiki/User:Tatica[tatica])
** *F34-F36*: Till Maas (https://fedoraproject.org/wiki/User:Till[till])
** *F37*: David Duncan (https://fedoraproject.org/wiki/User:Davdunc[davdunc])
* FCAIC
** *F31-F37*: Marie Nordin (https://fedoraproject.org/wiki/User:Riecatnor[riecatnor])
== 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 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].
== 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.
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].

3
website/modules/ROOT/pages/infographics/2019.adoc
View file

@ -1,3 +0,0 @@
= 2019 Mindshare Team Achievements
image::infographics/2019-achievements.png[2019 achievements,100%]

56
website/modules/ROOT/pages/large-events.adoc
View file

@ -1,56 +0,0 @@
= Holding or Attending a Large Event
While anyone can hold or attend a large Fedora-related event, these events are typically done by experienced Fedora contributors and or existing Fedora Ambassadors.
A large event is one where the budget is over $1000 or the event is generally larger or more complicated.
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
When preparing your ticket, keep these things in mind:
+
* Be clear in what you hope to accomplish and why the event is good for Fedora.
* Help the Mindshare Committee understand how you are qualified to help make this a success.
You may want to talk about your experience, or contribution history.
* Think about how you will use the budget and what kind of swag support, if any, will help you bue successful.
We like to see the budget spent directly on the event or attendance and not on swag production.
If you need more budget, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for a larger budget.
We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event.
. Monitor your ticket for questions from the Committee.
These tickets will often attract questions from the Committee.
. Expect discussion about your ticket to start fairly quickly.
Once all the questions are answered, a vote will be called for.
The ticket needs to get 3 +1s and no -1s in eleven days.
When this happens, a committee member will update the ticket with an approved message.
If all committee members vote sooner, the ticket can be approved sooner.
The goal of the eleven day period is to ensure that we have at least one meeting after the discussion period (allowing for holidays, etc.).
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
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* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

54
website/modules/ROOT/pages/medium-events.adoc
View file

@ -1,54 +0,0 @@
= Holding or Attending a Medium Event
While anyone can hold or attend a medium Fedora-related event, these events are typically done by experienced Fedora contributors and or existing Fedora Ambassadors.
A medium event is one where the budget is under $1000.
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
When preparing your ticket, keep these things in mind:
+
* Be clear in what you hope to accomplish and why the event is good for Fedora.
* Help the Mindshare Committee understand how you are qualified to help make this a success.
You may want to talk about your experience, or contribution history.
* Think about how you will use the budget and what kind of swag support, if any, will help you bue successful.
We like to see the budget spent directly on the event or attendance and not on swag production.
If you need more budget, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for a larger budget.
We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event.
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
The ticket needs to get 3 +1s and no -1s in eleven days.
When this happens, a committee member will update the ticket with an approved message.
If all committee members vote sooner, the ticket can be approved sooner.
The goal of the eleven day period is to ensure that we have at least one meeting during the discussion period (allowing for holidays, etc.).
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
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* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

57
website/modules/ROOT/pages/procedures/council_rep.adoc
View file

@ -1,57 +0,0 @@
= Fedora Council Mindshare representative
As a major steering committee under the Fedora Council, Mindshare is responsible for selecting a representative that covers the community aspects of the Fedora Project.
This person is responsible for representing Mindshare as a collective and not as a single voice.
They will be required to work with all of the various groups that collaborate with Mindshare and act as a liaison between these groups and the Council.
The role will require a fair amount of time investment and good communication skills.
== Responsibilities
The following responsibilities and duties are delegated to the Mindshare representative.
To Fedora Council:
* Participate in two to three Council hackfests a year (If these events happen).
* Participate in two to three Council meetings a month as representative of the Mindshare committee (If these events happen).
* Identify synergies and collaboration opportunities with Fedora Council responsibilities, Mindshare objectives, and the Fedora Community.
* Any other normal functions of a Fedora Council member
To the Mindshare Committee:
* Participate in two to three Mindshare meetings a month.
* Share periodic updates and insight on Council tasks and priorities back to the team.
* Listen to the needs, concerns, and hopes of the Fedora Community and relay them to the Mindshare Committee.
== Duration of Service
The representative will serve in this role for two release cycles.
They may also step down before that time or the Council or Mindshare may wish to replace them.
Careful consideration of time commitments should be taken when making the selection, and the Council, Mindshare, and the representative should evaluate their effectiveness as a group on a fairly regular basis.
In the event that the representative to Mindshare needs to step down, they should make the Committee aware and the process to choose a new rep will begin.
In the event that the Mindshare Committee or the Council wish to make a change in representative, a thorough explanation of why will be required, and each situation will be handled on a case by case basis.
In the event that the Council wants to change the rep, Mindshare Committee will review and make a final decision, and vice versa.
== Nomination
This section explains how the representative is nominated and confirmed.
The selection process documented below is initiated when a rotation of representatives is motioned by the existing representative, the Mindshare committee, or the Fedora Council.
There will be a two-week nomination period for potential representatives.
Nominees can be self-nominated or nominated by other members of the Mindshare Committee with their consent.
Nominees are required to be members of the Mindshare Committee and should have a basic understanding of various Fedora sub-projects, and have sufficient time to perform the responsibilities required.
In the event that there are no nominees, the Mindshare committee will work with the Council to broaden the search message and request more time.
Should no nominees be found after that, the role will rotate among existing Mindshare members until the next representative is identified.
== Selection
After the nomination period expires, Mindshare will discuss candidates in a public meeting.
A meeting discussion provides an opportunity for the team to weigh in and share another context.
In the unlikely event that more than two nominees are interested in the representative role, we will allow for an additional week to discuss and come to a resolution as a Committee.
The selected person and the Council will be notified, and the person will start serving in that role as soon as possible.

27
website/modules/ROOT/pages/procedures/limesurvey.adoc
View file

@ -1,27 +0,0 @@
# LimeSurvey
LimeSurvey (formerly PHPSurveyor) is a free and open source on-line statistical survey web app written in PHP based on a MySQL, SQLite, PostgreSQL or MSSQL database, distributed under the GNU General Public License.
Fedora Project pays for a https://fedoraproject.limequery.com/index.php/admin[limesurvey account] which we use for surveys in the community.
## Organize a survey using Fedora's LimeSurvey
If you want to use limesurvey to do a survey, you don't need the backend access. Please use mindshare repository and open the ticket with LimeSurvey https://pagure.io/mindshare/new_issue?template=LimeSurvey[template].
## Access to the Fedora Project LimeSurvey account as an admin
https://docs.fedoraproject.org/en-US/council/fcaic/[FCAIC] has the admin credentials for the Fedora Project LimeSurvey account. If you
want to use the Fedora Project LimeSurvey account, you need to request the
FCAIC to request an account (see https://manual.limesurvey.org/Manage_users[How
to add users]).
Please send an email to fcaic@fedoraproject.org with the following information:
* Your name:
* Your FAS Id:
* Why you want to get access to the Fedora Project LimeSurvey instance:
IMPORTANT: Please note that the Fedora Project LimeSurvey account is not free (limited responses per year) and it concerns Data protection and privacy. We will follow minimum permissions required process.
## How to use LimeSurvey
Please refer to https://manual.limesurvey.org/LimeSurvey_Manual[upstream documentation] for more information.

25
website/modules/ROOT/pages/procedures/meetbot.adoc
View file

@ -1,25 +0,0 @@
= Meetbot script for meetings in #fedora-mindshare
----
.members mindshare
Meeting in 10 minutes @bexelbie @bt0dotninja @jaredsmith @nebebout @sumantro93 @x3mboy codeblock relrod
#startmeeting Mindshare
#chair jsmith sumantrom robyduck nb x3mboy bt0dotninja relrod bt0
#topic Roll Call
#topic Agenda
Proposed: Tickets: <ticket numbers>, and then Open Floor
Any suggested additions or modifications?
#topic <ticket number and title>
#link https://pagure.io/mindshare/issue/<number>
...
#topic Open Floor
#endmeeting
Don't forget to email the minutes and any notes to mindshare-announce@lists.fedoraproject.org
----

26
website/modules/ROOT/pages/procedures/mentored_project_rep.adoc
View file

@ -1,26 +0,0 @@
= Fedora Mentored Project Representative
Purpose:
--------
Fedora has been participating in fedora has been a participant of GSoC, GSoD and Outreachy. All the three are program which runs throughout the year and need attention of a dedicated person.
Can I join in as a representative?
----------------------------------
Mindshare sees value in having *selected* seat assigned to a someone who will be taking care of the following responsibilities.
* Making sure GSoC, GSoD and Outreachy applications are submitted on time.
* Coordinating with GSoC, GSoD and Outreachy admins for common work like intern's intro interviews, weekly/biweekly/monthly reports on their work, community involvement, etc.
* Identify and segregate projects suggested on mentored project issues for GSoC/Outreachy/GSoD.
* Explore similar programs that can fit in mentored projects and see if it's feasible (like rails girls).
* Market and spread news of summer coding programs with other SIG members to attract more participation.
* Be one point of contact for communication around relevant topics.
* Be involved in mindshare committee with ticket approvals, decision making, and other things that mindshare seat is expected to do.
* Attend weekly meetings (if possible).
* Retain students and effectively show the students the pathway to be long term Fedora contributor.
Support the current representative
----------------------------------
This is an *Selected* seat which means that people who are interested in working as mentored project rep can actually help the current represenative to learn "how to do things right"

9
website/modules/ROOT/pages/procedures/new-member.adoc
View file

@ -1,9 +0,0 @@
= Adding New Members
The following typically need to be done to add a new member to the committee:
* Update the link:https://admin.fedoraproject.org/accounts/group/view/mindshare[Mindshare FAS Group]
* Update the link:https://pagure.io/group/fedora-mindshare[Mindshare Pagure Group]
* Update the link:https://pagure.io/mindshare/tree/master[Mindshare Docs Page] that lists the members
* Update the meeting script above
* Add the person to the calendar invite

49
website/modules/ROOT/pages/procedures/quarterly_report.adoc
View file

@ -1,49 +0,0 @@
= Mindshare Committee Quarterly Report Doc
== Overview
The Mindshare Committee represents the outreach teams in Fedora and provides an umbrella for other non-coding teams. Mindshare has established a Quarterly Report to help round up announcements, information, and updates from these teams. This page holds documentation on our process to gather information, format, and publish the report.
== Which teams are part of the report?
All teams on the Mindshare "side" of the Fedora ecosystem are welcome to participate. Teams which have active representatives on the committee are strongly suggested to contribute to the report.
Current list of teams and how to contact them for info:
* Ambassadors (Community Outreach Revamp Team/FCAIC)
* CommOps (Rep)
* Council (Rep)
* Design (Rep)
* Diversity, Equity, & Inclusion (Discourse)
* Docs (Rep)
* Globalization (https://pagure.io/i18n/issues)
* Join SIG (join@lists.fedoraproject.org)
* Magazine (Discourse)
* Marketing (Discourse)
* Mentored Projects (Rep)
* Mindshare (This is us!)
* Podcast (IRC/Element)
* Translations (trans@lists.fedoraproject.org)
* Websites & Apps (Discourse)
== What's the process?
A ticket is opened on the Mindshare pagure to track progress for each report (i.e. "Q1 Mindshare Report - January, February, March 2022") and is triaged with the tag "quarterly-report". The owner of the ticket is the Fedora Community Action and Impact Coordinator(FCAIC).
The report is written up and edited in a HackMD file. The Mindshare Committee has team space on HackMD to store these and other Mindshare related working documents.
A template has been created in HackMD for ease of reproducibility. To access the template you need to be a part of the Mindshare team space on HackMD. How to find the template:
* Click the "..." drop down menu
* Click "+ Insert from template"
* Choose "Mindshare Quarterly Report"
* Click "Use this template".
Once the ticket and template have been set up, additions are welcome to be made through the quarter.
The last month of the quarter, two Mindshare Committee meetings will be used in some capacity to gather information from the Representatives and other members of Mindshare. Any teams that are not represented on Mindshare should be contacted with at least two weeks notice to provide any additions.
Once all the information from the various teams has been gathered, the FCAIC does any final edits and moves the report into the CommBlog wordpress. This should be done the last week of the quarter. Make sure to follow the "Writing a Community Blog post" process outlined on the CommBlog. Request that the CommBlog editors publish the post within a week or two of the last quarter end.
After the report is published to the CommBlog, a link should be added to the corresponding ticket. That ticket can then be closed as complete and a new ticket for the upcoming quarter should be opened immediately. The cycle starts again!

19
website/modules/ROOT/pages/procedures/swag.adoc
View file

@ -1,19 +0,0 @@
= Creating and Ordering Swag
To make the production and creating of swag more efficient, the Mindshare Committee has empowered the link:https://docs.fedoraproject.org/en-US/council/fcaic/[Fedora Community Action and Impact Coordinator (FCAIC)] to produce and create swag as needed to keep our inventory full.
Swag items and use will be approved by Mindshare, in general, and then the FCAIC/others will fulfill needs for the various events based on their best judgement in concert with the event owner/coordinator.
The FCAIC will consult with Mindshare if there are questions.
Anyone can open a Mindshare ticket or contact the FCAIC to suggest swag items.
Event owners/coordinators can request specific swag when proposing their events.
No promises are made that specific swag items will be produced.
The goal of centralized swag production is to ensure high quality and reduced costs (through larger print runs).
We tend to use swag that is project themed and focused except for large events or special needs.
As an example, this process looks like this for the Fedora Booklets in link:https://pagure.io/mindshare/issue/105[Mindshare Ticket #105].
. Mindshare makes a decision about the use of the booklets in general and about Fedora providing them
. FCAIC/others arrange to have them printed and in-stock or on-demand for use
. Event Owners suggest when they will be useful at their events
. AMAZING EVENTS!

55
website/modules/ROOT/pages/release-parties.adoc
View file

@ -1,55 +0,0 @@
What is a Release Party?
------------------------
Release Parties are an informal gathering of community members hosted by Fedora to celebrate a new release. Release parties are a great way to help spread Fedora in your local area and provide an opportunity for Fedora users in your area to come together as a community.
Release parties can be casual events with a few people meeting in a coffee shop or larger events with numerous people in attendance, planned activities, and speakers.
What to do at Release Parties?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are many things you can do at a Release Party. A typical release party will have the following:
. *Talks/Presentations:*
Typically talks at release parties are ones that introduce features in the new release of Fedora. If you're not sure what are the most interesting and important check the https://fedoraproject.org/wiki/Fedora_29_talking_points[Talking points].
. *Question and Answer session:*
Host a session where people can come and ask questions about Fedora. This can be a great way to help answer people's questions and learn what common questions are in the community. It’s also an opportunity to help people with installs and upgrades.It’s OK if you’re not an expert. Make this an “audience participation” event and get everyone to help everyone, just like in the rest of Fedora. This is also a great time to show off the various ways to get help online.
. *Live USB Creation Station:*
Have a machine with you that you can create Live USB images for people on the USB keys they provide. This can be a great way to send someone home with a Live Fedora image they can work with if they are hesitant to commit to an actual Fedora install.
These are just ideas. You’re not required to do any or all of them. Focus your party on your audience. For example, if you’re hosting a release party at work, have talks focused on the way you use Linux and how that relates to Fedora.
Hosting Release Parties
~~~~~~~~~~~~~~~~~~~~~~~
_It’s simple to host a Release Party_
When you’re ready, you need to do a few simple things:
. Send an email to the https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[mindshare 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.
. 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) step. Please use the https://pagure.io/mindshare/new_issue?type=releaseparty[_Release Party_ template].
. Once your party is approved, do the following:
https://apps.fedoraproject.org/calendar/Events/[calendar], so others can easily find it.
.. Request a QR code to award the Release Party Attendee badge. You can do it by opening an issue at https://pagure.io/mindshare/new_issue?title=BadgeforEventName[mindshare pagure]
.. Put in a swag request ticket in the Fedora Budget Repo (See below)
..Finalize your plans and hold your party.
. After your party, 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 event requires financial or swag support (see below), this is mandatory. These reports should help us understand what happened and how the party went. Ideas for what went well and what could be improved are welcome.
. If you have financial assistance approved, file a reimbursement ticket in the https://pagure.io/fedora-budget/new_issue[Fedora Budget Repository]
Financial Assistance and Swag
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Release Parties and should be planned at least 30-40 days in advance. In our experience, events planned with less lead time are generally less successful. If you’re going to request swag, plan for 2 weeks for shipping.
Follow the Getting Financial Assistance and Swag section https://docs.fedoraproject.org/en-US/mindshare-committee/advocate/#_getting_swag_or_financial_support[here].
Writing Your Event Report
~~~~~~~~~~~~~~~~~~~~~~~~~~
* *Community Blog* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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 check out this https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo['how to'].
Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report].

48
website/modules/ROOT/pages/small-events.adoc
View file

@ -1,48 +0,0 @@
= Holding or Attending a Small Event
Anyone can hold or attend a small Fedora-related event, you don't have to be an Ambassador.
A small event is one where the budget is under $150.
The process is exactly the same as for our xref:advocate.adoc[Advocate Program].
It is summarized below:
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
You should use the **advocate** template from the `Type` drop down.
Please complete the fields required.
+
When you are planning for an event you should think about using Fedora stickers and similar swag along with a budget of $150 or less.
If you need more budget, we encourage you to team up with a Fedora Ambassador have them sponsor the event and ask for a larger budget.
We are open to you suggesting uses for your budget that make the most sense for you, your area, and the event.
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
The ticket needs to get 2 +1s and no -1s in three days.
When this happens, a committee member will update the ticket with an approved message.
. Open a **swag-shipment** request, if you need swag for this event, in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
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* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
. Submit a reimbursement request to the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Reimbursements are typically paid within 2 weeks.
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

40
website/modules/ROOT/pages/swag-only-requests.adoc
View file

@ -1,40 +0,0 @@
= Swag Only Requests
If you only need swag to help you hold an event, we have a fast-track policy to help you out.
Anyone can request swag for an event, you don't have to be an Ambassador.
If you're new to Fedora events, checkout our xref:advocate.adoc[Advocate Program].
. Please open a Mindshare ticket in the link:https://pagure.io/mindshare/new_issue[Mindshare Repository].
You need to select the **swag-only** template from the `Type` drop down.
Please complete the fields required.
. Monitor your ticket for questions from the Committee.
. Voting ususally starts very quickly.
The ticket needs to get 2 +1s and no -1s in three days.
When this happens, a committee member will update the ticket with an approved message.
. Open a **swag-shipment** request in the link:https://pagure.io/fedora-budget/issues[Fedora Budget Pagure] using the provided template.
Please allow 2-3 weeks for shipping as swag is generally not stored in your country.
Most of the delay is to allow time for customs processing in your country, not shipping.
. Hold your event!
. Write your event report
+
Fedora Events are often featured in the Mindshare newsletters and hence the event report holds a significant amount of importance.
The report is a general summary of an event which gives the project an idea of what's going on and reports on successes as well as lessons learned.
+
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* (a.k.a. *CommBlog*): You can https://communityblog.fedoraproject.org/wp-login.php[sign into the Community Blog WordPress site] using your FAS account credentials.
Once inside, you can create a new post where you can draft your experience.
After you are done, follow the steps in the https://communityblog.fedoraproject.org/writing-community-blog-article/[guide on publishing articles on the CommBlog].
Here's an example of a https://communityblog.fedoraproject.org/fedora-27-release-party-at-taipei/[Fedora 27 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, You may syndicate your blog to Fedora Planet.
For more information https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo[check out this 'how to'.]
. Comment on your issue in the https://pagure.io/mindshare/issues[mindshare repo with a link to your event report.]

12
website/modules/ROOT/pages/teams.adoc
View file

@ -1,12 +0,0 @@
= Mindshare Teams in Fedora
Mindshare Teams are focused on helping our community grow both the number of users and contributors.
The teams in Mindshare are each focused on a different aspect of this goal.
The xref:mindshare.adoc[Mindshare Committee] fosters communication amongst the Mindshare teams and helps facilitate Council strategy.
* 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.
* link:https://fedoraproject.org/wiki/Ambassadors[**Ambassadors**] — Ambassadors are the representatives of Fedora.
* link:https://fedoraproject.org/wiki/Design[**Design**] — The Fedora Design Team is Fedora's in-house design agency. We provide artwork, user experience, usability, and general design services to the Fedora project.
* link:https://fedoraproject.org/wiki/Websites[**Web Sites**] — The Fedora Websites initiative aims to improve Fedora's image and to create the best possible interface for users and contributors on the Internet.
* xref:badges:ROOT:index.adoc[**Fedora Badges**] — The group behind Fedora Badges — a fun website built to recognize contributors to the Fedora Project, help new and existing Fedora contributors find different ways to get involved, and encourage the improvement of Fedora's infrastructure.