Getting back to this subject, developers here have suggested that contributed modules should, ideally, have a co-maintainer. Others have suggested max-time-limits for 'ignored' modules before they are allowed to be adopted. Since Drupal is all about flexibility, what about gathering a little more info from developers at the time they request a CVS account? The current CVS app is pretty sparse http://drupal.org/cvs-account Here are some suggested additional questions: * Alternate email address in case your main email is broken. This email address would be visible to only Drupal management. * Drupal usernames and email addresses for your module co-maintainers * How should we proceed if someone not on the list above applies to be a co-maintainer for your module? (radio buttons with options) * How should we proceed if we are not able to contact you within (some time limit) and your module needs attention? (radio buttons with options: possible suggestions below) 1. Put your module up for adoption and remove you as maintainer 2. Allow another person to be added as co-maintainer but keep you as maintainer * What should the time limit be? (radio buttons with options) Comments? Suggestions? Thank you! Jill Elaine ---- discussion below as reference ---- Robert Douglass wrote:
Personally, I think that modules should have deputy maintainers or co-maintainers. This should be done by module maintainers just by talking to the other people interested in their work and selecting one to have "emergency" CVS access. Most of my modules have a clear 2nd (and sometimes 3rd) in line. I'll review the rest and find more people for the rest.
Larry Garfield wrote:
On Thu, 11 Jan 2007 06:48:47 -0800, Jill Elaine <jillsemail@bendbroadband.com> wrote:
As maintainers of modules, what do you think this procedure should be?
For instance, with your module, what would you like to see happen if you were 'run over by a truck' and disappeared from the Drupal world? ** What would be a reasonable set of steps so that your module continued to be maintained?
Try to get a hold of me via my contact tab, this list, and/or #Drupal. (Some busy maintainers may mention that they're disappearing for a while but will be back in IRC, and someone may remember that.) Some module readme files also contain contact info that can be used.
** What is a reasonable length of time to wait for a response from you?
Most contact attempts can probably be replied to within a week. I think a month is a not-unreasonable amount of time before someone can be considered "potentially dead".
** Who should be contacted if your profile is set to 'no contact'?
Site admins can contact someone even if they're contact tab is off. That said, I personally think it's irresponsible to have the contact tab off if you are actively maintaining a module.
** What else needs to be considered here?
What lack of contact is considered dead? No contact at all? Just no issue queue progress? What's the difference between vanishing and just vanishing from the issue queue for that module, but not others? Or not from working on core? What about temporary adoption if someone is going to be away for several months for some reason (long vacation, military service, etc.)?
--Larry Garfield