October 2020 - 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

[opensuse-project] Can one manually become a "Member Emeritus"
by Stefan Seyfried 09 Aug '21

09 Aug '21

Hi all, after reading https://en.opensuse.org/openSUSE:Members, I understand that I can cancel my membership status with immediate effect and forever. To become a "Member Emeritus", with a "way back" into the community in case things might turn good again, I have to wait for the status request and just not respond to it. But the last such request was almost 3 years ago. IIUC I need to stop all actions on the mailing lists (might be a good idea ;-)) and packaging (not so good) for the bot to pick me up. So is there a manual procedure to follow to become "Member Emeritus"? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 4

Re: [opensuse-project] huge amount of SPAM on opensuse-connect
by christian.imhorst＠posteo.de 02 Jun '21

02 Jun '21

Hi, Am Do., 21. Feb. 2019 um 15:32 Uhr schrieb Lars Vogdt <Lars.Vogdt(a)suse.com>: As such, maintaining 447 [1] openSUSE members should not depend on a single tool. Especially not if the used tool has open, well known security issues since years[2]. 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 system! 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 for example? 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 as possible. Regards Christian Imhorst -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

23 70

[opensuse-project] Please close my membership
by James Mason 28 Nov '20

28 Nov '20

Hello, It is with despair that I ask that you cancel my membership in openSUSE. The constant bickering on the mailing lists is by far outweighing any constructive growth/change in the project, and in light of everything else going on in the world, I just don't have the headspace for all that negative, unproductive noise. I'm cc'ing the project overall; please let this serve as a lesson that if one thinks they can bicker their way to the end result they want, they may find they arrive there alone. James Mason Technical Architect, Public Cloud SUSE

23 46

[opensuse-project] DevConf CfP Deadline
by ddemaio 02 Nov '20

02 Nov '20

Hi all, I want to bring your attention to DevConf.CZ - https://www.devconf.info/cz/. Typically this conference is the week before our beloved FOSDEM. This year it will be happening in mid-February. The call for papers is open until Nov. 1. This is a great opportunity to get your tech talk in front of 1,000+ developers. Each year, this free conference has this amount of attendees and people always ask me about having more SUSE and openSUSE project talks at this event. Seeing that this year's event is virtual, it should be much easier than traveling to Brno. Please consider submitting a talk. I'm sure the organizers would appreciate it. v/r Doug -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] download.o.o down?
by Mathias Homann 31 Oct '20

31 Oct '20

Hey all, is download.o.o down? cheers, MH -- Mathias Homann Mathias.Homann(a)openSUSE.org Jabber (XMPP): lemmy(a)tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102 -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 7

[opensuse-project] openSUSE Community To Have Kickoff Session for Leap 15.3
by ddemaio 28 Oct '20

28 Oct '20

Hi all, The openSUSE <https://www.opensuse.org/> community is inviting package maintainers, contributors, open source developers and Leap 15.3 stakeholders to join the openSUSE community for a kickoff of Leap <https://en.opensuse.org/Portal:Leap> 15.3. The kickoff session starts Nov. 4 at 16:30 UTC on https://meet.opensuse.org/LeapKickoff. You can find more info at https://news.opensuse.org/2020/10/28/opensuse-community-to-kickoff-session-… 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] An update on the Jump and Leap 15.3
by Lubos Kocman 27 Oct '20

27 Oct '20

