What's your PotentialMulti-Site ROI?
The ForresterWave™: Web ContentManagement Systems,Q1 2015
We're HiringFeatured Position: Software Engineer -Test (Boston, MA)
Tagging Drupal core files is fine for things that are directly
module/code related. Tagging documentation pages is fine for
documentation. But, what about everything else? It seems like this is
a more sophisticated way of finding people that commit code. Which is
great, if that is what you need. But what about people who want to
participate in redesigns, or community outreach? A module maintainer
is not necessarily someone who wants to participate in that, or even
be the right person for that.
I guess I'm thinking if groups.drupal.org was better
organized, it could be the place for that. Every initiative and part
of Drupal (I don't mean code) can have a separate group and the
admins of those groups are empowered to make actual changes in their
respective areas. As it stands now, it doesn't seem like people
are empowered to make change, or know who to go to do so.
More information about text formats