[Website] Update Community page for GitHub Discussions#630
[Website] Update Community page for GitHub Discussions#630amoeba merged 9 commits intoapache:mainfrom
Conversation
community.md
Outdated
|
|
||
| ### GitHub Issues | ||
|
|
||
| We use [GitHub Issues](https://github.com/apache/arrow/issues) as a way to ask questions and engage with the Arrow developer |
There was a problem hiding this comment.
'as a way to ask questions' seems redundant now that we have discussions?
There was a problem hiding this comment.
Should we add the GitHub issues for all repositories (arrow-java, arrow-go, ...) ?
There was a problem hiding this comment.
I think we should be more clear here. We should redirect users to ask questions to GitHub Discussions. As a new user with a question if I see three options I still would have no idea what is the preferred way. The current phrasing doesn't help in my opinion.
We have suggested in the past to redirect user questions to the mailing list when they were opened as issues. I feel this phrase was already outdated. I would say something in the lines:
We use GitHub Issues to track the queue of development work. Bugs and feature requests are welcome. For usage type questions we have GitHub Discussions and might redirect usage type issues to open the question there.
There was a problem hiding this comment.
and might redirect usage type issues to open the question there.
FWIW, if someone opens an issue that is clearly a usage question, we don't have to ask to open the question as a discussion instead, we (maintainers) should be able to click a button to convert the issue into a discussion/
There was a problem hiding this comment.
@jbonofre I think you're right. I'll change things around a bit.
There was a problem hiding this comment.
New text in ac8107b which points people to our repos and their issues/discussions.
community.md
Outdated
|
|
||
| ### GitHub Issues | ||
|
|
||
| We use [GitHub Issues](https://github.com/apache/arrow/issues) as a way to ask questions and engage with the Arrow developer |
There was a problem hiding this comment.
Should we add the GitHub issues for all repositories (arrow-java, arrow-go, ...) ?
Co-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
|
Thanks for the reviews so far. I think @jbonofre's point about directing users to the other repos was a good one so I overhauled the text in ac8107b. cc @jbonofre @raulcd @assignUser |
Co-authored-by: Ian Cook <ianmcook@gmail.com>
I found two things out here: 1. %includes require we use inline HTML here to get the correct final HTML 2. We don't want a final trailing newline in %include templates or things go screwy with word breaks
|
Here's the latest local preview with my recent fixes,
cc @ianmcook |
|
Thanks all for the reviews. @jbonofre since you didn't get a chance for another review, let me know if you have any feedback and we can open another PR. |
|
@amoeba i will do a quick pass but it sounds good ;) thanks ! |
|
FYI, I've opened this issue on arrow-java to enable GitHub discussions to |
8 participants
Note this reorders GitHub Issues and Discussions to be above Stack Overflow as SO seems to be significantly less popular now than it used to be.
Closes #629.