Hello openSUSE! The last update that you've received from me was the (Conditional) No Go for the Leap 15.2.1. https://en.opensuse.org/Portal:Jump/Leap15.2.1:GoNogo There is no longer ar dedicated Closing the Leap Gap/Jump weekly meeting since the Go/NoGo meeting. The only related weekly meeting getting the Jump concept updates would be the openSUSE Release Team meeting that happens every Wednesday at 10:30 CEST. Let me share with you the next steps with Closing The Leap Gap and openSUSE Leap and what I've agreed upon today with openSUSE Board members. I'm going to create a request(s) to set up openSUSE Leap 15.3 based on the setup we've come up with the Jump concept. I believe we have no issues with meeting Alpha/Beta criteria for Leap 15.3, unlike criteria used for Go/noGo for 15.2.1. We should have an initial setup done by the 4th of November to meet the roadmap. As far as 15.2.1 goes, we're making minor progress on both the Migration and Maintenance setup front for 15.2.1, but I'm not sure if that will be enough. Meanwhile, I'll keep monitoring the situation around Leap 15.2.1 in case that something would change this week and will come up with the final statement for the potential Leap 15.2.1 release on the 2nd of November. I want to close one chapter so the openSUSE Release team can focus on the upcoming Leap release. We've already delayed openSUSE Leap 15.3 enough. **With that said, I would like to announce that there will be a small openSUSE Leap 15.3 kickoff event on the 4th of November. ** The form would be a virtual coffee or beer (depends on your TZ) && friendly informative talk. I'll talk to openSUSE Marketing about what's the best format to handle such an event. Please expect an announcement with details later this week. -- Lubos Kocman, Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg - Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0

[opensuse-project] Does the elephant in the room of openSUSE mailing lists exist?
by Adrien Glauser 26 Oct '20

26 Oct '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, As far as I understand there is no centralized tool allowing users to manage their mailing list subscriptions. Each ML has to be individually micro-managed. Also MLs seem to assume that only messages from subscribed users are allowed through (even though there is a nice message that informs you if you are not yet subscribed that the message you just sent is "pending approval", in my recent experience none of the messages I sent this way actually went though). So the business logic here entails that sending message to several MLs pushes you under the following bus: Either your messages will land on the "waiting for approval" purgatory and probably won't ever go through Or you have to manually subscribe to every single ML you want to write to keep track of all of them (to avoid sending a message to the one ML you forgot you weren't subscribed to); and you have to add filters to your email client (as opposed to a centralized web manager) to avoid drowning in a tsunami of emails; and you have to be empirical about this, making sure your filters don't get false positives or negatives. Not a cool dilemma. I mean ML clearly have their purpose but if I didn't miss anything obvious, this does not help with making the ML for attractive to people born after 1995. Am I missing the obvious? Also what's the margin for feasible improvements? How strong do we need to push to shake up status quo? Best, Adrien -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEU4ol/0bSQTwqpAkNMy9Aieh+wJwFAl+NkY4ACgkQMy9Aieh+ wJzsBQf9GR19TZXld33zFfQzpSZGjs8QXGsWIVddQcaqAuJd1M0Wl+fFO2uYMTfI iVdOXpxSG3iGpOH0EtW4e6hdppW3GopffUSM2tJKfvgSXM5NOgtpZA/rBUl7lneb XOwWWD4bWn3w2pz1ucgAcc7NKv/ivkRoLnNqoH1zf6XUzLkDJfuvRYAKJf5A2NL3 Lt7/QnLoqYgsB+EOTdCwkN1utiogW1iVGgGs4SJsNSe96f9Dv9G1FWcT/Dw8IKho zvObm4J2hHOY3oYGxzjaAup3lons8Rjol0xE7XYkOV1T+9CZn/8v6/97Iv/F0HhK 3bwC3jaEq0341VYfqDC8y9+ZAusPGQ== =gkr0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

11 32

[opensuse-project] [DRAFT]NAPA Cleveland Camera Quote
by Malcolm 24 Oct '20

24 Oct '20

Hi Patrick Here is the first draft of the quote. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20201022 | GNOME Shell 3.36.7 | 5.8.15-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 6:59, 1 user, load average: 0.63, 0.69, 0.58

1 1

[opensuse-project] Minutes of openSUSE Board meeting 2020-10-13
by Gerald Pfeifer 22 Oct '20

22 Oct '20

Present: Axel, Gerald, Marina, Simon, Stasiek Excused: Vinz == Preparation for Board slot at openSUSE+LibreOffice conference == We discussed how to build out the current draft created by Axel with feedback by others and various practicalities. No further topics. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

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