Contrib.social

Enhancing Project Page Display to include Statistics by Drupal Version

Open on Drupal.org →
Created on 7 March 2014, about 11 years ago
Updated 22 May 2025, 15 days ago

Coming from #831654: Missing break condition on fivestar_comment_comment('insert') → it occurred to me that there would be benefits to splitting up the Issue block on the project page down by version so that it looks more like:

All issues
open 228 D6 / 200 D7, 1817 total
Bug report
open 40 D6 / 75 D7, 707 total

This would allow a maintainer to follow the best practice recently defined here https://drupal.org/node/2212549 for dealing with older D6 versions of a contrib module when a module maintainer is only able to maintain the D7 or D8 version of the code.

If we're going to be breaking down maintainers per version, it's good if we can make it possible for the D7 maintainer to work through the bugs and clearly leave the D6 bugs/issues open but different.

EDIT: There is some discussion about spiting off more than just the issue #'s in GDO https://groups.drupal.org/node/137914

📌 Task
Status

Active

Version

3.0

Component

Miscellaneous

Created by

🇨🇦Canada mgifford Ottawa, Ontario

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 15 days ago →
    🇩🇰Denmark ressa Copenhagen

    Thanks for raising this issue. Since Drupal 7 is EOL, perhaps the Statistics block in the right hand side should only count "modern" (8/9/10/11/12) Drupal versions?

    See for example Pathauto ( https://www.drupal.org/project/pathauto/ → ) where it says there are 287 open bugs:

    All issues
    650 open, 27 RTBC, 3,527 total

    Bug report
    288 open, 14 RTBC, 1,622 total

    Statistics
    New issues 1
    Response rate 100%
    1st response 18 hours
    Open bugs 287
    Participants 3
    2 year graph, updates weekly

    But there are only 131 open 8.x bug issues:
    https://www.drupal.org/project/issues/pathauto?status=Open&categories=1&... →

    ... or is this better handled in the individual projects, for example by setting Drupal 7 issues to "Closed (Outdated)"?

  • Comment 15 days ago →
    🇪🇸Spain fjgarlin

    Note that this block is going to dissapear completely with the move to GitLab issues. It will be just a simple link to the issue queue.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024