The more structural a component is (rather than providing a custom appearance) the better.

I'm still working out how to deal with people contributing components.

I was thinking about creating an organization on GitHub and moving all the repos there. Then people can create their own SUIT components and request that they be absorbed into the organization. An alternative is just to leave things as they are and I can add components to the SUIT readme if I think they align with the general project.

It would also be good if people resisted registering components under the suit- namespace on Bower.

Sounds good.

Whatever way you want to go with contributing ultimately it seems like the best approach for the moment (for contributors) is but the create the component repo and let you know about it.

I wrote a Node.js module to generate the boilerplate for a SUIT component package - https://github.com/suitcss/generator-suit

I can maintain a list of external components that get made, and any good, generic ones could be rolled into the core framework.