cle/docs
36
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Update modules/ROOT/pages/about.adoc

Browse source 
Updating information and fixing some spelling errors in this article that explains the CPE team within Red Hat.
This commit is contained in:
Camila Flores Granella 2022-01-21 15:23:51 +00:00
commit 1297b236ec
1 changed files with 19 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

49
modules/ROOT/pages/about.adoc
View file

@ -1,46 +1,35 @@
:experimental:
= About the team
In 2017 the Fedora Engineering team merged with the CentOS Engineering team
to form what is now called the Community Platform Engineering (CPE) team.
In 2017 the Fedora Engineering team merged with the CentOS Engineering team to form what is now called the Community Platform Engineering (CPE) team.
For the team members, the day to day work did not change much.
Currently, team members are fully dedicated to working on the Fedora and CentOS Stream projects in several different capacities. That includes helping the EPEL project and key SIGs such as the CentOS Automotive SIG
The members working on Fedora are still fully dedicated to work on the
Fedora Project, and those working on CentOS are still fully dedicated to
CentOS. On both projects its members are involved in infrastructure, release
engineering, and design. However, it brought the two infrastructures and
teams closer to each other, allowing for more collaboration between them.
On both, its members are involved in infrastructure, release engineering, design, and implementation of new services (which we term initiatives) for use by the community. The two infrastructures and teams were brought closer to each other, allowing for more collaboration between them, and where we can, we try and share services and ideas to better both our communities.
There are approximately 40 people on this consolidated team and we take a fluid approach to how we staff initiatives. The breakdown looks approximately like this:
There are 22 people on this consolidated team. The breakdown looks like this:
* In Fedora:
** 3 dedicated system administrators
** 7 dedicated developers
** 2 release engineers
** 10 software engineers
** 1 person dedicated to documentation
** 1 designer
** 1 design-centric engineer
* In CentOS:
** 3 system administrators
** 4 developers
** 1 dedicated to the build systems
** 8 software engineers
* There are 10 system administrators, Ops centric engineers, and software engineers working in Infrastructure & Release Engineering for CentOS Stream and Fedora where they help keep the lights on.
* There is also two Red Hat Interns working with us.
* There are also 4 Red Hat Interns working with us.
* The team is also helped and coordinated by:
** 3 people managers
** 1 project owner
** 1 agile practitioner
** 2 product owners
** 4 people managers
As you can see, the team is both quite diverse as well as limited. For
example, we do not have dedicated database administrators or network engineers,
even though most of our application is one or the other when not both.
Team members are geographically spread in multiple timezones giving us as much coverage as possible.
For these reasons we need to be careful on how our limited resources are
spent. The team has therefore defined a xref:index.adoc[Mission
Statement] for itself, allowing to focus its work in certain areas.
The team is both quite diverse as well as limited due to the variety of technologies, languages, and innovations that make up our communities. We are constantly trying to learn and upskill on the next big thing that our communities might need.
We have also written a document explaining xref:working_with_us.adoc[How to
work with us] for small and large tasks. Following this document makes it
easier for us to help you.
For these reasons, we need to be careful about how our limited time and effortare spent. The team has therefore defined a Mission Statement for itself, allowing it to focus its work in certain areas.
We have also written a document explaining How to work with us for small and large tasks. Following this document makes it easier for us to help you.