Hi,
I just want commit access to apply patches that have been in the issue queue for some time now. I wrote an email to the current maintainer (Barry ) and his reply is below.

Eric,

You are right that I do not have time for Primary Term. I am happy to give it away completely (I was not the original author). Moshe Weitzman (http://drupal.org/user/23) and Mike Ryan (http://drupal.org/user/4420) already have CVS commit rights but I think they did not want official ownership, just the ability to commit fixes. However, I think of them as the de-facto owners.

So, I suggest you talk with them. If they are happy with you taking the module, I'll give it to you.

Thanks,

Barry

At 01:25 PM 11/20/2009, you wrote:

bjaspan,

ericduran (http://drupal.org/user/244460) has sent you a message via your
contact form (http://drupal.org/user/46413/contact) at drupal.org.

If you don't want to receive such e-mails, you can change your settings at
http://drupal.org/user/46413.

Message:

Hi,
I use the primary term module a lot. You don't seem to have time for it. Can
I co-maintain the module? I've submitted patches before and there's a couple
of pending issues on the issue pages that don't seem to get attention.

Thanks.

Comments

cels’s picture

cels commented

I would like you to have access to cvs and commit the fixes.

Send this email and the reply to Moshe Weitzman and Mike Ryan too (be polite is important).

moshe weitzman’s picture

moshe weitzman commented
Status: Active » Postponed

I would prefer a co-maintainer that has a longer track record with module maintainership. eric has one commit at this time. lets talk again once a longer reputation is established.

ericduran’s picture

ericduran commented

Hi Moshe,
I completely understand your desicion, but I think I've been pretty good at least at monitoring the issue queue for primary term and providing patches or ad-hoc releases (This is only because no-one was applying the patches).

At the moment there isn't a group of people trying to get commit access to primary term or at least anyone else for that matter so I don't really see the harm in giving me commit access since the alternate option is to wait for someone else to want to do it.

Thanks for reviewing the thread.

rmjiv’s picture

rmjiv commented

+1 The lack of attention this module is getting risks a fork of this project. I submitted a patch (http://drupal.org/node/372809) over a year ago and it was never responded to. We need some additional features, some of which other people have also asked for. I'm willing to do the work and commit the patches back, but only if there is some chance of getting them committed.

ericduran’s picture

ericduran commented

rmjiv,
I'm not sure they'll give you commit access because of the lack of module maintainer-ship. I've also provided patches which have not been committed. I guess a fork wouldn't be such a bad idea if no one is willing to take up the job.

rmjiv’s picture

rmjiv commented

Just to be clear, I don't want commit access, I want you to have it. :)

I think forking this project would be really unfortunate. But the reality is that I'm going to have to add a few features to this module to support my company's needs and if there isn't an active maintainer there isn't any point in my taking to the time to contribute them back. So I'm going to end up with a locally forked version of the project. And I'm guessing that I'm not the only one in this boat.

sethcohn’s picture

sethcohn commented

Agreed, I'm currently spending a lot of time using this module for a paid project, and would like to see _someone_ take over it. Can someone take responsibility for this?

moshe weitzman’s picture

moshe weitzman commented

since i have worked with seth before, i just granted him commit access on this project. long term, the maintainership issue here is unresolved still.

bjaspan’s picture

bjaspan commented

I remain happy to give this module to anyone who will take it.

sethcohn’s picture

sethcohn commented
Assigned: Unassigned » sethcohn
Status: Postponed » Closed (fixed)

I've emailed (and gotten positive replies) from Eric and rmjiv, and plan on clearing up the issue queue, getting all of the pending patches committed, and adding small new additions (an improved views filter is one I think I can get done)

Thanks Moshe for the vote of confidence!

Barry, thanks for taking this on when you did!

A complete rewrite for D7 is likely the next needed step, and perhaps if someone want to take that task on once we get things cleaned up for D6, they'd make the best choice as the new maintainer. Right now, that's beyond my needs or plans. (Same with D5, which I don't plan on supporting)

I'll close this ticket for now.

moshe weitzman’s picture

moshe weitzman commented

For D7, I think we just need a widget on term reference that nicely handles ordering. Its odd that core provides no such widget. I think only autocomplete would work for ordering out of the box. Thats a pretty good solution for huge vocabs that need a primary term.