Update all references of CPE to CLE

README.md

@@ -1,7 +1,7 @@
-# CPE Documentation
+# CLE Documentation
 
-This repository contains documentation related to the Community Platform
-Engineering (CPE) team at Red Hat.
+This repository contains documentation related to the Community Linux
+Engineering (CLE) team at Red Hat.
 
 It aims at providing you information on who we are, what we do and how we work
 within the team as well as with you.
@@ -10,9 +10,11 @@ within the team as well as with you.
 To build and preview the site, run:
 
 ```
-$ ./build.sh && ./preview.sh
+$ ./docsbuilder.sh
 ```
 
+You will need to have Podman installed.
+
 The result will be available at http://localhost:8080
 
 Some resources to help you get started with asciidoc:

modules/ROOT/nav.adoc

@@ -1,4 +1,4 @@
-* xref:working_with_us.adoc[Working with CPE]
+* xref:working_with_us.adoc[Working with CLE]
 ** xref:day_to_day_fedora.adoc[Day to day in Fedora]
 ** xref:day_to_day_centos.adoc[Day to day in CentOS]
 ** xref:initiatives.adoc[Initiatives]

modules/ROOT/pages/about.adoc

@@ -3,7 +3,7 @@
 
 In 2017 the Fedora Engineering team merged with the 
 CentOS Engineering team to form what is now called 
-the Community Platform Engineering (CPE) team.
+the Community Linux Engineering (CLE) team.
 
 Currently, team members are fully dedicated to working 
 on the Fedora and CentOS Stream projects in several 

modules/ROOT/pages/day_to_day_centos.adoc

@@ -1,7 +1,7 @@
 :experimental:
-= Working with Community Platform Engineering in CentOS
+= Working with Community Linux Engineering in CentOS
 
-This document explains how to efficiently work with the CPE team.
+This document explains how to efficiently work with the CLE team.
 Your close attention to this document will help both you and us
 do the work you are asking us to do.
 

modules/ROOT/pages/day_to_day_fedora.adoc

@@ -1,4 +1,4 @@
-= Working with Community Platform Engineering in Fedora
+= Working with Community Linux Engineering in Fedora
 
-All you need to know about working with CPE Team is explained in
+All you need to know about working with CLE Team is explained in
 https://docs.fedoraproject.org/en-US/infra/day_to_day_fedora[Fedora Infrastructure documentation].

modules/ROOT/pages/glossary.adoc

@@ -70,27 +70,27 @@ Waiting on External:: This marks tickets that are blocked waiting on
 
 == Application categories
 
-The Fedora Infrastructure runs a fairly larged number of applications. CPE runs
+The Fedora Infrastructure runs a fairly larged number of applications. CLE runs
 most of them and maintain (as in maintain the code base, writing code and patches)
 quite a few of them.
-However, not all applications will get the same level of attention from CPE. So
+However, not all applications will get the same level of attention from CLE. So
 they have been categorized into two maintenance status and two maintenance level.
 
 Each appliction can then be categorized using these, for example:
 
-- bodhi is: CPE run and maintain - Critical path
-- koji is: CPE run and don't maintain (type a) - Critical path
-- waiverdb is: CPE run and don't maintain (type b) - Critical path
-- simple-koji-ci is: CPE run and don't maintain (type b) - Not critical path
+- bodhi is: CLE run and maintain - Critical path
+- koji is: CLE run and don't maintain (type a) - Critical path
+- waiverdb is: CLE run and don't maintain (type b) - Critical path
+- simple-koji-ci is: CLE run and don't maintain (type b) - Not critical path
 
 === Maintenance status
 
-CPE run and maintain:: these are the applications that we run and for which the
+CLE run and maintain:: these are the applications that we run and for which the
   team is responsible for the code base. We lead the project upstream and run it
   in the infrastructure. If something break, we will look at it and if that
   requires patching we will do it.
 
-CPE run and don't maintain:: these are applications that are running in the
+CLE run and don't maintain:: these are applications that are running in the
   infrastructure but for which we do not write the code base. There are two
   types of applications in this sections:
     - a) applications that for which we look after the deployment

modules/ROOT/pages/index.adoc

@@ -1,7 +1,7 @@
 :experimental:
-= The Community Platform Engineering Team
+= The Community Linux Engineering Team
 
-The Community Platform Engineering Team (CPE) is a Red Hat team dedicated
+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.
 
@@ -32,7 +32,7 @@ Our responsibilities are scoped in our mission statement:
 
 === Our Mission Statement
 
