Is this module still being maintained? Asking as I've noticed that there hasn't been a dev release in almost a year, and there hasn't been maintainer activity in the queues since May. There are dozens of RTBCs and many Needs Reviews issues that could use some love.

Thanks,
Renee S

(following the guidelines here: https://drupal.org/node/251466, I pinged Karen S as well, but haven't heard back.)

Comments

Renee S’s picture

It's been almost two weeks, I'll flip this to the webmaster queue on Monday. Is anybody willing to take over co-maintainer status, committing patches and looking into bugs, even for just one branch or another?

DamienMcKenna’s picture

socketwench’s picture

Tempting...

Renee S’s picture

You would be a hero for closing all those buggy issues! :) And it wouldn't be a lifetime commitment - Date is in D8 core, so even a commitment of a few months to get these things dealt with would be invaluable. I think it's also important to say here that Karen S along with many helpers over the years have done an amazing job, this is a huge and important module, and it deserves to thrive :)

Dave Reid’s picture

Tempting here as well, but I probably shouldn't do it for my own health.

cafuego’s picture

I'll put my hand up, at least to deal with the RTBC issues and push out new -dev versions. I don't know that I can commit any time to longer term maintenance at this stage, but a little bit is better than nothing I guess and if someone else pipes up willing to do more, then just add them too.

I work on COD related stuff, so a working non-buggy Date module is pretty important for me.

Renee S’s picture

Project:Date» Drupal.org webmasters
Version:7.x-2.x-dev»
Component:Miscellaneous» Project ownership

Flipping this to the webmasters queue: the Date module appears to be abandoned. We've got an offer from cafuego who's willing to help out by taking on co-maintainer status to clean up the queues (thanks!), although we should keep looking for another one or two people for a bit further into the future as well.

https://drupal.org/project/date

tim.plunkett’s picture

I've removed myself from the maintainers list.

chx’s picture

I have added cafuego to the maintainer list although I didn't turn the project over to him yet and I am keeping this issue open in hope of more maintainers showing up for this important project.

cafuego’s picture

I don't need to be the owner of the project, just enough access to push and roll a new (-dev) release :-)

sreynen’s picture

How long are we leaving this open and what are we trying to accomplish in that time? Should #2074649: Mark Calendar as abandoned also be delayed?

For the past several months I've been processing most of the project ownership issues in this queue. I've never intentionally delayed anything beyond the 2 week response period documented in https://drupal.org/node/251466. I understand Date is a high-profile project, but I'm not clear on why that makes the process different. I would have thought more users on an abandoned project would make it only more important to notify users of the risk and notify contributors of the need. If there is a different process for high-profile projects, can we update https://drupal.org/node/251466 to describe that process? I'm not comfortable continuing to help with these issues without understanding the community guidelines.

Renee S’s picture

sreynen: From the sounds of it, chx is leaving this open because it does not have a maintainer. A volunteer has offered to do some clean-up and much-needed commits, but this (and Calendar) still need somebody to take them over. (eta: Ok, I see what you mean: why not make this abandoned and put a message on the module page? Yeah.)

Dave Reid’s picture

@sreynen: I don't think anything is being delayed. Renne S explains there is not actual maintainer assigned, so naturally this remains open. I don't see how what's being done here is different from the process and guidelines we've established.

tim.plunkett’s picture

KarenS has been known to not visit the issue queue for a week or two at a time, and depending on how you "pinged" her, she may not have gotten to it yet.

I don't think we need to explicitly write out guidelines for high-profile modules, but I think common sense dictates that a top 10 used module authored and almost singlehandledly maintained for SEVEN YEARS should not have their maintainership stripped in fourteen days.

chx’s picture

@tim.plunkett, we didn't strip anyone of their maintainership rights, we added help. That's how I see it, at least. It's not like we watched for a two week window where KarenS is on vacation or something -- the issue was opened because it's been so long since a commit was made.

chx’s picture

> How long are we leaving this open and what are we trying to accomplish in that time?

I think a few more days and we are trying to get more maintainers. The guidelines is just that: guidelines, they are not set in stone and with a module this high profile I am treading a bit more slowly before actually changing the node ownership to Abandoned. What is a high profile module? I know it when I see it :) We could debate for a long time whether 50K usages is such or needs to be 100K -- but I doubt that debate is helpful.

Also, thanks much for tending these requests. I didn't want to step on any toes.

tim.plunkett’s picture

I'm more than fine with adding a comaintainer, and I agree with chx's actions. I was addressing @sreynen. I think transferring maintainership without response from KarenS (who is still on IRC often and active in Drupal in general) is wrong.

Renee S’s picture

Tim, it's worth mentioning that I emailed Karen S two weeks before I posted the issue, as well, and received no response.

chx’s picture

To clarify further: as dev releases are rolled automatically, I only gave cafuego VCS write access. We can do more as we see fit. If there is no further development in a few days and he feels comfortable, I will give him maintain releases as well and then we go from there. Keep calm and carry on.

arlinsandbulte’s picture

I am a date co-maintainer, but I have not been very diligent lately.
And, I have not spoken with KarenS in a while either.

I am interested in continuing my co-maintainer role, but I don't feel qualified to lead the project.

sreynen’s picture

What is a high profile module? I know it when I see it :)

I was afraid that would be the answer. I see no problem with others making these judgements on a case-by-case basis, but I'm not personally comfortable doing that. It sounds like there's little interest in documenting new standards, so I'll leave this queue to those who don't need such standards.

chx’s picture

@sreynen please do not abandon the queue! There is no new standards, there never were. But if you need a hard rule for guidance: what about we wait more for the top 50 in https://drupal.org/project/usage ?

