While updating http://drupal.org/contribute/translations I noticed that http://drupal.org/project/Translations can be very confusing for someone who's trying to find the right place for contributing to a translation. (See step 3 under "How to contribute".)

I propose we do the following:

  1. Add development status "Obsolete" to the project pages for all translations which have moved to localize.drupal.org, and add a very obvious "This translation has moved to localize.drupal.org, go there to contribute and to download updated translations" message to the project pages. (A lot of the projects have it, but not all, see for instance http://drupal.org/project/eu / http://localize.drupal.org/translate/languages/eu and http://drupal.org/project/zh-hans / http://localize.drupal.org/translate/languages/zh-hans )
  2. Filter http://drupal.org/project/Translations to only show translation projects which aren't obsolete
  3. Make the "Go to ldo" text at the top of http://drupal.org/project/Translations more obvious

Comments

gábor hojtsy’s picture

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

All of these sound like good plans actually :) We have not entirely cooked a solution for having "translation issue queues" outside of drupal.org and it might or might not make sense to have d.o projects for translations just for their issue queues (they'll not have version control space once git hits). If we can figure out a good way to have "issue queues" for them on l.d.o, we might make them cleanly obsolete (and in that case, maybe even autoredirect people to the right team page on l.d.o).

zirvap’s picture

zirvap commented
Status: Active » Postponed

Good point, I didn't think about issues. I'm postponing this until we have figured out #967146: What kind of issue tracking do we need for translations?

dddave’s picture

dddave commented
Project: Drupal.org site moderators » localize.drupal.org
Component: Other » Infrastructure