[
https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653706#comment-16653706
]
Scott Wegner commented on BEAM-5741:
------------------------------------
Thanks for the context [~melap], I'm glad to hear so much previous thought has
gone into this. I trust your expertise and the design decisions that have
already been made.
This bug jumps to a solution, but here's the problem we were trying to solve:
[~rohdesam] was going through the Contributor Guide as a new contributor, and
there were many places where he had questions. One piece of feedback was that
he couldn't find any details on how to ask for help.
There are scattered mentions in the Contributor Guide about the dev@ list and
Slack, but it's easy to miss if you're down deep in the page. The problem is
solved if new contributors understand the convention that "Community" includes
how to reach out, but in this case we didn't.
So maybe an alternative solution would be a dedicated heading at the top of the
Contributor Guide for how to get help. Something like:
h2. Finding Help
If you find any issues with this guide or have questions that aren't answered,
please check the <FAQ> or <reach out to the Beam community>.
> Move "Contact Us" to a top-level link
> -------------------------------------
>
> Key: BEAM-5741
> URL: https://issues.apache.org/jira/browse/BEAM-5741
> Project: Beam
> Issue Type: Sub-task
> Components: website
> Reporter: Scott Wegner
> Priority: Major
>
> It should be very easy to figure out how to get in touch with community.
> "Contact Us" should be a top-level link on the page.
> The page can also be improved with:
> * Some basic text on how to use subscribe / unsubscribe links
> * Recommendations on how to use various communications channels (Slack for
> quick questions, dev@ for longer conversations. And all decisions should make
> it back to dev@)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
