Re: #1009709 - RFS: nginx/1.18.0-2 [RC] -- small, powerful, scalable web/proxy server
On Thu, 2022-04-14 at 20:26 -0400, Thomas Ward wrote:
> I sent such requests literally when they gave me access, and it seems
> there may only be one or two individuals driving the package - of which
> it's impossibly hard to get one of them to even respond. Last response
> I had from Ondrej on the uploaders and team was "Join the maintainers
> team" on Salsa, which I did and they granted me access -
> https://salsa.debian.org/nginx-team/nginx has the recent work which has
> made the team "no longer inactive after a three week break". If this is
> not enough to point at me having maintainer access to the VCS for
> releasing the packages, then maybe Debian should do some research before
> outright rejecting.
I'd like to point out in Debian's convention Salsa permission is not
equivalent to any factual upload permission. Even if you are granted
with Owner access on Salsa, it's still a separated thing when talking
about upload permission. There are massive amount of examples of
salsa contributors without factual uploading permission. There are
historical reasons behind this, which seems quite different from
Ubuntu's convention.
Being unable to get a response from original maintainer is always
a pain to contribute for this community. You may want to look up
the "Intent To Salvage" process given your intent to maintain it
for long term. Whether people can get response varies across in
different teams at different times.
I understand such frustration as I experienced exactly the same thing
when I was not a DD.
> I'm happy to wait for one of their people to give me dak access or
> sponsor the upload, however keep in mind that after 3 weeks with no
> activity AND a merge request that took two weeks to get that would fix
> the FTBFS that broke NGINX in Testing to begin with, we're staring at a
> "Package is not fit for testing" problem currently that is nearly a
> month old and hasn't been fixed yet. (However, given that I've been
> making the commits on the Salsa repo that the packaging directly comes
> from, I'm not sure if you mean something other than the NGINX Team on
> Salsa when you refer to "maintainers" - I have 'Maintainer' access on
> the Salsa repo itself that the packaging comes from)
>
Unfortunately, I have to tell you the truth that Debian community is
a group of unpaid volunteers. And you may have to lower your
expectation on the other developer's response within this community.
Really, triggering autorm due to FTBFS happens all the time.
Bugs left for a month unfixed happens all the time.
When the package maintainers are going to do something, they will
continue from your work on salsa and include them in the next
upload.
You may have been confused by Salsa "Maintainer access" and "Debian
Maintainer". They are truely different thing and irrelevant.
Even if someone has "Owner access" on Salsa, it does not mean
this contributor should have "Debian Developer" or "Debian Maintainer"
permission for ftp-master upload.
Reply to: