commops/docs
SHA256
17
2
Fork 2
Code Issues Pull requests Activity Actions

🎉 Initial commit

Browse source 
This commit starts a brand new git repository, using the Fedora Docs
content that was previously hosted in the Community Ops "tickets" repo.
Since we moved to Forgejo, it makes more sense to split out our docs
content into its own dedicated repository, making it easier to discover
and having specific issues and bugs related to content.

A new Pull Request will be made to the "tickets" repo to remove the docs
content from there, to avoid duplication of content.

Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit is contained in:
Justin Wheeler 2026-02-10 16:21:42 +01:00
commit a34e4c9fcb
Signed by: jflory7
GPG key ID: 7748B15FA8FA4C7E
411 changed files with 485287 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
.gitignore vendored Normal file
View file

@ -0,0 +1,10 @@
# Documentation artifacts
# Antora-specific rules for preview documentation
_package/
_preview/
# Miscellaneous artifacts
/build/
/cache/
/public/
/preview.pid

427
LICENSE.txt Normal file
View file

@ -0,0 +1,427 @@
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.

50
README.adoc Normal file
View file

@ -0,0 +1,50 @@
= Community Ops Team Docs
// Style rule: one sentence per line please!
// This makes git diffs easier to read. :)
[link=https://creativecommons.org/licenses/by-sa/4.0/]
image::https://img.shields.io/badge/License-CC%20BY--SA%204.0-lightgrey.svg[Fedora Docs content licensed under CC BY-SA 4.0]
[link=https://matrix.to/#/#commops:fedoraproject.org]
image::https://img.shields.io/badge/Chat-in?style=flat&logo=Matrix&label=%23commops%3Afedoraproject.org&link=https%3A%2F%2Fmatrix.to%2F%23%2F%23commops%3Afedoraproject.org[Join us at #commops:fedoraproject.org on Matrix]
Please report issues and submit pull requests for *Content Fixes* to https://docs.fedoraproject.org/en-US/commops/[Fedora Community Ops documentation] against this repo.
General appearance issues and publishing issues should be reported to the https://forge.fedoraproject.org/docs/tickets[Fedora Docs Team].
Never done a pull request (or "PR")?
See the https://guides.github.com/[GitHub Guides] for getting started with git.
If you already know git, see the https://forgejo.org/docs/next/user/pull-requests-and-git-flow/[Forgejo documentation for Pull Requests] on how to submit contributions on _forge.fedoraproject.org_.
[[editing]]
== How to edit these documents
Content for the Community Ops documentation is stored https://forge.fedoraproject.org/commops/docs/src/branch/main/[in this repository].
Source content is written in https://asciidoc.org/[AsciiDoc].
See these resources for help using AsciiDoc:
* https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/[AsciiDoc Syntax - Quick Reference]
* https://asciidoctor.org/docs/asciidoc-recommended-practices/[AsciiDoc Recommended Practices]
* Advanced topics for Fedora Docs, AsciiDoc, and Antora:
** https://asciidoctor.org/docs/asciidoc-writers-guide/[AsciiDoc Writer's Guide]
** https://docs.antora.org/[Antora Documentation]
[[test]]
== Test with a local preview
This repo includes a shell script to build and preview the contents of this repository.
*NOTE*:
Please note that if you reference pages from other repositories, those links will be broken in the local preview, as it only builds this repository.
If you want to rebuild the whole Fedora Docs site, see the https://pagure.io/fedora-docs/docs-fp-o/[Fedora Docs build repository] for instructions.
Both of the below scripts use containers, so ensure Podman or Docker is installed on your system before beginning.
To build and preview the site, run:
```bash
./docsbuilder.sh
```
The preview is hosted at http://localhost:8080[http://localhost:8080].

29
antora.yml Normal file
View file

@ -0,0 +1,29 @@
# Name will be mostly visible in the URL. Treat it as an identifier.
# 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: commops
# Title will be visible on the page.
title: Fedora Community Ops
# 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 "~" to a specific version.
version: ~
# 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.adoc
# This lists all the menu definitions of your component.
nav:
- modules/ROOT/nav.adoc
- modules/analytics/nav.adoc
- modules/events/nav.adoc
- modules/flock/nav.adoc
- modules/matrix/nav.adoc
- modules/teams/nav.adoc
- modules/outreach-badges/nav.adoc
- modules/design-assets/nav.adoc

291
docsbuilder.sh Executable file
View file

@ -0,0 +1,291 @@
#!/bin/bash
# script to watch source directory for changes, and re-run build and preview
#
# License: MIT
# https://fedoraproject.org/wiki/Licensing:MIT#Another_Minimal_variant_(found_in_libatomic_ops)
#
# Copyright (c) Fedora community contributors.
#
# THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED OR
# IMPLIED. ANY USE IS AT YOUR OWN RISK.
#
# Permission is hereby granted to use or copy this program for any purpose,
# provided the above notices are retained on all copies. Permission to modify
# the code and to distribute modified code is granted, provided the above
# notices are retained, and a notice that the code was modified is included
# with the above copyright notice.
script_name="docsbuilder.sh"
script_source="https://gitlab.com/fedora/docs/templates/fedora-docs-template/-/raw/main/${script_name}"
version="1.2.0"
image="registry.gitlab.com/fedora/docs/docs-website/docs-fp-o:latest"
cmd="--html-url-extension-style=indexify site.yml"
srcdir="modules"
buildir="public"
previewpidfile="preview.pid"
# 4913: for vim users, vim creates a temporary file to test it can write to
# directory
# https://groups.google.com/g/vim_dev/c/sppdpElxY44
# .git: so we don't get rebuilds each time git metadata changes
inotifyignore="\.git.*|4913"
watch_and_build () {
if ! command -v inotifywait > /dev/null
then
echo "inotifywait command could not be found. Please install inotify-tools."
echo "On Fedora, run: sudo dnf install inotify-tools"
stop_preview_and_exit
else
# check for git
# required to get ignorelist
if ! command -v git > /dev/null
then
echo "git command could not be found. Please install git."
echo "On Fedora, run: sudo dnf install git-core"
stop_preview_and_exit
else
# Get files not being tracked, we don't watch for changes in these.
# Could hard code, but people use different editors that may create
# temporary files that are updated regularly and so on, so better
# to get the list from git. It'll also look at global gitingore
# settings and so on.
inotifyignore="$(git status -s --ignored | grep '^!!' | sed -e 's/^!! //' | tr '\n' '|')${inotifyignore}"
fi
while true
do
echo "Watching current directory (excluding: ${inotifyignore}) for changes and re-building as required. Use Ctrl C to stop."
inotifywait -q --exclude "($inotifyignore)" -e modify,create,delete,move -r . && echo "Change detected, rebuilding.." && build
done
fi
}
build () {
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 [ -n "$(command -v 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 --stacktrace
elif [ -n "$(command -v 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
}
start_preview () {
# clean up a preview that may be running
stop_preview
# always run an initial build so preview shows latest version
build
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 ""
pushd "${buildir}" > /dev/null 2>&1
python3 -m http.server 8080 &
echo "$!" > ../"${previewpidfile}"
popd > /dev/null 2>&1
fi
}
stop_preview () {
if [ -e "${previewpidfile}" ]
then
PID=$(cat "${previewpidfile}")
kill $PID
echo "Stopping preview server (running with PID ${PID}).."
rm -f "${previewpidfile}"
else
echo "No running preview server found to stop: no ${previewpidfile} file found."
fi
}
stop_preview_and_exit ()
{
# stop and also exit the script
# if stop_preview is trapped, then SIGINT doesn't stop the build loop. So
# we need to make sure we also exit the script.
# stop_preview is called before other functions, so we cannot add exit to
# it.
stop_preview
exit 0
}
# https://apple.stackexchange.com/questions/83939/compare-multi-digit-version-numbers-in-bash/123408#123408
version () { echo "$@" | awk -F. '{ printf("%d%03d%03d%03d\n", $1,$2,$3,$4); }'; }
check_update () {
if ! command -v curl > /dev/null
then
echo "curl command could not be found. Please install curl."
echo "On Fedora, run: sudo dnf install curl"
exit 0
fi
script_version="$(grep "^version=" ${script_name} | cut -d '=' -f2 | tr --delete '"')"
tempdir="$(mktemp -d)"
echo "$tempdir"
pushd "$tempdir" > /dev/null 2>&1
curl "$script_source" --silent --output "${script_name}"
upstream_version="$(grep "^version=" ${script_name} | cut -d '=' -f2 | tr --delete '"')"
echo "${upstream_version}"
if [ $(version $upstream_version) -gt $(version $script_version) ]; then
echo "Update available"
echo "Script version $upstream_version is available at $script_source"
echo "This version is $script_version."
echo "Please use the '-U' option to update."
echo
fi
popd > /dev/null 2&>1
}
install_update () {
if ! command -v curl > /dev/null
then
echo "curl command could not be found. Please install curl."
echo "On Fedora, run: sudo dnf install curl"
exit 0
fi
curl "$script_source" --silent --output "${script_name}.new"
mv "${script_name}.new" "${script_name}"
chmod +x "${script_name}"
}
usage() {
echo "$0: Build and preview Fedora antora based documentation"
echo
echo "Usage: $0 [-awbpkh]"
echo
echo "-a: start preview, start watcher and rebuilder"
echo "-w: start watcher and rebuilder"
echo "-b: rebuild"
echo "-p: start_preview"
echo "-k: stop_preview"
echo "-h: print this usage text and exit"
echo "-u: check builder script update"
echo "-U: install builder script from upstream"
echo
echo "Maintained by the Fedora documentation team."
echo "Please contact on our channels: https://docs.fedoraproject.org/en-US/fedora-docs/#find-docs"
}
# check if the script is being run in a Fedora docs repository
if [ ! -e "site.yml" ]
then
echo "site.yml not be found."
echo "This does not appear to be a Fedora Antora based documentation repository."
echo "Exiting."
echo
usage
exit 1
fi
if [ $# -lt 1 ]
then
echo "No options provided, running preview with watch and build."
echo "Run script with '-h' to see all available options."
echo
echo
trap stop_preview_and_exit INT
start_preview
watch_and_build
stop_preview
fi
# parse options
while getopts "awbpkhuU" OPTION
do
case $OPTION in
a)
# handle sig INT to stop the preview
trap stop_preview_and_exit INT
start_preview
watch_and_build
stop_preview
exit 0
;;
w)
watch_and_build
exit 0
;;
b)
build
exit 0
;;
p)
start_preview
echo "Please run ./${script_name} -k to stop the preview server"
exit 0
;;
k)
stop_preview
exit 0
;;
h)
usage
exit 0
;;
u)
check_update
exit 0
;;
U)
install_update
exit 0
;;
?)
usage
exit 1
;;
esac
done

