Problem/Motivation
The maintainers block on the project page for a module is missing the information about how many commits a maintainer did, and how long ago the last commits where.
For developers and site builders this is valuable information to assess how actively a module is maintained and whether development hinges on just one person or a larger group. The removal of this information is therefore a regression.
The avatars are now displayed without any information, and without any indication on why they are displayed in the specific order.
Steps to reproduce
Go to any project page and try to get a feeling for how active the module is maintained.
Or compare these two screenshots from

The first one shows me that it's actively maintained, that maintainers are committed to it over a long time, and who currently are more active maintainers. The second one doesn't give me any of that. (I guess the order is based on total number of commits, but for a 13 year old module that's less useful.)
Proposed resolution
Either revert the mainters block back to the previous information, or revert it but add smaller user icons to the name and commit info.
Remaining tasks
User interface changes
This is a reversion of a user interface regression.
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| maintainers-pictures-2.png | 74.94 KB | ifrik | |
| maintainers-with-info-2.png | 30.52 KB | ifrik |
Comments
Comment #2
irinaz commentedMaintainers block on the project page has been redesigned as a part of #3227737: [Meta] GitLab Acceleration Initiative and was implemented as discussed in the issue #3006207: Maintainers block on projects should show maintainers of project, not committers . One of the goals for the Gitlab Initiative is to use more features provided out of the box by GitLab Drupal.org instance.
Information about project commits is readily available on Gitlab, links to project code on gitlab are provided in block Development in the right sidebar.

For example most recent commits information about Ctools on link https://git.drupalcode.org/project/ctools/activity, complete information about contributors is provided on https://git.drupalcode.org/project/ctools/-/graphs/8.x-3.x.
Comment #3
irinaz commentedComment #4
ifrikThanks for the explanation.
The links listed under Development weren't clear enough for me then, and they still don't provide the summarized overview that was very useful information to site builders/developers.
How much maintainers have committed and when were they last active - That's very difficult to get out of list of commits, even though that's usefull when you get into the detail of assessing a module. But it doesn't provide an overview or summary.
The link te tho contributors on gitlab somewhat provides that, but it's then 3 clicks away, hidden under "Repository". The added problem there is that user names on drupal.org and gitlab are different - and by excluding merge commits it gives a very different list.
Comparing the list of contributors to the maintainers block on d.o for ctools for example; that looks compeletely different because the user who does the task of maintaining the module by assessing and accepting merge requests - that user doesn't show up as an active contributer on Gitlab's contributor list. (Which is a different problem in itself).
So the list of activity and commits is useful information, but the information about the actual maintenance of the module is hard to find on gitlab - let alone in a summarize way.
I'm happy to explain in more detail how as sitebuilders and developers, we use such information to assess a modules, to see whether such information can be somehow extracted from Gitlab.
Comment #5
chi commentedI agree. That block was very helpful to quickly evaluate maintenance status of a project.
Comment #6
ressaCase in point is Colorbox. Until the project recently got new maintainers, https://www.drupal.org/u/frjo was listed #1, even though his last Drupal commit was June 2018:
https://www.drupal.org/project/colorbox/issues/3244987#comment-14390736
I am not sure if frjo was listed first (now third) due to having the most commits, or the list is simply sorted alphabetically? The old sort order, by latest commit date descending, combined with showing number of commits worked well for me.
Comment #7
irinaz commented