[pkg-go] Fwd: Updating the pkg-go Team Maintenance policy

[Michael Stapelberg]

Dmitry, thanks for articulating your concerns. AFAICT, you are mostly
concerned about uploads of new versions.

Would you agree to a no-communication-necessary policy when it only covers
bugfixes/other package maintenance, for example mass-changes such as
getting rid of “Depends: golang-go” on all library packages?

On Tue, Jan 19, 2016 at 9:18 AM, Dmitry Smirnov <onlyjob at debian.org> wrote:

> On Tue, 19 Jan 2016 08:51:22 AM Michael Stapelberg wrote:
> > Dmitry, can you please outline what it is that you dislike about the
> > suggestion?
>
> Too much freedom to upload without notifying those who are responsible for
> package. Lack of notion that Team upload is a rough equivalent to NMU hence
> notification is a must as well as delay (through DELAYED queue or other
> means).
> Alexandre wants to ensure that everyone can upload everything without
> talking
> but team maintenance should be more about communication.
> For example one might want to upload new upstream release of a package
> without telling Uploaders. But new release may not be uploaded for reason
> like when Uploaders (who presumably follow upstream development) are aware
> of
> regression or disruptive change in new release and prefer to wait for
> update.
> In number of cases upload can be held by known upstream bugs etc. Therefore
> one who wants to upload must communicate and not just do as (s)he pleased
> without even sending an email to those who migh be aware of specifics and
> situation.
>
> We are all here to help each other but let's not forget about importance of
> communication.
>
> --
> Cheers,
>  Dmitry Smirnov.
>
> ---
>
> Every decent man is ashamed of the government he lives under.
>         -- H. L. Mencken
>



-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20160119/fa6a2bef/attachment.html>