Twitter: @heyrocker
Website: heyrocker.com
So you’ve finished your module, waited six months for your CVS account, spent six months figuring out CVS, gotten dww to delete your first aborted attempt at creating a release, and finally got your node created and your module available for download on drupal.org. Congratulations! You’ve just become a project manager!
Many people get excited about the prospect of releasing their code for the public to use and creating the next Views or CCK. What most people don’t realize is that as a module becomes more popular, the act of maintenance becomes as much (if not more) about project and resource management as it does about code and engineering. This session will talk about a variety of topics related to your new release including
Manging your issue queue
Lowering the barrier to contribution
Balancing new features with maintenance
Thinking ahead and planning for the future
Responsible release strategies
What to do when greggles calls you out for releasing a duplicate project
This talk will be targeted at intermediate to experienced developers who are interested in releasing their code to the public, based on my experiences maintaining the Deploy and Services modules.