August 2020 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] Too many open bugs (Leap 15.2 retro)
by Lubos Kocman 14 Aug '20

14 Aug '20

Hello openSUSE! one of the items raised on the retrospective* was a large number of open bugs, not just for openSUSE Leap 15.2 but for openSUSE Distribution in general. Tracked as https://progress.opensuse.org/issues/70000 . I already had a discussion with Oliver and Antonis on this topic on the Quality Assurance event that took place last Friday in Schweig. I'd like to share with you the idea of a regular "Bug smashing" meetings. (I'd call those "Bug triaging", those meeting will not get bug fixed but just allow to triage them properly, if I understand correctly) These https://meet.opensuse.org meetings would focus on outstanding bugs and respective "problematic components" (e.g. Other or Base system). We'd focus on one Bugzilla component at a time and would go through the results of pre-agreed queries. It could be multiple short (20 mins) sessions per week E.g. "Base system" Bug smashing etc. I don't mind low attendance but having an option to join and raise particular issue is very important to me. Keep in mind that the openSUSE Release Team is supposed to do this "overseeing" anyway. But I think we can be a bit more transparent about it. The idea is that I'd share screen go through the list of bugs, find an agreement on the next steps, and then the person sharing the screen (typically Release Team member) would write an update to the bug. This would then be followed by sending a notification to the bug owner or finding a new bug owner in case of no response. The public and virtual nature of sessions would enable people to join and raise attention to the bug that might be not getting enough attention. The goal should be on processing bugs in a way that we're able to achieve a decent response time and not cause a potential decrease in quality or close bugs that might potentially lead to a data loss. We're not doing this for the sake of better-looking statistics, but to have a more stable distribution. The pre-requisite for this is an agreed policy about how to tackle bugs properly. So we're helping instead of causing harm. The policy should provide answers to the following questions: What is expected to be tracked in Bugzilla and where to track other requests. E.g. the Documentation component is a bit controversial as it contains various types of requests. Criteria for keeping bugs open or closing them. (aka cleanup that helps). E.g. the definition of CLOSED/Insufficient data, do not close issues that lead to data loss. Agreement about setting the priority on issues, who is expected to do so, and what it means to the bug owner be it SUSE Employee or not. There are two ways how to see priority. How much of an issue is it for Given release (e.g. release can't be shipped with open P1 or P0) and how big of a priority is it to the bug owner. We need to find an agreement. Agreement about ownership of bugs. How does the screening team fit in and so on ... Agreement how to track 'seen' bugs P5 vs Confirmed etc. Agreement on who handles regular processing of bugs for what product(s) and what releases/versions. The last one is important as there seems to be a big difference in overseeing issues for the current release and releases in the maintenance phase. Who should oversee maintenance updates is still an open topic at least for SLE. I'd like to find an agreement with the openSUSE Maintenance team and join forces to be more efficient at pre- agreed bug processing. **Let's use https://etherpad.opensuse.org/p/ReleaseEngineering-bug-smashing-ideas-20200… for a brainstorm and revisit document on next the next Release Engineering meeting* on the Wednesday 19th Aug**. More info and meeting details are in the brainstorm document. [0] https://en.opensuse.org/Portal:15.2/Retrospective Best regards openSUSE Release team

1 2

Re: [opensuse-project] Election Campaign Page
by Richard Brown 13 Aug '20

13 Aug '20

On Tue, 2020-08-11 at 18:31 +0200, Pierre Böckmann wrote: > On Tuesday, 11 August 2020 16:09:01 CEST you wrote: > > Hi Pierre, Thanks for your responses, I have some followup > > questions. > > > > On Tue, 2020-08-11 at 15:47 +0200, Pierre Böckmann wrote: > > > > I'm dissapointed to find that your platform seems to be > > > > entirely > > > > based > > > > on effectively re-hashing the failed no-confidence vote. My > > > > views > > > > on > > > > that matter are not only well documented, but the vote failed, > > > > so > > > > it > > > > seems a peculiar decision to run primarily on the same topic. > > > > > > I am disappointed, too, that you pick a single point and pretend > > > this > > > would be > > > all I base my campaign on - though that is absolutely untrue. > > > > Skipping over responding to this train of thought in the name of > > compromise, collaboration, and wishing to avoid being baited into > > conflict. > > First accusing me of primarily running on the topic of a failed vote, > now > accusing me of trying to bait you into conflict... > Nothing of that's true or going to happen, I was only answering your > mail > without any bad intention and without any ulterior motives. Reading > those into > my response is not OK but at the same time it's ultimately telling > more about > your motives than mine. > Let's leave it at that. I find it very interesting you took my observations as 'accusations'. After all, I feel my observations are easily justifiable. In your platform, the "Why you shoud vote for me.." section ONLY states the No-Confidence Vote. There is no mention of the Foundation in that section at all. The "Current Issues" section dedicates a large paragraph to the No- Confidence Vote. That paragraph calls the work of your potential teammates 'unncessary' and 'disgraceful'. In the same section you only provide a single sentance to the foundation. There are no details as how you'd support the topic or what you'd expect the foundation to look like. And of your goals 3 of them are clearly related to your no-confidence motion, 1 is related to the foundation, and 1 is somewhat more generic. Considering the above, I think it's very easy for any reasnoble reader to feel that your primary motivation for running is to re-hash the no- confidence vote and there is a significant lack of substance beyond that. If the perception I got from that is incorrect, fine, then my first reply was a clear opportunity to clear up that misperception on my part. I find it exceptionally telling that, once realising that we had a difference in opinion regarding the content of your platform, that the discussion has evolved the way it has. I would have hoped a Board member would have taken the opportunity to look inward, and ask themselves how a voting Member like myself got such an impression. You have instead taken the route you have, even going so far to use rhetorical deflections to suggest that my words are more telling about my motives than yours. I think it's important for you to realise, my motives don't matter. I'm not the one running for the Board, I'm just a voter like several hundred others who's support you will need. You are the one running for the Board, and I suspect this thread has done a good job of showing what sort of Board member you could be. I'd like to thank you for all the responses in this thread. I have found it very insightful and helpful in deciding where my vote will go. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

