I would *really* love if this could be implemented with an eye towards
providing machine-readable search. Even if that's not the initial step, we
should eventually be able to have an administrator console special page on
the wiki that gets you into that portal and automates installation...
Collecting ideas from prior discussions and prepping up a plan would
definitely be a good intern-ish task, and that can scale out to
implementation depending on what details we choose to go with.
Now the catalog of extensions is total... wiki. I think that creation of
such catalog is not only programming task but also some changes related to
the actual process of publishing, documenting and quality assurance of the
extensions. The first things that come to my mind:
1) install semantic extensions so that it would be possible to search
through extensions by various parameters (smth like that but better:
2) allow users to rate the extensions and provide some analytics, filtering
and sorting based on that (for example showing the best rated)
3) add the information about what's happenning with the code of the
extension to its page. This will allow to search recently changed
extensions and quickly see those which have been abandonned.
I think that this task is very important and maybw the first step will be
to find other software that has good extension catalog and learn from them.