Closed (fixed)
Project:
Go - url redirects
Version:
5.x-1.0
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Reporter:
Created:
16 Jan 2007 at 21:42 UTC
Updated:
5 Apr 2007 at 20:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
luti commentedNo feedback in 8 weeks? Is this module still alive? I'd ask for a 5.x version as well.
Comment #2
jredding commentedYou know this is something that bugs me about the Drupal community. While there are a lot of good people in the community there are a number of leeches.
There is no update for Drupal 5.x because I (the assistant maintainer) and the original owner apparently don't have a need for one. I'm still running 4.7 and will be for quite some time. Until I upgrade I'm not going to put the time into updating the module.
However the original owner was nice enough to release his code to the community free of charge. He did not, however, signed up to support, maintain and give blood to the community.
Why do YOU get off your butt and upgrade this module?
The code is there available for you as well as a nice pretty license that ALLOWS you to do this. In fact its the freakin' point of it.
Sheesh. This is where the OSS community breaks down. When people expect to get free software, free support, free updates and never give anything back.
Comment #3
hass commented@jredding: thank you for your reply, however useless it is to get a solution. i think this module is very nice and i'd like to update my drupal to 5, but without this module i cannot, while i TRUSTED this module maintainer to be updated if a new Drupal version get's released. You make clear it will not, what is bad info. This makes me now rethinking of using this module. Keep in mind we are possibly developing other modules and this is what community makes. A maintainer should feel responsible for his work, isn't it? So please give the users a hint on the main download page, that you are not actively maintain this module and only update if you update yourself, what will not happen. In this case i will have a choice not to use this module while it is not actively maintained.
Someone knows a different module with the same or partly the same functionality that is actively maintained?
Comment #4
luti commentedjredding,
I don't understand why you are getting upset. As first, hass just asked (with a nice "please"), and I commented that in 2 months his post didn't deserve any feedback, so this module must be dead (or, not well maintained) more or less... Nobody tried to push you, or to request anything from you or form anyone else.
About myself, I don't have enough knowledge to make a new version, unfortunately. But, I've always tried to contribute to the community as much as I could, weather being it a Drupal community or some other free linux software one. So, I don't feel bad also asking something. Posting an interest about a module can maybe motivate someone else (even he would not be an official maintainer or assistant maintainer or assistant assistant maintainer or whoever like...) to make necessary changes module just to work in Drupal 5.x (even if he maybe wouldn't need it very much). There are still some people walking around, who enjoy to make a favour to the others sometimes, you know... ;-)
By the way, I wonder why you wasted your precious time to reply, with even quite a long post. And, don't worry - I am happy enough not to depend on your module very much, so - bye.
Comment #5
jredding commentedLuti and Haas,
I'm not exactly sure how you've interacted with the OSS community in the past but the idea is that you develop code and you release that code to the "wild" as opposed to closing it. This makes the code available to anyone that wants to use it. The OSS community nor movement has never been about releasing code and sticking around to be the maintainer. You'll find this in a lot of places and you should get used to it. People do not write free software to give themselves work. They write the software to fulfill a need that they or their employers had then they released that code. If they still need the code (or are getting paid) they stick around and maintain it but if they no longer need the code they do not update it.
Its pretty straightforward really.
Your question about why such a long reply. I'm a bit tired of this "give me, give me" attitude. Like you said "I won't use your module, bye". The owner nor myself was specifically out looking for "customers" neither of us is selling this module or our services. If we were then we'd be soliciting you. Both the owner and myself have gained tremendously from using the Drupal code and giving this module to the community is our small way of giving back. So you see, its never been able gaining "customers" but rather about "giving back". This is the heart of the OSS community.
If you want to help out. Instead of posting "Where is the Drupal 5.0 module"
Why don't you...
1) Download the module
2) install it on Drupal 5.0
3) Note the errors and post them here, maybe someone will help you
or if you really need this module then get involved in development. I am frequent logged into #drupal and #drupal-support. I work on other modules, sites, etc. and am more than willing to help. Unfortunately there are only so many hours in a day so I can not do everything for everyone.
I haven't had a need to update this module to Drupal 5.0 so I haven't been active here nor has the owner. I offered to help out with the development because I noticed that the owner was a bit swamped with work elsewhere or simply wanted to move on (both of which are completely understandable and are at the core of the OSS movement).
Ok with all of this said. I am updating this module and I commited a few patches last night. We had some permission issues to work through but it looks as though I'm all set with CVS access now (my commits are working now).
If you want to move on that's completely fine with me (and most likely the owner too). However if you'd like to be a contributing member of this community feel free to grab the code and start noting the errors. Between the three of us (and anyone else reading this thread) we should be able to knock out the errors and get this module updated to Drupal 5!
Comment #6
luti commentedjredding,
you are absolutely right about the principles. And, I am grateful for anything anyone provided to the community and I can use.
What I tried to say is that there is a difference if someone asks for something or if he is requesting it. I haven't understood any of our posts as a request, or any pressure to anyone. However, there is plenty of modules from the past which simply ceased somehow, and that's all what I intended to conclude, since there was no feedback for quite a long time...
I can not 100% agree with you about the commitment, as I am sure many people do also some smaller or bigger changes in their software for the others, not just for them. Sometimes you can make someone happy spending just some minutes of your time, and he simply wouldn't be capable to do it by himself... It simply feels good sometimes to know you've done something good. On the other hand, if the piece of software you are providing is more or less serious one, some people start using it and they rely on it. So, it is nice to make a note somewhere that this module is released as it is and that it won't be developed for new versions. I consider Drupal to be a very serious software (which could be used for serious web sites) and would find such a warning for any such module for it at least a fair gesture.
By the way, as I said, I haven't actually need this module until now (even if I had it installed in my 4.7 site and also see a potential use for it somewhere in the future, even if I didn't have time to figure out details about it yet...), so I am happy enough to simply not depend on it, as hass does. And, I also don't write this now for any personal benefit (as many other comments of mine here or somewhere else), and had also spent some time... ;-)
If we meet at some other module I need and I am using, you cold see that I try to provide as a feedback as some small pieces of code sometimes. But, unfortunately, I can change just some line or two (spending quite some time even for that, looking any kind of documentation for silly things a skilled programmer knows by heart), but don't have enough basics about php or mysql or Drupal, not to mention java etc. And, since my work is something totally different, I also can not dedicate enough time to learn everything I should, but am using just a common logic about programming which I have from the past (times of Assembler and C, not even C++).
Comment #7
raintonr commentedI agree with some of the comments here about having a go. That's what open source is all about.
As such, please find below a patch that appears to get this module going in the right direction in 5.1. The remove/add seems to be broken, but it should get you onto 5.1 at least, the admin settings and list appear to work. Will have a crack at more when time permits.
It was mainly missing .info file and a couple of menu niceties. Check this link for info if you'd like to fix the couple of issues remaining:
http://drupal.org/node/64279
Comment #8
jredding commentedThank you for the note and for the attempt and getting the port up. If you could attach the patch (instead of pasting them in the code) it would be easier to use
In any case I have begun the porting process and I appreciate the jumpstart on it by your patch.
Most functionality exists in HEAD (no 5.x release until the problems are solved). The disclaimer functionality doesn't exist and the administrative functionality isn't available. This is mainly due to the major change in forms in Drupal 5.x
http://drupal.org/node/64279#form-building
This isn't difficult to change but all of the forms need to be moved into functions. There are about 5 or 6 forms left to port. I'm hoping to get some time and possibly get this done by the weekend but I can't guarantee anything.
Anyone is welcome to grab the code and port those forms for me (everything under gotwo_admin_settings). Instructions are here
http://drupal.org/node/64279#hook-settings
Comment #9
designerbrent commentedOk, here is a patch to fix some of the problems with the current head version for Drupal 5.x. Functionality that is now working is:
I can't figure out what '__gotwo_filter' does, though, as I have not used this module before.
Comment #10
designerbrent commentedAlso needed is a .info file which is attached.
Comment #11
jredding commentedHEAD has been updated and an official 5.x version has been released. Thanks for the Patches.. I ran with them and finished up the code. Let me know if there are any problems.
I'm going to close this thread.