• ContentWeekly EditionArchivesSearchKernelSecurityEvents calendarUnread commentsLWN FAQWrite for us Weekly Edition Archives Search Kernel Security Events calendar Unread comments LWN FAQ Write for us openSUSE governance proposal advances Douglas DeMaio hasannouncedthat Jeff Mahoney’s newgovernance proposalfor openSUSE, which waspublished in January, is moving forward. • The new structure would have three governance bodies: a new technical steering committee (TSC), a community and marketing committee (CMC), as well as the existing openSUSE board. • The discussions during the meeting proposed that the Technical Steering Committee should begin with five members with a chair elected by the committee. • The group would establish clear processes for reviewing and approving technical changes, drawing inspiration from Fedora’s FESCo model. • Decisions for the TSC would use a voting system of +1 to approve, 0 for neutral, or -1 to block. • A proposal passes without objection.

Article Summaries:

  • Douglas DeMaio announced that Jeff Mahoney’s governance proposal for openSUSE, released in January, is progressing. The plan introduces three bodies: a new Technical Steering Committee (TSC), a Community and Marketing Committee (CMC), and the existing openSUSE board. The TSC would start with five members, elect a chair, and adopt a voting system (+1 to approve, 0 neutral, -1 to block) modeled after Fedora’s FESCo, with objections requiring documented rationale. The CMC would focus on outreach, advocacy, community growth, and serve as an escalation point for disputes before involving the board. No adoption timeline was set; discussions will continue on GitLab and future meetings.
  • openSUSE is moving forward with a new governance proposal announced by Douglas DeMaio, based on Jeff Mahoney’s January draft. The plan introduces three bodies: a Technical Steering Committee (TSC), a Community and Marketing Committee (CMC), and the existing openSUSE Board. The TSC would start with five members, elect a chair, and adopt a voting system (+1 to approve, 0 neutral, -1 to block) modeled after Fedora’s FESCo, with objections requiring documented rationale. The CMC would focus on outreach, advocacy, and serve as an initial escalation point for disputes, before matters reach the Board. No adoption timeline was set; discussions will continue via GitLab and future meetings.

Sources: