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

Issue triaging #50

Closed
boennemann opened this Issue Jul 10, 2014 · 20 comments

Comments

Projects
None yet
6 participants
@boennemann
Member

boennemann commented Jul 10, 2014

There are currently over 300 open issues across repos and more are opened every day. I wondered if it makes sense to put a triaging process in place, so that we can get them structured and closed/fixed faster.

(As always) the Angular team has something in place already and it's applicable to Hoodie with a few adaptions.
https://github.com/angular/angular.js/blob/master/TRIAGING.md

Thoughts, suggestions?

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 16, 2014

ping @hoodiehq/owners

@janl

This comment has been minimized.

Member

janl commented Jul 16, 2014

I’m major +1, we just need someone to lead this.

@svnlto

This comment has been minimized.

Member

svnlto commented Jul 16, 2014

Familiarising myself with the angular process..

@gr2m

This comment has been minimized.

Member

gr2m commented Jul 16, 2014

I like this a lot. Especially how they place the Code Of Conduct right in the process, and provide examples for good answers. I think we could adjust it for our needs (esp. reduce the amount of labels to a minimum, and add new as needed), but I wouldn't mind to start by referencing the Angular one, and create one for ourselves later.

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 16, 2014

@janl

This comment has been minimized.

Member

janl commented Jul 16, 2014

@davidpfahler

This comment has been minimized.

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 18, 2014

I rewrote the history of the gist so that it contains a diff to the original version now. Also I removed all mentions of security.

Please continue to discuss on this issue only (:

@janl

This comment has been minimized.

Member

janl commented Jul 18, 2014

👍

@davidpfahler

This comment has been minimized.

davidpfahler commented Jul 18, 2014

One thing we might want to add is an explanation how one can help with triaging issues. The document assumes that not just core members will help triage issues ("If in doubt, ask a core team member what to do."). Is this intentional? I think triaging can be a great, low friction way to help hoodie. So if this is your intention, how can other contributors become a "triager"?

@janl

This comment has been minimized.

Member

janl commented Jul 18, 2014

+100 to @davidpfahler’s suggestion :)

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 18, 2014

Issue owners and users with push access can edit an issue.

-- GitHub API

Create a "Issue Triaging" Team with access to all the repos. That's it – at least from a technical standpoint.

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 18, 2014

Oh and btw automatically creating all the above mentioned labels should be as easy as https://developer.github.com/v3/issues/labels/#create-a-label

@davidpfahler

This comment has been minimized.

davidpfahler commented Jul 19, 2014

OK, 4 things left to complete this:

  1. Add note to CONTRIBUTING.md and TRIAGING.md how people can join the triaging team
  2. Create triaging team on GitHub
  3. Sync TRIAGING.md to all repos
  4. add labels to all repos (via gh api)

Open question is, what the process will be to add people to triaging. Should they ask in the IRC chat or send an email? What would be the appropriate way to contact Hoodie that is both natural to the processes Hoodie is using now (like IRC) but also low barrier to entry (not like IRC)?

As soon as you tell me the answer to that question, I'll write the missing one or two sentences for CONTRIBUTING.md and TRIAGING.md. @boennemann can then take action on 2., 3. and 4., I suppose.

@janl

This comment has been minimized.

Member

janl commented Jul 19, 2014

I’d say keep it all in GitHub and have people open an issue to ask for being added to the triaging team.

@davidpfahler

This comment has been minimized.

davidpfahler commented Jul 19, 2014

@janl Is that on the repository they want to be triaging issues for or on a separate repo (triaging repo?). We need a link people can click and which takes them to the right place where they can apply for triaging access. Where would this link point to?

@janl

This comment has been minimized.

Member

janl commented Jul 19, 2014

doesn’t matter, pick one :)

@davidpfahler

This comment has been minimized.

davidpfahler commented Jul 19, 2014

@boennemann Please change first paragraph (if you agree) of TRIAGING.md to:

This document illustrates the steps the Hoodie community is taking to triage issues. The labels are used later on for planning releases. If you want to help Hoodie by sorting issues, please leave a comment here asking to join the triaging team.

Can you please complete the other three steps as well? Thanks in advance.

Also, I'd like to join the triaging team ;)

@boennemann boennemann referenced this issue Jul 19, 2014

Merged

Triaging #3

boennemann added a commit to hoodiehq-archive/hoodie-dotfiles that referenced this issue Jul 19, 2014

@lenareinhard

This comment has been minimized.

lenareinhard commented Jul 19, 2014

As discussed before, could we put including a Mary Poppins integration

  • on the to do list
  • as soon as integrated, into the triaging file?

Rest is +1 from my side.

@boennemann

This comment has been minimized.

Member

boennemann commented Jul 20, 2014

@ffffux For what would you like to use Mary Poppins? CLA does not apply. When it comes to commit message conventions we could first see how well contributors adopt the conventions.

+1 for MP when there is a use case (:

Note: Closing this issue as the process is now in place

@boennemann boennemann closed this Jul 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment