April 2022 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] How we will use the GSoC money
by Vincent Untz 18 Jul '24

18 Jul '24

Hi, (let's see how a public discussion about money goes :-)) The Google Summer of Code brings us great students, but also means that the openSUSE project will get $8000 (if I'm not mistaken) at the end of the summer. That's $500 per student. A while ago, I requested comments on my blog about what to do with the money, but didn't get any feedback. So I take this as "do what you feel is best", and this mail is about the plan. As a reminder, the main issue is that we will likely not have the openSUSE Foundation created in time for this. For instance, Google would like us to get some form filled before the end of June; this is not a mandatory timeline, but I think it shows that we won't be ready with the Foundation for that. The current plan is to give that money to another organization we feel close to, and I have two candidates in mind: - the Software Freedom Conservancy (http://sfconservancy.org/) it's a really nice org that provides a home for various cool projects (see http://sfconservancy.org/members/current/) and those projects help make openSUSE a great project. - the Desktop Summit (https://www.desktopsummit.org/) it's one of the biggest event this year, and this would help us have some more visibility (since we'd be sponsors, I guess). I'm sure they would welcome this to secure their budget. Note that an alternative solution would be to leave the money to Google for a future GSoC or similar program, but I feel it's better to use the money where it can make a difference today. Now, it's not too late to change the plan. If you have a better suggestion, please tell us. There's no need to argue forever about it, just explain why you think it's good. Keep in mind that if we cannot receive the money ourselves, this also means that we cannot use it to buy stuff for openSUSE. Pavol and I will take the final decision since we are the GSoC admins for openSUSE. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-project+help(a)opensuse.org

22 38

[Notice] - openSUSE Regular Board election 2021
by Ariez Vachha - openSUSE 01 Nov '22

01 Nov '22

Dear openSUSE members, openSUSE Board Election 2021 [1] It's time to elect new Board members to fill empty seats on the openSUSE Board. There are two seats for election in accordance per our normal election cycle. This is a regular election as defined in our Election Rules [2] ## Phase 0 01 November 2021 - Announcement of the Board Election 2021 - Call for Nominations and Applications for Board candidacy - Membership drive 22 November 2020 - Nominations and Applications for Board candidacy close ## Phase 1 22 November 2021 - Announcement of the final list of candidates - Campaign begins - Membership drive continues, opportunity to apply for openSUSE Membership, but members will only be eligible to vote and not run as a candidate ## Phase 2 13 December 2021 - Ballots open: Please cast your vote during this time - Campaign continues 30 December 2021 - Ballots close 31 December 2021 - Announcement of results To stand for a position in the openSUSE Board please send an email to: * project(a)lists.opensuse.org and * election-officials(a)lists.opensuse.org If a member would like to nominate another member, please inform the Election Committee and the officials will contact the nominee to ask whether they would like to run as a Board candidate. Only openSUSE members are eligible to run for openSUSE Board openings in accordance with the Eligibility and Validity section of our Election Rules [2]. The Election Committee [3] are hereby calling for Nominations & Applications for the openSUSE Board. [1] https://en.opensuse.org/openSUSE:Board_election [2] https://en.opensuse.org/openSUSE:Board_election_rules [3] Members: Ish Sookun, Edwin Zakaria and Ariez Vachha. -- Regards, The Election Committee election-officials(a)lists.opensuse.org

3 5

Update on next generation of SLE
by Stefan Behlert 14 Jun '22

14 Jun '22

(Sending to both openuse-project as well as opensuse-factory. Please keep discussions on the -project list to make life easier for all.) Moin, In the last months many people have brought up the topic of "When will the next SLE major version come out?". Today we would like to give you a first update on the plans. Since 2018, when SLE 15 was initially released a lot of things have changed, including requirements from users and customers, technologies, the speed of new versions of applications, languages and their libraries appearing. Also the connection between Leap and SLE has changed. And while some bits and pieces got better, we firmly believe we can do better. SLE 15 is a great general purpose operating system, yet challenges with some use cases, now places of deployment, and the type of enhancement requests show that it's time for a successor. With the next generation of Enterprise releases we want to tackle the above. Intending to do radical changes (regarding technology- but also design-wise) we choose "Adaptable Linux Platform" or short "ALP" as codename for that next generation. This indicates already that some things will be quite different than a "mere "SLE 15++ would be ;) First and foremost, ALP will be developed in the open. We are not going to put the pieces together internally and then share outside, as in the past. No, we are creating and building in the openSUSE Build Service - in a project next to you :). You get to directly see to see what is going on and participate more easaily. Another important point is that we intend to split what was a more generic, everything is closely intertwined into two parts: One smaller hardware enabling piece, a kind of "host OS", and the and the layer providing and supporting applications, which will be container (and VM) based. You might say "This is very generic, can you tell us more?" - of course. In the upcoming weeks more and more will crystalize, and we will share as quickly and regularly as possible. This is just a first heads-up to inform you that we are in the process of setting everything up - from project to feedback channels, from documentation to testing. Of course, you will have lots of other questions - how will contribution work, what impacts this has on LEAP and get-o-o, how migration could work, and many more. We kindly ask you for a little bit of patience. We promise we will share as soon as possible more details. ciao, Stefan -- Stefan Behlert, SUSE Software Solutions Product Management SUSE Linux Enterprise Maxfeldstr. 5, D-90409 Nuernberg, Germany SUSE Software Solutions Germany GmbH, GF: Ivo Totev (HRB 36809, AG Nuernberg)

11 23

discussion/workshop on Leap Successor & notes from Community Meeting 1: Week 17
by ddemaio 27 Apr '22

27 Apr '22

Hi all, We will have an open discussion/workshop during the community meetings on May 10 and 12 to discuss the successor of Leap and seek input and gather interests from people who are interested in joining the discussion. The workshop/discussion will be at https://meet.opensuse.org/meeting and we will be using a pad to write down points of interest. Please note that the time for the meetings will shift from the normal time of 14:30 UTC to 13:30 UTC for May 10 and the second meeting on May 12 will shift from 19:00 UTC to 18:00 UTC. You can see the notes from today's meeting 1 below. v/r Doug ## Participants: Knurpht, Emily, Doug, Lubos ## Topics Doug gave update on TSP discussions. Pathway to resolving the TSP looks promising and we hope to have solution soon. Unfortenately, we can't say with 100% certainty it will be in place in time for oSC22 and the openSUSE Summit at OSCAL Went over the Leap Micro slides and discussed possible use cases for it with Flatpaks, Snaps, AppImage Organizing an open discussion/workshop on May 10 and May 12 to discuss the successor of Leap and what are people's input/interests are. Will take place at the community meeting time. (With a slight time shift during that week) The next two weeks of meetings to Meeting 1: Tuesday at 13:30 UTC and Meeting 2: Thursdays at 18:00 UTC. updated on https://etherpad.opensuse.org/p/weeklymeeting Will return to normal on May 17

2 1

oSC22 and Community Meeting: Week 17
by ddemaio 27 Apr '22

27 Apr '22

Hi all, There will be a Regular Community Meeting tomorrow at 14:30 UTC. At 19:00 UTC tomorrow, we will have a meeting for the openSUSE Conference. The second Regular Community Meeting is scheduled for Thursday at 19:00 UTC. I will not be able to attend this meeting as I will be traveling to LAS. View the community meeting notes at https://etherpad.opensuse.org/p/weeklymeeting and the conference planning meeting notes at https://etherpad.opensuse.org/p/osc22 The meetings will take place on https://meet.opensuse.org/meeting v/r Doug

2 1

Translations for openSUSE Leap 15.4 Release Announcement / Screenshots
by ddemaio 25 Apr '22

25 Apr '22

Hi everyone, I have placed the release announcement for openSUSE Leap 15.4 on the wiki at https://en.opensuse.org/Release_announcement_15.4 It would be highly appreciated if you could help to translate the release announcement to your native language to help propagate the news of our next release. Currently it is only in English. Feel free to link your translated version to the top and include your ISO 639-1 Code language code. If you have any questions, please let me know. Screenshots Also, please consider updating the screenshots once we have the RC. You will find old screenshots on https://en.opensuse.org/Portal:15.4/Screenshots and new screenshots will just need to be uploaded and updated. v/r Doug

1 0

oSC22 and Community Meeting: Week 16
by ddemaio 25 Apr '22

25 Apr '22

Hi all, There will be a Regular Community Meeting today at 14:30 UTC. At 19:00 UTC tonight, we will have a meeting for the openSUSE Conference. We will have a second Regular Community Meeting on Thursday at 19:00 UTC. View the community meeting notes at https://etherpad.opensuse.org/p/weeklymeeting and the conference planning meeting notes at https://etherpad.opensuse.org/p/osc22 The meetings will take place on https://meet.opensuse.org/meeting v/r Doug

1 1

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 25 Apr '22

25 Apr '22

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

2 1

Fwd: Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by Luna Jernberg 23 Apr '22

23 Apr '22

---------- Forwarded message --------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Sat, Apr 23, 2022 at 1:58 PM Subject: Re: Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin) To: openSUSE Meeting Reminder <no-reply(a)opensuse.org>, <board(a)opensuse.org>, project <project(a)opensuse.org>, Gerald Pfeifer <gp(a)suse.com>, bittin < bittin(a)opensuse.org> Attending as a guest On 4/23/22, openSUSE Meeting Reminder <no-reply(a)opensuse.org> wrote: > Hello all, > > The biweekly board conf call will be held in two days at 13:00 Europe/Berlin > time (CET = UTC+1) > Meeting will be in the regular Board Meeting Room > https://meet.opensuse.org/OSBoard > > Current Topics: > https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting > > Board Members: If you cannot participate, please advise by replying to this > mail. >

