On Thu, Sep 01, 2016 at 01:03:39AM +0200, Tomasz Nitecki wrote:
>...
> On 31/08/16 19:28, Adrian Bunk wrote:
> > On Tue, Aug 30, 2016 at 04:34:21PM +0300, Adrian Bunk wrote:
> >> Similar, O/RFA -> ITA changes should also not trigger listing as "new".
> >
> > After thinking about it further, how-can-i-help should simply stop
> > listing ITA bugs:
> >
> > The semantics of ITA is "someone is adopting it, and the new maintainer
> > is expected to make an upload soon".
> >
> > At that point it is unlikely that help is needed.
> >
> > And many of the rare cases where the new maintainer does need help are
> > already covered by RFS/RFH/#825349.
>
> While I do agree that many ITAs don't need any help, I personally often
> check them, as they are sometimes misused (unintentionally) by newcomers
> who just assign them to themselves and then vanish. Just one of a
> possible use cases of this feature.
>
> Since you can easily configure how-can-i-help to ignore those bugs
> (section 'IGNORE SELECTED TYPES OF OPPORTUNITIES' in manpage), I'd
> rather leave it as it is.
Unless I miss something, how-can-i-help is primarily a tool for giving
newcomers suggestions where they could start contributing and current
Debian developers suggestions where they could expand their work on
Debian.
While doing special QA cleanup tasks is helpful and appreciated, the
information about ITAs you use for some very specific QA work is not
useful for the target audience of how-can-i-help.
I fully understand the value of a "debian-qa-helper" tool that lists for
example all ITA bugs and also has them ordered by date of the latest
update to the bug (for finding stale ITAs). But that would be
a different tool for a quite different target audience.
> Regards,
> T.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