4 5

[opensuse-project] Election campaign page
by Ish Sookun 11 Aug '20

11 Aug '20

Dear all, Pierre has set up his election campaign page at https://en.opensuse.org/ openSUSE:Ad_hoc_Board_election_2020_platform_crowbyte. Feel free to read and ask him questions. Let's keep the election debates on! Regards, Ish Sookun -- 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] Migrating mailing lists
by Stasiek Michalski 07 Aug '20

07 Aug '20

Hi, We are currently planning out the migration from mlmmj to mailman 3. We have been discussing moving lists over from opensuse-$list(a)opensuse.org to $list(a)lists.opensuse.org (and potentially allowing subprojects to use their own domains), for both collision and aesthetic reasons. We would like to hear your input. Thanks in advance, LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

11 18

[opensuse-project] Board Call Meeting Minutes 2020-08-04 - 0800 CEST
by Axel Braun 07 Aug '20

07 Aug '20

Meeting Minutes 2020-08-04 - 0800 CEST Attendees: Gerald, Vinz, Marina, Axel Absent: Simon Minutes taken: Axel ** Draft of foundation presentation ** Postponed as not every board member had the chance to look into the presentation. We need to broaden the group of people working on foundation. Idea: Restart the process on https://en.opensuse.org/Portal:Foundation New topic 'Foundation Restart 2020', cleaning up of portal and move old stuff to Portal:Archive (Vinz) Announce on project mailing list. Dependent on traffic, os-foundation(a)o.o may be reopened ** Pending Meeting Minutes ** Reminder on two missing meeting minutes ** Board Talk on openSUSE Conference ** Currently we have 114 registered attendees, 84 talks submitted and ~44 hours of presentations for oSLo Board will submit a 1h workshop for discussion with the community (Marina). Add your topics you want to discuss here: https://en.opensuse.org/ openSUSE_talk:Board_meetings#Topics_for_the_online_meeting_at_the_openSUSE. 2BLibreOffice_.28oSLO.29_conference Board will try a face2face meeting after election. Problem is that Simon cant leave Australia for at least next 6-12 month ** 2FactorAuthentification authentification ** 2FA on github repos for admins should be mandatory as requested by github organisation. AI Simon to send reminder to people not yet using 2FA Next board call: 18.08.2020 0800 CEST -- 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] Sharing results of the openSUSE Leap 15.2 release retrospective survey and suggested action items
by Lubos Kocman 07 Aug '20

07 Aug '20

Hello team, first let me thank you to all who participated in the survey, but also to all who helped me to process the results and suggest action items. Big thanks to Lars and Heroes for comming up with the idea to use LimeSurvey and making this happen. It was countless hours of data processing but it was worth it. Data with suggested set of action items from our review rounds: https://en.opensuse.org/Portal:15.2/Retrospective Raw data can be found here: (Please email me if your login can't access the data) https://progress.opensuse.org/projects/leap152retro/documents Next steps: I'll slowly start to process action items and create either: * Thank you emails (KUDOS) * bugs in bugzilla.opensuse.org * Feature requests in jira.suse.com * Issues in https://progress.opensuse.org/projects/leap152retro * Issues in https://github.com/openSUSE/openSUSE-release-process for changing the release process instructions I'll also re-raise feedback and action items with responsible teams Thank you very much once again Lubos

1 0

[opensuse-project] openQA for s390x
by azouhr 05 Aug '20

05 Aug '20

