I would definitely support a plugins directory of sorts, however, I think this is directly related to how much support for GitHub (etc) that ClassicPress will have.
Specifically, to differentiate this project from WordPress, to reduce work load, and to empower developers and agencies rather than creating another fiefdom of favoritism and corruption, I think a sort of “meta engine” or index of plugins would be more appropriate than a full blown WP.org style directory.
We were planning to do something similar for SlickStack, using the below website and their open source code as inspiration:
This could be up and running in a matter of days, instead of years. Instead of e.g. whitelisting or blacklisting plugins or agencies that ClassicPress doesn’t like, which is the drama that has gone on for a decade at WP.org, it would entail something more along the lines of indexing every single compatible plugin on GitHub that currently supports ClassicPress (whether or not still maintained). I don’t think over moderating or filtering such an index is a good idea because it will only narrow the potential ecosystem of developers, cause drama, etc. Instead, the meta engine could integrate a reviews system, but not host the plugin code. To login and leave a review (or to login to ClassicPress.net) it could require GitHub Oath to ensure that real identities are being used, to avoid trolling and spam, and to eliminate fake reviews and extortion of plugin authors… the reviews could also have a merit-based requirement meaning that only reviews that directly address the plugin’s functionality, code, etc will be retained. Complaining about the agency’s customer service or other unrelated topics (“I’ll change my review if you do XYZ…”) could be disallowed…
~ posted by Jesse