Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"

From Carsten Schoenert <c.schoenert@t-online.de>
Newsgroups linux.debian.maint.python
Subject Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)"
Date 2023-07-23 09:50 +0200
Message-ID <GUC0O-29Pn-7@gated-at.bofh.it> (permalink)
References <GFKCZ-fm0l-1@gated-at.bofh.it> <GFLpo-fmvy-7@gated-at.bofh.it> <GUBo5-29xU-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hello Christian,

Am 23.07.23 um 09:09 schrieb c.buhtz@posteo.jp:
> Hello,
> 
> On 2023-06-12 10:40 Jonathan Carter <jcc@debian.org> wrote:
>> Adding DPT to at least uploaders and having the package VCS in the
>> python-team namespace would probably be a good idea, but that's up to
>> Jonathan Wiltshire.
> 
> I have to state that after 5 weeks of waiting there is no reaction from
> Jonathan Wiltshire by mail, any bug-ticket (in context of backintime)
> and even IRC.

it might be sounds strange to you, but 5 or sometimes also 8 weeks and 
longer isn't a long time within Debian. I know that my answer isn't 
helping you, it's simply quite all of the DMs and DDs are doing their 
work for Debian within their free and spare time and they can decide 
when to work on something.
And Jonathan isn't only active as package maintainer, it's up to him 
what are his priorities and on what he wanted to work on.

> There is also this bug ticket where I had specific questions (in August
> last year) only the maintainer can answer but got no reaction.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940319

Why can't only the maintainer answer this?
Also the issue is marked correctly as wishlist, typically this indicates 
also that the underlying issue isn't time critical.

If you want to get applied something quickly then make it easy to the 
maintainer to accept the suggested modifications. Means prepare one (or 
more) patches which are easy and save to pick. I can't see anything like 
this within the bug report.

For sure testing and test suites are always a good thing to add, but 
basically they are not needed for the functionality of a package.

> How can we proceed further?
> IMHO it is blocking the process waiting on someone who do not answer.

I don't understand what or who is blocking whom here?
Is it that you feel you are blocked with your upstream work by the 
maintainer?
Do you like to have more power within the Debian package of your 
upstream work?
Is there a issue in the Debian package that is causing trouble on the users?

If you only think that the maintainer of backintime should be switched 
to the DPT then this is only a wish. And I don't think doing such a 
switch is improving the situation for you, still someone needs to do the 
work you requesting.
The Debian policy is quite clear that a maintainer of a package has more 
or less the full power of the package, that's how Debian is build and 
also working for years.

So far I've not seen any DPT member in the past weeks who would be 
willing to do work on the package backintime. If you want to improve 
this then you are welcome to become a member of the DPT by doing work on 
packages which are in the maintenance of the DPT, but becoming a DM will 
take time and requires to learn and accept the rules of being a DM.

So you want to process further something?
Provide patches, improve packages, enhance documentation, do some kind 
of the work. That's the typical answers to that question.

-- 
Regards
Carsten

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[backintime] Switch the maintainer to "Debian Python Team (DPT)" c.buhtz@posteo.jp - 2023-06-12 10:00 +0200
  Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Jonathan Carter <jcc@debian.org> - 2023-06-12 10:50 +0200
    Re: [backintime] Switch the maintainer to "Debian Python Team  (DPT)" <c.buhtz@posteo.jp> - 2023-07-23 09:10 +0200
      Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Carsten Schoenert <c.schoenert@t-online.de> - 2023-07-23 09:50 +0200
        Re: [backintime] Switch the maintainer to "Debian Python Team  (DPT)" <c.buhtz@posteo.jp> - 2023-07-27 22:00 +0200
          Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" c.buhtz@posteo.jp - 2023-07-28 09:20 +0200
          Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Carsten Schoenert <c.schoenert@t-online.de> - 2023-07-28 12:00 +0200
            Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" c.buhtz@posteo.jp - 2023-07-28 13:10 +0200
              Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Simon McVittie <smcv@debian.org> - 2023-07-28 14:40 +0200
              Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Andrey Rakhmatullin <wrar@wrar.name> - 2023-07-28 15:40 +0200
            Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Simon McVittie <smcv@debian.org> - 2023-07-28 14:50 +0200
              Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" c.buhtz@posteo.jp - 2023-07-28 15:00 +0200
            Re: [backintime] Switch the maintainer to "Debian Python Team (DPT)" Nicholas D Steeves <sten@debian.org> - 2023-07-28 21:40 +0200

csiph-web