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
Hi,
There is some documentation in progress about "base/default" layout,
the default layout that jekyll-theme-centos will be using to render
content. You can check it on the following URL:
https://centos.gitlab.io/artwork/centos-web/jekyll-theme-centos-base/docume…
This page is also an example of how the content presentation looks like
when you use the "base/default" layout in your site.
I would like to request some feedback from you about the "base/default"
layout features and visual presentation as well. Appreciate your
comments and concerns here.
Thanks!
--
Alain Reguera Delgado <alain.reguera(a)gmail.com>
January 2023 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat -
chair
_____________________________________
Membership update
This SIG does not have a formal membership process. The mailing list
currently has 106 subscribers representing at least 32 organizations,
though not all subscribers use corporate emails and some are participating
as individuals.
_____________________________________
Releases in the most recent quarter (or most recent release, if none in
that quarter)
The Automotive SIG produces three types of artifacts:
- AutoSD, a streaming distribution of CentOS designed for in-vehicle
automotive use cases.
- An Automotive SIG RPM repository that allows the community to expand the
content of AutoSD or experiment with some of its parts.
- Sample images, built using OSBuild, which provide examples of how to
assemble production images based on AutoSD, customized for some hardware,
including container images, based on CoreOS/ostree technologies.
AutoSD, or Automotive Stream Distribution, is a streaming distribution for
automotive in-vehicle software development based on CentOS Stream. It
is transparently the upstream project for Red Hat's eventual in-vehicle OS
product. AutoSD has been downloaded and used by many organizations who have
commented or asked for help, so we know it is getting some traction though
of course we don't have exact metrics on usage.
In Q4 2022, we released a version of AutoSD compatible with the emerging
SOAFEE specification. SOAFEE (https://soafee.io) is an initiative driven by
Arm for the purpose of developing a reference specification for Arm-based
software-defined vehicles (SDVs) consisting of an operating system,
container orchestration strategy, and application layer. In addition, we
introduced a very lightweight container runtime based on podman and systemd
that does not include Kubernetes, as the latter represented a significant
performance hit on all relevant hardware. We presented at the Arm Developer
Summit in November on these topics.
In the coming quarter, we plan to tighten up documentation, begin a process
for accepting and supporting hardware enablement contributions, and
continue to develop AutoSD toward the SOAFEE specification while also
contributing to that specification within the SOAFEE community.
_____________________________________
Health report and general activity narrative
The SIG typically has 1 public meeting per month with 25-40 attendees, with
visible participation from 7-10 separate organizations. We have largely
given up on a separate office hours meeting due to attendance.
This SIG is intended to be a community effort with contributions and shared
benefits from all participants. All formal meetings are recorded and posted
on this page:
https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings
Several Red Hat employees made the initial contributions to the project as
well as the infrastructure required to build and test it. We occupy a
gitlab repository in the CentOS namespace building software regularly using
CI, with build instructions provided on the documentation page at
https://sigs.centos.org/automotive/ . Sample images are present and
downloadable along with customization and build instructions.
_____________________________________
Issues for the board to address, if any
None, keep up the excellent work :)
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
The board had its monthly meeting last week. The recording, minutes,
and recap are all available.
Recording:
https://www.youtube.com/watch?v=2pWqcs4LJq8
Minutes:
https://hackmd.io/@centosboard/r14tdu5j2
Recap:
https://blog.centos.org/2023/08/centos-board-meeting-recap-august-2023/
We'll have the followup office hours this Thursday, August 24, at 14:00
UTC. Everybody is welcome to join and talk to the baord.
https://meet.google.com/nkj-psxs-urg
Highlights of the recap:
* We got an update on the status of trusting SIGs for secureboot (Issue
67).
* We discussed issues that have arisen with bridging Matrix to IRC
(Issue 116).
* We discussed guidelines for SIGs to publish images on Quay (Issue
90).
* The community architect gave a report from CentOS Connect and Flock.
* We briefly discussed the contributor docs, SIG health checkins, and
Promo SIG activity.
* We had some early discussions around planning CentOS Connect at
FOSDEM.
* We talked about various alternatives to using Zoom for board and SIG
meetings.
Hi folks,
The CloudSIG meeting, planned at 1500 UTC on Thursday 10th August, is
cancelled.
It will resume as normal on #centos-meeting channel at 1500 UTC on Thursday
14th September.
Regards,
Joel
Hi Everyone,
Our next board meeting will take place at 20:00 UTC on Wednesday:
`date -d "2023-08-09 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 Zoom 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/r14tdu5j2
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
I forgot to post the minutes immediately after the meeting.
Key points discussed were:
So far, there is no round of new rebuilds with GCC 13 scheduled.
The recommended way for installation remains starting out with CentOS
Stream and using dnf distro-sync. See
<https://sigs.centos.org/isa/consuming/centosstream9/>. Starting with
RHEL 9.2 results in cross-grade issues. If the update from c9s breaks,
we may have to rebuild some more packages.
Thanks,
Florian
Due to a hardware replacement and storage reorg, we'll have to move the
existing CentOS Community Build System (aka https://cbs.centos.org) to a
new node.
Migration is scheduled for """"Thursday August 3rd, 6:30 am UTC time"""".
You can convert to local time with $(date -d '2023-08-03 06:30 UTC')
The expected "downtime" is estimated to ~45 minutes , time needed to :
- stop kojid instances
- move kojihub instance and restore data
- reconfigure kojid builders to point to new storage location
Thanks for your understanding and patience.
on behalf of the Infra team,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi Carlos,
On Tue, Jul 25, 2023 at 12:15 PM Frantisek Lachman <flachman(a)redhat.com>
wrote:
>
>
> ---------- Forwarded message ---------
> From: Carlos Rodriguez-Fernandez <carlosrodrifernandez(a)gmail.com>
> Date: Tue, Jul 25, 2023 at 4:53 AM
> Subject: [CentOS-devel] [t_functional sig] Tests management with TMT
> To: <centos-devel(a)centos.org>
>
>
> Hi,
>
> Is there any interest or already a plan to convert the test management
> of the t_functional tests to TMT (https://github.com/teemtee/tmt)?
>
Note that the conversion might not be even needed, tmt now serves
well as a wrapper over various testing frameworks, many people
use it like that.
> I see that packit.dev and tmt is where fedora is trying to go instead of
> zuul ci,
>
This might be a confusion, note that these systems are on different levels:
* Packit is on the level of upstream project GitHub / GitLab contributions
* Zuul CI for Fedora
<https://fedora.softwarefactory-project.io/zuul/builds?job_name=rpm-tmt-test>
and Zuul CI for CentOS Stream
<https://centos.softwarefactory-project.io/zuul/t/centos/builds?job_name=rpm…>
are on the level of dist-git contributions
All these run tmt tests which can be defined basically in any git
repository (remote or local).
> and also I saw the email from the cloud sig about adopting
> packit.dev. I was wondering how it will impact t_functional.
>
Can you point me to that email please?
> I have been playing with it and seems like a good tool for the job.
>
Glad to hear that :)
Best regards,
/M
>
> Regards,
> Carlos.
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
--
Miroslav Vadkerti :: Senior Principal QE :: Testing Farm / Linux QE
IRC mvadkert #tft #tmt #osci :: Mobile +420 773 944 252
Remote Czech Republic :: Red Hat Czech s.r.o
Hi,
Is there any interest or already a plan to convert the test management
of the t_functional tests to TMT (https://github.com/teemtee/tmt)?
I see that packit.dev and tmt is where fedora is trying to go instead of
zuul ci, and also I saw the email from the cloud sig about adopting
packit.dev. I was wondering how it will impact t_functional.
I have been playing with it and seems like a good tool for the job.
Regards,
Carlos.