1 0

Leap 15.4 features, screenshots, release announcements
by ddemaio 22 Apr '22

22 Apr '22

Hi all, The marketing team is still working on the release announcement and plan to send it out for translation on or about April 20. We need more input from the community about what packages to highlight and new features we will have in openSUSE Leap 15.4. We go over the release announcement during the community meetings. Please visit https://en.opensuse.org/Features_15.4 for the list of features we are highlighting. Feel free to add your package and features, which will help us with some additional information to the release announcement. Also, we would appreciate anyone willing to add screenshots of their desktop and packages they are using to https://en.opensuse.org/Portal:15.4/Screenshots. Musicians, artist, developers, creators please add the things you like to screenshots wiki page https://en.opensuse.org/Portal:15.4/Screenshots v/r Doug

4 10

Important: Leap 15.5 Early planning and steering development towards ALP
by Lubos Kocman 21 Apr '22

21 Apr '22

Hello openSUSE! (sorry for the long but I believe important email) since the *announcement of next-gen SUSE Linux Enterprise has already landed, I'd like to take a moment and talk a bit about our last openSUSE Leap 15.X release and set some expectations. openSUSE Leap 15.5 will be based on the binaries and schedule of SUSE Linux Enterprise 15 SP5. SUSE Linux Enterprise 15 is using the tick-tock model, where 15 SP4 would be the feature release while 15 SP5 would be more of a bug fix r perhaps it better to say "maintenance" release. I did already created an SLE 15 SP5 draft-based *proposal for the Roadmap. For which I'd appreciate your feedback. I'm a bit keen on setting deadlines for the earlier milestones (See outlined alternatives) rather than the SLE Public ones as we did in 15.5. That in my opinion would result in fewer late changes and would be more testing-oriented which is what I believe this release needs to be. From the past, we know that "community originated" changes with a big impact can happen also outside feature release, such as glibc and rpm update in the late development phase of 15 SP3. We are in a bit different situation now, as the parallel development of the "Adaptable Linux Platform" is now happening publicly in OBS and neither community nor SUSE has unlimited resources. As the plan is that the next Community/Enterprise distribution (Leap) will be ALP itself (as it will be developed open) or closely based on ALP I believe it makes sense to steer community effort there as it pays off in the long run. There are some problematic topics that we will have to address. One of them in SLES 15 SP5+ and Leap 15.5 such as the python *situation. Which will only get worse with each SLE Service Pack (keep in mind that unlike for Leap there is a plan for SP7). Specifically for this isseu we could use existing *code-o-o#17 and interlink it with internal jsc#PM-3390 (Switch System Python3 to a supported version). If you know about other larger topics that are worth fixing in the last Leap 15.5 release, then please do not hesitate to report them in code- o-o and set milestone to 15.5. We'll process them on next-next monday on Community feature meeting (skip one due to Easter). Any feedback is greatly welcome. [0]https://lists.opensuse.org/archives/list/project@lists.opensuse.org/threa… [1]https://etherpad.opensuse.org/p/ReleaseEngineering-20220413#L124 [2]https://en.opensuse.org/openSUSE:Roadmap#Draft_schedule_for_openSUSE_Leap… [3]https://code.opensuse.org/leap/features/issue/17 [4]https://code.opensuse.org/leap/features/issues Thank you very much for your understanding Lubos Kocman on behalf of openSUSE Release Team

