Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Translation projects are now moving entirely to localize.drupal.org (see #980658: META ISSUE: get d.o language projects all on localize.drupal.org). The existing projects are probably best kept for history and until their issues are running out / migrated to the discussion system to be put into place on l.d.o. However, I've seen more and more users confused by the existing d.o translation projects and their outdated state. Ie. if you list translation projects for 7.x only two shows up, as if no other languages have translations.
Because we are to keep these projects for some time, we should put up big warnings on the top of their own pages, listing pages, issue pages, etc. that these are deprecated and localize.drupal.org is the definite source.
Comments
Comment #1
Gábor HojtsyRelated: #980682: Deny creation of new translation projects and releases of existing translations.
Comment #2
dwwSounds good. Hopefully a fairly easy patch for drupalorg_project.module. Let me know if you need any help figuring out how to do this properly.
Cheers,
-Derek
p.s. I'm so excited that l.d.o is coming along so far! Ideally we can remove all traces of translations from CVS before the Git migration! ;)
Comment #3
Gábor HojtsyI figured the projects need to be marked abandoned as well, and that this does not yet apply to all translation projects as per #980658: META ISSUE: get d.o language projects all on localize.drupal.org, so I've just added a warning note to projects that migrated and marked all of them abandoned. Also added a warning block on top of the project/translations page saying "Translations are now maintained on Drupal.org's translation server. This list is obsolete and is only kept for historical purposes.".