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
See, for example,
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.
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
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.
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
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.
Release Manager openSUSE Leap
Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt
As such, maintaining 447  openSUSE members should not depend on a
single tool. Especially not if the used tool has open, well known
security issues since years.
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
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
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
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
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
Should we cancel, postpone or go on with the meeting?
The meetings will now take place later in https://meet.opensuse.org/bar.
-----BEGIN PGP SIGNED MESSAGE-----
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
> Anyhow, I suggest people read
> 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.
It worries me that IRC is fragmented.
Carlos E. R.
(from openSUSE 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
I would like to share some great news with you on behalf of the
openSUSE Release team.
openSUSE Leap 15.3 Build 160.3 was accepted as the Gold Master. So
we're on time for the planned Global Availability next week on the 2nd
of June. Submissions that didn't make it will have be released as
The entire openSUSE release team would like to give a big thanks to all
of you who participated in the release. You all made Leap 15.3 happen!
Talking about dates, I'd like to correct my previous statement about
SUSE Linux Enterprise 15 SP3 GM date as it happened last Thursday,
therefore according to the schedule. There seem to have been some
miscommunication on both sides.
Some changes to the release process that you will most likely notice.
We did adapt the release process to pre-agreed changes from openSUSE
Leap 15.2 retrospective and will no longer explicitly hide images. We
expect to eliminate any issues on the mirror side. We've had a
discussion about this on last year's retrospective review. The outcome
can be found in
We also improved the signing of images as suggested in the
retrospective. This will hopefully show you that we take retrospectives
The official release announcement will be sent on the 2nd of June as
planned in our https://en.opensuse.org/openSUSE:Roadmap
This date is important not only from a marketing point of view but also
for the 0day maintenance part of the release. Some updates that we'd
like to have available with the GA are aiming at that date.
Same as last year, the Release retrospective survey will be open on GA
day. We'd like to kindly you about what went well and what didn't go
too well in this release. We will then review it together on my
Workshop on the upcoming *oSVC2021.
Thank you very much for all the hard work!
openSUSE Release team
Today, Tuesday, May 25, 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, attendance and emails sent out to
The meeting will provide a status update from last Friday's video team
If you plan on attending the conference, please register
https://events.opensuse.org. Registered people will receive a token to
If any of you have Ruby skills, there is one feature request that would
be nice to have for the conference -