Groups > linux.debian.maint.python > #9366

Re: Backport of python-lockfile and suggested team maintenance

From	Ben Finney <bignose@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Backport of python-lockfile and suggested team maintenance
Date	2017-03-11 01:50 +0100
Message-ID	<tjDom-3gr-29@gated-at.bofh.it> (permalink)
References	(2 earlier) <ti27x-199-35@gated-at.bofh.it> <tiq09-1A2-13@gated-at.bofh.it> <tiMam-bQ-17@gated-at.bofh.it> <tj5G2-5dM-13@gated-at.bofh.it> <tjrQh-3VY-97@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Andreas Tille <tille@debian.org> writes:

> In your last mail you agreed that team maintenance would acceptable

To clarify: I've not agreed with that.

Rather, I've agreed with your position that the practice of a team as
maintainer is sensible, and I've said the practice of an individual as
maintainer is sensible.

A particular package can't be both of those at once, of course. But both
are common practice in Debian, and both are sensible.

So, a decision of which to choose can't be based only on “option X is
sensible”, because that doesn't argue *against* other options.

What I've been confused by is the conflation of “team as maintainer is
sensible”, which I agree with, and some implicit assumption of
“individual as maintainer is *not* sensible”, which I don't agree with.

I haven't got an answer from you on whether that's your position, so I
don't even know what argument you're presenting.

> Thanks for considering

I've tried :-) but haven't even seen any reason presented to change the
package maintenance from what it is now. I'd consider it if that were
presented.

As for the Git commits you've made for backports: I remain open to
considering a pull request from any published Git repo at your choice of
host.

-- 
 \       “The great thing about science is we can test our ideas.… But |
  `\   until we do, until we have data, it is just one more proposal.” |
_o__)                                     —Darren Saunders, 2015-12-02 |
Ben Finney

Thread

Backport of python-lockfile and suggested team maintenance Andreas Tille <andreas@an3as.eu> - 2017-03-02 11:00 +0100
  Re: Backport of python-lockfile and suggested team maintenance Ben Finney <bignose@debian.org> - 2017-03-03 12:00 +0100
    Re: Backport of python-lockfile and suggested team maintenance Andreas Tille <tille@debian.org> - 2017-03-06 15:50 +0100
      Re: Backport of python-lockfile and suggested team maintenance Ben Finney <bignose@debian.org> - 2017-03-07 17:20 +0100
        Re: Backport of python-lockfile and suggested team maintenance Andreas Tille <tille@debian.org> - 2017-03-08 17:00 +0100
          Re: Backport of python-lockfile and suggested team maintenance Ben Finney <bignose@debian.org> - 2017-03-09 13:50 +0100
            Re: Backport of python-lockfile and suggested team maintenance Andreas Tille <tille@debian.org> - 2017-03-10 13:30 +0100
              Re: Backport of python-lockfile and suggested team maintenance Ben Finney <bignose@debian.org> - 2017-03-11 01:50 +0100
  Re: Backport of python-lockfile and suggested team maintenance Thomas Goirand <zigo@debian.org> - 2017-03-03 14:10 +0100
    Re: Backport of python-lockfile and suggested team maintenance Barry Warsaw <barry@debian.org> - 2017-03-03 15:30 +0100

csiph-web