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

[Michael Stapelberg]

tincho, I think you are in agreement with the policy change that aviau
suggested. Have you read the patch (which you can find at
https://lists.alioth.debian.org/pipermail/pkg-go-maintainers/Week-of-Mon-20160118/003015.html)
or were you referring to the discussion as a whole?

If your comment was in fact related to the patch, could you outline the
specific differences to the pkg-perl status quo that you dislike?

I haven’t committed anything yet (see
https://anonscm.debian.org/cgit/pkg-go/website.git/), so I’ll wait another
day to let you clarify things.

On Sun, Feb 7, 2016 at 5:55 AM, Martín Ferrari <tincho at tincho.org> wrote:

> On 04/02/16 18:57, Michael Stapelberg wrote:
> > I’m also in support of it.
> >
> > In case nobody else chimes in with an objection, I’ll commit it this
> > weekend.
>
> Sorry I am this late to the discussion, you probably have commited the
> new version by now.. Still I would like to voice my opinion for future
> iterations of the policy.
>
>
> I am sad to have missed this (I just kept saving the thread for when 'I
> had time' to properly read it), as I think this is an issue I always
> cared about, and hoped that it would move in a different direction from
> what the discussion went to.
>
> I started my life in Debian in the Perl group, and so it shaped my views
> pretty strongly. I always felt that was a very welcoming place, for
> newbies and old-timers, where work was always appreciated, and you did
> not feel alienated if you could not devote so much time sometimes (and I
> finally stopped working there at some point).
>
> It was very low-stress, and the group succeeds in maintaining an obscene
> number of packages with not so many active members. With many members
> staying for years, and old members are still friends. I don't remember
> any fight, just many calm technical discussions.
>
> A big part of all this "utopia" I am painting here - I believe - is that
> nobody "owned" a package. You only put your name in Uploaders before
> uploading, but you did not need to ask permission from anybody, because
> the owner was the group as a whole. So, instead of asking for
> permissions to fix bugs, you only discussed with the group bigger
> matters, like mass-commits, changes in tooling, etc.
>
> If you go away, most of the time nobody actually needs you to continue
> working. And I feel very relieved that I don't need to be committed for
> life to all the packages I have ever uploaded there.
>
> To address one concern about a more open policy; to avoid clashes, you
> never assume that nobody will touch the package unless you ask somehow.
> In that case, you would just leave a note in the changelog, asking other
> not to upload, and/or asking for help. For example, in this[1] commit.
>
>
>
> So, again, sorry for being this late to the conversation, but I hope we
> can discuss this approach for a next version.
>
> Tincho.
>
> [1]:
>
> https://anonscm.debian.org/cgit/pkg-perl/packages/libmemcached-libmemcached-perl.git/commit/?id=e780b94
>
> --
> Martín Ferrari (Tincho)
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



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