On 2017-11-30 09:40, Graham Wallis <[email protected]> wrote:
> It would be raising a JIRA for the documentation errors you spotted and Andrew - Some of the core documentation is currently in the build (ie the top level README.me, docs/*, and some module level documentation, javadoc), whilst more general guides, architecture sits in the Atlas wiki. If you want to contribute there, ask & one of the community leads can give you access to edit/create pages > With regard to your question about raising a PR, the way the Atlas > community works is by submitting a patch to the Review Board Tool, which > is then reviewed and committed. This link describes the process: > https://cwiki.apache.org/confluence/display/ATLAS/Using+Git+with+Atlas Also create the JIRA first... anyone can signup and create, but if you want to assign it to yourself to actually work on it (and submit a patch view the review tool) then ask for contributor access here too. > I think a slack channel would be good - I don't think there is one > already. I wonder if apache offer any infrastructure for this? Whilst anyone can setup a free slack team, discussions will roll-off and disappear unless it's premium. Also in apache I think people really like ensuring there's a mail archive of anything, so if slack were to be used, a plugin to post to a new mailing list would be preferred too I think (I actually use slack a fair bit myself)
