Team Coordination
Where do we have everyone register? Two options: Assembla and Gnomepal.
There are two ways of doing this. One is two simply ask the mailing list whenever we need resources for something, this could work fine. It just depends on how we decide we like to work. We also have the option of a more coordinated approach. This has advantages and disadvantages; some may not like to overly structure this and feel its too much overhead. On the other hand, by getting more info about people we might be giving a profile to our own community.
Also, some things will just happen automatically because people want to help of can't help but build something. There should also be a clear idea of priorities for those things that don't happen by themselves.
Overview of Experience and Wishes
To activate the Gnomepal community as much as possible, People need to know about eachother's experience level as well as what they'd like to do for and with the Gnomepal Development Community.
Everyone could, for instance, include a three sentence break down of what they can contribute.
On Drupal we can create a node type 'contributor' and have people select:
- Coder (level: script kiddie, fixer, wizard ; language: html, css, php, javascript, dhtml, sql, all of the above; drupal api knowledge: none, some, a lot, I created CCK)
- Tester
- Coordinator
- Graphic designer
- Teacher
I'd like to
- coordinate a module
- create a theme design
- code a theme design
- do theme bug fixing
- do api side bug fixing
- be a coder in a new module project
- optimize a module for client side performance
- optimize a module for database performance
- learn to be a better coder by watching others
- work on the setup wizard / install profile
Best Practices
What can we learn from successful community projects like
- Drigg
- CiviCRM
- Drupal itself
Space Home