Re: PAUSE 504 errors when trying to add a co-maintainer

--0000000000006e11df06583ced6b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Neil,

Thanks for the reply. If I understand what you're saying, the "alternative
interface for adding co-maint per module/package" is what I tried for the
last release. I thought I granted per-module co-maintainership to all
modules in the previous release and the non-version-specific modules,
similar to how you handled it for Dora, but that didn't prevent the
permission problems Mattia ran into. Do you have any idea why that didn't
work this time?

For your alternative solution, are you suggesting we include only the
latest Google Ads API version in a given dist version, e.g.
Google::Ads::GoogleAds::V25::* in a separate dist version from previous
Google Ads API versions? Or are you proposing putting them under a separate
distribution altogether (e.g., having the package be
Google::Ads::GoogleAds::V25 instead of Google::Ads::GoogleAds)? If I
understand correctly, either option would pose its own problems and
potentially break users' existing integrations or workflows. Let me know if
I've misunderstood.

If we can resolve the per-module co-maintainership issue, I think that
would be the preferred and sufficiently future-proof solution. If not, we
can look deeper into shared credentials or potentially changing how we
distribute new versions.

Many thanks,


Laura Chevalier

Developer Relations Engineer

[email protected]



On Tue, Aug 4, 2026 at 12:02=E2=80=AFPM Neil Bowers <[email protected]> wrote=
:

> Hi Mattia,
>
> I think what you're saying is that you want multiple people to have
> co-maint on all of the packages in the distribution(s).
>
> But right now you can't use the interface for "give co-maint on the
> distribution", because it times out before it can complete (because of ho=
w
> many packages there are in the distribution).
>
> You can use the alternative interface for adding co-maint per
> module/package. I don't think that suffers from the timeout problem, but
> it's a tedious approach for you, given how many packages there are.
>
> Another approach: if I remember rightly, the package explosion is because
> version numbers are embedded in package names, and you want backwards
> compatibility. Could you split off packages to support older versions of
> the API into a separate distribution, or even multiple distributions?
>
> Cheers,
> Neil
>
>

--0000000000006e11df06583ced6b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hey Neil,</div><div><br></div><div>Thanks for the rep=
ly. If I understand what you&#39;re saying, the &quot;alternative interface=
 for adding co-maint per module/package&quot; is what I tried for the last =
