This feature was proposed in E of #986718-9: Add support for sandbox projects.

It would be useful to have for:

The beauty of using this mechanism is that the most relevant parts of contrib (those in '/project/[slug]') will be refined, and no code will ever be lost.

The key feature of all qualifying 'full projects' is that their code bases are not expected to improve, so we are only to gain by pruning it.

Comments

mitchell’s picture

mitchell commented
Title: Demoting full projects to sandboxes » Ability to demote full projects to sandboxes
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.x-dev » 7.x-2.x-dev
Issue summary: View changes

I am not sure this is doable.
A full project has releases, while a sandbox could not have releases. (There is a setting to enable releases on sandboxes, at least on drupal.org.) What should happen to those releases, when a project is demoted? Should they be deleted, unpublished, or kept?

mitchell’s picture

mitchell commented

> (There is a setting to enable releases on sandboxes, at least on drupal.org.)

Why'd we #994260: Add a setting to disable releases for sandbox projects in the first place?

dww’s picture

dww
we/he/they
commented

re: #3 because not all users of Project* necessarily have the same requirements / use-case as d.o. At least, that's the theory. ;) We didn't want releases for d.o sandboxes, but we also didn't want to force that decision on everyone. So it was added as a site-wide setting.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I apologize: My previous comment seems to have caused confusion.
I just meant that, changing a setting, sandbox projects could have releases too, but on Drupal.org sandox projects don't have releases. I didn't also remember if that setting was implemented by a custom module used on drupal.org, or it was implemented by a third-party module such as the Project module or any of its related modules.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I don't see any reason for demoting a full project to sandbox in any of the listed use-cases:

  • Abandoned projects can eventually be taken over by other users
  • Projects without committed code can be taken over from other users, even to just use the namespace
  • Projects with that have problems with maintainership can be taken over from other users

On Drupal.org, if I take over a project to reuse its namespace, I can hide the existing releases and create my releases. I don't need it to be first demoted, and then make it a full project again.