BIN
modules/ROOT/assets/images/Advocates.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

BIN
modules/ROOT/assets/images/Amby_emeritus.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
modules/ROOT/assets/images/Mktg.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
modules/ROOT/assets/images/cheatcube_communityoutreachteams.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.1 MiB

BIN
modules/ROOT/assets/images/cheatcube_fedorafriends.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.2 MiB

BIN
modules/ROOT/assets/images/cheatcube_fourfoundations.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 645 KiB

BIN
modules/ROOT/assets/images/cheatcube_howtojoinFedora_version2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 881 KiB

BIN
modules/ROOT/assets/images/cheatcube_howtojoinfedora_version1.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 798 KiB

BIN
modules/ROOT/assets/images/cheatcube_packaging.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.5 MiB

BIN
modules/ROOT/assets/images/commops-logo.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 11 KiB

BIN
modules/ROOT/assets/images/fedoraslidetemplate_newbrand.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 112 KiB

BIN
modules/ROOT/assets/images/infographic-2020.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 981 KiB

1768
modules/ROOT/assets/images/infographic-2020.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 129 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 13 KiB

86
modules/ROOT/assets/images/team-logos/community-ops/commops.svg Normal file
View file

@ -0,0 +1,86 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="500.86301"
height="224"
viewBox="0 0 132.52 59.266667"
version="1.1"
id="svg83"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\CommOps.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs77" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="1.8"
inkscape:cx="340.12738"
inkscape:cy="114.93623"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata80">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.4178782"
rx="2.0576177"
y="0"
x="0"
height="59.266666"
width="132.51993"
id="rect1560"
style="fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:0.502828;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
id="text1568"
y="33.753902"
x="34.232574"
style="font-style:normal;font-weight:normal;font-size:15.6113px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#294172;fill-opacity:1;stroke:none;stroke-width:0.390284"
xml:space="preserve"><tspan
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.268273px;fill:#294172;fill-opacity:1;stroke-width:0.390284"
y="33.753902"
x="34.232574"
id="tspan1566"
sodipodi:role="line">COMMOPS</tspan></text>
<path
id="path1570"
style="fill:#51a2da;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.35278"
d="m 20.360096,18.232721 c -5.30632,0 -9.60677,4.29897 -9.61023,9.60408 h -0.002 v 7.43914 h 0.002 c 0.002,1.20438 0.9784,2.17929 2.1834,2.17929 h 0.0104 0.002 7.41865 c 5.30692,-0.003 9.60613,-4.30376 9.60613,-9.61024 0,-5.3087 -4.3015,-9.61227 -9.61022,-9.61227 z m 1.94786,3.9551 c 1.61399,0 3.13787,1.2367 3.13787,2.94125 0,0.15809 -6e-4,0.31636 -0.0266,0.49567 -0.0446,0.45351 -0.45815,0.77874 -0.90942,0.71482 -0.45124,-0.0647 -0.75735,-0.49189 -0.67385,-0.94013 0.007,-0.0511 0.0104,-0.13229 0.0104,-0.27036 0,-0.96644 -0.79033,-1.33954 -1.53821,-1.33954 -0.74744,0 -1.42172,0.62851 -1.42352,1.33954 0.0129,0.82249 0,1.63908 0,2.45991 l 1.38665,-0.0103 c 1.08302,-0.0225 1.09515,1.60998 0.0122,1.60171 l -1.39894,0.0103 c -0.005,0.66153 0.006,0.5414 0.002,0.87457 0,0 0.012,0.80806 -0.0123,1.42148 -0.16742,1.80154 -1.70078,3.24231 -3.54341,3.24231 -1.95304,0 -3.5639,-1.59785 -3.5639,-3.5557 0.0586,-2.01411 1.66631,-3.59703 3.68883,-3.57823 l 1.12652,-0.008 v 1.59965 l -1.12652,0.0103 h -0.008 c -1.1116,0.0328 -2.06277,0.78613 -2.08098,1.97652 0,1.08467 0.87656,1.95401 1.96423,1.95401 1.08587,0 1.954,-0.79087 1.954,-1.95195 0.0123,-1.92552 -0.008,-4.05253 -0.002,-6.05248 6e-4,-0.11239 0.007,-0.20172 0.0185,-0.32566 0.18336,-1.48072 1.50786,-2.60944 3.00679,-2.60944 z" />
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 4.3 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops_dark.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 12 KiB

100
modules/ROOT/assets/images/team-logos/community-ops/commops_dark.svg Normal file
View file

@ -0,0 +1,100 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="500.86301"
height="224"
viewBox="0 0 132.52 59.266667"
version="1.1"
id="svg83"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps_dark.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\CommOps_dark.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs77" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="1.8"
inkscape:cx="149.38664"
inkscape:cy="114.93623"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata80">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.4178782"
rx="2.0576177"
y="0"
x="0"
height="59.266666"
width="132.51993"
id="rect1560"
style="fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.502828;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
id="text1568"
y="33.753902"
x="34.232574"
style="font-style:normal;font-weight:normal;font-size:15.6113px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:0.390284;"
xml:space="preserve"><tspan
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.268273px;fill:#ffffff;fill-opacity:1;stroke-width:0.390284;"
y="33.753902"
x="34.232574"
id="tspan1566"
sodipodi:role="line">COMMOPS</tspan></text>
<text
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/feb-candidates/candidates.png"
id="text1564-3"
y="55.58289"
x="104.74385"
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.09958px;line-height:1.25;font-family:Montserrat;-inkscape-font-specification:Montserrat;letter-spacing:0px;word-spacing:0px;opacity:0.2;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.0965166"
xml:space="preserve"><tspan
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.09958px;font-family:Montserrat;-inkscape-font-specification:Montserrat;fill:#000000;stroke-width:0.0965166"
y="55.58289"
x="104.74385"
id="tspan1562-3"
sodipodi:role="line">team sub logo</tspan></text>
<path
id="path1819"
style="fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.446883"
d="m 20.359983,18.233 c -5.306383,0 -9.606901,4.299088 -9.610361,9.604337 h -0.0022 v 7.439312 h 0.0022 c 0.0024,1.204425 0.97841,2.179351 2.183428,2.179351 h 0.01026 0.0022 7.418741 c 5.306986,-0.0034 9.606264,-4.303874 9.606264,-9.610469 0,-5.308848 -4.301568,-9.612531 -9.610362,-9.612531 z m 1.94788,3.955215 c 1.614012,0 3.137911,1.236728 3.137911,2.941318 0,0.15809 -7.44e-4,0.316374 -0.02663,0.495669 -0.04468,0.45353 -0.458158,0.77878 -0.909419,0.714847 -0.451263,-0.06469 -0.757362,-0.491898 -0.673873,-0.940148 0.0076,-0.05118 0.01026,-0.132288 0.01026,-0.270368 0,-0.966463 -0.790339,-1.339578 -1.538231,-1.339578 -0.747438,0 -1.421747,0.628524 -1.42353,1.339578 0.01293,0.822502 0,1.639115 0,2.459966 l 1.386662,-0.01051 c 1.083023,-0.02245 1.095166,1.610028 0.01229,1.601741 l -1.398951,0.01051 c -0.0037,0.66156 0.0052,0.541426 0.0022,0.874619 0,0 0.01191,0.808069 -0.01229,1.421499 -0.167417,1.801604 -1.700811,3.242397 -3.543462,3.242397 -1.95306,0 -3.563945,-1.597894 -3.563945,-3.555784 0.05866,-2.014164 1.666333,-3.597133 3.688886,-3.578327 l 1.126535,-0.0084 v 1.599692 l -1.126535,0.01051 h -0.0082 c -1.111607,0.03285 -2.06281,0.786135 -2.081015,1.976574 0,1.08469 0.876576,1.954056 1.964266,1.954056 1.085886,0 1.954025,-0.7909 1.954025,-1.952002 0.01229,-1.925564 -0.0086,-4.052628 -0.0022,-6.052637 5.98e-4,-0.112374 0.0061,-0.201723 0.01843,-0.32567 0.183363,-1.480762 1.507883,-2.609505 3.006823,-2.609505 z" />
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 5.3 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops_dark_blue.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 12 KiB

104
modules/ROOT/assets/images/team-logos/community-ops/commops_dark_blue.svg Normal file
View file

