On 4/27/22 08:39, Aaron Puchert wrote:

Am 26.04.22 um 19:20 schrieb Axel Braun:

...

Contact the maintaners of server:dns directly for an override.

Exactly, you can also add a comment @mentioning them, just like the staging-bot does it. The bot will only ping package maintainers if they are explicitly specified, but project maintainers can also accept this.

You can also try and directly email them, some of us get very large numbers of comments and can often miss them. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

Hi, Am Mittwoch, 27. April 2022, 17:00:52 CEST schrieb toganm@dinamizm.com:

So the question how do we solve this not for now but for the future as well ?

I think we need different steps: First we need to clean up OBS from inactive users or invalid mail addresses. I seem to remember that there was an initiative planned, but dont know about the status. Second it would help to have an overview about the SR per project - ideally with the option to sort by different criteria, e.g. age. Some kind of dashboard. Third - someone has to process overdue SR, if the package maintainer does not do, for whatever reason. The natural choice would be the project maintainers. Second choice could be some kind of taskforce that reviews open SR on a regular basis. This would require additional communication with the package/ project owners, just to make sure the SR is in line with standards and (local) guidelines (from my experience, it can make a difference to where you submit a package - in one case one discusses that the description has to have a line break after 80 char, in the other case it is much more relaxed...). My 2c Axel

Am Mittwoch, 27. April 2022, 22:52:52 CEST schrieb Jan Engelhardt:

tOn Wednesday 2022-04-27 21:58, Axel Braun wrote:

...

Second it would help to have an overview about the SR per project - ideally with the option to sort by different criteria, e.g. age. Some kind of dashboard.

already exists. e.g. o:F at https://build.opensuse.org/project/requests/openSUSE:Factory

Good point, so step 3 can immediately be taken... Cheers Axel

On 4/28/22 00:30, toganm@dinamizm.com wrote:

...

...

...

...

...

"Simon" == Simon Lees writes:

Simon> On 4/27/22 08:39, Aaron Puchert wrote:

...

...

Am 26.04.22 um 19:20 schrieb Axel Braun:

...

Contact the maintaners of server:dns directly for an override.

Exactly, you can also add a comment @mentioning them, just like the staging-bot does it. The bot will only ping package maintainers if they are explicitly specified, but project maintainers can also accept this.

Simon> You can also try and directly email them, some of us get very large Simon> numbers of comments and can often miss them.

Which he did with no response, so that ship has sailed I am afraid.

Sorry I meant email the project maintainers, if there is a submit request that isn't being acted on its there responsibility too look at and approve it. They also have the power to appoint a new maintainer if someone volunteers. If you don't get a response from project maintainers then email here and we will appoint someone else to help. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

On Thu, Apr 28, Togan Muftuoglu wrote:

Out of curiosity how is it done in the corporate SuSE and if done how can we apply/adapt the approach to openSUSE ?

It's "SUSE" and not "SuSE" since a really very, very long time. SUSE pays developers to do the work, while openSUSE depends on contributors and their spare time. So you cannot apply or adapt the approach. Except somebody donates so much money to the openSUSE project, that they can hire developers, too. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)

On 4/28/22 22:08, Togan Muftuoglu wrote:

...

...

...

...

...

"Simon" == Simon Lees writes:

Simon> Sorry I meant email the project maintainers, if there is a submit Simon> request that isn't being acted on its there responsibility too look at Simon> and approve it. They also have the power to appoint a new maintainer if Simon> someone volunteers.

Simon> If you don't get a response from project maintainers then email here Simon> and we will appoint someone else to help.

What you are suggesting is a bandaid option, which is pointing to someone else or another group/project.

Well in an ideal world people would realize they no longer have time and would put there packages up for adoption that happens sometimes, often it doesn't. Regularly we don't realise until a package no longer builds. Project maintainers are designed to be the fallback for cases where package maintainers are away and to help when package maintainers disappear. I'm not really sure what we can do better here but if you have suggestions.

I suggest we need to find a better, sustainable approach which will help everyone from enduser to project maintainer to release team.

Out of curiosity how is it done in the corporate SuSE and if done how can we apply/adapt the approach to openSUSE ?

Sometimes well, sometimes badly but not really in a way we can adapt for openSUSE. For example if I was to leave the company my manager has a list of my packages and would get other people in the team to look after them until they hire a replacement, often in this period we will ping project maintainers with specific requests if they aren't being picked up by anyone then eventually a replacement person will be found and they will be assigned my packages (or they may swap some with others in the team). We also has a script that finds all SLE packages without a maintainer that usually have a lighter workload (not many security updates etc) and they rotate between a group of different people. This works for SUSE because we pay maintainers and can tell them that its there job to look after this group of packages for a week. That doesn't work for openSUSE where everyone is a volunteer and we can't really tell them to work on things. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

Axel Braun wrote:

Contact the maintaners of server:dns directly for an override.

That was something I already thought of, wrote to two of them last month without response. But is not only about that package, but for a general discussion as there are several packages I noticed (in Factory not random 3rd party packages) not updated / fixed for quite a time with pending requests. As Togan wrote there probably should be a strategy for handling requests without response and even bugs without response. Regards, Ferdinand