Just now I happened to stop by https://www.opensuse.org, and noticed
this:
CONTRIBUTE TO OPENSUSE
Be part of our community contributing with any of the following:
Code or hardware.
Firstly, I appreciate it is written in capitals, but shouldn't it still
be "openSUSE" ? Second, code and hardware are the only ways to
contribute ?? That seems a bit limited - shouldn't we be a bit more
inclusive?
I know the overlay that appears once you click "code" has more options,
largely copied from here:
https://en.opensuse.org/Portal:How_to_participate
Maybe it's just me, but when the first reply to "How to contribute"
is "code or send us some hardware", that's a bit too
limited. "Hardware" is surely not exactly the most common option
either ...
I honestly don't know what the most common ways are, although I expect
code is certainly one.
--
Per Jessen, Zürich (27.1°C)
Member, openSUSE Heroes
Hello openSUSE!
now when Leap 15.4 RC and Leap Micro 5.2 GA announcements are settled
let's go now for something completely different.
I'd like to invite you to a newly formed Community Work Group (or CWG)
around the new *Adaptable Linux Platform
https://en.opensuse.org/openSUSE:ALP/Workgroups/Community
We'll initially focus on transparency during ALP planning, prototyping,
and related public communication, opensuse infra readiness . There are
topics where we can already start working right now. The first desktop
*workshop has shown us that we need to focus on areas such as single
place for documentation, our "signature" look and feel, brand
recognition, event calendar, etc.
We will to turn feedback from the workshop into action items and ensure
we have WG members working on them.
We have a big opportunity in this regard since unlike SLES 15 , ALP is
going to (and already being *prototyped) be built in OBS by default.
If you're interested then please tell us which one of existing weekly
community weekly slots (Tuesday/Thursday) should be used for regular
CWG meetups https://doodle.com/meeting/organize/id/b68562Ve
[0]https://lists.opensuse.org/archives/list/project@lists.opensuse.org/threa…
[1]https://en.opensuse.org/openSUSE:ALP/Workgroups/Community/Workshops/LeapD…
[2]https://build.opensuse.org/project/show/devel:LEO
Hello openSUSE!
I'm happy to announce that our brand new distribution Leap Micro 5.2 is
now Globally Available.
More information and download links and deployment demo can be found at
https://get.opensuse.org/leapmicro/5.2/ or our *release notes.
Let me remind users that the main documentation source for Leap Micro
is SLE Micro documentation referenced bellow. The same applies to Leap
itself.
We recommend to try our self-install image for VM and host deployments
(see demo on download page).
For security reasons images have no root password set so you'll have to
use *ignition or combustion to set it up (unless you use the Offline
installer).
People who are interested in k3s use case should have a look at the
recent *work of Atilla. the combustion should work on both SLE/Leap
Micro and MicroOS. I would like to consider offering recommended
combustion scripts as part of the image download/experience on get-o-o.
Big thanks to all that participated!
[0]https://doc.opensuse.org/release-notes/x86_64/openSUSE/LeapMicro/5.2/
[1]https://documentation.suse.com/sle-micro/5.2/html/SLE-Micro-all/cha-selfi…
[2]https://code.opensuse.org/adathor/combustion-dotconf/
Hi all,
Our Regular Community Meetings will return to the normal times. For the
past two weeks, the times were bumped up for an hour.
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
and openSUSE Summit at OSCAL. We will have our 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
Additionally, I would like to thank the people who have helped to
translate the Release Announcement at
https://en.opensuse.org/Release_announcement_15.4. There are many other
languages it can be translated to, so please feel free to help translate
the announcement into a language you know.
Also, please help us take screenshots for the release of Leap 15.4 and
exchange the new photos with the old ones (Leap 15.3) in this wiki page
https://en.opensuse.org/Portal:15.4/Screenshots.
Have a great day.
v/r
Doug
Hello openSUSE!
if you follow the Release Engineering meeting minutes then you're aware
that we're a bit late with the delivery of Leap 15.4 RC.
There are a few reasons. One of them is the fact that we've stopped
using the snapshot mechanism for incoming changes after SLE 15 SP4 RC
and the fact that SLES 15 SP4 was quite busy with post-RC changes
including a mass rebuild last weekend. Since unlike prior 15.3 we're
tailing SLES we will always be a week or two late from SLES 15. X RC.
We were close to having a build last Friday/Saturday before the mass
rebuild of SLES, however, we were affected by broken IBS->OBS sync
which resulted in certain binaries missing, and that failed our product
builds.
Aside from our infra issue, we've also needed to eliminate build fails
on x86_64 most of them were related to python Problematic python-
cryptography was undecided until Wednesday
https://bugzilla.opensuse.org/show_bug.cgi?id=1198851
The cryptography update will land as SLES 15 SP4 update therefore we've
decided to temporarily remove related build fails. We will re-add them
once the update python-cryptography arrives.
The very last build (seamonkey) on aarch64 just finished and there are
no planned changes to be taken into SLES 15 SP4 as of now.
With that said I feel confident that we will have a new build today,
I'll keep an eye on testing and if we'll have no significant regression
we'll publish the current build as our Release Candidate early next
week.
Regarding the Leap 15.4 release which is currently schedule d for 8th
June. SLES 15 SP4 had a Gold Master Candidate code submission deadline
on Wednesday, May 11th. We can't make Leap Gold Master Candidate until
SLES 15 SP4 will announce a final GM build.
So we're currently blocked on further progress. According to my
experience if the GM build will happen next week. Then we could aim for
our GM the week after. Which would still be aligned with the current
Leap roadmap. Any delay on the SLE side will impact our roadmap as
well.
At this point we can take only fixes for SHIP_STOPPERS. To my knowledge
there are no *candidates nor *confirmed ship stoppers at the moment.
The last one was Bug #1199388
Thank you very much for your understanding.
Lubos
[0]
https://bugzilla.opensuse.org/buglist.cgi?cmdtype=dorem&list_id=13642778&na…
[1]
https://bugzilla.opensuse.org/buglist.cgi?cmdtype=dorem&list_id=13642779&na…
= Board Meeting Monday 9 May 2022 13.00 CEST =
Axel, Gerald, Maurizio (bad connection), Syds, Atilla, Neal
Guests: Doug, Emily
Excused: Gertjan
== Board meeting before oSC ==
* https://code.opensuse.org/board/tickets/issue/45
* Axel, Gerald, Gertjan, Maurizio (maybe), Neal able to attend
* Atilla cannot make it
* Syds cannot make it IRL (but join online for the board sessions at the event)
* Looks like SUSE is going to be in the new office, close to the event, by that point
* Monika kindly helping to arrange for a meeting room
* If anything needs anything paid upfront, please contact Gerald and Doug. (via board(a)o.o with cc Doug)
== TSP update ==
* https://code.opensuse.org/board/tickets/issue/48
* HSBC being tested for paying out. SUSE Finance is waiting on a demo to confirm if it is viable for cash transfers.
* one person has requested TSP for oSC after the pauze started, Doug replied know that we don't know how quick the payment can come.
== Logo Usage ==
* https://code.opensuse.org/board/tickets/issue/47
* request is approved, Axel will reply.
* New requests don't have to be discussed during the meeting, one board member can email back directly to speed up the process. Mention that it needs to in line with the Guiding principles and the trademark guidelines. and if possible sent us an example of the sticker if they want.
== FSFE Right to repair letter ==
* https://code.opensuse.org/board/tickets/issue/46
* https://twitter.com/fsfe/status/1519239571522916352
* Agreed to sign as Board
* Need to bring up during oSC if Board can sign these types of requests as Board or as Project by choice of the Board.
Meeting closed at 14.00 CEST
--
Syds Bearda
Treasurer openSUSE Project
opensuse(a)syds.eu