The process is to start the project outside the ZeroMQ org and then bring it in as a kind of sacrificial offering, which gets you admin karma. This also avoids rashes of new projects that don't go anywhere.
On Thu, Feb 4, 2016 at 5:01 AM, Kyle Kelley <[email protected]> wrote: > Hey all, > > I'm interested in creating prebuilt versions of zmq for node available. I > know that Pieter has started the more long term approach to supporting > node.js well with support in zproject: > > https://github.com/zeromq/zproject/pull/484 > > as well as in czmq: > > https://github.com/zeromq/czmq/pull/1319 > > In the meantime, I'd like to plug away on some of the prebuilt setup for the > current node bindings (https://github.com/JustinTulloss/zeromq.node), as a > standalone project (called e.g. node-zmq-prebuilt, zmq-prebuilt on npm). > This would mostly be dotting i's and crossing t's on appveyor + Travis > configuration, as well as finishing off what I worked on in > https://github.com/JustinTulloss/zeromq.node/pull/486 > > Would this be a good project to startup within zeromq, or should I build it > out on a different org for now? > > -- > Kyle Kelley (@rgbkrk; lambdaops.com) > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
