From d70e519a329eabfd83224ee45d8306419954db19 Mon Sep 17 00:00:00 2001 From: Adam Samalik Date: Jul 27 2018 13:43:28 +0000 Subject: switch to Antora --- diff --git a/.gitignore b/.gitignore index fa62c5c..9f3ebf5 100644 --- a/.gitignore +++ b/.gitignore @@ -1,9 +1,3 @@ -## AsciiBinder-specific ignores -_preview -_package -*.swp -diag-*.png -diag-*.png.cache - -## Project-specific ignores -_l10n/pot/ +build +cache +public diff --git a/README.md b/README.md index d7fe12c..82ad1f6 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,10 @@ -# Fedora Council Docs +# Fedora Modularity Docs Please report Issues and submit Pull Requests for **Content Fixes** here. Never done a pull request (or "PR")? Here's the [Pagure documentation for Pull Requests](https://docs.pagure.org/pagure/usage/pull_requests.html). -Note that since this is official Fedora Council documentation, some changes -may need agreement from the Council as a whole first. Generally, that's -pages dealing with policies or project structure, and when it's more than -just fixing typos. In general, the Council member reviewing a PR should -apply common sense and escalate to a -[Council ticket](https://pagure.io/Fedora-Council/tickets/) where appropriate. - General appearance issues and publishing issues should be reported against the [publishing software](https://pagure.io/fedora-docs/docs-fp-o). @@ -23,21 +16,28 @@ markup language. You may want to look at: * [AsciiDoc Syntax Quick Reference](http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/) * [AsciiDoc Writer’s Guide](http://asciidoctor.org/docs/asciidoc-writers-guide/) -* [Asciidoctor Diagram](http://asciidoctor.org/docs/asciidoctor-diagram/) (We use ditaa) +* [Antora Documentation](https://docs.antora.org/antora/1.0/page/) + -## Testing your changes locally +## Local preview -To test your changes, first install `asciibinder` +This repo includes scripts to build and preview the contents of this repository. -$ gem install ascii_binder +**NOTE**: Please note that if you reference pages from other repositoreis, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions. -To build your changes, from the root directory: +Both scripts use docker, so please make sure you have it installed on your system. Please see below for instructions. + +To build and preview the site, run: ``` -$ asciibinder package -$ firefox _package/main/index.html +$ ./build.sh && ./preview.sh ``` -**Help wanted**: We need Ruby packaging experts to [help us get asciibinder -into Fedora as an -RPM](https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org/message/7ZWMVGQ3RXDWAJNP3OOZXBC57SYB5IF5/). +The result will be available at http://localhost:8080 + +### Installing docker on Fedora + +``` +$ sudo dnf install docker +$ sudo systemctl start docker && sudo systemctl enable docker +``` diff --git a/_distro_map.yml b/_distro_map.yml deleted file mode 100644 index 40c5132..0000000 --- a/_distro_map.yml +++ /dev/null @@ -1,11 +0,0 @@ ---- -fedora: - name: Council Docs - author: Fedora Council - site: main - site_name: Home - site_url: https://docs.fedoraproject.org/ - branches: - master: - name: - dir: master diff --git a/_images/404.html b/_images/404.html deleted file mode 100644 index 898edfb..0000000 --- a/_images/404.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - - - Fedora Documentation Website - - - - - - - - - - - - - -
-
-
- -

Fedora Documentation Site

-
-
-
-
-

