This document discusses Drupal's project management tools and resources for module maintainers, including automated testing, documentation, issue tracking, and community support. It highlights how some popular modules grew large developer communities that fixed over 90% of critical bugs through these resources. The document encourages contributors to write tests before committing code and review patches through the issue queue. It also lists projects needing maintenance help and provides contact information.

1. Drupal contrib
module
maintaining
Andriy Podanenko @podarok
http://druler.com/drupalgive

2. use cases
http://dgo.to/gmap 50K+ installs
http://dgo.to/location 50K+ installs
http://dgo.to/captcha 200K+ installs
+ ~60 other small modules

3. community grow
http://dgo.to/gmap
16->73 developers ~18 month +15000 installs
0->726 tests
http://dgo.to/location
18->94 developers ~17 month + 20000 installs
100->425 tests
90% Critical and major bugs fixed by users!!!

4. drupal.org project management
- issue queue
- documentation
- change records
- package management
- git repository
- automated testing
- community

5. issue queue
- based on http://dgo.to/project + Drupal 7
- multiple statuses, priority, components, notifications,
following etc
- issue moving to another project
- issue smart links [#123456-34@]
- file attachments & patch QA testing
- dreditor support for maintainers
- usefull projects dashboard
- full user profile integration with counters

6. documentation
- module docs can be integrated into drupal.org
global documentation infrastructure
- http://dgo.to/book module for docs hierarhy
- smart links for backlinking to issues
- documentation editors have counters in
profiles

7. change records
all commited feature requests should be
documented via http://drupal.
org/node/add/changenotice

8. package management
- automatic git tag package builds
- automatic tests for package versions
- tar & zip support
- package hosting
- drush support http://drush.org

9. git reposirory
- http://drupalcode.org web git repo viewer
- repository per project
- http://simpletest.me support
- git patch attribution (use dreditor for commit
message creation)

10. automated testing
- http://dgo.to/testbot
- http://qa.drupal.org testbot farm
- patches, uploaded into issue with “Needs
Review” status tested automatically. If fails ->
status changed to “Needs work”

11. community
- irc chats with Druplicon bot http://dgo.to/bot
- #drupal-contribute room power
- #drupal-infrastructure support
- 10000+ developers using issue queue
- all *.drupal.org can be changed via “Create
issue” request

12. visualization how-to

15. New iss
ues afte
r release

16. ervice:
module +
external s econds) drupal +
ting
0s
anual tes
fast(10-3
stall for m
h in
apply patc
if t
patc est fail
s
h
re-t can be
este
d
manual
re
with dre view
ditor
qa.drupal.org status log
user attribution!!!
ctrl-c

17. no tests - no commits!!!
all code should be covered by tests before
commiting patch.
Maintainer is not module coder, but tests
hacker and patch reviewer
all commits should be authored for user
uploaded patch

18. issue queue management
Code standards https://drupal.org/coding-standards
How to create patch http://drupal.org/patch
Project Statuses https://drupal.org/node/156119
Priorities https://drupal.org/node/45111
Issue queue handbook https://drupal.org/node/317
Issue tag guidelines https://drupal.org/node/1023102

19. projects waiting for You
https://drupal.org/taxonomy/term/9990
~1392 modules looking for co-maintainers

20. Questions?
Andriy Podanenko
Drupal Trainer
Architect
Developer
Modules maintainer
http://druler.com/drupalgive
http://dgo.to/@podarok