comaintainer for amazon module
MGParisi - April 14, 2009 - 17:49
| Project: | Amazon Module |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Eaton, Is this project Dead? There has been no updates for many months, and no upgrade path from AAT! Should we just upgrade AAT to 6.x?
#1
subscribe
#2
subscribe !
#3
@Eaton: I would be happy to help with maintaining this project, if you are otherwise occupied. (e.g. by incorporating the currently open patches).
I would be willing to give up co-maintainership if/when I am no longer needed.
#4
I was thinking of AAT -> 6.x
It needs some work beyond upgrading though.
There is a new version of AAT 5.x in the CVS, I just cant seem to get it up on the website... I am not sure why Eaton went away from AAT and branched it to this! But I know some of the code in AAT needs work, and features are limited.
#5
See my script in #231612-10: Upgrade path for Amazon associate tools module?: it should allow you to import your AAT nodes to the Amazon module, although more testing is needed. I think the codebase for this module is better than that for AAT - especially since AAT didn't use CCK fields. Also, I believe that the AAT module could cause Amazon terms of use violations, especially if the cron didn't run properly.
#6
Back to the original question--Is this project dead?
@Eaton, please don't tell us you've tired of this great module! I seem to remember something in your notes about being better than sliced bread? I'm really looking forward to that part<> And some of the questions/feature requests look very interesting.
Connie
#7
subscribing
#8
Opening an issue "is this project dead" is not the kind of behavior that I'd want to see from a comaintainer.
If you want to be a comaintainer the best thing to do is go through the issue queue and make sure everything you would apply is in perfect shape. Create an issue "issues to fix before 6.x-1.0 final" and lay out a battle plan with links to all the issues. Mark everything that you feel is ready to go as "Reviewed and Tested by the Community." That proves your potential skill as a comaintainer and gets you in a perfect position to actually maintain the module.
When I look at the queue, I don't see anyone in a position to really step up so if I were eaton I wouldn't change anything: the module works relatively well. A good maintainer who is absent is better than an active maintainer who is doing it wrong.
#9
@greggles: This issue has not been opened to apply as co-maintainer - it was a (in my eyes fair) question by MGParisi whether there will be any more development to this module or not.
I ussed this issue to offer my help - I dont necessarily want "real comaintainership", only apply outstanding patches and stuff to help out. It's been a courtesy because I am using this module - nothing more. (EDIT - sorry - But I agree - it would be better to first go through the issue queue, make a list of patches, etc - but thats a hell of a lot of work w/o even knowing whether the maintainer will answer the issue. So: First state 'Yes, I'd be willing to accept co-maintainers.', then I will do this (or more then happily leave it to someone else ;) ))
Apart from that: A good maintainer who is absent is no maintainer. There are a couple of issues that should be fixed, there are a couple of patches that should be applied (e.g. patch to fix ASINs beginning with a '1'), etc
Now imagine that s/o really needs this module for some reasons - The only alternatives present ATM would be a) opening a new module (plain ugly), b) offering co-maintainership (did so) and fix outstanding bugs or c) maintaining an ever-growing list of patches (plain ugly).
Dont get me wrong - this is not meant as critic to Eaton. It is a great module and he is not bound to go on maintaining it - but it would be nice if he could say one or two words so people know what to expect.
#10
As far as I can tell, the only critical patch to be applied is the one for ASINs beginning with a 1. But maybe I haven't used the module long enough to know of others. It would be great if there was a way just to get that one committed.
#11
The patch that converts 13 digit isbns into 10 digit asins is an excellent patch, too.
Connie
#12
Me and Eaton have a very good relationship. I maintain the old AAT, and he has this new module. I am migrating to 6.x, and thus am going to need to update to his module. I am also closing out 5.x AAT with the last version posted today. If development for AAT wants to continue, thats ok, but I know Eaton's approach is the right way. Second of all, AAT needs so much work to make it run right. Its needs allot of work, more then I can provide. I also do NOT want to see two different Amazon Modules. If you pay attention to the Amazon modules of 5.x, there is about 5 modules that all try to do the same thing, Yet none of them do it very well, and none of them continue to work as well as they should. Now I know Eaton well enough to know that he has ALLOT on his plate. If he developed this module to the point that it meets his needs, and can no longer push it forward due to his many other Drupal Projects, then I (and allot of people) would like to know. Its getting to the point were we all have to upgrade, and AAT is one of the modules holding us up!
@greggles Please do not speak for Eaton and say that I am offending him. He can easily tell me how he feels on a daily basis in IRC (or email) and its not like he can not stand up for himself. We talked today and will always continue to talk. I consider him a friend, and he has my support in any way I can provide it.
#13
I didn't.
I didn't.
Please don't put words in my mouth.
What would you do differently if you got a response saying that eaton was OK with the state of the module. I think you have to assume that until proven otherwise. So, now that you've assume that, what will you do? Probably the things I listed in my comment (like polishing the issues, creating a list of which to apply in which order, etc.).
#14
I was stating my initial assumptions for posting the thread. What would I do if Eaton couldnt do the module? Right now? Not much... but in a week or few months I would be willing to take over the module...
Right now I am working heavy on the Doc Team, and am actually denying my other responsibilities. So I need to spend the next few Days on my projects. I spent all day on Drupal.org and IRC... I woke up at 8A.M. and its almost 3AM and I have done nothing but be on IRC and Drupal working on the site and project! Its been fun, but I need to focus tomorrow on the 3 sites I have to build... I am basically overwhelmed, I just don't know how I can get it all done! Not that I blame working on Drupal. I love to help out, and I do so because I get so much more in return then what I give!
And I talked with Eaton yesterday (the day I wrote the last comment) and he is working on the project. So all is good! I think CHX's idea inspired him to jump back into this project. It probably got stale for him (that can happen to me)...
As far as any conflict we may have, can we call a truce? I misunderstood you, and you misunderstood me:( I am sorry for my role in any problems I caused you!
#15
I'm now co-maintaining this module and look forward to all the support I can get from all of you, in the issue queue, documentation, and with patches.
#16
Automatically closed -- issue fixed for 2 weeks with no activity.