diff --git a/404.md b/404.md
index 5669972..591e977 100644
--- a/404.md
+++ b/404.md
@@ -1,6 +1,5 @@
---
title: Page not found
-layout: aside
---
The requested page could not be found.
diff --git a/_posts/2023-12-08-connect.md b/_posts/2023-12-08-connect.md
index 9b159d9..46f0e8b 100644
--- a/_posts/2023-12-08-connect.md
+++ b/_posts/2023-12-08-connect.md
@@ -1,6 +1,5 @@
---
title: "Connect at FOSDEM"
-layout: "aside"
category: news-and-events
---
diff --git a/_sponsors/altushost.md b/_sponsors/altushost.md
index f76ed90..0c6a5ee 100644
--- a/_sponsors/altushost.md
+++ b/_sponsors/altushost.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/altushost.png
address: https://www.altushost.com/
---
-
diff --git a/_sponsors/aws.md b/_sponsors/aws.md
index 04c88c2..773693c 100644
--- a/_sponsors/aws.md
+++ b/_sponsors/aws.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/aws.png
address: https://aws.amazon.com
---
-
diff --git a/_sponsors/baseip.md b/_sponsors/baseip.md
index 451c23c..913fe3c 100644
--- a/_sponsors/baseip.md
+++ b/_sponsors/baseip.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/baseip_240x60.jpg
address: http://www.baseip.com/
---
-
diff --git a/_sponsors/cdn77.md b/_sponsors/cdn77.md
index a1008e1..e6083ee 100644
--- a/_sponsors/cdn77.md
+++ b/_sponsors/cdn77.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/cdn77.png
address: http://www.cdn77.com/
---
-
diff --git a/_sponsors/clientvps.md b/_sponsors/clientvps.md
index 3cc75c7..6403101 100644
--- a/_sponsors/clientvps.md
+++ b/_sponsors/clientvps.md
@@ -1,5 +1,5 @@
---
-name: ClientVPS
+name: ClientVPS
country: Finland
logo: /assets/img/sponsors/clientvps.png
address: https://www.clientvps.com/
diff --git a/_sponsors/codero.md b/_sponsors/codero.md
index a3e5190..9ead15e 100644
--- a/_sponsors/codero.md
+++ b/_sponsors/codero.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/codero.png
address: http://www.codero.com
---
-
diff --git a/_sponsors/cpanel.md b/_sponsors/cpanel.md
index 02f28fa..d2db86c 100644
--- a/_sponsors/cpanel.md
+++ b/_sponsors/cpanel.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/cpanel.png
address: http://www.cpanel.com/
---
-
diff --git a/_sponsors/dedicatedsolutions.md b/_sponsors/dedicatedsolutions.md
index abf0c84..a157ea0 100644
--- a/_sponsors/dedicatedsolutions.md
+++ b/_sponsors/dedicatedsolutions.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/dedicatedsolutions.png
address: https://www.dedicatedsolutions.com/
---
-
diff --git a/_sponsors/equinix.md b/_sponsors/equinix.md
index 411d1eb..542d64c 100644
--- a/_sponsors/equinix.md
+++ b/_sponsors/equinix.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/equinix.png
address: https://metal.equinix.com/
---
-
diff --git a/_sponsors/eukhost.md b/_sponsors/eukhost.md
index 2b9c204..ae0c602 100644
--- a/_sponsors/eukhost.md
+++ b/_sponsors/eukhost.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/eukhost.png
address: http://www.eukhost.com/
---
-
diff --git a/_sponsors/fasthosts.md b/_sponsors/fasthosts.md
index 6f8bc0a..f6a596d 100644
--- a/_sponsors/fasthosts.md
+++ b/_sponsors/fasthosts.md
@@ -4,4 +4,3 @@ country: uk
logo: /assets/img/sponsors/fasthosts.png
address: https://www.fasthosts.co.uk/
---
-
diff --git a/_sponsors/heficed.md b/_sponsors/heficed.md
index c6b10e0..f129ba0 100644
--- a/_sponsors/heficed.md
+++ b/_sponsors/heficed.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/heficed.png
address: http://www.heficed.com/
---
-
diff --git a/_sponsors/host-stage.md b/_sponsors/host-stage.md
index e60d943..2339397 100644
--- a/_sponsors/host-stage.md
+++ b/_sponsors/host-stage.md
@@ -4,4 +4,3 @@ country: france
logo: /assets/img/sponsors/host-stage.png
address: http://www.host-stage.net/
---
-
diff --git a/_sponsors/hostiserver.md b/_sponsors/hostiserver.md
index 5bf4368..080eaa6 100644
--- a/_sponsors/hostiserver.md
+++ b/_sponsors/hostiserver.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/hostiserver.png
address: https://www.hostiserver.com/
---
-
diff --git a/_sponsors/itsyndicate.md b/_sponsors/itsyndicate.md
index 303ff91..6dcfe83 100644
--- a/_sponsors/itsyndicate.md
+++ b/_sponsors/itsyndicate.md
@@ -4,4 +4,3 @@ country: Ukraine
logo: /assets/img/sponsors/itsyndicate.png
address: https://itsyndicate.org/
---
-
diff --git a/_sponsors/leaseweb.md b/_sponsors/leaseweb.md
index f1925eb..18c4b95 100644
--- a/_sponsors/leaseweb.md
+++ b/_sponsors/leaseweb.md
@@ -4,4 +4,3 @@ country: netherlands
logo: /assets/img/sponsors/leaseweb.png
address: http://www.leaseweb.com/
---
-
diff --git a/_sponsors/liquidweb.md b/_sponsors/liquidweb.md
index 99c16a9..5f7ff8d 100644
--- a/_sponsors/liquidweb.md
+++ b/_sponsors/liquidweb.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/liquidweb.png
address: http://www.liquidweb.com/
---
-
diff --git a/_sponsors/nexcess.md b/_sponsors/nexcess.md
index a3f5011..9963989 100644
--- a/_sponsors/nexcess.md
+++ b/_sponsors/nexcess.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/nexcess.png
address: http://www.nexcess.net/
---
-
diff --git a/_sponsors/psw.md b/_sponsors/psw.md
index b0da1f8..5771b38 100644
--- a/_sponsors/psw.md
+++ b/_sponsors/psw.md
@@ -1,7 +1,6 @@
----
+---
name: psw group
country: usa
logo: /assets/img/sponsors/PSW_Banner_240x60.jpg
address: http://www.psw.net/
---
-
diff --git a/_sponsors/serverel.md b/_sponsors/serverel.md
index 9572fc8..dbb0576 100644
--- a/_sponsors/serverel.md
+++ b/_sponsors/serverel.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/serverel.png
address: http://www.serverel.com/
---
-
diff --git a/_sponsors/servermania.md b/_sponsors/servermania.md
index df5b536..522a520 100644
--- a/_sponsors/servermania.md
+++ b/_sponsors/servermania.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/servermania.gif
address: http://servermania.com/
---
-
diff --git a/_sponsors/serverpoint.md b/_sponsors/serverpoint.md
index cfe7082..ca752c0 100644
--- a/_sponsors/serverpoint.md
+++ b/_sponsors/serverpoint.md
@@ -4,4 +4,3 @@ country: us
logo: /assets/img/sponsors/serverpoint.png
address: http://www.serverpoint.com
---
-
diff --git a/_sponsors/serverpronto.md b/_sponsors/serverpronto.md
index 83a5e98..8afabce 100644
--- a/_sponsors/serverpronto.md
+++ b/_sponsors/serverpronto.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/serverpronto_small.gif
address: http://www.serverpronto.com/
---
-
diff --git a/_sponsors/stablepoint.md b/_sponsors/stablepoint.md
index 6cd5e8d..551a419 100644
--- a/_sponsors/stablepoint.md
+++ b/_sponsors/stablepoint.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/stablepoint.png
address: https://www.stablepoint.com/
---
-
diff --git a/_sponsors/steadfast.md b/_sponsors/steadfast.md
index a335a82..b6d91c2 100644
--- a/_sponsors/steadfast.md
+++ b/_sponsors/steadfast.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/steadfast.png
address: http://steadfast.net/
---
-
diff --git a/_sponsors/tailoredservers.md b/_sponsors/tailoredservers.md
index aa63f5b..15c1edc 100644
--- a/_sponsors/tailoredservers.md
+++ b/_sponsors/tailoredservers.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/tailoredservers.png
address: http://www.tailoredservers.com
---
-
diff --git a/_sponsors/trabia.md b/_sponsors/trabia.md
index 0931054..d7bd30a 100644
--- a/_sponsors/trabia.md
+++ b/_sponsors/trabia.md
@@ -1,7 +1,6 @@
---
-name: trabia network
+name: trabia network
country: usa
logo: /assets/img/sponsors/trabia.png
address: https://www.trabia.com/
---
-
diff --git a/_sponsors/vhostvn.md b/_sponsors/vhostvn.md
index f09ba86..dcab570 100644
--- a/_sponsors/vhostvn.md
+++ b/_sponsors/vhostvn.md
@@ -1,6 +1,5 @@
----
+---
name: vHost
logo: /assets/img/sponsors/vhostvn.gif
address: http://vhost.vn/
---
-
diff --git a/_sponsors/webnx.md b/_sponsors/webnx.md
index 1e84bdb..072d581 100644
--- a/_sponsors/webnx.md
+++ b/_sponsors/webnx.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/webnx1.png
address: http://www.webnx.com
---
-
diff --git a/_sponsors/whitelabelitsolutions.md b/_sponsors/whitelabelitsolutions.md
index 40812f5..65b8697 100644
--- a/_sponsors/whitelabelitsolutions.md
+++ b/_sponsors/whitelabelitsolutions.md
@@ -4,4 +4,3 @@ country: usa
logo: /assets/img/sponsors/whitelabelitsolutions.gif
address: http://whitelabelitsolutions.com/
---
-
diff --git a/about.md b/about.md
index 84ac372..b55a70c 100644
--- a/about.md
+++ b/about.md
@@ -1,6 +1,5 @@
---
title: About CentOS
-layout: aside
---
## CentOS Linux
diff --git a/about/governance.md b/about/governance.md
index 287d76a..2bb3b98 100644
--- a/about/governance.md
+++ b/about/governance.md
@@ -1,6 +1,5 @@
---
title: "Governance"
-layout: aside
---
The CentOS Project has two main levels of governance - The Board of Directors (“The Board”), and Special Interest Groups (SIGs).
@@ -66,4 +65,3 @@ small set of issues, in order to either create awareness or to focus on developm
* [Joining the project](/about/governance/joining-the-project)
* [Voting](/about/governance/voting)
* [Appendix: Glossary](/about/governance/appendix-glossary)
-
diff --git a/about/governance/appendix-glossary.md b/about/governance/appendix-glossary.md
index 582c2f3..c14a80f 100644
--- a/about/governance/appendix-glossary.md
+++ b/about/governance/appendix-glossary.md
@@ -1,6 +1,5 @@
---
title: "Glossary"
-layout: aside
---
## Meritocracy
diff --git a/about/governance/board-responsibilities.md b/about/governance/board-responsibilities.md
index c323295..eeb8efe 100644
--- a/about/governance/board-responsibilities.md
+++ b/about/governance/board-responsibilities.md
@@ -1,6 +1,5 @@
---
title: "Responsibilities"
-layout: aside
---
## CentOS Governing Board Responsibilities
@@ -47,6 +46,6 @@ The CentOS Governing Board shall include two named roles: a Chair and a Liaison,
* Allow for the Board to bring concerns or perspectives from the community to Red Hat.
* The Liaison may be requested by the Board Chair to escalate a decision beyond the Board in some cases when the Board cannot reach consensus. This is discussed in the section on The Role of the Liaison.
-The Liaison is required to be a Red Hat employee, which will enable this person to be an effective bi-directional conduit between Red Hat and the CentOS Project. The Chair, however, can be anyone selected by the Board from among its members. The Liaison may be rotated at any time to an alternate Red Hat employee who is a Board member. Newly appointed Board members may also hold the Liaison seat. The Chair and the Liaison cannot be the same person.
+The Liaison is required to be a Red Hat employee, which will enable this person to be an effective bi-directional conduit between Red Hat and the CentOS Project. The Chair, however, can be anyone selected by the Board from among its members. The Liaison may be rotated at any time to an alternate Red Hat employee who is a Board member. Newly appointed Board members may also hold the Liaison seat. The Chair and the Liaison cannot be the same person.
The Board will operate under the principles of [meritocracy](/about/governance/appendix-glossary/#meritocracy), having the Board be driven by a [consensus-based decision model](/about/governance/appendix-glossary/#consensus-decision-making). This model fosters an active healthy debate that furthers the Project while recognising its relationship to Red Hat's product source, the new formal relationship with Red Hat, and preserving the viability of the key upstream that feeds it.
diff --git a/about/governance/board.md b/about/governance/board.md
index c86ee3d..de0cdee 100644
--- a/about/governance/board.md
+++ b/about/governance/board.md
@@ -1,7 +1,6 @@
---
title: "Board of Directors"
title_lead: Structure and Policies
-layout: aside
---
**This document is a work in progress.**
@@ -98,7 +97,7 @@ A director may also, at any time, resign for reasons of their own, without being
#### Activity
-All directors are contacted by the Community Architect towards the end of their cohort period during the year to determine if they wish to continue serving. It is important for the community and the project that directors are
+All directors are contacted by the Community Architect towards the end of their cohort period during the year to determine if they wish to continue serving. It is important for the community and the project that directors are
active and participating. While it is understood that members of the board (not including the laison) are volunteers, it is important that directors are accessible. As such not attaining the following criteria could result in a director being considered inactive:
* Absence from 3 consecutive Board meetings without prior communication
@@ -180,5 +179,3 @@ The Community Architect’s day to day responsibilities include, but are not lim
* Managing the budget provided by Red Hat OSPO, for the benefit of the community
The Board of Directors may, at any time, petition the Red Hat OSPO to replace or remove the Community Architect for dereliction of duty, violation of the Code of Conduct, or other reasons agreed upon by the Board and presented to the CA’s management.
-
-
diff --git a/about/governance/director-requirements.md b/about/governance/director-requirements.md
index b1301c3..602228e 100644
--- a/about/governance/director-requirements.md
+++ b/about/governance/director-requirements.md
@@ -1,6 +1,5 @@
---
title: "Director Requirements"
-layout: aside
---
## Director Requirements
@@ -28,4 +27,3 @@ Directors are expected to subscribe to, and periodically check on new issues rai
Directors *do not* act on behalf of their employer, with the important exception of the [Red Hat Liaison](https://www.centos.org/about/governance/board-responsibilities/#red-hat-liaison-responsibilities). Board membership is an individual role. If you feel that you cannot act in the best interests of the project, even when it might not be the preferred decision of your employer, or if doing so may negatively impact your employment, this is not the role for you. You should discuss this with your employer and your management, and make this expectation clear to them, so that this does not come as a surprise to them at some later date. Furthermore, your employer should not issue public statements that imply that you are their representative.
Directors will typically be nominated based on their merit in the community. This includes, but is not limited to, active participation in the CentOS Project, and a clear understanding of project goals and governance. The community may decide, however, to nominate an “outsider”, if they believe that the new perspective of a potential candidate will be in the best interests of the project.
-
diff --git a/about/governance/joining-the-project.md b/about/governance/joining-the-project.md
index 4bd6961..0126e98 100644
--- a/about/governance/joining-the-project.md
+++ b/about/governance/joining-the-project.md
@@ -1,6 +1,5 @@
---
title: "Joining the Project"
-layout: aside
---
There are 3 primary paths within the CentOS Project for individuals to obtain and grow merit.
@@ -28,4 +27,4 @@ Each Board member appointed or reconfirmed by the Board will be selected based o
Based upon the merit criteria, the existing Board may nominate additional Board members. The Board must consist of at least 8 members and is capped at a total of 11 members. The Board values user representation on the Board directly through members seated on the Board who have met the merit criteria. This is in addition to the indirect user community influence via interactions with individual Board members.
-As the new CentOS grows and learns, the CentOS community may propose to the Board and/or the Board may propose its own changes to the governance and/or the merit criteria to account for, among other things, confusion or inadequacies.
+As the new CentOS grows and learns, the CentOS community may propose to the Board and/or the Board may propose its own changes to the governance and/or the merit criteria to account for, among other things, confusion or inadequacies.
diff --git a/about/governance/sigs.md b/about/governance/sigs.md
index e79168a..60d4533 100644
--- a/about/governance/sigs.md
+++ b/about/governance/sigs.md
@@ -5,7 +5,6 @@ title_lead: |
specific CentOS Project variants. Variants are specialized and focused rebuilds
of CentOS to meet the needs and requirements of their corresponding communities
and the technology associated with those communities.
-layout: aside
---
SIGs are usually self-forming around a technology by a small community of
diff --git a/about/governance/voting.md b/about/governance/voting.md
index c6b44a3..eb0da77 100644
--- a/about/governance/voting.md
+++ b/about/governance/voting.md
@@ -1,6 +1,5 @@
---
title: "CentOS Governance - Voting"
-layout: aside
---
The voting system used by all SIGs and the Governing Board uses a
@@ -19,7 +18,7 @@ Board business may be conducted on a private or public list, whichever is more
appropriate for the issue at hand.
All -1s votes require reason/ explanation, -1's with no substantiation may be
-overturned.
+overturned.
## When do votes need to be called?
@@ -53,11 +52,11 @@ or business critical by Red Hat if: (1) a board quorum (i.e., a majority) is
present or a quorum of Board members has cast their votes; or (2) after 3
working days if a Board quorum is not present at a meeting or a quorum has not
cast their votes (list votes); provided that the Chair may (or at the request
-of the Liaison, will) call a meeting and demand that a quorum be present.
+of the Liaison, will) call a meeting and demand that a quorum be present.
Unless the Liaison specifically indicates on a specific issue that they are
acting in their official capacity as Liaison, either prior to a vote or later
(e.g., after an issue has been deemed time or business critical), the Liaison's
voice and vote is treated the same as any other member of the Board. Decisions
indicated as Liaison decisions made on behalf of the Board by the Liaison may
-not be overturned.
+not be overturned.
diff --git a/centos-linux-eol.md b/centos-linux-eol.md
index 68e1d0f..fa64801 100644
--- a/centos-linux-eol.md
+++ b/centos-linux-eol.md
@@ -3,14 +3,13 @@ title: CentOS Linux EOL
title_lead: |
CentOS Linux 8 will reach End of Life on December 31, 2021. Here's
what that means.
-layout: aside
---
CentOS Linux 8 will reach End Of Life (EOL) on December 31st, 2021. Here's what that means.
In line with the EOL of previous releases, we will **NOT** be automatically migrating anyone to the next version (which is CentOS Stream 8 in this case).
-We **will** be shipping a rebuild of Red Hat Enterprise Linux (RHEL) 8.5 once it is released, even if that means that this is released slightly after the EOL date.
+We **will** be shipping a rebuild of Red Hat Enterprise Linux (RHEL) 8.5 once it is released, even if that means that this is released slightly after the EOL date.
The release of a RHEL point release is often accompanied, immediately afterwards, by a set of zero-day updates. We **will** be providing this content as part of the final CentOS Linux 8 release. There will, however, be no more updates to the CentOS Linux 8 content after that time.
@@ -22,4 +21,3 @@ See also:
* [CentOS Project shifts focus to CentOS Stream](https://blog.centos.org/2020/12/future-is-centos-stream/)
* [How CentOS Linux compares to CentOS Stream](/cl-vs-cs)
-
diff --git a/centos-linux.md b/centos-linux.md
index f1ffe1e..aa8b101 100644
--- a/centos-linux.md
+++ b/centos-linux.md
@@ -4,7 +4,6 @@ title_lead: |
Consistent, manageable platform that suits a wide variety
of deployments. For some open source communities, it is a solid, predictable
base to build upon.
-layout: aside
---
diff --git a/centos-stream.md b/centos-stream.md
index 140cad0..6c1b961 100644
--- a/centos-stream.md
+++ b/centos-stream.md
@@ -5,7 +5,6 @@ title_lead: |
(RHEL) development, positioned as a midstream between Fedora Linux and RHEL.
For anyone interested in participating and collaborating in the RHEL
ecosystem, CentOS Stream is your reliable platform for innovation.
-layout: aside
---
diff --git a/cl-vs-cs.md b/cl-vs-cs.md
index 29c44b4..993f9ee 100644
--- a/cl-vs-cs.md
+++ b/cl-vs-cs.md
@@ -2,7 +2,6 @@
title: Comparing CentOS Stream and CentOS Linux
title_lead: |
What's the difference between CentOS Stream and CentOS Linux?
-layout: aside
---
# Comparing Centos Linux and CentOS Stream
@@ -37,7 +36,7 @@ CentOS Stream contains content planned for upcoming RHEL minor releases. The up
Getting changes into CentOS Linux involves contributing to the upstream projects that are included in the distribution. This includes, but is not necessarily limited to, contributing to Fedora. Change that make it into Fedora might be in the next release of RHEL, which will then be in the next CentOS rebuild. This process can take years.
CentOS Stream provides a way to [contribute directly](https://docs.centos.org/en-US/stream-contrib/), cutting this process down to weeks or days.
-
+
## Testing
Testing for CentOS Linux and CentOS Stream is very similar, and differs mostly in the timing in which things happen.
@@ -45,4 +44,3 @@ Testing for CentOS Linux and CentOS Stream is very similar, and differs mostly i
Changes hit CentOS Stream and RHEL only once they have undergone [rigorous testing](https://blog.centos.org/2020/12/centos-stream-is-continuous-delivery/). These tests occur both internally to Red Hat, and in our public distro-wide test suite. As such, you can [contribute your tests](https://github.com/CentOS/sig-core-t_functional) to that system, so that future changes don't break the things you care about.
As a rebuild, CentOS Linux benefits from all of these same tests, but, prior to CentOS Stream, lacked a way for you to influence what was tested and how.
-
diff --git a/code-of-conduct.md b/code-of-conduct.md
index 49f0b6f..116c1ca 100644
--- a/code-of-conduct.md
+++ b/code-of-conduct.md
@@ -1,6 +1,5 @@
---
title: "CentOS Code of Conduct"
-layout: aside
---
## CentOS Community Code of Conduct
@@ -96,5 +95,3 @@ Additional material is drawn from many sources, including:
* [https://www.washingtonpost.com/opinions/how-my-restaurant-successfully-dealt-with-harassment-from-customers/2018/03/29/3d9d00b8-221a-11e8-badd-7c9f29a55815_story.html](https://www.washingtonpost.com/opinions/how-my-restaurant-successfully-dealt-with-harassment-from-customers/2018/03/29/3d9d00b8-221a-11e8-badd-7c9f29a55815_story.html)
* [https://www.shrm.org/hr-today/news/hr-magazine/Pages/1214-workplace-investigations.aspx](https://www.shrm.org/hr-today/news/hr-magazine/Pages/1214-workplace-investigations.aspx)
* [https://www.eeoc.gov/policy/docs/harassment.html](https://www.eeoc.gov/policy/docs/harassment.html)
-
-
diff --git a/community/calendar.md b/community/calendar.md
index 9165204..6e02f7e 100644
--- a/community/calendar.md
+++ b/community/calendar.md
@@ -1,7 +1,6 @@
---
title: "CentOS IRC meetings"
title_lead: ""
-layout: page
permalink: /:path/:basename/index.html
toc: true
---
@@ -92,7 +91,7 @@ Working agenda:
* [Link to Project Site](http://wiki.centos.org/SpecialInterestGroup/Cloud)
* The CentOS Cloud SIG (CCS) is a group of people coming together to focus on packaging and maintaining different FOSS based Private cloud infrastructure applications that one can install and run natively on CentOS. We are a non vendor, non technology and non agent specific focus group, but we will gladly work with and build content to suit relevant niches or vendor ecosystems. This group specifically targets users who wish to install and run their own, independent ( or hybrid ) cloud infrastructure on CentOS.
-The CCS intends to take ownership of existing CentOS Project relationships with vendors, and help to maintain the updated package repositories for all participating cloud projects.
+The CCS intends to take ownership of existing CentOS Project relationships with vendors, and help to maintain the updated package repositories for all participating cloud projects.
### CPE Infra and Releng Team stand-up
@@ -185,4 +184,4 @@ administrative access to shared services.
-Page generated on 2023-09-13 17:30:55.950002 UTC
\ No newline at end of file
+Page generated on 2023-09-13 17:30:55.950002 UTC
diff --git a/community/irc-meetings.ical b/community/irc-meetings.ical
index 1c1aa00..ccd4b09 100644
--- a/community/irc-meetings.ical
+++ b/community/irc-meetings.ical
@@ -25,8 +25,8 @@ UID:automotivesig-20231004
RRULE:FREQ=MONTHLY;BYDAY=1WE
DESCRIPTION:Project: Automotive SIG\nChair: Jefro Osier-Mixon (JeffreyOs
ierMixon)\, acting\nDescription: The purpose of the Automotive SIG is two
- -fold. First\, it is meant to be a neutral public space for collaboration
- between third parties interested in open development of software targeted
+ -fold. First\, it is meant to be a neutral public space for collaboration
+ between third parties interested in open development of software targeted
at in-vehicle automotive use cases. Second\, it is meant to provide such p
rojects with build and test infrastructure. (This second purpose is\, as w
e understand it\, common to many SIGs)\n\nThe goal of the SIG is to provid
@@ -45,7 +45,7 @@ DURATION:PT1H
DTSTAMP:20210908T105120Z
UID:boardofdirectors-20231018
RRULE:FREQ=MONTHLY;BYDAY=3WE
-DESCRIPTION:Project: Board of Directors\nChair: Rich Bowen (rbowen) and
+DESCRIPTION:Project: Board of Directors\nChair: Rich Bowen (rbowen) and
Thomas Oulevey (alphacc)\nDescription: Board of Directors open discussion
. Scheduled for one week after the monthly Board of Directors meeting\n\nP
roject URL: None
@@ -130,7 +130,7 @@ UID:cloudsig-20231012
RRULE:FREQ=MONTHLY;BYDAY=2TH
DESCRIPTION:Project: Cloud SIG\nChair: Alfredo Moralejo Alonso (amoralej
)\nDescription: The CentOS Cloud SIG (CCS) is a group of people coming to
- gether to focus on packaging and maintaining different FOSS based Private
+ gether to focus on packaging and maintaining different FOSS based Private
cloud infrastructure applications that one can install and run natively on
CentOS. We are a non vendor\, non technology and non agent specific focus
group\, but we will gladly work with and build content to suit relevant n
@@ -168,7 +168,7 @@ DESCRIPTION:Project: Hyperscale SIG monthly hangout\nChair: Davide Caval
G hangout (Zoom VC\, not IRC): https://us06web.zoom.us/j/84411093900?pwd=R
UxKUFAxVlJnQWVMODhobThLU3BHdz09\nThe Hyperscale SIG focuses on enabling Ce
ntOS Stream deployment on large-scale infrastructures and facilitating col
- laboration on packages and tooling. This is a monthly VC to work together
+ laboration on packages and tooling. This is a monthly VC to work together
on a common project\, ask questions\, or just hang out. This occurs on the
third Wednesday of each month. If Zoom asks for a passcode\, use 550255 (
the meeting ID is 844 1109 3900).\n\nProject URL: https://wiki.centos.org
@@ -184,7 +184,7 @@ UID:isasig-20230915
RRULE:FREQ=WEEKLY;INTERVAL=2
DESCRIPTION:Project: ISA SIG\nChair: Josh Boyer (jwboyer) and Florian We
imer (fweimer)\nDescription: The ISA SIG explores potential benefits of a
- pplying existing compiler technology to distribution packages\, targeting
+ pplying existing compiler technology to distribution packages\, targeting
more recent CPUs\, and evaluating different options for how these optimiza
tions can be maintained in a scalable way\, and delivered to end users.\n\
nProject URL: https://sigs.centos.org/isa/
@@ -198,7 +198,7 @@ DTSTAMP:20210719T092451Z
UID:infrastructuresig-20230925
RRULE:FREQ=WEEKLY;INTERVAL=2
DESCRIPTION:Project: Infrastructure SIG\nChair: Aoife Moloney (amoloney)
- or Brian Stinson (bstinson)\nDescription: The CentOS Infrastructure SIG
+ or Brian Stinson (bstinson)\nDescription: The CentOS Infrastructure SIG
will provide a working group to manage all\nCentOS infrastructure. It will
be responsible for oversight of all\ninfrastructure resources\, and provi
ding guidelines for who may be granted\nadministrative access to shared se
@@ -227,8 +227,8 @@ UID:nfvsig-20231004
RRULE:FREQ=MONTHLY;BYDAY=1WE
DESCRIPTION:Project: NFV SIG\nChair: Alfredo Moralejo (amoralej)\nDescri
ption: The goal of NFV SIG is to provide a set of packages related to vir
- tual networking and Network Function Virtualization for CentOS and pursue
- the cooperation between different users and projects sharing the interest
+ tual networking and Network Function Virtualization for CentOS and pursue
+ the cooperation between different users and projects sharing the interest
on these software pieces.\n\nAgenda URL: https://hackmd.io/oRe_HVJiTteDI4
H332ApMw\nProject URL: http://wiki.centos.org/SpecialInterestGroup/NFV
LOCATION:#centos-meeting
@@ -259,7 +259,7 @@ RRULE:FREQ=MONTHLY;BYDAY=1TU
DESCRIPTION:Project: Storage SIG\nChair: Karanbir Singh (kbsingh)\, Niel
s de Vos (ndevos)\, Giulio Fidente (gfidente)\nDescription: The CentOS St
orage Special Interest Group (SIG) is a collection of like-minded individu
- als coming together to ensure that CentOS is a suitable platform for many
+ als coming together to ensure that CentOS is a suitable platform for many
different storage solutions. This group will ensure that all Open Source s
torage options seeking to utilize CentOS as a delivery platform have a voi
ce in packaging\, orchestration\, deployment\, and related work. We meet m
diff --git a/community/stories.md b/community/stories.md
index fad00d8..36980d3 100644
--- a/community/stories.md
+++ b/community/stories.md
@@ -4,7 +4,6 @@ title_lead: |
The CentOS ecosystem has been built up with and around people. With no real
commercial ambition we set out to try and solve problems for people as they
exist in the sysadmin / operations trenches around the world.
-layout: aside
---
This page will try and collect some of the user stories over the next few
@@ -13,44 +12,44 @@ months. If you have one you'd like to offer up, get in touch with me at
## Major Hayden's story
-I started with Linux in 1998 and my first distribution was Mandrake. My
-PowerPC machines (older Macs) ran Yellow Dog Linux and I really started
-to enjoy using YUP (YUM's predecessor). I transitioned later to Gentoo
-Linux and spent quite a few sleepless nights testing the effects of USE
-flags as I compiled various software packages. Eventually, I stumbled
-upon some of the early Red Hat releases (prior to Enterprise Linux) and
-I enjoyed the ease of use and stability of the releases. It seemed like
-so many other distributions were being pulled in multiple directions but
+I started with Linux in 1998 and my first distribution was Mandrake. My
+PowerPC machines (older Macs) ran Yellow Dog Linux and I really started
+to enjoy using YUP (YUM's predecessor). I transitioned later to Gentoo
+Linux and spent quite a few sleepless nights testing the effects of USE
+flags as I compiled various software packages. Eventually, I stumbled
+upon some of the early Red Hat releases (prior to Enterprise Linux) and
+I enjoyed the ease of use and stability of the releases. It seemed like
+so many other distributions were being pulled in multiple directions but
the group working on Red Hat was highly organized.
-When Red Hat switched to the Enterprise Linux model, I didn't have the
-large sums of money available to purchase the support licenses. After
-all, I was just a college student at the time. CentOS was a welcomed
-find and I was able to get it running quickly with my previous Red Hat
+When Red Hat switched to the Enterprise Linux model, I didn't have the
+large sums of money available to purchase the support licenses. After
+all, I was just a college student at the time. CentOS was a welcomed
+find and I was able to get it running quickly with my previous Red Hat
knowledge.
-Linux has always been enjoyable for me because I don't have to fork over
-large sums of money for Windows licenses on multiple machines. It's also
-really rewarding to teach other people how to use Linux-based operating
-systems and I love seeing the smiles on their faces when they see how
+Linux has always been enjoyable for me because I don't have to fork over
+large sums of money for Windows licenses on multiple machines. It's also
+really rewarding to teach other people how to use Linux-based operating
+systems and I love seeing the smiles on their faces when they see how
much they can do with a free, open source operating system.
-When I started at Rackspace six years ago, I worked in support and spent
-much of my time assisting customers with servers running Red Hat. That
-led me to a position in our Cloud Servers product group as a Linux
-Engineer. We worked through the Slicehost acquisition and eventually
-created a brand new cloud compute offering with OpenStack. My
-contributions were a small part of what became The Rackspace Open Cloud
-servers product. The knowledge we gained from operating such a large
-multi-tenant virtualization solution was poured into our new offering
-and we're excited to be working closely with the OpenStack community for
-features and bug fixes. My focus has shifted a bit as the Chief
-Security Architect at Rackspace but I'm still a big fan of CentOS for my
+When I started at Rackspace six years ago, I worked in support and spent
+much of my time assisting customers with servers running Red Hat. That
+led me to a position in our Cloud Servers product group as a Linux
+Engineer. We worked through the Slicehost acquisition and eventually
+created a brand new cloud compute offering with OpenStack. My
+contributions were a small part of what became The Rackspace Open Cloud
+servers product. The knowledge we gained from operating such a large
+multi-tenant virtualization solution was poured into our new offering
+and we're excited to be working closely with the OpenStack community for
+features and bug fixes. My focus has shifted a bit as the Chief
+Security Architect at Rackspace but I'm still a big fan of CentOS for my
personal projects.
-If you'd like to get in touch with me, find me on Twitter[1] or on IRC
-(mhayden on Freenode). I've made plenty of posts regarding CentOS,
-Red Hat, and Fedora tips on my blog[2] and I maintain some Fedora/EPEL
+If you'd like to get in touch with me, find me on Twitter[1] or on IRC
+(mhayden on Freenode). I've made plenty of posts regarding CentOS,
+Red Hat, and Fedora tips on my blog[2] and I maintain some Fedora/EPEL
packages[3] that may be of interest.
1. [http://twitter.com/majorhayden/](http://twitter.com/majorhayden/)
@@ -68,4 +67,3 @@ At my current company we used to use OpenSuSE for various tasks i.e. syslog, rsy
For the foreseeable future, the core SIG will probably be the part of CentOS in which I will be most interested/most used by me.
It is also looking like we will be deploying some more machines with CentOS6 at work, as running typo3 and wordpress is starting to pick up momentum there.
-
diff --git a/distro-faq.md b/distro-faq.md
index 45a00eb..ba627f4 100644
--- a/distro-faq.md
+++ b/distro-faq.md
@@ -1,6 +1,5 @@
---
title: FAQ - CentOS Project shifts focus to CentOS Stream
-layout: aside
---
The future of the CentOS Project is CentOS Stream, and over the next year we’ll be shifting focus from CentOS Linux, the rebuild of Red Hat Enterprise Linux (RHEL), to CentOS Stream, which tracks just ahead of a current RHEL release. CentOS Linux 8, as a rebuild of RHEL 8, will end at the end of 2021. CentOS Stream continues after that date, serving as the upstream (development) branch of Red Hat Enterprise Linux. [Read the rest of our announcement](https://blog.centos.org/2020/12/future-is-centos-stream/).
@@ -38,7 +37,7 @@ We will not be producing a CentOS Linux 9, as a rebuild of RHEL 9. Instead CentO
### Q4: How will CVEs be handled in CentOS Stream?
-**A:** Security issues will be updated in CentOS Stream after they are solved in the current RHEL release. Obviously, embargoed security releases can not be publicly released until after the embargo is lifted. While there will not be any SLA for timing, Red Hat Engineers will be building and testing other packages against these releases. If they do not roll in the updates, the other software they build could be impacted and therefore need to be redone. There is therefore a vested interest for them to get these updates in so as not to impact their other builds and there should be no issues getting security updates.
+**A:** Security issues will be updated in CentOS Stream after they are solved in the current RHEL release. Obviously, embargoed security releases can not be publicly released until after the embargo is lifted. While there will not be any SLA for timing, Red Hat Engineers will be building and testing other packages against these releases. If they do not roll in the updates, the other software they build could be impacted and therefore need to be redone. There is therefore a vested interest for them to get these updates in so as not to impact their other builds and there should be no issues getting security updates.
### Q5: Does this mean that CentOS Stream is the RHEL BETA test platform now?
@@ -50,14 +49,14 @@ We will not be producing a CentOS Linux 9, as a rebuild of RHEL 9. Instead CentO
**A:** Each major release will have a branch, similar to how CentOS Linux is currently structured; however, CentOS Stream is designed to focus on RHEL development, so only the latest Stream will have the marketing focus of the CentOS Project.
-Because RHEL development cycles overlap, there will be times when there are multiple code branches in development at the same time.This allows users time to plan migrations and development work without being surprised by sudden changes.
+Because RHEL development cycles overlap, there will be times when there are multiple code branches in development at the same time.This allows users time to plan migrations and development work without being surprised by sudden changes.
Specifically, since the RHEL release cadence is every 3 years, and the full support window is 5 years, this gives an overlap of approximately 2 years between one stream and the next.
### Q7: How do I migrate my CentOS Linux 8 installation to CentOS Stream?
-**A:** Instructions to convert from the CentOS Linux 8 distribution to CentOS Stream 8 are published at
+**A:** Instructions to convert from the CentOS Linux 8 distribution to CentOS Stream 8 are published at
[https://www.centos.org/centos-stream/](https://www.centos.org/centos-stream/)
and are also below for your convenience.
@@ -91,9 +90,9 @@ This will result in some package updates and new packages being installed, which
### Q12: I used CentOS for CI because I could not use RHEL developer licenses for this. CentOS Stream is aimed at the next generation when I need the last/current one. What is my alternative?
-**A:** Red Hat is aware of these concerns and we encourage you to [talk to them](mailto:centos-questions@redhat.com). If you’re testing for RHEL, RHEL is the best operating system to use. We also think that CentOS Stream has a place in your CI testing to help you be ready for the next RHEL.
+**A:** Red Hat is aware of these concerns and we encourage you to [talk to them](mailto:centos-questions@redhat.com). If you’re testing for RHEL, RHEL is the best operating system to use. We also think that CentOS Stream has a place in your CI testing to help you be ready for the next RHEL.
+
-
### Q13: Can I start up a SIG that will maintain CentOS Stream 8 after RHEL8 reaches the end of Full Support?
**A:** We will not be putting hardware, resources, or asking volunteers to work towards that effort, nor will we allow the CentOS brand to be used for such a project. Once RHEL8 reaches the end of full support, CentOS Stream 8 will be retired from build servers, community build systems, primary mirror sites (copies will remain on vault.centos.org), and other places within our ecosystem. Having SIGs build against multiple streams, and packaging/distributing multiple streams, once they are no longer active, is a distraction from what we want to be our main focus - the active stream that precedes the next RHEL release.
@@ -108,4 +107,3 @@ This will result in some package updates and new packages being installed, which
### Q16: Where can I ask more questions?
**A:** Since many people will have the same questions, we encourage you to ask your questions on the public project mailing list, [devel](https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/), where everyone can benefit from the questions and answers being publicly archived. However, we will also be watching our various social media accounts for questions and comments.
-
diff --git a/download.md b/download.md
index 5db6bb2..1b3e1ee 100644
--- a/download.md
+++ b/download.md
@@ -1,6 +1,5 @@
---
title: Download
-layout: aside
---
-{% include download/cards.html %}
+{% include download/cards.html id="DownloadsCard-1"
+with_title=true
+with_description=true
+with_releases=true
+with_screenshots=true
+with_mirrors=true
+with_documentation=true
+with_eol=true
+with_commands=false
+%}
As you download and use CentOS Linux or CentOS Stream \([What's the
difference?](/cl-vs-cs/)\), the CentOS Project invites you to [be a part of the
@@ -63,7 +71,7 @@ This is documented in greater detail in the [CentOS wiki](https://wiki.centos.or
In order to help ease the workload for our primary mirror network, the source
rpms are not kept in the same tree as the binary packages. If you need the
-source packages used to build CentOS, you can find them in our vault
+source packages used to build CentOS, you can find them in our vault
[vault.centos.org](http://vault.centos.org).
## Older Versions
diff --git a/download/aws-images.md b/download/aws-images.md
index a4a2b76..66af50c 100644
--- a/download/aws-images.md
+++ b/download/aws-images.md
@@ -1,6 +1,5 @@
---
title: "CentOS AWS AMI Cloud Images"
-layout: download-mirror
---
CentOS Amazon AMI images
@@ -15,7 +14,7 @@ So far we build/update/maintain the following CentOS variants and architectures:
You can search for architecture or region through search bar.
-Please note that you can also directly use then the "Deploy Link" function to deploy in specific region, one click away.
+Please note that you can also directly use then the "Deploy Link" function to deploy in specific region, one click away.
diff --git a/download/mirrors-altarch.md b/download/mirrors-altarch.md
index 3c40de9..5ca4b06 100644
--- a/download/mirrors-altarch.md
+++ b/download/mirrors-altarch.md
@@ -1,7 +1,6 @@
---
title: AltArch Mirror List
title_lead: List of CentOS Mirrors providing alternative arquitectures.
-layout: download-mirror
---
CentOS welcomes new mirror sites. If you are considering setting up a public
diff --git a/download/mirrors.md b/download/mirrors.md
index a500610..5c276ae 100644
--- a/download/mirrors.md
+++ b/download/mirrors.md
@@ -1,7 +1,6 @@
---
title: Mirror List
title_lead: List of CentOS official mirrors.
-layout: download-mirror
---
@@ -11,7 +10,7 @@ Starting from CentOS Stream 9 , mirrors are listed in Mirrormanager so use
Key fingerprint = 2C77 CFEB 1F99 C559 E52B 3CDC 8DEF 9614 B094 B96D
@@ -240,5 +239,3 @@ Community driven ports of CentOS to other platforms.
pub 2048R/F533F4FA 2015-11-27 CentOS AltArch SIG - PowerPC (https://wiki.centos.org/SpecialInterestGroup/AltArch)
Key fingerprint = BAFA 3436 FC50 768E 3C3C 2E4E A963 BBDB F533 F4FA
-
-
diff --git a/keys/RPM-GPG-KEY-CentOS-5 b/keys/RPM-GPG-KEY-CentOS-5
index 2627d31..69676d9 100644
--- a/keys/RPM-GPG-KEY-CentOS-5
+++ b/keys/RPM-GPG-KEY-CentOS-5
@@ -25,4 +25,3 @@ GwwFCRLMAwAACgkQqKRH3OhWKJfvvACfbsF1WK193zM7vSc4uq51XsceLwgAoI0/
9GxdNhGQEAweSlQfhPa3yYXH
=o/Mx
-----END PGP PUBLIC KEY BLOCK-----
-
diff --git a/keys/RPM-GPG-KEY-CentOS-SIG-AltArch-Arm32 b/keys/RPM-GPG-KEY-CentOS-SIG-AltArch-Arm32
index f0a6dbd..54fe3db 100644
--- a/keys/RPM-GPG-KEY-CentOS-SIG-AltArch-Arm32
+++ b/keys/RPM-GPG-KEY-CentOS-SIG-AltArch-Arm32
@@ -18,4 +18,3 @@ gllMZz1Bdp+V51zndIm7Fe1d6jcSEjpPjRecIxfr5PBLAu3j/VbjBK90u8AKSKY9
q5eFcyxxA1r2IdmItGVwz73gSz8WkJoh8QeN
=72OZ
-----END PGP PUBLIC KEY BLOCK-----
-
diff --git a/keys/RPM-GPG-KEY-CentOS-SIG-AltImages b/keys/RPM-GPG-KEY-CentOS-SIG-AltImages
index 2788eba..d0690d2 100644
--- a/keys/RPM-GPG-KEY-CentOS-SIG-AltImages
+++ b/keys/RPM-GPG-KEY-CentOS-SIG-AltImages
@@ -36,4 +36,3 @@ tCHOvfQ16wkHW9Av8FYIbptW5bk2OKNh1hHb2yJ60DxEJeDh1B0JyiBbmL5Bf6jN
sKUPc+wYkgeuP5/TSaJrUoS/LXZX6IpyqQ==
=wA0g
-----END PGP PUBLIC KEY BLOCK-----
-
diff --git a/keys/RPM-GPG-KEY-CentOS-SIG-Extras b/keys/RPM-GPG-KEY-CentOS-SIG-Extras
index f49a9e1..e15f9a8 100644
--- a/keys/RPM-GPG-KEY-CentOS-SIG-Extras
+++ b/keys/RPM-GPG-KEY-CentOS-SIG-Extras
@@ -35,4 +35,3 @@ Boc66IZ0J5pmSzgJnSbLrr2dv1/jYHaolA24vkMqMxKzJbz+GeQ/SqBZ5/rA37VL
x90Tu9UVSfbyEbwS9Zj1sVmc3mdm1kn6dmTlOfTDIqehfHBlnQ==
=jx2B
-----END PGP PUBLIC KEY BLOCK-----
-
diff --git a/keys/RPM-GPG-KEY-CentOS-SIG-ISA b/keys/RPM-GPG-KEY-CentOS-SIG-ISA
index 6c846ef..2eaa69e 100644
--- a/keys/RPM-GPG-KEY-CentOS-SIG-ISA
+++ b/keys/RPM-GPG-KEY-CentOS-SIG-ISA
@@ -36,4 +36,3 @@ ftGqXh7xNzEXeCG9OrcDIz0y1DTWR32B+RXkLf64x0hlvWJiCc4QVWphidj5IW+6
po0pa45/4grTi+p3SQ==
=HN07
-----END PGP PUBLIC KEY BLOCK-----
-
diff --git a/legal.md b/legal.md
index 42ae448..998891a 100644
--- a/legal.md
+++ b/legal.md
@@ -1,6 +1,5 @@
---
title: "CentOS Legal"
-layout: aside
---
## Export Compliance/Customs Information
@@ -44,7 +43,7 @@ To file a counter notification with us, please provide the following information
* Your name, address, telephone number, email address, and a statement that you consent to the jurisdiction of the Federal District Court for the judicial district in which your address is located (or Wake County, North Carolina if your address is outside of the United States), and that you will accept service of process from the person who provided notification of infringement or an agent of such person.
* The following statement: "I swear, under penalty of perjury, that I have a good faith belief that the material identified above was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled."
* Your electronic or physical signature.
-
+
Red Hat has registered a designated agent with the Copyright Office pursuant to 17 U.S.C. 512(c). Please send notifications of infringement and counter notifications to the designated agent at:
Assistant General Counsel
diff --git a/legal/licensing-policy.md b/legal/licensing-policy.md
index 1143aa1..c49e06b 100644
--- a/legal/licensing-policy.md
+++ b/legal/licensing-policy.md
@@ -1,15 +1,14 @@
---
title: "CentOS Project Licensing Policy"
-layout: aside
---
# CentOS Project licensing policy
## Definitions
-A “Contribution” is any contribution to the CentOS Project, but does not include (a) already-existing upstream software or content that merely is packaged, or is intended to be packaged, in CentOS Linux or CentOS Stream, or changes or additions to such already-existing software or content, or (b) material intended to be used for CentOS project logos.
+A “Contribution” is any contribution to the CentOS Project, but does not include (a) already-existing upstream software or content that merely is packaged, or is intended to be packaged, in CentOS Linux or CentOS Stream, or changes or additions to such already-existing software or content, or (b) material intended to be used for CentOS project logos.
-Your Contribution is “Explicitly Licensed” if you specifically attach a license notice to it.
+Your Contribution is “Explicitly Licensed” if you specifically attach a license notice to it.
“Default License” means the license you grant under this policy for a Contribution that is not Explicitly Licensed.
@@ -17,9 +16,9 @@ Your Contribution is “Explicitly Licensed” if you specifically attach a lice
## Distributions
-The CentOS Linux and CentOS Stream distributions are [compilations](https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=17-USC-2076770877-364936160&term_occur=999&term_src=title:17:chapter:1:section:101) of software packages. Each package is governed by its own license. Like Red Hat Enterprise Linux, the CentOS Linux and CentOS Stream compilation copyright is licensed under [GPLv2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html). To the extent you hold any copyright in the selection, coordination, or arrangement of packages making up the CentOS Linux or CentOS Stream distributions, you license that copyright under GPLv2.
+The CentOS Linux and CentOS Stream distributions are [compilations](https://www.law.cornell.edu/definitions/uscode.php?width=840&height=800&iframe=true&def_id=17-USC-2076770877-364936160&term_occur=999&term_src=title:17:chapter:1:section:101) of software packages. Each package is governed by its own license. Like Red Hat Enterprise Linux, the CentOS Linux and CentOS Stream compilation copyright is licensed under [GPLv2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html). To the extent you hold any copyright in the selection, coordination, or arrangement of packages making up the CentOS Linux or CentOS Stream distributions, you license that copyright under GPLv2.
-The compilation license does not supersede the licenses of code and content contained in the distributions, including anything you may have contributed to that pre-existing material. The complete licensing terms applicable to a given package can be found in the source code of the package.
+The compilation license does not supersede the licenses of code and content contained in the distributions, including anything you may have contributed to that pre-existing material. The complete licensing terms applicable to a given package can be found in the source code of the package.
## Explicitly Licensed Contributions
@@ -27,11 +26,11 @@ Explicitly Licensed Contributions can be under any of the open source or open co
## CentOS.org Content
-As of 2020-04-23, new content published on [www.centos.org](https://www.centos.org/), [wiki.centos.org](https://wiki.centos.org), [docs.centos.org](https://docs.centos.org), and [blog.centos.org](https://blog.centos.org) is licensed under the Creative Commons Attribution-ShareAlike 4.0 [International Public License](https://creativecommons.org/licenses/by-sa/4.0/) (CC BY-SA 4.0), except as otherwise indicated in this document or the content itself. Accordingly, the Default License for Contributions to such content is CC BY-SA 4.0, with attribution solely to the CentOS Project.
+As of 2020-04-23, new content published on [www.centos.org](https://www.centos.org/), [wiki.centos.org](https://wiki.centos.org), [docs.centos.org](https://docs.centos.org), and [blog.centos.org](https://blog.centos.org) is licensed under the Creative Commons Attribution-ShareAlike 4.0 [International Public License](https://creativecommons.org/licenses/by-sa/4.0/) (CC BY-SA 4.0), except as otherwise indicated in this document or the content itself. Accordingly, the Default License for Contributions to such content is CC BY-SA 4.0, with attribution solely to the CentOS Project.
## Licensed Repositories
-The Default License for Contributions to a CentOS Project repository that contains notice of a license is that same license.
+The Default License for Contributions to a CentOS Project repository that contains notice of a license is that same license.
## Code Contributions
@@ -39,21 +38,21 @@ The Default License for Contributions of Code is the MIT license, as follows:
Copyright Contributors to the CentOS Project.
- Permission is hereby granted, free of charge, to any person obtaining a copy of
+ Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in the
- Software without restriction, including without limitation the rights to use,
+ Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
- Software, and to permit persons to whom the Software is furnished to do so,
+ Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
- The above copyright notice and this permission notice shall be included in all
+ The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
- INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
+ INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
- HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
- OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+ HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
## Other Contributions
@@ -66,5 +65,4 @@ CentOS logos are covered by the [CentOS Trademark Guidelines](https://www.centos
## Date
-This policy is in effect as of 2020-04-23.
-
+This policy is in effect as of 2020-04-23.
diff --git a/legal/privacy.md b/legal/privacy.md
index f4fd29c..c7b576f 100644
--- a/legal/privacy.md
+++ b/legal/privacy.md
@@ -1,6 +1,5 @@
---
title: "CentOS Privacy Policy"
-layout: aside
---
## Scope of this Notice
@@ -9,7 +8,7 @@ This Privacy Statement is intended to describe the CentOS Project's privacy
practices and to provide information about the choices you have regarding the
ways in which information is collected by the CentOS Project is used and
disclosed. For Convenience, the CentOS Project is referred to in this document
-as "CentOS".
+as "CentOS".
## Our Commitment to Privacy
diff --git a/legal/trademarks.md b/legal/trademarks.md
index e36b7d1..1e108c1 100644
--- a/legal/trademarks.md
+++ b/legal/trademarks.md
@@ -1,6 +1,5 @@
---
title: "CentOS Trademark Guidelines"
-layout: aside
---
## Introduction
@@ -20,7 +19,7 @@ Red Hat welcomes the assistance of the entire CentOS community in reporting non-
## General Principles
-Whenever you use the CentOS Marks, you must do so in a way that does not mislead others, either directly or by omission, concerning what they are obtaining and from whom. The law reflects this requirement in two principal ways: it prohibits creation of a "likelihood of confusion" but allows for "nominative use".
+Whenever you use the CentOS Marks, you must do so in a way that does not mislead others, either directly or by omission, concerning what they are obtaining and from whom. The law reflects this requirement in two principal ways: it prohibits creation of a "likelihood of confusion" but allows for "nominative use".
For example, you are not allowed to say you are distributing CentOS software when you are actually distributing some downstream modification of an official CentOS release ("Official" packages, builds, and releases are those that have been approved for the CentOS Project's release by the CentOS Project) . Otherwise, your recipients would be confused if they do not receive the same features and functionality they would have obtained had they received software officially released by the CentOS Project. As another example, you are not allowed to use the Logos on your website in a way that suggests that your website is an official website of the CentOS Project, or that the CentOS Project endorses your website. On the other hand, you may of course say, for example, that you like the CentOS software distribution or that you participate in the CentOS Project.
@@ -40,7 +39,7 @@ Trademark law does not allow your use of names or trademarks that are confusingl
4. You may use the 'Powered by CentOS' logo to truthfully state that your application runs on or uses an official CentOS release.
-5. You may use the CentOS Marks in themes, personas, or skins for applications to show your support for the CentOS Project, provided that the use is noncommercial and is clearly decorative, as contrasted with a use that is likely to be understood as the branding for a website or application.
+5. You may use the CentOS Marks in themes, personas, or skins for applications to show your support for the CentOS Project, provided that the use is noncommercial and is clearly decorative, as contrasted with a use that is likely to be understood as the branding for a website or application.
### Unacceptable uses
@@ -89,8 +88,8 @@ Notwithstanding anything to the contrary provided in these Guidelines, the follo
* Acceptable: I installed a CentOS release on my friend's laptop.
* Don't use a trademark as a verb.
* Unacceptable: We are CentOSing our servers.
- * Acceptable: We are installing the CentOS distribution on our servers.
-* Don't use a trademark as a possessive.
+ * Acceptable: We are installing the CentOS distribution on our servers.
+* Don't use a trademark as a possessive.
* Unacceptable: CentOS's distribution is stable.
* Acceptable: The CentOS distribution is stable.
diff --git a/news-and-events.md b/news-and-events.md
index af87b5d..6004911 100644
--- a/news-and-events.md
+++ b/news-and-events.md
@@ -1,8 +1,6 @@
---
title: News and Events
title_lead: News, views, and reports on CentOS.
-layout: blog
-pagination:
+pagination:
enabled: true
---
-
diff --git a/sponsors.md b/sponsors.md
index f95ab78..7d11b86 100644
--- a/sponsors.md
+++ b/sponsors.md
@@ -1,6 +1,5 @@
---
title: "Sponsors"
-layout: sponsors
---
If you are interested in becoming a CentOS sponsor, you can contact the us at .
diff --git a/stream9.md b/stream9.md
index f6e9a15..a2a4faa 100644
--- a/stream9.md
+++ b/stream9.md
@@ -1,6 +1,5 @@
---
title: CentOS Stream 9
-layout: page
permalink: /:path/:basename/index.html
toc: true
---
@@ -44,4 +43,3 @@ Notable community contributions so far:
* Davide Cavalca added default configs to enable systemd-oomd and make it usable out of the box ([BZ#1962255](https://bugzilla.redhat.com/show_bug.cgi?id=1962255))
* Neal Gompa added Wayland support for the GNOME Classic session ([BZ#2015914](https://bugzilla.redhat.com/show_bug.cgi?id=2015914))
* Andrew Lukoshko added product config for AlmaLinux ([BZ#2004653](https://bugzilla.redhat.com/show_bug.cgi?id=2004653))
-
diff --git a/variants.md b/variants.md
index 6b4c7b5..e1eb85e 100644
--- a/variants.md
+++ b/variants.md
@@ -5,7 +5,6 @@ title_lead: |
core distribution, then replaces or supplements a specific subset of
packages. This may include replacing everything down to the kernel,
networking, and other subsystems.
-layout: aside
---
Some open source projects need different software components to run properly, such as updated development languages or kernel functionality. By being able to get these components directly in CentOS, a variant maintainer solves many of the steps for users.