2 3

Fwd: oSC22 and Community Meeting: Week 16
by Luna Jernberg 19 Apr '22

19 Apr '22

---------- Forwarded message --------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Tue, Apr 19, 2022 at 4:27 PM Subject: Re: oSC22 and Community Meeting: Week 16 To: ddemaio <ddemaio(a)suse.de>, bittin <bittin(a)opensuse.org>, Martin Jernberg <droidbittin(a)gmail.com>, <ddemaio(a)opensuse.org> *attending* On Tue, Apr 19, 2022 at 11:39 AM Luna Jernberg <droidbittin(a)gmail.com> wrote: > Will attend the Community Meeting today, before the foss-north Online 2022 > hangout starts: https://foss-north.se/ https://foss-north.se/2022/ > > On Tue, Apr 19, 2022 at 11:34 AM ddemaio <ddemaio(a)suse.de> wrote: > >> Hi all, >> There will be a Regular Community Meeting today at 14:30 UTC. At 19:00 >> UTC tonight, we will have a meeting for the openSUSE Conference. We will >> have a second Regular Community Meeting on Thursday at 19:00 UTC. >> >> View the community meeting notes at >> https://etherpad.opensuse.org/p/weeklymeeting and the conference >> planning meeting notes at https://etherpad.opensuse.org/p/osc22 >> >> The meetings will take place on https://meet.opensuse.org/meeting >> >> v/r >> Doug >> >

