From jwashin at vt.edu Thu Mar 29 16:48:08 2007 From: jwashin at vt.edu (Jim Washington) Date: Thu, 29 Mar 2007 10:48:08 -0400 Subject: [z3] z3c.jsonserver In-Reply-To: <45B7E1A2-21DE-4AC3-AA84-5284E90A8552@lovelysystems.com> References: <32B0A780-EFCC-4602-B943-92D0C6F7DFE3@zope.com> <8928d4e90703261745q4885a120oab1954fef77f0d1c@mail.gmail.com> <29EC2AEE-58B8-4602-B259-41BBFAD53DF7@zope.com> <8928d4e90703270454u50593f9ex756fe7c1f1cb1348@mail.gmail.com> <46090CE5.4070502@vt.edu> <17929.25627.31012.31341@gargle.gargle.HOWL> <46096F8C.3040205@vt.edu> <20070327193101.GC6296@slinkp.com> <46097E7B.4010606@vt.edu> <45B7E1A2-21DE-4AC3-AA84-5284E90A8552@lovelysystems.com> Message-ID: <460BD1A8.6050105@vt.edu> cc for the list... Jodok Batlogg wrote: > hi jim, > > any objection to move z3c.jsonserver to svn.zope.org? > we'd like to eggify / buildoutify it and develop it further. > > Hi, Jodok I have no particular objections (it should all be ZPL), though I am maintaining a separate zif.jsonserver at zif.sourceforge.net, which is in a namespace package ("zif"), and hopes to have eggs/buildout support soon. Maybe you can help David Pratt with eggifying zif.jsonserver. z3c.jsonserver has, in addition to the zope 3 support, some work in branches for zope 2/plone support by Balazs Ree, with intention of a future unified package for both zopes, though this has been difficult due to proliferation of Five versions, as I understand it. You may wish to collaborate with him, if that is the further development you suggest. If you wish to assist development on zif.sourceforge.net, let us know, and David or I can give you write access to svn. As far as svn.zope.org is concerned, I would have placed this in svn.zope.org myself a long time ago, but I cannot do the ZF committer agreement. It's a long story :) . Let me know what you decide to do. I personally think keeping all zope3-specific development on sourceforge would be best, though I do not mind seeing competing zf.jsonserver / zif.jsonserver / z3c.jsonserver or even lovely.jsonserver implementations. More eyes and ideas makes better code in the long run. - Jim Washington