July 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

https://en.opensuse.org/Portal:Teams
by Gerald Pfeifer 16 Aug '22

16 Aug '22

Hi folks, by chance I ran into https://en.opensuse.org/Portal:Teams and noticed a couple of oddities (= historical artefacts?) * There is a team "Community Council" listed, which "Solves internal and external conflicts and communication issues". I never heard of that, and indeed following the link it ... redirects to the Board page. => This team best should be removed to reduce possible confusion, alas I don't know how to? The page appears to be generated automatically? Who can help? * The "openSUSE team at SUSE" as such does not exist any longer. And the links is borken. => Same as above; how do we get rid of that entry on that page? * Ditto for https://en.opensuse.org/openSUSE:Openfate_screening (which should be removed) and its entry on that page under the label of "openFATE screening". Any help (or pointers) would be lovely - thank you! Gerald

2 2

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

01 Aug '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

Community Meeting/ALP WG: Week 30
by ddemaio 28 Jul '22

28 Jul '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. The Community Meeting will be on Thursday at 19:00 UTC. Both meetings will be in https://meet.opensuse.org/meeting You can view the meeting notes from the ALP WG and other notes at https://etherpad.opensuse.org/p/weeklymeeting. You can find the Community Meeting notes from last week at https://etherpad.opensuse.org/p/weeklymeeting20220721 One key thing from that to highlight is we were asked to reserve the Z-Bau in advance of next year's openSUSE Conference. We were given a timeframe between May 25 - 29 to reserve the venue. To add to the topics of the conference, please remember of the Call for Papers for the openSUSE.Asia Summit is open until July 31. LOGO Yes, We need a logo from this year's openSUSE.Asia Summit. Find out how to submit your logo idea at https://news.opensuse.org/2022/07/01/osa-cfl/ v/r Doug

2 1

openSUSE on Linux Saloon
by Luna Jernberg 28 Jul '22

28 Jul '22

openSUSE on the Linux Saloon video podcast in 2 weeks: openSUSE on Linux Saloon 23-24th June

2 3

openSUSE Leap on Linux Saloon
by Luna Jernberg 28 Jul '22

28 Jul '22

https://www.youtube.com/watch?v=HejPzBYSExk The latest Linux Saloon episode is about openSUSE Leap

1 0

[opensuse-project] zypper refresh takes double time for update/leap/15.x/sle/ than all others combined
by Felix Miata 26 Jul '22

26 Jul '22

Is update/leap/15.3/sle/ the most populous, containing more packages than any other? What else could account for this obvious sloth, twice the time to refresh sle than all others combined? Behavior is similar for 15.4, since farther back than I can remember, probably since 15.3 was originally released. # 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) : 7 repositories # | Enabled | GPG Check | URI --+---------+-----------+------------------------------------------------------------------------ 1 | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_15.3/ 3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ 4 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ 5 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 6 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/Essentials 7 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/oss/ 8 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/backports/ 9 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ # time zypper ref Repository 'FCL' is up to date. Retrieving repository 'KDE3' metadata ......................................................[done] Building repository 'KDE3' cache ...........................................................[done] Retrieving repository 'Mozilla' metadata ...................................................[done] Building repository 'Mozilla' cache ........................................................[done] Repository 'NonOSS' is up to date. Repository 'OSS' is up to date. Retrieving repository 'PackmanE' metadata ..................................................[done] Building repository 'PackmanE' cache .......................................................[done] Retrieving repository 'Update' metadata ....................................................[done] Building repository 'Update' cache .........................................................[done] Retrieving repository 'UpdateBP' metadata ..................................................[done] Building repository 'UpdateBP' cache .......................................................[done] Retrieving repository 'UpdateNonOSS' metadata ..............................................[done] Building repository 'UpdateNonOSS' cache ...................................................[done] All repositories have been refreshed. real 0m27.997s user 0m2.711s sys 0m0.890s # 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) : 8 repositories # | Enabled | GPG Check | URI ---+---------+-----------+------------------------------------------------------------------------ 1 | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_15.3/ 3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ 4 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ 5 | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 6 | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/Essentials 7 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/oss/ 8 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/backports/ 9 | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ 10 | Yes | ( p) Yes | http://download.opensuse.org/update/leap/15.3/sle/ # time zypper ref Repository 'FCL' is up to date. Repository 'KDE3' is up to date. Repository 'Mozilla' is up to date. Repository 'NonOSS' is up to date. Repository 'OSS' is up to date. Repository 'PackmanE' is up to date. Repository 'Update' is up to date. Repository 'UpdateBP' is up to date. Repository 'UpdateNonOSS' is up to date. Retrieving repository 'UpdateSLE' metadata .................................................[done] Building repository 'UpdateSLE' cache ......................................................[done] All repositories have been refreshed. real 1m2.752s user 0m23.481s sys 0m2.810s # -- 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

