Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: [DPMT] radical changes: automation, carrot and stick
Date: Fri, 02 Oct 2015 20:40:02 +0200
Message-ID: <qfdpo-37r-21@gated-at.bofh.it>
References: <qeViO-2oq-17@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
User-Agent: KMail/4.13.3 (Linux/3.13.0-63-generic; KDE/4.13.3; x86_64; ; )
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1830096.ZBxJnrbYLS"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 128
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:7428


--nextPart1830096.ZBxJnrbYLS
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Friday, October 02, 2015 01:18:00 AM Piotr O=C5=BCarowski wrote:
> I think that the main problem of our team is that we have over 300
> members and only few people contribute to packages they didn't inject=
 to
> the repo (some people do not care even about those).

I think this is in part because we have a culture that discourages this=
.  I do=20
it, but only, as a rule, for packages that have DPMT set as maintainer.=


> Here are some ideas on how to change that:
> * team only in Uploaders field, the main contact (AKA Maintainer) has=
 to
>   be real person (reason: nobody reads -team mailing list) + automati=
c
>   team subscription via script that sets up git repository

Personally, I like the current approach where someone can either commit=
 to=20
either strong team maintainership (DPMT in maintainer) or weak team=20
involvement (DPMT as uploader).  If you'll check, I have done both and =
it=20
reflects my level of interest in the package.

If I'm maintainer, absent urgent things like RC bug fixes, I expect to =
know=20
about things before they go in the archive (delayed or not).

I do read the list as the bugs come in.  I don't necessarily try and de=
al with=20
all of them, but I do tackle them as i have time. I wish more people wo=
uld do=20
this, but changing the DPMT to uploader isn't going to help that.  Even=
 if=20
more people get bug mail, we can't make them read it.

> * when someone who is not listed in debian/control (i.e.
>   Maintainer/Uploaders) wants to upload team package - just commit
>   and upload to DELAYED/2 (in case of RC bug) or to DELAYED/7, no nee=
d
>   to notify anyone, because...

I think for RC issues, just upload.  For non-RC issues, I don't think j=
ust=20
uploading, even to delayed is OK.

> * emails with all commits (diffs) made by someone not listed in Maint=
ainer
>   are automatically sent to Maintainer

I like this idea, although I think it's OK to limit it to mailing diffs=
 by=20
someone neither in uploaders nor maintainer.  In cases where I have act=
ive co-
maintainers in uploaders, there's no need to mail their commits to me a=
s I=20
trust them.

BTW, don't forget that once we switch to git, the repos will be full so=
urce,=20
not just /debian so these diffs could get large.

> * adding a package to the team (and getting all benefits, like
>   sponsoring, bug fixes, etc.) requires pushing at least one commit t=
o
>   package without member's name in debian/control a month
>   (doesn't matter if it's a typo fix, RC bug fix or a tag which can
>   be made only by those who upload/sponsor packages from now on)

I think any sponsor can ask people do this now.  We don't need a rule.

> * automatic emails with a warning if there's more than 31 days since =
the
>   last contribution described above
> * removal=C2=B9 of packages (not person) from the team if there's no
>   contribution in 3 months in a row (and given person is not MIA, as =
in
>   active in other packages, for MIA ones: decide if someone wants to
>   take over or orphan the package, no more team packages that nobody
>   takes care of and no objections if someone takes over your package)=


Personally, I would find this kind of rule demotivating.  I think it wi=
ll=20
actually discourage participation which isn't what we want.

> I can implement all scripts that automate above tasks but someone
> will have to replace me in the admin seat.
>=20
> [=C2=B9] as in upload to unstable without DPMT in Uploaders, repo sta=
ys in
>     case one decides come back

I liike some of your suggestions.  I definitely agree with the goal of =
trying=20
to get more people working on a team wide basis.

Scott K
--nextPart1830096.ZBxJnrbYLS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABCAAGBQJWDs4rAAoJEHjX3vua1Zrxy/YP/3eRc0Thbzs2KGZG3Dytd6zU
B/xdkVRmpiXSSJyiRCiG97Zq25Eqyih4tYWKm08eYdTkzVojlEgKgY3eCZvQK3i5
MSU4SgS9KLxojx7SbsvJlOJgg9UHFe/ZcZkPnz0Ek0vKp4WQH66oDSisGs7I7IM0
ErjzNxdlAQ0Rt8fQAeYgvJ5IJ/6nOnyqr4bn6ERqsNWRR0QrEzGTTkvXW7pblWgB
JlYl9OfeGfrg3oHkBpVkUZrOFyxxxJyuNjGwbZYttSD9HvTsfX+JD4nc0Jxp1QLH
CQqtCwYrrglLSd2+vSdEZrMCgql3kKyS6aGgQGLJFD63DqqZVdSXcP+hmdbbN8lt
P+J1BFvDhAZWDI3+tSv+y37wNvpX4OjvuP9wOCjfM+AWTlRCzBNTkCzo0CmdXNmq
JTkEjMFFnf2V3CTy4eMSEEM+kjc9Aikjg/Ds/P7FXd+babu5A1ffVVDfuTjUKF9S
X6OF1wDfu0pgrHuRpIKNYhI8Fg5yxRdHI8aRJwVeOgndp6R5Qb08I0NAn3N66qK/
3VOq3sC5Xl/xZ1rmV9wdRvt27ofBxvKVcQqFFqeokn4Axm0DeklNTrPPI8E0opXt
LKUAerpAUtIf7oHqekV6AqVaUe0K5Yb/a8ssqNpbudW8WmIxh1w9i+e4KUesOfUz
Ju6bwe5Nv5rfr7WYbNCz
=neLi
-----END PGP SIGNATURE-----

--nextPart1830096.ZBxJnrbYLS--