Jump to:
| Project: | Feedback |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi Khalid!
As it seems to me that development of Feedback remains static (based on the issue queue), I wondered whether you would like to hand over this project to me. I would not develop the current module further, but replace it (i.e. 2.x) with a different module/intention, basically: Allow visitors and/or users of a site to report "issues" they are experiencing on all pages of a site. Those issues could be theming issues or missing/invalid data issues or even feature requests. So, that's a completely different interpretation of "feedback", but I really think that the current features of this module are already covered by other modules (contact in core, webform, CCK, etc.).
Of course, I could simply go on and name my module "site_feedback" or whatever; but I thought I'd simply ask if I could get this name. :)
Please let me know what you think.
Thanks,
Daniel
Comments
#1
Daniel
I gave you CVS access to this module. Once you check in you checkin the stuff in 2.x, we should have a new project description that mentions the old usage of the module, and that it is obsolete, and replace the current description with the new stuff.
#2
Thanks, Khalid. I should have mentioned that the replacement code for this module doesn't exist yet - however, since my current project could benefit from this, I'll try to finish a first (working) draft of this module today/tomorrow (depends on your timezone 8).
And, since the above mentioned project is based on D5, I'm moving version to 5.x.
#3
Well, I've created DRUPAL-5--2 and the first step is done: http://drupal.org/node/280076
Most of the code (despite the JS and CSS thingies) is forked from Journal module.
Because this module is already running on a production site, I'll wait for a "live feeling" of what needs to be done in the administrative UI. Currently, I'm thinking of grouping all feedback entries by their path (location), so site admins don't need to deal with duplicate messages.
Compatibility with custom themes might also be a problem. After testing it with Garland and other themes, I needed to fix (override) some of the styles.
#4
Khalid,
after committing some bug fixes and nice improvements, 5.x-2.x is in a RC1 stage now. Hence, I would like to create an initial release candidate ASAP. However, I don't know if I'm allowed to?
Additionally, I would like to propose the following:
- Let me make take over the Feedback project.
- I'll mark all existing issues for 1.x as won't fix.
- I'll update the project description for the new version.
- I'll insert a bold red warning message into all 2.x releases indicating that users should not upgrade to this major version.
If you want to, we can also release a final 1.x release containing all remaining patches from the queue - dunno, if that makes sense.
#5
You are now the project maintainer. Change the email for issues as well.
Yes, make a final release.
Push all the existing description down the page saying this is the old code.
Suggest the core contact module, or webform as replacements. Then add your new description.
#6
Thanks, Khalid. I have cleaned the issue queue and updated the project description. I'll give users some time to update their patches in front of creating the final 5.x-1.1 release. Since there was no commit since 5.x-1.0, there's no hurry.
To be honest, I really hope that this module replacement will work out as expected. I don't know of another module which has been completely replaced in the past. Well, I guess we'll see...
#7
Automatically closed -- issue fixed for two weeks with no activity.