On 09/28/2017 09:46 PM, Michał Górny wrote:
> As far as I'm concerned, one indicator for all bugs is enough,
> especially that in some cases projects have Gentoo upstream which blur
> the line between upstream and downstream bugs.

I don't buy this argument. The Gentoo Package repository is different
from the upstream software repository, so there needs to be a separation
between how to manage these situations. The guidelines (or requirements,
depending on how we decide on things) in this case only has the package
repository in scope and we shouldn't differentiate between gentoo as
upstream and external upstreams for the purpose of the package repository.

For this to be an issue would be a new patch release / revbump that only
happens in the Gentoo Package Repository but is not part of upstream,
which would be odd, in particular given we have a specific section in
the Gentoo social contract on:
###
We will give back to the free software community

We will establish relationships with Free Software authors and
collaborate with them when possible. We will submit bug-fixes,
improvements, user requests, etc. to the “upstream” authors of software
included in our system. We will also clearly document our contributions
to Gentoo as well as any improvements or changes we make to external
sources used by Gentoo (whether in the form of patches, “sed tweaks” or
some other form). We acknowledge that our improvements and changes are
much more meaningful to the larger Free Software community if they are
clearly documented and explained, since not everyone has the time or
ability to understand the literal changes contained in the patches or
tweaks themselves.
###

Further, for things to be an issue it would requires that automatic
tools touches bugs based on data. I can see that for Closes, which is an
explicit action, but not really for Gentoo-Bug, as a commit could be a
partial solution referencing it, e.g a stabilization, so the most an
automated tool would do is likely post a comment that the bug was
referenced in commit XYZ.

For Closes it brings up the question on whether only a specific list of
categories should be considered for such automated tooling, e.g for
specification of to https://bugs.gentoo.org/NNNNNN it will only
influence "Gentoo Linux" product and reject action from the Gentoo
Package Repository for the others, then the root cause of the upstream
issue is handled, as bugs for that is in Gentoo Hosted Projects.

-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3