openSUSE Project October 2020

project@lists.opensuse.org

24 participants
19 discussions

Re: [opensuse-project] Does the elephant in the room of openSUSE mailing lists exist?
by Per Jessen 22 Oct '20

22 Oct '20

Adrien wrote: >>> My humble suggestion to solve all these 4 problems at once, made >>> already but rehearsed here, goes like this: >>> a) authorize by default all and only those email addresses that >>> users have registered against the current openSUSE auth + login >>> system to send to any ML, no matter which >> >> This is doable, a nomail subscription for all. Although many will >> want a regular subscription. (you can't have both on the same list). >> Synchronization might be a stumbling block. Also, only one email >> address is registered (afaik), and many people (incl myself) use >> multiple. > > The backend logic I am assuming is: > - - for any message submitted to any ML, if the sender has *some* > email address associated with their account, let the message through; Okay, I'm with you sofar. > where *some email* can be determined in many different ways, for > instance: > - - in openSUSE user profile (feature: "use this text-field to add as > many email addresses as you want our MLs to whitelist for you). I see a bit of over-engineering? I have to log in, to a system I rarely have any reason to use, navigate unfamiliar territory and add my email address(es). Subscribing isn't much more difficult? > I notice en passant from what you just said that my proposal seems to > solve a 5th problem I overlooked in my previous message: > > Issue > 5) The current system (and mailman3!) enforce subscriptions as 1-1 > relations between email addresses and MLs, when in fact there is 0 > need for enforcing this if users have sets of addresses whitelisted > upstream in the work-flow. I don't see any issue, it is how mailing list managers work. >>> b) handle subscriptions to MLs closer to the literal meaning of >>> subscribing: i.e. open a receiver's channel, nothing less and >>> nothing more. >> >> I'm not sure I really understand what you mean here - the above >> sounds like what any mailing list manager does already ? i.e. you >> subscribe to a mailing list and you start receiving traffic. > > When you navigate a forum you usually don't need to subscribe to a > topic in order to be able to post to it. In that context "subscribing" > means "getting notified upon updates to the topic". My suggestion is > to move MLs closer to that meaning of "subscribing". Aha, I see - I never use any webfora, so I wasn't in the right context. Well, some of our lists are in fact open for non-subscribers, quite a few of them. opensuse-factory for instance. >>> (a) + (b) solve all four issues, don't open loopholes for spams, >>> and bring the ML worflow closer to the workflow of forums and >>> instant messaging apps, making use of the comfort zone of people >>> who already use these platforms. >> >> Just for the sake of argument - whose comfort zone is more important, >> the above or those of people who already use mailing lists? > > Care to explain in what way my proposal makes a negative impact on the > comfort zone of ML people? As I said - just for the sake of argument. I only meant to suggest you ought to be considering both sides. > Perhaps all this is a nice on paper but is horribly bad as far as > cost-efficiency is concerned, which may well be the case if mailman3 > does not easily bend to such fine-tunings. I have no way of knowing > that beforehand unless I discuss these things here :) Generally speaking, our (openSUSE's) mailing list manager has to be an appliance, not a bespoke development. If a feature is supported or can easily be done by normal means, we can do it. If a new feature means developing custom code, I am personally not in favour - development is easy, maintenance is the killer. -- Per Jessen, Zürich (15.2°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] GNOME.Asia Summit
by ddemaio 22 Oct '20

22 Oct '20

Hi all, openSUSE has long supported both GUADEC and GNOME.Asia Summits over the years. Please consider submitting a talk for the GNOME.Asia Summit at https://events.gnome.org/event/24/abstracts/ The deadline is Oct. 27 and the summit will take place November 24 - 26. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Documenting Leap Next and SLE differences
by Lubos Kocman 19 Oct '20

19 Oct '20

Hello openSUSE! I've mentioned on my yesterday's talk "Why should be companies be interested in Leap Next" that there is only a bunch of changes in between Leap Next and SLE 15. I spent today a bit of time on putting this together https://en.opensuse.org/Portal:Jump/Leap15.2.1:Forks I believe that's it for Jump (15.2.1) based on reviewing all the JIRA features that I created based on my diff/research effort earlier this year. Feature diff in openSUSE Leap 15.3 should be limited only to rejected SLE features, which are listed with "No." in the last column. Let me know if you think it's detailed enough. Thank you and Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

2 1

[opensuse-project] Confirming list of stakeholders for the openSUSE Leap 15.2.1 mini interlock on 19th October
by Lubos Kocman 18 Oct '20

18 Oct '20

Hello openSUSE! I'd like to confirm with a community on the list of stakeholders to sign off under the openSUSE Leap 15.2.1 go/nogo on a currently proposed release day of 4th November. The signoff (mini-interlock) should happen on Monday 19th Oct (intentionally after the openSUSE and LibreOffice conference). The exact time will be determined based on the geolocation of the audience. The signoff will happen on a jitsi meeting and progress-o-o and we will share the report on wiki and mailing lists. Currently proposed list of stakeholders is the regular crew of CtLG weekly updates (List can be found at last meeting minutes) and DimStar. https://etherpad.opensuse.org/p/ClosingTheLeapGap-meeting) What exactly are we signing off: agreed items listed at https://etherpad.opensuse.org/p/ClosingTheLeapGap-20200924-interlock-discus… https://en.opensuse.org/openSUSE:Roadmap in case of nogo we'd simply start to work on openSUSE Leap 15.3 release right away without an intermediate Leap 15.2.1 release. Please reach out to me if you believe you should be part of the sign- off itself. Thank you and Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer N��r��y隊Z)z{.��k�7��맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.��k�7��0��Ǩ�

3 4

[opensuse-project] Tumbleweed ISO checksums unsigned?
by Maximilian Trummer 18 Oct '20

18 Oct '20

Hey, I'm just wondering why Tumbleweed's ISO checksums are unsigned, while Leap's ISOs are signed. IIRC Tumbleweed's ISO checksums used to be signed too. https://software.opensuse.org/distributions/tumbleweed https://software.opensuse.org/distributions/leap

2 1

[opensuse-project] Refreshing the openSUSE learning experience
by Adrien Glauser 16 Oct '20

16 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, On behalf of our group of volunteers working with the doc team I wanted to share with you this annoucement. Cheers, Adrien - --- Join our team and help us improve the openSUSE learning experience ! --- For years openSUSE has meant more than one distribution. With the recent addition of Kubic and MicroOS to the Leap & Tumbleweed family, different package sets, release models and workflows can be difficult to keep tabs on. openSUSE's ecosystem is in full blossom, but even jungles sometimes need a clearing. This is why a group of volunteers has taken up the task of improving the learning experience for all users -- regardless of their experience and expertise. For new users, we want to make sure they can identify what best fits their needs, get the right tools and seamlessly take over from the post-installation screen. For experienced users, we want to provide them with detailed documentation that is easy to update, so that their experience and expertise can benefit others. We believe that from engineers to end-users, everyone deserves to have confidence not only in their OS, but in the way they're using it. A chain of trust like this is made of a user-friendly documentation where technical details are balanced with evidence-based good practices. It is with this goal in sight that we are calling the community for more volunteers. We are already set on course but the journey will be quicker -- and funnier -- with you. Any help is welcome, especially for: - - writing, editing and peer-reviewing: We would be delighted to benefit from more knowledgeable people to help us refresh, deepen and harmonize openSUSE's wikis and other documentation platforms - - video editing: Our video staff is looking for people interested in producing video contents and / or willing to script and record video tutorials in English - - testing: We need more people to help us test out already known work- flows and settings on new hardware, see if what used to be recommended still should be. So now you can't say you didn't know. Do reach out and come with us shape the future of the openSUSE learning experience! You can find us on the following platforms: - - Telegram group: https://t.me/opensuse_docs - - IRC bridge: https://matrix.to/#/#docs:opensuse.org - - Discord bridge: https://disboard.org/fr/server/366985425371398146 then Contributing > docs - - mailing list: https://lists.opensuse.org/opensuse-doc/ Last but not least: this is part of a collective effort so we are happy to relay to you that get.opensuse.org -- the future entry-point to the openSUSE web platforms -- is also looking for volunteers. Their goal is to deploy by November and they are still looking for committers to the repo at https://github.com/opensuse/get-o-o as well as translators. Translation tasks can be picked up at http://l10n.opensuse.org. Everyone interested is welcome to get in touch with Stasiek Michalski for details. Looking forward to meeting you! -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+Ec00ACgkQMy9Aieh+ wJyydQf+MhYnipalZG/R7xGGEwCkEGJG39DdO3oaNCM6hjH70xn3GSgNRM8eExvM qcshub2cf8VjCbr37kzKWBRcCMTu0KFNrs8JR758WJKdwVcy3/fm3cAv9kT4CM7d vI+/xJNPMnTR0qfyX4Dzbf/DFUSYd5VVvj3UiRstFWKaqs4kIkNnKa0CkSmmgVDL WnNcZFCKJwaSbPMaeSFAnnTReLosAsF5D4+m03/qVI95lwBp5p/8mIzHLjf3THRO QYBkfigDOIv4pF369DVH4ApdWN/3QLbWbcYP7J7S/k2gwigV59eusuBAQKQRCBKt m5Nq4UprevG3hpawcZ/xq9B6YFbgfg== =s5dF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

9 16

[opensuse-project] openSUSE + LibreOffice Help
by ddemaio 08 Oct '20

08 Oct '20

Hi all, We could use some help with introducing some of the speakers and helping people out throughout the openSUSE + LibreOffice Conference. We have some people who have signed up to help, but could use more. If you are interested, please reply and let me know. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Minutes of openSUSE Board meeting 2020-09-29
by Gerald Pfeifer 08 Oct '20

08 Oct '20

Present: Axel, Gerald, Marina, Stasiek, Vinz Excused: Simon Minutes: Gerald Marina got delayed so we restarted the meeting half an hour later, then also including her. == "openSUSE Intro" == * Gerald wonders whether we have / should have / can get a general presentation? * Use cases: events, new partners, new colleagues (think SUSE and Rancher) * AI anyone who has material, please share. * AI Gerald to send a question to marketing@ == Data protection officer for openSUSE == * Not strictly necessary as of today, though desirable; latest with a Foundation openSUSE will need a data protection officer. * Gerald is waiting for a brief role description. * Will then share that and a request for volunteer(s) with project@. == openSUSE + LibreOffice conference update == * Marina reported from prep call Sep 28th, where the team tested the platform, * Next step is testing accessibility. * AI everyone to log into the platform to become familiar. == Board presentation slot at openSUSE + LibreOffice conference == * Not too much input from project@ so far. * Probably a good idea to create a slide deck, go through that, and then take open questions. * Some thoughts ** Foundation ** Closing the Leap Gap: transparency (features, bugs,...) ** It would be great to get updates from the different teams of openSUSE. * AI Axel: prepare board presentation for oSLO, update statistics * AI Axel to invite heroes, marketing@, membership officials, election officials, localization teams to ** co-present, or ** share input or slides, or ** abstain this time around. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 2

[opensuse-project] metrics.o.o
by Axel Braun 07 Oct '20

07 Oct '20

Hi, does anyone of you know who maintains metrics.o.o? And the log file parsing for this site? Thanks Axel -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

3 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Project October 2020