Just realized the weight of moving the primary location of our source code given the number of links to it out there
And the whole forks ecosystem
And the way commit messages refer to GitHub issue numbers
@Gargron I supose you can always keep a mirror on github, while writing that the active repository to submit patches and issues is self-hosted, and that the github mirror is not monitored.
Similar to https://github.com/WordPress/WordPress?
No point to doing any kind of rage-quit and bridge burning. Just plan, then execute, a pivot, switching around priorities.
You didn't get locked-in all at once. It'll take time, too, to get sufficiently untangled.
Generalistic and moderated instance. All opinions are welcome, but hate speeches are prohibited. Users who don't respect rules will be silenced or suspended, depending on the violation severity.