Ricardo,

Sorry for the slow reply -- I'm in China at SIGGRAPH Asia this week.

I asked Jonathan about the github repo and I think that was being used
by an internal development effort.  It's not intended to be a public
repo.

We don't currently have a way to contribute patches, but this is
something I think we'd like to put together.  There currently are no
planned releases coming up, in part because the developers at SCI were
tasked on more pressing jobs.  Do you have specific features that
you're ready to add?

I'm under the impression that Kitware is fairly interested in
development efforts wrt to Cleaver.  There are lots of small features
we've talked about internally adding, which I think would be
interesting to discuss.  David Thompson and I have been discussing a
visit to NC about this topic?  I think the folks at SCI as well as
myself are certainly interested in working with you guys too.  I guess
the first task at hand is to try to get everyone on the same page?

Thanks,
Josh

On Sat, Nov 16, 2013 at 1:27 AM, Ricardo Ortiz
<ricardo.ortiz@kitware.com> wrote:
> Hello developers,
>
> I have a couple questions:
>
> 1. What is the best way to contribute patches to Cleaver?
> 2. Is there a planed release in the near future (far future)?
>
> I noticed that SCI has a Github account and that Cleaver is one of its
> repositories.  For us the best way to contribute to it is to create pull
> requests against this repository but I want to make sure upstream get these
> patches.  Thanks.
>
> Best,
>
> /Ricardo
>
> --
> Ricardo Ortiz, Ph.D.
> R&D Engineer
> Kitware, Inc.
> 101 East Weaver St. G4
> Carrboro, NC 27510
> Phone: (919) 869-8870
> Fax: (919) 969-6910
>