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.
The answer is off topic, but I'll add a little.
1. Backend. Why you don't need links to other websites: Since you know the structure of your site and content, you can decide for...
Hi Chrys,
AI isn't always your best friend. A form alter hook is correct, but hiding by CSS isn't ideal.
You could look at how the TinyMCE integration does it, which provides hiding...
Hi zilvervos...,
Welcome back to Backdrop.
I've just started a new "news" website for a client, but it's at the very early stages. I'm hoping to have a soft launch in a couple...
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme.
By default, such users won't have permissions to see the...
Posted5 days 2 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) 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.