@ -0,0 +1,104 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="500.86301"
height="224"
viewBox="0 0 132.52 59.266667"
version="1.1"
id="svg83"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps_dark_blue.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\CommOps_dark_blue.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs77" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="1.8"
inkscape:cx="180.56224"
inkscape:cy="114.93623"
inkscape:document-units="mm"
inkscape:current-layer="g867"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata80">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.4178782"
rx="2.0576177"
y="0"
x="0"
height="59.266666"
width="132.51993"
id="rect1560"
style="fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.502828;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
id="text1568"
y="33.753902"
x="34.232574"
style="font-style:normal;font-weight:normal;font-size:15.6113px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#51a2da;fill-opacity:1;stroke:none;stroke-width:0.390284;"
xml:space="preserve"><tspan
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.268273px;fill:#51a2da;fill-opacity:1;stroke-width:0.390284;"
y="33.753902"
x="34.232574"
id="tspan1566"
sodipodi:role="line">COMMOPS</tspan></text>
<text
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/feb-candidates/candidates.png"
id="text1564-3"
y="55.58289"
x="104.74385"
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.09958px;line-height:1.25;font-family:Montserrat;-inkscape-font-specification:Montserrat;letter-spacing:0px;word-spacing:0px;opacity:0.2;fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.0965166"
xml:space="preserve"><tspan
style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:3.09958px;font-family:Montserrat;-inkscape-font-specification:Montserrat;fill:#000000;stroke-width:0.0965166"
y="55.58289"
x="104.74385"
id="tspan1562-3"
sodipodi:role="line">team sub logo</tspan></text>
<g
id="g867"
transform="translate(-44.04304,21.601595)">
<path
id="path1616-5"
style="fill:#51a2da;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.238469"
d="m 64.402964,-3.368594 c -5.306451,0 -9.607022,4.2990868 -9.610483,9.6043363 h -0.002 v 7.4393107 h 0.002 c 0.0027,1.204424 0.978421,2.179351 2.183455,2.179351 h 0.01028 0.002 7.418834 c 5.307053,-0.0034 9.60638,-4.303873 9.60638,-9.6104687 0,-5.3088455 -4.301619,-9.6125303 -9.610476,-9.6125303 z m 1.947899,3.9552138 c 1.614038,0 3.137955,1.23673 3.137955,2.9413192 0,0.158089 -6.76e-4,0.316375 -0.02663,0.495669 -0.04468,0.453529 -0.458166,0.7787799 -0.909431,0.7148449 -0.451266,-0.06469 -0.757372,-0.4918969 -0.673883,-0.9401469 0.0076,-0.05117 0.01028,-0.132287 0.01028,-0.270368 0,-0.9664632 -0.790346,-1.3395782 -1.538248,-1.3395782 -0.747449,0 -1.421764,0.628524 -1.423549,1.3395782 0.01291,0.822501 0,1.6391149 0,2.4599663 l 1.386682,-0.01048 c 1.083034,-0.02244 1.095175,1.6100271 0.0123,1.6017391 l -1.39897,0.01048 c -0.0034,0.6615587 0.0054,0.5414257 0.002,0.8746187 0,0 0.0119,0.808069 -0.0123,1.421499 -0.167418,1.8016059 -1.700832,3.2423969 -3.54351,3.2423969 -1.953084,0 -3.563985,-1.597894 -3.563985,-3.5557839 0.05867,-2.0141637 1.666351,-3.5971308 3.688932,-3.5783258 l 1.126547,-0.0084 v 1.5996911 l -1.126547,0.01048 h -0.0082 c -1.111621,0.03285 -2.062835,0.7861337 -2.081039,1.9765727 0,1.0846899 0.876587,1.9540569 1.964286,1.9540569 1.0859,0 1.954051,-0.790899 1.954051,-1.9520019 0.01237,-1.9255637 -0.0086,-4.0526275 -0.002,-6.0526361 5.95e-4,-0.112373 0.0061,-0.2017232 0.01845,-0.3256692 0.183364,-1.480762 1.507903,-2.609505 3.006856,-2.609505 z" />
</g>
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 5.5 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 8.8 KiB

87
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical.svg Normal file
View file

@ -0,0 +1,87 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="264.108"
height="220.202"
viewBox="0 0 69.878574 58.26178"
version="1.1"
id="svg8"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps_vertical.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\Ambassadors emeritus_vertical.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs2" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="0.99"
inkscape:cx="-13.266177"
inkscape:cy="145.29791"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:snap-bbox="true"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata5">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.9893851"
rx="3.0866201"
y="0"
x="6.2624613e-06"
height="58.261879"
width="69.878563"
id="rect1776"
style="fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:0.362024;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
xml:space="preserve"
style="font-style:normal;font-weight:normal;font-size:10.2469px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#294172;fill-opacity:1;stroke:none;stroke-width:0.256172"
x="6.4176087"
y="38.714005"
id="text1780"><tspan
sodipodi:role="line"
id="tspan1778"
x="6.4176087"
y="38.714005"
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.176087px;fill:#294172;fill-opacity:1;stroke-width:0.256172">COMMOPS</tspan></text>
<path
id="path1787"
style="fill:#51a2da;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.35278"
d="m 34.940018,11.0282 c -4.08302,0 -7.39206,3.3079 -7.39472,7.38998 h -10e-4 v 5.72414 h 10e-4 c 0.001,0.92673 0.75284,1.67688 1.68005,1.67688 h 0.008 0.001 5.70837 c 4.08347,-0.002 7.39156,-3.31158 7.39156,-7.39472 0,-4.08484 -3.30985,-7.39628 -7.39471,-7.39628 z m 1.4988,3.0433 c 1.2419,0 2.41447,0.9516 2.41447,2.26318 0,0.12165 -4.6e-4,0.24343 -0.0205,0.3814 -0.0343,0.34896 -0.35253,0.59921 -0.69976,0.55003 -0.34721,-0.0498 -0.58275,-0.37849 -0.51851,-0.72339 0.006,-0.0393 0.008,-0.1018 0.008,-0.20804 0,-0.74364 -0.60812,-1.03072 -1.18359,-1.03072 -0.57512,0 -1.09396,0.48361 -1.09534,1.03072 0.01,0.63288 0,1.26121 0,1.89281 l 1.06697,-0.008 c 0.83334,-0.0173 0.84268,1.23882 0.009,1.23245 l -1.07643,0.008 c -0.004,0.50902 0.004,0.41659 10e-4,0.67295 0,0 0.009,0.62177 -0.009,1.09377 -0.12882,1.38622 -1.30869,2.49484 -2.72652,2.49484 -1.50279,0 -2.74229,-1.22949 -2.74229,-2.73598 0.0451,-1.54978 1.28216,-2.76778 2.83842,-2.75331 l 0.86681,-0.006 v 1.23087 l -0.86681,0.008 h -0.006 c -0.85534,0.0252 -1.58723,0.6049 -1.60124,1.52086 0,0.83461 0.67448,1.50353 1.5114,1.50353 0.83554,0 1.50353,-0.60854 1.50353,-1.50195 0.01,-1.48161 -0.007,-3.11827 -0.001,-4.65716 4.6e-4,-0.0865 0.005,-0.15521 0.0142,-0.25058 0.14109,-1.13936 1.16025,-2.00787 2.31362,-2.00787 z" />
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 4.3 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical_dark.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 8.2 KiB

91
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical_dark.svg Normal file
View file

@ -0,0 +1,91 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="264.108"
height="220.202"
viewBox="0 0 69.878574 58.26178"
version="1.1"
id="svg8"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps_vertical_dark.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\CommOps_vertical_dark.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs2" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="0.99"
inkscape:cx="16.700153"
inkscape:cy="145.29791"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:snap-bbox="true"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata5">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title></dc:title>
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.9893851"
rx="3.0866201"
y="0"
x="6.2624613e-06"
height="58.261879"
width="69.878563"
id="rect1776"
style="fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.362024;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
xml:space="preserve"
style="font-style:normal;font-weight:normal;font-size:10.2469px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#51a2da;fill-opacity:1;stroke:none;stroke-width:0.256172"
x="6.4176087"
y="38.714005"
id="text1780"><tspan
sodipodi:role="line"
id="tspan1778"
x="6.4176087"
y="38.714005"
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.176087px;fill:#ffffff;fill-opacity:1;stroke-width:0.256172">COMMOPS</tspan></text>
<path
id="path1787"
style="fill:#51a2da;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.35278"
d="m 34.940018,11.0282 c -4.08302,0 -7.39206,3.3079 -7.39472,7.38998 h -10e-4 v 5.72414 h 10e-4 c 0.001,0.92673 0.75284,1.67688 1.68005,1.67688 h 0.008 0.001 5.70837 c 4.08347,-0.002 7.39156,-3.31158 7.39156,-7.39472 0,-4.08484 -3.30985,-7.39628 -7.39471,-7.39628 z m 1.4988,3.0433 c 1.2419,0 2.41447,0.9516 2.41447,2.26318 0,0.12165 -4.6e-4,0.24343 -0.0205,0.3814 -0.0343,0.34896 -0.35253,0.59921 -0.69976,0.55003 -0.34721,-0.0498 -0.58275,-0.37849 -0.51851,-0.72339 0.006,-0.0393 0.008,-0.1018 0.008,-0.20804 0,-0.74364 -0.60812,-1.03072 -1.18359,-1.03072 -0.57512,0 -1.09396,0.48361 -1.09534,1.03072 0.01,0.63288 0,1.26121 0,1.89281 l 1.06697,-0.008 c 0.83334,-0.0173 0.84268,1.23882 0.009,1.23245 l -1.07643,0.008 c -0.004,0.50902 0.004,0.41659 10e-4,0.67295 0,0 0.009,0.62177 -0.009,1.09377 -0.12882,1.38622 -1.30869,2.49484 -2.72652,2.49484 -1.50279,0 -2.74229,-1.22949 -2.74229,-2.73598 0.0451,-1.54978 1.28216,-2.76778 2.83842,-2.75331 l 0.86681,-0.006 v 1.23087 l -0.86681,0.008 h -0.006 c -0.85534,0.0252 -1.58723,0.6049 -1.60124,1.52086 0,0.83461 0.67448,1.50353 1.5114,1.50353 0.83554,0 1.50353,-0.60854 1.50353,-1.50195 0.01,-1.48161 -0.007,-3.11827 -0.001,-4.65716 4.6e-4,-0.0865 0.005,-0.15521 0.0142,-0.25058 0.14109,-1.13936 1.16025,-2.00787 2.31362,-2.00787 z" />
<path
id="path1819"
style="fill:#ffffff;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.343839"
d="m 34.939286,11.02859 c -4.082683,0 -7.391462,3.307902 -7.394124,7.389989 h -0.0017 v 5.724125 h 0.0017 c 0.0019,0.926736 0.752779,1.676886 1.679909,1.676886 h 0.0079 0.0017 5.707911 c 4.083147,-0.0026 7.390972,-3.311585 7.390972,-7.394707 0,-4.084854 -3.309587,-7.396293 -7.394124,-7.396293 z m 1.498681,3.043312 c 1.241806,0 2.41428,0.951592 2.41428,2.263176 0,0.121641 -5.72e-4,0.243432 -0.02049,0.381389 -0.03438,0.348965 -0.352502,0.599227 -0.699699,0.550034 -0.347196,-0.04978 -0.582706,-0.378488 -0.518471,-0.72339 0.0058,-0.03938 0.0079,-0.101788 0.0079,-0.208033 0,-0.743638 -0.60808,-1.030729 -1.183501,-1.030729 -0.575072,0 -1.09388,0.483614 -1.095251,1.030729 0.01,0.632868 0,1.261206 0,1.892804 l 1.066885,-0.0081 c 0.833268,-0.01727 0.842611,1.238824 0.0095,1.232448 l -1.076341,0.0081 c -0.0028,0.509032 0.004,0.416596 0.0017,0.672969 0,0 0.0092,0.621763 -0.0095,1.093762 -0.128809,1.386232 -1.308588,2.494839 -2.726306,2.494839 -1.502667,0 -2.742068,-1.229488 -2.742068,-2.735972 0.04513,-1.549784 1.282062,-2.767788 2.838196,-2.753318 l 0.866747,-0.0064 v 1.230872 l -0.866747,0.0081 h -0.0063 c -0.85526,0.02527 -1.587107,0.604885 -1.601114,1.52086 0,0.834607 0.674429,1.503535 1.511289,1.503535 0.83547,0 1.503409,-0.608552 1.503409,-1.501954 0.0095,-1.481612 -0.0066,-3.118266 -0.0017,-4.657159 4.6e-4,-0.08647 0.0047,-0.155214 0.01418,-0.250584 0.141078,-1.139362 1.16015,-2.007865 2.313422,-2.007865 z" />
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 5.9 KiB

