I would like to create and maintain ec_region module, which is a extension to the ecommerce module. This is not completely written from scratch. ec_region was part of ecommerce 5.x version, when they ported the ecommerce 5.x to 6.x gordon (ecommerce developer) left out few features and made the ecommerce 6.x more generic. This was a very useful feature for implementing global store with region based content and region based pricing.
I have taken the initial code from ecommerce 5.x and ported it to drupal 6.x and tested the same. I have contacted gordon via email to ask him the permission to extend his code. He replied taking over this module will make a number of people happy.
I would like the community to review the code before submitting to the cvs. I have attached the module with this issue.
| Comment | File | Size | Author |
|---|---|---|---|
| ec_region.6.x.4.0.tgz | 5.37 KB | vinothg |
Comments
Comment #1
gordon commentedThanks for your contribution. But the changes that I have made to e-Commerce we are not longer taking additional modules into the core, but I have getting people like yourself to create your own projects and maintain them yourself. See http://groups.drupal.org/node/17110 for some more information on the reasons that I did this.
Basically it means that the core of e-Commerce is much smaller and easier to maintain and advance to newer version, and people who take ownership of the contrib modules will have much control of the direction of their module and can make it work a lot better without having interference from me, and are more likely to continue working on the module and keeping up its development beyond their own project, which is better for e-Commerce as a whole. Developer retention has always been an issue with the e-Commerce project.
You will need to apply for a cvs account (git it the future) and then you will be able to commit the module into it's own project and then maintain your own releases. See http://drupal.org/cvs-application/requirements for more information on getting a cvs account.
I am closing this issue, not because the module is not right, but because under the new system that I have implemented it will no longer be in the core system, but be available for people as a separate download.
Thanks for helping, and if you need any help, or input on better methods to do things, or even ways we can improve core so that your and other modules will work better.
Gordon.
Comment #2
vinothg commentedThanks much for the swift response. I appreciate the idea of making the e-Commerce module much smaller for easy maintenance. I will apply for the cvs account and maintain ec_region as a separate project.
Comment #3
vinothg commentedThanks much for the swift response. I appreciate the idea of making the e-Commerce module much smaller for easy maintenance. I will apply for the cvs account and maintain ec_region as a separate project.
Comment #4
vinothg commentedThanks much for the swift response. I appreciate the idea of making the e-Commerce module much smaller for easy maintenance. I will apply for the cvs account and maintain ec_region as a separate project.