I will also have a look at it. Wondering though if it shouldn't replace the existing operator developer guide?
http://apex.apache.org/docs/apex/operator_development/ For the contributing guidelines on the web site, maybe it is better to have a shorter checklist that gives folks the necessary pointers w/o too much detail? http://apex.apache.org/contributing.html Thomas On Tue, Jul 5, 2016 at 1:07 PM, Munagala Ramanath <[email protected]> wrote: > Pramod, I'll take a look this evening if you can wait that long. > Ram > On Jul 5, 2016 11:24 AM, "Pramod Immaneni" <[email protected]> wrote: > > > I received some feedback. Any other comments before adding these > guidelines > > to the project. > > > > Thanks > > > > On Fri, Jun 17, 2016 at 3:12 PM, Pramod Immaneni <[email protected] > > > > wrote: > > > > > Hi everyone, > > > > > > I wanted to create a set of guidelines that would help folks that want > to > > > contribute to Malhar. The goal is that by following these guidelines > the > > > contributions will be assured a certain level of quality as the > different > > > aspects to consider, common missteps and mistakes will be taken care of > > > which in turn would also make the review process smoother by reducing > the > > > number of review iterations before the contribution gets merged. I > tried > > to > > > capture as much information as I thought would help developers towards > > this > > > goal based on past experience and exposure, in a document. > > > > > > Please go through it and provide your feedback, it will be greatly > > > appreciated. I will go through your comments and incorporate any > > necessary > > > changes. After that I hope this document will become a living document > as > > > part of the contribution guidelines and evolve with the times. > > > > > > > > > > > > https://drive.google.com/open?id=1WjbaIogVtMDQwbvxTlQxrFqUbK9D75bk98asW9e5OxA > > > > > > Thanks > > > > > >
