+1 Taking a proven process is a great idea.
Thanks On Fri, 12 Jun 2015 at 22:25 William Markito <wmark...@pivotal.io> wrote: > ++1 > > These are all pretty awesome ideas and I'd say a must have for a sane and > healthy build/release/community process. > > Thanks a lot. > > > On Jun 12, 2015, at 6:36 PM, jun aoki <ja...@apache.org> wrote: > > > > Hi Geode community > > > > My name is Jun Aoki and I work for Pivotal's Ambari project, and am > super excited to contribute to Geode! > > > > I'd like to propose a few things about contribution process. > > > > The Geode community should have a clear cut process to open up to > anybody who are interested in contributing to Geode. > > e.g. Apache Ambari community has adopted a contribution process > > https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute > > Ambari's workflow > > > https://docs.google.com/document/d/1hz7qjGKkNeckMibEs67ZmAa2kxjie0zkG6H_IiC2RgA/edit > > > > > > > > I am listing a few tasks that can be Jira tickets of Geode. > > - test-patch CI job to make sure submitted patches to Geode jira has > minimum quality (Apache RAT pass, being able to compile, unit test added, > etc) > > - commit CI job to make sure master branch passes the unit test upon > patch commits. > > - Geode build environment within Docker to enable anybody and any OS and > any environment can build Geode as long as there is Docker. > > > > e.g. jobs serve for ambari > > https://builds.apache.org/view/A-D/view/Ambari/ > > > > > > Please let me know if my proposals are good for the Geode community, > then I will make tickets and will work on them. > > > > - jun > > >
