As a translation moderator I like to know what is going on in the group. Instead of visiting l.d.o at a regular basis, I like to have a detailed overview or receive emails of translation and moderation activity.
I made an inventory of what statistics could be relevant. Not all are "must haves".

Per language:

  • Status
    • Number of contributors
    • Number of strings to translate
    • Number of translations recorded
    • Number of suggestions awaiting approval
    • Number of projects
    • Number of Project/release percentage of completion
  • Activity (per day, per week, per month)
    • Number of translations approved (total)
    • Number of translations approved top projects
    • Number of translations suggested (total)
    • Number of translations suggested top projects
    • Projects/releases near completion (completion > 90%)
    • Projects/releases popular (increase > xx%)
    • Projects/releases completed
    • Projects added
    • Active translators (added suggestions)
    • Active translators and their projects
    • Active moderators (approved translations)
    • Active moderators and their projects
    • New contributors
  • History
    • Suggestion added per week
    • Translations approved per week
    • Number of active contributors (suggestion + approval)

Comments

droplet’s picture

droplet commented

"statistics" or accessible data (eg. a list of new suggested strings ) ?

baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented

Wouldn't this feature consume too much resources? My humble concern based on the case of l.d.o as Gábor Hojtsy described here: https://drupal.org/comment/8404933#comment-8404933

baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented

(Duplicated comment.)

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

Yeah this would likely be very expensive **on the current database structure**. There are surely much better ways to store our data (and archive old data that we don't do now). It would be great to not build that out on the Drupal 6 based platform we have now, since you know.... that is going out of support sooner than later. So moving to Drupal 7 and then doing rearchitecting would be preferred IMHO. See #1424984: Port localize.drupal.org to Drupal 7 (which is not that far off!!)