Recommended packages site?

I agree that it would be good to have an easy way to find quality, stable packages to add to a CodeIgniter app.

I see several ways to achieve this:

1) use the existing wiki on our repo.
This wiki is out-dated, unreliable, spammed, and a mess.
I am inclined to drop the wiki altogether, unless the community steps up to maintain it. I put out a "help wanted" notice last year, and some work got done, but the problems remain.
I would not trust the wiki.

2) a third party site
There are a few, such as the github site referenced above. I haven't had a chance to check them out properly, but I see no indication of beta vs stable, CI version supported, endorsements by the community, etc. There are a *lot* of packages there I am not familiar with, and which have not been mentioned on the forum in the last year or so nor on the IRC channel.
This could be a good idea, and CI doesn't oppose it, but we cannot endorse it or give it our blessing or in any way make it official.

3) stuff on packagist
Suggested several times. There is nothing to stop any developer from making their packages available through composer. There is also no way to "vet" such packages ... a problem similar to both the previous solutions.

4) CI-maintained "official" packages.
This won't happen. We don't have the resources, as has been previously pointed out.

5) An "official" package list, on our website.
This is a possibility, and I had a UCOSP team do some preliminary work on it in the fall of 2015.
We even have a feature branch on the website repo ... https://github.com/bcit-ci/codeigniter-w...ure/addons
No comments, issues or PRs since the fall ... hmmm. Maybe it isn't the right approach either.

The problem that I see with any solution that asks for CI's blessing is vetting the packages, and categorizing them properly.
I don't want to see such a tool, whatever form it takes, getting spammed or being used as an advertising vehicle, etc, etc.

By the way, the only one of the above strategies that comes close to being official in any capacity, is #5, where we vet or have someone vet on our behalf proposed entries. I think I have a way to manage that, without it costing a huge time commitment, other than the initial development and proofing. It is not high on the priority list at the moment, and probably won't be until CI4 gets further along, our forum software software gets updated to a more secure tool, and we get more of a core team for developing and managing our project.

A huge thank you to Narf for keeping CI3 strong and secure, Lonnie for kickstarting CI4, and all of the community for continuing to care!

James Parry
Project Lead