1 0

oSC22 and Community Meeting: Week 15
by ddemaio 19 Apr '22

19 Apr '22

Hi all, There will be a Regular Community Meeting tomorrow at 14:30 UTC. (I might be a little late from another meeting). At 19:00 UTC tomorrow, we will also have a meeting for the openSUSE Conference. The Call for Papers ends on Thursday, April 14.. We will have a second Regular Community Meeting on Thursday at 19:00 UTC. View the community meeting notes at https://etherpad.opensuse.org/p/weeklymeeting and the conference planning meeting notes at https://etherpad.opensuse.org/p/osc22 The meetings will take place on https://meet.opensuse.org/meeting v/r Doug

2 1

[opensuse-project] zypper repos (lr)
by Felix Miata 13 Apr '22

13 Apr '22

How about switching default output fields for zypper lr, for the benefit of both help responders, and seekers? Who are the most common users, anyone outside the various support forums? In support forums, it's pretty common that repos are an issue, and when they are, the URIs in those repos are the most vital information. So, why aren't URIs included in the default output? OPs often know they're needed without knowing why, so will include them, but without the -r switch, whereupon someone must ask for them again, with the switch, prolonging the useful response and solution times. OTOH, repo names and nicknames in conjunction with URIs add nothing in this use context. In addition, with both name and alias, and URIs, and default other fields, command output invariably gets wrapped, making their use difficult. Here's mine, unedited: # zypper lr Repository priorities in effect: (See 'zypper lr -P' for details) 72 (raised priority) : 1 repository 90 (raised priority) : 1 repository 99 (default priority) : 10 repositories # | Enabled | GPG Check | URI ---+---------+-----------+----------------------------------------------------------------------------------- 1 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_15.3/ 2 | Yes | (r ) Yes | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/ 3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ 4 | Yes | (r ) Yes | http://ftp5.gwdg.de/pub/opensuse/repositories/multimedia:/apps/openSUSE_Lea… 5 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ 6 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 7 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/ 8 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/Essentials 9 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/oss/ 10 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/backports/ 11 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ 12 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/sle/ It's the result of repoListColumns = u in my zypper.conf. What information is actually added to URIs by including also either name or alias, much less both? Alternatively, a new switch, appropriate specifically to common help situations, with reduced likelihood of being wrapped, possibly by truncating name and/or alias at some maximum field width, maybe 18, 20 or 24. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 4

Fwd: Summary of a call on the topic of Cisco's openh264 distribution for openSUSE
by Luna Jernberg 12 Apr '22

12 Apr '22