release. I thought I granted per-module co-maintainership to all modules=C2=
=A0in the previous release=C2=A0and the non-version-specific modules, simil=
ar to how you handled it for Dora, but that didn&#39;t prevent the permissi=
on problems Mattia ran into. Do you have any idea why that didn&#39;t work =
this time?</div><div><br></div><div>For your alternative solution, are you =
suggesting we include only the latest Google Ads API version in a given dis=
t version, e.g. <font face=3D"monospace">Google::Ads::GoogleAds::V25::*</fo=
nt><font face=3D"arial, sans-serif">=C2=A0in a separate dist version from p=
revious Google Ads API versions</font>? Or are you proposing putting them u=
nder a separate distribution altogether=C2=A0(e.g., having the package be=
=C2=A0<span style=3D"font-family:monospace">Google::Ads::GoogleAds::V25</sp=
an><font face=3D"arial, sans-serif">=C2=A0instead of=C2=A0</font><span styl=
e=3D"font-family:monospace">Google::Ads::GoogleAds</span><font face=3D"aria=
l, sans-serif">)</font>? If I understand correctly, either option would pos=
e its own problems and potentially break users&#39; existing integrations o=
r workflows. Let me know if I&#39;ve misunderstood.</div><div><br></div><di=
v>If we can resolve the per-module co-maintainership issue, I think that wo=
uld be the preferred and sufficiently future-proof solution. If not, we can=
 look deeper into shared credentials or potentially changing how we distrib=
ute new versions.</div><div><br></div><div>Many thanks,</div><div><div dir=
=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div =
dir=3D"ltr"><span><p dir=3D"ltr" style=3D"line-height:1.656;background-colo=
r:#ffffff;margin-top:0pt;margin-bottom:0pt"></p><p dir=3D"ltr" style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span></span></p><div dir=
=3D"ltr" style=3D"margin-left:0pt" align=3D"left"><span><p dir=3D"ltr" styl=
e=3D"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div dir=3D"lt=
r" style=3D"margin-left:0pt" align=3D"left"><span><p dir=3D"ltr" style=3D"l=
ine-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div dir=3D"ltr" sty=
le=3D"margin-left:0pt" align=3D"left"></div><p dir=3D"ltr" style=3D"line-he=
ight:1.656;background-color:#ffffff;margin-top:0pt;margin-bottom:0pt"></p><=
div dir=3D"ltr" style=3D"margin-left:0pt" align=3D"left"></div><div dir=3D"=
ltr" style=3D"margin-left:0pt" align=3D"left"><span><p dir=3D"ltr" style=3D=
"line-height:1.656;margin-top:0pt;margin-bottom:0pt"></p><div dir=3D"ltr" s=
tyle=3D"margin-left:0pt" align=3D"left"><table style=3D"border:none;border-=
collapse:collapse"><colgroup><col width=3D"167"><col width=3D"180"></colgro=
up><tbody><tr style=3D"height:0pt"><td style=3D"border-left:solid #ffffff 0=
.75pt;border-right:solid #ffffff 0.75pt;border-bottom:solid #ffffff 0.75pt;=
border-top:solid #ffffff 0.75pt;vertical-align:top;padding:5pt 5pt 5pt 5pt;=
overflow:hidden"><img src=3D"https://lh3.googleusercontent.com/pw/AP1GczO27=
AMjXjdjiz3YHI9EYFM9URDOE8pckjh0ff_RRYs2kZAkFFtumuhkR3q1McW0xRbPlUWFFeV4SHAN=
glfLFTe-svso1aZsrlKs6XNKBFVDPJ3m8GmFv32lcYSOT3VQIhe0AmkU0eUDgUWprsjAzEtu=3D=
w468-h162-s-no-gm?authuser=3D0" width=3D"200" height=3D"69"><br></td><td st=
yle=3D"border-left:solid #ffffff 0.75pt;border-right:solid #ffffff 0.75pt;b=
order-bottom:solid #ffffff 0.75pt;border-top:solid #ffffff 0.75pt;vertical-=
align:top;padding:5pt 5pt 5pt 5pt;overflow:hidden"><p dir=3D"ltr" style=3D"=
line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size=
:11pt;font-family:&quot;Google Sans&quot;,sans-serif;color:rgb(103,78,167);=
background-color:transparent;font-weight:700;vertical-align:baseline">Laura=
 Chevalier</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><span style=3D"font-size:8pt;font-family:&quot;Google =
Sans&quot;,sans-serif;color:rgb(17,85,204);background-color:transparent;ver=
tical-align:baseline">Developer Relations Engineer</span></p><p dir=3D"ltr"=
 style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D=
"font-size:8pt;font-family:&quot;Google Sans&quot;,sans-serif;color:rgb(60,=
120,216);background-color:transparent;vertical-align:baseline"><a href=3D"m=
ailto:[email protected]" target=3D"_blank">[email protected]=
m</a></span></p></td></tr></tbody></table></div><br></span></div></span></d=
iv></span></div></span></div></div></div><br></div><br><div class=3D"gmail_=
quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, =
Aug 4, 2026 at 12:02=E2=80=AFPM Neil Bowers &lt;<a href=3D"mailto:neilb@nei=
lb.org">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">



<div>
<div name=3D"messageBodySection">
<div>Hi Mattia,</div>
<div>=C2=A0</div>
<div>I think what you&#39;re saying is that you want multiple people to hav=
e co-maint on all of the packages in the distribution(s).</div>
<div>=C2=A0</div>
<div>But right now you can&#39;t use the interface for &quot;give co-maint =
on the distribution&quot;, because it times out before it can complete (bec=
ause of how many packages there are in the distribution).</div>
<div>=C2=A0</div>
<div>You can use the alternative interface for adding co-maint per module/p=
ackage. I don&#39;t think that suffers from the timeout problem, but it&#39=
;s a tedious approach for you, given how many packages there are.</div>
<div>=C2=A0</div>
<div>Another approach: if I remember rightly, the package explosion is beca=
use version numbers are embedded in package names, and you want backwards c=
ompatibility. Could you split off packages to support older versions of the=
 API into a separate distribution, or even multiple distributions?</div>
<div>=C2=A0</div>
<div>Cheers,</div>
<div>Neil</div>
<div>=C2=A0</div>
</div>
</div>

</blockquote></div>

--0000000000006e11df06583ced6b--