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 takes a more "formal" form, I would second the
suggestion to migrate to google groups.

Lorenzo Pastrana

Weston Ruter wrote:
> 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.
>
> On 8/19/07, *Jeffrey Damick* <jeffreydamick@...
> <mailto:jeffreydamick@...>> wrote:
>
>
> 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@...
> <mailto: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,
> <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.
>
> Jan-Klaas Kollhof
>
>
>
>