If there's some time left in the dev meeting - although it might rather be a topic for the PMC:
We have nice documentation and procedures, how to provide projects in backdrop-contrib space.
We don't seem to have any guidelines or procedures, how to sunset a project.
Recently there was some guessing in our Zulip chat (not the public part), what to do with a project that's obsolete, replaced by another project, and shows no installs in the stats - and nobody knew how to handle that. The suggestions sounded more like workarounds, not solutions.
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module isn't an option for me; I didn't know what else to do. I didn't want to take any actions like "archiving" it until I found out if there's an official policy.
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again.
Then...
Posted3 days 23 hours ago by Francis Greaves (themetman) on:
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Posted1 week 2 days ago by Francis Greaves (themetman) on:
Comments
The need for a clear AI policy is growing. Please can this be a priority.
If there's some time left in the dev meeting - although it might rather be a topic for the PMC:
We have nice documentation and procedures, how to provide projects in backdrop-contrib space.
We don't seem to have any guidelines or procedures, how to sunset a project.
Recently there was some guessing in our Zulip chat (not the public part), what to do with a project that's obsolete, replaced by another project, and shows no installs in the stats - and nobody knew how to handle that. The suggestions sounded more like workarounds, not solutions.
I second this-- I have a module in contrib now that I just marked as "deprecated", and I removed its sole alpha release (because a fix in Core made it obsolete). Just plain deleting the module isn't an option for me; I didn't know what else to do. I didn't want to take any actions like "archiving" it until I found out if there's an official policy.