I am wondering if there other people in the Twin-Cities using Drupal, that would want to create sub-group for development of Drupal or more advanced topics for Drupal.
I really like the group we have going here. I think the range of Drupal expertise is a huge benefit, but I also feel like it is limiting at the same time. The difference between beginner CSS and writing Drupal Modules is huge.
My idea has spawned from this post (http://drupal.org/node/160239) and what others have said about other Drupal Users Groups.
I propose a Twin Cities Drupal User Group focused on more advanced topics (Module Building, Installation, etc.). Maybe we can get involved with the Twin Cities PHP User Group (http://www.tcphp.org/).
Let me know what you think.
-Alan Palazzolo
Comments
Great idea, Binary Bill
I like the idea and would be involved if my schedule permits.
Another idea would be to split the current group's schedule into two tracks. For lack of a more accurate description of the separation: one for users, the other for developers. We could keep the same structure-- meeting place and time-- but alternate the topics. In other words if July's meeting covers beginning CSS, the August meeting could cover the form API. It would, in effect, be two groups meeting bi-monthly but be less complicated to organize and attend than two completely separate groups.
======================
Barry Madore
Advantage Labs, Inc.
Barry Madore
Triplo
Minneapolis-St. Paul, MN
Please present a topic!
I've noticed that various meeting topics bring different audiences. For example, at the last meeting, roughly 1/2 of our "regulars" were absent, but 1/2 of the room was filled with new faces and we had the same attendance. At every meeting, I learn something new! If you propose a presentation - or even an open discussion - on something that interests you, my guess is that you'll find others who are interested in the same topics right here in the group.
FWIW, As a fulltime Drupal developer and someone who's had to clean up a lot of messes, my preferred topic would be how NOT to write a module -instead supporting others' work or working smart by leveraging existing modules to get what you need done. Thus, I'm never done learning about Views, fields, output formatters, and other seemingly-basic topics.