I agree with David. Although slack does have advantages over email - particularly in terms of managing channels for different topics, I would be reluctant to add it as another comms mechanism if all of the Slack messages were not automatically sent to the dev list.
All the best Mandy ___________________________________________ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: [email protected] LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - [email protected] From: David Radley <[email protected]> To: [email protected] Date: 30/11/2017 11:14 Subject: slack Hi , Having all communication on the dev list means there is one place to look to see how a community is communicating and is the way Apache project are supposed to work. If we start to use slack then we would need to to remember to copy the dev list for any non-trivial communications to ensure the community is communicating openly and healthily, all the best, David. From: "Nigel Jones" <[email protected]> To: <[email protected]> Date: 30/11/2017 10:19 Subject: Re: standalone mode setup 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://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_ATLAS_Using-2BGit-2Bwith-2BAtlas&d=DwIBAw&c=jf_iaSHvJObTbx-siA1ZOg&r=QhpUQPr5YlG95aAgCvZGStEXHg4hBbSYQ9JkRqR_svY&m=hrKzFXBdkHHcNRmufNdh7tRO1yUzxBuZbwe6HcDNvy8&s=My9YkYi38m7K_Pu4cvg3ZvkLRIzGP4D90DNAlE6Jr6A&e= 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) Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
