new commitfest transition guidance

During the developer meeting at FOSDEM last Thursday, there was strong
consensus that we should no longer move patches to the next commitfest
in a semi-automatic, mechanical way, has commitfest managers have
traditionally done. Patches should only be moved forward by someone
involved in the patch who knows that the patch is actually being worked
on. That way, there is a higher likelihood that the patches arriving in
the next commitfest actually have someone currently invested in them.

My interpretation of this is that patches should be moved forward by
either an author, possibly a reviewer, possibly a committer signed up
for the patch, or maybe even a colleague of an author who knows that the
author is on vacation and will get back to it in a couple of weeks, or
some similar situation.

CF 2025-01 has just ended, so I suggest that everyone try this now. We
can check in perhaps two weeks whether this results in lots of stuff
falling through the cracks or still too much stuff with unclear status
being moved forward, and then see what that might mean going forward.