dba.module maintenance?
while we're talking about contrib modules that we wish were being more actively maintained, what's up with the dba.module (database administration, http://drupal.org/node/8482)? this is one of the most useful modules in contrib, IMHO. there hasn't been a commit in over 4 weeks, the 4.7 port isn't done, there are quite a few active tickets that haven't gotten any attention in longer than that, and i've got a minor RTBC patch from 9 weeks ago that still hasn't gone in. anyone seen jeremy@kerneltrap recently? ;) jeremy, if you're still around and too busy to deal with dba (i know we're all too busy), would you be willing/interested in a granting cvs access to anyone else to help maintain it? i'm already spread way too thin, so i don't want to actually become the maintainer. however, i rely on this module so much (and already know the code well enough to have submitted some patches a while ago that were committed), that i'd be willing to help commit patches. any other volunteers? anyone available to roll a patch for a thorough port to 4.7 (http://drupal.org/node/59073)? thanks, -derek (dww)
Op maandag 22 mei 2006 09:30, schreef Derek Wright:
would you be willing/interested in a granting cvs access to anyone else to help maintain it? i'm already spread way too thin, so i don't want to actually become the maintainer. however, i rely on this module so much (and already know the code well enough to have submitted some patches a while ago that were committed), that i'd be willing to help commit patches.
Though I agree that DBA is a very nice module, I think "radomly" granting access is a very bad idea. the maintainer is the one and only respsible person. He/she is the one we can point to in case of security holes or issues etc. So I think we should either leave it as it is, or kindly ask Jeremy to hand over maintainership to somone else. Then that someone else can choose to grant others access! Bèr -- [ End user Drupal services and hosting | Sympal.nl ] CVS onder de knie krijgen: http://help.sympal.nl/cvs_onder_de_knie_krijgen
On May 22, 2006, at 3:05 AM, Bèr Kessels wrote:
I think "radomly" granting access is a very bad idea.
so do i... that's not what i proposed at all. :) i asked: a) if anyone's seen jeremy and b) if jeremy is reading this thread, what does he think of granting a few other people (e.g. me and perhaps another qualified developer) cvs access to dba.
He/she is the one we can point to in case of security holes or issues etc.
right. and i certainly value (and then some!) all the work jeremy has put into dba so far. however, for whatever reasons (all of which are probably valid and good, and who am i to judge, anyway?), he hasn't been able to do anything with this module for over a month. there's a backlog of issues piling up... especially given that 4.7.0 is out and the module still doesn't fully work in 4.7.
or kindly ask Jeremy to hand over maintainership to somone else.
i'm not trying to take over, i'm just offering to lend a hand. i'm also fishing for other volunteers who might offer to lend a hand, and/ or information about the current maintainer (e.g. "oh, dww, you idiot, don't you realize jeremy is really 'xyz' on IRC, and he already told you he was going to be gone on vacation for 6 weeks?"). ;) -derek
On 22 May 2006, at 12:47 PM, Derek Wright wrote:
a) if anyone's seen jeremy
Jeremy is on holiday last I heard. -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
On Mon, 22 May 2006 00:30:51 -0700 Derek Wright <drupal@dwwright.net> wrote:
while we're talking about contrib modules that we wish were being more actively maintained, what's up with the dba.module (database administration, http://drupal.org/node/8482)?
It is in need of some loving, something I've been planning for months but haven't had/made time for as of yet. There is a TODO list in the CHANGELOG of known issues remaining to get it fully working with 4.7. As for an official 4.7 release, I was hoping to do some cleanup of the underlying logic while retaining functionality -- the code is too messy. Patches to either end are welcome. [snip]
and i've got a minor RTBC patch from 9 weeks ago that still hasn't gone in. anyone seen jeremy@kerneltrap recently? ;)
Oops. I've been on vacation this month, and will be until early next month. I've obviously been neglecting the issue queue.
jeremy, if you're still around and too busy to deal with dba (i know we're all too busy), would you be willing/interested in a granting cvs access to anyone else to help maintain it? i'm already spread way too thin, so i don't want to actually become the maintainer. however, i rely on this module so much (and already know the code well enough to have submitted some patches a while ago that were committed), that i'd be willing to help commit patches. any other volunteers? anyone available to roll a patch for a thorough port to 4.7 (http://drupal.org/node/59073 )?
I too rely on this module, which is why I wrote it. It's not one I'm looking to pass on maintainership of, though I'd certainly welcome help in improving the code, the user interface, etc... Anyone interested in CVS access to help with my goals outlined above can ping me offline. I'm not interested in people who plan to just blindly commit patches from the queue, though someone whose primary focus is getting the module 100% functional with 4.7 would be welcome. Cheers, -Jeremy
participants (4)
-
Adrian Rossouw -
Bèr Kessels -
Derek Wright -
Jeremy Andrews