Exposing Our Organizational Structure (Labeling Drupal.org Users)
Drupal started as and has remained an egalitarian organization, and we've hesitated to put official labels on contributors ("Module developer", "1000+ core patches", or whatever). The unfortunate result of this is that newcomers to the community have absolutely no roadmap. They can't figure out who they need to influence to get something done, or even who to go to in order to solve a problem. Essentially, by being purists about how egalitarian we are, we hide the actual structure of our organization and end up being elitist!
The community has already started talking about this problem, and there's probably a move toward some kind of badges explaining what users are. In addition, webchick has posted an actual org chart for Drupal Infrastructure, and written eloquently on how we need to expose our structure more explicitly.
So we need to:
* Decide what steps we're going to take
* Organize to get them done
