Posted by Aren Cambre on November 17, 2009 at 4:43pm
Jump to:
| Project: | Editview |
| Version: | master |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Looking through the queue, I haven't significant developer activity on this module for months. Are the developers busy on other projects?
Comments
#1
Hi Aren,
Yeah, the module is not abandoned, we just have not had time for it for a while. We have a lot of paid projects as well as a few other modules to maintain so it takes a while to get to each one sometimes.
We have spent some time on some of the other modules recently so we will get to this one shortly.
#2
Thanks!
#3
By the way Aren, if you want to co-maintain this module then we'd be delighted to have your assistance.
#4
subscribe
#5
Hello!
First of all, thank you for a great module!
Next, i've managed to implement your idea for editing location-based views (those provided by a monstrous location.module). Interestingly, this new module seems to be the only way to edit location records directly, so i suppose it will be of an interest for people in location-camp. But first i'd like to show it to you and listen to your opinion.
Here's the code: http://code.google.com/p/drupal-bi/source/browse
My work is basically c'n'p of yours, as it was hardly possible to reuse anything directly. I'm not sure i've understood every bit, so there are chunks of orphaned code. I think, if you're not against, it makes sense to integrate it into editview.module as a contributed one, instead of keeping it elsewhere. What do you think?
Also, a minor technical question. I've noticed you're posting ajax form by hand. Have you any objections against ajax.module approach? (They're using some jQuery.forms plugin to post a form asynchronously.)
#6
Automatically closed -- issue fixed for 2 weeks with no activity.
#7
I need to raise this issue again.
Observation: last commit was over a year ago, last release was 14 months ago, only three closed issues in prior year, and this issue is one of them.
Abandoning doesn't mean the project will be deleted. It just makes it clear that nobody is available to support it at the moment.
#8
Abandoning doesn't mean deleted but it effectively means don't use this module.
Still maintaining my modules but just very busy with paid work at the moment.
This module is flagged as seeking co-maintainers so if anyone wants to help co-maintain this module send me a message via my contact form.
#9
Frodo Looijaard (http://drupal.org/user/6199) has just been added as a co-maintainer of this module. Way to go Frodo Looijaard!
If anyone else wants to co-maintain this module then please contact Agileware, http://drupal.org/user/89106/contact
#10
I am currently making an inventory to see what issues are outstanding. First thing I will probably do is add a TODO file :-0
I'll probably concentrate on adding several often asked for enhancements to the Drupal 6 branch, as well as fixing several bugs.