Automotive SIG Meeting: September 16, 2021
These are shared minutes for the meeting of the CentOS Automotive SIG.
Meeting time: September 16, 2021, 11am EDT (5pm CEST) Meeting link: https://bluejeans.com/870492784
Note, some items are repeated from the first meeting to make up for connectivity issues. If you have a particular discussion item, please add it below and/or contact jefro for help.
- Introduction to the Automotive SIG
- General goals for this SIG
- Specific goals through EOY 2021
- Establishment of community standards
- Open discussion
Jeffrey Osier-Mixon, Red Hat jefro
- add your name here
Introduction to the Automotive SIG
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 at in-vehicle automotive use cases. Second, it is meant to provide such projects with build and test infrastructure.
- Why an Automotive SIG in CentOS?
- Advancement of distro-based automotive Linux
- Focal point for working with other upstreams, hardware options, and related projects
- Public development for POCs, including the automotive CentOS variant
Upstream resource & primary test bed for RHEL in an automotive context
General goals for this SIG
The general goal of the SIG is to provide an open-source home for distro-oriented automotive work (i.e. derived from binary artifacts, rather than rebuilt from source), and to attract and encourage open development of automotive software between commercial and non-commercial partners.
To that end, this SIG will have three primary functions, as outlined in the slide.
- General Goals
In the meeting, we will speak frankly about Red Hat's motivation for creating this SIG, as it will be used as an upstream for RHEL in an automotive context preparatory to an eventual Red Hat automotive product. Red Hat feels strongly that community development with the open source process is by far the best way to achieve success with this by working collaboratively in this SIG and with other existing automotive Linux projects. The intent is to augment existing efforts with a new design paradigm and to collaborate and share code whenever & wherever possible.
Note: CentOS is a public, fully transparent project, so any work that happens within the context of this SIG is by definition public, and, according to the CentOS guidelines, must carry an open license approved by the CentOS board. This applies to both code and documentation. If any work requires an NDA or other privacy protection, it must be done outside the scope of this SIG.
Specific goals through EOY 2021
Some practical goals to work toward over the next 4-5 months.
- Build a foundational community
- Establish working relationships among all participants, and encourage others to join
- Create robust community guidelines, including contribution guidelines and CoC
- Vote administrative roles
Develop plans for the CentOS Automotive variant and build & test infrastructure
- Presentation at Automotive Linux Summit (with stickers)
Establishment of community standards
Community standards, and the communication of these standards, is the backbone of a healthy community.
- asynchronous: mailing lists
- synchronous: IRC
periodic: meeting schedules & calendars
- Code of Conduct
- abide by the CentOS Code of Conduct
- discuss additional guidelines
- Administration and “leadership” roles
Several community communications channels have been established:
- monthly meetings on the third Thursday, 1500 UTC, or as decided by the group
- bi-weekly "office hours" on a separate call
The current meeting time is reasonable for Europe and the US, but not for Asia. As the group develops, it may be advantageous to hold meetings at times more conducive to all times zones. To achieve this, we may move to alternating times and/or a divided meeting that repeats on the same day, and to record meetings so people can catch up asynchronously. Important topics should always be brought up on the mailing list as a primary avenue for discussion.
The SIG is subject to the CentOS Code of Conduct, which outlines conduct expectations as well as an escalation path for anyone who feels uncomfortable. Jefro also has had training in code of conduct resolution, so if anyone has any concerns or needs guidance on this subject, please feel free to send email to him personally as a first step. All communication on this subject will remain strictly confidential.
A chair position is required in order to have a point of contact between the SIG and the CentOS board. The word "leadership" is in quotes to indicate that the chair position is administrative and not actually a set of power - all decisions will be made by group consensus in accordance with the CentOS SIG charter (and good community practice), and no single organization will hold sway regardless of how many people show up. The SIG must report status back to the CentOS board on a quarterly basis, which is one of the duties of the chair, along with developing the agenda for this ongoing meeting and maintaining minutes. Jefro has agreed to function as chair for now as the SIG gets underway.
Open discussion and Action Items
Action items from the August meeting:
- fix the meeting invitation so everyone has the correct code (Jefro)
- continue to develop basic build/test infrastructure (Pierre-Yves)
- encourage all interested parties to join this community (everyone)