As per http://drupal.org/node/251466:

1. Last commit to this project was 34 weeks ago in Jan.
2. 72 bug reports and growing, 213 open issues and growing
3. Several major bug reports that completely break the module or the rest of Drupal (just take a look at http://drupal.org/project/issues/gallery?categories=bug)

I'd like to know if this module is still maintained because it does not seem that way at all. If we don't hear back from the maintainer within two weeks I'll have to put this module up for adoption.

I have the same concerns for http://drupal.org/project/gallery_addon as well.

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Title: Is this module still being maintained? » Is Gallery module still being maintained?
Project: Gallery » Drupal.org site moderators
Version: master »
Component: Miscellaneous » Project ownership
Assigned: Unassigned » dave reid

No response in two weeks (really more than that but I waited to create this issue)...moving to the webmasters queue and marking the module as abandoned.

Project: http://drupal.org/project/gallery and http://drupal.org/project/gallery_addon

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed

Module marked as abandoned.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Any for anyone wondering why I abandoned such a popular module, it's because the maintainer has failed to respond to e-mails about other modules that have been marked abandoned, and there are some major Drupal-breaking bugs with the module that are just not fixed. Plus, I followed the procedure.

profix898’s picture

profix898 commented
Status: Fixed » Active

As mentioned in http://drupal.org/node/593984#comment-2144630 I didnt have time to properly maintain my modules. However, in case of Gallery and RepTag I'm still/currently working on updated versions.
For Gallery the module has to be rewritten from scratch to get compatible to development branch of Gallery 3. I'd be happy to have someone supporting gallery module development (especially the 6.x version for Gallery2), but asking for help for half a year didnt reveal anybody ...

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@profix898: Also see #552994: Maintenance? ThemeKey appears to be abandoned. Two different people tried to e-mail you personally about your modules before they were transferred. Your website was down and we didn't hear anything back from you. Each of these module transfer issues has started in your module's issue queue so you had plenty of opportunity to respond to them.

I don't have a problem with moving ownership of gallery back to you. But what I do have a problem with is leaving the latest stable release out when has *lots* of critical, Drupal-breaking bugs in it. People are posting issues in the module's queue regularly and no one ever hears back from you. Do you intend to support the current version of the module or not? If not, you should mark the release as unsupported.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

If you are still working on modules, then you should be committing changes to CVS on the current branch or a new branch. This lets users know that you at least are working on it instead of nothing.

profix898’s picture

profix898 commented

But what I do have a problem with is leaving the latest stable release out when has *lots* of critical, Drupal-breaking bugs in it.

Who said that the module contains lots of Drupal-breaking bugs? I'm using the module on two sites of my own and it works nicely. Looking at the statistics for gallery there are over 3000 sites using the 6.x-1.0 release, so obviously it is not that bad ...

People are posting issues in the module's queue regularly and no one ever hears back from you.

As long as nobody feels comfortable in helping out, I dont think I can actually do much about it. Yes, this is a bad situation. However, many of the requests have been answered before and I really believe in the community being able to solve some problems themselves.
I can try to spend a little bit more time on Drupal, but I'm sure I just can't answer requests in the queue on a regular basis (daily/weekly). I'm currently focused on getting compatible with Gallery3 leaving no free time for the queue. Sad but true.

I guess, you can choose ...
A) having the module abandoned completely
B) having the module put into a holding pattern, with a new release every half a year (or sth.)
There is no other option for/with me atm. Sorry!

Regards, Thilo

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Fixed

I am fine moving the project back to you.

But you say you are working on code with Gallery 3. So...create a new CVS branch and start committing code. At least give people looking into the module some indication that it is not abandoned since you aren't able to reply in the issue queues. Find an interested co-maintainer or two (again, co-maintainers will need access to latest code so see above point about code).

lvthunder’s picture

lvthunder commented

The main holdup is the developers of Gallery 3. They originally said G3 would be out in February. It's still not out yet. That said I'm trying to help out in the issue queue here but I'm not a coder so I can only help people that are having problems that can be worked around. Now my question is if there is an issue that's been sitting there for a year or so what is the correct procedure to close those issues as I doubt those people are still waiting for an answer?

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

If issues waiting for a long time haven't had a response from a maintainer they should not be closed. Leave them open.

lvthunder’s picture

lvthunder commented

What about issues that have had a response asking for more information, but they never responded back.

vm’s picture

vm commented

Issues where the OP did not follow up on information requested can be closed, IMO.

slurpee’s picture

slurpee commented
Priority: Critical » Normal

I have interest in helping with this module.

I am using it my personal site and love it.

Drupal has no way to mass importing many photos from a local server.

michelle’s picture

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

I, unfortunately, can't offer any time to maintain Gallery but I can attest that it does work. I'm using it on the La Crosse Area Camera Club site with no problems at all.

Michelle

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

It doesn't seems that profix898 is even checking the project page to see if there are new issue reports; if he would have done it, he would have noticed the message in the page.

joachim’s picture

joachim commented

Quicksketch and I were discussing at DC that it would be good for the old image_gallery module from image module to have this namespace when image is broken up for D7; this could perhaps live at gallery2?

michelle’s picture

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

I don't think gallery2 is a good name because, hopefully, this will be updated for Gallery 3 at some point. Maybe "menalto_gallery"?

Michelle

Status: Fixed » Closed (fixed)

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

joachim’s picture

joachim commented
Status: Closed (fixed) » Active

Um?
Hello bot?

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

Issue was marked as fixed in http://drupal.org/node/586782#comment-2150934

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

The question about the project being still maintained has already found an answer. I agree with Dave that it could have been created the branch for the Gallery 3 version, but this is a different thing.

As replied from the maintainer, the project is not abandoned.

joachim’s picture

joachim commented

Ah sorry, I missed that bit.
I'll open a new issue regarding the namespace.

Status: Fixed » Closed (fixed)

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

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