Drupal contrib module maintaining

Drupal contrib modulemaintainingAndriy Podanenko @podarokhttp://druler.com/drupalgive

use cases

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

community grow

http://dgo.to/gmap16->73 developers ~18 month +15000 installs0->726 testshttp://dgo.to/location18->94 developers ~17 month + 20000 installs100->425 tests90% Critical and major bugs fixed by users!!!

drupal.org project management

- issue queue- documentation- change records- package management- git repository- automated testing- community

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

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

change records

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

package management

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

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)

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”

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

visualization how-to

New issues after release

qa.drupal.org status log

if test fails patch can be re-tested

manual review with dreditor

external service:

fast(10-30 seconds) drupal + module +

apply patch install for manual testing

ctrl-c

user attribution!!!

no tests - no commits!!!

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

issue queue management

Code standards https://drupal.org/coding-standardsHow to create patch http://drupal.org/patchProject Statuses https://drupal.org/node/156119 Priorities https://drupal.org/node/45111 Issue queue handbook https://drupal.org/node/317Issue tag guidelines https://drupal.org/node/1023102

projects waiting for You

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

Questions?

Andriy PodanenkoDrupal TrainerArchitectDeveloperModules maintainerhttp://druler.com/drupalgive http://dgo.to/@podarok