ctubbsii commented on code in PR #382: URL: https://github.com/apache/accumulo-website/pull/382#discussion_r1159033794
########## pages/contact-us.md: ########## @@ -54,6 +54,11 @@ follow discussions as they happen. Drop by and chat about Accumulo at the [#accumulo][accumulo-channel] channel on the [ASF Slack workspace][asf-slack]. Join using this [invite link][slack-invite]. If you have trouble joining, email `[email protected]` for an invite. +## Confluence + +The [Accumulo Confluence Space][confluence] provides a collaboration space for design documents. If you would like write +access, please send a request to `[email protected]` with your Confluence username. + Review Comment: > Added a reference on how-to-contribute and a link back to the contact-us. > > Being that the Confluence space is a communications channel and one way to interact with the Accumulo community, the contact-us page seems a logical place to look if someone is searching for a way to interact with the community. The Confluence space isn't a way for people to contact us, though. The contact us page shows ways to contact us, not ways to contribute to the community. Similarly, GitHub is a communication channel... but it's not really a way for people to contact us. That's why we mention it in the how to contribute page, but not on the contact us page (except by linking to the How To contribute page). > > The intention of this PR was to raise the visibility of the Confluence space. The refresh of the `/contribute` page can be done as a separate effort. One of the primary arguments used to justify the need for Confluence, as opposed to using more visible space of using the website, was (among other reasons), that we needed a space that was explicitly **less** visible to end users, for us developers to collaborate on things that we weren't ready to publish more widely. If that's still true, and I see no reason to believe it isn't, then we should not be trying to raise visibility of it to people who are not engaged in Accumulo development. It should be treated as a developer resource, and not a means to communicate with us more generally. I agree that the `/contribute` page improvement efforts could be done separately. My point in bringing it up here was that there is value in consolidating the developer resources. Confluence is a developer resource, and our best page for consolidated developer resource information is our "How To Contribute" page. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