---------- 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>, bittin <bittin(a)opensuse.org> Cc: factory(a)lists.opensuse.org <factory(a)lists.opensuse.org>, results(a)suse.de <results(a)suse.de> Looks good 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 > https://github.com/cisco/openh264/issues/3480 > https://code.opensuse.org/leap/features/issue/22 > > Document used for introduction to the issue > https://etherpad.opensuse.org/p/openh264-summary > > > -- > Best regards > > Lubos Kocman > on behalf of openSUSE Release Team >

1 0

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)
by openSUSE Meeting Reminder 11 Apr '22

11 Apr '22

Hello all, The biweekly board conf call will be held in two days at 13:00 Europe/Berlin time (CET = UTC+1) Meeting will be in the regular Board Meeting Room https://meet.opensuse.org/OSBoard Current Topics: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting Board Members: If you cannot participate, please advise by replying to this mail.

3 2

oSC22, OSCAL Summit and Community Meeting: Week 13
by ddemaio 10 Apr '22

10 Apr '22

Hi all, We will have Regular Community Meeting tomorrow at 14:30 UTC. At 19:00 UTC tomorrow, we will also have a quick meeting for the openSUSE Conference and openSUSE Summit at OSCAL. We will have a second Regular Community Meeting on Thursday at 19:00 UTC. This week we we have the following topics we will spend some time covering: * Getting access to following landing page (https://microos.opensuse.org/) and update to reflect current state of project to better manage user expectations and potentially request assistance/volunteers for areas of need. * Go over Social Media Plan and start coming up with points to be listed - https://en.opensuse.org/openSUSE:Social_media_launch_plan * Go over a completed lesson plan in the next Thursday meeting View the meeting notes at https://etherpad.opensuse.org/p/weeklymeeting The meetings will take place on https://meet.opensuse.org/meeting You can find the meeting notes for the conference planning at https://etherpad.opensuse.org/p/osc22 v/r Doug

2 3

Community Meetings: Week 14
by ddemaio 08 Apr '22

08 Apr '22

Hi all, We will have Regular Community Meeting tomorrow at 14:30 UTC. We will have a second Regular Community Meeting on Thursday at 19:00 UTC. View the meeting notes at https://etherpad.opensuse.org/p/weeklymeeting The meetings will take place on https://meet.opensuse.org/meeting You can find the meeting notes for the conference planning at https://etherpad.opensuse.org/p/osc22 v/r Doug

1 1

How to build a FOSS maintainer community (Was: Planning decomission of software.opensuse.org)
by Henne Vogelsang 06 Apr '22

06 Apr '22

Hey, 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 distribution etc. - clarify *what* we want to achieve. What are the priorities? *Who* is the priority? - 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 of it!) - 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 - Events - 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. https://lists.freedesktop.org/mailman/listinfo/foundations https://chaoss.community https://github.com/maintainers https://sustainoss.org https://opensource.guide/best-practices https://foss-backstage.de https://communityrule.info 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 maintainers. Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson

6 12

openSUSE Finalizes New Code of Conduct
by ddemaio 05 Apr '22

05 Apr '22

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 [1] 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 [2]. 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 Board. 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://en.opensuse.org/Code_of_Conduct. [3] [1] - https://etherpad.opensuse.org/p/weeklymeeting [2] - https://code.opensuse.org/board/tickets/issues [3] - https://en.opensuse.org/Code_of_Conduct

4 3

Minutes of openSUSE Board meeting 2022-02-28
by Gerald Pfeifer 04 Apr '22

04 Apr '22

[ 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 this situation. * 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.

1 0

Threat to privacy by preinstalled operating systems
by Axel Braun 03 Apr '22

03 Apr '22

Dear Community, the openSUSE Board is involved in an activity to challenge the data privacy issues created by preinstalled operating systems. tl:dr 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. Long version ============ 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 [1], 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 national authorities". Having had a discussion with the EU DPO (does not feel responsible), we have prepared a letter [2] 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 month. If you *do not* agree, please reply by 20 Mar 2022, 23:59 UTC latest. Thanks Axel (on behalf of the openSUSE Board) [1] https://www.europarl.europa.eu/doceo/document/E-9-2020-005058-ASW_EN.html [2] https://c.gmx.net/@329946484294293704/APCSs-yfQMiN4fKa-YpfEw -- Dr. Axel Braun <docb(a)opensuse.org> Member of the openSUSE Board

9 27