I agree, Jeffery. No single individual should have complete control of maintaining the specification or moderating the discussion. A committee should be formed so that JSON-RPC doesn't become one single person's thing, and so that there can be accountability and collaboration.
Mycompany also has several implementations of the json-rpc 1.1WD in java and ruby which have been in a production environment for about 10 months..So I would rather not see the spec just left up for grabs to the first person that responds.. Maybe a commitee would be better than a single individual?
On 8/19/07, Jan-Klaas Kollhof <
keyjaque@...> wrote:
Hello all,
As many have seen over the past two years my involvement with JSON-RPC have almost come to a stop. I am sorry to let everyone down. With a fulltime job and other hobbies I just don't have time.
So, I am looking for anyone who would like to be the discussion group's maintainer(group owner).
If anyone likes to take over the subversion repository, source code, ticket and wiki on
http://json-rpc.org, please let me know, too. I am happy to keep this up and running until someone volunteers to take it over.
Hello all, As many have seen over the past two years my involvement with JSON-RPC have almost come to a stop. I am sorry to let everyone down. With a fulltime...
Jan-Klass: I would very much like to help take over maintaining the discussion and development of JSON-RPC. I have just released new JSON-RPC client and server...
Mycompany also has several implementations of the json-rpc 1.1WD in java and ruby which have been in a production environment for about 10 months..So I would...
I agree, Jeffery. No single individual should have complete control of maintaining the specification or moderating the discussion. A committee should be formed...
Agreed. In particular I would like to see that the 1.0 spec is archived and kept available, for those of us who have issues with the 1.1WD in it's current ...
Hi, Agreed! My company is developing solutions for tourism using JSON-RPC too, and would be interested in participating to the committee. Before the committee...
Here's a list of action items that I see as being pending: 1. Determine who will be the discussion group's maintainer (group owner); Jan-Klass was referring to...
... In case hosting is still needed, i could provide a virtual server for this too. ... Count me in as well. Mit freundlichen Grüßen/Regards, Arne Blankerts ...
Yes, count me in as well. For 2,3,4 - If you want to move to google groups (fine with me), you know code.google.com also has wiki, issue tracking, svn, etc....
Does anyone object to moving over to Google Groups? If not I can create a new Google Group for JSON-RPC tomorrow and we can begin discussing matters there. We...
My feeling about http://code.google.com is that the purpose there is to promote Google's own public APIs and some Google related stuff ... Not really an...
I did not get the same feeling. Although a spec might not fit by itself, a sample code implementation that sticks to the specs would be a worthwhile addition....
Wow, lot's of action. I have a few things; I do think google groups hosting is a bit dangerous for an open project. Google has shown itself to be very good...
Mikeal Rogers
mikeal@...
Sep 3, 2007 5:43 am
... Agreed, but mainly about files/svn etc.. I guess google is ok for hosting the mailing list, and might even be a good point regarding 'publicity', archives...
Hi all, I have been offline for a week. Wow, lots of discussion going on. Regarding the hosting, I will keep it up and running as long as it takes. No rush...
I'll love to be part of this, I'm using json-rpc as a side project, but I'm planning on using it a lot more. As for the trac/svn I got several patches I'll...
Having problems with message search?
Offline 
Send Email