Hi Xintong,

yes, such labels would make a lot of sense. I added a sentence to the
document.

Thanks,

Konstantin

On Mon, Mar 1, 2021 at 8:51 AM Xintong Song <tonysong...@gmail.com> wrote:

> Thanks for driving this discussion, Konstantin.
>
> I like the idea of having a bot reminding reporter/assignee/watchers about
> inactive tickets and if needed downgrade/close them automatically.
>
> My two cents:
> We may have labels like "downgraded-by-bot" / "closed-by-bot", so that it's
> easier to filter and review tickets updated by the bot.
> We may want to review such tickets (e.g., monthly) in case a valid ticket
> failed to draw the attention of relevant committers and the reporter
> doesn't know who to ping.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Sat, Feb 27, 2021 at 1:37 AM Till Rohrmann <trohrm...@apache.org>
> wrote:
>
> > Thanks for starting this discussion Konstantin. I like your proposal and
> > also the idea of automating the tedious parts of it via a bot.
> >
> > Cheers,
> > Till
> >
> > On Fri, Feb 26, 2021 at 4:17 PM Konstantin Knauf <kna...@apache.org>
> > wrote:
> >
> > > Dear Flink Community,
> > >
> > > I would like to start a discussion on improving and to some extent
> simply
> > > defining the way we work with Jira. Some aspects have been discussed a
> > > while back [1], but I would like to go a bit beyond that with the
> > following
> > > goals in mind:
> > >
> > >
> > >    -
> > >
> > >    clearer communication and expectation management with the community
> > >    -
> > >
> > >       a user or contributor should be able to judge the urgency of a
> > ticket
> > >       by its priority
> > >       -
> > >
> > >       if a ticket is assigned to someone the expectation that someone
> is
> > >       working on it should hold
> > >       -
> > >
> > >    generally reduce noise in Jira
> > >    -
> > >
> > >    reduce overhead of committers to ask about status updates of
> > >    contributions or bug reports
> > >    -
> > >
> > >       “Are you still working on this?”
> > >       -
> > >
> > >       “Are you still interested in this?”
> > >       -
> > >
> > >       “Does this still happen on Flink 1.x?”
> > >       -
> > >
> > >       “Are you still experiencing this issue?”
> > >       -
> > >
> > >       “What is the status of the implementation”?
> > >       -
> > >
> > >    while still encouraging users to add new tickets and to leave
> feedback
> > >    about existing tickets
> > >
> > >
> > > Please see the full proposal here:
> > >
> > >
> >
> https://docs.google.com/document/d/19VmykDSn4BHgsCNTXtN89R7xea8e3cUIl-uivW8L6W8/edit#
> > > .
> > >
> > > The idea would be to discuss this proposal in this thread. If we come
> to
> > a
> > > conclusion, I'd document the proposal in the wiki [2] and we would then
> > > vote on it (approval by "Lazy Majority").
> > >
> > > Cheers,
> > >
> > > Konstantin
> > >
> > > [1]
> > >
> > >
> >
> https://lists.apache.org/thread.html/rd34fb695d371c2bf0cbd1696ce190bac35dd78f29edd8c60d0c7ee71%40%3Cdev.flink.apache.org%3E
> > > [2]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLINK+Jira+field+definitions
> > >
> > > --
> > >
> > > Konstantin Knauf
> > >
> > > https://twitter.com/snntrable
> > >
> > > https://github.com/knaufk
> > >
> >
>


-- 

Konstantin Knauf

https://twitter.com/snntrable

https://github.com/knaufk

Reply via email to