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é <j...@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 <owenzhang1...@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
>

Reply via email to