Hi Ilya! Just wanted to touch base - we're back to work after the holidays on the automated labeling feature and have made a lot of progress. In a couple days we'll be rolling out a beta and following up shortly with a "post-beta" for a larger audience; we'll be sure to keep you all in the loop as we move forward and we'd love your input and feedback.
Is there anything I can address in the meantime? Happy 2018! Best, John On Mon, Dec 11, 2017 at 8:18 PM, John Forstmeier <[email protected]> wrote: > Hi Ilya, > > Awesome feedback! This is super helpful and we'll be using it as part of > our framework for this feature. We'll likely do a pre-launch rollout so > feel free to subscribe to our Upcoming page here > <https://www.producthunt.com/upcoming/heupr> for the announcement. > Otherwise, we'll reach out to you here when it is up and running. > > We made a lot of progress this weekend so we might actually have a > labeling feature up and running in MVP pretty soon. > > Thanks again! > > Best, > John > > On Dec 7, 2017 10:22 PM, "Ilya Volodin" <[email protected]> wrote: > >> Hi Ilya, >> >> Awesome feedback! This is super helpful and we'll be using it as part of >> our framework for this feature. We'll likely do a pre-launch rollout so >> feel free to subscribe to our Upcoming page here >> <https://www.producthunt.com/upcoming/heupr> for the announcement. >> Otherwise, we'll reach out to you here when it is up and running. >> >> We made a lot of progress this weekend so we might actually have a >> labeling feature up and running in MVP pretty soon. >> >> Thanks again! >> >> Best, >> John >> >> On Dec 7, 2017 10:22 PM, "Ilya Volodin" <[email protected]> wrote: >> >>> ESLint’s labels setup is pretty simple. We have “triage” label that is >>> automatically added by our bot on issue creation. Once the issue is triaged >>> it usually falls into 3 different categories “bug”, “enhancement” and >>> “feature”. “Bug” is obvious, “enhancement” is a request for minor >>> addition/change of the existing behavior (for example, a new option in one >>> of our rules), and “feature” is a feature request, which is basically a >>> brand-new functionality. We also have labels that indicate area of the >>> project that this issue is target, such as “rules”, “core”, “formatters”, >>> “build” and “documentation”. That would cover 98% of our issues. I’m not >>> sure how this could be automated. I think the only real way to do that >>> would be to train a neural network on existing issues and see if it will be >>> able to identify at least first label group. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Ilya Volodin >>> >>> >>> >>> *From:* John Forstmeier [mailto:[email protected]] >>> *Sent:* Wednesday, December 6, 2017 11:09 PM >>> *To:* Ilya Volodin <[email protected]> >>> *Cc:* [email protected] >>> *Subject:* Re: [ESLint] Re: ESLint issue triage >>> >>> >>> >>> 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.
