---------- Forwarded message ---------
From: Luna Jernberg <droidbittin(a)gmail.com>
Date: Tue, Apr 12, 2022 at 5:03 PM
Subject: Re: Summary of a call on the topic of Cisco's openh264
distribution for openSUSE
To: Lubos Kocman <lubos.kocman(a)suse.com>, <ddemaio(a)opensuse.org>,
Knurpht-openSUSE <knurpht(a)opensuse.org>, Emily Gonyer <emilyyrose(a)gmail.com>,
Cc: factory(a)lists.opensuse.org <factory(a)lists.opensuse.org>, results(a)suse.de
We discussed this a bit in this weekly openSUSE meeting :)
On Thu, Apr 7, 2022 at 6:39 PM Lubos Kocman <lubos.kocman(a)suse.com> wrote:
> Hello openSUSE,
> We've just had a meeting with Cisco regarding providing easy access to
> the openh264 codec to the openSUSE users.
> The outcome is that Cisco will help us with the redistribution side by
> utilizing the ciscobinary.openh264.org host. There seems to be more
> space for collaboration that could lead to the usage of OBS in some
> more of Cisco's open-source-related processes. OBS seems to be a good
> fit as we can cover builds for multiple distributions and image builds.
> Big thanks to Neal Gompa for raising this topic. Neal was really
> shining on the call :-)
> We seem to found the right people for the job, and the rest of the
> discussion will happen in the email thread with selected people.
> I'm really excited about the current direction of conversation as Cisco
> seems to be very enthusiastic about further collaboration with openSUSE
> and Open Build Service.
> Big thanks to Ann for making this meeting happen. And also big thanks
> to Neal, Adrian, Fabian, and Bernhard for being our technical experts
> on the call. Release management was represented on the call by me and
> Stefan Weiberg.
> Related issues
> Document used for introduction to the issue
> Best regards
> Lubos Kocman
> on behalf of openSUSE Release Team
redirected to project@ as this the more appropriate list for me to rant
about community building :-)
On 30.03.22 13:23, Simon Lees wrote:
> On 3/30/22 20:59, Henne Vogelsang wrote:
>> On 30.03.22 10:24, Simon Lees wrote:
>>> which is why I spent alot of time looking at foundation related topics.
>> And that is nice and all. But *additionally* to doing the grunt work of
>> attracting contributors, not *instead* of it.
> Sure, do you have a magical time tree for me?
Sure not. And if you can't you can't. Your time, your decision. But you
are not the only person in this crowd :-)
> If I could think of simple easy things to attract new contributors I
> would absolutely have been doing them as well, but its hard and I don't
> have many ideas, do you?
This is a well established, written about, even researched topic.
There are tons of things we can do "passively" for our projects. And by
projects I don't mean openSUSE as a whole. I mean all the building
blocks that make up openSUSE. The teams, the software projects, the
- clarify *what* we want to achieve. What are the priorities? *Who* is
- establish contribution guidelines
- clearly express roles and responsibilities
- clearly express how we do conflict management
- document the path to leadership
- clearly express areas/problems that need attention
- establish onboarding practices for new contributors
- establish mentoring practices for contributors
- establish decommission practices (something isn't salvageable, get rid
- establish successor practices (people leave all the time)
So help existing openSUSE maintainers/projects by setting up a golden
path to follow for maintainership. Basically define what is openSUSEs
shared understanding of how FOSS projects are supposed to be if they are
part of openSUSE.
Once the "passive" things are under control you can go out and be active
about attracting people to projects.
- Practice running projects to our standards
- Practice mentoring & onboarding
- Ask *people* you think will be a fit personally (best thing to do)
- Hook into the existing mentoring programs
- Shouting to the public via blogs, social media, podcasts etc.
This isn't something we are alone with. *Every* healthy FOSS community
does this. There are whole communities about building communities!
Books, events, guides etc.
Working in Public by Nadia Eghbal
The Art of Community by Jono
So there is, as usual, just a shitload of things to learn and to do.
And also as usual: A crowd (like this one here) will not collaborate.
Some people out of the crowd will be interested. And only a very small
amount of those interested will actually be able to do it. And *those*
are the openSUSE community.
We need to be more efficient in turning our crowd into a community of
Everybody has a plan, until they get hit.
- Mike Tyson
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
[ First of all, my apologies for sending these with such a delay. ]
= Minutes of openSUSE Board meeting 2022-02-28 =
Present: Axel, Gerald, Gertjan, Maurizio, Neal, Syds
Guests: Ariez, bittin, Doug, Emily, Sasi
== Minutes of recent meetings ==
* Syds just done
* Gentle reminder to Neal
== openSUSE social media accounts (and openSUSE as a project) and events like the war in Ukraine ==
* Doug liked a couple of posts from the openSUSE Twitter account that
referred to Ukrainian leaders.
* Another community member approach him and asked to remain neutral.
* Doug notes "there are things we as a community should stand for."
* Gertjan, Syds,...: "openSUSE should be about inclusion; we do not
want to exclude people."
* Maurizio: "As a board we should represent everybody."
* A number of board members indicate they struggle how to best handle
* Sasi suggests to take a stance for both Ukrainians and Russians;
it's quite important to differentiate between political identities
of a country and the people living there.
* Gerald references on a "A note on principles ..." mail last year
which got mixed responses.
* Mau is in favor of a message of solidarity
* "So, shall we send a public message?"
* ...long discussion...
* Agreement to primarily issue a statement when events like these
encrouch on our project/community.
* Agreement that there's a difference between personal opinion and
actions vs those of projects.
* Rough consensus to not send a generic statement at this point
while definitely keeping an eye on the situation.
== Online Communities ==
* How to go about groups using the openSUSE name but not following
our guiding principles?
* Example: In 2020 a Polish Telegram group was created
** Sasi was very excited originally.
** The groupd quickly died down due to disagreement.
** One person got banned for sexual orientation, others stigmatized.
** Just one admin.
* Agreement: There should be no group under/using the openSUSE flag
not complying with our guiding principles.
* Challenge: Guiding Principles are not very specific ...
* Gerald believes we can enforce trademarks to expell/shutdown/... groups
* AI: Gerald will check with SUSE Legal
* Next steps?
** Start working on a Code of Conduct with help of the community.
** We do not need to change the Guiding Principles to implement a
Code of Conduct.
** But we can consider adjusting the Guiding Principles to be
explicit about being open and welcoming versus discrimination.
** AI: Mau and Gertjan to have a look.
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