devel September 2023

devel@lists.centos.org

17 participants
14 discussions

Archiving wiki.centos.org (next week)
by Fabian Arrotin 14 Sep '23

14 Sep '23

As discussed multiple times either on centos-devel list (for example https://lists.centos.org/pipermail/centos-devel/2023-February/142773.html) or during last docs hackaton in Brussels (day after Fosdem), it was decided to just archive the wiki as static html files (exported from moin) and just have these available through git repository The ticket to track this is https://pagure.io/centos-infra/issue/1245 As we need to also migrate/move that VM elsewhere, and itself disappearing when CentOS Linux 7 will be EOL, and because the PoC was enough, I intend to do the following next monday (September 11th): - snapshot wiki.centos.org content (frozen) - export to html static page - import that back in dedicated git repository (https://gitlab.com/CentOS/docs/wiki_archives- - have a new vhost that would just pull from that git repository (if anything was modified/updated) and still content served from https://wiki.centos.org (so that existing links would still work) From that point, it's up to CentOS Docs SIG to decide how/where to put content, but most of the SIGs already moved content elsewhere (usually under https://sigs.centos.org) but in the meantime, it will still be possible to just use git workflow on html files to modify/update/remove content as needed (interim solution) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 3

2023-09-13 - CentOS Public Board Meeting
by Thomas Oulevey 09 Sep '23

09 Sep '23

Hi Everyone, Our next board meeting will take place at 20:00 UTC on next Wednesday: `date -d "2023-09-13 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/@centosboard/H1XiSh7ah As a reminder we will enforce few rules : * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redaction, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. I hope some of you can join. Sorry for the late announcement. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

An update on RHEL moving to issues.redhat.com
by Brendan Conoboy 08 Sep '23

08 Sep '23

Hi folks, In March of this year, Josh Boyer sent out a message to Fedora's devel list letting everybody know RHEL was going to move from bugzilla.redhat.com to issues.redhat.com (Jira) in the future [1]. The work on this activity has proceeded with relative quiet since, although a couple weeks ago Florian mentioned on centos-devel that Platform Tools had begun to move [2]. I'm now providing a more official followup: All new issues found or desired in RHEL (Or CentOS Stream) need to be filed on issues.redhat.com. It's no longer possible to create new BZs for current RHEL (7 through 9) releases. Over the next few weeks, most RHEL BZs will be migrated to tickets in the RHEL project on issues.redhat.com. The BZs that are migrated will be closed with resolution MIGRATED and a pointer to the Jira issue included in the external links section of each respective BZ. Issues that don't get migrated may still be worked on in Bugzilla- only new BZ creation is disabled, and only disabled in RHEL products. Like before, most new RHEL issues are publicly visible by default, without any login required to view. As CentOS Stream development *is* direct RHEL development, this is a definite change, but hopefully only skin-deep. As an example, previously you might have created a RHEL 9 BZ with the Version field set to "CentOS Stream". On issues.redhat.com you would do the same thing by creating an issue in the RHEL project with the "Affects Version" set to "CentOS Stream 9". People are welcome to create an account on issues.redhat.com, just like was done on bugzilla.redhat.com previously, see what we're up to, file issues, and contribute there as well. We've created a hopefully-helpful article with account basics to get your account setup [3]. I've sent a corresponding message to fedora-devel, so apologies if you're reading this a second time. References: 1. Initial Announcement - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… 2. Migration Starting - https://lists.centos.org/pipermail/centos-devel/2023-August/143056.html 3. Issues.redhat.com account basics - https://access.redhat.com/articles/7032570 -- Brendan Conoboy / CASE & CPE / Red Hat, Inc.

1 0

Proposal for documentation layout on docs.centos.org
by Aleksandra Fedorova 06 Sep '23

06 Sep '23

Hi, folks, I was playing with the ways to organize the CentOS Documentation site and came up with the following proposal: https://hackmd.io/@bookwar/centos-docs-layout The link has more details but in short we need three categories of content: * User Documentation: everything about installing and administering the CentOS system. Large guides go here, as well as small Knowledge Base articles. * Project Documentation: All about processes and policies of the CentOS Project. * SIGs documentation: Documentation subtrees maintained by each Special Interest group on their own. Note that by SIG docs here I mean documentation written and owned by individual special interest groups. The current SIG Guide (https://sigs.centos.org/guide/) belongs to the "Project Documentation" section in this hierarchy. Each top-level item is then expanded to more sub-levels. For many of the items mentioned in the proposal we do not have the content written yet. But if we agree on the layout, we can start by rearranging existing documents to fit the hierarchy. Then we will be able to use the proposed map for any new content, which we add in the future. -- Aleksandra Fedorova Matrix: @bookwar:fedora.im Fediverse: @bookwar@fosstodon.org

4 5

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2023