Project handoff

[stuartpb]

Just touched on in #7.

My thinking is that I'll probably, in the event that I hand off to new maintainers, make a second directory of maintainers, which uses the same UUID-YAML-file format (maybe using the UUID of the maintainer they have as a user in whatever system tracks vote status etc, and maybe keeping them as foreign keys to each other with maybe mutual links), which'll contain their contact / profile / GitHub info, which will then get referred to in new fields in the projects file for project(s) that they inherit

within handed-off project YAMLs, maybe I'll give more details in remarks (and maybe not, maybe having an accordion for whoever the project was handed off to that'll be closed by default if remarks are present and open otherwise), and the handoff list will always be an array (and should this track history?)

but this feels like jumping the gun to consider in too much detail right now (especially since I'm not sure if I might have more than one kind of handoff, ie. I-remain-the-BDFL-of-the-project versus completely-disowning-the-project, and everything in between)

[stuartpb]

On this subject, I might want to figure out otherwise crediting people who participate on a project on-stream in the project data - thinking of the directory of user profiles as maintainers is probably a little narrow-minded, in that context (like, it should just be people?)

[stuartpb]

Further discussion around people data should happen in #9

[stuartpb]

Worth noting that, as these projects are all open source, projects can also fork into a scenario with multiple derivatives (some of which could even be my own)

See also #11 on spinoffs / splits (a fork being a type of split)