I’d like to throw in my two cents to how this is organized. Chris Coyier, I know you’re wanting to limit this to possibly ten people, which is a good idea if you want to avoid the Too-Many-Cooks problem, but I want to offer you another idea so more people can have at least a little input:
Set up a repository, be it SVN, Git, Mercurial, whathaveyou. Let people pull the project, make modifications, and let them submit patches up. You have a team of qualified people, the moderator team, who could monitor the patches, approving or dropping them. In a sense, this would be following a congressional style, letting everybody contribute but still have a reasonable and fair congress to judge the modifications. And, yes, Git CAN monitor binary blob changes, so the .psd file would have a change-log description on it.
My hope is that such a plan could let this be a project that would be a true CSS-Tricks-community project that was curated by the CSS-Tricks team. As it stands now, it’s just you (Chris Coyier) leading a small section of the CSS-Tricks community.
Essentially, you’re taking a small-group profession (web design and development) and applying a Computer Science methodology to development.
