July 2022 - openSUSE Project - openSUSE Mailing Lists

[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

Re: ALP Git-Packaging-Workflow group created
by Neal Gompa 21 Jul '22

21 Jul '22

On Wed, Jul 20, 2022 at 8:44 AM Jan Engelhardt <jengelh(a)inai.de> wrote: > > > On Wednesday 2022-07-20 14:13, Dirk Müller wrote: > > > >* Exploration of the Git Hosting options (run by me) openSUSE already has some > >experience with Pagure.io (used by https://code.opensuse.org/ for example) and > >GitHub (used by various openSUSE projects under https://github.com/openSUSE) > >as well as some projects also in GitLab (used by a few community efforts as > >well as SUSE-internally for hosting) so we explored another option named > >Gitea, which is now available to the community under > >https://gitea.opensuse.org/. > > gitea with the lfs approach works well. > > I wonder how the ipfs symlinks stored in pagure would be handled. > Fuse mount, or another global hook like git-lfs? > Right now, we don't have any blob storage system attached to Pagure. We can do whatever we want for this. Fedora's Dist-Git setup[0] leverages a wrapper tool called fedpkg[1] built on the rpkg[2] framework. We don't have to do it the same way, but there are a lot of nice things from having a swiss army knife tool for packaging. We have this today with OBS through osc, for example. After working with Git-LFS for years for normal development, I'm not a huge fan of it. A couple of issues I have with LFS: * It's incredibly difficult to mirror LFS, and there's no straightforward way to do it with git repos, given how the integration works * LFS easily breaks when modifications occur across forks, and it's difficult to identify the problems there and fix them There are other issues that happen specific to LFS server implementations. For example, GitLab's implementation imposes ACLs on each blob which makes it difficult for forks made by non-members to work reliably. GitHub's implementation has issues where smudging can be broken when doing complex merges that have LFS objects touched. For some of the awkwardness around Dist-Git, these problems don't happen because it's a transparent blob cache and the only thing written to Git is a plain text file with the filename and checksum, which is used as the blob reference. Authorization to upload and download those blobs is controlled by packager ACLs or whatever you wish to use to control that, making it effectively global, so it works properly across forks, or even cross-server forks. With my downstream hat, that's also useful if I'm building patched derivative packages, because I can use the Dist-Git server references even without my own Git repo on my own Git server. It makes CI and all kinds of other things easier too. [0]: https://github.com/release-engineering/dist-git [1]: https://pagure.io/fedpkg [2]: https://pagure.io/rpkg > >* Exploration of the history import from the SUSE and openSUSE build service > >source history [...] > >Your feedback on the history import quality and how it could be made > >better is very much > >appreciated. > > I would make the case that OBS history is not particularly interesting > for its messages, because (a) we have had .changes files, > (b) the SVN-ish nature of the OBS SCM meant that you can't go back > and edit messages or commits, so there is little incentive to write > up much if you missed it in the first commit. The history is better than nothing because things like Git blame work reasonably okay. When Bernhard was working on the original setup, he didn't bother because it was a read-only setup. If we transition to Git, we probably want the attribution and messages to be more accurate because the Git history is useful for working through the package's development. It would also open the door for things like rpmautospec to be used in the future[3]. [3]: https://docs.pagure.org/Fedora-Infra.rpmautospec/ -- 真実はいつも一つ！/ Always, there's only one truth!

3 3

Re: ALP Git-Packaging-Workflow group created
by Adrian Schröter 21 Jul '22

21 Jul '22

On Donnerstag, 21. Juli 2022, 09:34:17 CEST Jan Engelhardt wrote: > > On Wednesday 2022-07-20 16:37, Dirk Müller wrote: > > > >> I would make the case that OBS history is not particularly interesting > >> for its _messages_ [..] > > > >[.. ]There are some suggestions around using git notes for the end-user > >changelog, but that hasn't been evaluated in detail yet. Any > >suggestions or input welcome. > > Adam Majer held a conversation with a few individuals ahead of the > openSUSE conf 2022 for thoughts, I'd like to repaste some of that > since it was originally off-list and still hope to see this coming to > build.opensuse.org soon. > > --- > > Date: Tue, 31 May 2022 15:33:31 +0200 > From: Jan Engelhardt > To: adamm > Cc: stroeder > > On Tuesday 2022-05-31 12:50, Adam Majer wrote: > > > https://build.opensuse.org/project/show/devel:ALP > > https://code.opensuse.org/adrianSuSE/Alp > > https://code.opensuse.org/adrianSUSE/zypper > > https://code.opensuse.org/package/zypper > > > > Internally, most of the feedback from maintainers I've talked to is > > along the lines of "ok, so I'll have to adapt to this I guess", ie. > > not enthusiastic :-) > > > > I would like to get your thoughts about this and any suggestions of > > what you would expect this "new" approach to have. > > * Because the git checkout does not have the .osc directory, the osc > build line is a bit longer than usual. > > osc build --alternative-project openSUSE:Factory standard x86_64 pdns.spec the current osc can checkout a scmsync package. You get a local git clone, but osc remains working with local builds inside. The downside atm is that it still creates a .osc which need to be ignored by git. I hope we will find a better solution for that in future. Try osc co home:adrianSuSE:OBSGIT git-example-1 for an example package which defines a git url. At least osc-0.179 is required for this though. > * Checking out /package/zypper: the tarball is a (dangling) symlink to > /ipfs. > > ALP is "just" a spin/a distribution -- let's deploy this git scheme for > an "actual" development prj and see how that works out. I could think > of a few to spare for the experiment that have low volume > (security:netfilter, maybe network:telephony). > > > > Also, any sticking points when it comes to current (current OBS) > > workflow that git could improve? > > * Some command-line equivalent for `osc sr` will be needed if git is used as a > backend. `git push` to /jengelh/zypper is (would be) easy, but making > the actual SR/MR/PR.. if I don't know better, would require opening a > browser, and one shouldn't have to go to a browser. A sr would not transfer the git information atm (and on purpose). That means you can work with such a git setup in your devel or home project and submit request the result to factory for example. However, the long term plan here is that the sr gets actually replaced by a pull request in the git hosting instance. -- Adrian Schroeter <adrian(a)suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

1 0

Re: ALP Git-Packaging-Workflow group created
by Dirk Müller 20 Jul '22

20 Jul '22

Hi Jan, > I wonder how the ipfs symlinks stored in pagure would be handled. > Fuse mount, or another global hook like git-lfs? For now we're not looking at the pagure setup at all. I personally have no experience with ipfs and it wouldn't work for the certified part of the SUSE product building, so it is a dead end. We're taking Git with LFS as plan A, unless there are compelling reasons against it, we will not look back. > I would make the case that OBS history is not particularly interesting > for its messages, because (a) we have had .changes files, > (b) the SVN-ish nature of the OBS SCM meant that you can't go back > and edit messages or commits, so there is little incentive to write > up much if you missed it in the first commit. Right, the *.changes files are still part of the commit content, so you get these as part of the commits (and follown commits). There are some suggestions around using git notes for the end-user changelog, but that hasn't been evaluated in detail yet. Any suggestions or input welcome. Greetings, Dirk

1 0

ALP Git-Packaging-Workflow group created
by Dirk Müller 20 Jul '22

20 Jul '22

Git Packaging Workflow Exploration A few colleagues from SUSE, namely the build service team and others like myself are exploring the options on what the best way would be to use Git, rather than the current open Build Service source handling, for storing openSUSE / SLE package sources. This was originally launched under the ALP Workgroup umbrella but for now is timeline wise decoupled from this effort, except that if we would decide to switch, that it would have to happen before the first commercially supported Alp release would be branched off openSUSE Factory. For now, all of this is in the exploration and experimentation phase and no decision in either way has been taken. Meanwhile, we do however feel confident and organized enough to be open to wider feedback. If you're interested in any of the topics please let the work package driver know, or if in any doubt contact me. Here's the current list of work packages and their state: * Exploration of the Git Hosting options (run by me) openSUSE already has some experience with Pagure.io (used by https://code.opensuse.org/ for example) and GitHub (used by various openSUSE projects under https://github.com/openSUSE) as well as some projects also in GitLab (used by a few community efforts as well as SUSE-internally for hosting) so we explored another option named Gitea, which is now available to the community under https://gitea.opensuse.org/. Please note that this is not a production service, and can lose data or disappear at any point in time, it is only being operated in the context of the Git packaging workflow exploration. * Exploration of the history import from the SUSE and openSUSE build service source history (run by Stephan Kulow). Stephan Kulow has managed to import the majority of existing history of packages that landed in released products or in openSUSE Tumbleweed as history into package-git repositories and published under https://gitea.opensuse.org/rpm . As an example the history of zlib is here: https://gitea.opensuse.org/rpm/zlib/commits/branch/factory which is significantly more detailed than a similar effort implemented by Bernhard Wiedemann a couple of years ago on our code.opensuse.org instance: https://code.opensuse.org/package/zlib/commits/master Your feedback on the history import quality and how it could be made better is very much appreciated. The key difference compared to the pagure setup is that we use Git LFS for storing large files (like tarballs for example) and currently these large files are mapped via a small redirector proxy directly to the openSUSE build service source service. With that the git repository history is extremely small and very manageable for local cloning. * Exploration of the git packaging workflow going forward. Alberto Planas, with contributions by others, has written up ideas and options in the following document: https://github.com/aplanas/openSUSE-git/blob/main/notes-about-git.md Please provide feedback either as a pull request or as a discussion entry in the forum here: https://github.com/aplanas/openSUSE-git/discussions * Exploration of build and status integration. This one is less well-defined, but for now it is about automatically syncing new changes in the git repository with the state of the Build Service instance that is used for building as well as exploring the options for reporting back the build status into the Git Hosting infrastructure. This is currently worked on by Adrian Schroeter. We store the meeting time and minutes under https://en.opensuse.org/openSUSE:ALP/Workgroups/Git-Packaging-Workflow In case there are any questions, feel free to reach out to related work package owners or myself. Greetings, Dirk

1 0

Raw results from openSUSE Leap 15.4 retrospective are available!
by Lubos Kocman 19 Jul '22

19 Jul '22

Hello openSUSE! Big thanks to everyone who participated in the openSUSE Leap 15.4 release survey. And yet again apologize for the initial miscommunication. We received incredible 760 responses in total, which is a nice increase compared to the previous years (605, 409). Raw data is already available at https://en.opensuse.org/Portal:15.4/Retrospective As for the past two releases, I want to yet again process the release retrospective results in a few public rounds, categorize responses, and share feedback with respective teams once done. We had at least three rounds of review last time. Numbers tell me we'll need more this time, or we need to find a more effective way of categorizing. We'll announce more rounds if necessary. https://meet.opensuse.org/meeting Monday 18th July 9:00 am - 10:00am CEST Tuesday 19th July 3:30 pm - 4:40 pm CEST (Before regular meeting) Thursday 21th July 8:00 pm - 9:00 pm CEST (Before regular meeting) Best regards Lubos Kocman openSUSE Leap Release Manager

1 1

minutes Board Meeting Monday 2022-07-18 13:00 CEST
by Syds Bearda 18 Jul '22

18 Jul '22

= Board Meeting Monday 2022-07-18 13:00 CEST = * Present: Axel, Gerald, Gertjan, Maurizio, Neal, Syds, Gertjan * Guests: Doug * Not present: Attila == TSP Program Update == * Doug: still work in progress with SUSE Finance, manager. Reached out to new contact within Finance * TSP is still a work in progress from SUSE Finance. Some TSP's have not been paid yet, but those are being worked through by SUSE Finance. Payment will come soon (hopefully). * TSP in general it's a point of frustration, cause of no movements from SUSE. New people are looking at and needs to be explained, currently decisions are going to be made higherup at SUSE. * If Doug needs our help, he'll let us know. == Moderator accountability across all platforms == * https://code.opensuse.org/board/tickets/issue/9 * Meeting in the next two weeks * AI Maurizio to call for that meeting == Creating a consistent way to document differences in policy between devel projects == * https://code.opensuse.org/board/tickets/issue/20 * Closed for lack of activity for a year == Bar t-shirts == * https://code.opensuse.org/board/tickets/issue/31 * Board will support once becomes active again; closing for now. == openSUSE online communities == * https://code.opensuse.org/board/tickets/issue/38 * Code of Conduct has been rolled out (and was triggered by this ticket). == Make Membership / Election official aware of all members of the Emeritus Members group. * https://code.opensuse.org/board/tickets/issue/49 * https://code.opensuse.org/board/tickets/issue/5 * AI: get list from Simon (Gerald reached out to Simon) == Follow-up from oSC: "A Fork in the Road" == * Syds reached out to Patrick, still needs to talk to him regarding research on legal entities. Continued at private part at CEST 13.35 Meeting closed at CEST 14.00

1 0

Minutes of openSUSE Board meeting 2022-07-04
by Maurizio Galli 18 Jul '22

18 Jul '22

= Board Meeting Monday 2022-07-04 13:00 CEST = * Present: Attila, Axel, Gerald, Maurizio, Syds, Gertjan ( late ) * Guests: Doug, Emily * Excused: Neal == Follow-up from oSC: "A Fork in the Road" == * openSUSE Futures session initiated by the board at openSUSE Conference * Recording of opening session at https://youtu.be/ixx8uQQwr90 * Recording of closing session not yet available. * Patrick Fitzgerald kindly agreed to do some research about legal entities * AI Syds: contact Patrick Fitzgerald * AI all: gather snippets we want to put together, then work on mail to project@ in next meeting == Mod team == * Mod team needs to meet and decide if the document summarizing the mission statement and practices is ready to be shared with the community. == openSUSE.Asia Summit == * Maurizio and Attila should represent the board with a keynote Meeting closed

1 0

Community Meeting/ALP WG: Week 29
by ddemaio 18 Jul '22

18 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. BOARD MEETING The biweekly board conference call with the board is scheduled for today at 13:00 Europe/Berlin time. The meeting will be in the regular Board Meeting Room at https://meet.opensuse.org/OSBoard ASIA SUMMIT CFP The Call for Papers for the openSUSE.Asia Summit is now open until July 31. That leaves 27 days to submit your proposal for the online event. Submit your proposal at https://events.opensuse.org. Please find the news at https://news.opensuse.org/2022/07/01/osa-cfp/ 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

1 0

Re: Raw results from openSUSE Leap 15.4 retrospective are available!
by Marcus Meissner 15 Jul '22

15 Jul '22

Hi, On Thu, Jul 14, 2022 at 09:02:19PM +0300, Andrei Borzenkov wrote: > On 14.07.2022 20:55, G McAlister wrote: > > On 14/07/2022 17:53, Andrei Borzenkov wrote: > >> On 13.07.2022 15:14, Jan Engelhardt wrote: > >> ... > >>> * https://download.opensuse.org/update/leap/15.3/sle/repodata/4c483b355b0c317… > >>> is 101 MB. > >>> > >>> The big elephant in the room: xz compress it. It's 28 MB. > >>> (Similar gains for the other xml.gz files I guess) > >>> > >>> * I know zypper does a file conflict check, but it does that > >>> right before rpm transaction start when it already has all the rpm files (and > >>> thus contents). Why do we need filelists.xml at all? > >> I wonder when it is downloaded at all? This file is not in > >> /var/cache/zypp/raw, this file is not present in zypper.log. Four files > >> downloaded by zypper are deltainfo, updateinfo, susedata, primary. > >> Actually looking at libzypp, it explicitly skips filelists. > >> > >> File lists used by command-not-found come from primary.xml. > >> > > The Remote Mirroring Tool (RMT) downloads filelists.xml. > > > > RMT by definition mirrors repository, so it downloads everything in this > repository. In any case, it has no impact on end-system update time - > repository download happens before repository mirror is used for update. I have opened a ticket, and Adrian also found there is some weird setting missing that reduces download speed (some meta checksumming issue). Ciao, Marcus

1 0

Re: Raw results from openSUSE Leap 15.4 retrospective are available!
by Marcus Meissner 13 Jul '22

13 Jul '22

On Wed, Jul 13, 2022 at 01:46:54PM +0200, Jan Engelhardt wrote: > > On Wednesday 2022-07-13 12:52, Lubos Kocman wrote: > >Raw data is already available at > >https://en.opensuse.org/Portal:15.4/Retrospective > > The summary of the "bad" column: > > >* certbot is gone at least this is meanwhile resolved. > >* packages too old > >* slow repositories (actually, from own experience, > > it's due to the *size* of the rpmmd files being outragerous) This is something we need to think about, split update repos perhaps into multi arch again. > >* patent related user "issues" with ffmpeg > >* non-patent related user issues with ffmpeg > >* some issue that should have been a bugzilla report instead of a > > retrospective response Ciao, Marcus

1 0

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

08 Jul '22

Hi all, Since I won't be at the WG on Tuesday, I'm sending this out now. We had a community meeting last night and created a merchdesigns folder in https://github.com/openSUSE/artwork. This folder is for spreadshirt designs for merchandise. If anyone is interested in creating a design for an openSUSE t-shirt, please feel free to put it in there. You can find the meeting notes from last nights community meeting at https://etherpad.opensuse.org/p/weeklymeeting20220707 The ALP Work Group (WG) will take place on July 12 at 14:30 UTC. The Community Meeting will be on July 14 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. The Call for Papers for the openSUSE.Asia Summit is open until July 31. Please submit your proposal at https://events.opensuse.org. There is also a need for a logo. Find out how to submit your logo idea at https://news.opensuse.org/2022/07/01/osa-cfl/ v/r Doug

1 0

Re: ALP WG Meeting minutes - July 5th 2022
by Lubos Kocman 07 Jul '22

07 Jul '22

Hello openSUSE! I'm happy to see these discussions, and this is precisely why we need to plan in an open way! I have an understanding of many concerns which are being raised here. Just an idea that I discussed with Dominique a few days ago. My first-time personal experience with our current "Immutable Desktop" was quite good, but not perfect. I definitely would have some RFEs, which seem to be relatively low-hanging fruits that would improve my day-to-day experience by a lot (mostly default configuration) I can see how the entry barrier may appear too high to people meeting such a concept for the first time. I'm thinking of an idea to make a "workshop" where users would install MicroOS Desktop and try to use it for a week, and then we'd meet to talk about the user experience, both good and bad). I think people liked our last *workshop. We've had around 50 visitors in total. We could start putting together known issues (FAQ), try to propose some changes, and make sure they're being tracked for ALP GA. Thoughts? [0]https://en.opensuse.org/openSUSE:ALP/Workgroups/Community/Workshops/LeapD…

2 1

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

07 Jul '22

Jan Engelhardt <jengelh(a)inai.de> writes: > On Wednesday 2022-07-06 11:48, Dan Čermák wrote: >>> >>> 1) What are the advantages of flatpak/container vs RPM? >> >>Flatpaks support sandboxing when configured properly giving you greater >>security benefits in comparison to traditional rpms. > > But that is not inherent to the flatpaks themselves. As you say, > flatpaks are but a different method of _distributing_ software. And > so the critique becomes: stop distributing software twice. That's what will happen. Currently we distribute software for every code stream and with flatpaks we hope to reduce the burden on our maintainers and allow them to distribute it only once. > To make flatpaks (or, at this point: sandboxes) more widely accepted, > generate them on the fly from an existing system, i.e. from {an rpmdb > and loose files} rather than from a set of .rpm files. Sure, that would be nice to have. But creating such a system is a lot of work which is really hard to justify if there is already a perfectly functioning and widely adopted system in place. 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

3 3

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

07 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 lot of the containerized software is written in Go and that is already statically linked, so my guess is that no one really looked at this so far. However with flatpaks the situation is different and it would be theoretically possible to deduplicate shared runtimes of flatpaks. Unfortunately I don't know whether that is actually done in practice or even feasible. > And what about userspace live patching? Would we provide it for SLE for > all the containers? Or don't you expect these continaers to be available > on SLE (which would be against the advertised purpose, it seems)? This would be a question for Libor, who is driving the Kernel and Live Patching WG. 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

Nest with Fedora 2022
by ddemaio 07 Jul '22

07 Jul '22

Hi all, As you well know, Fedora and openSUSE have long been sponsors and supporters of each other's conference. In addition to all the tools, projects and friendships we share, taking part in each others conference helps us grow and support the open-source communities. Registration for Nest with Fedora 2022 is open. It will be August 4, 5 & 6. Please register for the virtual conference at https://hopin.com/events/nest-with-fedora-2022 v/r Doug

2 1

Community Info: Meeting/ALP WG/Board Meeting/Asia Summit CfP&Logo Week 27
by ddemaio 07 Jul '22

07 Jul '22

Hi all, The ALP Work Group (WG) will take place tomorrow at 14:30 UTC. We plan on having a special guest to ask questions to about ALP. Please be reminded that these WG are opportunities to discuss & help shape ALP. 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. BOARD MEETING The biweekly board conference call with the board is today at 13:00 Europe/Berlin time. It about 90 minutes. The meeting will be in the regular Board Meeting Room at https://meet.opensuse.org/OSBoard Current Topics are: https://code.opensuse.org/board/tickets/issues?status=Open&tags=meeting ASIA SUMMIT CFP The Call for Papers for the openSUSE.Asia Summit is now open until July 31. That leaves 27 days to submit your proposal for the online event. Submit your proposal at https://events.opensuse.org. Please find the news at https://news.opensuse.org/2022/07/01/osa-cfp/ 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

8 23

Minutes of openSUSE Board meeting 2022-05-23
by Gerald Pfeifer 04 Jul '22

04 Jul '22

[ We noticed those minutes weren't posted back then, and I volunteered to remedy that situation. Posting and Wiki... ] = Minutes of openSUSE Board meeting 2022-05-23 = Present: Axel, Gerald, Maurizio, Syds, Gertjan, Neal Guests: Doug, Emily Excused: Atilla == Board meeting before oSC == * Day 1: Gerald recommens to start a bit later, so 1000h-1800, since SUSE is moving offices in Nürnberg around that week. * Day 2 start at 0900, Gerald needs to leave noonish * https://code.opensuse.org/board/tickets/issue/45 * Axel, Gerald, Gertjan, Maurizio, 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 * Doug has another meeting scheduled for tomorrow. == Logo Usage == * https://code.opensuse.org/board/tickets/issue/47 * request is approved, Axel had a good exchange, ticket closed. == openSUSE online communities == * https://code.opensuse.org/board/tickets/issue/38 * Made good progress * Plan status update at the conference and release a bit afterwards. == Going through some older tickets == * #27 Create mailing list (or some other platform) for all moderators across all media (forums, lists, Telegrams, IRC,...) ** https://code.opensuse.org/board/tickets/issue/27 ** AI Gertjan to check and update- mau: we can close this one and create a new one or merge with issue #38, first check if ML is working * #11 Enable community repositories during installation ** AI Neal to check and update Meeting closed at 13:57 CEST

1 0

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

02 Jul '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.

1 0