Moving patches traffic to a another list?

[Gregory Szorc]

On Thu, Mar 19, 2020 at 3:06 AM Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:

> Hello everyone,
>
> After chatting with various people, I would like to suggest that we move
> patches and phabricator away from mercurial-devel at mercurial-scm.org to a
> new mailing list (mercurial-patches at mercurial-scm.org).
>
> My goal here is to make other email discussion between developer more
> visible and to encourage core-developers to exchange more about their
> ideas. Right now, the patches related noise (especially from phabricator
> who don't thread series) makes other discussion hard to spot and follow.
> I know developers that explicitly don't read the ML but for specific
> keyword.
>
> What do you think?
>

I like the idea of having a lower volume list for non-patch discussions. I
think mercurial-devel is that list. If the list is Phabricator only, we
should disable posting to ensure all discussion is captured on Phabricator
and isn't fragmented across tools.

I support moving all Phabricator traffic to a new list. I'm OK with email
based patches still going to the mercurial-devel list, as volume is low.

I think it would also be interesting to explore a mechanism to add
mercurial-devel CC to a Phabricator review. A use case would be if there is
a particularly controversial change under review and we want to raise
awareness on the developer list to get more eyeballs on it. I anticipate
the number of reviews incurring this would be low. Is this technically
doable?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20200320/2679ff9f/attachment-0002.html>