Issue triaging

[boennemann]

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]

ping @hoodiehq/owners

[janl]

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

[svnlto]

Familiarising myself with the angular process..

[gr2m]

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]

Made some adaptations:
https://gist.github.com/boennemann/f4e3785455c488baa434

[janl]

Comment https://gist.github.com/boennemann/f4e3785455c488baa434#

[davidpfahler]

Comment https://gist.github.com/boennemann/f4e3785455c488baa434#comment-1265185

[boennemann]

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]

👍

[davidpfahler]

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]

+100 to @davidpfahler’s suggestion :)

[boennemann]

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]

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]

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]

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

[davidpfahler]

@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]

doesn’t matter, pick one :)

[davidpfahler]

@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 ;)

[lenareinhard]

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]

@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