greggles’s picture

Title:Is Date abandoned?» Grant cafuego commit rights to Date module.
Status:Active» Fixed

I agree with sreynen. A policy should be followed. There are very few fully irreversible actions on drupal.org.

so naturally this remains open

What? There's no history or reason to keep an issue open until a maintainer is found. A project ownership issue has a purpose. That purpose is carried out and the issue is closed. Re-titling to make the purpose more clear and marking fixed.

@cafuego if you want or need more access to the project please re-open this issue explaining what/why.

I think transferring maintainership without response from KarenS (who is still on IRC often and active in Drupal in general) is wrong.

I don't think this is a focus of the ongoing discussion, but if you feel that way please open a new issue about changing the policy with some specific reasoning of why it is wrong. If it's wrong to do for Date it's wrong in other cases.

CatherineOmega’s picture

@greggles: But what do we actually do longer-term though? Is this project still effectively without leadership if not technically abandoned?

greggles’s picture

If someone wants to take over 100% maintainership of the project they can file an issue to do that and it can follow the process for unsupported modules.

Renee S’s picture

The module isn't marked as abandoned, though, so if that process isn't going to be followed, should something at least be posted on the project page indicating the need for maintainers?

greggles’s picture

If someone wants to mark it as unsupported or seeking (co-)maintainer they should follow the process on https://drupal.org/node/251466

greggles’s picture

Another way: if you feel that should still be done as part of this issue, please reopen it and re-title it.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Renee S’s picture

Title:Grant cafuego commit rights to Date module.» Find a primary maintainer for the Date and Calendar modules.
Status:Closed (fixed)» Active

The Date module still lacks a primary maintainer. (And, thanks much to cafuego for committing several essential patches!)

greggles’s picture

Status:Active» Postponed (maintainer needs more info)

That's a statement of opinion that might support some further action but it's not clear what action you want.

So...what action do you propose?

cafuego’s picture

Actually, I'd like additional permissions so I can change the project page and project status.

tim.plunkett’s picture

That probably should have been done already, fixed.

cafuego’s picture

Ta :-)

greggles’s picture

Status:Postponed (maintainer needs more info)» Fixed

OK, marking fixed again. If someone reopens this please state what you want to have happen.

Renee S’s picture

Status:Fixed» Postponed

"That's a statement of opinion that might support some further action but it's not clear what action you want." "If someone reopens this please state what you want to have happen."

It's not that unclear: this *was* an abandoned module issue. The correct protocol was to post it to the Webmasters queue after two weeks of being unable to contact the maintainer. I did that. It's been almost two months since I originally attempted to get in touch with Karen S. it's been over a month since this issue was moved to the queue. The next step in the abandoned module process was, as I understood it, to put on the abandoned module's page that it is *actually* abandoned. That never got done.

However! Thanks to tim.plunkett's change, @cafuego has now marked it "Needs co-maintainers", which works fine for me, and has updated the project page to point people towards this queue. Not sure if "fixed" is the right status, exactly: I've flipped it to "postponed," which seems to make more sense to me, but since we're off in the weeds here wrt how these things are supposed to proceed, who knows?

sreynen’s picture

I had the same expectation Renee S expressed in #36. However, the guidelines leave a lot of room for interpretation, which I hadn't realized until this issue. Step 8 says "If they agree with the assessment, they can then add a note" (emphasis added). So it's entirely up to webmasters whether or not to mark something as abandoned. Most webmasters here seem to think it shouldn't happen in this case. So in the context of this issue, I think "fixed" is the right status.

However, in the wider context of the issue queue, this issue has introduced a new problem: no one is attending the queue now. I think that problem deserves a new issue, which I would open myself but I don't really want to be involved in what seems likely to be an angry debate in that issue, after almost stumbling into it here.

greggles’s picture

Title:Find a primary maintainer for the Date and Calendar modules.» Mark Date/Calendar modules as unsupported

The main reason I don't have the expectation to mark it unsupported is because of the title of this issue. If we make the title match your expectations...now what is the right status?

Given that cafuego already has the ability to edit the page and status, I think an issue with that title/focus would become "won't fix" because there is a relatively active person with access to set the right status already. Leaving as postponed.

Renee S’s picture

Ah-hah: #2108697: Application for co-maintainer

I'm interested to be part of maintaining this module by actively monitoring issue queues and work on bugs & feature requests. I have used date module in d5, d6 & d7 and have a sandbox of date time utility (https://drupal.org/sandbox/vijaycs85/1345534) created for one my client project. - vijaycs85

dddave’s picture

It's been three weeks since the user posted the offer to co-maintain. Shouldn't we move this forward?

vijaycs85’s picture

As mentioned in #39, I'm still interested to become a co-maintainer.

dddave’s picture

Title:Mark Date/Calendar modules as unsupported» Assign Co-Maintainership [Mark Date/Calendar modules as unsupported]
Issue summary:View changes
Status:Postponed» Reviewed & tested by the community
chx’s picture

Why don't make vijaycs85 the primary maintainer instead of marking it as unsupported? With cafuego as a co-maintainer.

dddave’s picture

I am all for it. Should have been clearer in my update of the issue (I lack the perms to do so though).

cafuego’s picture

Sure, I have no privs to do it either, though :-)

chx’s picture

Status:Reviewed & tested by the community» Fixed

I transferred the Date module to vijaycs85. Calendar is a different issue.

vijaycs85’s picture

Thanks @chx.

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Project:Drupal.org webmasters» Drupal.org project ownership
Component:Project ownership» Ownership transfer