-__The Community Platform Engineering Team is responsible for the
+__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:__
 

modules/ROOT/pages/initiatives.adoc

@@ -3,11 +3,11 @@
 = New Initiative Workflow
 
 This document documents a proposed workflow to get new initiatives onto the
-CPE backlog.
+CLE backlog.
 
 == The Process
 
-The process to submit a new initiative to the CPE team to be potentially worked on is outlined below:
+The process to submit a new initiative to the CLE team to be potentially worked on is outlined below:
 
 * Propose a new initiative by opening a ticket at
   https://pagure.io/cpe/initiatives-proposal/new_issue - the proposal should
@@ -23,7 +23,7 @@ The process to submit a new initiative to the CPE team to be potentially worked
   sets needed, hardware, storage, automation, dependant services that could be
   impacted by changes made & how long they think this would take to complete.
 * This information is then reshared with the requestor to verify and sign off on
-  and then reviewed by the CPE review team to be accepted or rejected to our
+  and then reviewed by the CLE review team to be accepted or rejected to our
   backlog.
 * If rejected, the requestor is notified by the product owner.
 * If accepted, the proposal is added to our backlog queue and will be refined
@@ -44,7 +44,7 @@ The process to submit a new initiative to the CPE team to be potentially worked
 .Initiatives flow
 [#img-initiative-flow]
 [caption="Figure 1: "]
-image::CPE_new_initiatives_flow.png[The initiative flow,750,750, link="../_images/CPE_new_initiatives_flow.png"]
+image::CLE_new_initiatives_flow.png[The initiative flow,750,750, link="../_images/CLE_new_initiatives_flow.png"]
 
 === Proposing a New Initiative
 
@@ -65,28 +65,27 @@ information such as:
      nice-to-have or really-nice-to-have you would like to see/have.
 * Area and community concerned/impacted
 
-=== First Decision Point: Is This Initiative for the CPE Team?
+=== First Decision Point: Is This Initiative for the CLE Team?
 
-Based on the information provided in the ticket, the CPE team will consider
+Based on the information provided in the ticket, the CLE team will consider
 whether the initiative is in scope of the xref:index.adoc[Mission Statement],
-and if there is a clear benefit for the communities the CPE team is involved
+and if there is a clear benefit for the communities the CLE team is involved
 in. If your initiative does not fit in the scope of our mission statement,
-it does not mean your challenge is not worth pursuing - but that the CPE team
+it does not mean your challenge is not worth pursuing - but that the CLE team
 has limited resources and needs to be careful on how they are spent. There may
 be occasions where an initiative outside of our scope is accepted. Should this
 happen, it will be at our team and management's discretion.
 
-The CPE team meets regularly to go over the proposed initiatives.
+The CLE team meets regularly to go over the proposed initiatives.
 At this point, it will be decided if your initiative is accepted, or not, and if
 necessary, appoint someone to work with you on refining this proposal.
 
 
 == Final Notes
 
-This new workflow is a change from how the CPE team has worked until now.
+This new workflow is a change from how the CLE team has worked until now.
 The core idea is to maximize the output of the team to the community. We are
 not able to accept everything and anything, and we want to make sure that what
 we do accept is properly limited in scope and time. Hopefully this will allow us
 to work on more initiatives and bring more beneficial changes to our
 communities.
-

modules/ROOT/pages/meet_the_team.adoc

@@ -1,5 +1,7 @@
 = Meet The Team
 
+Note that this is currently outdated due to the reorganization and change from CPE to CLE.
+
 == Current Members
 
 [grid=cols]
@@ -34,7 +36,7 @@ a|image::/trading_cards/current/Tomas Hrcka.png[]
 
 |===
 
-== CPE Cousins
+== CLE Cousins
 
 [cols="1,1"]
 

modules/ROOT/pages/process_unmaintained_apps.adoc

@@ -2,8 +2,8 @@
 
 = Process for unmaintained apps
 
-This document describes the process of handling apps CPE team doesn't maintain anymore.
-The reason why CPE is not maintaining some apps is simple. We want to focus on the
+This document describes the process of handling apps CLE team doesn't maintain anymore.
+The reason why CLE is not maintaining some apps is simple. We want to focus on the
 problems that are directly related to our xref:index.adoc[Mission Statement] and don't
 maintain large amount of applications that are not related to it. Because of this we
 want to shrink the amount of applications we own, but don't have capacity to maintain.
@@ -36,7 +36,7 @@ _production environment if there is no maintainer for 6 months._
 
 _Regards,_
 
-_CPE Team_
+_CLE Team_
 --
 
 . *Stop the service on staging*
@@ -44,10 +44,10 @@ _CPE Team_
 --
 Stop the application in staging first (if there is staging instance).
 See if this will broke any other service. If the broken service
-is CPE owned application remove any ties to the application that is unmaintained
+is CLE owned application remove any ties to the application that is unmaintained
 (this will probably be a mini-initiative).
 
-If the broken application is not CPE owned, let the maintainers of
+If the broken application is not CLE owned, let the maintainers of
 the affected application known about this and warn them that the unmaintained
 app will be removed in 6 months if there is no new maintainer.
 --
@@ -66,7 +66,7 @@ Resend the e-mail from the first step each month.
 +
 --
 Stop the application on production. At this time all the ties to any other
-CPE owned application should be removed.
+CLE owned application should be removed.
 --
 
 . *Announce the application was orphaned*
@@ -90,7 +90,7 @@ _feel free to reach us on #cpe-redhat on https://libera.chat._
 
 _Regards,_
 
-_CPE Team_
+_CLE Team_
 
 If new maintainer is found after this announcement.
 Hand over the application to new maintainer together with all knowledge

modules/ROOT/pages/processes.adoc

@@ -2,4 +2,4 @@
 
 = Processes
 
-This section will contain all processes defined in CPE Team.
+This section will contain all processes defined in CLE Team.

modules/ROOT/pages/sle.adoc

@@ -1,9 +1,9 @@
 :experimental:
 :toc:
-//TODO: this file keeps talking about Fedora Infra. We should either change it to CPE, or have a separate SLE doc for CentOS if there's a difference in SLEs.
+//TODO: this file keeps talking about Fedora Infra. We should either change it to CLE, or have a separate SLE doc for CentOS if there's a difference in SLEs.
 = Service Level Expectations
 
-The CPE team does not have any formal agreement or contract regarding the
+The CLE team does not have any formal agreement or contract regarding the
 availability of its different services. However, we do try our best to keep
 services running, and as a result, you can have some expectations as to what
 we will do to this extent.
@@ -38,7 +38,7 @@ the availability of staff.
 
 * Provide full and detailed reports of the problem or requested service.
 * Provide clear and complete contact information and times when available.
-* Interact with CPE members with respect and courtesy.
+* Interact with CLE members with respect and courtesy.
 * Leave alternative contacts who can also be available in case of vacation
   or other emergencies.
 * When contacted by Fedora IT, respond back within 5 business days.

modules/ROOT/pages/sle_services.adoc

@@ -9,7 +9,7 @@ presented in our xref:sle.adoc[SLE Documentation].
 ====
 This document is still a **work in progress**. The services listed
 there are at their appropriate level for Fedora but not all of them are under
-the responsabilities of the CPE team which is currently not represented here.
+the responsabilities of the CLE team which is currently not represented here.
 ====
 
 == Critical

modules/ROOT/pages/time_tables.adoc

@@ -2,11 +2,11 @@
 :toc:
 = Time Tables
 
-This document aims at recording the different deadlines that the CPE team
+This document aims at recording the different deadlines that the CLE team
 tries to aim for its planning.
 
 NOTE: Please be aware that all initiatives briefed in will be reviewed by
-      our review team which includes: CPE members (manager, project owner,
+      our review team which includes: CLE members (manager, project owner,
       technical leads and agile practitioner), Fedora Representative,
       CentOS Representative, who will make a decision to accept this work,
       or decline due to unavailability of time/people, etc.

modules/ROOT/pages/working_with_us.adoc

@@ -1,9 +1,9 @@
 :experimental:
-= Working with Community Platform Engineering
+= Working with Community Linux Engineering
 
-This document explains how the CPE team works.
+This document explains how the CLE team works.
 
-We break down work requests that the team responds to into two categories, which we believe benefits both the CPE team and the communities we serve as they allow the team to operate efficiently and allow us to plan our work.
+We break down work requests that the team responds to into two categories, which we believe benefits both the CLE team and the communities we serve as they allow the team to operate efficiently and allow us to plan our work.
 
 * Initiatives handled by dedicated project teams
   ** Initiatives are projects that require multiple team members to complete

site.yml

@@ -1,6 +1,6 @@
 site:
   title: Local Preview
-  start_page: cpe:ROOT:index.adoc
+  start_page: cle:ROOT:index.adoc
 content:
   sources:
    - url: .