Consider adding a new abandoned lifecycle status

It'd interesting if this could also be automatically added to an info.yml during packaging based on branch status or the module's actual "unsupported" status as well.

Then it's not just up to the "major upgrade fixer team" to ensure it is set for nearly abandoned modules.

Pasting my comment from slack:

One thing that someone commented on when I created the "abandoned project/module" spreadsheet a while back was that they didn't like the word "abandoned" because it could just be the maintainer was busy with other things for a while and was planning on coming back to the project/module at some point... I ended up updating the spreadsheet/sub-initiative wording to switch from "abandoned" to "adoption".

So... we may want to consider something other than "abandoned" ... i.e. "Needs some love" :D

It'd interesting if this could also be automatically added to an info.yml during packaging based on branch status or the module's actual "unsupported" status as well.

I don’t think we’ll be adding anything additional to .info.yml in packaging due to issues like 📌 Packaging info from .info.yml often creates conflicts when patching (ddo) Active . (We could add a separate metadata file as mentioned in that/related issues.)

Composer already has a standard for marking abandoned packages: https://getcomposer.org/doc/04-schema.md#abandoned. Since this proposal looks like it is about projects, not individual modules within projects, I recommend using the standard from Composer.

#3406954: Proposal - create a 'Project Update Working Group' → is RTBC so we need to decide if we want to

• go ahead here OR
• leave things as they are OR
• convey abandoned via composer.json