-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do we need to duplicate issue answers into actual docs? #24
Comments
Yeah, maybe unless many people have the same problem, it should be okay to only answer them in issues. |
Agree that we do not need to reflect it in "docs" as long as it is explicit somewhere in the readme that any users having issues should check the issues tab in the repo (both open and closed issues). |
in response to #24 (comment), what do you think should be the threshold for many people? |
I agree. However when left in Issues, please note the keywords needed for us to search for the solutions to the problems on our own. RTFM is not sufficient when there are several hundred online "manuals" available for trying to solve questions. |
Yes I agree. I think reflecting on docs can be haphazard, we can look into the issues if some information is required. |
@shankari 5 seems like a reasonable number. |
@jackcsullivan hm and maybe we can have people vote on confusing issues. Hm, it looks like voting is a frequently requested feature of github but doesn't exist yet. Any thoughts on how to simulate voting? |
@shankari we could comment a few numbers and people could thumbs up the ones they like. |
@jackcsullivan I was talking about voting for issues to highlight that "it was confusing for me and needs to go into the docs" |
Or you can upvote issues (emoji on the top right conner of each comment --> thumb-up). Then on the issues tab, top right conner, sort issues by reactions. This can track the popularity of the issues. |
@bz247 that sounds like a great idea. Also, who wants to do this? |
@shankari Have an issues section under "Contributing" in the main e-mission-docs readme that has instructions for the protocol? |
I propose that if an issue is answered, then unless it is super general, we do not need to reflect it back in "docs".
Reasons:
Thoughts?
The text was updated successfully, but these errors were encountered: