Evan, Moving some of the contrib and clients out could make sense. One of the problems is that current committers don't necessarily have the skill set to review patches for those contribs. We could either move those contribs to other repositories or make the contributor of those contribs committers.
Thanks, Jun On Fri, May 25, 2012 at 11:59 AM, Evan chan <e...@ooyala.com> wrote: > Jun, > > What if the contrib and other clients were split off into their own > projects? This would help achieve binary release for core Kafka, plus > enable faster development of the other projects (for example, I could > easily fork and improve on the ruby client without worrying about the other > code...) > > -Evan > Carry your candle, run to the darkness > Seek out the helpless, deceived and poor > Hold out your candle for all to see it > Take your candle, and go light your world > > > > On May 25, 2012, at 10:34 AM, Jun Rao <jun...@gmail.com> wrote: > > > Ken, > > > > We tried to do a binary release and ended up going through 10 RCs, mostly > > to sort out the license of all jars. We gave up in the end. One of the > > biggest problems is that we have contribs for clients in other languages, > > which introduces dependent libraries in C#, go, etc whose license > agreement > > is not totally clear to us. If someone can help out on that, we'd be > happy > > to do a binary release. > > > > Thanks, > > > > Jun > > > > On Fri, May 25, 2012 at 10:16 AM, Ken Krugler > > <kkrugler_li...@transpac.com>wrote: > > > >> Hi Jun, > >> > >> Here's my +1 for publishing Kafka (jar and pom.xml with dependencies) to > >> some public repo. > >> > >> That makes it _much_ easier for a project to include Kafka. > >> > >> Note that it's pretty easy to get it into the Apache repo; publishing to > >> Maven central is a bit more challenging... > >> > >> -- Ken > >> > >> On May 25, 2012, at 9:46am, Jun Rao wrote: > >> > >>> Sam, > >>> > >>> Because of the overhead of certifying every dependent jar, we chose to > do > >>> only the source release, not the binary release for Kafka. This > creates a > >>> bit overhead for our users since they have to build the source to > >> generate > >>> the kafka jar. > >>> > >>> Thanks, > >>> > >>> Jun > >>> > >>> On Thu, May 24, 2012 at 10:34 PM, Sam William <sa...@stumbleupon.com> > >> wrote: > >>> > >>>> Hi, > >>>> Im writing a framework involving kafka consumers in scala and Im > using > >>>> sbt as the build tool. Where do I get kafka-0.7.jar from ? Is it > >>>> available in any maven or ivey repositories? > >>>> > >>>> > >>>> Sam William > >>>> sa...@stumbleupon.com > >>>> > >>>> > >>>> > >>>> > >> > >> -------------------------- > >> Ken Krugler > >> http://www.scaleunlimited.com > >> custom big data solutions & training > >> Hadoop, Cascading, Mahout & Solr > >> > >> > >> > >> > >> >
