GitHub issue labels

[Manu Zhang <ow...@gmail.com>]

Hi all,

Currently, a label, one of bug, improvement, proposal and question, is
applied automatically
to an issue if it's created from a template. However, I'm not sure we are
actually making use of those labels. We have questions without answers,
bugs without double checks and improvements without discussions.

Do you think we can send a weekly report of those issues somewhere to get
more attention from the community? I remember @Jean-Baptiste Onofré
<jb...@nanthrax.net> having a similar proposal before.

Thanks,
Manu

Re: GitHub issue labels

[Yufei Gu <fl...@gmail.com>]

 It’s a good idea to send a weekly report. It increases visibility, engages
the community, and helps track progress. Key considerations include keeping
the report concise, and automating the process.

We could categorize issues/PRs with labels. For example, putting the ones
triaged and un-triaged into different buckets. Looking forward to a PR for
the automation part.


Yufei


On Tue, May 28, 2024 at 8:08 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:

> Hi Manu,
>
> You are right: I extracted logic from Apache Kiddle which is a suite
> of tools for collecting, aggregating and visualizing activity in
> projects. I'm starting to use it while reviewing project report during
> board meeting preparation.
>
> I'm busy with revapi/gradle update right now, but I can prepare a PR
> to share the script and integration in GH Action.
>
> Regards
> JB
>
> On Mon, May 27, 2024 at 6:02 PM Manu Zhang <ow...@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > Currently, a label, one of bug, improvement, proposal and question, is
> applied automatically
> > to an issue if it's created from a template. However, I'm not sure we
> are actually making use of those labels. We have questions without answers,
> bugs without double checks and improvements without discussions.
> >
> > Do you think we can send a weekly report of those issues somewhere to
> get more attention from the community? I remember @Jean-Baptiste Onofré
> having a similar proposal before.
> >
> > Thanks,
> > Manu
>

Re: GitHub issue labels

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Manu,

You are right: I extracted logic from Apache Kiddle which is a suite
of tools for collecting, aggregating and visualizing activity in
projects. I'm starting to use it while reviewing project report during
board meeting preparation.

I'm busy with revapi/gradle update right now, but I can prepare a PR
to share the script and integration in GH Action.

Regards
JB

On Mon, May 27, 2024 at 6:02 PM Manu Zhang <ow...@gmail.com> wrote:
>
> Hi all,
>
> Currently, a label, one of bug, improvement, proposal and question, is applied automatically
> to an issue if it's created from a template. However, I'm not sure we are actually making use of those labels. We have questions without answers, bugs without double checks and improvements without discussions.
>
> Do you think we can send a weekly report of those issues somewhere to get more attention from the community? I remember @Jean-Baptiste Onofré having a similar proposal before.
>
> Thanks,
> Manu

Re: GitHub issue labels

[Fokko Driesprong <fo...@apache.org>]

Hey Manu,

I don't explicitly use the labels, but they help me to categorize the
issues mentally. I agree that there is room for improvement as there are
more issues being raised every day.

Other communities also have interesting approaches, such as:

   - Triage label: When a new bug, improvement, proposal, or question is
   being raised it gets a triage label to make sure that someone from the
   community looks at it. Assesses the severity of the issue, assesses the
   effort, etc. After an initial follow-up, the triage label can be removed,
   this can be done by either a committer or someone who has contributor
   rights.
   - Full process: Arrow takes this to the next level and has a full
   process for it: https://github.com/apache/arrow/pulls. There are many
   different issues to indicate the process: awaiting review, awaiting
   committer review, awaiting changes, awaiting change review, and probably a
   few more. For me, this feels a bit too much.

I think it might be good to add a triage label, and this might also be
included in a report. You could also easily see the newest issues by
filtering on this issue.

WDYT?

Kind regards,
Fokko


Op ma 27 mei 2024 om 18:03 schreef Manu Zhang <ow...@gmail.com>:

> Hi all,
>
> Currently, a label, one of bug, improvement, proposal and question, is
> applied automatically
> to an issue if it's created from a template. However, I'm not sure we are
> actually making use of those labels. We have questions without answers,
> bugs without double checks and improvements without discussions.
>
> Do you think we can send a weekly report of those issues somewhere to get
> more attention from the community? I remember @Jean-Baptiste Onofré
> <jb...@nanthrax.net> having a similar proposal before.
>
> Thanks,
> Manu
>