Unmaintained/Abandoned Modules
Hi everyone, Can somebody tell me what the proceedure is with unmaintained modules? Specifically Im talking about the Invite module -- It *appears* that the author is not contactable and does not look like the module is being maintained. (his last activity on drupal.org was in march) I've been working on the module, and have fixed a number of bugs and made some improvements but don't know how to go about getting them included/reviewed for this module. I would be happy to take over the maintenance, or commit as a new module -- whatever is the norm. thanks -- Nick Wilson http://performancing.com/user/1
Can somebody tell me what the proceedure is with unmaintained modules?
Out of the 929 module directories in contrib I only managed to generate 879 package files. This is not counting directories with multiple modules. Some directories are blank others have changed their name and are duplicated now and a lot of them contain errors. Cleaning this up will be a great aid in getting the dependency system done. -- Nick Lombard +27 82 413 9931 www.jigsoft.co.za
Nick Wilson wrote:
Can somebody tell me what the proceedure is with unmaintained modules?
Asking at this list is the right thing.
Specifically Im talking about the Invite module -- It *appears* that the author is not contactable and does not look like the module is being maintained. (his last activity on drupal.org was in march)
Robert Douglass seems to act as a de facto maintainer.
I've been working on the module, and have fixed a number of bugs and made some improvements but don't know how to go about getting them included/reviewed for this module.
Use the issue tracker to upload patches.
I would be happy to take over the maintenance, or commit as a new module -- whatever is the norm.
The norm is to add patches to the issue tracker for the maintainer to review. http://drupal.org/project/cvs/20967 makes me believe that Robert will review patches. Cheers, Gerhard
* and then Gerhard Killesreiter declared....
The norm is to add patches to the issue tracker for the maintainer to review. http://drupal.org/project/cvs/20967 makes me believe that Robert will review patches.
That's great, from the patch que it looked like no one was there -- but i never thought to look at cvs, so will upload a patch and ping Robert thanks! -- Nick Wilson http://performancing.com/user/1
The invite module seems to be currently abandoned. Robert did some stuff on it a while back, and I wanted to take temporary ownership of it for integration with adsense and user points, but that is a client project that is now delayed. I would say that if Nick Wilson wants to take ownership, or at least be allowed to have commit access, then give him that now.
* and then Khalid B declared....
The invite module seems to be currently abandoned.
Robert did some stuff on it a while back, and I wanted to take temporary ownership of it for integration with adsense and user points, but that is a client project that is now delayed.
I would say that if Nick Wilson wants to take ownership, or at least be allowed to have commit access, then give him that now.
Well, i've submitted the patch as it stands http://drupal.org/node/76632 and have cc'd Robert -- Nick Wilson http://performancing.com/user/1
That'd be great! I'd like to keep commit privileges, but if you want to be the official maintainer, please do. I outlined my vision for the module in the issue queue, and Khalid had some very interesting ideas to add, so it would be especially great if we all agree on the direction. -Robert Nick Wilson wrote:
* and then Khalid B declared....
The invite module seems to be currently abandoned.
Robert did some stuff on it a while back, and I wanted to take temporary ownership of it for integration with adsense and user points, but that is a client project that is now delayed.
I would say that if Nick Wilson wants to take ownership, or at least be allowed to have commit access, then give him that now.
Well, i've submitted the patch as it stands http://drupal.org/node/76632
and have cc'd Robert
* and then Robert Douglass declared....
That'd be great! I'd like to keep commit privileges, but if you want to be the official maintainer, please do.
I'd be happy just to help out Robert, I could work with you to get some of these things done but leave the overall direction in your hands.
I outlined my vision for the module in the issue queue, and Khalid had some very interesting ideas to add, so it would be especially great if we all agree on the direction.
I can't seem to find that post... but yes, lets get agreement then get some of this stuff in there. Cheers -- Nick Wilson http://performancing.com/user/1
Here is what I did: - Made Nick Wislon the owner of the project node (and hence gets cvs access too). - Keep Robert's commit access as it is. Regarding the ideas I had, I think they were in emails between Rob and I. In a nutshell, from memory, they were providing hooks that can be called at certain points, and hence modules get notified. For example if someone invited someone else, they can get a portion of adsense's page views. Also, when someone invites someone else they get user points, and when the person actually registers they get more points. As I said, the client has not given the green light for the project, so this is currently on hold.
* and then Khalid B declared....
Here is what I did:
- Made Nick Wislon the owner of the project node (and hence gets cvs access too).
- Keep Robert's commit access as it is.
Ok thanks Khalid, i'll work on getting some of these fixes done in cvs and email with Rob (and you if you like) before putting anything out properly.
Regarding the ideas I had, I think they were in emails between Rob and I.
In a nutshell, from memory, they were providing hooks that can be called at certain points, and hence modules get notified.
For example if someone invited someone else, they can get a portion of adsense's page views.
Also, when someone invites someone else they get user points, and when the person actually registers they get more points.
like an inviteapi() function right? Sounds good to me, i actually need something like this with what im doing right now, so will look into how to do it and talk to you about that... -- Nick Wilson http://performancing.com/user/1
Regarding the ideas I had, I think they were in emails between Rob and I.
In a nutshell, from memory, they were providing hooks that can be called at certain points, and hence modules get notified.
For example if someone invited someone else, they can get a portion of adsense's page views.
Also, when someone invites someone else they get user points, and when the person actually registers they get more points.
like an inviteapi() function right? Sounds good to me, i actually need something like this with what im doing right now, so will look into how to do it and talk to you about that...
Here is my email to Rob from May, it outlines my ideas. ---------- Forwarded message ---------- From: Khalid B Date: May 23, 2006 12:37 PM Subject: invite module vs. referral module To: Robert Douglass Hi I am thinking of deprecating referral module in favor of invite module, now that it has hooks that I can use in adsense and userpoints. This avoids code duplication and user confusion. My questions are: 1. Do you plan on having an insert argument to the invoke all that happens when a user registers? I need this to award points when a user invites someone else, and that new person registers. module_invoke_all('invite', 'register', $args); module_invoke_all('invite', 'insert', $args); I see from the code that I can use 'escalate' since it is called indirectly from invite_save(), but would rather have a specific. 2. Do you have somewhere I can call at any time to query whether a certain uid was referred by another? I need this for adsense to be able to split the revenue sharing if the user was referred by another user. Perhaps an invite_invite() function? 3. When is a stable 4.7 release of invite expected? Regards
* and then Khalid B declared....
Regarding the ideas I had, I think they were in emails between Rob and I.
In a nutshell, from memory, they were providing hooks that can be called at certain points, and hence modules get notified.
For example if someone invited someone else, they can get a portion of adsense's page views.
Also, when someone invites someone else they get user points, and when the person actually registers they get more points.
like an inviteapi() function right? Sounds good to me, i actually need something like this with what im doing right now, so will look into how to do it and talk to you about that...
Here is my email to Rob from May, it outlines my ideas.
Thanks Khalid, im working on clearing some of the more urgent issues, then will take a look at all this and discuss. -- Nick Wilson http://performancing.com/user/1
participants (5)
-
Gerhard Killesreiter -
Khalid B -
Nick Lombard -
Nick Wilson -
Robert Douglass