Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Now that there will be more full projects on Drupal.org, there will occasionally be test projects and ideas that do not take off. Webmasters and everyone else shouldn’t have to deal with the namespace squatting for these projects. They can just go away after awhile.
For projects without code:
- After N days: show a notice on the project page when maintainers view.
- After M days: email the maintainers.
- After L days: auto-delete the project, and its issues too.
Comments
Comment #2
gregglesThis idea makes a ton of sense to me. Why not email on day N? And why not show the warning publicly so that webmasters or peopled interested in the project can see it?
I could also see a different set of thresholds for projects with issues.
To get discussion started, how about:
* After 14 days: show a notice on the project page and email the maintainers.
* After 28 days: email the maintainers again letting them know "final warning".
* After 30 days: auto-delete the project, and its issues too.
Comment #3
mlhess CreditAttribution: mlhess as a volunteer commentedThis sounds good, However, on 30 days, I would unpublish the project and its issues.
Then on 45 days, delete.
I could see someone coming along, and creating something, putting issues in to get done, and then having a life emergency happen and having to go away, so 45 days seems to make sense from project node creating till 100% gone.
Maybe delete everything on 30 days if there are no issues.
Comment #4
drummI was thinking the notice on the page would appear soon. A day feels like a long time to have a fresh project without code, to me. 2 emails makes sense to me, the first is onboarding and initial warning, the second is a final warning.
Comment #5
mlhess CreditAttribution: mlhess as a volunteer commentedWe need to be very careful, not to delete projects like webmasters/etc
Comment #6
pingwin4egInstead of deleting the project maybe it will be better to make it a sandbox?
Comment #7
fuzzy76 CreditAttribution: fuzzy76 commentedA notice on the project page only visible to maintainers (as I read the issue description) could probably be there from day 0.
Comment #8
kattekrab CreditAttribution: kattekrab as a volunteer commentedWhat about projects like the Drupal Community Working Group that have no code?
eg. https://www.drupal.org/project/drupal_cwg
Would our project get automatically deleted?
Or would we need to put some dummy code into a repo to prevent it?
In which case, anyone could put dummy code in their repos to prevent the robotdelete.
Comment #9
mlhess CreditAttribution: mlhess as a volunteer commented@katterab, I guess we think alike, I bring this up in #5.
Comment #10
drummComment #11
fuzzy76 CreditAttribution: fuzzy76 commentedIsn't there a type field for projects (module, theme, etc)? If so, could there be a "meta" type excempt from cleanup and only available to the DA?
Comment #12
drummFound an exact duplicate of this issue: #2455751: [policy, no patch] Projects older than x months with no code are purged (namesquatting)