It seems to me that the drupal problem is different:
* There is an apparent misunderstanding of how translations should use projects. Most drupal "projects" are actually translation projects. People creating them think "I am creating a translation project", therefore create a project without realizing the proper thing is to attach themselves to the upstream.
I do not believe that duplicate checking on project registration would help, because I believe those users have deliberately created multiple projects. It seems to me the issue is more of misunderstanding what is the purpose of a project, and how to collaborate on translations using Launchpad.
It seems to me that the drupal problem is different:
* There is an apparent misunderstanding of how translations should use projects. Most drupal "projects" are actually translation projects. People creating them think "I am creating a translation project", therefore create a project without realizing the proper thing is to attach themselves to the upstream.
See: https:/ /launchpad. net/drupaltr https:/ /launchpad. net/drupal- ru https:/ /launchpad. net/drupal- project https:/ /launchpad. net/drupal- tr https:/ /launchpad. net/drupal- 5.0-ru https:/ /launchpad. net/drupal- ru-4.7- core https:/ /launchpad. net/drupal5eusk ara https:/ /launchpad. net/drupal- il https:/ /launchpad. net/4.7
I do not believe that duplicate checking on project registration would help, because I believe those users have deliberately created multiple projects. It seems to me the issue is more of misunderstanding what is the purpose of a project, and how to collaborate on translations using Launchpad.
* A couple of drupal-related projects seem to be legitimate separate objects: https:/ /launchpad. net/drupal https:/ /launchpad. net/drupal- signup
* One case looks like a genuine unintentional duplicate: https:/ /beta.launchpad .net/drupal- cms