Re: Separate Mailing Lists for Patches vs General Dev Discussion?

[Ludovic Courtès]

Hi,

Vincent Legoll <address@hidden> skribis:

> But resurrection & real use of patchwork (or any other consensus
> web tracker) would be a plus for at least some of us newcomers
> from different horizons.

The instance at <http://patchwork.sourceware.org/project/guix/list/> is
not widely used, it seems.  Part of the problem is that it often does
not automatically detect whether a patch has already been committed
(requiring manual intervention), and does not recognize patch series and
revisions.

Newer versions of Patchwork fix the latter, as can be seen at
<http://patchwork.ozlabs.org/project/glibc/list/>.  Not sure about the
former.

Maybe we could register at ozlabs.org to see the difference?

> I can understand the repulsion against some of them, but a PR-like
> enabled one could ease the on-boarding of new contributors. So if
> it's acceptable to committers, why not try to use one a bit more
> regularly ?

Some of us prefer an email-based workflow, though there’s no consensus.
I’ve tried to look for tools that would allow not only email but also a
CLI or Web UI, as you might have seen in the ML archive, but to no
avail.  So, concrete suggestions are welcome.  :-)

Thanks,
Ludo’.