Everyone ok with the usual MPLv2 for the license? On Tue, Sep 8, 2015 at 8:19 AM, Pieter Hintjens <[email protected]> wrote:
> First recipe can be Hello World :-) I suggest we make the whole repo > with pull requests as always. So all we need to get started is a new > repo, a link to RFC 22, a license for code. > > I think we can make a load of different Hello World recipes, for > different socket types. > > On Tue, Sep 8, 2015 at 4:32 AM, Doron Somech <[email protected]> wrote: > > Happy to hear the good responses. I have limited access to internet and > > computer in the coming month so I won't be able to contribute much. But > will > > contribute afterwards. Looking forward to see the first recipe... > > > > This is a fantastic idea... > > > > The Guide is old, and the process predates C4. It's time to build a > > new repository of examples IMO. > > > > We can write recipes clearly, as problem statements, and then show how > > to make them in all our languages and bindings. > > > > > > > > On Mon, Sep 7, 2015 at 5:28 PM, Brian Knox <[email protected]> > wrote: > >> I think a ZeroMQ cookbook sounds like a neat idea. I'd happily > contribute > >> some examples for the GoCZMQ bindings - it would be a fun project to > >> implement some of the patterns using them. > >> > >> Tying each pattern to a problem statement would be very much in the > spirit > >> of ZeroMQ development methodology itself. > >> > >> On Mon, Sep 7, 2015 at 10:03 AM, Doron Somech <[email protected]> > wrote: > >>> > >>> Hi All, > >>> > >>> Problem1: Find the right zeromq pattern is sometime complicated, not > all > >>> patterns are documented and searching through different blog posts or > >>> mail > >>> archives is hard. > >>> > >>> Problem2: I have a problem and I want to know if another user in the > >>> community already had it and found a simple solution. Right now I have > to > >>> ask on the mailing list and wait for somebody to response. > >>> > >>> So zeromq guide have some patterns documented but I think we can do > more. > >>> My idea is to create cookbook repository, so each pattern has > >>> documentation > >>> (what is the problem this pattern is solving and how to use) and > >>> implementation in at least one language. > >>> > >>> It will be easier to direct people to a specific pattern in the > cookbook > >>> repository and also share the different problems and solutions we all > >>> use. > >>> > >>> What do you think? > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> > > _______________________________________________ > > 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 > > > _______________________________________________ > 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
