A quick and dirty way to get the busiest repos per number of commits is to use git log on mediawiki/extensions:

Another note from a discussion with Zeljko: we have a third party gathering git/gerrit metrics. They store it in ElasticSearch and use Kibana for dashboarding: https://wikimedia.biterg.io/

That was build for technical community metrics.

Thanks @hashar, Bitergia is really useful! It's report for the last year:

[[ https://github.com/tj/git-extras/blob/master/man/git-effort.md | git effort ]] results for mediawiki/extensions (git effort --above 100 -- --after="one year ago"'):

Just saying, the "ORES" service and backend of the ORES extension is being maintained by scoring platform team not growth.

In T199133#4732915, @Ladsgroup wrote:

Just saying, the "ORES" service and backend of the ORES extension is being maintained by scoring platform team not growth.

Thanks, but Developers/Maintainers says Growth. Should it be updated?

In T199133#4765747, @zeljkofilipin wrote:

Thanks, but Developers/Maintainers says Growth. Should it be updated?

So there are three different things called ORES here:

• ORES service (ores.wikimedia.org) that does the heavy lifting.
  • The code for that is in mediawiki/services/ores/deploy, it's python
  • Has one incident in the table but I suspect it's more
  • This is being maintained by Scoring platform team
• ORES extension frontend:
  • The code is mostly in the ORES extension (The Recentchanges hook handlers basically), it's mostly PHP
  • Doesn't have any incidents
  • That is being maintained by Growth team
• ORES extension backend (that gets the data from the service and store it in ores_classification table):
  • This code is also sitting in ORES extension (basically the rest of the extension), it's also mostly PHP
  • It had two incidents (It might the frontend part but my guess goes to the backend)
  • It's being maintained by Scoring platform team.

HTH

In T199133#4766085, @Ladsgroup wrote:

So there are three different things called ORES here:

• ORES service...
  • This is being maintained by Scoring platform team
• ORES extension frontend...
  • That is being maintained by Growth team
• ORES extension backend...
  • It's being maintained by Scoring platform team.

The only mention of ORES at Developers/Maintainers page is about the extension. It does not mention frontend/backend or service. Should the page be updated? 😄

In T199133#4773545, @zeljkofilipin wrote:

The only mention of ORES at Developers/Maintainers page is about the extension. It does not mention frontend/backend or service. Should the page be updated? 😄

Done now :D Thanks for pointing out.

Thanks!