The future maintainership of Multiping

This module hasn't received any official code updates since november 2008 - it's reasonable to believe that it's rather dead.

If it is then somebody would need to take over maintainer ship because Drupal needs a good ping module and especially so when Drupal 7 comes since then the one in core has been dropped.

I've been thinking about spending some time aiding in making the Drupal 6 version stable, but haven't had that time yet. Anyone who got time to spend on this module?

The original issue for the update to Drupal 6, which is still open, can be found here: #232400: Update MultiPing to Drupal 6

I suggest that we organize the discussion regarding how the actual update will be done in that issue and have this issue only be about the future of the maintainer ship of Multiping.

Updating the topic once again to make the content of this issue even clearer.

In accordance to the guidebook about Dealing with abandoned projects I want it to be clear that my aim is for this module to have an active maintainer - whoever that might become - and if the existing maintainers doesn't wake up before two weeks from now this will be moved to the webmaster queue.

If the existing maintainers do wake up - let us have a discussion regarding how this module can be best maintained :)

This is a polite request to Skyr, Takafumi, PineRay and dgtlmoon to ask if they are still maintaining this module?

Jonathan

Hi all,

unfortunately, I currently have very little spare time, and I have to admit that multiping is not a high-priority hobby project at the moment (I recently moved to a new town and at the moment, I even don't have Internet at my new home). At some point in time, the RSS feeds for project issues on drupal.org broke (at least I wasn't able to fix them), which made things even worse for me; and finally, dealing with CSV is (in comparison to svn and others) a real pita for me.

I feel bad for the couple of people who submitted patches and didn't get committed to the module's repository. I hope you accept my excuse :-)

I'd really like to see the module to continue to live. It started as a personal hack (not conforming to any Drupal code style guides, etc.) and grew step by step... I still think the module is a good idea, and it would be a pity if it would die just because of my lack of time.

So if anyone would like to take care of this baby - boldly step forward :-)

A "backup alternative" might be streamlining the process of submitting and including patches, although this would most likely mean to move away from drupal.org's CVS toward a distributes vcs site like github oder launchpad (my favourites at the moment ;) ). Even if I don't have time for active development - this would allow me to review patches and maintain a repository in an easier way (increasing the chances to get the work actually done).

Hi Skyr - nice to hear from you!

I would suggest adding me and jonathan1055 as co-maintainers of the 6.x and future version and that we all continue to discuss all changes in the issue queue before committing them to make sure that we all agree about the direction that multiping is heading.

About RSS - I think that it is working again - I'm using it on several projects.

Regarding git - I like it but I think it's more suitable for "staging" changes and modules before adding them to Drupal.org - the main development should be done here to avoid scattering the community that is one of Drupal's great assets. Let us hope that someone will make Drupal.org support git soon :)

Re-hi,

indeed - RSS seems to be working again (got notified via my feedreader :-)

I'd love to add the both of you as co-maintainers (including cvs access) - if I knew how to do that. When I made my request to add this module to the drupal.org repository, the project was created with a different project owner. Probably he's the one who can make such changes...

Seems like only the main maintainer can add new co-maintainers - in this case that would be dgtlmoon - I sent him a message about this issue.