[execnet-dev] [RFC] putting execnet under the C4.2 process and under the MPL
holger krekel
holger at merlinux.eu
Mon Jun 11 13:24:24 EDT 2018
Hey Ronny,
On Mon, Jun 11, 2018 at 15:34 +0200, RonnyPfannschmidt wrote:
> Hi Holger,
>
> https://rfc.zeromq.org/spec:22/C4/
>
> https://www.mozilla.org/en-US/MPL/2.0/
>
> its not necessarily clear that this will bring more community,
> but the process in C4.2 is designed to prevent stuff like the 2 recent
> major messes (aka execmodel addition, and the serializer protocol
> regression)
well, you could also fork an earlier version and release as
a different project? the license allows this ...
i am skeptical of discussing licensing and other process questions
if execnet does not see much development at all ...
holger
> -- Ronny
>
> Am 08.06.2018 um 18:05 schrieb holger krekel:
> > hi Ronny,
> >
> > can you post a link to "c4.2" and "mpl" both of which i don't recall
> > as code words currently?
> >
> > also, what evidence is there that changing "governing" would bring
> > more community? Are there people wanting to land PRs but they are
> > blocked?
> >
> > holger
> >
> >
> >
> > On Fri, Jun 08, 2018 at 16:00 +0200, RonnyPfannschmidt wrote:
> >> Hi everyone,
> >>
> >>
> >> since execnet development has been kind of dead since ages,
> >> i wonder if opening up using a proofen model would help along.
> >>
> >> thus i propose putting execnet under c4.2 as governing process while
> >> using the mpl as compatible license that has sufficient liberties.
> >>
> >> -- Ronny
> >>
> >> _______________________________________________
> >> execnet-dev mailing list
> >> execnet-dev at python.org
> >> https://mail.python.org/mailman/listinfo/execnet-dev
More information about the execnet-dev
mailing list