[Slackbuilds-users] nginx maintenance

[B. Watson]

On Sun, 1 Sep 2024, Roberto Puzzanghera via SlackBuilds-users wrote:

>> I would estimate that about 25% of our repo is effectively
>> unmaintained.  We really need folks to step up and take over anything
>> they need or are interested in.
>
> I would be happy to be a new entry. But something is not clear to me about 
> the steps to follow when I would like to take over a certain package.
> Let's suppose that I contacted the maintainer and got no responce from 
> her/him. How can I be officially declared the new maintainer of that package?

Announce it on the list, and give some details ("I tried to contact
the maintainer and (the email bounceed | I got no response after N
days | I was given permission to take over")...

> Is it sufficient to give an advice on this list?

Almost. The next step is to actually submit an update, even if all you
change is MAINTAINER (your name) and EMAIL, in the .info file.

Quite a few times over the years, someone has announced they were
taking over a build, and then never got around to updating it with
their information, and it just got forgotten about.

Maybe I should write a new section for the FAQ. There doesn't seem to
be anything there about taking over a build.