Fedora Documentation - 404 Page Not Found :(

-

Hi! You've arrived at Fedora documentation page which does not actually exist. This may be because you followed a link to an older document which has been retired. For reference, you can find those in our old document archive. Or, you can browse current docs.

-

It may also be that this page _should_ exist, but sadly does not. If this is the case, and you know what it should say, you can contribute via the Docs Project.

-
-
-
- -
-
-
-
-
-

About

-
-
-
About Fedora
-
Sponsors
-
Fedora Magazine
-
Legal
-
-
    -
  • - -
    • -
  • - -
    • -
  • - -
    • -
-
-
- -
-

Download

-
-
-
Get Fedora Workstation
-
Get Fedora Server
-
Get Fedora Atomic
-
Fedora Spins
-
Fedora Labs
-
Fedora ARM®
-
Alternative Downloads
- -
-
-
- -
-

Support

-
-
-
Get Help
-
Ask Fedora
-
Common Bugs
-
Fedora Developer Portal
-
Installation Guide
-
-
-
- -
-

Join

-
-
-
Join Fedora
-
Planet Fedora
-
Fedora SIGs
-
Fedora Account System
-
Fedora Community
-
-
-
-
- -
-
-
- -
-
-
-
- - -

© 2017 Red Hat, Inc. and others. Please send any comments or corrections to the websites team

-
-
-
- -
-
-
- - - - - - diff --git a/_images/favicon.ico b/_images/favicon.ico deleted file mode 100644 index a912017..0000000 Binary files a/_images/favicon.ico and /dev/null differ diff --git a/_images/favicon32x32.png b/_images/favicon32x32.png deleted file mode 100644 index d33bd5e..0000000 Binary files a/_images/favicon32x32.png and /dev/null differ diff --git a/_images/fedora.svg b/_images/fedora.svg deleted file mode 100644 index e8fd52b..0000000 --- a/_images/fedora.svg +++ /dev/null @@ -1,61 +0,0 @@ - - - - - - - - - - - - - - - - - - - diff --git a/_images/redhat-logo.png b/_images/redhat-logo.png deleted file mode 100644 index f085f1a..0000000 Binary files a/_images/redhat-logo.png and /dev/null differ diff --git a/_javascripts/.gitkeep b/_javascripts/.gitkeep deleted file mode 100644 index e69de29..0000000 --- a/_javascripts/.gitkeep +++ /dev/null diff --git a/_javascripts/bootstrap-offcanvas.js b/_javascripts/bootstrap-offcanvas.js deleted file mode 100644 index 62cf7b6..0000000 --- a/_javascripts/bootstrap-offcanvas.js +++ /dev/null @@ -1,6 +0,0 @@ -$(document).ready(function () { - $('[data-toggle="offcanvas"]').click(function () { - $('.sidebar').show(); - $('.row-offcanvas').toggleClass('active'); - }); -}); diff --git a/_stylesheets/asciibinder.css b/_stylesheets/asciibinder.css deleted file mode 100644 index 5ed14b9..0000000 --- a/_stylesheets/asciibinder.css +++ /dev/null @@ -1,576 +0,0 @@ -@import url(https://maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css); -/* ------------------------------------------------------------ -Image: "Spin" https://www.flickr.com/photos/eflon/3655695161/ -Author: eflon https://www.flickr.com/photos/eflon/ -License: https://creativecommons.org/licenses/by/2.0/ ----------------------------------------------------------------*/ -.attribution { - text-align: center; - position: relative; - bottom: -20px; -} -.attribution .btn { - color: #808080; - color: rgba(175,175,175, .65); - font-size: 11px; -} -.attribution .btn:hover { - text-decoration: none; - color: #aaa; -} -.popover-content { - font-size: 12px; - line-height: 1.3; - font-weight: normal; -} - -@media screen and (max-width: 980px) { - body { - margin-bottom: 200px; - } - footer { - text-align: center; - } - footer .text-right { - text-align: center !important; - } - #footer_social .first { - margin-left: 0; - } - #footer_social > a { - top: 24px; - } -} - -.fa-inverse:hover { - color: #ccc; -} - -.collapse a.active { - background-color: #DEEAF4; - color: #000; - position: relative; -} - -.collapse a.active:hover { - text-decoration: none; -} - -.collapse a.active:before { - background-color: #A0C3E5; - content: ""; - display: inline-block; - height: 100%; - left: 0; - position: absolute; - top: 0; - width: 3px; -} - -.main h2, .main .h2 { - border-top: 0px; - padding-top: 10px; - font-size: 28px; -} - -.page-header { - height: 100% !important; -} -.page-header .img-responsive { - display: inline; -} -.page-header h2 { - font-size: 32px; - display: inline; - vertical-align: bottom; -} - -.navbar-brand { - padding: initial; - height: initial; -} - -.nav > li > a.hover{ - background-color: none; -} - -h1, h2, h3, h4, h5, h6, .h1, .h2, .h3, .h4, .h5, .h6 { - position: relative; -} - -h2 > a.anchor, h3 > a.anchor, h4 > a.anchor, h5 > a.anchor, h6 > a.anchor { - display: block; - font-weight: normal; - margin-left: -1.5ex; - position: absolute; - text-align: center; - text-decoration: none !important; - visibility: hidden; - width: 1.5ex; - z-index: 1001; -} - -h2 > a.anchor:before, h3 > a.anchor:before, h4 > a.anchor:before, h5 > a.anchor:before, h6 > a.anchor:before { - content: "\f0c1"; - display: block; - font-family: FontAwesome; - font-size: 0.7em; - -webkit-font-smoothing: antialiased; - -moz-osx-font-smoothing: grayscale; - padding-top: 0.2em; -} - -h4 > a.anchor:before, h5 > a.anchor:before, h6 > a.anchor:before { - font-size: 1em; -} - -h2:hover > a.anchor, -h2 > a.anchor:hover, -h3:hover > a.anchor, -h3 > a.anchor:hover, -h4:hover > a.anchor, -h4 > a.anchor:hover, -h5:hover > a.anchor, -h5 > a.anchor:hover, -h6:hover > a.anchor, -h6 > a.anchor:hover { - visibility: visible; -} - -.main { - border-left: 1px solid #e7e7e7; - margin-left: -1px; - padding-left: 25px; -} - - -@media (min-width: 768px) { - .main { - padding-left: 30px; - } -} - -/* - * Sidebar - */ - -.nav-header { - font-size: 16px; -} - -.nav-header ul { - font-size: 14px; -} - -.nav-header ul li a { - display: block; - padding: 5px 20px 5px 25px; - font-size: 13px; - font-weight: normal; -} - -.nav-sidebar .fa { - text-align: center; - top: -1px; - width: 14px; -} - -.nav-sidebar li a { - color: inherit; -} - -.nav-sidebar li a:hover { - color: #000; -} - -.nav-sidebar ul li ul.nav-tertiary li a { - padding-left: 50px; -} - -.nav-sidebar > li > a { - padding: 7px 0; -} - -.nav-sidebar > li > a:focus, .nav-sidebar > li > a:hover { - background: transparent; -} - -.sidebar { - font-weight: 300; - display: none; - padding-top: 13px; -} - -@media screen and (max-width: 767px) { - .sidebar { - padding-left: 30px; - padding-right: 0; - } -} - -@media screen and (min-width: 768px) { - .sidebar { - border-right: 1px solid #e7e7e7; - display: block; - } -} - -/* - * Off Canvas - * -------------------------------------------------- - */ - -body, html { - overflow-x: hidden; /* Prevent scroll on narrow devices */ - font-family: "Overpass", sans-serif; -} - -.toggle-nav { - margin-right: 20px; -} - -@media screen and (max-width: 767px) { - .row-offcanvas { - position: relative; - -webkit-transition: all .25s ease-out; - -o-transition: all .25s ease-out; - transition: all .25s ease-out; - } - - .row-offcanvas-right { - right: 0; - } - - .row-offcanvas-left { - left: 0; - } - - .row-offcanvas-right - .sidebar-offcanvas { - right: -75%; /* 8 columns */ - } - - .row-offcanvas-left - .sidebar-offcanvas { - left: -75%; /* 8 columns */ - } - - .row-offcanvas-right.active { - right: 75%; /* 8 columns */ - } - - .row-offcanvas-left.active { - left: 75%; /* 8 columns */ - } - - .sidebar-offcanvas { - overflow: hidden; - position: absolute; - top: 0; - width: 75%; /* 8 columns */ - } -} - - p { - margin: 0 0 1.6em; - } - - /* Remnants of Asciidoctor default stylesheet - remove styles as needed */ - -#map_canvas img, #map_canvas embed, #map_canvas object, .map_canvas img, .map_canvas embed, .map_canvas object { max-width: none !important; } -.left { float: left !important; } -.right { float: right !important; } -.text-left { text-align: left !important; } -.text-right { text-align: right !important; } -.text-center { text-align: center !important; } -.text-justify { text-align: justify !important; } -.hide { display: none; } -.subheader, #content #toctitle, .admonitionblock td.content > .title, .audioblock > .title, .exampleblock > .title, .imageblock > .title, .listingblock > .title, .literalblock > .title, .stemblock > .title, .openblock > .title, .paragraph > .title, .quoteblock > .title, table.tableblock > .title, .verseblock > .title, .videoblock > .title, .dlist > .title, .olist > .title, .ulist > .title, .qlist > .title, .hdlist > .title { line-height: 1.4; color: #7a2518; font-weight: 300; margin-top: 0.2em; margin-bottom: 0.5em; } -abbr, acronym { text-transform: uppercase; font-size: 90%; color: #333333; border-bottom: 1px dotted #dddddd; cursor: help; } -abbr { text-transform: none; } -blockquote { margin: 0 0 1.25em; padding: 0.5625em 1.25em 0 1.1875em; border-left: 3px solid #487c58; } -blockquote cite { display: block; font-size: inherit; color: #454545; } -blockquote cite:before { content: "\2014 \0020"; } -blockquote cite a, blockquote cite a:visited { color: #454545; } -blockquote, blockquote p { line-height: 1.6; color: #6e6e6e; } -@media only screen and (min-width: 768px) { - #toctitle, .sidebarblock > .content > .title { line-height: 1.4; } - #toctitle, .sidebarblock > .content > .title { font-size: 1.6875em; } -} -table { background: white; margin-bottom: 1.25em; border: solid 1px #dddddd; } -table thead, table tfoot { background: whitesmoke; font-weight: bold; } -table thead tr th, table thead tr td, table tfoot tr th, table tfoot tr td { padding: 0.5em 0.625em 0.625em; font-size: inherit; color: #333333; text-align: left; } -table tr th, table tr td { padding: 0.5625em 0.625em; font-size: inherit; color: #333333; } -table tr.even, table tr.alt, table tr:nth-of-type(even) { background: #f9f9f9; } -table tr.even.nostriping, table tr.alt, table tr:nth-of-type(even) { background: #ffffff; } -table thead tr th, table tfoot tr th, table tbody tr td, table tr td, table tfoot tr td { display: table-cell; line-height: 1.6; } -.clearfix:before, .clearfix:after, .float-group:before, .float-group:after { content: " "; display: table; } -.clearfix:after, .float-group:after { clear: both; } -*:not(pre) > code { font-size: inherit; padding: 0; white-space: nowrap; background-color: inherit; border: 0 solid #dddddd; -webkit-border-radius: 4px; border-radius: 4px; text-shadow: none; line-height: 1; } -.keyseq { color: #666666; } -kbd:not(.keyseq) { display: inline-block; color: #333333; font-size: 0.75em; line-height: 1.4; background-color: #f7f7f7; border: 1px solid #ccc; -webkit-border-radius: 3px; border-radius: 3px; -webkit-box-shadow: 0 1px 0 rgba(0, 0, 0, 0.2), 0 0 0 2px white inset; box-shadow: 0 1px 0 rgba(0, 0, 0, 0.2), 0 0 0 2px white inset; margin: -0.15em 0.15em 0 0.15em; padding: 0.2em 0.6em 0.2em 0.5em; vertical-align: middle; white-space: nowrap; } -.keyseq kbd:first-child { margin-left: 0; } -.keyseq kbd:last-child { margin-right: 0; } -.menuseq, .menu { color: #1a1a1a; } -b.button:before, b.button:after { position: relative; top: -1px; font-weight: normal; } -b.button:before { content: "["; padding: 0 3px 0 2px; } -b.button:after { content: "]"; padding: 0 2px 0 3px; } -p a > code:hover { color: #561309; } -#header, #content, #footnotes, #footer { width: 100%; margin-left: auto; margin-right: auto; margin-top: 0; margin-bottom: 0; max-width: 62.5em; *zoom: 1; position: relative; padding-left: 0.9375em; padding-right: 0.9375em; } -#header:before, #header:after, #content:before, #content:after, #footnotes:before, #footnotes:after, #footer:before, #footer:after { content: " "; display: table; } -#header:after, #content:after, #footnotes:after, #footer:after { clear: both; } -#content:before { content: none; } -#header { margin-bottom: 2.5em; } -#header > h1 { color: black; font-weight: 300; border-bottom: 1px solid #d8d8d8; margin-bottom: -28px; padding-bottom: 32px; } -#header span { color: #6e6e6e; } -#header #revnumber { text-transform: capitalize; } -#header br { display: none; } -#header br + span { padding-left: 3px; } -#header br + span:before { content: "\2013 \0020"; } -#header br + span.author { padding-left: 0; } -#header br + span.author:before { content: ", "; } -#toc { border-bottom: 3px double #e5e5e5; padding-top: 1em; padding-bottom: 1.25em; } -#toc > ul { margin-left: 0.25em; } -#toc ul.sectlevel0 > li > a { font-style: italic; } -#toc ul.sectlevel0 ul.sectlevel1 { margin-left: 0; margin-top: 0.5em; margin-bottom: 0.5em; } -#toc ul { font-family: "Open Sans", "DejaVu Sans", "Sans", sans-serif; list-style-type: none; } -#toc a { text-decoration: none; } -#toc a:active { text-decoration: underline; } -#toctitle { color: #7a2518; } -@media only screen and (min-width: 768px) { body.toc2 { padding-left: 15em; padding-right: 0; } - #toc.toc2 { background-color: #fafaf9; position: fixed; width: 15em; left: 0; top: 0; border-right: 1px solid #e5e5e5; border-bottom: 0; z-index: 1000; padding: 1.25em 1em; height: 100%; overflow: auto; } - #toc.toc2 #toctitle { margin-top: 0; font-size: 1.2em; } - #toc.toc2 > ul { font-size: .90em; margin-bottom: 0; } - #toc.toc2 ul ul { margin-left: 0; padding-left: 1em; } - #toc.toc2 ul.sectlevel0 ul.sectlevel1 { padding-left: 0; margin-top: 0.5em; margin-bottom: 0.5em; } - body.toc2.toc-right { padding-left: 0; padding-right: 15em; } - body.toc2.toc-right #toc.toc2 { border-right: 0; border-left: 1px solid #e5e5e5; left: auto; right: 0; } } -@media only screen and (min-width: 1280px) { body.toc2 { padding-left: 20em; padding-right: 0; } - #toc.toc2 { width: 20em; } - #toc.toc2 #toctitle { font-size: 1.375em; } - #toc.toc2 > ul { font-size: 0.95em; } - #toc.toc2 ul ul { padding-left: 1.25em; } - body.toc2.toc-right { padding-left: 0; padding-right: 20em; } } -#content #toc { border-style: solid; border-width: 1px; border-color: #e3e3dd; margin-bottom: 1.25em; padding: 1.25em; background: #fafaf9; border-width: 0; -webkit-border-radius: 4px; border-radius: 4px; } -#content #toc > :first-child { margin-top: 0; } -#content #toc > :last-child { margin-bottom: 0; } -#content #toctitle { font-size: 1.375em; } -#footer { max-width: 100%; background-color: #333333; padding: 1.25em; } -#footer-text { color: #cccccc; line-height: 1.44; } -.audioblock, .imageblock, .literalblock, .listingblock, .stemblock, .verseblock, .videoblock { margin-bottom: 2.5em; } -.admonitionblock td.content > .title, .audioblock > .title, .exampleblock > .title, .imageblock > .title, .listingblock > .title, .literalblock > .title, .stemblock > .title, .openblock > .title, .paragraph > .title, .quoteblock > .title, table.tableblock > .title, .verseblock > .title, .videoblock > .title, .dlist > .title, .olist > .title, .ulist > .title, .qlist > .title, .hdlist > .title { text-rendering: optimizeLegibility; text-align: left; font-family: "Noto Serif", "DejaVu Serif", "Serif", serif; font-weight: normal; font-style: italic; } -table.tableblock > caption.title { white-space: nowrap; overflow: visible; max-width: 0; } -table.tableblock #preamble > .sectionbody > .paragraph:first-of-type p { font-size: inherit; } -.admonitionblock > table { border: 0; background: none; width: 100%; } -.admonitionblock > table td.icon { text-align: center; width: 80px; } -.admonitionblock > table td.icon img { max-width: none; } -.admonitionblock > table td.icon .title { font-weight: 300; text-transform: uppercase; } -.admonitionblock > table td.content { padding-left: 0; padding-right: 1.25em; color: #6e6e6e; } -.admonitionblock > table td.content > :last-child > :last-child { margin-bottom: 0; } -.exampleblock > .content { border-style: solid; border-width: 1px; border-color: #e6e6e6; margin-bottom: 1.25em; padding: 1.25em; background: white; -webkit-border-radius: 4px; border-radius: 4px; } -.exampleblock > .content > :first-child { margin-top: 0; } -.exampleblock > .content > :last-child { margin-bottom: 0; } -.exampleblock > .content h1, .exampleblock > .content h2, .exampleblock > .content h3, .exampleblock > .content #toctitle, .sidebarblock.exampleblock > .content > .title, .exampleblock > .content h4, .exampleblock > .content h5, .exampleblock > .content h6, .exampleblock > .content p { color: #333333; } -.exampleblock > .content h1, .exampleblock > .content h2, .exampleblock > .content h3, .exampleblock > .content #toctitle, .sidebarblock.exampleblock > .content > .title, .exampleblock > .content h4, .exampleblock > .content h5, .exampleblock > .content h6 { line-height: 1; margin-bottom: 0.625em; } -.exampleblock > .content h1.subheader, .exampleblock > .content h2.subheader, .exampleblock > .content h3.subheader, .exampleblock > .content .subheader#toctitle, .sidebarblock.exampleblock > .content > .subheader.title, .exampleblock > .content h4.subheader, .exampleblock > .content h5.subheader, .exampleblock > .content h6.subheader { line-height: 1.4; } -.exampleblock.result > .content { -webkit-box-shadow: 0 1px 8px #e3e3dd; box-shadow: 0 1px 8px #e3e3dd; } -.sidebarblock { border-style: solid; border-width: 1px; border-color: #e3e3dd; margin-top: -1.0em; margin-bottom: 1.6em; margin-left: 1em; padding: .5em; background: #F1F3F5; -webkit-border-radius: 4px; border-radius: 4px; overflow-x: auto; float: right; width: 40%; } -.sidebarblock > :first-child { margin-top: 0; } -.sidebarblock > :last-child { margin-bottom: 0; } -.sidebarblock h1, .sidebarblock h2, .sidebarblock h3, .sidebarblock #toctitle, .sidebarblock > .content > .title, .sidebarblock h4, .sidebarblock h5, .sidebarblock h6, .sidebarblock p { color: #333333; } -.sidebarblock h1, .sidebarblock h2, .sidebarblock h3, .sidebarblock #toctitle, .sidebarblock > .content > .title, .sidebarblock h4, .sidebarblock h5, .sidebarblock h6 { line-height: 1; margin-bottom: 0.625em; } -.sidebarblock h1.subheader, .sidebarblock h2.subheader, .sidebarblock h3.subheader, .sidebarblock .subheader#toctitle, .sidebarblock > .content > .subheader.title, .sidebarblock h4.subheader, .sidebarblock h5.subheader, .sidebarblock h6.subheader { line-height: 1.4; } -.sidebarblock > .content > .title { color: inherit; font-size: 28px; font-weight: 500; margin-top: 0; line-height: 1.6; } -.width50 { width: 50% ! important} -.exampleblock > .content > :last-child > :last-child, .exampleblock > .content .olist > ol > li:last-child > :last-child, .exampleblock > .content .ulist > ul > li:last-child > :last-child, .exampleblock > .content .qlist > ol > li:last-child > :last-child, .sidebarblock > .content > :last-child > :last-child, .sidebarblock > .content .olist > ol > li:last-child > :last-child, .sidebarblock > .content .ulist > ul > li:last-child > :last-child, .sidebarblock > .content .qlist > ol > li:last-child > :last-child { margin-bottom: 0; } -.literalblock pre, .literalblock pre[class], .listingblock pre, .listingblock pre[class] { border: 0px; background-color: #F0F3F5; -webkit-border-radius: 5px; border-radius: 5px; padding: 1.5em 2.5em; word-wrap: break-word; } -.literalblock pre.nowrap, .literalblock pre[class].nowrap, .listingblock pre.nowrap, .listingblock pre[class].nowrap { overflow-x: auto; white-space: pre; word-wrap: normal; } -.literalblock pre > code, .literalblock pre[class] > code, .listingblock pre > code, .listingblock pre[class] > code { display: block; } -.listingblock > .content { position: relative; } -.listingblock:hover code[class*=" language-"]:before { text-transform: uppercase; font-size: 0.9em; color: #999; position: absolute; top: 0.375em; right: 0.375em; } -.listingblock:hover code.asciidoc:before { content: "asciidoc"; } -.listingblock:hover code.clojure:before { content: "clojure"; } -.listingblock:hover code.css:before { content: "css"; } -.listingblock:hover code.go:before { content: "go"; } -.listingblock:hover code.groovy:before { content: "groovy"; } -.listingblock:hover code.html:before { content: "html"; } -.listingblock:hover code.java:before { content: "java"; } -.listingblock:hover code.javascript:before { content: "javascript"; } -.listingblock:hover code.python:before { content: "python"; } -.listingblock:hover code.ruby:before { content: "ruby"; } -.listingblock:hover code.sass:before { content: "sass"; } -.listingblock:hover code.scss:before { content: "scss"; } -.listingblock:hover code.xml:before { content: "xml"; } -.listingblock:hover code.yaml:before { content: "yaml"; } -.listingblock.terminal pre .command:before { content: attr(data-prompt); padding-right: 0.5em; color: #999; } -.listingblock.terminal pre .command:not([data-prompt]):before { content: '$'; } -table.pyhltable { border: 0; margin-bottom: 0; } -table.pyhltable td { vertical-align: top; padding-top: 0; padding-bottom: 0; } -table.pyhltable td.code { padding-left: .75em; padding-right: 0; } -.highlight.pygments .lineno, table.pyhltable td:not(.code) { color: #999; padding-left: 0; padding-right: .5em; border-right: 1px solid #d8d8d8; } -.highlight.pygments .lineno { display: inline-block; margin-right: .25em; } -table.pyhltable .linenodiv { background-color: transparent !important; padding-right: 0 !important; } -.quoteblock { margin: 0 0 1.25em 0; padding: 0.5625em 1.25em 0 1.1875em; border-left: 3px solid #487c58; } -.quoteblock blockquote { margin: 0 0 1.25em 0; padding: 0 0 0.625em 0; border: 0; } -.quoteblock blockquote > .paragraph:last-child p { margin-bottom: 0; } -.quoteblock .attribution { margin-top: -0.625em; padding-bottom: 0.625em; font-size: inherit; color: #454545; line-height: 1.6; } -.quoteblock .attribution br { display: none; } -.quoteblock .attribution cite { display: block; } -table.tableblock { max-width: 100%; } -table.tableblock td .paragraph:last-child p > p:last-child, table.tableblock th > p:last-child, table.tableblock td > p:last-child { margin-bottom: 0; } -table.spread { width: 100%; } -table.tableblock, th.tableblock, td.tableblock { border: 0 solid #dddddd; } -table.grid-all th.tableblock, table.grid-all td.tableblock { border-width: 0 1px 1px 0; } -table.grid-all tfoot > tr > th.tableblock, table.grid-all tfoot > tr > td.tableblock { border-width: 1px 1px 0 0; } -table.grid-cols th.tableblock, table.grid-cols td.tableblock { border-width: 0 1px 0 0; } -table.grid-all * > tr > .tableblock:last-child, table.grid-cols * > tr > .tableblock:last-child { border-right-width: 0; } -table.grid-rows th.tableblock, table.grid-rows td.tableblock { border-width: 0 0 1px 0; } -table.grid-all tbody > tr:last-child > th.tableblock, table.grid-all tbody > tr:last-child > td.tableblock, table.grid-all thead:last-child > tr > th.tableblock, table.grid-rows tbody > tr:last-child > th.tableblock, table.grid-rows tbody > tr:last-child > td.tableblock, table.grid-rows thead:last-child > tr > th.tableblock { border-bottom-width: 0; } -table.grid-rows tfoot > tr > th.tableblock, table.grid-rows tfoot > tr > td.tableblock { border-width: 1px 0 0 0; } -table.frame-all { border-width: 1px; } -table.frame-sides { border-width: 0 1px; } -table.frame-topbot { border-width: 1px 0; } -th.halign-left, td.halign-left { text-align: left; } -th.halign-right, td.halign-right { text-align: right; } -th.halign-center, td.halign-center { text-align: center; } -th.valign-top, td.valign-top { vertical-align: top; } -th.valign-bottom, td.valign-bottom { vertical-align: bottom; } -th.valign-middle, td.valign-middle { vertical-align: middle; } -table thead th, table tfoot th { font-weight: bold; } -tbody tr th { display: table-cell; line-height: 1.6; background: whitesmoke; } -tbody tr th, tbody tr th p, tfoot tr th, tfoot tr th p { color: #333333; font-weight: bold; } -td > div.verse { white-space: pre; } -ul.unstyled, ol.unnumbered, ul.checklist, ul.none { list-style-type: none; } -ul.unstyled, ol.unnumbered, ul.checklist { margin-left: 0.625em; } -ul.checklist li > p:first-child > .fa-check-square-o:first-child, ul.checklist li > p:first-child > input[type="checkbox"]:first-child { margin-right: 0.25em; } -ul.checklist li > p:first-child > input[type="checkbox"]:first-child { position: relative; top: 1px; } -ul.inline { margin: 0 auto 0.625em auto; margin-left: -1.375em; margin-right: 0; padding: 0; list-style: none; overflow: hidden; } -ul.inline > li { list-style: none; float: left; margin-left: 1.375em; display: block; } -ul.inline > li > * { display: block; } -.unstyled dl dt { font-weight: normal; font-style: normal; } -ol.arabic { list-style-type: decimal; } -ol.decimal { list-style-type: decimal-leading-zero; } -ol.loweralpha { list-style-type: lower-alpha; } -ol.upperalpha { list-style-type: upper-alpha; } -ol.lowerroman { list-style-type: lower-roman; } -ol.upperroman { list-style-type: upper-roman; } -ol.lowergreek { list-style-type: lower-greek; } -.hdlist > table, .colist > table { border: 0; background: none; } -.hdlist > table > tbody > tr, .colist > table > tbody > tr { background: none; } -td.hdlist1 { padding-right: .75em; font-weight: bold; } -td.hdlist1, td.hdlist2 { vertical-align: top; } -.literalblock + .colist, .listingblock + .colist { margin-top: -0.5em; } -.colist > table tr > td:first-of-type { padding: 0 .75em; line-height: 1; } -.colist > table tr > td:last-of-type { padding: 0.25em 0; } -.qanda > ol > li > p > em:only-child { color: #1d4b8f; } -.thumb, .th { line-height: 0; display: inline-block; border: solid 4px white; -webkit-box-shadow: 0 0 0 1px #dddddd; box-shadow: 0 0 0 1px #dddddd; } -.imageblock.left, .imageblock[style*="float: left"] { margin: 0.25em 0.625em 1.25em 0; } -.imageblock.right, .imageblock[style*="float: right"] { margin: 0.25em 0 1.25em 0.625em; } -.imageblock > .title { margin-bottom: 0; } -.imageblock.thumb, .imageblock.th { border-width: 6px; } -.imageblock.thumb > .title, .imageblock.th > .title { padding: 0 0.125em; } -.image.left, .image.right { margin-top: 0.25em; margin-bottom: 0.25em; display: inline-block; line-height: 0; } -.image.left { margin-right: 0.625em; } -.image.right { margin-left: 0.625em; } -a.image { text-decoration: none; } -span.footnote, span.footnoteref { vertical-align: super; font-size: 0.875em; } -span.footnote a, span.footnoteref a { text-decoration: none; } -span.footnote a:active, span.footnoteref a:active { text-decoration: underline; } -#footnotes { padding-top: 0.75em; padding-bottom: 0.75em; margin-bottom: 0.625em; } -#footnotes hr { width: 20%; min-width: 6.25em; margin: -.25em 0 .75em 0; border-width: 1px 0 0 0; } -#footnotes .footnote { padding: 0 0.375em; line-height: 1.3; font-size: 0.875em; margin-left: 1.2em; text-indent: -1.2em; margin-bottom: .2em; } -#footnotes .footnote a:first-of-type { font-weight: bold; text-decoration: none; } -#footnotes .footnote:last-of-type { margin-bottom: 0; } -#content #footnotes { margin-top: -0.625em; margin-bottom: 0; padding: 0.75em 0; } -.gist .file-data > table { border: none; background: #fff; width: 100%; margin-bottom: 0; } -.gist .file-data > table td.line-data { width: 99%; } -div.unbreakable { page-break-inside: avoid; } -.replaceable { font-style: italic; font-color: inherit; font-family: inherit; } -.parameter { font-style: italic; font-family: monospace; } -.userinput { font-weight: bold; font-family: monospace; } -.envar { font-weight: bold; font-family: monospace; font-size: 90%; } -.sysitem { font-weight: bold; font-size: 90%; } -.package { font-weight: bold; font-size: 90%; } -.filename { font-weight: bold; font-style: italic; font-size: 90%; } -.big { font-size: larger; } -.small { font-size: smaller; } -.underline { text-decoration: underline; } -.overline { text-decoration: overline; } -.line-through { text-decoration: line-through; } -.aqua { color: #00bfbf; } -.aqua-background { background-color: #00fafa; } -.black { color: black; } -.black-background { background-color: black; } -.blue { color: #0000bf; } -.blue-background { background-color: #0000fa; } -.fuchsia { color: #bf00bf; } -.fuchsia-background { background-color: #fa00fa; } -.gray { color: #606060; } -.gray-background { background-color: #7d7d7d; } -.green { color: #006000; } -.green-background { background-color: #007d00; } -.lime { color: #00bf00; } -.lime-background { background-color: #00fa00; } -.maroon { color: #600000; } -.maroon-background { background-color: #7d0000; } -.navy { color: #000060; } -.navy-background { background-color: #00007d; } -.olive { color: #606000; } -.olive-background { background-color: #7d7d00; } -.purple { color: #600060; } -.purple-background { background-color: #7d007d; } -.red { color: #bf0000; } -.red-background { background-color: #fa0000; } -.silver { color: #909090; } -.silver-background { background-color: #bcbcbc; } -.teal { color: #006060; } -.teal-background { background-color: #007d7d; } -.white { color: #bfbfbf; } -.white-background { background-color: #fafafa; } -.yellow { color: #bfbf00; } -.yellow-background { background-color: #fafa00; } -span.icon > .fa { cursor: default; } -.admonitionblock td.icon [class^="fa icon-"] { font-size: 2.5em; cursor: default; } -.admonitionblock td.icon .icon-note:before { content: "\f05a"; color: #4E9FDD; } -.admonitionblock td.icon .icon-tip:before { content: "\f0eb"; color: #2C8596; } -.admonitionblock td.icon .icon-warning:before { content: "\f071"; color: #ec7a08; } -.admonitionblock td.icon .icon-caution:before { content: "\f06d"; color: #ec7a08; } -.admonitionblock td.icon .icon-important:before { content: "\f06a"; color: #c00; } -.conum[data-value] { display: inline-block; color: white !important; background-color: #333333; -webkit-border-radius: 100px; border-radius: 100px; text-align: center; width: 20px; height: 20px; font-size: 12px; line-height: 20px; font-family: "Open Sans", "Sans", sans-serif; font-style: normal; font-weight: bold; text-indent: -1px; } -.conum[data-value] * { color: white !important; } -.conum[data-value] + b { display: none; } -.conum[data-value]:after { content: attr(data-value); } -pre .conum[data-value] { position: relative; top: -2px; } -b.conum * { color: inherit !important; } -.conum:not([data-value]):empty { display: none; } -.print-only { display: none !important; } -@media print { @page { margin: 1.25cm 0.75cm; } - * { -webkit-box-shadow: none !important; box-shadow: none !important; text-shadow: none !important; } - a, a:visited { color: inherit !important; text-decoration: underline !important; } - a[href^="http:"]:after, a[href^="https:"]:after { content: " (" attr(href) ")"; } - a[href^="#"], a[href^="#"]:visited, a[href^="mailto:"], a[href^="mailto:"]:visited { text-decoration: none !important; } - abbr[title]:after { content: " (" attr(title) ")"; } - pre, blockquote { page-break-inside: avoid; } - code { color: #191919; } - thead { display: table-header-group; } - tr, img { page-break-inside: avoid; } - img { max-width: 100% !important; } - p { orphans: 3; widows: 3; } - h2, h3, #toctitle, .sidebarblock > .content > .title, #toctitle, .sidebarblock > .content > .title { page-break-after: avoid; } - #toc, .sidebarblock { background: none !important; } - #toc { border-bottom: 1px solid #d8d8d8 !important; padding-bottom: 0 !important; } - .sect1 { padding-bottom: 0 !important; } - .sect1 + .sect1 { border: none !important; } - body.book #header { text-align: center; } - body.book #header > h1 { border: none !important; margin: 2.5em 0 1em 0; padding: 0; } - body.book #header span { line-height: 1.6; } - body.book #header br { display: block; } - body.book #header br + span { padding-left: 0; } - body.book #header br + span:before { content: none !important; } - body.book #toc { border: none !important; text-align: left !important; padding: 0 !important; } - #footer { background: none !important; } - #footer-text { color: #333333 !important; } - .hide-on-print { display: none !important; } - .print-only { display: block !important; } - .hide-for-print { display: none !important; } - .show-for-print { display: inherit !important; } } diff --git a/_templates/_css.html.erb b/_templates/_css.html.erb deleted file mode 100644 index 0fca7ae..0000000 --- a/_templates/_css.html.erb +++ /dev/null @@ -1,3 +0,0 @@ -<%- Dir.glob("_stylesheets/*").sort.each do |sheet| -%> - -<%- end -%> diff --git a/_templates/_nav.html.erb b/_templates/_nav.html.erb deleted file mode 100644 index 95a7e5c..0000000 --- a/_templates/_nav.html.erb +++ /dev/null @@ -1,31 +0,0 @@ - diff --git a/_templates/page.html.erb b/_templates/page.html.erb deleted file mode 100644 index ded5df7..0000000 --- a/_templates/page.html.erb +++ /dev/null @@ -1,184 +0,0 @@ - - - - - - - <%= distro %> <%= version %> | <%= [group_title, subgroup_title, topic_title].compact.join(' | ') %> - - - - - - - - - <%= render("_templates/_css.html.erb", :css_path => css_path) %> - - - - - - " rel="shortcut icon" type="text/css"> - - - - - -
-

- -

-
    -
  1. - <%= site_name %> -
    2. - - - <%= breadcrumb_subgroup_block %> - -
-
-
- <%= render("_templates/_nav.html.erb", :navigation => navigation, :group_id => group_id, :topic_id => topic_id, :subgroup_id => subgroup_id, :subtopic_shim => subtopic_shim) %> -
-
-
-

<%= article_title %>

-
- <%= content %> -
-
-
-
-
-
-
-
-

About

-
-
-
About Fedora
-
Sponsors
-
Fedora Magazine
-
Legal
-
-
    -
  • - -
    • -
  • - -
    • -
  • - -
    • -
-
-
- -
-

Download

-
-
-
Get Fedora Workstation
-
Get Fedora Server
-
Get Fedora Atomic
-
Fedora Spins
-
Fedora Labs
-
Fedora ARM®
-
Alternative Downloads
- -
-
-
- -
-

Support

-
-
-
Get Help
-
Ask Fedora
-
Common Bugs
-
Fedora Developer Portal
-
Installation Guide
-
-
-
- -
-

Join

-
-
-
Join Fedora
-
Planet Fedora
-
Fedora SIGs
-
Fedora Account System
-
Fedora Community
-
-
-
-
- -
-
-
- " alt="Red Hat Logo" /> -
-
-
-
- - -

© 2017 Red Hat, Inc. and others. Please send any comments or corrections to the websites team

-
-
-
- -
-
-
- - - - - - - - diff --git a/_topic_map.yml b/_topic_map.yml deleted file mode 100644 index 26414b4..0000000 --- a/_topic_map.yml +++ /dev/null @@ -1,97 +0,0 @@ -# This configuration file dictates the organization of the topic groups and -# topics on the main page of the doc site for this branch. Each record -# consists of the following: -# -# --- <= Record delimiter -# Name: Origin of the Species <= Display name of topic group -# Dir: origin_of_the_species <= Directory name of topic group -# Topics: -# - Name: The Majestic Marmoset <= Topic name -# File: the_majestic_marmoset <= Topic file under group dir +/- -# - Name: The Curious Crocodile <= Topic 2 name -# File: the_curious_crocodile <= Topic 2 file -# - Name: The Numerous Nematodes <= Sub-topic group name -# Dir: the_numerous_nematodes <= Sub-topic group dir -# Topics: -# - Name: The Wily Worm <= Sub-topic name -# File: the_wily_worm <= Sub-topic file under / -# - Name: The Acrobatic Ascarid <= Sub-topic 2 name -# File: the_acrobatic_ascarid <= Sub-topic 2 file under / -# -# The ordering of the records in this document determines the ordering of the -# topic groups and topics on the main page. ---- -Name: Project Overview -Dir: project -Topics: - - Name: index alias - File: index - Alias: project/fedora-overview - - Name: Mission and Foundations - File: fedora-overview - - Name: Leadership - File: leadership - - Name: Current Objectives - File: objectives - - Name: High-Level Organization - File: orgchart - - Name: Code of Conduct - File: code-of-conduct - - Name: Get Help - File: help - - Name: Get Involved - File: join ---- -Name: Fedora Council -Dir: council -Topics: - - Name: index alias - File: index - Alias: council/charter - - Name: Fedora Council Charter - File: charter - - Name: Contact the Fedora Council - File: contact - - Name: Current Council Members - File: members - - Name: Fedora Project Leader - File: fpl - - Name: Fedora Community Action and Impact Coordinator - File: fcaic - - Name: Fedora Program Manager - File: fpgm - - Name: Fedora Diversity Advisor - File: diversity-advisor - - Name: Council Policies - File: policies - - Name: Council and Board Historical Membership - File: history ---- -Name: Fedora Subprojects -Dir: subprojects -Topics: - - Name: index alias - File: index - Alias: subprojects/collaboration - - Name: Collaboration in Fedora - File: collaboration - - Name: Engineering - Dir: fesco - Topics: - - Name: About the Fedora Engineering Steering Committee - File: fesco -#INSERT:6:modularity:subprojects/fesco - - Name: Mindshare - Dir: mindshare - Topics: - - Name: About the Mindshare Committee - File: mindshare -#INSERT:6:commops:subprojects/mindshare - - Name: Diversity & Inclusion - File: diversity - - Name: Working Groups - File: workinggroups - - Name: Other Subprojects - File: subprojects - - Name: Special Interest Groups - File: sigs diff --git a/build.sh b/build.sh new file mode 100755 index 0000000..c9349e3 --- /dev/null +++ b/build.sh @@ -0,0 +1,16 @@ +#!/bin/sh + +if [ "$(uname)" == "Darwin" ]; then + # Running on macOS. + # Let's assume that the user has the Docker CE installed + # which doesn't require a root password. + docker run --rm -it -v $(pwd):/antora antora/antora --html-url-extension-style=indexify site.yml + +elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then + # Running on Linux. + # Let's assume that it's running the Docker deamon + # which requires root. + echo "" + echo "This build script is using Docker to run the build in an isolated environment. You might be asked for a root password in order to start it." +sudo docker run --rm -it -v $(pwd):/antora:z antora/antora --html-url-extension-style=indexify site.yml +fi diff --git a/council/antora.yml b/council/antora.yml new file mode 100644 index 0000000..97ec4f4 --- /dev/null +++ b/council/antora.yml @@ -0,0 +1,12 @@ +# Name will be mostly visible in the URL. Treat it as an indentifier. +# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) +name: council +# Title will be visible on the page. +title: Fedora Council +# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. +version: master +# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. +start_page: ROOT:index +# This lists all the menu definitions of your component. +nav: +- modules/ROOT/nav.adoc diff --git a/council/charter.adoc b/council/charter.adoc deleted file mode 100644 index 07cd132..0000000 --- a/council/charter.adoc +++ /dev/null @@ -1,334 +0,0 @@ -Fedora Council Charter -====================== - -image::council-logo-500px.png[float="right"] - -The Fedora Council is our top-level community leadership and governance -body. It is responsible for stewardship of the Fedora Project as a -whole, and supports the health and growth of the Fedora Community. - -The Council is composed of a mix of representatives from different areas -of the project, named roles appointed by Red Hat, and a variable number -of seats connected to medium-term project goals. Decisions are made by a -*consensus process*, in which we work together as a common team to find -shared solutions and address concerns, with a focus on giving voice -rather than on balance of power. - -The Council is ultimately accountable for the Fedora Project as a whole, -and is responsible for providing advice to and oversight of other Fedora -governance bodies and teams as needed. - -Responsibilities ----------------- - -The Council is responsible for issues of strategic importance for Fedora -that require leadership and coordination across the various teams and -subprojects to achieve. - -*Its primary role is to identify the short, medium, and long term goals -of the Fedora community and to organize and enable the project to best -achieve them.* This is done in consultation with the entire Fedora -community through transparent, public discussion. - -The Council *governs Fedora's financial resources*, working with our -sponsor(s) to establish an annual budget allocated to support Fedora -initiatives, including Fedora Ambassadors, Fedora-managed events, and -other activities which advance the project's goals. - -The Council also decides on issues regarding use of the Fedora -*trademarks*, is responsible for final *arbitration of complaints* -related to project policies and for *settling disputes* escalated from -other committees or subgroups, and may handle *sensitive legal or -personnel issues* which require research and discussion to protect the -interests of the Fedora Project or its sponsor(s). - - -Making Decisions ----------------- - -**** -Consensus decision-making aims to be: - -* *Agreement Seeking:* A consensus decision-making process attempts to help everyone get what they need. -* *Collaborative:* Participants contribute to a shared proposal and shape it into a decision that meets the concerns of all group members as much as possible. -* *Cooperative:* Participants in an effective consensus process should strive to reach the best possible decision for the group and all of its members, rather than competing for personal preferences. -* *Egalitarian:* All members of a consensus decision-making body should be afforded, as much as possible, equal input into the process. All members have the opportunity to present, and amend proposals. -* *Inclusive:* As many stakeholders as possible should be involved in the consensus decision-making process. -* *Participatory:* The consensus process should actively solicit the input and participation of all decision-makers - -— from https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[Wikipedia on Consensus decision-making] - -**** - -Many basic decisions are made through a process known as “*lazy -approval*”, in which general consent is assumed unless valid objections -are raised within a period of time — generally three to seven days, -although the timeframe should be stated each time and should be -proportionate to the impact of the action. This process is used for -decisions with short-term consequences and which can be easily reversed. -Any project member can ask for the deadline to be extended or the -decision escalated to require full consensus. - -More significant decisions are made through a process of *full -consensus*. In order to pass, these decisions need three positive votes -(+3) and _no_ negative votes (-1). A negative vote immediately halts the -process and requires discussion. Therefore, in order to remain valid, -negative votes must be supported with a specific concerns about the -proposal, and suggestions for what could be changed in order to make the -proposal acceptable. A vote of “0” is sometimes used to indicate a -disagreement but willingness to stand aside; this should also be -accompanied with an explanation. - -This model matches Fedora's “Friends” foundation, which calls for -finding acceptable consensus to serve the interests of advancing free -software. It works because we work together in a community of mutual -respect even when we disagree. - -In general, the Council conducts business in public discussion, and any -Fedora project member can make negative or positive votes. It is the -duty of the Council to take concerns raised in this way into serious -consideration, but only Council members' votes are binding in the final -tally. - -When consensus can't be reached, the Council may ask the Fedora Project -Leader to decide on a resolution. Such a request can be made when issues -leading to negative votes are outstanding and all Council members agree -that the Council is deadlocked, or if the dispute is unresolved after -fourteen days and a simple majority of Council members are in favor of -the request. - - -Composition ------------ - - -Objective Leads -~~~~~~~~~~~~~~~ - -On an ongoing basis, including sessions at Flock and in public online -meetings, the Council will identify two to four key community objectives -with a timeframe of approximately eighteen months, and appoint -*Objective Leads* for each goal. These will serve as auxiliary Council -members, with binding votes only over concerns relevant to their -particular area. - -Each objective will be documented with measurable goals, and the -objective lead is responsible for coordinating efforts to reach those -goals, evaluating and reporting on progress, and working regularly with -all relevant groups in Fedora to ensure that progress is made. - - -Representatives -~~~~~~~~~~~~~~~ - -The Council also includes four representative seats, an *Engineering -Representative*, an *Mindshare Representative*, and two *Elected -Representatives*. - -“Engineering” and “Mindshare” are broad areas roughly encompassing two -of the major areas of activity in Fedora. _Engineering_ is the technical -work related to building and releasing the Fedora operating system and -the infrastructure related to that. _Mindshare_ includes marketing, -design, and Fedora Ambassadors — largely activities that happen between -Fedora and the world at large, with the distribution release cycle -serving as a fuel source, not the thing that's being worked on. - -The engineering and mindshare representatives' responsibility is to -represent their areas collectively, _not_ to be just an individual voice -that happens to be voted-in by some subset of Fedora. They are selected -by the people active in those areas, coordinated by the Fedora -Engineering Steering Committee (FESCo) and a to-be-created mindshare -group respectively, and serve for terms to be determined by those -committees. - -The elected positions cover all Fedora subprojects that are not under the -engineering or mindshare banners, and the community at large. One -specific responsibility is to represent the voice of individual -contributors to the Fedora project. Each representative will also work -on specific goals which she or he brings to the Council as highlighted -during the election process. - -Elections are held twice a year, in concert with the joint Fedora -election cycle. One seat is selected at each election, and each position -has a two-election (approximately one year) term. No person who -currently holds another Council seat can be elected. If a seat becomes -vacant, the Council will arrange for a temporary replacement. - - -Appointed Leadership Positions -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -*Fedora Project Leader* - -The link:fpl.html[Fedora Project Leader] serves as the -chair of the Council, organizing discussion agendas, bringing issues to -the table, and facilitating the consensus process. He or she is -accountable for success in all areas of the project, but is not a -dictator, benevolent or otherwise. The FPL often serves as the public -face and collective voice of the project, and has a corresponding duty -to listen to, understand, and fairly represent the collective views and -needs of project contributors and stakeholders. - -The Fedora Project Leader is hired by Red Hat with the advice and -consent of the Council. - -*Fedora Community Action and Impact Coordinator* - -The link:fcaic.html[Fedora Community Action and Impact -Coordinator (FCAIC)] initiatives to grow the Fedora user and developer -communities, and to make Red Hat / Fedora interactions even more -transparent and positive. The Fedora community budget comes to us -through OSAS, and this position facilitates decision-making on how to -best focus that to meet our collective objectives. - - -Auxiliary Seats -~~~~~~~~~~~~~~~ - -As with the objective leads, the next two appointed positions are -auxiliary seats. They are intended to have significant positive impact -on the project as a whole, but in order to minimize the overall -influence of appointed positions vs. those selected by the community, -their votes in the consensus process are expected to be related to the -scope of the respective role. - -*Diversity Team Representative* - -The Fedora https://fedoraproject.org/wiki/Diversity[Diversity Team] -works on initiatives to assess and promote equality and inclusion -within the Fedora contributor and user communities, and helps develop -project strategy on diversity issues. The Diversity Team Representative -connects the team's efforts to the Council. - -This position is appointed by members of the Fedora Diversity Team, -with the approval of the Council. - -*Fedora Program Manager* - -The https://fedoraproject.org/wiki/Fedora_Program_Management#Fedora_Program_Manager[FPgM] coordinates the planning and -scheduling of Fedora releases, and tracks changes and features during -the development and testing cycle. He or she also assists with the -creation, maintenance, and execution of formal, repeatable Fedora -processes. Additionally, the FPgM serves as record keeper and secretary -for Fedora Council Meetings. - -This position is funded by and hired for by Red Hat, with the approval -of the Council. - - -Coda ----- - - -Meetings -~~~~~~~~ - -The Fedora Council is not driven by meetings or by tickets, but does -hold https://fedoraproject.org/wiki/Council_Meetings[regular public IRC meetings] to -discuss current issues, to clear through anything outstanding which can -be quickly resolved, and to ensure that nothing important is left in -limbo. All members are be expected to regularly communicate what's going -on in their area, through blog posts or other public updates. - -Additionally, the Fedora Project Leader will set aside regular times on -IRC to meet with the community. Attendance is not mandatory for all -members but is encouraged. - - -Transparency -~~~~~~~~~~~~ - -The general policy of the Fedora Council is to default to open. Meetings -are held in public IRC channels, and open to all Fedora users and -contributors. Discussion is held in on a -https://lists.fedoraproject.org/mailman/listinfo/council-discuss[public -mailing list] open to all subscribers, and formal decisions will be -recorded in a public ticket tracking system. - -Occasionally, when personal, private, or sensitive issues need to be -discussed, a phone call might be used. A private mailing list and ticket -tracking instance also exist for these situations, but will also only be -used when dealing with these uncommon issues. - - -Time Commitment -~~~~~~~~~~~~~~~ - -Serving on the Fedora Council is a significant commitment of time and -energy. Workload for the various roles will vary, but each will require -a number of hours every week, and in most cases, the more, the better a -Council member is able to do the job fully. - -We recognize that most Fedora community members do not have the luxury -of working on Fedora full-time or as part of a paid position. The time -commitment required for these roles comes simply from what is required -to lead a large project like Fedora, and is not intended to be an -artificial limit on who can participate. We know that that it can be a -_pragmatic_ limit, and for that reason, the Council is responsible for -extra effort to receive, recognize, be responsive to, and meaningfully -reward the input of contributors offering their individual time. - - -Governance Philosophy -~~~~~~~~~~~~~~~~~~~~~ - -To advance free software, we need to provide a sustainable integration -of free software without cutting corners. By providing a positive first -impression before and during installation and real use, we support -Fedora's reputation as a leading and reliable product that attracts -future users and contributors. To provide that integration and -experience we must have a clear set of priorities to help all -contributors decide how to allocate resources and resolve conflicts. -These priorities are not meant to be exclusive, or to keep contributors -from working on the parts of Fedora that matter to them. - -These priorities will sometimes expose gaps where contributors need -additional assistance, and allow them to seek it both within the -community and by bringing in additional contributors to help, -exclusively on their particular interest area if desired. While -narrowing our focus in some areas, though, we must provide opportunities -for exploration to all contributors within the framework of our core -values and without impeding progress. - - -Historical Note -~~~~~~~~~~~~~~~ - -The previous https://fedoraproject.org/wiki/Board[previous governance structure (Fedora Board)] -had five members directly appointed by Red Hat and five elected at -large. The current structure is more complicated but has a much greater -proportion of members selected by the community by election or merit. In -the previous board structure, the Fedora Project leader had a special -veto power; in the current model, all voting members can block on -issues, with a valid reason. The FPL does not have a special veto, but -does have a limited power to “unstick” things if consensus genuinely -can't be reached and a decision needs to be made. - - -Record of Former Members -~~~~~~~~~~~~~~~~~~~~~~~~ - -Former membership on the Fedora Council, along with membership on the -previous Fedora Board, is documented on the link:history.html[History of -Council Membership] page. - - -Document History -~~~~~~~~~~~~~~~~ - -This charter was approved by the Fedora Project Board on -https://fedorahosted.org/council/ticket/13[Oct. 9th, 2014] and is in effect -as of Nov. 26th, 2014. Any other significant changes will be noted here; -smaller changes (minor wording or formating, etc., without impact on -meaning) can be found in the -https://pagure.io/Fedora-Council/council-docs/commits/master[git repository] -for Council documents. - -2017-11-15: Update Diversity Advisor to Diversity Team Representative - -2017-10-20: Move current membership list and contact info to separate docs. - -2017-04-05: Switched “Outreach” to Mindshare. (https://pagure.io/Fedora-Council/tickets/issue/102[ticket]) - -2014-11-26: Initital approval by the Fedora Project Board (https://pagure.io/Fedora-Council/tickets/issue/13[ticket]) - diff --git a/council/contact.adoc b/council/contact.adoc deleted file mode 100644 index ea108f5..0000000 --- a/council/contact.adoc +++ /dev/null @@ -1,28 +0,0 @@ -Contacting the Fedora Council -============================= - -The Fedora Council uses two mailing lists. - -https://lists.fedoraproject.org/admin/lists/council-discuss@lists.fedoraproject.org/[*council-discuss*] (formerly "board-discuss") is a public list. Subscription is open to -anyone, as are the archives. This list is the main discussion point for -the Fedora Council, and the goal of the list is to either reach a -decision, or to delegate the thread to a more appropriate location. For -example, engineering-specific threads may get some comments on -council-discuss, before being redirected to the devel list for in-depth -discussion. - -https://lists.fedoraproject.org/admin/lists/council-private@lists.fedoraproject.org/[*council-private*] is a private list. Its membership is restricted to the current -Council members, and its archives are private. This list is only used -for topics that cannot be discussed on the public council-discuss list. - -Council members are also often present on the *#fedora-council* IRC -channel on *irc.freenode.net* - -If you have an issue to be worked on by the Council you can also open a -ticket on the https://pagure.io/Fedora-Council/tickets[Council Pagure -instance]. This is a public issue tracker. However, if you have a -particularly privacy- or security-sensitive issue, you can check the -*Private* box when you create the ticket. If an issue is not sensitive -the discussion should be in the open, in the public Pagure instance or -the council-discuss list. - diff --git a/council/diversity-advisor.adoc b/council/diversity-advisor.adoc deleted file mode 100644 index 881d190..0000000 --- a/council/diversity-advisor.adoc +++ /dev/null @@ -1,63 +0,0 @@ -= Fedora Diversity Advisor = -The *Fedora Diversity Advisor* acts as a source of support and -information for all contributors and users, especially those from -underrepresented populations, so that issues of inclusion and equity can -be discussed and addressed with the planning of multiculturalism and -comfort. The Fedora Diversity Advisor will lead initiatives to assess -and promote equality and inclusion within the Fedora contributor and -user communities, and will develop project strategy on diversity issues. -The Diversity Advisor will also be the point of contact for Fedora’s -participation in third-party outreach programs and events. - -== Current Diversiity Advisor - -image::https://fedoraproject.org/w/uploads/7/7c/My.jpg[float="right",50%] -link:https://fedoraproject.org/wiki/User:Amsharma[Amita Sharma] has been involved with the Fedora project since 2011. -She started her contributions with work in Fedora QA. -She is also a founding member of the Fedora Diversity Team. -After contributing to the Diversity Team for around 2 years, Amita got the opportunity to represent the team as the Diversity Representative on the Fedora Council. -Amita works as a full time Senior Quality Assurance Engineer on Red Hat Directory Server at Red Hat in Pune, India. - -*Information about the Fedora Diversity Team is available at link:https://fedoraproject.org/wiki/Diversity[the team's wiki page]* - -[[responsibilities]] -== Responsibilities - -* Implement diversity efforts that will have a big effect on the Fedora community -* Promote inclusion in the Fedora community -* Act as a source of support and a mediator should there be any concerns or incidents -* Increase visibility of minority contributors and users through talks, feature articles, and awards -* Make explicit invitations and providing financial support to attend conferences and give talks -* Help develop skills by offering targeted workshops and internships -* Create a welcoming environment by adopting and enforcing codes of conduct -* Fostering communication, networking, and support forums with mailing lists and in-person events - -[[contact]] -== Contact - -Contact Amita Sharma online by pinging *Amita* on -#fedora-diversity on FreeNode IRC. The Diversity Advisor also joins -the link:https://fedoraproject.org/wiki/Diversity[Fedora Diversity -team meetings]. - -[[selection]] -== Selection - -The Diversity Advisor is selected by the -link:https://fedoraproject.org/wiki/Diversity[Fedora Diversity team] -and approved by the Fedora Council. Currently the Diversity Team has -decided to rotate the position with every release of Fedora. - -== History of Fedora Community Action and Impact Coordinators - -|=== -|Releases | Diversity Advisor - -|27, … -|https://fedoraproject.org/wiki/User:Amsharma[Amita Sharma] - -|23, 24, 26, 26 -|https://fedoraproject.org/wiki/User:Tatica[Maria "tatica" Leandro] - -|=== - diff --git a/council/fcaic.adoc b/council/fcaic.adoc deleted file mode 100644 index 27e9af3..0000000 --- a/council/fcaic.adoc +++ /dev/null @@ -1,82 +0,0 @@ -Fedora Community Action and Impact Coordinator -============================================== - -The _Fedora Community Action and Impact Coordinator_ (or _FCAIC_) is a full-time, Red Hat-employed job to lead initiatives to grow the Fedora user and developer communities, and to make Red Hat / Fedora interactions even more transparent and positive. -The Fedora community budget comes to us through the Red Hat Open Source and Standards (OSAS) team. -This position facilitates decision-making on how to best focus that to meet our community's goals and objectives. -The FCAIC supports the link:fpl.html[Project Leader] with all things "Community" and works directly with the Fedora Leadership to help bring more Heat and Light to the project. - -The FCAIC is appointed to the Community Action and Impact seat on the Fedora link:charter.html[Council], Fedora’s top-level community leadership and governance body. -The Council is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora Community. - -== Current F-🎂footnote:[What's with the cake? The abbreviation FCAIC sounds like "F-Cake" in American English. If this position is going to have a title that is a mouthful, at least the mouthful can be yummy cake!] - -image::bex-ocean-thumb.jpg[float="right",50%] -https://fedoraproject.org/wiki/User:bex[Brian (bex) Exelbierd] joined Red Hat in 2013 and became the Fedora Community Action and Impact Coordinator in October 2016. -At Red Hat, Brian has worked as a technical writer, software engineer, content strategist and is now an Open Source community manager in the Open Source and Standards team at Red Hat. -Before Red Hat, Brian worked with the University of Delaware as the Director of Graduate and Executive Programs in the Alfred Lerner College of Business and Economics and as a Budget Analyst. -Brian’s background in software engineering stretches back years before his university work and includes stints at small, medium, large and governmental organizations. -“Glue Code” is how many of Brian’s projects could be described. -These are projects that fill in the interstitial spaces between large systems and provide continuity and ease of use. -Follow him on Twitter https://twitter.com/bexelbie[@bexelbie] or on his http://www.winglemeyer.org[blog]. - -== Roles and Responsibilities == - -=== Council === - -* Work with other Council members to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them -* Primary Council member with responsibility for the development of the annual Fedora community budget -* Participate in decision-making about use of trademarks, project structure, community disputes or complaints, and other such issues - -=== Special Initiatives === - -* Design and spearhead special initiatives to grow user and contributor bases - -=== Metrics === - -* Implement metrics for community engagement, participation, and satisfaction; create and execute projects to improve those metrics; report regularly on progress and adjust approach as needed - -=== Opportunities === - -* Identify opportunities to engage new contributors and community members; align project around supporting those opportunities - -=== Liaise between Red Hat and FOSS Community === - -* Communicate community needs to Red Hat and participate in regular meetings with internal Red Hat stakeholders; align Red Hat participation in Fedora beyond platform engineering -* Represent Red Hat’s stake in Fedora community success -* Improve on-boarding materials and presentation of Fedora to new Red Hat hires; develop standardized materials on Fedora which can be used at Red Hat globally. - -=== Budget === - -The FCAIC will work with Fedora Council and OSAS to determine annual Fedora Budget - -* Ensure that budget is published and tracked transparently, with a public page indicating how each year’s budget is earmarked and its current state. -* The budget is published at https://budget.fedoraproject.org - -=== Fedora Event Planning and Participation === - -Participate in planning and organizing Fedora’s Flagship events each year, including: - -* Flock -* FUDCons -* Fedora Activity Days (FADs) - -The FCAIC also represents Fedora at other major industry conferences and hackathons such as: - -* AllThingsOpen -* DevConf -* FOSDEM -* PyCon (and Sprints) -* LibrePlanet -* Red Hat Summit -* Software Freedom Legal Conference - -=== Communications === - -The FCAIC provides and facilitates regular communications to Fedora Magazine, the Fedora Community Blog, and other mass communication channels to talk about community goals/progress and general community boosting. - -== Previous Fedora Community Action and Impact Coordinators - -https://fedoraproject.org/wiki/User:Decause[Remy DeCausemaker ]:: - February 2015 – June 2016 - diff --git a/council/fpgm.adoc b/council/fpgm.adoc deleted file mode 100644 index 8fe93b4..0000000 --- a/council/fpgm.adoc +++ /dev/null @@ -1,49 +0,0 @@ -Fedora Program Manager -====================== - -The _Fedora Program Manager_ (or _FPgM_) is responsible for managing the planning and release processes for Fedora. This includes schedule management, change wrangling, and providing status reports to the community and to Red Hat. - -image::bcotton-rh_neo.jpeg[float="right",50%] -https://fedoraproject.org/wiki/User:Bcotton[Ben Cotton] is the current FPgM. He joined Red Hat after a decade in high performance computing (HPC) administration and marketing. Ben first started contributing to Fedora in 2009 as a member — and later leader — of the Fedora Docs team. He is a community moderator for Opensource.com and co-founded HackLafayette — a local tech meetup group. - -Contact Ben on Freenode IRC (`bcotton`) or by email (`bcotton@fedoraproject.org`). - -== Roles and Responsibilities == - -Within the Fedora Project, the Program Manager (FPGM) is primarily responsible for: - -* planning and http://fedorapeople.org/groups/schedule/[scheduling] of Fedora releases -* tracking the changes/features during the development/testing cycle -* release coordination (within QA, releng, FESCo, etc.) -* processes behind Fedora Project -* member of Fedora Council - Auxiliary Seat, Council secretary - -=== Program management SOPs === -This SOP (Standard Operating Procedure) section contains a list of common FPGMs tasks. - -* https://fedoraproject.org/wiki/Fedora_Program_Management/GoNoGoSOP[The Go/No-Go meeting] -* https://fedoraproject.org/wiki/Fedora_Program_Management/ReadinessSOP[The Readiness meeting] -* https://fedoraproject.org/wiki/Fedora_Program_Management/ChangesSOP[Change Process] -* https://fedoraproject.org/wiki/Fedora_Program_Management/EOLRebaseSOP[End Of Life and Rawhide Rebase] - -=== Release Planning === -https://fedoraproject.org/wiki/Releases[Track of releases] - -=== House Keeping === -Previously, house keeping was done in BugZappers wiki but as BugZappers group is dismissed for several years, it was moved to FPgM wiki. - -https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping[House keeping] - -== History == - -Previous Fedora Program Managers: - -* https://fedoraproject.org/wiki/User:Jkurik[Jan Kuřík] (Fedora 23-28) -* https://fedoraproject.org/wiki/User:Jreznik[Jaroslav Řezník] (Fedora 20-23) -* https://fedoraproject.org/wiki/User:Rbergero[Robyn Bergeron] (Fedora 17-20) -* https://fedoraproject.org/wiki/User:Poelstra[John Poelstra] (Fedora 8-16) - -== Useful links == -* http://fedorapeople.org/groups/schedule[Schedules] in HTML/ICS formats with sources -* https://pagure.io/fedora-project-schedule[Fedora Project Schedule repository] to report scheduling issues, and GIT with scripts making FPGM happier -* https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Release Life Cycle] aka how to schedule next Fedora release diff --git a/council/fpl.adoc b/council/fpl.adoc deleted file mode 100644 index 22683da..0000000 --- a/council/fpl.adoc +++ /dev/null @@ -1,44 +0,0 @@ -= The Fedora Project Leader - -The _Fedora Project Leader_ (or _FPL_) is ultimately accountable for everything that happens within Fedora and in particular is responsible for maintaining Red Hat's relationship with Fedora and vice versa. -He/She is Fedora's President, CEO, Chair, Fearless Leader, whatever-you-want-to-call-it. -However the project leader is not a dictator, benevolent or otherwise. -The FPL chairs the Fedora link:charter.html[Council]. - -image::mattdm-2014-fedora10y-thumb.jpg[float="right",50%,link="https://fedoraproject.org/w/uploads/e/e8/Mattdm-2014-fedora10y-small.jpg"] -https://fedoraproject.org/wiki/User:mattdm[Matthew Miller] is the current Fedora Project Leader. -He led the Fedora.next initiative for a strategic approach to Fedora's second decade, -as well as the transition from the Fedora Board to the current Council governance model. -Matthew created the BU Linux distribution for Boston University in 1999 and maintained that through 2008, -when he moved to the Harvard School of Engineering and Applied Sciences to work on high performance computing and this up-and-coming “cloud” thing. -He has been at Red Hat since 2012, first working on Fedora Cloud and becoming FPL in June, 2014. - -Contact Matthew as `mattdm` on Freenode IRC, -as https://twitter.com/mattdm[@mattdm] on Twitter, or -on the -https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[Council-Discuss] -mailing list. - -== Previous Fedora Project Leaders - -https://fedoraproject.org/wiki/User:Rbergero[Robyn Bergeron]:: - February 2012 – June 2014 (Fedora 17 – 21) - -https://fedoraproject.org/wiki/User:Jsmith[Jared Smith]:: - July 2010 – February 2012 (Fedora 14 – 16) - -https://fedoraproject.org/wiki/User:Pfrields[Paul W. Frields]:: - February 2008 – July 2010 (Fedora 9 – 14) - -https://fedoraproject.org/wiki/User:Mspevack[Max Spevack]:: - February 2006 – February 2008 (Fedora Core 5 – Fedora 9) - -https://fedoraproject.org/wiki/User:Gdk[Greg DeKoenigsberg]:: - August 2005 – February 2006 (Fedora Core 4 & 5) - -Cristian Gafton:: - January 2004 – August 2005 (Fedora Core 2, 3, & 4) - -Michael Johnson:: - July 2003 – January 2004 (Fedora Core 1) - diff --git a/council/history.adoc b/council/history.adoc deleted file mode 100644 index 7e452cf..0000000 --- a/council/history.adoc +++ /dev/null @@ -1,124 +0,0 @@ -Fedora Council and Board Historical Membership -============================================== - -History of Fedora Council Membership ------------------------------------- -Previous members of the Fedora Council are listed here. - -Elected Representatives -~~~~~~~~~~~~~~~~~~~~~~~ - -|=== -|Nick Bebout | January 2018 – May 2018 (f28) -|Robert Mayr | December 2015 – January 2018 (f24-f25, f26-f27) -|Justin Flory | August 2017 – January 2018 (f27) -|Rex Dieter | November 2014 – December 2015 (f22-f23) -|Langdon White | November 2014 – August 2016 (f22, f23-f24, f25-f26) -|=== - -_Historical note: The initial elected representatives were selected in a -single election, with the candidate with the most votes selected for a full -term (through the release of F23) and the runner-up for a half term (through -the release of F22)._ - -Project Objective Leads -~~~~~~~~~~~~~~~~~~~~~~~ - -|=== -|Stephen Gallagher | _Three Editions (Fedora.next)_ | January 2015 – November 2015 -|Stef Walter | _CI/CD of Fedora Atomic Host_ | August 2017 – December 2017 -|=== - -Mindshare Representative -~~~~~~~~~~~~~~~~~~~~~~~~ - -|=== -|Christoph Wickert (Outreach Representative) | January 2015 – December 2016 -|=== - - -Diversity Advisor -~~~~~~~~~~~~~~~~~ - -|=== -|María Leandro | March 2016 — March 2017 -|=== - -Fedora Program Manager -~~~~~~~~~~~~~~~~~~~~~~ - -|=== -|Jan Kuřík | June 2015 — February 2018 -|Jaroslav Reznik | September 2014 – May 2015 -|=== - -Fedora Community Action and Impact Coordinator -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -|=== -|Remy DeCausemaker | February 2015 – June 2016 -|=== - - -''' -<<< - - - -History of Fedora Board Membership ----------------------------------- - -The Fedora Board was the Project's top-level governance body from July 2007 -to November 2014. Before that, the "Fedora Advisory Board" was merely (as -the name suggests) advisory and had no formal membership. - -|=== -|Elliot Lee | Apr 2006 - Nov 2006 -|Jeremy Katz | Apr 2006 - Jul 2007 -|Rahul Sundaram | Apr 2006 - Jul 2007 -|Paul Frields | Apr 2006 - Jul 2007, Feb 2008 - Jul 2010 -|Rex Dieter | Apr 2006 - Jul 2007, Jun 2010 - Jun 2012, Dec 2012 - Oct 2014 -|Chris Blizzard | Apr 2006 - Dec 2007 -|Max Spevack | Apr 2006 - Feb 2008 -|Bill Nottingham | Apr 2006 - Dec 2008, Dec 2008 - Dec 2009 -|Seth Vidal | Apr 2006 - Jul 2009 -|Matt Domsch | Apr 2006 - Nov 2010 -|Greg DeKoenigsberg | Nov 2006 - Jul 2007 -|Steve Dickson | Jul 2007 - Jun 2008 -|Christopher Aillon | Jul 2007 - Jun 2008, Dec 2008 - Dec 2010 -|Dennis Gilmore | Jul 2007 - Jun 2008, Jun 2009 - Jun 2010 -|Jef Spaleta | Jul 2007 - Dec 2008 -|Karsten Wade | Jul 2007 - Dec 2008 -|Bob McWhirter | Dec 2007 - Jun 2008 -|Dimitris Glezos | Dec 2008 - Dec 2009 -|Harald Hoyer | Jul 2008 - Jun 2009 -|Jesse Keating | Jul 2008 - Jun 2009 -|Chris Tyler | Jul 2008 - Jun 2009, Dec 2009 - Nov 2010 -|Tom Callaway | Jul 2008 - Jun 2011 -|John Poelstra | Jun 2009 - Jun 2010 -|Mike McGrath | Jun 2009 - Jun 2010 -|Josh Boyer | Jun 2009 - Jun 2010, Jun 2013 - Oct 2014 -|Colin Walters | Dec 2009 - Nov 2010 -|Mairin Duffy | Jun 2010 - Jun 2011 -|Stephen Smoogen | Jun 2010 - Jun 2011 -|Jon Stanley | Jun 2010 - Jun 2012 -|Jared Smith | Jul 2010 - Feb 2012 -|Joerg Simon | Nov 2010 - Dec 2011 -|Jaroslav Reznik | Nov 2010 - Jan 2014 -|David Nalley | Dec 2010 - Dec 2012 -|Toshio Kuratomi | Nov 2010 - Nov 2012 -|Rudi Landmann | Jun 2011 - May 2012 -|Guillermo Gomez | Jun 2011 - Jun 2012 -|Peter Robinson | Jun 2011 - Jun 2013 -|Christoph Wickert | Dec 2011 - Dec 2012 -|Robyn Bergeron | Feb 2012 - Jun 2014 -|Garrett Holmstrom | May 2012 - Oct 2014 -|Nick Bebout | Jun 2012 - Jun 2013 -|Eric Christensen | Jun 2012 - Oct 2014 -|John Rose | Jun 2012 - Oct 2014 -|Major Hayden | Nov 2012 - Oct 2014 -|Michael Scherer | Dec 2012 - Jan 2014 -|Matthew Garrett | Jun 2013 - Oct 2014 -|Haïkel Guémar | Jan 2014 - Oct 2014 -|Neville Cross | Jan 2014 - Oct 2014 -|=== diff --git a/council/images/bcotton-rh_neo.jpeg b/council/images/bcotton-rh_neo.jpeg deleted file mode 100644 index aa76e18..0000000 Binary files a/council/images/bcotton-rh_neo.jpeg and /dev/null differ diff --git a/council/images/bex-ocean-thumb.jpg b/council/images/bex-ocean-thumb.jpg deleted file mode 100644 index 8ee5764..0000000 Binary files a/council/images/bex-ocean-thumb.jpg and /dev/null differ diff --git a/council/images/council-badge.png b/council/images/council-badge.png deleted file mode 100644 index 5e0399d..0000000 Binary files a/council/images/council-badge.png and /dev/null differ diff --git a/council/images/council-logo-500px.png b/council/images/council-logo-500px.png deleted file mode 100644 index 5f74569..0000000 Binary files a/council/images/council-logo-500px.png and /dev/null differ diff --git a/council/images/mattdm-2014-fedora10y-thumb.jpg b/council/images/mattdm-2014-fedora10y-thumb.jpg deleted file mode 100644 index 9756885..0000000 Binary files a/council/images/mattdm-2014-fedora10y-thumb.jpg and /dev/null differ diff --git a/council/members.adoc b/council/members.adoc deleted file mode 100644 index fef6125..0000000 --- a/council/members.adoc +++ /dev/null @@ -1,48 +0,0 @@ -Current Members of the Fedora Council -===================================== - -image::council-badge.png[float="right"] - -* Elected Representative: *https://fedoraproject.org/wiki/User:Ausil[Dennis Gilmore]* _(f28-f29)_ -+ -Dennis has been involved in Fedora since the begining. Holding various roles. -From leading up Alternative Architectures, to leading Release Engineering, -contributing to Infrastructure, helping found EPEL, Serving on the Board and -Fedora Engineering Steering Committee. He works at Red Hat in the Platform -Enablement organisation working on multi-arch. - -* Elected Representative: *Till Maas* _(f29-f30)_ - -* Engineering Representative: *Josh Boyer* -+ -Josh has been involved with Fedora for over 10 years. He started as nothing -more than a user, then a mailing list contributor, and has continued to -participate in a number of different SIGs, committees, and roles. Josh -is currently on the Fedora Engineering Steering Committee in addition to his -Council role. He works at Red Hat in the Platform Engineering organization. -+ -You can find him on Freenode irc as `jwb`. - -* Mindshare Representative: *Robert Mayr* - -* Diversity Team Representative: *Amita Sharma* - -+ -Read more about the link:diversity-advisor.html[Fedora Diversity Advisor's role] and current Fedora Diversity Advisor's link:diversity-advisor.html[biography] on the page about this position. - -* Fedora Project Leader: *Matthew Miller* -+ -Read more about the link:fpl.html[Fedora Project Leader's role] and the current FPL's link:fpl.html[biography] on the page about this position. - -* Fedora Community Action and Impact Coordinator: *Brian Exelbierd* -+ -Read more about the link:fcaic.html[Fedora Community Action and Impact Coordinator's role] and the current FCAIC's link:fcaic.html[biography] on the page about this position. - -* Fedora Program Manager: *Ben Cotton* -+ -Read more about the link:fpgm.html[Fedora Program Manager's role] and the current FPgM's link:fpgm.html[biography] on the page about this position. - -* Objective Leads: - *Langdon White* (Fedora Modularity), - *Dominik Perpeet* (Atomic CI/CD), - *Peter Robinson* (Internet of Things) diff --git a/council/modules/ROOT/assets/images/bcotton-rh_neo.jpeg b/council/modules/ROOT/assets/images/bcotton-rh_neo.jpeg new file mode 100644 index 0000000..aa76e18 Binary files /dev/null and b/council/modules/ROOT/assets/images/bcotton-rh_neo.jpeg differ diff --git a/council/modules/ROOT/assets/images/bex-ocean-thumb.jpg b/council/modules/ROOT/assets/images/bex-ocean-thumb.jpg new file mode 100644 index 0000000..8ee5764 Binary files /dev/null and b/council/modules/ROOT/assets/images/bex-ocean-thumb.jpg differ diff --git a/council/modules/ROOT/assets/images/council-badge.png b/council/modules/ROOT/assets/images/council-badge.png new file mode 100644 index 0000000..5e0399d Binary files /dev/null and b/council/modules/ROOT/assets/images/council-badge.png differ diff --git a/council/modules/ROOT/assets/images/council-logo-500px.png b/council/modules/ROOT/assets/images/council-logo-500px.png new file mode 100644 index 0000000..5f74569 Binary files /dev/null and b/council/modules/ROOT/assets/images/council-logo-500px.png differ diff --git a/council/modules/ROOT/assets/images/mattdm-2014-fedora10y-thumb.jpg b/council/modules/ROOT/assets/images/mattdm-2014-fedora10y-thumb.jpg new file mode 100644 index 0000000..9756885 Binary files /dev/null and b/council/modules/ROOT/assets/images/mattdm-2014-fedora10y-thumb.jpg differ diff --git a/council/modules/ROOT/nav.adoc b/council/modules/ROOT/nav.adoc new file mode 100644 index 0000000..16ccc1a --- /dev/null +++ b/council/modules/ROOT/nav.adoc @@ -0,0 +1,8 @@ +* xref:contact.adoc[Contact the Fedora Council] +* xref:members.adoc[Current Council Members] +** xref:fpl.adoc[Fedora Project Leader] +** xref:fcaic.adoc[Fedora Community Action and Impact Coordinator] +** xref:fpgm.adoc[Fedora Program Manager] +** xref:diversity-advisor.adoc[Fedora Diversity Advisor] +* xref:policies.adoc[Council Policies] +* xref:history.adoc[Council and Board Historical Membership] diff --git a/council/modules/ROOT/pages/contact.adoc b/council/modules/ROOT/pages/contact.adoc new file mode 100644 index 0000000..ea108f5 --- /dev/null +++ b/council/modules/ROOT/pages/contact.adoc @@ -0,0 +1,28 @@ +Contacting the Fedora Council +============================= + +The Fedora Council uses two mailing lists. + +https://lists.fedoraproject.org/admin/lists/council-discuss@lists.fedoraproject.org/[*council-discuss*] (formerly "board-discuss") is a public list. Subscription is open to +anyone, as are the archives. This list is the main discussion point for +the Fedora Council, and the goal of the list is to either reach a +decision, or to delegate the thread to a more appropriate location. For +example, engineering-specific threads may get some comments on +council-discuss, before being redirected to the devel list for in-depth +discussion. + +https://lists.fedoraproject.org/admin/lists/council-private@lists.fedoraproject.org/[*council-private*] is a private list. Its membership is restricted to the current +Council members, and its archives are private. This list is only used +for topics that cannot be discussed on the public council-discuss list. + +Council members are also often present on the *#fedora-council* IRC +channel on *irc.freenode.net* + +If you have an issue to be worked on by the Council you can also open a +ticket on the https://pagure.io/Fedora-Council/tickets[Council Pagure +instance]. This is a public issue tracker. However, if you have a +particularly privacy- or security-sensitive issue, you can check the +*Private* box when you create the ticket. If an issue is not sensitive +the discussion should be in the open, in the public Pagure instance or +the council-discuss list. + diff --git a/council/modules/ROOT/pages/diversity-advisor.adoc b/council/modules/ROOT/pages/diversity-advisor.adoc new file mode 100644 index 0000000..881d190 --- /dev/null +++ b/council/modules/ROOT/pages/diversity-advisor.adoc @@ -0,0 +1,63 @@ += Fedora Diversity Advisor = +The *Fedora Diversity Advisor* acts as a source of support and +information for all contributors and users, especially those from +underrepresented populations, so that issues of inclusion and equity can +be discussed and addressed with the planning of multiculturalism and +comfort. The Fedora Diversity Advisor will lead initiatives to assess +and promote equality and inclusion within the Fedora contributor and +user communities, and will develop project strategy on diversity issues. +The Diversity Advisor will also be the point of contact for Fedora’s +participation in third-party outreach programs and events. + +== Current Diversiity Advisor + +image::https://fedoraproject.org/w/uploads/7/7c/My.jpg[float="right",50%] +link:https://fedoraproject.org/wiki/User:Amsharma[Amita Sharma] has been involved with the Fedora project since 2011. +She started her contributions with work in Fedora QA. +She is also a founding member of the Fedora Diversity Team. +After contributing to the Diversity Team for around 2 years, Amita got the opportunity to represent the team as the Diversity Representative on the Fedora Council. +Amita works as a full time Senior Quality Assurance Engineer on Red Hat Directory Server at Red Hat in Pune, India. + +*Information about the Fedora Diversity Team is available at link:https://fedoraproject.org/wiki/Diversity[the team's wiki page]* + +[[responsibilities]] +== Responsibilities + +* Implement diversity efforts that will have a big effect on the Fedora community +* Promote inclusion in the Fedora community +* Act as a source of support and a mediator should there be any concerns or incidents +* Increase visibility of minority contributors and users through talks, feature articles, and awards +* Make explicit invitations and providing financial support to attend conferences and give talks +* Help develop skills by offering targeted workshops and internships +* Create a welcoming environment by adopting and enforcing codes of conduct +* Fostering communication, networking, and support forums with mailing lists and in-person events + +[[contact]] +== Contact + +Contact Amita Sharma online by pinging *Amita* on +#fedora-diversity on FreeNode IRC. The Diversity Advisor also joins +the link:https://fedoraproject.org/wiki/Diversity[Fedora Diversity +team meetings]. + +[[selection]] +== Selection + +The Diversity Advisor is selected by the +link:https://fedoraproject.org/wiki/Diversity[Fedora Diversity team] +and approved by the Fedora Council. Currently the Diversity Team has +decided to rotate the position with every release of Fedora. + +== History of Fedora Community Action and Impact Coordinators + +|=== +|Releases | Diversity Advisor + +|27, … +|https://fedoraproject.org/wiki/User:Amsharma[Amita Sharma] + +|23, 24, 26, 26 +|https://fedoraproject.org/wiki/User:Tatica[Maria "tatica" Leandro] + +|=== + diff --git a/council/modules/ROOT/pages/fcaic.adoc b/council/modules/ROOT/pages/fcaic.adoc new file mode 100644 index 0000000..27e9af3 --- /dev/null +++ b/council/modules/ROOT/pages/fcaic.adoc @@ -0,0 +1,82 @@ +Fedora Community Action and Impact Coordinator +============================================== + +The _Fedora Community Action and Impact Coordinator_ (or _FCAIC_) is a full-time, Red Hat-employed job to lead initiatives to grow the Fedora user and developer communities, and to make Red Hat / Fedora interactions even more transparent and positive. +The Fedora community budget comes to us through the Red Hat Open Source and Standards (OSAS) team. +This position facilitates decision-making on how to best focus that to meet our community's goals and objectives. +The FCAIC supports the link:fpl.html[Project Leader] with all things "Community" and works directly with the Fedora Leadership to help bring more Heat and Light to the project. + +The FCAIC is appointed to the Community Action and Impact seat on the Fedora link:charter.html[Council], Fedora’s top-level community leadership and governance body. +The Council is responsible for stewardship of the Fedora Project as a whole, and supports the health and growth of the Fedora Community. + +== Current F-🎂footnote:[What's with the cake? The abbreviation FCAIC sounds like "F-Cake" in American English. If this position is going to have a title that is a mouthful, at least the mouthful can be yummy cake!] + +image::bex-ocean-thumb.jpg[float="right",50%] +https://fedoraproject.org/wiki/User:bex[Brian (bex) Exelbierd] joined Red Hat in 2013 and became the Fedora Community Action and Impact Coordinator in October 2016. +At Red Hat, Brian has worked as a technical writer, software engineer, content strategist and is now an Open Source community manager in the Open Source and Standards team at Red Hat. +Before Red Hat, Brian worked with the University of Delaware as the Director of Graduate and Executive Programs in the Alfred Lerner College of Business and Economics and as a Budget Analyst. +Brian’s background in software engineering stretches back years before his university work and includes stints at small, medium, large and governmental organizations. +“Glue Code” is how many of Brian’s projects could be described. +These are projects that fill in the interstitial spaces between large systems and provide continuity and ease of use. +Follow him on Twitter https://twitter.com/bexelbie[@bexelbie] or on his http://www.winglemeyer.org[blog]. + +== Roles and Responsibilities == + +=== Council === + +* Work with other Council members to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them +* Primary Council member with responsibility for the development of the annual Fedora community budget +* Participate in decision-making about use of trademarks, project structure, community disputes or complaints, and other such issues + +=== Special Initiatives === + +* Design and spearhead special initiatives to grow user and contributor bases + +=== Metrics === + +* Implement metrics for community engagement, participation, and satisfaction; create and execute projects to improve those metrics; report regularly on progress and adjust approach as needed + +=== Opportunities === + +* Identify opportunities to engage new contributors and community members; align project around supporting those opportunities + +=== Liaise between Red Hat and FOSS Community === + +* Communicate community needs to Red Hat and participate in regular meetings with internal Red Hat stakeholders; align Red Hat participation in Fedora beyond platform engineering +* Represent Red Hat’s stake in Fedora community success +* Improve on-boarding materials and presentation of Fedora to new Red Hat hires; develop standardized materials on Fedora which can be used at Red Hat globally. + +=== Budget === + +The FCAIC will work with Fedora Council and OSAS to determine annual Fedora Budget + +* Ensure that budget is published and tracked transparently, with a public page indicating how each year’s budget is earmarked and its current state. +* The budget is published at https://budget.fedoraproject.org + +=== Fedora Event Planning and Participation === + +Participate in planning and organizing Fedora’s Flagship events each year, including: + +* Flock +* FUDCons +* Fedora Activity Days (FADs) + +The FCAIC also represents Fedora at other major industry conferences and hackathons such as: + +* AllThingsOpen +* DevConf +* FOSDEM +* PyCon (and Sprints) +* LibrePlanet +* Red Hat Summit +* Software Freedom Legal Conference + +=== Communications === + +The FCAIC provides and facilitates regular communications to Fedora Magazine, the Fedora Community Blog, and other mass communication channels to talk about community goals/progress and general community boosting. + +== Previous Fedora Community Action and Impact Coordinators + +https://fedoraproject.org/wiki/User:Decause[Remy DeCausemaker ]:: + February 2015 – June 2016 + diff --git a/council/modules/ROOT/pages/fpgm.adoc b/council/modules/ROOT/pages/fpgm.adoc new file mode 100644 index 0000000..8fe93b4 --- /dev/null +++ b/council/modules/ROOT/pages/fpgm.adoc @@ -0,0 +1,49 @@ +Fedora Program Manager +====================== + +The _Fedora Program Manager_ (or _FPgM_) is responsible for managing the planning and release processes for Fedora. This includes schedule management, change wrangling, and providing status reports to the community and to Red Hat. + +image::bcotton-rh_neo.jpeg[float="right",50%] +https://fedoraproject.org/wiki/User:Bcotton[Ben Cotton] is the current FPgM. He joined Red Hat after a decade in high performance computing (HPC) administration and marketing. Ben first started contributing to Fedora in 2009 as a member — and later leader — of the Fedora Docs team. He is a community moderator for Opensource.com and co-founded HackLafayette — a local tech meetup group. + +Contact Ben on Freenode IRC (`bcotton`) or by email (`bcotton@fedoraproject.org`). + +== Roles and Responsibilities == + +Within the Fedora Project, the Program Manager (FPGM) is primarily responsible for: + +* planning and http://fedorapeople.org/groups/schedule/[scheduling] of Fedora releases +* tracking the changes/features during the development/testing cycle +* release coordination (within QA, releng, FESCo, etc.) +* processes behind Fedora Project +* member of Fedora Council - Auxiliary Seat, Council secretary + +=== Program management SOPs === +This SOP (Standard Operating Procedure) section contains a list of common FPGMs tasks. + +* https://fedoraproject.org/wiki/Fedora_Program_Management/GoNoGoSOP[The Go/No-Go meeting] +* https://fedoraproject.org/wiki/Fedora_Program_Management/ReadinessSOP[The Readiness meeting] +* https://fedoraproject.org/wiki/Fedora_Program_Management/ChangesSOP[Change Process] +* https://fedoraproject.org/wiki/Fedora_Program_Management/EOLRebaseSOP[End Of Life and Rawhide Rebase] + +=== Release Planning === +https://fedoraproject.org/wiki/Releases[Track of releases] + +=== House Keeping === +Previously, house keeping was done in BugZappers wiki but as BugZappers group is dismissed for several years, it was moved to FPgM wiki. + +https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping[House keeping] + +== History == + +Previous Fedora Program Managers: + +* https://fedoraproject.org/wiki/User:Jkurik[Jan Kuřík] (Fedora 23-28) +* https://fedoraproject.org/wiki/User:Jreznik[Jaroslav Řezník] (Fedora 20-23) +* https://fedoraproject.org/wiki/User:Rbergero[Robyn Bergeron] (Fedora 17-20) +* https://fedoraproject.org/wiki/User:Poelstra[John Poelstra] (Fedora 8-16) + +== Useful links == +* http://fedorapeople.org/groups/schedule[Schedules] in HTML/ICS formats with sources +* https://pagure.io/fedora-project-schedule[Fedora Project Schedule repository] to report scheduling issues, and GIT with scripts making FPGM happier +* https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle[Fedora Release Life Cycle] aka how to schedule next Fedora release diff --git a/council/modules/ROOT/pages/fpl.adoc b/council/modules/ROOT/pages/fpl.adoc new file mode 100644 index 0000000..22683da --- /dev/null +++ b/council/modules/ROOT/pages/fpl.adoc @@ -0,0 +1,44 @@ += The Fedora Project Leader + +The _Fedora Project Leader_ (or _FPL_) is ultimately accountable for everything that happens within Fedora and in particular is responsible for maintaining Red Hat's relationship with Fedora and vice versa. +He/She is Fedora's President, CEO, Chair, Fearless Leader, whatever-you-want-to-call-it. +However the project leader is not a dictator, benevolent or otherwise. +The FPL chairs the Fedora link:charter.html[Council]. + +image::mattdm-2014-fedora10y-thumb.jpg[float="right",50%,link="https://fedoraproject.org/w/uploads/e/e8/Mattdm-2014-fedora10y-small.jpg"] +https://fedoraproject.org/wiki/User:mattdm[Matthew Miller] is the current Fedora Project Leader. +He led the Fedora.next initiative for a strategic approach to Fedora's second decade, +as well as the transition from the Fedora Board to the current Council governance model. +Matthew created the BU Linux distribution for Boston University in 1999 and maintained that through 2008, +when he moved to the Harvard School of Engineering and Applied Sciences to work on high performance computing and this up-and-coming “cloud” thing. +He has been at Red Hat since 2012, first working on Fedora Cloud and becoming FPL in June, 2014. + +Contact Matthew as `mattdm` on Freenode IRC, +as https://twitter.com/mattdm[@mattdm] on Twitter, or +on the +https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[Council-Discuss] +mailing list. + +== Previous Fedora Project Leaders + +https://fedoraproject.org/wiki/User:Rbergero[Robyn Bergeron]:: + February 2012 – June 2014 (Fedora 17 – 21) + +https://fedoraproject.org/wiki/User:Jsmith[Jared Smith]:: + July 2010 – February 2012 (Fedora 14 – 16) + +https://fedoraproject.org/wiki/User:Pfrields[Paul W. Frields]:: + February 2008 – July 2010 (Fedora 9 – 14) + +https://fedoraproject.org/wiki/User:Mspevack[Max Spevack]:: + February 2006 – February 2008 (Fedora Core 5 – Fedora 9) + +https://fedoraproject.org/wiki/User:Gdk[Greg DeKoenigsberg]:: + August 2005 – February 2006 (Fedora Core 4 & 5) + +Cristian Gafton:: + January 2004 – August 2005 (Fedora Core 2, 3, & 4) + +Michael Johnson:: + July 2003 – January 2004 (Fedora Core 1) + diff --git a/council/modules/ROOT/pages/history.adoc b/council/modules/ROOT/pages/history.adoc new file mode 100644 index 0000000..7e452cf --- /dev/null +++ b/council/modules/ROOT/pages/history.adoc @@ -0,0 +1,124 @@ +Fedora Council and Board Historical Membership +============================================== + +History of Fedora Council Membership +------------------------------------ +Previous members of the Fedora Council are listed here. + +Elected Representatives +~~~~~~~~~~~~~~~~~~~~~~~ + +|=== +|Nick Bebout | January 2018 – May 2018 (f28) +|Robert Mayr | December 2015 – January 2018 (f24-f25, f26-f27) +|Justin Flory | August 2017 – January 2018 (f27) +|Rex Dieter | November 2014 – December 2015 (f22-f23) +|Langdon White | November 2014 – August 2016 (f22, f23-f24, f25-f26) +|=== + +_Historical note: The initial elected representatives were selected in a +single election, with the candidate with the most votes selected for a full +term (through the release of F23) and the runner-up for a half term (through +the release of F22)._ + +Project Objective Leads +~~~~~~~~~~~~~~~~~~~~~~~ + +|=== +|Stephen Gallagher | _Three Editions (Fedora.next)_ | January 2015 – November 2015 +|Stef Walter | _CI/CD of Fedora Atomic Host_ | August 2017 – December 2017 +|=== + +Mindshare Representative +~~~~~~~~~~~~~~~~~~~~~~~~ + +|=== +|Christoph Wickert (Outreach Representative) | January 2015 – December 2016 +|=== + + +Diversity Advisor +~~~~~~~~~~~~~~~~~ + +|=== +|María Leandro | March 2016 — March 2017 +|=== + +Fedora Program Manager +~~~~~~~~~~~~~~~~~~~~~~ + +|=== +|Jan Kuřík | June 2015 — February 2018 +|Jaroslav Reznik | September 2014 – May 2015 +|=== + +Fedora Community Action and Impact Coordinator +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +|=== +|Remy DeCausemaker | February 2015 – June 2016 +|=== + + +''' +<<< + + + +History of Fedora Board Membership +---------------------------------- + +The Fedora Board was the Project's top-level governance body from July 2007 +to November 2014. Before that, the "Fedora Advisory Board" was merely (as +the name suggests) advisory and had no formal membership. + +|=== +|Elliot Lee | Apr 2006 - Nov 2006 +|Jeremy Katz | Apr 2006 - Jul 2007 +|Rahul Sundaram | Apr 2006 - Jul 2007 +|Paul Frields | Apr 2006 - Jul 2007, Feb 2008 - Jul 2010 +|Rex Dieter | Apr 2006 - Jul 2007, Jun 2010 - Jun 2012, Dec 2012 - Oct 2014 +|Chris Blizzard | Apr 2006 - Dec 2007 +|Max Spevack | Apr 2006 - Feb 2008 +|Bill Nottingham | Apr 2006 - Dec 2008, Dec 2008 - Dec 2009 +|Seth Vidal | Apr 2006 - Jul 2009 +|Matt Domsch | Apr 2006 - Nov 2010 +|Greg DeKoenigsberg | Nov 2006 - Jul 2007 +|Steve Dickson | Jul 2007 - Jun 2008 +|Christopher Aillon | Jul 2007 - Jun 2008, Dec 2008 - Dec 2010 +|Dennis Gilmore | Jul 2007 - Jun 2008, Jun 2009 - Jun 2010 +|Jef Spaleta | Jul 2007 - Dec 2008 +|Karsten Wade | Jul 2007 - Dec 2008 +|Bob McWhirter | Dec 2007 - Jun 2008 +|Dimitris Glezos | Dec 2008 - Dec 2009 +|Harald Hoyer | Jul 2008 - Jun 2009 +|Jesse Keating | Jul 2008 - Jun 2009 +|Chris Tyler | Jul 2008 - Jun 2009, Dec 2009 - Nov 2010 +|Tom Callaway | Jul 2008 - Jun 2011 +|John Poelstra | Jun 2009 - Jun 2010 +|Mike McGrath | Jun 2009 - Jun 2010 +|Josh Boyer | Jun 2009 - Jun 2010, Jun 2013 - Oct 2014 +|Colin Walters | Dec 2009 - Nov 2010 +|Mairin Duffy | Jun 2010 - Jun 2011 +|Stephen Smoogen | Jun 2010 - Jun 2011 +|Jon Stanley | Jun 2010 - Jun 2012 +|Jared Smith | Jul 2010 - Feb 2012 +|Joerg Simon | Nov 2010 - Dec 2011 +|Jaroslav Reznik | Nov 2010 - Jan 2014 +|David Nalley | Dec 2010 - Dec 2012 +|Toshio Kuratomi | Nov 2010 - Nov 2012 +|Rudi Landmann | Jun 2011 - May 2012 +|Guillermo Gomez | Jun 2011 - Jun 2012 +|Peter Robinson | Jun 2011 - Jun 2013 +|Christoph Wickert | Dec 2011 - Dec 2012 +|Robyn Bergeron | Feb 2012 - Jun 2014 +|Garrett Holmstrom | May 2012 - Oct 2014 +|Nick Bebout | Jun 2012 - Jun 2013 +|Eric Christensen | Jun 2012 - Oct 2014 +|John Rose | Jun 2012 - Oct 2014 +|Major Hayden | Nov 2012 - Oct 2014 +|Michael Scherer | Dec 2012 - Jan 2014 +|Matthew Garrett | Jun 2013 - Oct 2014 +|Haïkel Guémar | Jan 2014 - Oct 2014 +|Neville Cross | Jan 2014 - Oct 2014 +|=== diff --git a/council/modules/ROOT/pages/index.adoc b/council/modules/ROOT/pages/index.adoc new file mode 100644 index 0000000..07cd132 --- /dev/null +++ b/council/modules/ROOT/pages/index.adoc @@ -0,0 +1,334 @@ +Fedora Council Charter +====================== + +image::council-logo-500px.png[float="right"] + +The Fedora Council is our top-level community leadership and governance +body. It is responsible for stewardship of the Fedora Project as a +whole, and supports the health and growth of the Fedora Community. + +The Council is composed of a mix of representatives from different areas +of the project, named roles appointed by Red Hat, and a variable number +of seats connected to medium-term project goals. Decisions are made by a +*consensus process*, in which we work together as a common team to find +shared solutions and address concerns, with a focus on giving voice +rather than on balance of power. + +The Council is ultimately accountable for the Fedora Project as a whole, +and is responsible for providing advice to and oversight of other Fedora +governance bodies and teams as needed. + +Responsibilities +---------------- + +The Council is responsible for issues of strategic importance for Fedora +that require leadership and coordination across the various teams and +subprojects to achieve. + +*Its primary role is to identify the short, medium, and long term goals +of the Fedora community and to organize and enable the project to best +achieve them.* This is done in consultation with the entire Fedora +community through transparent, public discussion. + +The Council *governs Fedora's financial resources*, working with our +sponsor(s) to establish an annual budget allocated to support Fedora +initiatives, including Fedora Ambassadors, Fedora-managed events, and +other activities which advance the project's goals. + +The Council also decides on issues regarding use of the Fedora +*trademarks*, is responsible for final *arbitration of complaints* +related to project policies and for *settling disputes* escalated from +other committees or subgroups, and may handle *sensitive legal or +personnel issues* which require research and discussion to protect the +interests of the Fedora Project or its sponsor(s). + + +Making Decisions +---------------- + +**** +Consensus decision-making aims to be: + +* *Agreement Seeking:* A consensus decision-making process attempts to help everyone get what they need. +* *Collaborative:* Participants contribute to a shared proposal and shape it into a decision that meets the concerns of all group members as much as possible. +* *Cooperative:* Participants in an effective consensus process should strive to reach the best possible decision for the group and all of its members, rather than competing for personal preferences. +* *Egalitarian:* All members of a consensus decision-making body should be afforded, as much as possible, equal input into the process. All members have the opportunity to present, and amend proposals. +* *Inclusive:* As many stakeholders as possible should be involved in the consensus decision-making process. +* *Participatory:* The consensus process should actively solicit the input and participation of all decision-makers + +— from https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[Wikipedia on Consensus decision-making] + +**** + +Many basic decisions are made through a process known as “*lazy +approval*”, in which general consent is assumed unless valid objections +are raised within a period of time — generally three to seven days, +although the timeframe should be stated each time and should be +proportionate to the impact of the action. This process is used for +decisions with short-term consequences and which can be easily reversed. +Any project member can ask for the deadline to be extended or the +decision escalated to require full consensus. + +More significant decisions are made through a process of *full +consensus*. In order to pass, these decisions need three positive votes +(+3) and _no_ negative votes (-1). A negative vote immediately halts the +process and requires discussion. Therefore, in order to remain valid, +negative votes must be supported with a specific concerns about the +proposal, and suggestions for what could be changed in order to make the +proposal acceptable. A vote of “0” is sometimes used to indicate a +disagreement but willingness to stand aside; this should also be +accompanied with an explanation. + +This model matches Fedora's “Friends” foundation, which calls for +finding acceptable consensus to serve the interests of advancing free +software. It works because we work together in a community of mutual +respect even when we disagree. + +In general, the Council conducts business in public discussion, and any +Fedora project member can make negative or positive votes. It is the +duty of the Council to take concerns raised in this way into serious +consideration, but only Council members' votes are binding in the final +tally. + +When consensus can't be reached, the Council may ask the Fedora Project +Leader to decide on a resolution. Such a request can be made when issues +leading to negative votes are outstanding and all Council members agree +that the Council is deadlocked, or if the dispute is unresolved after +fourteen days and a simple majority of Council members are in favor of +the request. + + +Composition +----------- + + +Objective Leads +~~~~~~~~~~~~~~~ + +On an ongoing basis, including sessions at Flock and in public online +meetings, the Council will identify two to four key community objectives +with a timeframe of approximately eighteen months, and appoint +*Objective Leads* for each goal. These will serve as auxiliary Council +members, with binding votes only over concerns relevant to their +particular area. + +Each objective will be documented with measurable goals, and the +objective lead is responsible for coordinating efforts to reach those +goals, evaluating and reporting on progress, and working regularly with +all relevant groups in Fedora to ensure that progress is made. + + +Representatives +~~~~~~~~~~~~~~~ + +The Council also includes four representative seats, an *Engineering +Representative*, an *Mindshare Representative*, and two *Elected +Representatives*. + +“Engineering” and “Mindshare” are broad areas roughly encompassing two +of the major areas of activity in Fedora. _Engineering_ is the technical +work related to building and releasing the Fedora operating system and +the infrastructure related to that. _Mindshare_ includes marketing, +design, and Fedora Ambassadors — largely activities that happen between +Fedora and the world at large, with the distribution release cycle +serving as a fuel source, not the thing that's being worked on. + +The engineering and mindshare representatives' responsibility is to +represent their areas collectively, _not_ to be just an individual voice +that happens to be voted-in by some subset of Fedora. They are selected +by the people active in those areas, coordinated by the Fedora +Engineering Steering Committee (FESCo) and a to-be-created mindshare +group respectively, and serve for terms to be determined by those +committees. + +The elected positions cover all Fedora subprojects that are not under the +engineering or mindshare banners, and the community at large. One +specific responsibility is to represent the voice of individual +contributors to the Fedora project. Each representative will also work +on specific goals which she or he brings to the Council as highlighted +during the election process. + +Elections are held twice a year, in concert with the joint Fedora +election cycle. One seat is selected at each election, and each position +has a two-election (approximately one year) term. No person who +currently holds another Council seat can be elected. If a seat becomes +vacant, the Council will arrange for a temporary replacement. + + +Appointed Leadership Positions +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +*Fedora Project Leader* + +The link:fpl.html[Fedora Project Leader] serves as the +chair of the Council, organizing discussion agendas, bringing issues to +the table, and facilitating the consensus process. He or she is +accountable for success in all areas of the project, but is not a +dictator, benevolent or otherwise. The FPL often serves as the public +face and collective voice of the project, and has a corresponding duty +to listen to, understand, and fairly represent the collective views and +needs of project contributors and stakeholders. + +The Fedora Project Leader is hired by Red Hat with the advice and +consent of the Council. + +*Fedora Community Action and Impact Coordinator* + +The link:fcaic.html[Fedora Community Action and Impact +Coordinator (FCAIC)] initiatives to grow the Fedora user and developer +communities, and to make Red Hat / Fedora interactions even more +transparent and positive. The Fedora community budget comes to us +through OSAS, and this position facilitates decision-making on how to +best focus that to meet our collective objectives. + + +Auxiliary Seats +~~~~~~~~~~~~~~~ + +As with the objective leads, the next two appointed positions are +auxiliary seats. They are intended to have significant positive impact +on the project as a whole, but in order to minimize the overall +influence of appointed positions vs. those selected by the community, +their votes in the consensus process are expected to be related to the +scope of the respective role. + +*Diversity Team Representative* + +The Fedora https://fedoraproject.org/wiki/Diversity[Diversity Team] +works on initiatives to assess and promote equality and inclusion +within the Fedora contributor and user communities, and helps develop +project strategy on diversity issues. The Diversity Team Representative +connects the team's efforts to the Council. + +This position is appointed by members of the Fedora Diversity Team, +with the approval of the Council. + +*Fedora Program Manager* + +The https://fedoraproject.org/wiki/Fedora_Program_Management#Fedora_Program_Manager[FPgM] coordinates the planning and +scheduling of Fedora releases, and tracks changes and features during +the development and testing cycle. He or she also assists with the +creation, maintenance, and execution of formal, repeatable Fedora +processes. Additionally, the FPgM serves as record keeper and secretary +for Fedora Council Meetings. + +This position is funded by and hired for by Red Hat, with the approval +of the Council. + + +Coda +---- + + +Meetings +~~~~~~~~ + +The Fedora Council is not driven by meetings or by tickets, but does +hold https://fedoraproject.org/wiki/Council_Meetings[regular public IRC meetings] to +discuss current issues, to clear through anything outstanding which can +be quickly resolved, and to ensure that nothing important is left in +limbo. All members are be expected to regularly communicate what's going +on in their area, through blog posts or other public updates. + +Additionally, the Fedora Project Leader will set aside regular times on +IRC to meet with the community. Attendance is not mandatory for all +members but is encouraged. + + +Transparency +~~~~~~~~~~~~ + +The general policy of the Fedora Council is to default to open. Meetings +are held in public IRC channels, and open to all Fedora users and +contributors. Discussion is held in on a +https://lists.fedoraproject.org/mailman/listinfo/council-discuss[public +mailing list] open to all subscribers, and formal decisions will be +recorded in a public ticket tracking system. + +Occasionally, when personal, private, or sensitive issues need to be +discussed, a phone call might be used. A private mailing list and ticket +tracking instance also exist for these situations, but will also only be +used when dealing with these uncommon issues. + + +Time Commitment +~~~~~~~~~~~~~~~ + +Serving on the Fedora Council is a significant commitment of time and +energy. Workload for the various roles will vary, but each will require +a number of hours every week, and in most cases, the more, the better a +Council member is able to do the job fully. + +We recognize that most Fedora community members do not have the luxury +of working on Fedora full-time or as part of a paid position. The time +commitment required for these roles comes simply from what is required +to lead a large project like Fedora, and is not intended to be an +artificial limit on who can participate. We know that that it can be a +_pragmatic_ limit, and for that reason, the Council is responsible for +extra effort to receive, recognize, be responsive to, and meaningfully +reward the input of contributors offering their individual time. + + +Governance Philosophy +~~~~~~~~~~~~~~~~~~~~~ + +To advance free software, we need to provide a sustainable integration +of free software without cutting corners. By providing a positive first +impression before and during installation and real use, we support +Fedora's reputation as a leading and reliable product that attracts +future users and contributors. To provide that integration and +experience we must have a clear set of priorities to help all +contributors decide how to allocate resources and resolve conflicts. +These priorities are not meant to be exclusive, or to keep contributors +from working on the parts of Fedora that matter to them. + +These priorities will sometimes expose gaps where contributors need +additional assistance, and allow them to seek it both within the +community and by bringing in additional contributors to help, +exclusively on their particular interest area if desired. While +narrowing our focus in some areas, though, we must provide opportunities +for exploration to all contributors within the framework of our core +values and without impeding progress. + + +Historical Note +~~~~~~~~~~~~~~~ + +The previous https://fedoraproject.org/wiki/Board[previous governance structure (Fedora Board)] +had five members directly appointed by Red Hat and five elected at +large. The current structure is more complicated but has a much greater +proportion of members selected by the community by election or merit. In +the previous board structure, the Fedora Project leader had a special +veto power; in the current model, all voting members can block on +issues, with a valid reason. The FPL does not have a special veto, but +does have a limited power to “unstick” things if consensus genuinely +can't be reached and a decision needs to be made. + + +Record of Former Members +~~~~~~~~~~~~~~~~~~~~~~~~ + +Former membership on the Fedora Council, along with membership on the +previous Fedora Board, is documented on the link:history.html[History of +Council Membership] page. + + +Document History +~~~~~~~~~~~~~~~~ + +This charter was approved by the Fedora Project Board on +https://fedorahosted.org/council/ticket/13[Oct. 9th, 2014] and is in effect +as of Nov. 26th, 2014. Any other significant changes will be noted here; +smaller changes (minor wording or formating, etc., without impact on +meaning) can be found in the +https://pagure.io/Fedora-Council/council-docs/commits/master[git repository] +for Council documents. + +2017-11-15: Update Diversity Advisor to Diversity Team Representative + +2017-10-20: Move current membership list and contact info to separate docs. + +2017-04-05: Switched “Outreach” to Mindshare. (https://pagure.io/Fedora-Council/tickets/issue/102[ticket]) + +2014-11-26: Initital approval by the Fedora Project Board (https://pagure.io/Fedora-Council/tickets/issue/13[ticket]) + diff --git a/council/modules/ROOT/pages/members.adoc b/council/modules/ROOT/pages/members.adoc new file mode 100644 index 0000000..fef6125 --- /dev/null +++ b/council/modules/ROOT/pages/members.adoc @@ -0,0 +1,48 @@ +Current Members of the Fedora Council +===================================== + +image::council-badge.png[float="right"] + +* Elected Representative: *https://fedoraproject.org/wiki/User:Ausil[Dennis Gilmore]* _(f28-f29)_ ++ +Dennis has been involved in Fedora since the begining. Holding various roles. +From leading up Alternative Architectures, to leading Release Engineering, +contributing to Infrastructure, helping found EPEL, Serving on the Board and +Fedora Engineering Steering Committee. He works at Red Hat in the Platform +Enablement organisation working on multi-arch. + +* Elected Representative: *Till Maas* _(f29-f30)_ + +* Engineering Representative: *Josh Boyer* ++ +Josh has been involved with Fedora for over 10 years. He started as nothing +more than a user, then a mailing list contributor, and has continued to +participate in a number of different SIGs, committees, and roles. Josh +is currently on the Fedora Engineering Steering Committee in addition to his +Council role. He works at Red Hat in the Platform Engineering organization. ++ +You can find him on Freenode irc as `jwb`. + +* Mindshare Representative: *Robert Mayr* + +* Diversity Team Representative: *Amita Sharma* + ++ +Read more about the link:diversity-advisor.html[Fedora Diversity Advisor's role] and current Fedora Diversity Advisor's link:diversity-advisor.html[biography] on the page about this position. + +* Fedora Project Leader: *Matthew Miller* ++ +Read more about the link:fpl.html[Fedora Project Leader's role] and the current FPL's link:fpl.html[biography] on the page about this position. + +* Fedora Community Action and Impact Coordinator: *Brian Exelbierd* ++ +Read more about the link:fcaic.html[Fedora Community Action and Impact Coordinator's role] and the current FCAIC's link:fcaic.html[biography] on the page about this position. + +* Fedora Program Manager: *Ben Cotton* ++ +Read more about the link:fpgm.html[Fedora Program Manager's role] and the current FPgM's link:fpgm.html[biography] on the page about this position. + +* Objective Leads: + *Langdon White* (Fedora Modularity), + *Dominik Perpeet* (Atomic CI/CD), + *Peter Robinson* (Internet of Things) diff --git a/council/modules/ROOT/pages/policies.adoc b/council/modules/ROOT/pages/policies.adoc new file mode 100644 index 0000000..ce49551 --- /dev/null +++ b/council/modules/ROOT/pages/policies.adoc @@ -0,0 +1,14 @@ +[NOTE] +==== + +This page is a placeholder. It should include links to all currently active +Council policy documents. You can help make this document more useful by +submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs + +==== + +# Code of Conduct reponse policy + +Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response. + +(Fedora Council IRC meeting, 2018-05-23) \ No newline at end of file diff --git a/council/policies.adoc b/council/policies.adoc deleted file mode 100644 index ce49551..0000000 --- a/council/policies.adoc +++ /dev/null @@ -1,14 +0,0 @@ -[NOTE] -==== - -This page is a placeholder. It should include links to all currently active -Council policy documents. You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - -==== - -# Code of Conduct reponse policy - -Once a ticket notifying us of a code of conduct issue has been filed, the Council will respond with an initial contact message within one week. That will come with a request for response, and further action will come within a week of the Council's initial response. - -(Fedora Council IRC meeting, 2018-05-23) \ No newline at end of file diff --git a/fesco/antora.yml b/fesco/antora.yml new file mode 100644 index 0000000..1005e8b --- /dev/null +++ b/fesco/antora.yml @@ -0,0 +1,16 @@ +# Name will be mostly visible in the URL. Treat it as an indentifier. +# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) +name: fesco + +# Title will be visible on the page. +title: FESCo + +# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. +version: master + +# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. +start_page: ROOT:index + +# This lists all the menu definitions of your component. +nav: +- modules/ROOT/nav.adoc diff --git a/fesco/modules/ROOT/nav.adoc b/fesco/modules/ROOT/nav.adoc new file mode 100644 index 0000000..c3d173e --- /dev/null +++ b/fesco/modules/ROOT/nav.adoc @@ -0,0 +1 @@ +* xref:teams.adoc[Technical Teams] diff --git a/fesco/modules/ROOT/pages/index.adoc b/fesco/modules/ROOT/pages/index.adoc new file mode 100644 index 0000000..f2e7345 --- /dev/null +++ b/fesco/modules/ROOT/pages/index.adoc @@ -0,0 +1,37 @@ +Fedora Engineering Steering Committee +===================================== + +[.lead] +FESCo is the Fedora Engineering Steering Committee. It is a fully community +elected body and represents the technical leadership in Fedora. + +Overall Mission +--------------- + +FESCo handles the process of accepting new features, the acceptance of new +packaging sponsors, Special Interest Groups (SIGs) and SIG Oversight, the +packaging process, handling and enforcement of maintainer issues and other +technical matters related to the distribution and its construction. + +Common tasks and responsibilities +--------------------------------- + +Issues FESCo handles include: + +* Approval and coordination of "Changes" for Fedora releases +* Package maintainer disputes +* Larger changes to the Fedora Package collection +* Guidance and technical direction for other parts of the project +* Setting the schedule for Fedora development cycles +* Reviewing and approving technical content from Fedora Working groups +* Responsible for what software is offered to end users under what + conditions +* Oversight and approval of new spins and other media that doesn't fit + under a working group + +More Info +--------- + +You can find further information about FESCo, its members, and its policies +on the +https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo wiki pages] diff --git a/fesco/modules/ROOT/pages/teams.adoc b/fesco/modules/ROOT/pages/teams.adoc new file mode 100644 index 0000000..554c410 --- /dev/null +++ b/fesco/modules/ROOT/pages/teams.adoc @@ -0,0 +1,3 @@ += Technical Teams in Fedora + +* xref:modularity:ROOT:index.adoc[**Fedora Modularity**] — Modularity introduces an optional Modular repository that provides additional versions of software on independent lifecycles. diff --git a/index-main.html b/index-main.html deleted file mode 100644 index f951554..0000000 --- a/index-main.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - - - - - Fedora Council Docs Website - - - - - - - - - - - - - - -
-
-
- -
-
-
-
-

Fedora Council Docs Site

-

Test Build.

-
-
-
Fedora Council Docs
-
- -  Documentation - -
-
-
-
-
-
-
-
-
-

About

-
-
-
About Fedora
-
Sponsors
-
Fedora Magazine
-
Legal
-
-
    -
  • - -
    • -
  • - -
    • -
  • - -
    • -
-
-
- -
-

Download

-
-
-
Get Fedora Workstation
-
Get Fedora Server
-
Get Fedora Atomic
-
Fedora Spins
-
Fedora Labs
-
Fedora ARM®
-
Alternative Downloads
- -
-
-
- -
-

Support

-
-
-
Get Help
-
Ask Fedora
-
Common Bugs
-
Fedora Developer Portal
-
Installation Guide
-
-
-
- -
-

Join

-
-
-
Join Fedora
-
Planet Fedora
-
Fedora SIGs
-
Fedora Account System
-
Fedora Community
-
-
-
-
- -
-
-
- -
-
-
-
- - -

© 2017 Red Hat, Inc. and others. Please send any comments or corrections to the websites team

-
-
-
- -
-
-
- - - - - - diff --git a/mindshare/antora.yml b/mindshare/antora.yml new file mode 100644 index 0000000..96cd004 --- /dev/null +++ b/mindshare/antora.yml @@ -0,0 +1,16 @@ +# Name will be mostly visible in the URL. Treat it as an indentifier. +# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) +name: mindshare + +# Title will be visible on the page. +title: Fedora Mindshare + +# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. +version: master + +# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. +start_page: ROOT:index + +# This lists all the menu definitions of your component. +nav: +- modules/ROOT/nav.adoc diff --git a/mindshare/modules/ROOT/assets/images/Screenshot_from_2017-09-22_23-33-02.png b/mindshare/modules/ROOT/assets/images/Screenshot_from_2017-09-22_23-33-02.png new file mode 100644 index 0000000..04722cf Binary files /dev/null and b/mindshare/modules/ROOT/assets/images/Screenshot_from_2017-09-22_23-33-02.png differ diff --git a/mindshare/modules/ROOT/nav.adoc b/mindshare/modules/ROOT/nav.adoc new file mode 100644 index 0000000..bf0a0a1 --- /dev/null +++ b/mindshare/modules/ROOT/nav.adoc @@ -0,0 +1 @@ +* xref:teams.adoc[Mindshare Teams] diff --git a/mindshare/modules/ROOT/pages/index.adoc b/mindshare/modules/ROOT/pages/index.adoc new file mode 100644 index 0000000..7bd1b8d --- /dev/null +++ b/mindshare/modules/ROOT/pages/index.adoc @@ -0,0 +1,88 @@ += Mindshare + +The Fedora Mindshare Committee represents the outreach leadership in Fedora. Mindshare aims to help outreach teams to reach their targets in a more effective way, by unifying and sharing their working process through an optimized and standardized communication. It consists of mostly appointed, but also elected members. + +== Responsibilities + +Mindshare takes care of some responsibilities hold actually by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed. These include: + +* Communication between teams (outreach teams rely on the work of other groups). Mindshare ensures all information from technical teams will get out in time to all outreach teams, working out also a common strategy with Marketing of how to communicate them outside and how to manage them within all outreach teams. +* Ambassadors activity: Mindshare will create templates to help ambassadors to work more effectively. Not only by providing report templates, but also by asking them once a year to compile a short survey. This can help to get real information whether an ambassador is active or not and will not result too binding. +* Motivate contributors to work also in other groups, providing easier access to funding and more autonomy. This challenging part will need some verifying tools (TBD) +* Mindshare takes over all decisional responsibilities left on FAmSCo. Administrative responsibilities will be handled by FAmA, which will consist mainly by treasurers and FAmA admins. +* CommOps which is part of Mindshare takes care of the operations inside Fedora. CommOps will lead the communication between technical and outreach teams. +* Sharing best practices: one of the Mindshare's goals is to take down barriers or whatever is blocking sharing best practices. All teams and all regions can learn from each other and apply successful practices to their local community. +* Mindshare will also try to unify ambassadors more and more, also by dropping the actual Regions. They are not helping communication and were created mostly for organizational aspects. FAmA (with treasurers) will help to sort out regional aspects and meetings, but having a unique ambassadors group will help in several ways to be more effective again. +* Budget: Without regions also the (ex-)regional budgeting process changes. Mindshare will, in collaboration with the FCAIC and consequently with the Council, take care of the Fedora outreach budget (sum of the 4 regional budgets). Minor funding requests can be handled directly by FAmA and treasurers, more important expenses will go through Mindshare, in order to be able and track even necessary reports the Council needs. +* Marketing as part of Mindshare will drive the other teams by providing messages, strategies and talking points for ambassadors. A good collaboration with the other teams is necessary. + +== Making Decisions + +Many basic decisions are made through a process known as *"lazy approval"*, in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus. + +More significant decisions are made through a process of *full consensus*. In order to pass, these decisions need three positive votes (+3) and no negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the poposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of "0" is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation. + +This model matches Fedora's "Friends" foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree. + +In general, Mindsharel conducts business in public discussion, and any Fedora project member can add more opinions and thoughts. It is the duty of the Mindshare Committee to take concerns raised in this way into serious consideration, but only Mindshare members' votes are binding in the final tally. + +== Composition + +image::Screenshot_from_2017-09-22_23-33-02.png[Mindshare Structure,100%,] + +Mindshare has appointed and elected members, and initially there will be 9 seats: + +* FCAIC (chair) +* Ambassadors (2 appointed members) +* Design & Web (appointed) +* Docs (appointed) +* Marketing (appointed) +* Commops (appointed) +* 2 elected seats + +*Note:* The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even. + +== Current Members + +* Elected Representative: *Jared Smith* (https://fedoraproject.org/wiki/User:Jsmith[jsmith]) (_f27-f28_) +* Elected Representative: *Sumantro Mukherjee* (https://fedoraproject.org/wiki/User:Sumantrom[sumantrom])(_f28-f29_) +* FCAIC: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex]) +* Ambassador Representative: FAmA *Robert Mayr* (https://fedoraproject.org/wiki/User:Robyduck[robyduck]) - _ad interim_ +* Ambassador Representative: FAmA *Nick Bebout* (https://fedoraproject.org/wiki/User:Nb[nb]) - _ad interim_ +* Marketing Representative: *Eduard Lucena* (https://fedoraproject.org/wiki/User:X3mboy[x3mboy]) +* CommOps Representative: *Justin W. Flory* (https://fedoraproject.org/wiki/User:Jflory7[jflory7]) +* Design & Web Representative: *Maria Leonova* (https://fedoraproject.org/wiki/User:Mleonova[mleonova]) +* Docs Representative: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex]) - _ad interim_ + +== Contact Info + +=== Mailing lists + +The Mindshare Committee uses two mailing lists: a regular discussion list and an announcement-only mailing list. + +*https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[mindshare]* is a public discussion list. +This is the main discussion point for the Mindshare Committee. +The goal of the list is to either reach a decision or delegate a thread to a more appropriate location. + +*https://lists.fedoraproject.org/admin/lists/mindshare-announce@lists.fedoraproject.org/[mindshare-announce]* is a low-traffic, announcement-only mailing list. +This list is used for occasional updates, news, and announcements from the Committee. +Posting privileges are limited to Mindshare Committee members. +Consider subscribing to this list if you want to stay informed about ongoing activities within the Mindshare Committee. + +== IRC / Telegram + +Mindshare Committee members are present in the *#fedora-mindshare* IRC channel on the Freenode IRC network. +This IRC channel is also bridged to a Telegram group for convenience. +Messages are synchronized between the two. +Telegram users can join https://t.me/fedoramindshare[here]. + +== Pagure == + +The Mindshare Committee operates in a ticket-based workflow. +If you have an issue or task for the Mindshare Committee, open a ticket on the https://pagure.io/mindshare/issues[Pagure instance]. +This is a public issue tracker. +If you have a privacy- or security-sensitive issue, check the _Private_ box when creating the ticket. + +== Meetings + +The Fedora Mindshare Committee does hold regular public IRC meetings to discuss current issues, to clear through anything outstanding which can be quickly resolved, and to ensure that nothing important is left in limbo. All members are be expected to regularly communicate what's going on in their area, through blog posts or other public updates. diff --git a/mindshare/modules/ROOT/pages/teams.adoc b/mindshare/modules/ROOT/pages/teams.adoc new file mode 100644 index 0000000..6b2fc9e --- /dev/null +++ b/mindshare/modules/ROOT/pages/teams.adoc @@ -0,0 +1,3 @@ += Outreach Teams in Fedora + +* xref:commops:ROOT:index.adoc[**Fedora Community Operations (CommOps)**] — Community Operations (CommOps) provides tools, resources, and utilities for different sub-projects of Fedora to improve effective communication. \ No newline at end of file diff --git a/preview.sh b/preview.sh new file mode 100755 index 0000000..acab783 --- /dev/null +++ b/preview.sh @@ -0,0 +1,18 @@ +#!/bin/sh + +if [ "$(uname)" == "Darwin" ]; then + # Running on macOS. + # Let's assume that the user has the Docker CE installed + # which doesn't require a root password. + echo "The preview will be available at http://localhost:8080/" + docker run --rm -v $(pwd)/public:/usr/share/nginx/html:ro -p 8080:80 nginx + +elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then + # Running on Linux. + # Let's assume that it's running the Docker deamon + # which requires root. + echo "" + echo "This build script is using Docker to run the build in an isolated environment. You might be asked for a root password in order to start it." + echo "The preview will be available at http://localhost:8080/" + sudo docker run --rm -v $(pwd)/public:/usr/share/nginx/html:ro -p 8080:80 nginx +fi diff --git a/project/antora.yml b/project/antora.yml new file mode 100644 index 0000000..855b68b --- /dev/null +++ b/project/antora.yml @@ -0,0 +1,16 @@ +# Name will be mostly visible in the URL. Treat it as an indentifier. +# Tip: If you want to use the local preview scripts that come with this repository, please change this value in the site.yml file as well. (under site/start_page) +name: project + +# Title will be visible on the page. +title: Fedora Project + +# If you don't plan to have multiple versions of the docs (for example, to document multiple versions of some software), you can ignore this field. Otherwise, change "master" to a specific version. +version: master + +# We encourage you to name the index page as "index.adoc". If you absolutely have to use a different name, please reflect it here. You can ignore this field otherwise. +start_page: ROOT:index + +# This lists all the menu definitions of your component. +nav: +- modules/ROOT/nav.adoc diff --git a/project/code-of-conduct.adoc b/project/code-of-conduct.adoc deleted file mode 100644 index 4c4c665..0000000 --- a/project/code-of-conduct.adoc +++ /dev/null @@ -1,28 +0,0 @@ -Code of Conduct -=============== - -The Fedora community is made up of a mixture of professionals and volunteers -from all over the world, working on every aspect of the distribution from -coding through to marketing. Diversity is one of our huge strengths, but it -can also lead to communication issues and unhappiness. To that end, we have -a few ground rules that we ask people to adhere to when they're using -project resources. - -This isn't an exhaustive list of things that you can't do. Rather, take it -in the spirit in which it's intended - a guide to make it easier to be -excellent to each other. - -* Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. - -* Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Fedora community should be respectful when dealing with other contributors as well as with people outside the Fedora community and with users of Fedora. - -When we disagree, we try to understand why. Disagreements, both social and -technical, happen all the time and Fedora is no exception. It is important -that we resolve disagreements and differing views constructively. - -Remember that we're different. The strength of Fedora comes from its varied -community, people from a wide range of backgrounds. Different people have -different perspectives on issues. Being unable to understand why someone -holds a viewpoint doesn't mean that they're wrong. Don't forget that it is -human to err and blaming each other doesn't get us anywhere, rather offer to -help resolving issues and to help learn from mistakes. diff --git a/project/fedora-overview.adoc b/project/fedora-overview.adoc deleted file mode 100644 index 8d59f1a..0000000 --- a/project/fedora-overview.adoc +++ /dev/null @@ -1,219 +0,0 @@ -Fedora's Mission and Foundations -================================ - -.How do I get the software? -[[getfedora]] -[sidebar.width50] -**** -image:banner-getfedora_sq.png[Get Fedora,title="getfedora.org",float="right",role="pl-2",link=https://getfedora.org/] - -Download one of the different editions of Fedora for your laptop/desktop, -server, or containers at https://getfedora.org[Get Fedora], or explore other -options provided by https://labs.fedoraproject.org/[Labs], -https://spins.fedoraproject.org/[Spins], -https://arm.fedoraproject.org/[ARM], and -https://alt.fedoraproject.org/[Alternative Downloads]. - -Everything included is open source and free software — not only is it -available at no cost to you, but you can share, remix, and modify. -**** - -What is Fedora? ---------------- - -[.lead] -The Fedora Project is a community of people working together to build a -free and open source software platform and to collaborate on and share -user-focused solutions built on that platform. Or, in plain English, we -make an operating system and we make it easy for you do useful stuff -with it. - - -<<< - - -What is Fedora all about? -------------------------- - -The Fedora community includes thousands of individuals with different -views and approaches, but together we share some common values. We call -these the “*Four Foundations*”: Freedom, Friends, Features, and First. - -[cols="1a,1a",frame=none,grid=none,nostriping] -|=== -|Freedom -~~~~~~~ - -image:divider-top-freedom.png[Four Foundations: Freedom,title="Four Foundations: Freedom"] - -We are dedicated to free software and content. - -Advancing software and content freedom is a central community goal, -which we accomplish through the software and content we promote. We -choose free alternatives to proprietary code and content and limit the -effects of proprietary or patent encumbered code on the Project. - -Sometimes this goal prevents us from taking the easy way out by -including proprietary or patent encumbered software in Fedora. But by -concentrating on the free software and content we provide and promote, -the end result is that we are able to provide: - -* releases that are predictable and 100% legally redistributable for -everyone; -* innovation in free and open source software that can equal or exceed -closed source or proprietary solutions; -* and, a completely free project that anyone can emulate or copy in -whole or in part for their own purposes. - - -|Friends -~~~~~~~ - -image:divider-top-friends.png[Four Foundations: Friends,title="Four Foundations: Friends"] - -We are a strong, caring community. - -image:photo-friends.png[] - -The Fedora community is made up of people from all walks of life, -working together to advance free software. There is a place in Fedora -for https://whatcanidoforfedora.org/[anyone who wants to help], -regardless of technical skill level, as long as they believe in our core -values. - -Like any friends, we occasionally disagree on details, but we believe in -finding an acceptable consensus to serve the interests of advancing free -software. We believe in a strong partnership between Red Hat and our -enormous volunteer community, since they both provide essential -contributions that help the Fedora Project succeed. - -^|image:divider-bottom-freedom.png[] -^|image:divider-bottom-friends.png[] - -|Features -~~~~~~~~ - -image:divider-top-features.png[Four Foundations: Features,title="Four Foundations: Features"] - -We care about excellent software. - -The Fedora community creates many of the technical features that have -made Linux powerful, flexible, and usable for a wide spectrum of -millions of users, administrators, and developers worldwide. We -recognize the status quo is worth changing to empower additional -end-users, or to create a more flexible and powerful environment for -building new solutions on the free software we provide. - -We also believe that these changes are best developed in direct concert with -the https://fedoraproject.org/wiki/Staying_close_to_upstream_projects[upstream -software communities] whose work is part of the Fedora distribution. We work -with the upstream in cases where we find opportunities for improvement, so -all free software users benefit — even if they don’t use Fedora directly. -Our feature development is always done openly and transparently, and anyone -may participate. - - -|First -~~~~~ - -image:divider-top-first.png[Four Foundations: First,title="Four Foundations: First"] - - -We are committed to innovation. - -We are not content to let others do all the heavy lifting on our behalf; -we provide the latest in stable and robust, useful, and powerful free -software in our Fedora distribution. - -At any point in time, the latest Fedora platform shows the future -direction of the operating system as it is experienced by everyone from -the home desktop user to the enterprise business customer. Our -https://fedoraproject.org/wiki/Releases[rapid release cycle] is a major enabling factor in our -ability to innovate. - -We recognize that there is also a place for long-term stability in the -Linux ecosystem, and that there are a variety of community-oriented and -business-oriented Linux distributions available to serve that need. -However, the Fedora Project's goal of advancing free software dictates -that the Fedora Project itself pursue a strategy that preserves the -forward momentum of our technical, collateral, and community-building -progress. Fedora always aims to provide the future, first. - -^|image:divider-bottom-first.png[] -^|image:divider-bottom-features.png[] - -|=== - -Our Mission ------------ - -____ -_Fedora creates an innovative platform for hardware, clouds, and -containers that enables software developers and community members to -build tailored solutions for their users._ -____ - -At the operating system level, we don’t just integrate. We do new things -— we build a _platform_, not just a distribution. The _Features_ and -_First_ foundations drive us to innovate. We do all of this as a -transparent, collaborative community of _Friends_, and entirely as open -source and free software — _Freedom_. - - -Our Method ----------- - -The Fedora Project is a center for innovation in free and open source -software. In our community,contributors of all kinds come together to -advance the ecosystem for the benefit of everyone. The Fedora community -contributes everything it builds back to the free and open source world -and continues to make advances of significance to the broader community, -as evidenced by the regular and rapid incorporation of its features into -other Linux distributions. Regardless of which Linux distribution you -use, you are relying on code developed within the Fedora Project. - -We believe https://fedoraproject.org/wiki/Software_Patents[software patents] -are harmful, a hindrance to innovation in software development, and are -inconsistent with the values of free and open source software. While tightly -integrating proprietary and patent encumbered components might superficially -improve ease of use, this practice does not benefit the community in the -long run. The Fedora community prefers approaches that benefit the progress -of free software in the future over those that emphasize short term ease of -use. - - -Our Community -------------- - -Fedora is more than just software. It is a community of contributors -from https://fedoracommunity.org/[around the world], including volunteers -and Red Hat employees, who work with each other to advance the interests -of the free culture movement. Everyone is invited to join. No matter -what your skills are, we have a place for you in our community! We are -https://fedoraproject.org/wiki/PackageMaintainers[software engineers], https://fedoraproject.org/wiki/Design[designers and artists], -https://fedoraproject.org/wiki/Infrastructure[system administrators], https://fedoraproject.org/wiki/Websites[web -designers], https://fedoraproject.org/wiki/DocsProject[writers], https://fedoraproject.org/wiki/Ambassadors[speakers], -https://fedoraproject.org/wiki/G11N[translators], and more — and we are happy to help you get -started. - -We believe that all contributors should -https://fedoraproject.org/code-of-conduct[be excellent to each other]. -By creating an environment for constructive contribution, we can more -effectively and successfully compare and challenge different ideas to -find the best solutions for advancement, while building the size, -diversity, and strength of our community. - - -Leadership and Governance -------------------------- - -The https://fedoraproject.org/wiki/../council/charter.html[Fedora Council] is responsible for -stewardship of the Fedora Project as a whole, and supports the health and -growth of the Fedora Community. As in any large project, there are many -different levels of responsibility, accountability, and decision-making. As -a general rule, we want people working on a Fedora -https://fedoraproject.org/wiki/Subprojects[subproject] to be make meaningful decisions about their -areas of interest and expertise. More details are available on our page on -https://fedoraproject.org/wiki/Leadership[Fedora Leadership]. - - diff --git a/project/help.adoc b/project/help.adoc deleted file mode 100644 index 8cf642d..0000000 --- a/project/help.adoc +++ /dev/null @@ -1,10 +0,0 @@ -[NOTE] -==== -This page is a placeholder. It should have content adopted from -https://fedoraproject.org/wiki/Communicating_and_getting_help -but ideally made to be less scary. - -You can help make this document more useful by submitting changes via pull -request at https://pagure.io/Fedora-Council/council-docs - -==== \ No newline at end of file diff --git a/project/images/4Foundations-features100px.png b/project/images/4Foundations-features100px.png deleted file mode 100644 index c54d6a9..0000000 Binary files a/project/images/4Foundations-features100px.png and /dev/null differ diff --git a/project/images/4Foundations-first100px.png b/project/images/4Foundations-first100px.png deleted file mode 100644 index da7f5ce..0000000 Binary files a/project/images/4Foundations-first100px.png and /dev/null differ diff --git a/project/images/4Foundations-freedom100px.png b/project/images/4Foundations-freedom100px.png deleted file mode 100644 index bd2be3a..0000000 Binary files a/project/images/4Foundations-freedom100px.png and /dev/null differ diff --git a/project/images/4Foundations-friends100px.png b/project/images/4Foundations-friends100px.png deleted file mode 100644 index c3c21af..0000000 Binary files a/project/images/4Foundations-friends100px.png and /dev/null differ diff --git a/project/images/banner-colorblock-icons-4up.png b/project/images/banner-colorblock-icons-4up.png deleted file mode 100644 index dec3d12..0000000 Binary files a/project/images/banner-colorblock-icons-4up.png and /dev/null differ diff --git a/project/images/banner-colorblock-photos-4up.png b/project/images/banner-colorblock-photos-4up.png deleted file mode 100644 index fc14f20..0000000 Binary files a/project/images/banner-colorblock-photos-4up.png and /dev/null differ diff --git a/project/images/banner-getfedora_horiz.png b/project/images/banner-getfedora_horiz.png deleted file mode 100644 index 60cabf8..0000000 Binary files a/project/images/banner-getfedora_horiz.png and /dev/null differ diff --git a/project/images/banner-getfedora_sq.png b/project/images/banner-getfedora_sq.png deleted file mode 100644 index 7dc528f..0000000 Binary files a/project/images/banner-getfedora_sq.png and /dev/null differ diff --git a/project/images/colorblock-features.png b/project/images/colorblock-features.png deleted file mode 100644 index 66c386e..0000000 Binary files a/project/images/colorblock-features.png and /dev/null differ diff --git a/project/images/colorblock-first.png b/project/images/colorblock-first.png deleted file mode 100644 index 3ebe017..0000000 Binary files a/project/images/colorblock-first.png and /dev/null differ diff --git a/project/images/colorblock-freedom.png b/project/images/colorblock-freedom.png deleted file mode 100644 index 230575d..0000000 Binary files a/project/images/colorblock-freedom.png and /dev/null differ diff --git a/project/images/colorblock-friends.png b/project/images/colorblock-friends.png deleted file mode 100644 index 2a28bdf..0000000 Binary files a/project/images/colorblock-friends.png and /dev/null differ diff --git a/project/images/colorblock-iconphoto-features.png b/project/images/colorblock-iconphoto-features.png deleted file mode 100644 index 75aeb31..0000000 Binary files a/project/images/colorblock-iconphoto-features.png and /dev/null differ diff --git a/project/images/colorblock-iconphoto-first.png b/project/images/colorblock-iconphoto-first.png deleted file mode 100644 index b839516..0000000 Binary files a/project/images/colorblock-iconphoto-first.png and /dev/null differ diff --git a/project/images/colorblock-iconphoto-freedom.png b/project/images/colorblock-iconphoto-freedom.png deleted file mode 100644 index 2b72f83..0000000 Binary files a/project/images/colorblock-iconphoto-freedom.png and /dev/null differ diff --git a/project/images/colorblock-iconphoto-friends.png b/project/images/colorblock-iconphoto-friends.png deleted file mode 100644 index 494882b..0000000 Binary files a/project/images/colorblock-iconphoto-friends.png and /dev/null differ diff --git a/project/images/colorblock-iconphototext-features.png b/project/images/colorblock-iconphototext-features.png deleted file mode 100644 index 6f2cd88..0000000 Binary files a/project/images/colorblock-iconphototext-features.png and /dev/null differ diff --git a/project/images/colorblock-iconphototext-first.png b/project/images/colorblock-iconphototext-first.png deleted file mode 100644 index 4de9385..0000000 Binary files a/project/images/colorblock-iconphototext-first.png and /dev/null differ diff --git a/project/images/colorblock-iconphototext-freedom.png b/project/images/colorblock-iconphototext-freedom.png deleted file mode 100644 index 2344fe2..0000000 Binary files a/project/images/colorblock-iconphototext-freedom.png and /dev/null differ diff --git a/project/images/colorblock-iconphototext-friends.png b/project/images/colorblock-iconphototext-friends.png deleted file mode 100644 index db3680a..0000000 Binary files a/project/images/colorblock-iconphototext-friends.png and /dev/null differ diff --git a/project/images/colorblock-icons-features.png b/project/images/colorblock-icons-features.png deleted file mode 100644 index c60d0ca..0000000 Binary files a/project/images/colorblock-icons-features.png and /dev/null differ diff --git a/project/images/colorblock-icons-first.png b/project/images/colorblock-icons-first.png deleted file mode 100644 index 68ebe07..0000000 Binary files a/project/images/colorblock-icons-first.png and /dev/null differ diff --git a/project/images/colorblock-icons-freedom.png b/project/images/colorblock-icons-freedom.png deleted file mode 100644 index edacfd9..0000000 Binary files a/project/images/colorblock-icons-freedom.png and /dev/null differ diff --git a/project/images/colorblock-icons-friends.png b/project/images/colorblock-icons-friends.png deleted file mode 100644 index 0bea8c0..0000000 Binary files a/project/images/colorblock-icons-friends.png and /dev/null differ diff --git a/project/images/commmunity-horiz.png b/project/images/commmunity-horiz.png deleted file mode 100644 index c4365b7..0000000 Binary files a/project/images/commmunity-horiz.png and /dev/null differ diff --git a/project/images/community-square.png b/project/images/community-square.png deleted file mode 100644 index 59f8ea5..0000000 Binary files a/project/images/community-square.png and /dev/null differ diff --git a/project/images/council-badge.png b/project/images/council-badge.png deleted file mode 100644 index 5e0399d..0000000 Binary files a/project/images/council-badge.png and /dev/null differ diff --git a/project/images/divider-bottom-features.png b/project/images/divider-bottom-features.png deleted file mode 100644 index 81147e8..0000000 Binary files a/project/images/divider-bottom-features.png and /dev/null differ diff --git a/project/images/divider-bottom-first.png b/project/images/divider-bottom-first.png deleted file mode 100644 index 9a7f75a..0000000 Binary files a/project/images/divider-bottom-first.png and /dev/null differ diff --git a/project/images/divider-bottom-freedom.png b/project/images/divider-bottom-freedom.png deleted file mode 100644 index fddd97d..0000000 Binary files a/project/images/divider-bottom-freedom.png and /dev/null differ diff --git a/project/images/divider-bottom-friends.png b/project/images/divider-bottom-friends.png deleted file mode 100644 index ac413a4..0000000 Binary files a/project/images/divider-bottom-friends.png and /dev/null differ diff --git a/project/images/divider-top-features.png b/project/images/divider-top-features.png deleted file mode 100644 index 92bd46f..0000000 Binary files a/project/images/divider-top-features.png and /dev/null differ diff --git a/project/images/divider-top-first.png b/project/images/divider-top-first.png deleted file mode 100644 index ab4bc51..0000000 Binary files a/project/images/divider-top-first.png and /dev/null differ diff --git a/project/images/divider-top-freedom.png b/project/images/divider-top-freedom.png deleted file mode 100644 index a672c5a..0000000 Binary files a/project/images/divider-top-freedom.png and /dev/null differ diff --git a/project/images/divider-top-friends.png b/project/images/divider-top-friends.png deleted file mode 100644 index 30c31bd..0000000 Binary files a/project/images/divider-top-friends.png and /dev/null differ diff --git a/project/images/fedora-logo.png b/project/images/fedora-logo.png deleted file mode 100644 index 39b6c91..0000000 Binary files a/project/images/fedora-logo.png and /dev/null differ diff --git a/project/images/fesco-badge.png b/project/images/fesco-badge.png deleted file mode 100644 index 93ed858..0000000 Binary files a/project/images/fesco-badge.png and /dev/null differ diff --git a/project/images/modularity-badge.png b/project/images/modularity-badge.png deleted file mode 100644 index 076394d..0000000 Binary files a/project/images/modularity-badge.png and /dev/null differ diff --git a/project/images/orgchart.mm b/project/images/orgchart.mm deleted file mode 100644 index 567defb..0000000 --- a/project/images/orgchart.mm +++ /dev/null @@ -1,368 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/project/images/orgchart.png b/project/images/orgchart.png deleted file mode 100644 index 2621ec5..0000000 Binary files a/project/images/orgchart.png and /dev/null differ diff --git a/project/images/orgchart.txt b/project/images/orgchart.txt deleted file mode 100644 index ff4f1aa..0000000 --- a/project/images/orgchart.txt +++ /dev/null @@ -1,92 +0,0 @@ -**Fedora Council** - Objectives - Fedora CI - Modularity - Internet of Things - Mindshare - Ambassadors - LATAM - NA - EMEA - APAC - Ambassadors Membership Administration (FAmA) - Join Fedora - Classroom - Documentation - Design - Badges - Wallpapers - Web - Marketing Execution - Social Media - Magazine - Ask Fedora - IRC Support - CommOps - Community Blog - Globalization - Language Test Group - Internationalization - Translations - Zanata - Diversity & Inclusion - Fedora Women - Outreachy - Fedora Engineering Steering Committee (FESCo) - - Spins - Cinnamon - KDE - Xfce - Sugar on a Stick - Mate-Compiz - LXDE - LXQt - Fedora EPEL - Copr - Fedora Editions - Fedora Workstation Working Group - Fedora Atomic Working Group - Fedora Server Working Group - Fedora Packagers - Packaging Committee (FPC) - Proven Packagers - Kernel - Sponsors - Infrastructure - Apps - Apprentices - Sysadmins - Release Engineering - Programming Language SIGs - PHP - Ruby - Perl - Python - Java - Go - Rust - DotNet - Erlang - Quality Assurance - Security - Fedora Red Team - Alternate Architectures - x86-32 - s390x - ARM - POWER - RISC-V - Other Technical SIGS - SELinux - Big Data - Astronomy - Gaming SIG - Cloud SIG - Fonts SIG - Amateur Radio - Machine Learning - Robotics - Atomic Workstation - 3D Printing - Audio \ No newline at end of file diff --git a/project/images/photo-friends.png b/project/images/photo-friends.png deleted file mode 100644 index 269e6c8..0000000 Binary files a/project/images/photo-friends.png and /dev/null differ diff --git a/project/images/photo-laptop.png b/project/images/photo-laptop.png deleted file mode 100644 index 97458a4..0000000 Binary files a/project/images/photo-laptop.png and /dev/null differ diff --git a/project/join.adoc b/project/join.adoc deleted file mode 100644 index 76aee6d..0000000 --- a/project/join.adoc +++ /dev/null @@ -1,9 +0,0 @@ -[NOTE] -==== -This page is a placeholder. It should have content adopted from -https://fedoraproject.org/wiki/Join - -You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - -==== \ No newline at end of file diff --git a/project/leadership.adoc b/project/leadership.adoc deleted file mode 100644 index deb38d2..0000000 --- a/project/leadership.adoc +++ /dev/null @@ -1,67 +0,0 @@ -= Fedora Leadership - -The Fedora Project is led by contributors from across the community. -Different functional areas of Fedora at times evolve, build, or dismantle their own formal (or informal!) leadership over time. -Because Fedora is an open source project, we encourage new contributors to identify problems, find solutions, and collaborate with other members to achieve results. -Our community recognizes and empowers able leaders from among our peers. - -The Fedora Project aims to have a thin layer of governance that enables decision making without excessive drag. - - -The following are current examples of _leadership groups_ in Fedora. - -== Fedora Council == -image::council-badge.png[float="right",50%] - -The https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is the topmost governance and leadership body in Fedora, and is made up of appointed and elected members from across the Fedora community. -Details about the Council such as size, constitution, and succession planning are found in the https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council Charter]. - -The https://docs.fedoraproject.org/fedora-project/council/fpl.html[Fedora Project Leader] (or "FPL") serves as the chair of the Council. - - -== Fedora Engineering Steering Committee == -image::fesco-badge.png[float="right",50%] - -The https://docs.fedoraproject.org/fedora-project/subprojects/fesco.html[Fedora Engineering Steering Committee] (commonly known as "FESCo") is a community-elected body empowered by the Council to manage the technical features of the Fedora distribution and specific implementations of policy in the Fedora Project. -You can find further information about FESCo, its members, and its policies on the https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo wiki pages]. - - -== Fedora Mindshare Committee == - -The https://docs.fedoraproject.org/fedora-project/subprojects/mindshare.html[Mindshare Committee] represents leadership for user and contributor community growth and support. - - -== Other groups == - -The list above is not a complete list of every group of empowered community members. -Other groups steer specific parts of Fedora as well, empowered and supported by the relevant teams. -The list above shows the three leadership groups that most often work on issues of policy or practice affecting large portions of the Fedora Project. - -Community members are always encouraged to get involved in leading Fedora in ways that are important to them, while minimizing overhead and governance project-wide. - - -=== Working Groups === - -Fedora https://fedoraproject.org/wiki/Editions[Editions] — currently, -https://fedoraproject.org/wiki/Atomic_WG[Atomic], -https://fedoraproject.org/wiki/Server[Server], -and -https://fedoraproject.org/wiki/Workstation[Workstation], -— and sometimes Fedora Project Objectives are lead by _Working Groups_. -These groups are either independent subcommittees of FESCo, Mindshare, or the Council. -They have formal membership and decision-making processes, but generally the membership is intended to include active contributors and the decision-making power reflects that. -A seat on the Working Group itself is _not at all_ required to participate meaningfully in the work on Editions or Objectives. - - -=== Subprojects === - -https://docs.fedoraproject.org/fedora-project/subprojects/subprojects.html[Subprojects] are long-standing major areas of effort under the overall Fedora umbrella. -Each subproject has its own governance. - - -=== Special Interest Groups === - -https://docs.fedoraproject.org/fedora-project/subprojects/sigs.html[Special Interest Groups], or "SIGs", are much less formal. -The process for https://fedoraproject.org/wiki/Creating_a_Fedora_SIG[creating a SIG] has *no red tape*. -Different SIGs have different structures; some use formalized voting and others don't. -Some SIGs may eventually become subprojects; for others, the lightweight framework is perfect. diff --git a/project/modules/ROOT/assets/images/4Foundations-features100px.png b/project/modules/ROOT/assets/images/4Foundations-features100px.png new file mode 100644 index 0000000..c54d6a9 Binary files /dev/null and b/project/modules/ROOT/assets/images/4Foundations-features100px.png differ diff --git a/project/modules/ROOT/assets/images/4Foundations-first100px.png b/project/modules/ROOT/assets/images/4Foundations-first100px.png new file mode 100644 index 0000000..da7f5ce Binary files /dev/null and b/project/modules/ROOT/assets/images/4Foundations-first100px.png differ diff --git a/project/modules/ROOT/assets/images/4Foundations-freedom100px.png b/project/modules/ROOT/assets/images/4Foundations-freedom100px.png new file mode 100644 index 0000000..bd2be3a Binary files /dev/null and b/project/modules/ROOT/assets/images/4Foundations-freedom100px.png differ diff --git a/project/modules/ROOT/assets/images/4Foundations-friends100px.png b/project/modules/ROOT/assets/images/4Foundations-friends100px.png new file mode 100644 index 0000000..c3c21af Binary files /dev/null and b/project/modules/ROOT/assets/images/4Foundations-friends100px.png differ diff --git a/project/modules/ROOT/assets/images/banner-colorblock-icons-4up.png b/project/modules/ROOT/assets/images/banner-colorblock-icons-4up.png new file mode 100644 index 0000000..dec3d12 Binary files /dev/null and b/project/modules/ROOT/assets/images/banner-colorblock-icons-4up.png differ diff --git a/project/modules/ROOT/assets/images/banner-colorblock-photos-4up.png b/project/modules/ROOT/assets/images/banner-colorblock-photos-4up.png new file mode 100644 index 0000000..fc14f20 Binary files /dev/null and b/project/modules/ROOT/assets/images/banner-colorblock-photos-4up.png differ diff --git a/project/modules/ROOT/assets/images/banner-getfedora_horiz.png b/project/modules/ROOT/assets/images/banner-getfedora_horiz.png new file mode 100644 index 0000000..60cabf8 Binary files /dev/null and b/project/modules/ROOT/assets/images/banner-getfedora_horiz.png differ diff --git a/project/modules/ROOT/assets/images/banner-getfedora_sq.png b/project/modules/ROOT/assets/images/banner-getfedora_sq.png new file mode 100644 index 0000000..7dc528f Binary files /dev/null and b/project/modules/ROOT/assets/images/banner-getfedora_sq.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-features.png b/project/modules/ROOT/assets/images/colorblock-features.png new file mode 100644 index 0000000..66c386e Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-features.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-first.png b/project/modules/ROOT/assets/images/colorblock-first.png new file mode 100644 index 0000000..3ebe017 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-first.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-freedom.png b/project/modules/ROOT/assets/images/colorblock-freedom.png new file mode 100644 index 0000000..230575d Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-freedom.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-friends.png b/project/modules/ROOT/assets/images/colorblock-friends.png new file mode 100644 index 0000000..2a28bdf Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-friends.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphoto-features.png b/project/modules/ROOT/assets/images/colorblock-iconphoto-features.png new file mode 100644 index 0000000..75aeb31 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphoto-features.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphoto-first.png b/project/modules/ROOT/assets/images/colorblock-iconphoto-first.png new file mode 100644 index 0000000..b839516 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphoto-first.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphoto-freedom.png b/project/modules/ROOT/assets/images/colorblock-iconphoto-freedom.png new file mode 100644 index 0000000..2b72f83 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphoto-freedom.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphoto-friends.png b/project/modules/ROOT/assets/images/colorblock-iconphoto-friends.png new file mode 100644 index 0000000..494882b Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphoto-friends.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphototext-features.png b/project/modules/ROOT/assets/images/colorblock-iconphototext-features.png new file mode 100644 index 0000000..6f2cd88 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphototext-features.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphototext-first.png b/project/modules/ROOT/assets/images/colorblock-iconphototext-first.png new file mode 100644 index 0000000..4de9385 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphototext-first.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphototext-freedom.png b/project/modules/ROOT/assets/images/colorblock-iconphototext-freedom.png new file mode 100644 index 0000000..2344fe2 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphototext-freedom.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-iconphototext-friends.png b/project/modules/ROOT/assets/images/colorblock-iconphototext-friends.png new file mode 100644 index 0000000..db3680a Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-iconphototext-friends.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-icons-features.png b/project/modules/ROOT/assets/images/colorblock-icons-features.png new file mode 100644 index 0000000..c60d0ca Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-icons-features.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-icons-first.png b/project/modules/ROOT/assets/images/colorblock-icons-first.png new file mode 100644 index 0000000..68ebe07 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-icons-first.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-icons-freedom.png b/project/modules/ROOT/assets/images/colorblock-icons-freedom.png new file mode 100644 index 0000000..edacfd9 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-icons-freedom.png differ diff --git a/project/modules/ROOT/assets/images/colorblock-icons-friends.png b/project/modules/ROOT/assets/images/colorblock-icons-friends.png new file mode 100644 index 0000000..0bea8c0 Binary files /dev/null and b/project/modules/ROOT/assets/images/colorblock-icons-friends.png differ diff --git a/project/modules/ROOT/assets/images/commmunity-horiz.png b/project/modules/ROOT/assets/images/commmunity-horiz.png new file mode 100644 index 0000000..c4365b7 Binary files /dev/null and b/project/modules/ROOT/assets/images/commmunity-horiz.png differ diff --git a/project/modules/ROOT/assets/images/community-square.png b/project/modules/ROOT/assets/images/community-square.png new file mode 100644 index 0000000..59f8ea5 Binary files /dev/null and b/project/modules/ROOT/assets/images/community-square.png differ diff --git a/project/modules/ROOT/assets/images/council-badge.png b/project/modules/ROOT/assets/images/council-badge.png new file mode 100644 index 0000000..5e0399d Binary files /dev/null and b/project/modules/ROOT/assets/images/council-badge.png differ diff --git a/project/modules/ROOT/assets/images/divider-bottom-features.png b/project/modules/ROOT/assets/images/divider-bottom-features.png new file mode 100644 index 0000000..81147e8 Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-bottom-features.png differ diff --git a/project/modules/ROOT/assets/images/divider-bottom-first.png b/project/modules/ROOT/assets/images/divider-bottom-first.png new file mode 100644 index 0000000..9a7f75a Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-bottom-first.png differ diff --git a/project/modules/ROOT/assets/images/divider-bottom-freedom.png b/project/modules/ROOT/assets/images/divider-bottom-freedom.png new file mode 100644 index 0000000..fddd97d Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-bottom-freedom.png differ diff --git a/project/modules/ROOT/assets/images/divider-bottom-friends.png b/project/modules/ROOT/assets/images/divider-bottom-friends.png new file mode 100644 index 0000000..ac413a4 Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-bottom-friends.png differ diff --git a/project/modules/ROOT/assets/images/divider-top-features.png b/project/modules/ROOT/assets/images/divider-top-features.png new file mode 100644 index 0000000..92bd46f Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-top-features.png differ diff --git a/project/modules/ROOT/assets/images/divider-top-first.png b/project/modules/ROOT/assets/images/divider-top-first.png new file mode 100644 index 0000000..ab4bc51 Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-top-first.png differ diff --git a/project/modules/ROOT/assets/images/divider-top-freedom.png b/project/modules/ROOT/assets/images/divider-top-freedom.png new file mode 100644 index 0000000..a672c5a Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-top-freedom.png differ diff --git a/project/modules/ROOT/assets/images/divider-top-friends.png b/project/modules/ROOT/assets/images/divider-top-friends.png new file mode 100644 index 0000000..30c31bd Binary files /dev/null and b/project/modules/ROOT/assets/images/divider-top-friends.png differ diff --git a/project/modules/ROOT/assets/images/fedora-logo.png b/project/modules/ROOT/assets/images/fedora-logo.png new file mode 100644 index 0000000..39b6c91 Binary files /dev/null and b/project/modules/ROOT/assets/images/fedora-logo.png differ diff --git a/project/modules/ROOT/assets/images/fesco-badge.png b/project/modules/ROOT/assets/images/fesco-badge.png new file mode 100644 index 0000000..93ed858 Binary files /dev/null and b/project/modules/ROOT/assets/images/fesco-badge.png differ diff --git a/project/modules/ROOT/assets/images/modularity-badge.png b/project/modules/ROOT/assets/images/modularity-badge.png new file mode 100644 index 0000000..076394d Binary files /dev/null and b/project/modules/ROOT/assets/images/modularity-badge.png differ diff --git a/project/modules/ROOT/assets/images/orgchart.mm b/project/modules/ROOT/assets/images/orgchart.mm new file mode 100644 index 0000000..567defb --- /dev/null +++ b/project/modules/ROOT/assets/images/orgchart.mm @@ -0,0 +1,368 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/project/modules/ROOT/assets/images/orgchart.png b/project/modules/ROOT/assets/images/orgchart.png new file mode 100644 index 0000000..2621ec5 Binary files /dev/null and b/project/modules/ROOT/assets/images/orgchart.png differ diff --git a/project/modules/ROOT/assets/images/orgchart.txt b/project/modules/ROOT/assets/images/orgchart.txt new file mode 100644 index 0000000..ff4f1aa --- /dev/null +++ b/project/modules/ROOT/assets/images/orgchart.txt @@ -0,0 +1,92 @@ +**Fedora Council** + Objectives + Fedora CI + Modularity + Internet of Things + Mindshare + Ambassadors + LATAM + NA + EMEA + APAC + Ambassadors Membership Administration (FAmA) + Join Fedora + Classroom + Documentation + Design + Badges + Wallpapers + Web + Marketing Execution + Social Media + Magazine + Ask Fedora + IRC Support + CommOps + Community Blog + Globalization + Language Test Group + Internationalization + Translations + Zanata + Diversity & Inclusion + Fedora Women + Outreachy + Fedora Engineering Steering Committee (FESCo) + + Spins + Cinnamon + KDE + Xfce + Sugar on a Stick + Mate-Compiz + LXDE + LXQt + Fedora EPEL + Copr + Fedora Editions + Fedora Workstation Working Group + Fedora Atomic Working Group + Fedora Server Working Group + Fedora Packagers + Packaging Committee (FPC) + Proven Packagers + Kernel + Sponsors + Infrastructure + Apps + Apprentices + Sysadmins + Release Engineering + Programming Language SIGs + PHP + Ruby + Perl + Python + Java + Go + Rust + DotNet + Erlang + Quality Assurance + Security + Fedora Red Team + Alternate Architectures + x86-32 + s390x + ARM + POWER + RISC-V + Other Technical SIGS + SELinux + Big Data + Astronomy + Gaming SIG + Cloud SIG + Fonts SIG + Amateur Radio + Machine Learning + Robotics + Atomic Workstation + 3D Printing + Audio \ No newline at end of file diff --git a/project/modules/ROOT/assets/images/photo-friends.png b/project/modules/ROOT/assets/images/photo-friends.png new file mode 100644 index 0000000..269e6c8 Binary files /dev/null and b/project/modules/ROOT/assets/images/photo-friends.png differ diff --git a/project/modules/ROOT/assets/images/photo-laptop.png b/project/modules/ROOT/assets/images/photo-laptop.png new file mode 100644 index 0000000..97458a4 Binary files /dev/null and b/project/modules/ROOT/assets/images/photo-laptop.png differ diff --git a/project/modules/ROOT/nav.adoc b/project/modules/ROOT/nav.adoc new file mode 100644 index 0000000..9e08e45 --- /dev/null +++ b/project/modules/ROOT/nav.adoc @@ -0,0 +1,7 @@ +* xref:index.adoc[Mission and Foundations] +* xref:leadership.adoc[Leadership] +* xref:objectives.adoc[Current Objectives] +* xref:orgchart.adoc[High-Level Organization] +* xref:code-of-conduct.adoc[Code of Conduct] +* xref:help.adoc[Get Help] +* xref:join.adoc[Get Involved] diff --git a/project/modules/ROOT/pages/code-of-conduct.adoc b/project/modules/ROOT/pages/code-of-conduct.adoc new file mode 100644 index 0000000..4c4c665 --- /dev/null +++ b/project/modules/ROOT/pages/code-of-conduct.adoc @@ -0,0 +1,28 @@ +Code of Conduct +=============== + +The Fedora community is made up of a mixture of professionals and volunteers +from all over the world, working on every aspect of the distribution from +coding through to marketing. Diversity is one of our huge strengths, but it +can also lead to communication issues and unhappiness. To that end, we have +a few ground rules that we ask people to adhere to when they're using +project resources. + +This isn't an exhaustive list of things that you can't do. Rather, take it +in the spirit in which it's intended - a guide to make it easier to be +excellent to each other. + +* Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. + +* Be respectful. Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Fedora community should be respectful when dealing with other contributors as well as with people outside the Fedora community and with users of Fedora. + +When we disagree, we try to understand why. Disagreements, both social and +technical, happen all the time and Fedora is no exception. It is important +that we resolve disagreements and differing views constructively. + +Remember that we're different. The strength of Fedora comes from its varied +community, people from a wide range of backgrounds. Different people have +different perspectives on issues. Being unable to understand why someone +holds a viewpoint doesn't mean that they're wrong. Don't forget that it is +human to err and blaming each other doesn't get us anywhere, rather offer to +help resolving issues and to help learn from mistakes. diff --git a/project/modules/ROOT/pages/help.adoc b/project/modules/ROOT/pages/help.adoc new file mode 100644 index 0000000..8cf642d --- /dev/null +++ b/project/modules/ROOT/pages/help.adoc @@ -0,0 +1,10 @@ +[NOTE] +==== +This page is a placeholder. It should have content adopted from +https://fedoraproject.org/wiki/Communicating_and_getting_help +but ideally made to be less scary. + +You can help make this document more useful by submitting changes via pull +request at https://pagure.io/Fedora-Council/council-docs + +==== \ No newline at end of file diff --git a/project/modules/ROOT/pages/index.adoc b/project/modules/ROOT/pages/index.adoc new file mode 100644 index 0000000..8d59f1a --- /dev/null +++ b/project/modules/ROOT/pages/index.adoc @@ -0,0 +1,219 @@ +Fedora's Mission and Foundations +================================ + +.How do I get the software? +[[getfedora]] +[sidebar.width50] +**** +image:banner-getfedora_sq.png[Get Fedora,title="getfedora.org",float="right",role="pl-2",link=https://getfedora.org/] + +Download one of the different editions of Fedora for your laptop/desktop, +server, or containers at https://getfedora.org[Get Fedora], or explore other +options provided by https://labs.fedoraproject.org/[Labs], +https://spins.fedoraproject.org/[Spins], +https://arm.fedoraproject.org/[ARM], and +https://alt.fedoraproject.org/[Alternative Downloads]. + +Everything included is open source and free software — not only is it +available at no cost to you, but you can share, remix, and modify. +**** + +What is Fedora? +--------------- + +[.lead] +The Fedora Project is a community of people working together to build a +free and open source software platform and to collaborate on and share +user-focused solutions built on that platform. Or, in plain English, we +make an operating system and we make it easy for you do useful stuff +with it. + + +<<< + + +What is Fedora all about? +------------------------- + +The Fedora community includes thousands of individuals with different +views and approaches, but together we share some common values. We call +these the “*Four Foundations*”: Freedom, Friends, Features, and First. + +[cols="1a,1a",frame=none,grid=none,nostriping] +|=== +|Freedom +~~~~~~~ + +image:divider-top-freedom.png[Four Foundations: Freedom,title="Four Foundations: Freedom"] + +We are dedicated to free software and content. + +Advancing software and content freedom is a central community goal, +which we accomplish through the software and content we promote. We +choose free alternatives to proprietary code and content and limit the +effects of proprietary or patent encumbered code on the Project. + +Sometimes this goal prevents us from taking the easy way out by +including proprietary or patent encumbered software in Fedora. But by +concentrating on the free software and content we provide and promote, +the end result is that we are able to provide: + +* releases that are predictable and 100% legally redistributable for +everyone; +* innovation in free and open source software that can equal or exceed +closed source or proprietary solutions; +* and, a completely free project that anyone can emulate or copy in +whole or in part for their own purposes. + + +|Friends +~~~~~~~ + +image:divider-top-friends.png[Four Foundations: Friends,title="Four Foundations: Friends"] + +We are a strong, caring community. + +image:photo-friends.png[] + +The Fedora community is made up of people from all walks of life, +working together to advance free software. There is a place in Fedora +for https://whatcanidoforfedora.org/[anyone who wants to help], +regardless of technical skill level, as long as they believe in our core +values. + +Like any friends, we occasionally disagree on details, but we believe in +finding an acceptable consensus to serve the interests of advancing free +software. We believe in a strong partnership between Red Hat and our +enormous volunteer community, since they both provide essential +contributions that help the Fedora Project succeed. + +^|image:divider-bottom-freedom.png[] +^|image:divider-bottom-friends.png[] + +|Features +~~~~~~~~ + +image:divider-top-features.png[Four Foundations: Features,title="Four Foundations: Features"] + +We care about excellent software. + +The Fedora community creates many of the technical features that have +made Linux powerful, flexible, and usable for a wide spectrum of +millions of users, administrators, and developers worldwide. We +recognize the status quo is worth changing to empower additional +end-users, or to create a more flexible and powerful environment for +building new solutions on the free software we provide. + +We also believe that these changes are best developed in direct concert with +the https://fedoraproject.org/wiki/Staying_close_to_upstream_projects[upstream +software communities] whose work is part of the Fedora distribution. We work +with the upstream in cases where we find opportunities for improvement, so +all free software users benefit — even if they don’t use Fedora directly. +Our feature development is always done openly and transparently, and anyone +may participate. + + +|First +~~~~~ + +image:divider-top-first.png[Four Foundations: First,title="Four Foundations: First"] + + +We are committed to innovation. + +We are not content to let others do all the heavy lifting on our behalf; +we provide the latest in stable and robust, useful, and powerful free +software in our Fedora distribution. + +At any point in time, the latest Fedora platform shows the future +direction of the operating system as it is experienced by everyone from +the home desktop user to the enterprise business customer. Our +https://fedoraproject.org/wiki/Releases[rapid release cycle] is a major enabling factor in our +ability to innovate. + +We recognize that there is also a place for long-term stability in the +Linux ecosystem, and that there are a variety of community-oriented and +business-oriented Linux distributions available to serve that need. +However, the Fedora Project's goal of advancing free software dictates +that the Fedora Project itself pursue a strategy that preserves the +forward momentum of our technical, collateral, and community-building +progress. Fedora always aims to provide the future, first. + +^|image:divider-bottom-first.png[] +^|image:divider-bottom-features.png[] + +|=== + +Our Mission +----------- + +____ +_Fedora creates an innovative platform for hardware, clouds, and +containers that enables software developers and community members to +build tailored solutions for their users._ +____ + +At the operating system level, we don’t just integrate. We do new things +— we build a _platform_, not just a distribution. The _Features_ and +_First_ foundations drive us to innovate. We do all of this as a +transparent, collaborative community of _Friends_, and entirely as open +source and free software — _Freedom_. + + +Our Method +---------- + +The Fedora Project is a center for innovation in free and open source +software. In our community,contributors of all kinds come together to +advance the ecosystem for the benefit of everyone. The Fedora community +contributes everything it builds back to the free and open source world +and continues to make advances of significance to the broader community, +as evidenced by the regular and rapid incorporation of its features into +other Linux distributions. Regardless of which Linux distribution you +use, you are relying on code developed within the Fedora Project. + +We believe https://fedoraproject.org/wiki/Software_Patents[software patents] +are harmful, a hindrance to innovation in software development, and are +inconsistent with the values of free and open source software. While tightly +integrating proprietary and patent encumbered components might superficially +improve ease of use, this practice does not benefit the community in the +long run. The Fedora community prefers approaches that benefit the progress +of free software in the future over those that emphasize short term ease of +use. + + +Our Community +------------- + +Fedora is more than just software. It is a community of contributors +from https://fedoracommunity.org/[around the world], including volunteers +and Red Hat employees, who work with each other to advance the interests +of the free culture movement. Everyone is invited to join. No matter +what your skills are, we have a place for you in our community! We are +https://fedoraproject.org/wiki/PackageMaintainers[software engineers], https://fedoraproject.org/wiki/Design[designers and artists], +https://fedoraproject.org/wiki/Infrastructure[system administrators], https://fedoraproject.org/wiki/Websites[web +designers], https://fedoraproject.org/wiki/DocsProject[writers], https://fedoraproject.org/wiki/Ambassadors[speakers], +https://fedoraproject.org/wiki/G11N[translators], and more — and we are happy to help you get +started. + +We believe that all contributors should +https://fedoraproject.org/code-of-conduct[be excellent to each other]. +By creating an environment for constructive contribution, we can more +effectively and successfully compare and challenge different ideas to +find the best solutions for advancement, while building the size, +diversity, and strength of our community. + + +Leadership and Governance +------------------------- + +The https://fedoraproject.org/wiki/../council/charter.html[Fedora Council] is responsible for +stewardship of the Fedora Project as a whole, and supports the health and +growth of the Fedora Community. As in any large project, there are many +different levels of responsibility, accountability, and decision-making. As +a general rule, we want people working on a Fedora +https://fedoraproject.org/wiki/Subprojects[subproject] to be make meaningful decisions about their +areas of interest and expertise. More details are available on our page on +https://fedoraproject.org/wiki/Leadership[Fedora Leadership]. + + diff --git a/project/modules/ROOT/pages/join.adoc b/project/modules/ROOT/pages/join.adoc new file mode 100644 index 0000000..76aee6d --- /dev/null +++ b/project/modules/ROOT/pages/join.adoc @@ -0,0 +1,9 @@ +[NOTE] +==== +This page is a placeholder. It should have content adopted from +https://fedoraproject.org/wiki/Join + +You can help make this document more useful by +submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs + +==== \ No newline at end of file diff --git a/project/modules/ROOT/pages/leadership.adoc b/project/modules/ROOT/pages/leadership.adoc new file mode 100644 index 0000000..deb38d2 --- /dev/null +++ b/project/modules/ROOT/pages/leadership.adoc @@ -0,0 +1,67 @@ += Fedora Leadership + +The Fedora Project is led by contributors from across the community. +Different functional areas of Fedora at times evolve, build, or dismantle their own formal (or informal!) leadership over time. +Because Fedora is an open source project, we encourage new contributors to identify problems, find solutions, and collaborate with other members to achieve results. +Our community recognizes and empowers able leaders from among our peers. + +The Fedora Project aims to have a thin layer of governance that enables decision making without excessive drag. + + +The following are current examples of _leadership groups_ in Fedora. + +== Fedora Council == +image::council-badge.png[float="right",50%] + +The https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is the topmost governance and leadership body in Fedora, and is made up of appointed and elected members from across the Fedora community. +Details about the Council such as size, constitution, and succession planning are found in the https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council Charter]. + +The https://docs.fedoraproject.org/fedora-project/council/fpl.html[Fedora Project Leader] (or "FPL") serves as the chair of the Council. + + +== Fedora Engineering Steering Committee == +image::fesco-badge.png[float="right",50%] + +The https://docs.fedoraproject.org/fedora-project/subprojects/fesco.html[Fedora Engineering Steering Committee] (commonly known as "FESCo") is a community-elected body empowered by the Council to manage the technical features of the Fedora distribution and specific implementations of policy in the Fedora Project. +You can find further information about FESCo, its members, and its policies on the https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo wiki pages]. + + +== Fedora Mindshare Committee == + +The https://docs.fedoraproject.org/fedora-project/subprojects/mindshare.html[Mindshare Committee] represents leadership for user and contributor community growth and support. + + +== Other groups == + +The list above is not a complete list of every group of empowered community members. +Other groups steer specific parts of Fedora as well, empowered and supported by the relevant teams. +The list above shows the three leadership groups that most often work on issues of policy or practice affecting large portions of the Fedora Project. + +Community members are always encouraged to get involved in leading Fedora in ways that are important to them, while minimizing overhead and governance project-wide. + + +=== Working Groups === + +Fedora https://fedoraproject.org/wiki/Editions[Editions] — currently, +https://fedoraproject.org/wiki/Atomic_WG[Atomic], +https://fedoraproject.org/wiki/Server[Server], +and +https://fedoraproject.org/wiki/Workstation[Workstation], +— and sometimes Fedora Project Objectives are lead by _Working Groups_. +These groups are either independent subcommittees of FESCo, Mindshare, or the Council. +They have formal membership and decision-making processes, but generally the membership is intended to include active contributors and the decision-making power reflects that. +A seat on the Working Group itself is _not at all_ required to participate meaningfully in the work on Editions or Objectives. + + +=== Subprojects === + +https://docs.fedoraproject.org/fedora-project/subprojects/subprojects.html[Subprojects] are long-standing major areas of effort under the overall Fedora umbrella. +Each subproject has its own governance. + + +=== Special Interest Groups === + +https://docs.fedoraproject.org/fedora-project/subprojects/sigs.html[Special Interest Groups], or "SIGs", are much less formal. +The process for https://fedoraproject.org/wiki/Creating_a_Fedora_SIG[creating a SIG] has *no red tape*. +Different SIGs have different structures; some use formalized voting and others don't. +Some SIGs may eventually become subprojects; for others, the lightweight framework is perfect. diff --git a/project/modules/ROOT/pages/objectives.adoc b/project/modules/ROOT/pages/objectives.adoc new file mode 100644 index 0000000..b58fd55 --- /dev/null +++ b/project/modules/ROOT/pages/objectives.adoc @@ -0,0 +1,100 @@ += Current 12-18 Month Community Objectives + +== Overview + +The primary role of the https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them. +This section documents the **medium-term** targets we've highlighted (as explained in the Council charter). +Each objective has a designated Objective Lead who is responsible +for coordinating efforts to reach the Objective's goals, +for evaluating and reporting on progress, and +for working regularly with all relevant groups in Fedora to ensure that progress is made. + +== Proposing an Objective + +Any community member can propose an Objective to the Council +(discuss on the https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[mailing list] +and if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket]). +Of course, people need to be on board to do the actual work required — an Objective with no passionate implementers won't get very far. + +== Current Objectives + +=== Fedora Modularization — The Release + +image::modularity-badge.png[float="right"] + +Summary:: +Implement a new https://docs.pagure.org/modularity/[modular Fedora] design, building on lessons learned in prototype phase. + +Objective Lead:: +https://fedoraproject.org/wiki/User:Langdon[Langdon White] + +Timeframe:: +Release with F28, improvements in F29, with publicity to follow. + +Latest Status Report:: +– + +Objective Details:: +https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_The_Release[Fedora Modularization — The Release] + +Documentation:: +https://docs.pagure.org/modularity/ + + +''' + +=== Continuous Integration and Delivery of Fedora Atomic Host + +Summary:: +We aim to deliver Atomic Host in Fedora via +https://fedoraproject.org/wiki/CI[Continuous Integration and Continuous Delivery]. + +Objective Lead:: +Dominik Perpeet + +Timeframe:: +Release via CI/CD in F27, with refinements in F28 + +Latest Status Report:: +https://www.youtube.com/watch?v=3N6LNASP4EA[Fedora Council Subproject Report: Atomic CI (December 2017)] (YouTube) + +Objective Details:: +https://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Delivery_of_Fedora_Atomic_Host[Continuous Integration and Delivery of Fedora Atomic Host] + +Documentation:: +https://fedoraproject.org/wiki/CI + + +''' + +=== Fedora Internet of Things + +Summary:: +Create a Fedora Edition for Internet of Things, which will make Fedora the default for open source innovation on IoT hardware, middleware and backend platforms. + +Objective Lead:: +Peter Robinson + +Timeframe:: +Beta-level "side compose" in F28, +"spin-like thing" for F29 (potentially made into a Fedora Edition if it's ready), +Fedora Edition for F30 if F29 is missed. + + +Latest Status Report:: +https://www.youtube.com/watch?v=aA6JNeCt8Aw[Fedora Council Subproject Report: Internet of Things (February 2018)] (YouTube) + +Objective Details:: +https://fedoraproject.org/wiki/Objectives/Fedora_IoT + +Documentation:: +(Coming soon!) + + + +== History and Future + +See +https://fedoraproject.org/wiki/Objectives/Completed[Objectives/Completed] +and +https://fedoraproject.org/wiki/Objectives/Potential[Objectives/Potential] diff --git a/project/modules/ROOT/pages/orgchart.adoc b/project/modules/ROOT/pages/orgchart.adoc new file mode 100644 index 0000000..06f928d --- /dev/null +++ b/project/modules/ROOT/pages/orgchart.adoc @@ -0,0 +1,17 @@ +How is Fedora Organized? +======================== + +image::orgchart.png[Fedora Organizational Chart,100%] + +Fedora is a big project, with many moving parts and dozens of groups and subgroups. +You can learn more about the various groups in the chart above in our +https://docs.fedoraproject.org/fedora-project/subprojects/collaboration.html[subprojects documentation]. + +The https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is our overall leadership and governance body. +Most of the project is then roughly organized under https://docs.fedoraproject.org/fedora-project/subprojects/fesco.html[FESCo] +(the Fedora Engineering Steering Committee) or the +https://docs.fedoraproject.org/fedora-project/subprojects/mindshare.html[Mindshare Committee]. + +If this is all a little overwhelming, don't worry — pick an area you're +interested in, introduce yourself to the people involved, and get started. +Fedora is a friendly and open community, welcoming to all. diff --git a/project/objectives.adoc b/project/objectives.adoc deleted file mode 100644 index b58fd55..0000000 --- a/project/objectives.adoc +++ /dev/null @@ -1,100 +0,0 @@ -= Current 12-18 Month Community Objectives - -== Overview - -The primary role of the https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them. -This section documents the **medium-term** targets we've highlighted (as explained in the Council charter). -Each objective has a designated Objective Lead who is responsible -for coordinating efforts to reach the Objective's goals, -for evaluating and reporting on progress, and -for working regularly with all relevant groups in Fedora to ensure that progress is made. - -== Proposing an Objective - -Any community member can propose an Objective to the Council -(discuss on the https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/[mailing list] -and if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket]). -Of course, people need to be on board to do the actual work required — an Objective with no passionate implementers won't get very far. - -== Current Objectives - -=== Fedora Modularization — The Release - -image::modularity-badge.png[float="right"] - -Summary:: -Implement a new https://docs.pagure.org/modularity/[modular Fedora] design, building on lessons learned in prototype phase. - -Objective Lead:: -https://fedoraproject.org/wiki/User:Langdon[Langdon White] - -Timeframe:: -Release with F28, improvements in F29, with publicity to follow. - -Latest Status Report:: -– - -Objective Details:: -https://fedoraproject.org/wiki/Objectives/Fedora_Modularization_%E2%80%94_The_Release[Fedora Modularization — The Release] - -Documentation:: -https://docs.pagure.org/modularity/ - - -''' - -=== Continuous Integration and Delivery of Fedora Atomic Host - -Summary:: -We aim to deliver Atomic Host in Fedora via -https://fedoraproject.org/wiki/CI[Continuous Integration and Continuous Delivery]. - -Objective Lead:: -Dominik Perpeet - -Timeframe:: -Release via CI/CD in F27, with refinements in F28 - -Latest Status Report:: -https://www.youtube.com/watch?v=3N6LNASP4EA[Fedora Council Subproject Report: Atomic CI (December 2017)] (YouTube) - -Objective Details:: -https://fedoraproject.org/wiki/Objectives/Continuous_Integration_and_Delivery_of_Fedora_Atomic_Host[Continuous Integration and Delivery of Fedora Atomic Host] - -Documentation:: -https://fedoraproject.org/wiki/CI - - -''' - -=== Fedora Internet of Things - -Summary:: -Create a Fedora Edition for Internet of Things, which will make Fedora the default for open source innovation on IoT hardware, middleware and backend platforms. - -Objective Lead:: -Peter Robinson - -Timeframe:: -Beta-level "side compose" in F28, -"spin-like thing" for F29 (potentially made into a Fedora Edition if it's ready), -Fedora Edition for F30 if F29 is missed. - - -Latest Status Report:: -https://www.youtube.com/watch?v=aA6JNeCt8Aw[Fedora Council Subproject Report: Internet of Things (February 2018)] (YouTube) - -Objective Details:: -https://fedoraproject.org/wiki/Objectives/Fedora_IoT - -Documentation:: -(Coming soon!) - - - -== History and Future - -See -https://fedoraproject.org/wiki/Objectives/Completed[Objectives/Completed] -and -https://fedoraproject.org/wiki/Objectives/Potential[Objectives/Potential] diff --git a/project/orgchart.adoc b/project/orgchart.adoc deleted file mode 100644 index 06f928d..0000000 --- a/project/orgchart.adoc +++ /dev/null @@ -1,17 +0,0 @@ -How is Fedora Organized? -======================== - -image::orgchart.png[Fedora Organizational Chart,100%] - -Fedora is a big project, with many moving parts and dozens of groups and subgroups. -You can learn more about the various groups in the chart above in our -https://docs.fedoraproject.org/fedora-project/subprojects/collaboration.html[subprojects documentation]. - -The https://docs.fedoraproject.org/fedora-project/council/charter.html[Fedora Council] is our overall leadership and governance body. -Most of the project is then roughly organized under https://docs.fedoraproject.org/fedora-project/subprojects/fesco.html[FESCo] -(the Fedora Engineering Steering Committee) or the -https://docs.fedoraproject.org/fedora-project/subprojects/mindshare.html[Mindshare Committee]. - -If this is all a little overwhelming, don't worry — pick an area you're -interested in, introduce yourself to the people involved, and get started. -Fedora is a friendly and open community, welcoming to all. diff --git a/site.yml b/site.yml new file mode 100644 index 0000000..cc91c00 --- /dev/null +++ b/site.yml @@ -0,0 +1,30 @@ +site: + title: Local Preview + start_page: council::index +content: + sources: + - url: . + branches: HEAD + start_path: council + - url: . + branches: HEAD + start_path: fesco + - url: . + branches: HEAD + start_path: mindshare + - url: . + branches: HEAD + start_path: project +ui: + bundle: + url: https://asamalik.fedorapeople.org/ui-bundle.zip + snapshot: true + default_layout: with_menu +output: + clean: true + dir: ./public + destinations: + - provider: archive +runtime: + pull: true + cache_dir: ./cache diff --git a/subprojects/collaboration.adoc b/subprojects/collaboration.adoc deleted file mode 100644 index 848a269..0000000 --- a/subprojects/collaboration.adoc +++ /dev/null @@ -1,21 +0,0 @@ -Collaboration in Fedora -======================= - -… or, how we formalize working together ---------------------------------------- - - -[NOTE] -==== - -This page is a placeholder. You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - - -==== - - -Working Groups, Subprojects, Teams, SIGs, Committees, and Councils.... what's all this? ---------------------------------------------------------------------------------------- - -TODO: explain! \ No newline at end of file diff --git a/subprojects/diversity.adoc b/subprojects/diversity.adoc deleted file mode 100644 index 9c359da..0000000 --- a/subprojects/diversity.adoc +++ /dev/null @@ -1,12 +0,0 @@ -[NOTE] -==== - -This page is a placeholder. It should contain a brief description -of Fedora's Diversity Team and a link to more documentation (like, the -Diversity Team's own pages). - -You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - - -==== diff --git a/subprojects/fesco/fesco.adoc b/subprojects/fesco/fesco.adoc deleted file mode 100644 index f2e7345..0000000 --- a/subprojects/fesco/fesco.adoc +++ /dev/null @@ -1,37 +0,0 @@ -Fedora Engineering Steering Committee -===================================== - -[.lead] -FESCo is the Fedora Engineering Steering Committee. It is a fully community -elected body and represents the technical leadership in Fedora. - -Overall Mission ---------------- - -FESCo handles the process of accepting new features, the acceptance of new -packaging sponsors, Special Interest Groups (SIGs) and SIG Oversight, the -packaging process, handling and enforcement of maintainer issues and other -technical matters related to the distribution and its construction. - -Common tasks and responsibilities ---------------------------------- - -Issues FESCo handles include: - -* Approval and coordination of "Changes" for Fedora releases -* Package maintainer disputes -* Larger changes to the Fedora Package collection -* Guidance and technical direction for other parts of the project -* Setting the schedule for Fedora development cycles -* Reviewing and approving technical content from Fedora Working groups -* Responsible for what software is offered to end users under what - conditions -* Oversight and approval of new spins and other media that doesn't fit - under a working group - -More Info ---------- - -You can find further information about FESCo, its members, and its policies -on the -https://fedoraproject.org/wiki/Fedora_Engineering_Steering_Committee[FESCo wiki pages] diff --git a/subprojects/mindshare/images/Screenshot_from_2017-09-22_23-33-02.png b/subprojects/mindshare/images/Screenshot_from_2017-09-22_23-33-02.png deleted file mode 100644 index 04722cf..0000000 Binary files a/subprojects/mindshare/images/Screenshot_from_2017-09-22_23-33-02.png and /dev/null differ diff --git a/subprojects/mindshare/mindshare.adoc b/subprojects/mindshare/mindshare.adoc deleted file mode 100644 index 7bd1b8d..0000000 --- a/subprojects/mindshare/mindshare.adoc +++ /dev/null @@ -1,88 +0,0 @@ -= Mindshare - -The Fedora Mindshare Committee represents the outreach leadership in Fedora. Mindshare aims to help outreach teams to reach their targets in a more effective way, by unifying and sharing their working process through an optimized and standardized communication. It consists of mostly appointed, but also elected members. - -== Responsibilities - -Mindshare takes care of some responsibilities hold actually by other teams, adding some more strategical responsibilities to make sure communication and sharing of ideas, actions and projects can be guaranteed. These include: - -* Communication between teams (outreach teams rely on the work of other groups). Mindshare ensures all information from technical teams will get out in time to all outreach teams, working out also a common strategy with Marketing of how to communicate them outside and how to manage them within all outreach teams. -* Ambassadors activity: Mindshare will create templates to help ambassadors to work more effectively. Not only by providing report templates, but also by asking them once a year to compile a short survey. This can help to get real information whether an ambassador is active or not and will not result too binding. -* Motivate contributors to work also in other groups, providing easier access to funding and more autonomy. This challenging part will need some verifying tools (TBD) -* Mindshare takes over all decisional responsibilities left on FAmSCo. Administrative responsibilities will be handled by FAmA, which will consist mainly by treasurers and FAmA admins. -* CommOps which is part of Mindshare takes care of the operations inside Fedora. CommOps will lead the communication between technical and outreach teams. -* Sharing best practices: one of the Mindshare's goals is to take down barriers or whatever is blocking sharing best practices. All teams and all regions can learn from each other and apply successful practices to their local community. -* Mindshare will also try to unify ambassadors more and more, also by dropping the actual Regions. They are not helping communication and were created mostly for organizational aspects. FAmA (with treasurers) will help to sort out regional aspects and meetings, but having a unique ambassadors group will help in several ways to be more effective again. -* Budget: Without regions also the (ex-)regional budgeting process changes. Mindshare will, in collaboration with the FCAIC and consequently with the Council, take care of the Fedora outreach budget (sum of the 4 regional budgets). Minor funding requests can be handled directly by FAmA and treasurers, more important expenses will go through Mindshare, in order to be able and track even necessary reports the Council needs. -* Marketing as part of Mindshare will drive the other teams by providing messages, strategies and talking points for ambassadors. A good collaboration with the other teams is necessary. - -== Making Decisions - -Many basic decisions are made through a process known as *"lazy approval"*, in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus. - -More significant decisions are made through a process of *full consensus*. In order to pass, these decisions need three positive votes (+3) and no negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the poposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of "0" is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation. - -This model matches Fedora's "Friends" foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree. - -In general, Mindsharel conducts business in public discussion, and any Fedora project member can add more opinions and thoughts. It is the duty of the Mindshare Committee to take concerns raised in this way into serious consideration, but only Mindshare members' votes are binding in the final tally. - -== Composition - -image::Screenshot_from_2017-09-22_23-33-02.png[Mindshare Structure,100%,] - -Mindshare has appointed and elected members, and initially there will be 9 seats: - -* FCAIC (chair) -* Ambassadors (2 appointed members) -* Design & Web (appointed) -* Docs (appointed) -* Marketing (appointed) -* Commops (appointed) -* 2 elected seats - -*Note:* The minimum of elected representatives is 2; 3 representatives are elected when the number of seats would otherwise be even. - -== Current Members - -* Elected Representative: *Jared Smith* (https://fedoraproject.org/wiki/User:Jsmith[jsmith]) (_f27-f28_) -* Elected Representative: *Sumantro Mukherjee* (https://fedoraproject.org/wiki/User:Sumantrom[sumantrom])(_f28-f29_) -* FCAIC: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex]) -* Ambassador Representative: FAmA *Robert Mayr* (https://fedoraproject.org/wiki/User:Robyduck[robyduck]) - _ad interim_ -* Ambassador Representative: FAmA *Nick Bebout* (https://fedoraproject.org/wiki/User:Nb[nb]) - _ad interim_ -* Marketing Representative: *Eduard Lucena* (https://fedoraproject.org/wiki/User:X3mboy[x3mboy]) -* CommOps Representative: *Justin W. Flory* (https://fedoraproject.org/wiki/User:Jflory7[jflory7]) -* Design & Web Representative: *Maria Leonova* (https://fedoraproject.org/wiki/User:Mleonova[mleonova]) -* Docs Representative: *Brian Exelbierd* (https://fedoraproject.org/wiki/User:Bex[bex]) - _ad interim_ - -== Contact Info - -=== Mailing lists - -The Mindshare Committee uses two mailing lists: a regular discussion list and an announcement-only mailing list. - -*https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[mindshare]* is a public discussion list. -This is the main discussion point for the Mindshare Committee. -The goal of the list is to either reach a decision or delegate a thread to a more appropriate location. - -*https://lists.fedoraproject.org/admin/lists/mindshare-announce@lists.fedoraproject.org/[mindshare-announce]* is a low-traffic, announcement-only mailing list. -This list is used for occasional updates, news, and announcements from the Committee. -Posting privileges are limited to Mindshare Committee members. -Consider subscribing to this list if you want to stay informed about ongoing activities within the Mindshare Committee. - -== IRC / Telegram - -Mindshare Committee members are present in the *#fedora-mindshare* IRC channel on the Freenode IRC network. -This IRC channel is also bridged to a Telegram group for convenience. -Messages are synchronized between the two. -Telegram users can join https://t.me/fedoramindshare[here]. - -== Pagure == - -The Mindshare Committee operates in a ticket-based workflow. -If you have an issue or task for the Mindshare Committee, open a ticket on the https://pagure.io/mindshare/issues[Pagure instance]. -This is a public issue tracker. -If you have a privacy- or security-sensitive issue, check the _Private_ box when creating the ticket. - -== Meetings - -The Fedora Mindshare Committee does hold regular public IRC meetings to discuss current issues, to clear through anything outstanding which can be quickly resolved, and to ensure that nothing important is left in limbo. All members are be expected to regularly communicate what's going on in their area, through blog posts or other public updates. diff --git a/subprojects/sigs.adoc b/subprojects/sigs.adoc deleted file mode 100644 index 5907ca8..0000000 --- a/subprojects/sigs.adoc +++ /dev/null @@ -1,12 +0,0 @@ -[NOTE] -==== - -This page is a placeholder. It should be adapted from -https://fedoraproject.org/wiki/SIGs -(and should be brought up to date, listing only active groups) - -You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - - -==== diff --git a/subprojects/subprojects.adoc b/subprojects/subprojects.adoc deleted file mode 100644 index 250582d..0000000 --- a/subprojects/subprojects.adoc +++ /dev/null @@ -1,12 +0,0 @@ -[NOTE] -==== - -This page is a placeholder. It should be adapted from -https://fedoraproject.org/wiki/Subprojects -(and possibly be brought up to date) - -You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - - -==== diff --git a/subprojects/workinggroups.adoc b/subprojects/workinggroups.adoc deleted file mode 100644 index e3c29c0..0000000 --- a/subprojects/workinggroups.adoc +++ /dev/null @@ -1,12 +0,0 @@ -[NOTE] -==== - -This page is a placeholder. It should describe how working groups differ -from SIGs and other subprojects (they correspond to Editions and -Objectives) and describe the current ones and link to further docs. - -You can help make this document more useful by -submitting changes via pull request at https://pagure.io/Fedora-Council/council-docs - - -====