openSUSE Project April 2022

project@lists.opensuse.org

28 participants
20 discussions

by ddemaio

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 months, 1 week

[opensuse-project] zypper repos (lr)

by Felix Miata

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 months, 2 weeks

Fwd: Summary of a call on the topic of Cisco's openh264 distribution for openSUSE

by Luna Jernberg

---------- 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 >

2 months, 2 weeks

Reminder meeting : openSUSE Board meeting next Monday (13:00 Europe/Berlin)

by openSUSE Meeting Reminder

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 months, 2 weeks

oSC22, OSCAL Summit and Community Meeting: Week 13

by ddemaio

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 months, 2 weeks

Community Meetings: Week 14

by ddemaio

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

2 months, 2 weeks

How to build a FOSS maintainer community (Was: Planning decomission of software.opensuse.org)

by Henne Vogelsang

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

2 months, 3 weeks

openSUSE Finalizes New Code of Conduct

by ddemaio

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

2 months, 3 weeks

Minutes of openSUSE Board meeting 2022-02-28

by Gerald Pfeifer

[ 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.

2 months, 3 weeks

Threat to privacy by preinstalled operating systems

by Axel Braun

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

2 months, 3 weeks

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project April 2022