You have to let the supporters make that decision. You can make that decision easy, you can automate a lot of it, you can inform, but you can’t change which pr

You have to let the supporters make that decision. You can make that decision easy, you can automate a lot of it, you can inform, but you can’t change which project the funding is going to without explicit consent. And yes, for these purposes, the new fork should be considered a new project. It is a completely different situation than if the project itself decided to change maintainers, etc. This is really a crazy situation where the original maintainer blows up the project. The best scenario would be for the original authors to hand over the project in some capacity. But that seems pretty unlikely. To put it in different terms… this was not a SQL UPDATE. The was a DELETE. You don’t just change foreign keys to a different project_id when you delete a record. I would also argue that the author was completely irresponsible, and made life difficult for everyone that used and supported the project. But that’s a separate issue and doesn’t make what the open collective decided right.