What are the plans for this meeting? Are we just showing up with a random bucket of things to present? Are we going to try to nail down a particular topic for presentations?
I suggest we get the ones who want to present on February 17th to prepare now. So, we can get word out at least a week in advance with the topics of presentations. This will give time to persuade some of the possible showers to come out to check out a certain topic. I really do not want to have another meeting where we do not really know what is going to be presented, and it feels like we are just winging it.
I am really interested in presenting my Validation API to get some content into our meetings. So, people can walk away from the meeting with at least one new tool to go try out.
This is my proposed agenda:
7:30 - 7:45: Introductions. We always have some new people at the meetings, so it is always helpful to get more familiar with the members.
7:45 - 8:00: I will present Validation API. 5 minute presentation on how to set it up and work with it. Then, extra time set-up for questions and discussion.
8:00 - 9:00: Theme presentations. We had a lot of members interested in discussion of theming topics, and so it would be great to set aside a nice chunk of time for a couple people to present. Then, have open discussions about the ideas and other aspects of theming.
9:00 - 9:30: If Odin Dev is ok with this. After the main discussion has been completed, we could have this sort-of optional hands-on time. Where members can stay and help out the newer members learn about how to do specific things within Drupal. For example, a member is having a difficult time working with Taxonomy+Views integration in Drupal. They can ask questions about their specific problems and get help from another member that is more experienced in the area.
Im hoping we can get some more discussion going around about what people are interested in and how we can turn this group into a very informative and worthwhile network in our Drupal lives.