Best practices in contrib development and support
Presented by
Contributed modules and themes are fundamental to the Drupal experience, but the quality varies oh, so widely.
How can we improve our development process, keep modules maintained, help maintainers, and somehow harness the explosion of modules.
This forum will cover:
- What's expected of a module maintainer
- How to get help from others
- Finding maintainers, abandoning projects, dealing with abandoned projects
- Best practices in CVS (or Git!), including when to branch, and how to maintain branches
- Best practices in patch issue work flow
- Best practices in the issue queue: How to enlist the community, deal with support, and deal with newbies.
- Avoiding duplication in contributed projects
- Namespacing your module, your files, and your functions
- Module test coverage and issue testing with qa.drupal.org
- Documentation and coding standards
This will be an open discussion of how we can continue the great tradition of contributions, while improving the quality and user experience. Your thoughts are welcome!
Follow along with our presentation: https://docs.google.com/present/edit?id=0ASq3jhAyVqlqZGZxdmN2bWJfOTVnOGd...
Industry: education, entertainment, library, marketing, media, non-profit
Bakery Single Sign-On System
Browscap
CCK Latitude Longitude
Comment Notify
Documentation
Email Registration
Mail Comment
Maintenance Helper
Meez Integration
microsummary
Moneris Payment Gateway for Ubercart
Nofollow List
Omniture Integration
Pathauto
Phorum Converter
Porter-Stemmer
Prediction Markets
S5 presentation player
Sandbox
Talk
Term statistics
Text Link Ads Integration
Token
Tokenize
Ubercart Alternative Price
User merge
User Points Contributed modules
User Quota
Utility
Accurate Read Count
Admin links
Admin my content comments
Admin Role
Administration menu
Anonymous Contact
Atom
Autocomplete username
Bad Behavior
Bio
CCK Date Testsite
Checklist
Code Filter
Coder
Comment alter taxonomy
Comment RSS
Contact
CVS deploy
CVS integration
Database Administration
Devel
Devel
Diff
Disemvowel
Documentation
Documentation
Domain XML sitemap
Drupal Documentation
Drupal.org customizations
Drupal.org Testing
DUMMY Update test module
Earth Hour
Elements
Examples for Developers
Feature
Feedback
FeedBurner
Filter allowed protocols
Flood control
Form
Global Redirect
Google Friend Connect
Google News sitemap
Gravatar integration
Install Profile API
Local Menu
Location
Logging and alerts
Mailing lists subscription
Module supports
Module taxonomy
Mollom
oEmbed
OG Project
OpenSearch feed
Organic groups
Override Node Options
Panels header panes
Password change confirm
Path redirect
Pathauto
Poormanscron
Popularity
Project
Project CVS instructions
Project issue tracking
Project issue voting
Protection
Resource Conflict
Restricted content
Role inheritance
Sandbox
Sandbox
SEO Checklist
Signup
Signup Status
Simple Access
Site verification
Statistics Advanced Settings
Stumble
Subscriptions
SuperSearch
Theme Settings
Token
Ubercart Bought together
Ubercart Heartland Payment Systems
Update Status
Update status advanced settings
Update status advanced settings
URL alter
User status change notifications
Vertical Tabs
Views
Views Plugins
Wedding site
XML sitemap
For context, this is the combined contrib modules maintained by Greg (greggles), Derek (dww), and myself. Wowzers.
Great to see this panel! In addition, i think collaboration in contrib is an important topic to cover, maybe a bit more than is covered here. As the field gets more crowded, as more modules become as important as core (and potentially belong in core), it becomes necessary to think like core in contrib-- and above all, that means collaboration. And that's not easy, so looking forward to discussion on it!