I would be happy to keep track of all the developer docs. To extend what we propose, should we discuss, form and document a standard development cycle to better the code quality and make people easy to join on new stuff? So every one can follow the standard when developing new features or fixing bugs.
Best, Hao On Thu, Nov 12, 2015 at 5:59 PM, Sravya Tirukkovalur <[email protected]> wrote: > Notes from the call: > 1. HDFS Sentry sync bug fixes and improvement jiras. > Discussed about SENTRY-953, SENTRY-954, SENTRY-957, SENTRY-945 > 2. Hive authV2 > Discussed the motivation. Feature branch is ready to be reviewed > 3. Test and Quality > - We need to make sure all new features have proper documentation: Java > docs for apis, liberal comments on test cases. Developer documentation > which covers design docs, where code lives and test lives. User > documentation and how the feature is used, configurations and recommended > values for the configurations. > Is any one interested in leading this effort? Would be good to have a > champion here. > - Make sure we are running our local e2e tests in a recommended setup to > make sure we catch real problems sooner. > Misc: > - Discussed CacheProvider, needs design review. > > > On Thu, Nov 12, 2015 at 10:42 AM, Sravya Tirukkovalur <[email protected] > > > wrote: > > > Hi all, > > > > We have our 1st hangout today. And here are the topics I propose. > > > > 1. HDFS Sentry sync bug fixes and improvement jiras. (5 mins) > > 2. Hive authV2 (5 mins) > > 3. Test and Quality(5 mins) > > > > I was thinking we can do introductions first 5 mins and we can leave 10 > > mins at the end for unstructured discussions. Also, feel free to respond > to > > this thread if there is any thing else you would like to discuss. > > > > Regards, > > -- > > Sravya Tirukkovalur > > > > > > -- > Sravya Tirukkovalur >
