Skip to content
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

Open
shankari opened this issue Aug 21, 2018 · 12 comments
Open

Do we need to duplicate issue answers into actual docs? #24

shankari opened this issue Aug 21, 2018 · 12 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@shankari
Copy link
Contributor

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:

  • extra work - we don't have a dedicated doc person on staff
  • danger of docs bitrotting/becoming obsolete if people forget to update while with an issue you can always see the timestamp of the last update and know which one is correct
  • docs will get too verbose and confusing if every single possible issue is in the docs

Thoughts?

@shankari shankari added enhancement New feature or request help wanted Extra attention is needed labels Aug 21, 2018
@bz247
Copy link

bz247 commented Aug 21, 2018

Yeah, maybe unless many people have the same problem, it should be okay to only answer them in issues.

@jackcsullivan
Copy link
Contributor

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).

@shankari
Copy link
Contributor Author

shankari commented Aug 21, 2018

in response to #24 (comment), what do you think should be the threshold for many people?

@MetroPietro
Copy link
Contributor

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.

@deepalics0044
Copy link

Yes I agree. I think reflecting on docs can be haphazard, we can look into the issues if some information is required.

@jackcsullivan
Copy link
Contributor

jackcsullivan commented Aug 21, 2018

@shankari 5 seems like a reasonable number.

@shankari
Copy link
Contributor Author

@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.
isaacs/github#9

Any thoughts on how to simulate voting?

@jackcsullivan
Copy link
Contributor

jackcsullivan commented Aug 21, 2018

@shankari we could comment a few numbers and people could thumbs up the ones they like.

@shankari
Copy link
Contributor Author

@jackcsullivan I was talking about voting for issues to highlight that "it was confusing for me and needs to go into the docs"

@bz247
Copy link

bz247 commented Aug 21, 2018

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.

@shankari
Copy link
Contributor Author

@bz247 that sounds like a great idea.
Let's see if others have any comments in the next couple of days, and then we can make the change.
Where should we put the instructions?
docs repository? README?

Also, who wants to do this?

@jackcsullivan
Copy link
Contributor

@shankari Have an issues section under "Contributing" in the main e-mission-docs readme that has instructions for the protocol?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants