Its been on my mind to focus a bit on building a local community here and
the opportunity came when Yash reached out to talk about Drill. It was a
good discussion where I shared the 2 cents I've understood about Drill.
Clearly there are enthusiastic folks who want to contribute to Open Source
in general but need some hand holding.
Specifically we spoke about the areas where people can contribute and the
different StorageEngine implementations seemed like a reasonably
independent stream of work that someone can pick up. We decided to spend
some time understanding the interfaces and also figure out a database that
we can implement for. Mongo was something we talked about owning to its
popularity. It looks like there is a JIRA out
deal with Mongo. Not sure if this means the same as implementing
StorageEngine for Mongo!
In any case the folks are open to exploring other ways of contributing.
Just that the Mongo idea seemed to be up-for-grabs at the moment. I'll look
up to others on this list for more guidance before concluding.
On Mon, Aug 19, 2013 at 8:07 PM, Tanujit Ghosh <[EMAIL PROTECTED]>wrote:
> Excellent stuff guys :-)
> missed out this session as i'm in pune...but please let me know if there is
> anything that i can pick up and help out in anyway possible.
> On Mon, Aug 19, 2013 at 7:45 PM, Yash Sharma <[EMAIL PROTECTED]
> > Hi Guys,
> > We had a small drill meetup here in Bangalore with few like minded people
> > who would love to contribute to Drill.
> > We are a group of 3 people here. We called Srihari for discussion - who
> > already working on the REST api part currently.
> > Me , Srihari and Arun met and discussed which all areas can we start
> > working on. We decided to begin with the StorageEngine part of it where
> > could make some API's for some storage engines. We decided to start off
> > with MongoDB.
> > Please give your suggestions for the same, so that we can start some work
> > over it.
> > Best Regards,
> > Yash.
> > ________________________________
> > NOTE: This message may contain information that is confidential,
> > proprietary, privileged or otherwise protected by law. The message is
> > intended solely for the named addressee. If received in error, please
> > destroy and notify the sender. Any use of this email is prohibited when
> > received in error. Impetus does not represent, warrant and/or guarantee,
> > that the integrity of this communication has been maintained nor that the
> > communication is free of errors, virus, interception or interference.