Once we remove the filter of key Wikimedia projects, there are some open questions:

• projects to analyze: all of the projects that appear in Gerrit. If there are others, we need some pointers to them.
• Issue tracking system: given that all of the projects were moved to Phabricator,
  • what do we do with the current set of projects? Should the Bugzilla panels be removed?
  • or we keep them

In T86154#1020446, @Dicortazar wrote:

Once we remove the filter of key Wikimedia projects, there are some open questions:

• projects to analyze: all of the projects that appear in Gerrit. If there are others, we need some pointers to them.

gerrit.wikimedia.org is all what it is. If someone in GitHub or elsewhere convinces us to be included, we will handle special requests to be addedto Korma via Phabricator tasks.

• Issue tracking system: given that all of the projects were moved to Phabricator,
  • what do we do with the current set of projects? Should the Bugzilla panels be removed?
  • or we keep them

Let's keep them until we have something better to show...

Ok, so no changes for Bugzilla repositories.

For source code, add all projects from gerrit.wikimedia.org (cvsanaly2 analysis and gerrit analysis).

Tomorrow I will start working on it!

Quim, checking the complete list of repositories, you have 1203 repositories.

So, do you want to manage the full 1203 repositories in the dashboard?

owl@atari:~$ ssh -p 29418 owl@gerrit.wikimedia.org gerrit ls-projects --format=JSON |  grep '"id"' | wc -l
1203

Is this a problem? Many of these are mostly inactive.

In T86154#1042241, @Qgil wrote:

Is this a problem? Many of these are mostly inactive.

The number is not a biig problem ... more time to generate metrics. If the activity is not high, I think we can cope with them. Let's try :)

As discussed in T86630: Consolidating time ranges across tech community metrics, the minimum requirement is to have this data updated on a monthly basis. It's fine if generating the stats takes a while.