diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index b51ae3f..a890c30 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -6,7 +6,5 @@ ** xref:glossary.adoc[Glossary] ** xref:sle.adoc[SLE] *** xref:sle_services.adoc[Services] -* xref:about.adoc[About the Team] -** xref:meet_the_team.adoc[Meet The Team] * xref:processes.adoc[Processes] ** xref:process_unmaintained_apps.adoc[Unmaintained apps] diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index 0932764..e29f0b8 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -1,54 +1,101 @@ :experimental: -= The Community Linux Engineering Team += The Community Linux Engineering team The Community Linux Engineering Team (CLE) is a Red Hat team dedicated -to the Fedora and CentOS projects where they contribute to the infrastructure -and release engineering. +to the Fedora and CentOS projects where they contribute to the infrastructure, +release engineering, quality engineering, design, and documentation. The team +was formed in late 2024 by merging the Community Platform Engineering (CPE) +team with Fedora QE. +== Our mission -== Our Mission - -Our mission rests on three axes: - -.Our Mission -[#img-mission] -[caption="Figure 1: "] -image::our_missions.jpg[Our Mission,500,500] +Our mission rests on multiple axes: * **Infrastructure/release-engineering**: To provide power and ping to the different systems that are used and manage the releases of our communities. + **Quality Engineering**: To continually improve the quality of Fedora releases + and updates. * **Application maintenance**: For the applications that we maintain, we work on bug fixes, new features and community development. * **Initiatives**: For a limited time and scope we dedicate some of our engineers and administrators to initiatives deemed important and beneficial to the communities we are involved in. +* **Design**: To provide artwork, user experience, usability, and general design + services to the Fedora project +* **Documentation**: To provide user documentation for current Fedora releases +as well as support for any documentation contributors. +* **CentOS**: Infrastructure and release engineering for the CentOS project. +* **EPEL**: Extra Packages for Enterprise Linux - a project providing additional +package repositories for CentOS and RHEL. -One of the key challenges this team faces is balancing these three axes. -For this reason, we developed the following Mission Statement. +== How to contact us -== Our Responsibilities +Due to the fact that members of CLE work on highly varied tasks, there is no +single point of contact for the team. Instead, if you need help in any of the +areas listed above, you should talk to: -Our responsibilities are scoped in our mission statement: +* **Infrastructure** +** The **Fedora Infrastructure Team** channel on Matrix (`#admin:fedoraproject.org`) +** The link:++https://discussion.fedoraproject.org/tag/infrastructure-team++[#infrastructure-team] +tag on Fedora Discussions +** The link:++https://pagure.io/fedora-infrastructure/new_issue++[Infra issue tracker on Pagure] +* **Release Engineering** +** The **Fedora Release Engineering** channel on Matrix (`#releng:fedoraproject.org`) +** The link:++https://discussion.fedoraproject.org/tag/release-engineering-team++[#release-engineering-team] +tag on Fedora Discussions +** The link:++https:/​/​pagure.​io/​releng/​++[Releng issue tracker on Pagure] +* **QA** +** The **Fedora Quality** channel on Matrix (`#quality:fedoraproject.org`) +** The link:++https://discussion.fedoraproject.org/tag/quality-team++[#quality-team] +tag on Fedora Discussions +** The link:++https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/++[test mailing list] (also see +link:++https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org/++[test-announce] + for announcements) + ** The link:++https://pagure.io/fedora-qa/issues++[fedora-qa issue tracker on Pagure] +** Also see the link:++http://fedoraproject.org/wiki/QA++[Fedora QA wiki page] +and link:++https://openqa.fedoraproject.org/++ +* **Design** +** The **Fedora Design** channel on Matrix (`#design:fedoraproject.org`) +** The link:++https://discussion.fedoraproject.org/tag/design-team++[#design-team] +tag on Fedora Discussions +** The link:++https://gitlab.com/fedora/design/team/requests++[Design team requests issue tracker on Pagure] +* **Documentation** +** The **Fedora Documentation** channel on Matrix +** The link:++https://discussion.fedoraproject.org/tag/docs-team++[#docs-team] +tag on Fedora Discussions +** Docs issues (click the bug icon in the top right corner of any page on +link:++https://docs.fedoraproject.org/++[the Docs site]) +* **CentOS** +** link:++https://matrix.to/#/#centos-space:fedora.im++[CentOS Matrix] +** The link:++https://discussion.fedoraproject.org/tag/centos++[#centos] +tag on Fedora Discussions +** link:+++ https://pagure.io/centos-infra/issues++[CentOS Infra issue tracker on Pagure] +** link:++https://lists.centos.org/hyperkitty/++[CentOS mailing lists] +* **EPEL** +* The **Fedora EPEL** channel on Matrix (#epel:fedoraproject.org) +* The link:++https://discussion.fedoraproject.org/tag/epel-sig++[#epel-sig] +tag on Fedora Discussions +* The link:++https://pagure.io/epel/issues++[EPEL issue tracker on Pagure] +* Also see link:++https://docs.fedoraproject.org/en-US/epel/++[EPEL project documentation] -=== Our Mission Statement +Unless specified otherwise, Matrix rooms can be found at link:++https://chat.fedoraproject.org++. +You will need a link:++https://accounts.fedoraproject.org/++[Fedora account] to join. -__The Community Linux Engineering Team is responsible for the -infrastructure and services that support developing, building, and releasing -of Fedora and CentOS platform artifacts and deliverables, including:__ +Also see +link:++https://docs.fedoraproject.org/en-US/project/communications/++[Communication in Fedora] +for more general information about communicating and getting help within the Fedora +project. -* __Hosting, automating, monitoring and maintaining infrastructure components__ -* __Service monitoring and lifecycle management of services hosted within our - infrastructure__ -* __Feature development for infrastructure-related initiatives__ -* __Tooling to enable all of the above__ +== FAQ/Common misconceptions +[qanda] +Are Red Hat teams separate from the community?:: +Red Hatters can, and indeed many do, play key roles in the community Linux +space, regardless of team affiliation. +Can community members can’t take part in the same Fedora activities that Red Hat employees can?:: +Most activities are or can be open to all and community participation is always +welcome. -=== Why a Mission Statement? - -A mission statement means the team shares a common vision about what our -work is or should be. It gives us clear boundaries for our work and it -helps us having a critical view on our work (current or in the future): “Does -this fit our mission statement?”. With this in mind we can focus on bringing -more value to the community. In other words, we want to maximize our value and -impact in a targeted mission rather than having limited impact on a broad -spectrum. +Are CLE team members responsible for All the Things?:: +No, would be impossible – it’s way too much. We all are part of making these +distributions and communities succeed and grow.