Keeping all the ports in one repository has a few downsides compared to hosting an organisation.
BIG repo.
This repo is already >30K lines and 40M of code and will only grow. Splitting it into multiple smaller ones will make it easier to maintain individually customised forks or to fix bugs/issues in existing ones.
(!De)centralisation
Right now, you, @kepano, have all the responsibility over this project and every contribution has to go through you, which is a bit ineffective, since I suppose you have a dayjob and other projects to focus on. Decentralising the ports will make it easier for people to create new ones and as every port will have it's own main maintainer, they will have more understanding over their own project and can more effectively manage it.
I understand that this migration may take some work, but over time the amount of work required to do this will only grow, as will the severity of the problems outlined, especially repo size.
Keeping all the ports in one repository has a few downsides compared to hosting an organisation.
BIG repo.
This repo is already >30K lines and 40M of code and will only grow. Splitting it into multiple smaller ones will make it easier to maintain individually customised forks or to fix bugs/issues in existing ones.
(!De)centralisation
Right now, you, @kepano, have all the responsibility over this project and every contribution has to go through you, which is a bit ineffective, since I suppose you have a dayjob and other projects to focus on. Decentralising the ports will make it easier for people to create new ones and as every port will have it's own main maintainer, they will have more understanding over their own project and can more effectively manage it.
I understand that this migration may take some work, but over time the amount of work required to do this will only grow, as will the severity of the problems outlined, especially repo size.