2019-08-11 11:16:11 +02:00
|
|
|
|
:experimental:
|
2025-01-15 17:58:53 +01:00
|
|
|
|
= The Community Linux Engineering team
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2024-10-22 16:08:13 +02:00
|
|
|
|
The Community Linux Engineering Team (CLE) is a Red Hat team dedicated
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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.
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-09-19 12:07:13 +02:00
|
|
|
|
== Our Vision
|
|
|
|
|
|
|
|
|
|
|
|
To collaborate and grow the future of open source communities.
|
|
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
== Our mission
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-09-19 12:07:13 +02:00
|
|
|
|
The CLE team connects Red Hat and upstream communities, empowering Fedora, CentOS,
|
|
|
|
|
|
and RHEL communities through collaboration, innovation, and sustainable open source growth.
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
== How to contact us
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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:
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
* **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
|
2025-01-15 18:11:30 +01:00
|
|
|
|
** The link:++https://pagure.io/releng/++[Releng issue tracker on Pagure]
|
2025-01-15 17:58:53 +01:00
|
|
|
|
* **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]
|
2025-01-15 18:11:30 +01:00
|
|
|
|
and link:++https://openqa.fedoraproject.org/++[]
|
2025-01-15 17:58:53 +01:00
|
|
|
|
* **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**
|
2025-01-15 18:11:30 +01:00
|
|
|
|
** The **Fedora Documentation** channel on Matrix (`#docs:fedoraproject.org`)
|
2025-01-15 17:58:53 +01:00
|
|
|
|
** 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
|
2025-01-15 18:11:30 +01:00
|
|
|
|
** link:++https://pagure.io/centos-infra/issues++[CentOS Infra issue tracker on Pagure]
|
2025-01-15 17:58:53 +01:00
|
|
|
|
** 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]
|
2019-06-26 17:14:57 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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.
|
2019-07-26 17:37:13 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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.
|
2019-07-26 17:37:13 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
== 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.
|
2019-07-26 17:37:13 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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.
|
2019-07-26 17:37:13 +02:00
|
|
|
|
|
2025-01-15 17:58:53 +01:00
|
|
|
|
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.
|