May 2021 - openSUSE Project - openSUSE Mailing Lists

lifecycle wiki page
by ddemaio 16 Aug '21

16 Aug '21

Hi all, There was a recent post on reddit (https://old.reddit.com/r/linux/comments/m1xl56/is_opensuse_leap_ready_to_be…) that made us take a look at how to present our lifecycle page (https://en.opensuse.org/Lifetime) and info to be added to the marketing of Leap 15.3. There were several comments on reddit that can be summarized as there is a lack of clear information on how long the lifecycle of Leap 15.x will be going forward. When the info on https://en.opensuse.org/Lifetime was originally written, there was some clarity on major versions lasting a minimum of 36 months. We know Leap 42 and 15 exceeded that lifecycle. It looks like we're at a point where we evolved and need to provide a bit more clarity for people based on the reddit comments I propose we change the lifecycle page to include the following sentences and include the info in the marketing of Leap 15.3 and beyond (for the foreseeable future): Leap *Major Release* (15.x) extends maintenance and support until a successor. At present, a successor has not been declared; Leap 15's lifecycle fully aligns with SUSE Linux Enterprise. There is a projection as of March 2021 that Leap 15 will extend to Leap 15.5. Both major versions of Leap 42 and 15 were supported more than 36 months. Any thoughts, changes, removals or additions to the above sentences. v/r Doug

12 25

[opensuse-project] Can one manually become a "Member Emeritus"
by Stefan Seyfried 09 Aug '21

09 Aug '21

Hi all, after reading https://en.opensuse.org/openSUSE:Members, I understand that I can cancel my membership status with immediate effect and forever. To become a "Member Emeritus", with a "way back" into the community in case things might turn good again, I have to wait for the status request and just not respond to it. But the last such request was almost 3 years ago. IIUC I need to stop all actions on the mailing lists (might be a good idea ;-)) and packaging (not so good) for the bot to pick me up. So is there a manual procedure to follow to become "Member Emeritus"? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 4

Moving from Freenode to Libera.Chat
by Gerald Pfeifer 17 Jun '21

17 Jun '21

Hi everyone, as some of you noticed, lately there've been challenges around Freenode, the IRC network that has been home to a number of openSUSE channels for years. See, for example, https://arstechnica.com/gadgets/2021/05/freenode-irc-has-been-taken-over-by… https://news.itsfoss.com/freenode-controversy/ Approached by several of you we discussed this with those, the board, and the weekly release meeting. There is consensus to move our channels to Libera.Chat ( https://libera.chat ), a new network many other projects are migrating to as well. With help from Antonio and Sasi I already registered the openSUSE project with Libera.Chat (which by itself is not a move yet) and Marcus R. and others are ready to execute the move. The plan of record is to move quickly. If you have any concerns or questions, please advise as soon as possible. Likewise if you support. Thanks, Gerald PS: https://code.opensuse.org/board/tickets/issue/4 publicly tracks this matter on the openSUSE side; feel free to chime in there. -- Dr. Gerald Pfeifer <gp(a)suse.com>, CTO @SUSE + chair @openSUSE

11 21

Need Volunteers to help moderate (oSVC21)
by ddemaio 14 Jun '21

14 Jun '21

Hi all, We are asking for volunteers to help moderate the conference talks. We would like to fill 10 slots. If you are interested, please visit https://etherpad.opensuse.org/p/osc21mods and put your name next one or more of the times you would like to help moderate. We will have a Practice Day on June 16 for live speakers and moderators. v/r Doug

3 4

Heads up: Early Feature request deadline for SLE 15 SP4 / Leap 15.4 is on 26th June 2021
by Lubos Kocman 14 Jun '21

14 Jun '21

Hello openSUSE! I'd like to communicate an early feature deadline for SUSE Linux Enterprise 15 SP4, which is on 26th June 2021. This deadline is for having requests reported in jira.suse.com, not for the actual code submit requests. This is very important to openSUSE Leap 15.4 contributors as 1/3 of Leap 15.4 binaries will be re-used with SUSE Linux Enterprise and therefore submit requests are accepted there. This is important to keep in mind if you plan to update Leap exclusive package which depends on e.g. a library from SUSE Linux Enterprise. This will be the most common type of request according to my current experience from SP3. I was personally a bit surprised to have this deadline so early even prior the OBS setup, as last year had it shortly after the first Alpha. Just to clarify, this deadline is the same for everyone be it a largest partner, community contributor or an employee. openSUSE Leap and Package Hub exclusive packages will have similar deadlines as described in https://en.opensuse.org/openSUSE:Roadmap. We're aiming for the Leap 15.4 GA in early June 2022, therefore deadlines will only slightly vary from the previous release. We already have to feature requests open for 15.4 (usage of appx-utils instead of fb-utils-appx and update of python-pycairo to 1.20). If you're interested and have some open questions, feel free to pop up on Monday's meeting at 3:00 CEST ( https://meet.opensuse.org/FeatureRequests). More details about jira access and meeting at https://en.opensuse.org/Portal:Jump/Policy/CommunitySLEChangeRequests#Weekl… This call is mainly to identify very obvious updates or requests for features that we'd like to have in SLE 15 SP4 and therefore inherited to Leap 15.4. We'll have a harder time to justify requests that cause massive rebuilds, have large impacts, or seem to be risky (package renames etc) later in the development. Here I'd like to clarify that SUSE Linux Enterprise uses a layered structure and in many cases packages have to be updated in the oldest supported code-stream. I recommend checking the true origin of the package (see referenced wiki). Larger or backward incompatible changes to these packages would result in package forks in SP4. Therefore it's not so easy, but the openSUSE release team is here to help you. Requests during later development cycle have a bit more complicated path but there is processes for it as well (https://en.opensuse.org/ECO ). These are just bit more complication to pass and it generally takes longer, so if you want to have less work, please request it early. I'm acting as sort of a partner manager and I'm going to help you with reporting and deduplication on the SUSE side. I'm processing requests together with Neal Gompa and others who join our call on Mondays. Neal and I would like to work on opening the request even further to the community (Most likely by skipping the jira.suse.com from initial report), but I'm bit afraid we won't make it new few weeks. If you're unsure, please reach out to me or Neal over telegram/Email or even irc or simply join the Monday afternoon call. As a side note, SUSE Linux Enterprise 15 SP4 is considered to be the feature release (Tick-tock model). Therefore, we have relatively free hands with requests of updates as soon as they are backed by some reasoning (I need this for x.y.z). Thank you very much for your understanding. Lubos Kocman Release Manager openSUSE Leap

2 4

Re: [opensuse-project] huge amount of SPAM on opensuse-connect
by christian.imhorst＠posteo.de 02 Jun '21

02 Jun '21

Hi, Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt <Lars.Vogdt(a)suse.com>: As such, maintaining 447 [1] openSUSE members should not depend on a single tool. Especially not if the used tool has open, well known security issues since years[2]. On Thu, 21 Feb 2019 11:41:19 +0100 Richard Brown wrote: > This isn't the first time I've asked this question on a public stage, > but in the hope that this time I get an answer; > Who volunteers to tackle the problem with connect.o.o and drive > forward a solution? I made my proposal already and I stand the point: shut down an insecure system! what does "drive forward a solution" mean? Can we integrate the functions of connect.o.o into other services at openSUSE which are allready maintained like the openSUSE wiki? A form for travel support for example? An application for membership could be done by e-mail to an e-mail address of the membership officials. Elections could be done with an eVote software like https://github.com/mdipierro/evote for example, but probably there are better tools. What did I miss? I think Lars is right an we should shutdown this insecure system as soon as possible. Regards Christian Imhorst -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

23 70

oSVC21 Meeting: June 1
by ddemaio 02 Jun '21

02 Jun '21

Hi all, Tomorrow, Tuesday, June 1, we will have planning meeting for the openSUSE Conference at 18:00 UTC. The meetings will take place later in https://meet.opensuse.org/bar. There will be a brief update on the progress of the conference planning and attendance. If you plan on attending the conference, please register https://events.opensuse.org. Registered people will receive a token to use https://opensuse.venueless.events/ If any of you have Ruby skills, there is one feature request that would be nice to have for the conference - https://github.com/openSUSE/osem/issues/2768 v/r Doug

1 1

openSUSE Sprint Thursday May 6
by ddemaio 02 Jun '21

02 Jun '21

Hi all, Our monthly Thursday sprint was scheduled for June 3 at 18:30 UTC. For some, that day is a holiday. I am uncertain of whether to cancel the meeting this month because of this. If only have the people might show up, it might make sense to postpone or cancel it. Let me know what you all think. Should we cancel, postpone or go on with the meeting? The meetings will now take place later in https://meet.opensuse.org/bar. v/r Doug

2 3

Release Party Online 15.3
by Luna Jernberg 01 Jun '21

01 Jun '21

Hello! I will join the Online release party for 15.3 :)

2 3

Re: Moving from Freenode to Libera.Chat
by Carlos E. R. 29 May '21

29 May '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <4217ef4f-ec9a-a8a2-ab3c-7c246848b94(a)Telcontar.valinor> On Thursday, 2021-05-27 at 18:39 +0200, İsmail Dönmez wrote: > On Thu, May 27, 2021 at 5:36 PM Glenn Holmer <> wrote: >> On 5/27/21 8:09 AM, Martin Wilck wrote: ... > I agree with Martin and also with you too. I agree that we should > avoid knee-jerk reactions created by an echo bubble which happens a > lot these days. And we can't have access to all the facts, not yet. > But on the other hand I think what Freenode admins did is > unacceptable. > > Anyhow, I suggest people read > https://gist.github.com/prawnsalad/4ca20da6c2295ddb06c1646791c61953 > and see that both parts are guilty in this, I'd be happier if we moved > to Oftc.net instead. The XFS people are migrating to oftc too. I don't have an opinion. <https://www.spinics.net/lists/linux-xfs/msg52693.html> It worries me that IRC is fragmented. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYLFbEBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV2CsAn0eSZuCSDkBnLyHUNEfm LPCLvIlaAKCIVMyuOfWn9pWpKAuMwrYa2L0CeQ== =lSIk -----END PGP SIGNATURE-----

4 5