3 3

Reminder: All SLE 15 SP5 feature requests need to be evaluated until 29th July (this Friday)
by Lubos Kocman 25 Jul '22

25 Jul '22

Hello openSUSE! To start on a positive note, this deadline does not apply for Community/Leap only changes, which do not require any changes on the SLE side. There, we have time until the Beta code submission deadline next year. So this deadline is really for Leap changes that are otherwise blocked by SLES or generally any update requests to SLES. These requests need to be evaluated (in jira) and moved to engineering, which means to be approved by SLES product and project management. I went through all community requested features in *code-o-o, and so far, all should be processed. Each of Leap 15.5 features touching SLE packages should have linked Jira (done by me). Please reach out to me if I missed your feature. If you have anything last minute, then please report it in code-o-o, provide quick summary (see mdadm update request as an *example) why is the change needed and reach out to me as quickly as possible. Otherwise, PM might not get to evaluate it on time, and it will be tracked as a late feature. Late feature is not a big deal, but it also might simply not be approved later on, especially if it's a more significant change. Keep in mind that 15.5/15 SP5 is expected to be a conservative release. Let's rather be on the safe side, report it early. Leap 15.5 has not yet bugs in *Bugzilla, so checking for any "masked feature request" was quick. (Original 15.5 early planning call) https://lists.opensuse.org/archives/list/project@lists.opensuse.org/thread/… Thank you very much for your understanding Lubos Kocman openSUSE Leap Release Manager [0]https://en.opensuse.org/openSUSE:Roadmap [1]https://code.opensuse.org/leap/features/issues [2]https://code.opensuse.org/leap/features/issue/82 [3]https://bugzilla.opensuse.org/buglist.cgi?cmdtype=dorem&remaction=run&nam…

1 0

Re: ALP WG Meeting minutes - July 5th 2022
by Dan Čermák 24 Jul '22

24 Jul '22

Jiri Slaby <jslaby(a)suse.cz> writes: > On 05. 07. 22, 17:46, Dan Čermák wrote: >> we have mostly focused this week's meeting on how the ALP Desktop is >> going to look like and how we can dispel fears around flatpaks and >> containers when it comes to the ALP desktop. > > I have never looked into this container stuff in more detail. But one of > the concerns I was always afraid of was how this behaves WRT shared > libraries and their memory footprint? IOW, containers kill the purpose > of shlibs completely and one has to hold all of the versions (per each > container on the top of ones from the base system) in memory, right? > This sounds as if using static libraries. A small follow up on this one, more in the context of flatpaks though. The question has been raised, whether flatpaks sharing a runtime would benefit from memory deduplication of shared libraries in the common runtime. The short answer is: yes. The longer and much more elaborate answer can be found in this great reply from upstream: https://github.com/flatpak/flatpak/issues/4997#issuecomment-1192616912 So as long as we don't stop dynamically linking, there shouldn't be any huge memory penalties for flatpak applications. Cheers, Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman

1 0