docs(contribution): add Feedback/Issues #1338
Conversation
soniasingla
requested review from
Pantani,
fadeev,
ilgooz and
lumtis
as code owners
soniasingla
changed the title
soniasingla
changed the title
soniasingla
changed the title
fadeev
changed the title
ilgooz
changed the title
There was a problem hiding this comment.
@soniasingla thank you for being a part of our team and thanks for this PR. I applied our style standards and made some editorial suggestions... lmk if I can explain or provide more context. Carry on, teammate!
contributing.md
Outdated
| Thank you for your contribution! | ||
|
|
||
| ## Opening pull requests | ||
| ## Feedback / Issues |
There was a problem hiding this comment.
| ## Feedback / Issues | |
| ## Providing feedback |
There was a problem hiding this comment.
@soniasingla (it's great to see you here, thanks for this PR!) let's follow the model of using active verbs for headings
There was a problem hiding this comment.
@barriebyron thanks for the great feedback, i have updated the PR, feel free to take a look! 🙌
There was a problem hiding this comment.
We welcome all contributions, and this clarity will help attract them. Thanks @soniasingla
| ## Opening pull requests | ||
| ## Providing Feedback | ||
|
|
||
| * Before you open an issue, do a web search, and check for [existing open and closed GitHub Issues](https://github.com/tendermint/starport/issues) to see if your question has already been asked and answered. If you find a relevant topic, you can comment on that issue. |
There was a problem hiding this comment.
What about navigating users to the Discussions page instead and only use issues for direct bug reports and feature requests?
So, basially, we can convert these three bullets in two, first one saying that "please open a discussion or comment to an existent one for your questions, feedbacks, ideas or use the Discord channel for quick responses."
Second, "please create issues from this link to report a bug or ask for a feature request."
There was a problem hiding this comment.
@ilgooz Discussions pages are great alternative but our large user-base/community is over Discord, it supports group voice channels if needed + Screen sharing available in groups!
There was a problem hiding this comment.
IIUC, the Discussions page provides a repo-based home... I like @ilgooz's proposal. I had forgotten about using Discussions. @soniasingla wdyt about sending folks from Discord to Discussions? (I seem to remember a conversation about centralizing feedback in GitHub). In this case, @ilgooz suggestions make sense.
I was just reading up on Discussions https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/about-discussions
So in this case, it depends on the dev team and how they want to capture the user feedback. Big opportunities!
There was a problem hiding this comment.
We'll think about Discord vs alternatives later. Right now Discord has traction, so we're using that. If people will start using discussions (it's open for them now), we might reconsider.
There was a problem hiding this comment.
Sending users from Discord to GitHub discussions and issues might be the direction that @fadeev and team prefer? A larger discussion on workflow can define the content here.
| ## Opening pull requests | ||
| ## Providing Feedback | ||
|
|
||
| * Before you open an issue, do a web search, and check for [existing open and closed GitHub Issues](https://github.com/tendermint/starport/issues) to see if your question has already been asked and answered. If you find a relevant topic, you can comment on that issue. |
There was a problem hiding this comment.
IIUC, the Discussions page provides a repo-based home... I like @ilgooz's proposal. I had forgotten about using Discussions. @soniasingla wdyt about sending folks from Discord to Discussions? (I seem to remember a conversation about centralizing feedback in GitHub). In this case, @ilgooz suggestions make sense.
I was just reading up on Discussions https://docs.github.com/en/discussions/collaborating-with-your-community-using-discussions/about-discussions
So in this case, it depends on the dev team and how they want to capture the user feedback. Big opportunities!
…1338) Co-authored-by: Denis Fadeev <denis@fadeev.org>
5 participants
Add a section about
Feedback/Issuesin the Contributing File 🤗