Add a "Submit Issue" page#139
Conversation
ebouchut
force-pushed
the
ebouchut/refactor/submit_issue
branch
from
10fef5f to
037f399
Compare
Goal: Users should ask for help on FB and Discord first
ebouchut
force-pushed
the
ebouchut/refactor/submit_issue
branch
from
037f399 to
7f62d1f
Compare
- Reorganize and renamed the section: Where to Find Help - Add checkboxes (only a visual clue, not persisted) - Add admonitions: Help the Community help you
to the "Submit an Issue" page
ebouchut
force-pushed
the
ebouchut/refactor/submit_issue
branch
2 times, most recently
from
6f2189f to
04f6fcc
Compare
ebouchut
force-pushed
the
ebouchut/refactor/submit_issue
branch
from
04f6fcc to
e6110d0
Compare
|
@marionbarker would you please take a look and let me know if it meets the initial request. |
Fix list indentation
"using Trio"/"building Trio"
marionbarker
left a comment
marionbarker
left a comment
There was a problem hiding this comment.
Overall Comment
I put in some specific ideas about rearranging particular items.
In addition, I suggest you reorganize to have separate section for Building Help and Using Help.
In the using help - in addition to posting on FB / Discord, they may be asked to post a formal GitHub issue. They need a brief set of instructions on how to do that with a link.
| - [Trio Settings](https://discord.com/channels/1020905149037813862/1239982177190678549) | ||
|
|
||
| - [ ] **Avoid posting the same question in multiple groups.** | ||
| Many mentors follow several communities, and cross-posting can lead to confusion. Only try another group if you've received no replies after several hours. |
There was a problem hiding this comment.
I would modify the several hours. Perhaps, "Even if you feel your situation cannot wait, give the mentors several hours to respond. Most questions get an answer the same day."
| Please, do **not** send the same message on multiple sites/channels. | ||
| Our volunteers monitor multiple sites. | ||
|
|
||
| - [ ] If your **question hasn’t been answered** by checking *TrioDocs* or browsing the *Featured posts* in the Facebook group, go ahead and **post your question**. |
There was a problem hiding this comment.
I think lines 32 through 38 belong in the details in How to Ask for Help.
The details currently in How to Ask for Help are specifically about asking for Build Help - and seem to be redundant with some details in What to Share . . .
|
|
||
| - [ ] Once your **issue is resolved**: | ||
| - [ ] **Leave** your **post online** so it can help others | ||
| - [ ] **Edit** your **original message** to **include** the word **RESOLVED** at the beginning. |
There was a problem hiding this comment.
IMO changing the post online so the original comment with resolved is a Facebook only request.
|
I initially added checkboxes so that users could mark off the steps they'd completed. |
and not spam every support channel.
… Facebook support request
…klist Details: App version, CGM, pump
3 participants
This PR replaces the link to submit an issue on GitHub with a dedicated page.
The purpose of this page is to encourage users to ask their questions on Facebook and Discord first, and only submit a GitHub issue if the Trio team advises them to do so.
Source
EDIT: Disregard this update, to re-trigger the PR-check that was stuck.