Hey Ilya! That's correct - Heupr (currently) sits at the very "front" of the issue triage process. It's there to make sure that every issue is at least seen by a contributor. From what we've seen, it appears to help increase activity/awareness.
And it's funny you mention labeling because this is the #1 most requested/mentioned feature that projects are interested in. As a result, Mike and I have decided to move forward with building it out as a full feature for Heupr! As an initial idea (rough sketch at this point), we're considering having users group issue labels together by type (e.g. which part of the code the issue address) into buckets. Heupr then selects the best label from each bucket (e.g. front-end) per new issue raised. How would you see a labeling function looking and operating in the context of ESLint? We're still in the design phase so ideas are very welcome! Thank you very much for your feedback/thoughts - it's super helpful! Best, John On Wed, Dec 6, 2017 at 9:42 PM, Ilya Volodin <[email protected]> wrote: > Hi John, > > > > That sounds like a very interesting idea. Based on your site’s > description, it sounds like most of the work your application can do > revolves around issue assignment. I’m not sure that would work in our case, > because we tend to not assign issues/PRs and handle them on first come, > first serve bases. Can your application handle language analysis and > labeling? Could you also provide a bit more information about what’s > possible with your application? > > > > Thanks, > > > > Ilya Volodin > > > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *John Forstmeier > *Sent:* Wednesday, December 6, 2017 9:31 PM > *To:* [email protected] > *Subject:* [ESLint] Re: ESLint issue triage > > > > Hi everyone! > > > > I'm John and me and my co-creator Mike have built an automated GitHub > Issue assignment service called Heupr <https://heupr.io/>. It helps very > active repositories like yours (with 200+ open issues and 500+ > contributors) coordinate software maintenance and feature creation. One of > our users, and a past ESLint contributor, recommended that we reach out to > you and offer our services. We're actively looking to help more projects > improve how they coordinate bug fixes and develop new features. What can we > do for you and ESLint? > > > > Best, > > John > > > > On Wed, Dec 6, 2017 at 9:25 PM, John Forstmeier <[email protected]> > wrote: > > Hi everyone! > > > > I'm John and me and my co-creator Mike have built an automated GitHub > Issue assignment service called Heupr <https://heupr.io/>. It helps very > active repositories like yours (with 200+ open issues and 500+ > contributors) coordinate software maintenance and feature creation. One of > our users, and a past ESLint contributor, recommended that we reach out to > you and offer our services. We're actively looking to help more projects > improve how they coordinate bug fixes and develop new features. What can we > do for you and ESLint? > > > > Best, > > John > > > > -- > You received this message because you are subscribed to the Google Groups > "ESLint" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
