A possible path forward

Our group is not focused and not very productive. I don’t feel like we are getting a lot of lasting value out of the presentations, they are too passive. We need to engage the group members and get our hands dirty as that is the only way to really learn. I suggest that we structure the group like an ongoing training camp, with emphasis on collaboration.

Here are my specific suggestions:
1. Use the dug.lv site as a platform for learning and collaboration.
a. Work only with Drupal 7 as it is the future.
i. Create multiple subdirectory instances of D7, one for each “project” (see below)
ii. Work with base theme and minimal modules so that projects are as clean as possible.
iii. Appoint a leader for each project. The leader’s role is to manage, to 1) define the “project”, 2) lead the “development” role, 3) be the central communications point, 4) push/pull/prod (or kick), to get everyone involved and contributing to the effort.
iv. Once the project is complete (including documentation and videos were appropriate), the Leader will (either be, or) hand the project off to an ongoing administrator who will then be responsible for keeping the project live, documented, and up to date as new versions become available. The administrator should become the “subject matter expert” for that project and the go-too person when questions arise.
v. These projects should be teaching/learning/collaboration platforms where we can all be involved but also where the process/results will be available to the greater Drupal community as a “how-to” for each configuration.

b. Pick 6+ modules/module sets and implement them in a way to showcase their capabilities and to allow everyone to participate. Here is a list of possibilities:
i. a cluster of basic commonly used modules: editor(s), backup & migrate, captcha/recaptcha, pathauto, +?
ii. faqs
iii. panels
iv. fbconnect & twitter
v. views
vi. xampp and php.ini (obviously offline but documented as all projects)
vii. reference & nodereference
viii. tokens
ix. ctools
x. features
xi. ideal development process (from planning thru live online including maintenance)
xii. Advanced backup strategies (e.g. github)
xiii. og & subgroups
xiv. theme(s)

We can add more module project or PHP, Java, CSS, etc., whatever projects, and/or take the above projects to greater depths once we have basic configurations up, stable, and well documented.

c. Start with the simplest modules and functions and work our way up, but ALWAYS document/retain/maintain the individual platforms that have been developed.

1. Next steps for DUG LV
   a. Develop and prioritize a projects list
   b. Appoint Leaders for each project
   c. Develop a rough plan for how we will collaborate (including tools) – this will change as we try and as we learn, so strong leaders will be critical for early projects.
   d. Get commitment from all parties to participate (this will be an ongoing process as new people join)
   e. Open up the dug.lv site so that we can actually do something with it.
   f. Create a number of instances of Drupal, one for each project.

2. Outreach should be a key part of our process. We should engage other groups and/or the module owners in our efforts. Once they see that we have a program that will help support their modules and aid the Drupal community, I think we will find their participation/cooperation to be forthcoming.

Our goal should be to set a standard for other DUGs to follow. Think how powerful it would be if we had 10 groups around the world, each following this model. There would be operating and documented environments for most commonly used modules. I could see competition developing between groups to produce the best projects and documentation/training programs, and even from module owners competing to get the best DUG to take on their module(s). This would greatly assist the Drupal community and it would establish DUG LV as a leader.

I would like any and all comments.