Closed (won't fix)
Project:
Invite
Version:
6.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2009 at 18:54 UTC
Updated:
19 Apr 2009 at 20:58 UTC
It seems like the maintainer is not actively working on this module anymore. There are many support/patch threads unanswered for months. If this is abandoned, I like to work on this module as the new maintainer. Please let me know.
Comments
Comment #1
neokrish commentedSince the invite module is an integral part of dcl_importer, both modules needs active development. But both of them are now stalled for many months with no reply on the support thread/ nor applied the community submitted patch. I am taking up dcl_importer and will be interested in taking up invite module also for better integration of both these modules.
thanks,
neokrish
Comment #2
neokrish commentedComment #3
avpadernoIt should be better to leave the report open in the project issue queue for two weeks.
Comment #4
neokrish commentedYes, sure.
Comment #5
avpadernoIs the project still maintained?
Comment #6
sunYes, it is.
See #406472: Is INVITE module still being maintained?
Comment #7
avpaderno@neokrish: If you think you can contribute to the module, you can ask to become co-maintainer.
Comment #8
neokrish commentedPls correct me if I am wrong here. If I understand correctly, the module maintainer has to reply to this thread that he is still interested, right?
I looked at the thread referred by sun (54136) even before I started this but I think it was closed without maintainer's response.The invite is maintained by smk-ka (user 48898) but he hasn't replied to the thread Is INVITE module still being maintained? posted a month before but was closed. I contacted the maintainer via contact form for helping him maintaining the module as co-maintainer (a week ago) but he has not replied back.
For these reasons, I am setting this thread back to active and marking it for drupal.org webmasters's attention again.
Comment #9
avpadernoWhat you said is correct: the mantainer has not replied to that support request. I wonder how the project is still considerated active, if the code has not been updated, in the last times.
Comment #10
webchicksmk-ka and sun are bothers, so I'm sure that sun knows of smk-ka's whereabouts and intentions.
I only see one RTBC patch in the queue, which is less indicative of an inactive maintainer, and more indicative of a lack of contributors submitting and reviewing useful patches. If it becomes a situation where there are 40 RTBC issues that have been sitting there for months, then that's a bit more serious.
For now, I'd suggest that the best way to help Invite module along is to submit and review patches to fix the bugs you need fixed. If you do this often and thoroughly enough, you may even be granted co-maintainer perms by the maintainer, so it's win-win.
Comment #11
avpadernoAlso, none of the developers replied to that support request.
The last commit has been done 22 weeks ago.
Comment #12
avpadernoI am sorry for the cross-posting.
Intentions are one thing, the facts are another one; the code has not been updated in 22 weeks, and the maintainer has not committed code in more time.
I agree that neokrish can always ask to become co-maintainer.
Comment #13
avpadernoAs neokrish stated, he would like to actively help in the development of the module; he could become co-maintainer.
Comment #14
webchickBut as sun said in http://drupal.org/node/406472#comment-1385072,
I'd have to agree. I'm not sure why someone who's active in the Drupal community would hand over maintainership rights on a promise/desire. After seeing several patches and reviews? Much more likely.
Comment #15
sunhttp://drupal.org/node/310775#comment-1494792
Sorry, this won't fix for now. Feel free to re-open this issue when you are familiar with Drupal's coding standards, issue statuses, and project maintenance in general. Best practices for co-maintaining projects might be a good starting point to get up to speed.
Comment #16
sunEven better. #310775: Duplicate email causes nasty warning was a duplicate of #317040: Inviting a single existing email address results in error where the "real" maintainer provided a patch that just needed another push... Hrm.