Home / Blog

Add new comment

Posted on by David Hernandez.

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

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.