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

Edit issue reporting guides #3006

Merged
merged 1 commit into from
Sep 14, 2016

Conversation

RichardLitt
Copy link
Member

I think this language makes it a bit more clear how we use issues in this repository.

License: MIT
Signed-off-by: Richard Littauer richard.littauer@gmail.com

@RichardLitt RichardLitt added topic/docs-ipfs Topic docs-ipfs need/review Needs a review labels Jul 28, 2016
@ghost
Copy link

ghost commented Jul 28, 2016

Good call! Do you think we should also change the issue category examples? Maybe remove meta and question, and add performance, crash, proposal?

@RichardLitt
Copy link
Member Author

I think that would be a good idea! question is vague and I don't think it is useful. @em-ly @whyrusleeping thoughts?

@whyrusleeping
Copy link
Member

whyrusleeping commented Aug 25, 2016

LGTM

actually, on second though. Lets use this as an opportunity to fix the issue template, shall we?

@RichardLitt
Copy link
Member Author

Yes! I was thinking yesterday circling back to this.

Do you have any specific pain points you want to bring up?

@whyrusleeping
Copy link
Member

We should put most of the 'help' text in comments, so it doesnt wind up in the actual issue. And i think we should also reverse the "priority" numbers. They are the opposite of what is standard.

Let me see if i can find that other issue where i made a few suggestions...

@jbenet
Copy link
Member

jbenet commented Aug 26, 2016

Yes +1 to reverse prios.
On Thu, Aug 25, 2016 at 14:54 Jeromy Johnson notifications@github.com
wrote:

We should put most of the 'help' text in comments, so it doesnt wind up in
the actual issue. And i think we should also reverse the "priority"
numbers. They are the opposite of what is standard.

Let me see if i can find that other issue where i made a few suggestions...


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3006 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIcoRXKitLRqv8LQFyzUzHsLHTYAkM0ks5qjeTwgaJpZM4JXfv1
.

@whyrusleeping
Copy link
Member

@RichardLitt the discussion was here: #2786 (comment)

Mostly just want to use comments to hide all the 'help text' from the actual issue.

@RichardLitt
Copy link
Member Author

SGTM. Will make a PR.

@RichardLitt RichardLitt force-pushed the feature/edit-issue-reporting-guides branch from 518790c to 7662213 Compare September 1, 2016 15:07
License: MIT
Signed-off-by: Richard Littauer <richard.littauer@gmail.com>
@RichardLitt RichardLitt force-pushed the feature/edit-issue-reporting-guides branch from 7662213 to c05e225 Compare September 1, 2016 15:08
@RichardLitt
Copy link
Member Author

@whyrusleeping Take a look at the edits?

Copy link
Member

@whyrusleeping whyrusleeping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@whyrusleeping whyrusleeping merged commit 98fdffa into master Sep 14, 2016
@whyrusleeping whyrusleeping deleted the feature/edit-issue-reporting-guides branch September 14, 2016 19:57
@whyrusleeping whyrusleeping removed the status/in-progress In progress label Sep 14, 2016
@ghost ghost mentioned this pull request Dec 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/review Needs a review topic/docs-ipfs Topic docs-ipfs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants