So we've been talking about creating a [Non-g.d.o.] site for DrupalPGH for a while now, and the idea of creating a distribution to share with other local user groups would seem to fulfill that need, give us an interesting topic to discuss and build, and create a tool for other user groups. Question is, what should such a distro look like? Are other user groups interested in such a thing? I know many groups have non-g.d.o. sites, the content and functionality seems to vary quite a bit.
G.d.o. is definitely a great place for discussion, support, events, and job postings, and should continue to be the primary venue for this type of interaction. To my thinking, a local group distribution should augment g.d.o. by providing things that it doesn't, and evangelizing Drupal to the local community in a way that may encourage non-users to join the Drupal community.
A couple of things I'd like to see:
- A content repository for stuff generated by local groups (video, slide decks, etc.), attached to their event(s), with some categorization and/or user feedback
- A forward-facing welcome for non-users to learn more about Drupal and/or participate in the community (marketing)
- Event promotion and calendar. Events should live at g.d.o. but be promoted on the group's site, possibly with additional marketing
- A local marketplace or directory of Drupal service providers. Some rules governing what constitutes 'local' may need to be established.
- Generally useful tools for user group admins.
Not sure what admin tools, if any, would be useful for most groups. Submission templates for project showcases and presentation topics come to mind. Also, We market on g.d.o., meetup.org, twitter, and sometimes craigslist -- many folks sign up in one place or another, or don't sign up at all, so I use counts from the previous few meetings to guess at how much space and/or pizza we'll need. It'd be nice to have some sort of sign-in or headcount to be used at the meetups.
This is certainly not an exhaustive list, and for such a thing to be useful it'd need to be broadly applicable. Is this something other user groups would be interested in? Are other groups doing anything similar already? Thoughts and/or suggestions on features/strategy?