view - project by completeness

I would also add "Moderated by" to the list. As you suggested in one of our previous discussions it's a great way to motivate moderators to review and accept suggestions (their work becomes "visible").

One more thing - I think that every entry should represent a module version, not a project. If the latest version of a module is fully translated it doesn't really matter whether some ancient versions are translated or not.

This issue belongs to the localization server and I agree it is a great suggestion. The current project list does not really work for this many projects.

However, it is a general (not language specific project list, so to have language specific project stats for all projects, we'd need to implement stats one level deeper).

@palik: Unfortunately we do not have stored values for completeness, it is computed from queries to the data sources directly. We do cache the list of projects in a structure, so theoretically we could do sorting on it on the PHP level. Not sure about the performance of that, but we do not have that many projects in fact, so it sounds feasible.

@archetwist: identifying which version of a project is relevant is an interesting question of its own right. "The latest" version is not really well defined due to all the branching possible. Is Drupal 6.latest not relevant now that Drupal 7.0 alphas are available? I hope not :) There are I believe multiple issues relating to branch identification, one I found is #648928: Only show source code warnings for latest release on each branch.

Gábor, the question is not as tricky as it seems - the most relevant versions are the latest stable versions for every supported branch of Drupal :-) . But, actually, my idea was not to filter out any but to treat every version as a separate entry (to "group by" - to use Views' terminology - version, not project).

@archtewist: well, the latest versions for core branches is not really workable. A module can easily have a 1.x-3.2 version and a 2.x-alpha3. Now should people use 2.x-alpha3, because that is the latest or 1.x-3.2 because that is the stable? Many modules have multiple branches which are supported and they are at different levels of completeness. Eg. if a module has numerous alphas and betas on its 2.x branch all released after the latest 1.x stable branch, you'll have a list of stuff where the top X items are not suggested for deployment and therefore probably not good to translate for use in live environments, so the latest supported version will be in the middle of the list.

Latest stable - alphas or betas are not stable by definition. But I think what you wanted to say is that latest stable releases may not be the most interesting ones and latest beta releases may not be ready to use. However, I still think it's better than grouping by project completeness when some translations may be at the bottom of the list just because a project has many ancient versions.

We could also use the latest version marked as supported. I suppose this information has to be stored somewhere in the drupal.org database.

Yes, supported branches and versions are not yet carried over to the l.d.o database, so we need that as a prerequisite too.

This is being worked on in #1095806: Add sorting options to overall project list.