Gathering Requirements For A PEAR Channel Aggregator
I've had several conversations on Twitter about how it could be a good idea for someone to setup a new community website for PHP components. This website would not host components itself; it would track all of the independently-published PEAR channels, and be the one-stop shop for users to come to whenever they needed to find a component to solve a requirement.
I think this would be a good thing for the PHP ecosystem.
So - requirements! What do you want from such a website? What do you want it to do? How do you want it to work? At this stage, the sky's the limit. Leave your requirements in the comments, please, and I'll pull them together into a summary post next weekend.
Once the requirements are stable-ish, I'd like to organise a hackathon to get the first version built and live. If you're up for that, and want to help make that happen, do ping me on Twitter: @stuherbert.