[dropping the bug from CC; adding the mailing list] Hello,
On Fri 03 Aug 2018 at 10:58PM -0700, Jonathan Nieder wrote:
> This doesn't mean I like the change. It just means that I think this
> reflects the outcome of the discussion you cited. My understanding is
> that the current policy process doesn't require me to check that the
> main relevant stakeholders among those who haven't spoken up have
> weighed in, since they can propose additional changes to address any
> harms.
This is an interesting question. The closest thing we have in the
Policy Changes Process is
Package maintainers whose packages may be impacted should have
access to policy change proposals, even if they do not subscribe to
policy mailing lists (policy gazette?).
but we don't have an implementation of this.
Often I am tempted to CC -devel in the hope of gathering relevant input,
but that somewhat defeats the purpose of a separate -policy mailing
list. We can't copy every bug there.
Suggestions for doing better at this would be welcome.
--
Sean Whitton
signature.asc
Description: PGP signature
