The Taxonomy List module was owned by BoogieBug. According to tracker, he hasn't posted a thing on DO in over 38 weeks, and that was the last update to the module.

What would be involved in taking over the module? If he ever comes back, I'd certainly be willing to return it to him.

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Forgot to mention, I wrote him an email a week ago and it has not been answered.

AjK’s picture

AjK commented
Status: Active » Fixed

Project transferred. Note, I left BoogieBug on the CVS access list just so we remember who it was in 6month time.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I should have suggested that. Thank you very much.

heine’s picture

heine commented
Status: Fixed » Active

The procedure for these transfers is supposed to be:

1. Post an issue in the modules' issue queue regarding the transfer/requesting (co) maintainership.
2. When two weeks go by without a response, move the issue to the webmaster queue.
3. Transfer project.

AjK’s picture

AjK commented

@ Hiene: Yes, true, I am aware of that proceedure. However, when a user's track shows no sign of usage for an extended period, no commits made to a project for an extended period, a growing unmagaged issue queue is in place and there's an offer of help right now from another maintainer who has the exact opposite record, I'm inclined to "move things along" by allowing access rather than stagnate.

I work on the simple assumption that CVS, as a versioning control system, allows for rollback and thus protects you against "commits you'd rather not have had".

I think handing may have been a little premature but I still think making nancyw a co-maintainer to move it along is valid.

Comments?

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I did email him; true it has not been two full weeks, and true it was not posted in the issue queue. I was not aware of the procedure, but now I am.

I will, if it's okay with both of you, still work the issue queue. I already have it ported to 6.x and just need to tell my CVS that it's okay. I am familiar with another important issue that's out there, since I'm the one that told the person what to patch.

If you would prefer I will hold off feature requests for a while longer and just concentrate on bugs.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

http://drupal.org/node/232788

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Well, if or when I get commit authority, the issue queue will go almost completely away overnight.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

I'm with AjK on this. If a module looks long abandoned and someone with a good track record has an itch to work on it, I think making them wait two weeks is silly. I think it's better to take this on a case by case basis with what Heine said as the standard method but making exceptions as needed.

Michelle

heine’s picture

heine commented
Status: Active » Fixed

I cannot speak for other maintainers, but getting a mail from the issue queue mailer is more likely to get registered then a mail by some random drupal.org nut.

Either stick with the agreed workflow, update it, or abandon it. For another issue queue though.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Fixed » Active

I have posted the request in the module's issue queue per the policy. The link to it is above. Unless you're telling me that I won't be allowed to take over this module, then the issue is still active.

I'm sorry that I offended your sensibilities. As I said, I was unaware of the policy. If you can tell me where to discuss it, I will be happy to suggest changes to the policy. When it is clear that an owner is not paying attention the issue queue (or drupal.org in general) it would seem that a direct email would be appropriate.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

When it is clear that an owner is not paying attention the issue queue (or drupal.org in general) it would seem that a direct email would be appropriate.

The problem with a private mail is that it's private. Public issues have the benefit of being obvious to all parties involved since they are public.

So, you said that you mailed them a while ago and while I may trust you about this, it's hard to verify that as a fact. If you posted a public issue then it's quite easy to say "yes, Nancyw posted a public issue and the maintainer hasn't responded for two weeks."

So, let's give it another week and then transfer ownership.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

Indeed, since it was sent through the contact form here at DO, I have no copy in my sent mail folder.

I am waiting and have all the issues fixed.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Active » Closed (duplicate)

http://drupal.org/node/232788, to be transferred here momentarily.

Project: Drupal.org site moderators » Drupal.org project ownership
Component: Project ownership » Ownership transfer