[OpenInfra Foundation] Initial setup of OpenStack's Community Metrics Dashboard with Bitergia

[Miguel Ángel Fernández Sánchez]

Dear Jeremy,

The deployment of your instance at https://openstack.biterg.io/ is almost
ready. The data related to Git is already available, but we need to confirm
with you some details about the mailing lists we will be tracking for you.

The platform organizes the different tracked sources into sections named
"Projects" inside the instance. We use this information to have the
possibility of filtering data with another level of granularity (i.e., in
this case, a "Project" could group many mailing lists), hence the question
of which category we should use.

Please note that you will still be able to have all the data aggregated.
Having said that, if you don't want to add those lists under any particular
category, I suggest they can be added inside a section called "General",
which would appear as a fictional project.

This would allow this filtering to work anyway, for instance: if you want
to see the overall view with all the projects (no filters are needed), and
also if you want to obtain a single-project view, you could add this
"General" project as a complimentary filter.

Please, let us know if you agree so we can proceed this way.

That said,
> one thing I've been doing in OpenDev's engagement reports is
> filtering by known nonhuman senders, since we have some high-volume
> mailing lists which pretty much only include posts from automation


Answering this part of your last message, Bitergia Analytics Platform
includes an identity management system that supports marking non-human
accounts (as Bots), so you will be able to filter out this activity if
needed.

Best, Miguel Ángel

Miguel Ángel Fernández

Consultant - Analytics Specialist

TZ: Central European (Madrid) Time

Stay connected! LinkedIn <https://www.linkedin.com/in/mafesan/>

www.bitergia.com | @bitergia <https://es.linkedin.com/company/bitergia>

Software analytics for your peace of mind


El vie, 23 sept 2022 a las 18:46, Jeremy Stanley (<fungi at yuggoth.org>)
escribió:

> On 2022-09-23 10:36:40 +0200 (+0200), Thierry Carrez wrote:
> [...]
> > Not grouping them at all sounds like the preferred solution, since
> > they apply to all projects.
> [...]
>
> That sounds fine to me. I doubt we'll expect to slice-n-dice mailing
> list activity by anything other than senders and times. That said,
> one thing I've been doing in OpenDev's engagement reports is
> filtering by known nonhuman senders, since we have some high-volume
> mailing lists which pretty much only include posts from automation:
>
>
> https://opendev.org/opendev/engagement/src/commit/fd6cd1d/engagement/stats.py#L207-L233
>
> Also, to follow up, the aforementioned structured data list of all
> our ML archives is once again accessible at
> https://lists.opendev.org/archives.yaml and I've added regression
> testing to ensure we don't inadvertently break it in the future.
> --
> Jeremy Stanley
> _______________________________________________
> Foundation mailing list
> Foundation at lists.openinfra.dev
> https://lists.openinfra.dev/cgi-bin/mailman/listinfo/foundation
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openinfra.dev/pipermail/foundation/attachments/20221021/8d773ebe/attachment.htm>