Hi all, just a reminder that we will host our first unofficial general chat
& office hours tomorrow, October 1, at 1500UTC (8am PDT, 11am EDT, 5pm CEST)
https://bluejeans.com/870492784
As we discussed in the last call, this meeting has no set agenda and is
totally optional. I expect that we will discuss the current state of the
infrastructure as well as the incoming contribution by Red Hat of an
initial framework so we can start discussions on what to include. I'd also
like to start a discussion on good meeting times - there is no perfect time
for everyone, but I'd like as much feedback as possible for future
scheduling.
So whether you have anything to share or not, please feel free to stop in!
Finally - if you haven't already done so (and if you are interested),
please make sure to subscribe to the automotive SIG mailing list for all
future announcements.
Also, please let me know if you would like to be added to a Google
calendar invite for future meetings - and yes we are looking for a more
universal option.
best regards,
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
Hey everyone,
This came up on the call yesterday to open a discussion about where we
should host our code and I'd like to open it up here for transparency on
the path forward. We have a lot of options in this sphere and all are Git
based.
Historically, CentOS SIGs had their code hosted at https://git.centos.org/.
That's wired up to the CentOS Account system so users can login seamlessly.
Some SIGs have opted to host on Github as well and use their own Github
profile (which is not connected to their CentOS account).
Currently, CentOS Stream is being built in the open at
gitlab.com/redhat/centos-stream where community contributors can create a
Gitlab account and interact with CentOS Stream. Gitlab is not currently
wired into the CentOS Account system and the team is working to get that
integration on the gitlab.com/CentOS project (which is currently dormant).
The suggestion put forward by Pierre-Yves Chibon, who is leading the effort
within Red Hat on creating the services and infrastructure for the SIG, is
to base ourselves on Gitlab. We can create a
gitlab.com/redhat/automotive-sig project and mirror it at
gitlab.com/centos/automotive-sig so we can show people where we will work
once we've resolved the authentication question. The drawback is the need
to use a gitlab.com account, which, in time, we can merge into the CentOS
Account when the integration is completed. The key benefit of having us
base our code on Gitlab is the closeness to Stream from a codebase
perspective and the potential to use similar tools and approaches as their
development workflow.
While no formal decision on where the overall CentOS SIGs will host their
code in the future has been made, the presence of Stream on Gitlab is
potentially future proofing us against a migration.
Does the community have a strong preference for where we should base our
repos? I'm going to suggest we leave this topic percolate for a week to
have some dialog on the best path forward and then create our presence on
the source forge of choice.
Thanks,
Leigh
--
Leigh Griffin
Senior Engineering Manager
Red Hat Waterford <https://www.redhat.com/>
Communications House
Cork Road, Waterford City
lgriffin(a)redhat.com
M: +353877545162 IM: lgriffin
@redhatjobs <https://twitter.com/redhatjobs> redhatjobs
<https://www.facebook.com/redhatjobs> @redhatjobs
<https://instagram.com/redhatjobs>
<https://red.ht/sig>
Hi all - I'd like to propose an informal office hours chat on Friday at
11am EDT, 5pm CEST. This will be an open discussion about automotive
software and the ongoing efforts within the SIG. I'd also like to discuss
meeting schedules going forward so we can make sure to maximize
participation. Hope to see you there.
Friday October 1
1500 UTC / 11am EDT / 5pm CEST
https://bluejeans.com/870492784
Going forward, I would like to maintain these meetings on a SIG calendar,
and I'm exploring how to do that most effectively. Thanks for your patience.
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
Hello,
I would like to hear about the community opinion on this.
The pipeline delivery team currently installs a number of packages in some
of their pipeline tasks, this package list (package + package version) is
stored in a file and that file gets updated when a new version of a listed
package is around in Koji.
The problem is that Koji is being used to check for new package versions
but that doesn't mean a compose was run which can lead to a situation where
mirrors do not have that "latest" package version that was built on koji
(a compose is run weekly).
To illustrate things in a practical way:
- A new version (1.34.0) of NetworkManager was built in koji:
https://koji.mbox.centos.org/koji/packageinfo?packageID=1433;
- The package is not available in centos mirrors (yet):
http://mirror.centos.org/centos/8-stream/BaseOS/aarch64/os/Packages/ ;
- The package gets updated in this file:
https://gitlab.com/redhat/edge/ci-cd/manifests/-/blob/update-package-Networ…
;
- The pipeline job fails because yum can't find that version of the
package in the BaseOS repository.
I know that we can download those RPMs directly from Koji but I was
wondering if this is where the SIG could/should step in and make the user
experience a bit better by providing a single source of truth, be it a
repository or some tooling, to retrieve package info and show where they
stand.
Any thoughts on this?
Thanks!
--
Leonardo Rossetti
Red Hat <https://www.redhat.com>
lrossett(a)redhat.com
<https://www.redhat.com>
Hi all - here is a link to the video recording from yesterday's call
https://www.youtube.com/watch?v=b0pUDb_BWSQ
I will be putting together a poll to make sure the meeting time works for
most people going forward, and will also put together an Office Hours in
about 2 weeks. hope to see you there!
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive
I'd like to personally invite you to the upcoming CentOS Automotive SIG
meeting, which will happen this upcoming Thursday. I'd also like to
personally apologize for the connectivity problems we had during the
initial meeting. We will have a better solution this time using Bluejeans.
In addition, we will start the actual meeting 5 minutes after the hour so I
can help people join as needed.
date: Sept 16
time: 8am PDT / 11am EDT / 5pm CEST
conf: https://bluejeans.com/870492784
agenda:
https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings/2021-09
We will go over the goals and details about the SIG at the beginning for
those who missed it last time, and will set some time aside to talk about
the ongoing infrastructure status. I'd also like to have some time to talk
about what people want to see in this SIG in terms of content, and if we
are able, to outline the steps needed to get to a release of the Automotive
variant.
I'm also planning to announce a monthly Office Hours informal meeting that
will happen between the standard formal meetings, in the same time slot.
This will simply be an hour for interested parties to drop in and talk shop
about automotive software.
Thanks & I hope to see you there on Thursday! Let me know if you have any
questions.
Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com
Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive