----- Original Message ----
> From: Michael Lum <[email protected]>
> To: [email protected]
> Cc: Joe Schaefer <[email protected]>
> Sent: Thu, August 12, 2010 5:09:39 PM
> Subject: Re: time for a reboot?
>
> I still intend to submit a patch implementing thrift-c-glib,
> and then maintaining it, but have been doing the work on
> github to clean it up. It doesn't really matter to me where
> I do the work. We're just after a pure C, leak-free code
> generated interface to Thrift, and continuing the previous
> work that had been contributed seemed like the right way
> to get it.
Right, this is the sort of activity a healthy Apache project
would encourage you to do in the Apache svn repo for thrift.
Hoarding the commit bit isn't what we should be encouraging
from the thrift committers.
> Commercially speaking, Thrift is a key component of our
> service architecture, so we have a vested interest in its
> stability. We pretty much internally version our own thrift
> releases internally by taking stable-ish trunk revisions,
> forking, patching and versioning, and then building packages
> (rpms and debs) for the engineers to use here. We used to do
> that with Cassandra, but now we are able to use the release
> versions. For selfish reasons, I would be glad to offer our
> developers' time to make Thrift builds and releases easier and
> more convenient, although as you may have seen from our
> patch submissions, we'd probably keep obstinately pushing to get
> the source build to work on stock CentOS 5 (see the autoconf
> 2.59 JIRA tickets).
Would love to see you be able to rely on thrift releases as
much as you currently do for cassandra; absolutely this is
great feedback.
