Request to clean up published_state_indicator namespace

Created on 15 May 2024, 9 months ago
Updated 4 September 2024, 5 months ago

Problem/Motivation

I created a new project but didn't realise the the short name would be used as the project ID, I thought the 'Name' field would be used.
Could this project be deleted: https://www.drupal.org/project/psi β†’ so I can recreate it with the full name.

Would it be possible to have the Short name field on the form updated with a description that indicates this will be the project's ID?

Thanks.

πŸ’¬ Support request
Status

Fixed

Version

1.0

Component

Namespace request

Created by

πŸ‡¬πŸ‡§United Kingdom omahm Belfast

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @omahm
  • Status changed to Closed: won't fix 9 months ago
  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

    Projects are not deleted from Drupal.org. Since there is a release, we would not put someone in a situation where something they are using is removed; and we certainly wouldn’t want the possibility of existing releases replaced with a different codebase.

    If you would like to direct people to a replacement project, you can mark the releases and projects as unsupported and update the project to note what it is replaced by.

  • πŸ‡¬πŸ‡§United Kingdom omahm Belfast

    There is a release but nobody is using it because I just created it and realised the short name was used.
    The issue with creating another project is that I cannot now use that project name as it's taken.

  • Status changed to Active 9 months ago
  • πŸ‡¬πŸ‡§United Kingdom omahm Belfast
  • πŸ‡¬πŸ‡§United Kingdom omahm Belfast

    I created a new project using the full name as the short name but now the releases use both as the composer package name.
    composer require 'drupal/published_state_indicator-published_state_indicator:^1.0'

    What is going on?

  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US
  • πŸ‡¦πŸ‡ΉAustria maxilein

    please, please ...

  • πŸ‡¬πŸ‡§United Kingdom johan.gant Belfast, UK

    @drumm I can see why deleting/unpublishing an actively used project would be a bad idea. I think it's pretty clear @omahm is in a bit of a stuck state due to being unfamiliar with the module/composer admin process so this is more of a support request to yourself or another person who might be able to help. A new project was created to supersede the original module but it's unclear why the composer package name has the structure @omahm outlined in comment #5.

    I guess we need a steer on how to turn drupal/published_state_indicator-published_state_indicator into drupal/published_state_indicator, if possible? Any help or directions much appreciated, thanks

  • Status changed to Fixed 6 months ago
  • πŸ‡ΊπŸ‡ΈUnited States hestenet Portland, OR πŸ‡ΊπŸ‡Έ

    Note that the prefixing of a project with its own name was not an error, but rather a way to prevent a namespace collision with the first project created.

    Updating the namespaces is a manual process on the DA's part - I've gone ahead and made the following change now:

  • πŸ‡¬πŸ‡§United Kingdom omahm Belfast

    @hestenet that's great and I really appreciate you cleaning up the namespaces.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024