Ted, I will start with both, with web site updates being my immediate path forward.
I will try to capture all the answers and tips that I get through the Dev mailing list into a set of documented practices, and upload it there. Three things I think need specific modification and details are: 1. Accurate and up-to-date "how to get started" - how to get code, where to look for what, etc. 2. How to compile, unit and integration test (currently we cannot run mvn tests) 3. How to submit a patch as a contributor and then go from there. Also, there is I think fair amount of documentation that can be added to the internals of the Drill, so that one can write extensions/plugins as I intend to do. What is, btw, that side project you were referring to? Thank you, Edmon On Sunday, August 30, 2015, Ted Dunning <[email protected]> wrote: > Edmon, > > This sounds Great! > > There are two ways to move forward on this. > > One is that you can already send pull requests for the web-site itself. > That should be pretty easy for content pages since they are all done in > markdown and are easy to edit or create. > > Secondly, there is a side project which aims specifically to have examples > of how to do things with Drill, much as you are describing. Currently that > project is code only, it would probably be better to have a fair bit of > text along with that, but I think that pushing the text back onto the Drill > web site itself might be a good plan. > > Where would you like to start? > > > > On Sat, Aug 29, 2015 at 4:16 PM, Edmon Begoli <[email protected] > <javascript:;>> wrote: > > > Hey folks, > > > > I think that Drill project could benefit from a developers cookbook-like > > material. > > > > I am saying this because, as a newcomer contributor, I feel like I need > > one - how to get to code, how to test, what are the living standards, > etc. > > > > There is stuff out here, some is little bit dated, some is not > > accurate, and I figuring it out, but I think it would help the overall > > contribution process if there would be a living cookbook with very > precise > > and clear How Tos. I feel like I will need to prepare one anyway if I am > to > > bring any of my team members to pitch in some help. > > > > What do you think? > > > > If you think this makes sense, what would, in your opinion, be the best > way > > to get started on the cookbook? > > > > It would be also good to do this a little bit sooner than having to wait > > for the product release cycle. > > > > I would be happy to record and publish my own notes, if that makes > sense. > > > > Thanks, > > Edmon > > >
