Closed (fixed)
Project:
Commerce Reporting
Version:
7.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Jul 2013 at 10:44 UTC
Updated:
23 Dec 2013 at 07:11 UTC
Jump to comment: Most recent
Comments
Comment #1
mglamanOur company could really use this module for clients, and I would be willing to step up as a maintainer.
I have not had the experience of maintaining a Drupal module yet - but you have to start somewhere. I plan to begin working on patches soon.
Comment #2
dydave commentedJust wanted to cross post here another issue related with the required module Visualization API: #2042155: Looking for new co-maintainers as well....
It would seem that for both modules, @cvangysel would require assistance to be able to sustain an active code maintenance or further developments.
The possibility of dropping the development/support of the Visualization API, in favor of the Charts module, is being discussed at #2042155-8: Looking for new co-maintainers, which would already relieve an important part of the maintaining workload.
However, in this case, perhaps one of the first major changes that would probably have to be made, would be to replace Commerce Reporting's dependency for the Visualization API with a dependency on the Charts module.
This would sound like a pretty major change and would probably need some work from a potential future maintainer.
But unless someone would be ready to step up to maintain both modules, it seems this is most likely the way things are going to evolve.
Feel free to let us know if you would have any particular questions, comments, objections, issues, recommendations, feedbacks or concerns on any aspects of this comment, I would surely be glad to provide more information.
Thanks in advance to everyone for your reviews, comments and involvement.
Cheers!
Comment #3
mglamanHey @DYdave,
Since it seems Charts has an active maintainer and provides the same functionality (Highcharts and Google Charts) it makes sense to use that module as a dependency versus maintaining a wholly different module.
I know it's a late reply but Commerce Reports was not working out for our client so I had to dive off and setup a custom solution. Which brings a lot of ideas to the table for this module. I recently wrote up a blog about Drupal Commerce and Reporting that outlined the issues and my possible solution.
rszrama replied to my post and essentially revitalized my effort to make this module work and bring it up to speed. I'm willing to work to start writing patches to migrate Commerce Reports to Chart and help bring a robust reporting system into the Commerce ecosystem.
Comment #4
mglamanClosing this out