BIN
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical_dark_blue.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 8.9 KiB

87
modules/ROOT/assets/images/team-logos/community-ops/commops_vertical_dark_blue.svg Normal file
View file

@ -0,0 +1,87 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="264.108"
height="220.202"
viewBox="0 0 69.878574 58.26178"
version="1.1"
id="svg8"
inkscape:version="1.0.2-2 (e86c870879, 2021-01-15)"
sodipodi:docname="CommOps_vertical_dark_blue.svg"
inkscape:export-filename="C:\Users\pc\Desktop\Fedora\Logos\CommOps_vertical_dark_blue.png"
inkscape:export-xdpi="96"
inkscape:export-ydpi="96">
<defs
id="defs2" />
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="0.99"
inkscape:cx="16.700153"
inkscape:cy="145.29791"
inkscape:document-units="mm"
inkscape:current-layer="layer1"
inkscape:document-rotation="0"
showgrid="false"
units="px"
inkscape:snap-bbox="true"
inkscape:window-width="1366"
inkscape:window-height="705"
inkscape:window-x="-8"
inkscape:window-y="-8"
inkscape:window-maximized="1" />
<metadata
id="metadata5">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title />
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Layer 1"
inkscape:groupmode="layer"
id="layer1">
<rect
inkscape:export-ydpi="96"
inkscape:export-xdpi="96"
ry="2.9893851"
rx="3.0866201"
y="0"
x="6.2624613e-06"
height="58.261879"
width="69.878563"
id="rect1776"
style="fill:#000000;fill-opacity:1;stroke:none;stroke-width:0.362024;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1"
inkscape:export-filename="/home/duffy/Cáipéisí/Work/Fedora/Tickets/620 - logo/2020 edits/Set 1/2020-19.png" />
<text
xml:space="preserve"
style="font-style:normal;font-weight:normal;font-size:10.2469px;line-height:1.25;font-family:sans-serif;letter-spacing:0px;word-spacing:0px;fill:#51a2da;fill-opacity:1;stroke:none;stroke-width:0.256172;"
x="6.4176087"
y="38.714005"
id="text1780"><tspan
sodipodi:role="line"
id="tspan1778"
x="6.4176087"
y="38.714005"
style="font-style:normal;font-variant:normal;font-weight:600;font-stretch:normal;font-family:Montserrat;-inkscape-font-specification:'Montserrat Semi-Bold';letter-spacing:-0.176087px;fill:#51a2da;fill-opacity:1;stroke-width:0.256172;">COMMOPS</tspan></text>
<path
id="path1787"
style="fill:#51a2da;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.35278"
d="m 34.940018,11.0282 c -4.08302,0 -7.39206,3.3079 -7.39472,7.38998 h -10e-4 v 5.72414 h 10e-4 c 0.001,0.92673 0.75284,1.67688 1.68005,1.67688 h 0.008 0.001 5.70837 c 4.08347,-0.002 7.39156,-3.31158 7.39156,-7.39472 0,-4.08484 -3.30985,-7.39628 -7.39471,-7.39628 z m 1.4988,3.0433 c 1.2419,0 2.41447,0.9516 2.41447,2.26318 0,0.12165 -4.6e-4,0.24343 -0.0205,0.3814 -0.0343,0.34896 -0.35253,0.59921 -0.69976,0.55003 -0.34721,-0.0498 -0.58275,-0.37849 -0.51851,-0.72339 0.006,-0.0393 0.008,-0.1018 0.008,-0.20804 0,-0.74364 -0.60812,-1.03072 -1.18359,-1.03072 -0.57512,0 -1.09396,0.48361 -1.09534,1.03072 0.01,0.63288 0,1.26121 0,1.89281 l 1.06697,-0.008 c 0.83334,-0.0173 0.84268,1.23882 0.009,1.23245 l -1.07643,0.008 c -0.004,0.50902 0.004,0.41659 10e-4,0.67295 0,0 0.009,0.62177 -0.009,1.09377 -0.12882,1.38622 -1.30869,2.49484 -2.72652,2.49484 -1.50279,0 -2.74229,-1.22949 -2.74229,-2.73598 0.0451,-1.54978 1.28216,-2.76778 2.83842,-2.75331 l 0.86681,-0.006 v 1.23087 l -0.86681,0.008 h -0.006 c -0.85534,0.0252 -1.58723,0.6049 -1.60124,1.52086 0,0.83461 0.67448,1.50353 1.5114,1.50353 0.83554,0 1.50353,-0.60854 1.50353,-1.50195 0.01,-1.48161 -0.007,-3.11827 -0.001,-4.65716 4.6e-4,-0.0865 0.005,-0.15521 0.0142,-0.25058 0.14109,-1.13936 1.16025,-2.00787 2.31362,-2.00787 z" />
</g>
</svg>
Side by side

After

Width:  |  Height:  |  Size: 4.3 KiB

5
modules/ROOT/nav.adoc Normal file
View file

@ -0,0 +1,5 @@
* xref:index.adoc[Home]
* xref:join.adoc[Join Community Ops]
* xref:community-blog.adoc[Community Blog]
* xref:planet.adoc[Fedora Planet]
* xref:sig-howto.adoc[Create a Fedora SIG]

91
modules/ROOT/pages/appreciation-week.adoc Normal file
View file

