The openSUSE Community is proud to announce its new Code of Conduct as
approved by the openSUSE Board.
The openSUSE Code of Conduct was written during several Community
Meetings  as a collaborative project and reports were sent to the
project mailinglists. The input from the openSUSE community members was
sent the openSUSE Board and discussed at length during two public
openSUSE Board meetings .
During the February 28, 2022, public Board Meeting, it was recognized
that openSUSE did not have an adequate Code of Conduct; as such, the
board asked if any attendees were willing to take the initiave to work
with the community develope one. Through the regulary scheduled
community meetings, one was written, and subsequently proposed to the
We hope that by having a clear and concise Code of Conduct for the
project, the openSUSE Community can continue to grow and prosper in the
years to come.
The openSUSE Code of Conduct can be found at
 - https://etherpad.opensuse.org/p/weeklymeeting
 - https://code.opensuse.org/board/tickets/issues
 - https://en.opensuse.org/Code_of_Conduct
the openSUSE Board is involved in an activity to challenge the data privacy
issues created by preinstalled operating systems.
We want to address a letter to all data protection officers (DPO) of the EU
countries. We want to sign this as Board as well as for the openSUSE
Community, seeking the community approval for the same.
Nowadays consumers regularly face a restriction in their freedom of choice, an
essential element of digital sovereignty, when it comes to buying a new
computer (Laptop or PC): Software is offered pre-installed with no choice for
the consumer. 100% of Apple devices are sold with MacOS pre-installed and
nearly 100% of 'the rest' comes with Windows pre-installed.
Manufacturers are constantly imposing pre-installed software on consumers,
claiming that software and hardware are an "unit". Most of these devices work
perfectly with any free/open source operating system, so this statement is
not quite true. Still consumers find themselves forced to take – and buy -
what they are offered, mostly without even knowing about alternatives.
These pre-installed operating systems are going against not only freedom of
choice and digital sovereignty, but also data protection. MacOS, Windows (and
Microsoft Office, which often comes pre-installed as well) are not compliant
with European GDPR legislation.
An initiative was kicked off some 3 years ago to address these issues. FSFE
launched their connections to a member of the european parliament, who raised
the questions to the EU commission , and its answer was that "in the area
of data protection, under the system set up by the General Data Protection
Regulation (GDPR), supervision and enforcement fall within the competence of
Having had a discussion with the EU DPO (does not feel responsible), we have
prepared a letter  to the national DPO that we as Board (amongst others,
like FSFE) want so sign, as Board as well as for the community.
This mail is to ask for feedback on the letter as well as for approval to
sign. To shorten the process, please stand up if you *do not* agree with
signing the letter as Community Member. In this case we will ask the election
officials to set-up a vote, which will delay the process at least another 2
If you *do not* agree, please reply by 20 Mar 2022, 23:59 UTC latest.
(on behalf of the openSUSE Board)
Dr. Axel Braun <docb(a)opensuse.org>
Member of the openSUSE Board
Beta images of our new host-os distribution *Leap Micro 5.2 are finally
available at (get.opensuse.org for download and further testing.
Users are advised to use "transactional-update dup" during the Beta
phase of Leap Micro 5.2 (same for SLE Micro).
Leap Micro is a community rebuild of SLE Micro in a similar fashion to
how we build Leap nowadays. The big difference is that Leap micro is
intended to be strictly a small and ultra-reliable host os, for
container and VM workloads.
Distribution is very interesting from a schedule perspective. Leap
Micro has two releases a year (Spring/Autumn) and support is until the
next-next release is out. SLE Micro takes this even further and allows
you to stay on a given release (e.g. 5.1) for up to 4 years and then
e.g. migrate to 5.8
Please expect a very short Beta phase for 5.2 as we're a bit behind on
delivery with Beta (SLE Micro had its RC already out). Once we address
all *P1/P2 issues we will transition to RC as well. SLE Micro is
targeting GA in mid-April 2022. Mid-May 2022 would be a realistic
target for Leap Micro.
ps. Big big thanks to Ludwig, Max, Adrian for the build side, Jose,
Andrii, and cloud-qa team for work on the openQA side and publishing,
and also lcp for all the help on the get-o-o side.
openSUSE Leap Release Manager
Board Meeting Minutes 2022-03-28, 1330 CEST
Attendees: Gertjan, Syds, Mau, Axel, Attila, Emily, Doug, Neal, Gerald, Bill
== General Topics ==
As we regularly need more than an hour for our call, and Axel has a hard stop
at 1430h, the start time of the meeting should be moved back to 1300 CE(S)T
(Which is 1100UTC during summer time period)
All Board members are OK in moving the start time back to 1300 CE(S)T
(Neal considers moving to a different timezone)
AI: Axel to change invitation mail
===Vote on OpenLetter===
The Board intents to co-sign a letter to DPO in Europe (see https://
If this should happen 'on behalf of the project', a poll is required according
to discussion in the ML.
Q: Do we go that way (which is time consuming), do we sign as board or do we
Gertjan, Neal: Go with whatever is faster
Mau: for me signing as board is the same as on behalf of the project
Gerald: It's a task of every member, including board, to promote openSUSE.
Once u are in a specific role, one needs to be a bit more careful
Agreement that we sign this as individuals. Each community member who want to
sign this as well should drop a mail by Fri 08 Apr to board(a)l.o.o
===Role of the Board===
In the context of the above thread, the role of the board as such was
discussed, as 'signing a letter' is not listed in the wiki as part of the
role. 'Advocating openSUSE Linux' neither
Gerald: Current 'setup' does not allow to respond to inquiries / actions in
less than 4 weeks
Bill: If I vote for the Board, do I not trust the board in that way?
Board understanding is that Board actions are by default not limited to the
points listed in the wiki. That would limit the board more than a normal
Neal: Fedora could make it to Laptops because Fedora council was able to pick
this up. If oS needs a poll for everything, it will fail
Neal: Need to rephrase the board duties and give this to community approval
Fedora Council equivalent: https://docs.fedoraproject.org/en-US/council/
Syds: the election rule states: <br>Members of the openSUSE board shall act on
behalf of all openSUSE contributors in the best interest of the openSUSE
project. Although board members may be affiliated with companies or
organizations that have an interest in the success of openSUSE, they will not
be considered representatives of the companies or organizations with which
they are affiliated.
Emily: Board scope comes from guiding principles, so we would need to change
the guiding principles https://en.opensuse.org/openSUSE:Guiding_principles
(needs some update, as very old)
Current situation is bad for the community as a whole, as we are somehow in a
Participants agreed to change this, as this would improve community
Proposal: Workshop during oSC22 for this (volunteer to submit workshop
This list was found at https://old-en.opensuse.org/Board_election/2009 on role
of the board with link
===Code of Conduct===
The Code of Conduct was reviewed with a few edits submitted and agreed apon by
Gerald. A submission to the project mailing list will be made during the next
Neal updated the Code of Conduct.
I was asked if anyone from openSUSE is willing to take part in a panel
session on April 2nd at 15:00 UTC during the Fedora Mentor Summit (April
1st & 2nd). We will discuss this in today's community meeting
(https://etherpad.opensuse.org/p/weeklymeeting), but if you are
interested and won't make the meeting today, please send me an email and
I'll connect you with the organizers. You can register for the event at
Here are the minutes for the January 31 meeting.
These can also be viewed here:
= Minutes of openSUSE Board meeting 2022-01-31 =
Board: Gerald, Axel, Gertjan, Neal, Syds
Absent: Atilla, Maurizio
Guests: Bill, Doug, Emily, Luna, Max, Lubos
== Topic: openSUSE Membership ==
Bill: Suggests the Board asks for the state of membership
applications/processing on a regular occurrence. It would add some
more accountability for such a core function.
Gerald: What would be a reasonable cadence?
Bill: Seems reasonable, we should also report around election time
too, since that's when most applications happen anyway.
Emily: Would like to join the membership officials too. Bill seems to
be doing everything and she's like to help out.
Axel: Don't think the board can do this.
Neal: It's actually one of the few things we can directly do.
Gerald: Points out Wolfgang and others do plenty too. We shouldn't use
this power to randomly add more people because it's not terribly
There's a lot of discussion about the particulars between Gerald and Bill.
Emily: They seem to be full of people that do lots of things right
now, and don't focus much on membership.
Gerald: Historically the team was quite large and we were told even
members of the team didn't precisely know who was on it, and some were
missing in action. Plus they did not have ownership of their own
mailing list or Wiki page, which has been/is being addressed now. The
ones that were primarily processing things (Wolfgang and Dominique)
are also very busy processing things around the last election. Bill
was a good addition and perhaps adding Emily will help too.
Bill: He proposed to the team to meet monthly, they didn't receive the
Neal: Regular meetings are a rather new thing for teams, it's not a
cultural norm yet. Hopefully it will be eventually.
== Topic: Communication Platform Moderation ==
Gertjan: Atilla, Maurizio, and him have started figuring out all the
platforms and made the first steps toward getting a central moderation
group set up (mailing list, etc.). Reaching out to Jim from the
forums, waiting for a response.
Bill: Discovered there's already a moderator list that Sasi Olin owns,
they'll be modifying that.
== Topic: AlmaLinux sponsorship ==
Doug: AlmaLinux reached out again to sponsor.
The Board generally seems fine about it. Would like to know what they
want out of it though, since it's a bit odd.
== Topic: openSUSE Leap 15.4 ==
Axel: Wants opinion on new release, thinks we'll shoot ourselves in
the foot on default Python (3.6).
Neal: This is a consequence of the Leap platform being based on SLE.
We do have alternate interpreters that we can build community packages
on top of. Python 3.6 is also the default in RHEL 8 and between Fedora
EPEL and openSUSE community, we could probably continue supporting
stuff on it by sharing effort. But we can also build modules in
Backports against newer interpreters.
Lubos: SUSE ships 3.6 as default for stable. And 3.9 as an alternate
interpreter with no packages built against it.
Neal: Points out that Tumbleweed is failing here, where 3.8 is still
the default and neither 3.9 nor 3.10 never made it. We should sort
that out first before tackling Leap. Newer stuff has to land in
Gerald: Leap (or SLE) are always about compromises. In software every
(major) update fares a good chance of breaking something - and be it
an unwarranted assumption It's difficult to handle this kind of stuff.
If the community wants something like the classic (open)SUSE Linux
releases branched from Tumbleweed, the community needs to take that
Lubos: Our build system capacity for s390x is close to our limits,
duplicating distro would push us past our limits.
Neal: For the Python issue, we can just set up community support for them.
== Topic: openSUSE Leap Micro 5.1 ==
Lubos: openSUSE meets Cardano (Leap Micro 5.1)
* Requests board review: https://code.opensuse.org/leap/features/issue/59
Neal Gompa (ID: Pharaoh_Atem)