I guess I should add a little bit of clarification. * The contribute.groovy page should be a cheat sheet for anyone in the community who wants to make a contribution. * The guidelines.groovy page should be additional information that we would expect committers to know about.
So we should try not to duplicate info on both pages. Also, our build file should be the point of truth for details - this should just be giving hints on relevant bits. Finally, I see doing a release as something separate from above. Cheers, Paul. P.S. we have some old wiki pages which contain info which overlaps some of the above - I might archive them on archive.org and then delete them once this is in shape. On Wed, Mar 11, 2020 at 3:14 PM Paul King <pa...@asert.com.au> wrote: > > Hi everyone, > > To make it easier for developer/committer on-boarding, I thought I would > try to collect some developer guidelines in one spot: > > https://groovy.apache.org/guidelines.html > > Please feel free to add to it or let me know if you think there is a > better way to do it. > > Cheers, Paul. > >