@ -0,0 +1,91 @@
include::ROOT:partial$attributes.adoc[]
= Fedora Appreciation Week
Fedora Appreciation Week is an annual event organized by the Fedora xref:index.adoc[Community Operations] (CommOps) team.
Fedora Appreciation Week, abbreviated as FAW, is a week-long event to celebrate efforts of Fedora Project contributors and to say "thank you" to each other.
FAW is normally held on the week of November 6th to coincide with the https://www.redhat.com/archives/fedora-announce-list/2003-November/msg00000.html[anniversary] of the Fedora Project.
== What is it?
The https://wiki.ubuntu.com/UCADay[Ubuntu Community Appreciation Day] inspired CommOps to organize a similar event of appreciation for contributors who make the Fedora community what it is.
This includes all types of contributors: development, design, infrastructure, marketing, engineering, and more.
During the week, anyone is encouraged to select an individual or a group of contributors to thank for their efforts in Fedora.
Appreciation can be given as an IRC karma cookie, a short note of thanks on a mailing list, or a longer form of appreciation (e.g. a https://happinesspackets.fedorainfracloud.org/[Fedora Happiness Packet]),
== Why do it?
Most Fedora contributors do not get to work together in the same building or office.
Our daily interactions are usually in text form (e.g. IRC, emails, wikis, etc.).
Even though these work well and we accomplish our goals, we lose touch with the human side of contributing.
Fedora contributors aren’t robots, but real people!
Fedora Appreciation Week is a chance to remember the Fedora community is a community of people, and to thank our colleagues and friends who might be halfway across the room or halfway across the planet.
== How to participate
Different ways to participate in Fedora Appreciation Week are explained below.
Consider using one or many of the methods below to participate.
=== Write a Contributor Story
https://pagure.io/fedora-commops/contributor-stories[Contributor Stories] are just that: the record of our best moments with our Fedora friends.
The story can be about our work in Fedora or something personal or unique which you would like to share with the community.
Selected stories will be shared on the Community Blog every day during Fedora Appreciation Week.
See some https://pagure.io/fedora-commops/contributor-stories/issues?status=all[examples] and consider https://pagure.io/fedora-commops/contributor-stories/new_issue[writing one of your own].
=== Submit and vote on your favorite community pictures
More coming soon (see https://pagure.io/fedora-commops/issue/110#comment-531973[discussion]).
=== Send a Fedora Happiness Packet
Happiness Packets are public or private notes of thanks you can send as emails to other contributors.
The Fedora Happiness Packets (*FHP*) project launched as part of {url_commblog}/happiness-packets-fedora-gsoc-2018/[Fedora Summer Coding 2018].
It is a fork of https://www.happinesspackets.io/[happinesspackets.io].
FHP supports FAS account login and account search.
You can earn a Fedora Badge by sending a message of gratitude or thanks to another contributor.
https://happinesspackets.fedorainfracloud.org/[**Send one now!**]
=== Write your appreciation ===
You can also consider other ways of sharing and writing your appreciation for someone else and what they bring to our community.
If you are not sure of a specific person, you can also tweet general appreciation of Fedora, as operating city or as community.
Consider these ideas:
* Write a blog post
* Tweet a "thank you" that mentions https://twitter.com/fedora[@fedora]
* Tweet a hat tip / thanks to another Fedora contributor with hashtag *#_WeAreFedora_*
== Press
This section is a running list of press coverage of Fedora Appreciation Week:
=== 2018
* *2018-05-01*: {url_commblog}/contributor-stories/[Introducing Contributor Stories] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-08-09*: https://www.youtube.com/watch?v=wV8j2xt8pmw[Flock 2018 - Thank the Fedora Community! Launching Fedora Appreciation Week] - https://youtube.com[_youtube.com_]
* *2018-09-18*: {url_commblog}/fedora-appreciation-week-2018/[Say thank you this November during Fedora Appreciation Week 2018] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-10-29*: https://fedoramagazine.org/say-thanks-appreciation-week-2018/[Say thanks during Fedora Appreciation Week (Nov. 5-11)] - https://fedoramagazine.org[_fedoramagazine.org_]
* *2018-10-29*: https://www.linuxjournal.com/content/fedora-appreciation-week-qt-announces-deprecation-qbs-d-language-front-end-merged-gcc[Fedora Appreciation Week, Qt Announces the Deprecation of Qbs…] - https://www.linuxjournal.com[_linuxjournal.com_]
* *2018-11-09*: https://fedoramagazine.org/appreciate-fedora-2018/[How Do You Appreciate Fedora?] - https://fedoramagazine.org[_fedoramagazine.org_]
==== Appreciation Week highlights
* *2018-11-05*: {url_commblog}/faw-2018-day-1-community-makes-the-difference/[FAW 2018 Day 1: “Community makes the difference”] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-11-06*: {url_commblog}/faw-2018-day-2-change-the-world-through-open-source/[FAW 2018 Day 2: “Change the world through Open Source. He said.”] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-11-07*: {url_commblog}/faw-2018-day-3-becoming-part-of-fedora-family-because-of-her/[FAW 2018 Day 3: “Becoming part of Fedora family because of her!”] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-11-08*: {url_commblog}/faw-2018-day-4-you-know-you-can-do-it/[FAW 2018 Day 4: “You know you can do it”] - {url_commblog}[_communityblog.fedoraproject.org_]
* *2018-11-09*: {url_commblog}/faw-2018-day-5-encouraging-crazy-ideas/[FAW 2018 Day 5: “Encouraging crazy ideas”] - {url_commblog}[_communityblog.fedoraproject.org_]
==== Community appreciation
* *2018-11-06*: https://blog.justinwflory.com/2018/11/fedora-appreciation-week-tribute-to-a-legacy/[Fedora Appreciation Week: Tribute to a legacy] - https://blog.justinwflory.com/[_blog.justinwflory.com_]
* *2018-11-06*: https://blog.hildenco.com/2018/11/thank-you-fedora.html[Thank You, Fedora] - https://blog.hildenco.com/[_blog.hildenco.com_]
* *2018-11-10*: https://forums.fedoraforum.org/showthread.php?319858-Fedora-appreciation-week[Fedora appreciation week] - https://forums.fedoraforum.org/[_forums.fedoraforum.org_]
* *2018-11-10*: https://lushka.al/thank-you-fedora/[Thank you, Fedora] - https://lushka.al/[_lushka.al_]

90
modules/ROOT/pages/community-blog.adoc Normal file
View file

@ -0,0 +1,90 @@
include::ROOT:partial$attributes.adoc[]
= Community Blog
The link:{url_commblog}[Fedora Community Blog] (CommBlog) is a WordPress-based site that delivers news, updates, and calls for help from contributors across Fedora.
image::https://fedoraproject.org/w/uploads/0/09/Community_Blog_screenshot.png[Community Blog screenshot,90%,90%]
[[content]]
== Content
The Community Blog focuses on updates and information about the Fedora Project community.
Topics vary, but mostly include…
* News from specific sub-projects
* Updates on new features or changes in Fedora
* Calls for help from other contributors
* Official {url_wiki}/Elections[Fedora Elections] coverage
* Anything related to Fedora _contributor_ community
[[magazine-vs-community-blog]]
== Fedora Magazine vs. Community Blog
What is the difference between the https://fedoramagazine.org[Fedora Magazine] and the Community Blog?
They focus on two different audiences (or types of readers).
The Fedora Magazine targets everyday Fedora users, Linux enthusiasts, and technology hobbyists.
Fedora contributors are included in these audiences, but they are not the main focus.
The Community Blog is the news hub for Fedora contributors and people working inside of the Fedora community.
The Community Blog specifically focuses on our contributors.
For example, an article on how to use a new package in Fedora is better for the Magazine.
Any Fedora user may be interested in using the package.
An article that announces a new feature to a Fedora Infrastructure service or an Ambassador event report is better for the Community Blog.
A Fedora user may not be interested, but our contributors have a stronger interest.
Sometimes there is some overlap between the two.
Think hard about who you are writing for and who you want to read your article.
This should answer the question of where to write your article.
The CommOps and Fedora Magazine teams are happy to answer any doubts or questions if you are unsure.
[[write-article]]
== Write an article
The Community Blog is managed by the CommOps team.
The system administration is managed by {url_wiki}/Infrastructure[Fedora Infrastructure].
However, we need _your help_ to share the awesome things you and your area of Fedora are working on.
Articles don't need to be long.
Short snippets are useful too.
If you're not sure how much to write, 300 words is a good target.
If needed, you can always write more.
See the link:{url_commblog}/writing-community-blog-article/[_Writing an article_] guide to get started.
This page explains the process for writing and how to get your post published.
[[community-blog-theme]]
== Community Blog theme
The Community Blog WordPress theme is open source.
Find the source code https://pagure.io/communityblog-theme[on Pagure].
Open a ticket if you find a bug, problem, or something to improve.
Pull requests are also welcome!
Before submitting a pull request, post to {team_asynch_communication}[{team_asynch_communication_name}] first and ask for feedback on your planned contribution.
[[editors]]
== Editors
Community Blog editors review article drafts and schedule new posts.
Editors are reachable on {team_asynch_communication}[{team_asynch_communication_name}].
Below, you can find a current list of editors:
|===
|Name |FAS account
|Justin W. Wheeler
|{url_wiki}/User:Jflory7[jflory7]
|Michal Konecny
|{url_wiki}/User:Zlopez[zlopez]
|Sumantro Mukherjee
|{url_wiki}/User:Sumantrom[sumantrom]
|===

180
modules/ROOT/pages/index.adoc Normal file
View file

@ -0,0 +1,180 @@
include::ROOT:partial$attributes.adoc[]
= {team_name}
:page-aliases: contribute/commops-landing.adoc, teams:commops.adoc, teams:commops-role.adoc
// #TODO Create a new page to document the CommOps brand assets.
// This does not exist yet.
// The link below is where the source SVGs currently live as of 2025-02-03.
// When the page is created, this comment and the URL can be removed from the index page.
// https://gitlab.com/fedora/commops/home/-/blob/main/docs/modules/ROOT/assets/images/team-logos/community-ops/
image::team-logos/community-ops/commops.png[Fedora Community Ops team logo.]
{team_summary}
// NOTE: This variables are defined in ROOT/partials/attributes.adoc
[[profile]]
== Team profile
[cols=2]
|===
|*Team URL*
|{team_url}
|*Team status*
|{team_status}
|*Forum*
|link:{team_synch_communication}[{team_synch_communication_name}]
|*Chat*
|link:{team_asynch_communication}[{team_asynch_communication_name}]
|*Issue tracker*
|link:{team_issue_tracker}[{team_issue_tracker_name}]
|*Meeting schedule*
|link:{team_meetings}[{team_meetings_name}]
|*Meeting agenda* (A/V meetings)
|link:{team_meetings_agenda_url}[{team_meetings_agenda_name}]
|*Meeting minutes* (Matrix meetings)
|link:{team_meetings_minutes_url}[{team_meetings_minutes_name}]
|===
[[vision]]
== Vision
To foster a transparent, inclusive, and data-informed Fedora community that empowers collaboration, celebrates diversity, and continuously evolves.
We envision a community where contributors, teams, and leaders have the insight, tools, and support needed to sustain a thriving open source ecosystem.
[[mission]]
== Mission
The {team_name} (CommOps) strengthens the Fedora Project by connecting people, data, and process to create a more resilient, informed, and cohesive community.
Community Operations supports the lifecycle of community collaboration by supporting contributors and sustaining teams through data-driven insights, clear communication, and process excellence.
[[focus-areas]]
== Focus Areas
* *Community Activities*:
Supporting teams and community projects & initiatives that build contributor engagement and community growth.
* *Moderation & Community Collaboration*:
Partnering with moderation working groups to support a safe, respectful, and inclusive community culture.
* *Data & Analytics*:
Building and maintaining ethical, privacy-conscious analytics that provide visibility into community health, participation, and trends.
* *Events & Outreach*:
Collaborating with event organizers and outreach teams to enhance community experiences, from global conferences and local meetups.
* *Process Improvement & Incubation*:
Experimenting with and incubating new methods, tools, and workflows that improve how Fedora collaborates, communicates, and evolves.
[[goals]]
== Goals & objectives
The following are examples of where the {team_name} focuses:
* Work closely with xref:council::fca.adoc[Fedora Community Architect] to prioritize key focus areas
* Assist xref:council::foa.adoc[Fedora Operations Architect] with release preparations
* Support preparation and execution of link:{url_wiki}/Elections[Fedora Elections]
* Work with sub-projects and teams to improve on-boarding methods and practices
* Use metrics and data to improve understanding of Fedora community
** Support development of metrics tooling
[[contact]]
== Get in touch with us
The {team_name} uses a {team_asynch_communication}[{team_asynch_communication_name}] forum tag and a {team_synch_communication}[{team_synch_communication_name}] room to communicate.
The {team_asynch_communication}[{team_asynch_communication_name} forum tag] is best for _asynchronous_ communication.
This means it is best for questions or topics that someone may respond to later.
It is better for longer, threaded discussions.
The {team_synch_communication_name} room is best for _synchronous_ communication.
This means it is best for quick feedback, like in a conversation.
It is helpful for real-time discussions or getting someone's attention.
{team_asynch_communication_name} forum tag::
{team_asynch_communication}[{team_asynch_communication}]
{team_synch_communication_name} room::
link:{team_synch_communication}[`#commops:fedoraproject.org`]
[[workflow]]
== Workflow
The {team_name} uses a ticket-based workflow to keep track of our work.
The repository with tickets is found on link:{team_issue_tracker}[{team_issue_tracker_name}].
Tickets are found under the link:{team_issue_tracker}/-/issues[_Issues_] tab in the sidebar.
Various labels are used to sort and triage GitLab Issues.
For good beginner tasks, look at the link:{team_issue_tracker}/-/issues/++?label_name[]=good%20first%20issue++[_good first issue_] tag.
[[meetings]]
== Meetings
The {team_name} holds meetings every other week to check in on tasks and plan ahead.
This translates to two meetings a month.
One of the meetings is run via a text chat in a Matrix room.
The other meeting is run as an audio/video call.
Check link:{team_meetings}[{team_meetings_name}] for the next meeting date and time.
Past text meeting minutes are recorded in link:{team_meetings_minutes_url}[{team_meetings_minutes_name}].
[[meeting-format]]
=== Meeting format
The upcoming meeting agenda is found on link:{team_meetings_agenda_url}[{team_meetings_agenda_name}].
Meetings follow an agenda split into six parts:
. *Intros, welcomes, hellos*:
Appx. 5 minutes.
Waiting for others to arrive, opportunity to introduce yourself, and ask general questions.
. *Team announcements & news*:
Appx. 5-10 minutes.
Any Fedora news or updates to share with the wider team.
. *Initiative Co-leads updates to the team*:
Appx. 5-10 minutes.
Fedora Council updates from the Initiative Co-leads, if there are any.
. *Follow-ups from last meeting (if any)*:
Appx. 5-10 minutes.
Follow up on pending action items from the previous meeting.
. *Ticket discussions*:
Use the remaining meeting time.
Discussion and follow-up on tickets link:{team_issue_tracker}/-/issues/++?label_name[]=meeting%20topic%20request++[marked for meetings].
. *Open floor*:
Final 5-10 minutes of the meeting.
General discussion or comments, or time to discuss anything that had to be revisited during the meeting.
[[join]]
== Get involved
Read our guide on xref:join.adoc[how to join the {team_name}].
The team always welcomes new contributors.
Whether you are a newcomer or an old-timer, there are ways to get involved.
Join our team to do some or all of the following:
* Build your portfolio in open source community management
* Directly see the impact of your contributions over time
* Gain a holistic view of the Fedora Project and learn how the pieces fit together
* Work directly with Fedora Project leadership
* Work with teammates from around the world
* Aspire to the greatness of a community superhero
.Join the {team_name} today!
[#img-panda,caption="",link="join/"]
image::https://fedoraproject.org/w/uploads/7/72/Happypanda.png[Happy Panda,100]

107
modules/ROOT/pages/join.adoc Normal file
View file

@ -0,0 +1,107 @@
include::ROOT:partial$attributes.adoc[]
= Join Community Operations
Become a member of Fedora Community Operations (CommOps) by following these steps.
[[fas]]
== Create a FAS account
Create a {url_wiki}/Account_System[Fedora Account System account] and sign the {url_wiki}/Legal:Fedora_Project_Contributor_Agreement[Fedora Project Contributor Agreement].
Do this through the https://admin.fedoraproject.org/accounts/[Fedora Account System].
[[discourse]]
== Log into {team_asynch_communication_name}
Log into the {team_asynch_communication}[{team_asynch_communication_name} forum] using your FAS account credentials.
News, updates, and discussion are shared through on the forum.
It is a *key part* to how we communicate.
It receives low to medium traffic.
[[introduction]]
== Post a self-introduction
Say hello and introduce yourself to the team!
{team_asynch_communication}[Post a self-introduction] to {team_asynch_communication_name} and tell us a little about yourself.
Not sure what to say?
Answer these questions to start:
* Why are you interested in contributing to Fedora?
* Why are you interested in contributing to {team_name}?
* If you are involved with other things in Fedora, what are/were you working on?
* Do you have any experience in open source or online communities?
If so, what?
* What parts of {team_name} were interesting to you?
* Do you have any questions for us?
How can we help _you_ get started?
[[community-blog]]
== Register on Community Blog
The Fedora {url_commblog}[Community Blog] is a key component to CommOps.
An account gives permissions to view article drafts and previews before they are published.
If you ever write an article, you will need an account.
To register, log in at the {url_commblog}/wp-login.php[login page] with your Fedora Account System (FAS) credentials.
Need more help logging in?
Read the {url_commblog}/how-to-log-in/[help page] for more detailed instructions.
[[matrix]]
== Join our Matrix channel
Fedora uses the Matrix protocol for instant messaging and communication.
Our Matrix rooms can be accessed using any Matrix client, but https://element.io/[Element client] and the https://chat.fedoraproject.org/[chat.fedoraproject.org] web app are the most common and easiest ways to get started.
Discussions and planning take place in Matrix channel https://matrix.to/#/#commops:fedoraproject.org[#commops:fedoraproject.org], while our monthly team meetings are held in a meeting room such as https://matrix.to/#/#meeting:fedoraproject.org/[#meeting:fedoraproject.org].
[[first-steps]]
== Make your first steps
See xref:contribute/first-steps.adoc[Make your first steps in Fedora] for more info.
[[start-task]]
== Start on a task
CommOps uses https://gitlab.com/fedora/commops[this GitLab repository] to track our tasks and what we're working on.
Tasks, problems, and goals are filed as tickets in the https://gitlab.com/fedora/commops/home/-/issues[issue tracker].
There are a lot of tickets, but we're not working on everything at once.
Scrolling through the issue tracker gives a good idea of what CommOps helps with.
Look for the https://gitlab.com/fedora/commops/home/-/issues/?label_name%5B%5D=good%20first%20issue[good first issue] tag on tickets to find good tasks for beginners.
Does something look interesting?
Leave a comment if you have a question or want to work on something.
Also check and see if the ticket is assigned to someone.
If it is unassigned, you can start working on it now.
If there is an assignee, ask them if they need help or if they are still working on the ticket.
This provides an opportunity to receive mentorship and get help to start a new task.
[[meetings]]
== Join our meetings
CommOps has an IRC team meeting each week.
In our meeting, the team discusses items on our agenda and checks in on any progress of current tasks.
Tickets selected for meetings are updated after the meeting with new information.
The meetings are open to the public and anyone can join.
See when our meetings are in your time zone on the https://apps.fedoraproject.org/calendar/commops/[CommOps meeting calendar].
Feel free to attend and introduce yourself during roll call!
[[fasgroup]]
== Request to be added to CommOps in FAS
To get updates, and to gain access to different tools in CommOps, you'll need to join our FAS group. To be sponsored as a member of CommOps, raise a issue request in our https://gitlab.com/fedora/commops/home[repo here] with the following information.
* Your FAS ID
* What areas of Fedora Community Operations are you intersted in (community growth, analytics, engagement, etc)
The issue will be reviwed and after two members of CommOps add a +1 to the issue, you will be added to the FAS group.
Periodically, we may review the list of members in the FAS group and check in if you're still interested in contributing.
Inactive members may be removed after two Fedora Linux releases.

55
modules/ROOT/pages/planet.adoc Normal file
View file

@ -0,0 +1,55 @@
include::ROOT:partial$attributes.adoc[]
= How to enroll in Fedora Planet
Justin W. Wheeler <jww@fedoraproject.org>; Fedora community contributors
// Article content last reviewed and verified by a human on…
2025-02-17
[IMPORTANT]
====
Before you federate with the Fedora Planet, understand the guidelines on appropriate material to federate to Fedora Planet.
Read link:{url_wiki}/Planet#Appropriate_Material[these guidelines on appropriate material] before you aggregate your blog.
====
[[prerequisites]]
== Prerequisites
. Register a Fedora Account System (FAS) account.
. Sign the Fedora Project Contributor Agreement (FPCA).
. Be a member of at least one other group in the FAS system (also known as FPCA+1).
[[enroll]]
== Enroll your feed in Fedora Planet
. Configure a category on your blog for content containing link:{url_wiki}/Planet#Appropriate_Material[appropriate material] for Fedora Planet.
(For help with this, xref:#categories[see below].)
. Log into the https://accounts.fedoraproject.org/[Fedora Account System].
Navigate to your profile and click _Edit Profile_.
. Find the _RSS URL_ option.
. Paste the URL of your category-specific RSS/RSS2/Atom feed into the option box.
. Scroll to the bottom and click _Save_.
Your blog content will eventually appear on Fedora Planet, together with independently-authored content from other Fedora community members.
[NOTE]
====
There are two fields on the Fedora Account System profile page: *RSS URL* and *Blog URL*.
RSS URL is used to build Fedora Planet.
Any RSS feed you add to your profile will automatically be pulled into Fedora Planet.
Blog URL is used to publish a link to your public blog, so it can appear in your profile.
Blog URL is not used to build Fedora Planet.
====
[[categories]]
=== Using categories, labels, or tags
Use a single category, label, or tag on your personal blog to enroll in Fedora Planet, rather than your whole blog.
This allows you to highlight posts that are interesting for the Fedora community.
Here are some specific instructions for making a category or label and finding your correct URL:
* link:{url_wiki}/How_to_provide_a_category_specific_feed_using_WordPress[How to provide a category specific feed using WordPress]
* link:{url_wiki}/How_to_provide_a_category_specific_feed_using_Blogger[How to provide a category specific feed using Blogger]
* link:{url_wiki}/How_to_provide_a_category_specific_feed_using_Blogspot[How to provide a category specific feed using Blogspot]
* link:{url_wiki}/How_to_provide_a_category_specific_feed_using_Tumblr[How to provide a category specific feed using Tumblr]

168
modules/ROOT/pages/sig-howto.adoc Normal file
View file

@ -0,0 +1,168 @@
include::ROOT:partial$attributes.adoc[]
= Creating a Fedora SIG
Nancy Nwankwo; Justin Wheeler; Fedora community contributors
:description: Steps on how to start a Fedora Special Interest Group (SIG) using current communication platforms and tools.
:page-authors: {author}, {author_2}, {author_3}
:revdate: 2025-10-29
:revnumber: 1.0
This page provides instructional steps on how to start a Fedora SIG using current communication platforms and tools.
A Fedora Special Interest Group (SIG) is a group of people who share an interest in a specific topic or project within Fedora.
SIGs are easy to start and offer a great way to collaborate and work together on things you are passionate about, such as a new idea, project, or community effort.
This guide will show you the simple steps to create your own SIG using available tools and resources.
[[explore]]
== Step 1: Explore Other SIGs & Subprojects
You don’t have to reinvent the wheel!
Other SIGs may already be tackling related ideas or have systems in place that you can learn from.
Reach out and collaborate!
Examples:
* xref:design::index.adoc[*Fedora Design Team*]:
Helpful for logos, visuals, and branding your SIG.
* *xref:fedora-docs::index.adoc[Fedora Docs] or xref:infra::index.adoc[Infrastructure] teams*:
Great for guidance on hosting content or automation tools.
[[build-interest]]
== Step 2: Get Others Interested
Before creating a SIG, confirm that at least a few other Fedora contributors are interested in the topic.
You can:
* Post on link:{team_asynch_communication}[{team_asynch_communication_name}] (using the appropriate category or tag) and the link:https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org//[Fedora devel mailing list].
* Join a relevant {team_synch_communication_name} room and share your ideas.
The Fedora devel mailing list is a good place to start if you are not sure of what group to join.
Many Fedora developers and packagers can be found there.
Your post should clearly explain:
* What your proposed SIG is about
* Why it matters
* How others can get involved
.Example titles
----
“Looking to start a Fedora Edge Computing SIG, anyone interested?”
“Fedora for Students SIG: anyone want to join?”
----
[[basics]]
== Step 3: Set Up the Basics
Once there is enough interest, establish your SIG’s basic footprint in Fedora’s ecosystem.
This helps others find you and contributes to long-term sustainability.
.Required Setup
* Create a tag on {team_asynch_communication_name} (to organize conversations).
* xref:project::communications.adoc#_primary_channels[Request a {team_synch_communication_name} room].
If a related room exists or there isn’t much traffic yet, use the existing room and wait until there’s enough interest to request a new one.
* Create a Forgejo repository or project board (optional but useful for tracking tasks).
* Create a private mailing list for Bugzilla bugs (required for SIGs that maintain packages).
If you are unsure where to start, the xref:fedora-join::index.adoc[Fedora Join SIG] can assist.
[TIP]
====
Create a dedicated {team_asynch_communication_name} tag for your SIG early on.
It helps organize all related topics and makes your group easier to discover.
Drop into community-wide {team_synch_communication_name} rooms like link:++https://matrix.to/#/#social:fedoraproject.org++[`#social:fedoraproject.org`] or link:++https://matrix.to/#/#join:fedoraproject.org++[`#join:fedoraproject.org`] for community social chatter and quick help.
====
[[documentation]]
== Step 4: Document the SIG
Create a Fedora Docs site that introduces your SIG.
The Fedora Docs site index page should include:
* The SIG's mission and scope
* A list of communication channels
* Links to resources ({team_asynch_communication_name} tag, {team_synch_communication_name} room, Forgejo repo, etc.)
* How others can join or contribute
* Team leads or go-to people
You may:
* Publish this on the Fedora Docs page (_recommended_)
* Or as part of your Forgejo README
[NOTE]
====
While Fedora Wiki is still in use, SIGs are starting to move their documentation to Fedora Docs.
Fedora Docs are better because they are easier to find information and show up better in search results.
====
[[activities]]
== Step 5: Plan Your First Activities
SIGs gain momentum by working together toward shared goals.
Early actions might include:
* Tracking to-do items in a Forgejo issue board
* Organizing an async planning thread in {team_asynch_communication_name}
* Hosting a regular or one-time {team_synch_communication_name} meeting
You can also:
* Submit articles to link:https://fedoramagazine.org/[Fedora Magazine] to promote what your SIG is doing in Fedora
* Share contributor journeys and milestones on the link:{url_commblog}[Community Blog]
* Ping the xref:marketing::index.adoc[Marketing Team] for help with graphics, campaign ideas, and event promotion
* Get community planning and coordination tips from the xref:commops::index.adoc[Community Ops team]
* Reach out to other related SIGs for cross-group support
Further Reading:
* link:https://www.runn.io/blog/asynchronous-meeting/[_How to run good async meetings_]
[[keep-going]]
== Step 6: Keep It Going
Successful SIGs grow by being active, inclusive, and goal-driven.
Some tips:
* Review progress regularly (monthly/quarterly) and share public reports on progress.
* Actively welcome and onboard new contributors with documentation for newcomers and/or designated mentors to help onboard new contributors to the community.
* Share your progress publicly via blog posts, social media, local outreach, or mailing list.
* Define leadership roles or points of contact for long-term sustainability.
Need inspiration?
Check out well-run SIGs like xref:fedora-coreos::index.adoc[Fedora CoreOS] for best practices.
[[get-help]]
== Step 7: Where to Get Help
You are not doing this alone!
Fedora has a helpful, friendly community and lots of places where you can ask questions, get guidance, and find people to work with.
Here is a quick decision path:
|===
|I need help with… |Try reaching out to…
|Setting up SIG tools
|xref:fedora-join::index.adoc[Join SIG], xref:infra::index.adoc[Infra Team]
|Finding collaborators
|link:{team_asynch_communication}[{team_asynch_communication_name}], xref:fedora-join::index.adoc[Join SIG]
|Writing docs or onboarding guides
|xref:fedora-docs::index.adoc[Docs Team], xref:commops::index.adoc[Community Ops]
|Promotion & outreach
|xref:marketing::index.adoc[Marketing Team], xref:fedora-magazine::workflow-article-proposal.adoc[Fedora Magazine]
|Hosting meetings or async planning
|xref:project::communications.adoc#_primary_channels/[{team_synch_communication_name} rooms], link:{url_commblog}[Community Blog]
|Ending or pausing a SIG
|xref:council::index.adoc[Fedora Council], xref:fedora-join::index.adoc[Join SIG]
|===

88
modules/ROOT/pages/successful-contributor.adoc Normal file
View file

@ -0,0 +1,88 @@
include::ROOT:partial$attributes.adoc[]
= How to be a successful contributor
Audience for this document
--------------------------
This document is targeted at people interested in contributing to the Fedora Project. In the Fedora Project, students, professionals and hobbyists all come together to produce software, marketing materials, art, documentation, etc. We all started as new volunteers at some point. The items below are designed to help you through the process of joining a team. It helps you know what we expect of you and what you can expect of us.
Things to know before you join
------------------------------
So you think that you would enjoy being a successful contributor to Fedora. Great!! You are most welcome. Here are some thoughts to consider. Everyone who joins a free software project does so with the best intentions of staying. A few stay to become regular contributors, and fewer still become leaders within the project, and others lose interest. The biggest difference between those that stay and those that leave is "commitment and time".
Time commitment
---------------
A commitment requires reserving some time. If you strongly believe you will enjoy what you are doing, consider your dedication of time. Time commitment is as little as 4 hours per week. Some volunteers may spend 15-30 hours per week contributing. Doing that level of commitment while holding down a proper day job is a difficult time management skill. As a volunteer, you should ask yourself whether you can devote 2-4 hours per week, even though it's less than an hour per day. Four hours a week for most people is an entire afternoon one day. That's a significant chunk of time.
Get permission from work and family
-----------------------------------
Volunteering has great rewards in many ways. The two most prominent ones are your success at introducing a person to Fedora, another is your own ego. A third benefit is with your job.
There is a mutually beneficial relationship between working for a living and volunteering. Many contributors will find their skill sets at work increase dramatically just by having access to and learning from another environment. This volunteering benefits employer and worker. It is completely worthwhile to sit down with your employer and ask for permission to contribute during work hours, even if it's only a couple of hours on a Friday afternoon. If you are married, make sure your family agrees to your being busy for this time commitment. Your volunteering must be a win-win-win for the company, your family and you. Explain the benefits to you, to the business, and your family. Family is the important people in your social life. (spouse, friends, parents, others).
If work says no, then you will have to volunteer in your own time. Your family may be enthusiastic to help you. Volunteering is very rewarding.
Joining
-------
The single biggest mistake most new contributors make is showing up "just wanting to contribute." It's important to take the time to observe the team (refer to the section below) and see how their work aligns with your own skills and personality. Know that getting work to do on day one is very rare, and those who are highly skilled in a specific technology will still have to take the time to get to know an environment before access is granted.
For example, if you're a database expert it is very unlikely you'll be given access to databases (where personal info, passwords, etc are stored) within your first several weeks of volunteering. If you're looking to become an ambassador, it is unlikely you'll get marketing materials shipped to you in your first week. This may seem unfortunate, but it's necessary to keep the project members working well together. The same can be said about any major changes, like a complete redesign of a system or a new look and feel for a website. Don't get discouraged. Show up as often as you can, and get to know the team.
Observation
-----------
It is important to get to know the organization and teams you are looking to work with before you try to join them. Learn what they do and how they do it, and try to get to know the people involved. It is extremely unlikely you will be able to actually contribute from day one. In organizations with hundreds or thousands of people working together, understanding how things work is critical.
Don't be shy about asking questions and getting to know people. Plan to spend several days or even weeks attending meetings, emailing on mailing lists and hanging out on IRC before you get to do any actual work. Offer suggestions on topics being discussed, and share any experiences (good or bad) you've had that is relevant to the discussion.
Part of observing and making constructive suggestions may require withholding judgment. When making suggestions, don't assume you come with all of the answers or that the Fedora Project is ''doing it all wrong.'' There is a good chance we can improve the way we are doing things, however most of our current practices were developed over long periods of time after lengthy discussion. Your criticism may be better received once you have established yourself in the community and are perceived as understanding our culture.
Pick what you want to work on
-----------------------------
It's your job to decide what you want to work on. Pick something that's important to you and something you have passion for. You'll see this advice repeated several times in this document: Don't just show up looking to have work assigned to you. Get to know the teams and procedures they have in place. Ask questions and really get to know what you're going to be working on _before_ trying to work on it.
Don't jump into the deep end
----------------------------
When picking something to work on, don't be the sole person to take on a huge task as your first contribution. Picking a task that's too large significantly raises the chances of failure. Also don't pick several things on several teams to work on. Start small, picking at most one or two things, and grow from there. The key is slow, steady, and sustainable growth. Don't join with the immediate goal of becoming the next leader of the project. Start small.
First contact
-------------
After you've decided what you're looking to do and what team you are looking to do it with, it's time to send an introduction to the list. When sending an introduction (usually by mail list), include the following information:
* Name
* Time Zone / Country
* Basic skills and experiences
* Why you're joining
* What you're looking to do (be specific)
* How much time you can contribute (usually hours per week)
If any of the above questions are not clearly answered, don't send the email yet. You're not ready. Remember, be specific about what type of work you're looking to do. Saying "Whatever needs to get done" isn't helping anyone. Saying "I'd like to help document system A," "I'd like to translate software for my native language," or "I noticed this webapp is particularly slow sometimes and I'd like to help fix that" is perfect.
Find a mentor or sponsor
------------------------
This step is both incredibly difficult and important. Finding a proper sponsor will increase your chances of being a successful contributor significantly. Sometimes it's absolutely required. A sponsor will help with training, introductions and teaching new contributors how a team works.
Most teams have mailing lists. Email the list, say you're looking for a sponsor, and explain what you are wanting to do. If you haven't heard back in a few days, reply saying that you are still looking. ''Keep doing this.'' Most sponsors are people that have been in the project for a long time, and are often very busy.
They don't mean to be rude and don't want to send the impression they don't want new contributors. It's just that at the moment, some people will assume other people will take care of you and so for the moment, no one does. This is a common problem -- in real life as well as in online communities -- and a difficult one to fix. But sticking to it and continuing to ask for help without being annoying will show that you are serious and ready to contribute. Don't send this kind of message more than once every couple of days, but be positive, and persistent if needed.
Contributing
------------
Once you've got something to work on, it's time to actually do work. The first several tasks you will work on will likely be small or maybe mundane. Do them consistently, conscientiously and well. This will raise the level of trust you have from the other team members.
As with other volunteer organizations, there are high turnover rates in the free software universe. Training volunteers is time consuming, especially for more complex tasks, and requires a commitment from currently busy volunteers. Spending days or weeks training someone only for them to vanish can be disheartening for mentors and sponsors. By giving out small tasks that have been hanging around, a sponsor can help you take small but vital steps, and learn whether or not the work you're going to be doing is really for you.
Look for work
-------------
If you have access to a repository, system, or content, consider yourself a partial owner. This doesn't mean you should immediately re-design everything. Remember that other owners have time and effort invested in the current material as well. It does mean, though, that you should take pride in the work you are doing. If you see something not quite right, do research on it and notify the list. Seek work out, keep yourself busy and help others.
Quitting
--------
If you've found you've over-committed or decide volunteering isn't for you, that's OK. You don't need to be embarrassed that you can't contribute further. Contributors will not make you feel bad about it either. Realize that lots of contributors come and go every day. Being busy with your day job or not having enough free time is a perfectly valid reason for not being able to contribute. It's even possible that you might not feel a good fit with the team or organization. You're entitled to offer help as a volunteer how you want and when you want.
First and foremost, though, don't just vanish. When a contributor or potential contributor agrees to do work, can't follow through for a valid reason, and vanishes, the team may not know the work can be reassigned. In some cases, people in the team may even worry about the contributor's health or well being.
When you've decided it's time for you to go or take a break, let your sponsor or the list know and let them know what you were working on. Having people think you are working on something when you aren't slows the team down, and ultimately doesn't benefit you or the team.

39
modules/ROOT/partials/attributes.adoc Normal file
View file

@ -0,0 +1,39 @@
// This is a data store of information about the Fedora Community Operations Team.
// Team name:
:team_name: Fedora Community Operations Team
// Team summary:
:team_summary: The {team_name} provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication.
// Team page URL:
:team_url: https://docs.fedoraproject.org/en-US/commops/
// Team activity status.
// Choose from: Active, Inactive
:team_status: Active
// Preferred asynchronous communication channel
:team_asynch_communication: https://discussion.fedoraproject.org/tags/c/project/7/commops-team
:team_asynch_communication_name: Fedora Discussion
// Preferred synchronous communication channel
:team_synch_communication: https://matrix.to/#/#commops:fedoraproject.org
:team_synch_communication_name: Fedora Chat/Matrix
// Issue tracker
:team_issue_tracker: https://gitlab.com/fedora/commops/home
:team_issue_tracker_name: GitLab
// Meetings
:team_meetings: https://calendar.fedoraproject.org/commops/
:team_meetings_name: Fedora Calendar
:team_meetings_agenda_name: SFC Etherpad
:team_meetings_agenda_url: https://pad.sfconservancy.org/p/fedora-commops-meetings
:team_meetings_minutes_name: Møte
:team_meetings_minutes_url: https://meetbot.fedoraproject.org/teams/commops/
// Common URLs
:url_commblog: https://communityblog.fedoraproject.org
:url_fedmsg: https://fedmsg.readthedocs.io/en/stable/
:url_wiki: https://fedoraproject.org/wiki

BIN
modules/all-assets/Badge Artwork/2beeornot2bee.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 35 KiB

2597
modules/all-assets/Badge Artwork/2beeornot2bee.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 102 KiB

BIN
modules/all-assets/Badge Artwork/Join SIG.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 41 KiB

BIN
modules/all-assets/Badge Artwork/beesknees.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 39 KiB

2773
modules/all-assets/Badge Artwork/beesknees.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 112 KiB

BIN
modules/all-assets/Badge Artwork/community2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 41 KiB

2386
modules/all-assets/Badge Artwork/community2_1.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 207 KiB

BIN
modules/all-assets/Badge Artwork/even organizer.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 39 KiB

2276
modules/all-assets/Badge Artwork/even organizer.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 86 KiB

62249
modules/all-assets/Badge Artwork/join SIG.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 2.7 MiB

BIN
modules/all-assets/Badge Artwork/marketing.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 33 KiB

2260
modules/all-assets/Badge Artwork/marketing.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 90 KiB

BIN
modules/all-assets/Badge Artwork/onboarding-idea.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 36 KiB

3267
modules/all-assets/Badge Artwork/onboarding-idea.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 133 KiB

BIN
modules/all-assets/Badge Artwork/onboarding.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 38 KiB

2825
modules/all-assets/Badge Artwork/onboarding.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 116 KiB

BIN
modules/all-assets/Badge Artwork/onboarding2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 40 KiB

3225
modules/all-assets/Badge Artwork/onboarding2.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 133 KiB

BIN
modules/all-assets/Badge Artwork/sighting.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 33 KiB

2688
modules/all-assets/Badge Artwork/sighting.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 114 KiB

BIN
modules/all-assets/Badge Artwork/welcome.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 32 KiB

2326
modules/all-assets/Badge Artwork/welcome.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 85 KiB

BIN
modules/all-assets/Badge Artwork/welcome2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 31 KiB

2314
modules/all-assets/Badge Artwork/welcome2.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 82 KiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_communityoutreachteams.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.1 MiB

4605
modules/all-assets/Cheat Cubes/cheatcube_communityoutreachteams.svg Normal file
View file

File diff suppressed because it is too large Load diff
Side by side

After

Width:  |  Height:  |  Size: 267 KiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_fedorafriends.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.2 MiB

7724
modules/all-assets/Cheat Cubes/cheatcube_fedorafriends.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 1.2 MiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_fourfoundations.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 645 KiB

3427
modules/all-assets/Cheat Cubes/cheatcube_fourfoundations.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 195 KiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_howtojoinFedora_version2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 881 KiB

5837
modules/all-assets/Cheat Cubes/cheatcube_howtojoinFedora_version2.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 329 KiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_howtojoinfedora_version1.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 798 KiB

4452
modules/all-assets/Cheat Cubes/cheatcube_howtojoinfedora_version1.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 205 KiB

BIN
modules/all-assets/Cheat Cubes/cheatcube_packaging.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.5 MiB

4986
modules/all-assets/Cheat Cubes/cheatcube_packaging.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 450 KiB

BIN
modules/all-assets/Fedora Slide Template/fedoraslidetemplate_newbrand.odp Normal file
View file

Binary file not shown.

BIN
modules/all-assets/Fedora Slide Template/fedoraslidetemplate_newbrand.pdf Normal file
View file

Binary file not shown.

BIN
modules/all-assets/Fedora Slide Template/fedoraslidetemplate_newbrand.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 112 KiB

BIN
modules/all-assets/Four Foundations Bandana/bandana v4.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 1.5 MiB

19943
modules/all-assets/Four Foundations Bandana/bandana v4.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 1.9 MiB

BIN
modules/all-assets/How to Join Fedora/Cheat Cube Version 1/cheatcube_howtojoinfedora_version1.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 798 KiB

4452
modules/all-assets/How to Join Fedora/Cheat Cube Version 1/cheatcube_howtojoinfedora_version1.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 205 KiB

BIN
modules/all-assets/How to Join Fedora/Cheat Cube Version 2/Copy of cheatcube_howtojoinFedora_version2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 881 KiB

5837
modules/all-assets/How to Join Fedora/Cheat Cube Version 2/Copy of cheatcube_howtojoinFedora_version2.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 329 KiB

875
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_German.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 610 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_english.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 239 KiB

855
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_english.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 609 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_french.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 242 KiB

887
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_french.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 610 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_german.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 247 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_hindi.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 234 KiB

883
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_hindi.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 610 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_portuguese.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 245 KiB

869
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_portuguese.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 610 KiB

BIN
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_spanish.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 244 KiB

870
modules/all-assets/How to Join Fedora/Print Version 1/howtojoinfedora_printversion1_spanish.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 610 KiB

1894
modules/all-assets/How to Join Fedora/Print Version 2/howtojoinfedora_printversion2_French.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 125 KiB

1838
modules/all-assets/How to Join Fedora/Print Version 2/howtojoinfedora_printversion2_German.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 122 KiB

1841
modules/all-assets/How to Join Fedora/Print Version 2/howtojoinfedora_printversion2_Portuguese.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 122 KiB

1827
modules/all-assets/How to Join Fedora/Print Version 2/howtojoinfedora_printversion2_Spanish.svg Normal file
View file

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

After

Width:  |  Height:  |  Size: 121 KiB

Some files were not shown because too many files have changed in this diff Show more