Hi, currently, there is no openQA for s390x. I have heard that this is due to some storage issues, but that is only second hand rumours, no direct communication. For me this is kind of unfortunate, because I do care about openSUSE:Factory:zSystems, and without openQA, there is no release nor any reasonable information about the state of the distribution. During my time at SUSE, I did the Mainframe part to get openQA running, later on, when openQA had some network requirements changed, I even sponsored a Server to make that running again. However, even though I addressed this multiple times, I am not able to get information about the state, not to say get it rebuilt. Is there anyone who knows what I can do to bring this issue forward? To me, this is kind of frustrating at the moment and I think this needs broader attention. So, if you know what I could do, please tell me ... Berthold azouhr(a)opensuse.org -- 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] openSUSE Leap 15.2 retro review of results on Thursday
by Lubos Kocman 04 Aug '20

04 Aug '20

Hello openSUSE! Thanks to everyone who participated in our openSUSE Leap 15.2 release retrospective that took place on survey.opensuse.org. Also big thanks to Lars for making it happen! The survey was fully anonymous and questions were: What went well and What didn't go too well. We did receive about 200 responses*, 623 records in total, but a lot of them were blank, perhaps expired sessions. There is a lot of feedback for both questions some of them are really heartwarming. Which is also why I'd like to go through results with you. I'll do initial categorization and deduplication of results today/tomorrow and will place it on a single etherpad page which will be easier to consume. I'd like to do two rounds of reviews where we'd go together over results and turn them into action items (progress-o-o issues*, bugs, Thank you emails to maintainers, ...). We'll revisit what went well on both meetings, otherwise, we would simply continue in the afternoon review where we ended in the morning as I expect there will be a lot of action items on the "what didn't go too well" side. Please expect no blame talk or fingerpointing (unless it's on me :) ) but rather a constructive discussion about how to make the next release even better. The virtual review meetings will take place here: https://meet.opensuse.org/ReleaseEngineeringMeeting in following time slots: 8:00 - 10:00 CEST Thursday 6th August 2020 17:00 - 19:00 CEST Thursday 6th August 2020 [0] Raw export, preferably wait for my post-processing https://progress.opensuse.org/projects/leap152retro/documents?sort_by=title [1] Project for retro issues https://progress.opensuse.org/projects/leap152retro/issues Thank you 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

1 0

[opensuse-project] [reminder] openSUSE and LibreOffice Conference
by Marina Latini 04 Aug '20

04 Aug '20

Dear Community, as Douglas already reminded[0], the extended deadline for submitting your proposal for the openSUSE+LibreOffice (oSLO) conference will expire today. If you want to share your achievements, your project or simply share something with both the openSUSE and LibreOffice communities hurry up and don't forget to send your proposal! The cross-communities organization team will meet again for the usual bi-weekly call today, at 19.00 CEST. Join us on: https://meet.jit.si/oSLibCon [0] https://news.opensuse.org/2020/07/22/opensuse-libreoffice-virtual-conferenc… Happy hacking and have a lot of fun! Marina -- Marina Latini openSUSE Board: deneb_alpha www.documentfoundation.org www.libreitalia.org -- 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] Reflection on the last weeks - Lessons learned from the board
by Simon Lees 03 Aug '20

03 Aug '20

Dear Community, many of you have witnessed discussions and allegations of different kinds on this mailing list, some very offensive and disrespectful towards the community and the values that bond it together. In order to not add further discussions, to not nurture the chaos already present, and aiming to have a fair and unbiased vote on the "motion of no confidence", as a board we agreed to not comment on individual emails during the period of the poll. Now we feel that we need to disclose some background and provide clarification over how this all started. Sarah Julia Kriesch, former member of this board, has repeatedly moved heavy accusations against some members of this community during her first term on the board 2017-2019. In each case these accusations were unfounded after in-depth considerations. The measure taken after the first incident was a formal warning in alignment with the openSUSE Community Guiding Principles. [1] The second time lead to a vote on her removal from the board, where she maintained her seat after a narrow vote. Unfortunately Sarah's behavior has continued and the board received complaints, despite repeated efforts by several members of the community to carefully explain and council Sarah on her behavior and its implications on others. To handle the situation with minimal impact on the parties involved a moderate solution was sought: Sarah was offered the opportunity to step down instead of being removed and the complete background being disclosed. Even though "mutual confidentiality" was agreed between all parties, Sarah decided to violate this agreement that same evening and also started making false accusations about her stepping down. All this, together with some base speculation, then led to the motion of no confidence and what followed. We would like to assure you that with every action the board has undertaken, the well-being of all involved parties has been a main priority. As a community, and on the board, we spent a huge amount of time on this topic in the last half year and we have learned some lessons. Two of these are to 1) defer handling a complaint against a community member to the following board meeting (not on the same day), and 2) in case of extremely severe decisions taken, even if undelightful for the person affected, provide transparency to the community about the actions taken, keeping confidentiality as much as possible but not at all cost. [1] https://en.opensuse.org/openSUSE:Guiding_principles

8 15