I'm working in Strabinarius (www.strabinarius.com), a little spanish company that is engaged in making web projects. For last 3 years, we've been doing several projects with Drupal 5 and 6. Some examples, www.circulodelarte.com, www.viajestejedor.com or www.sefac.org.
In these projects, we've developed some custom modules and we'd like to share it with Drupal community.
We have built a quick & mass import/export module of CCK, Views and Imagecache elements. For next future, we want to adapt it to Drush project. We think this module is very useful for working on a development team environment. All members of the team are always updated with last CCK, Views and Imagcache changes.
As well, we have another module with some little functions that could be useful for other Drupal developers.
I'm and my team are interested in maintaining these both modules. In fact, we're doing it on every project we do.
Thank you and regards.
Fabián Ruiz
STRABINARIUS
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | briefcase.zip | 13.64 KB | fabian.ruiz |
| #1 | briefcase.zip | 13.21 KB | fabian.ruiz |
Comments
Comment #1
fabian.ruiz commentedI'm glad to send you the first version of our import/export module: BRIEFCASE.
The main goal of this module is to share quickly all your Drupal elements (Views, CCK, Imagecache, ...) with other members of your project development team.
We've been updating this module for last weeks before sending it to you. Now, it includes following features:
TODO features:
We're very excited to create a new Drupal project where we can mantain and improve our module. So, it would be very grateful if you give us a feedback.
Thank you very much.
Fabián Ruiz
STRABINARIUS IT
Comment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
The description of your module made me think to the module Features (http://drupal.org/project/features). May you point out the differences between the modules, and eventually why you didn't open feature requests for the existing module?
Comment #3
fabian.ruiz commentedHi. Thank you for replying so quickly.
Yes, we know Features module and we've checked it before. It's great... I think it is a very potential and ambitious project and, of course, our module (Briefcase) isn't so complicated.
In fact, we've used Features for a project, but it wasn't exactly what we needed (or so fast as we'd like).
In my opinion, Features module is perfect to combine different Drupal elements in just one module. As well, control dependencies is very great. However, we only want to have these elements updated without having to package them.
Fabián Ruiz
STRABINARIUS
Comment #4
avpadernoMenu titles, and descriptions don't need to be passed through
t()as that is already done from Drupal core code.There is a much simply way to obtain that, and without write all that code. It's enough to correctly define the menu callbacks.
Actually, that code is not even necessary, basing on how the sub-modules define their own menu callbacks.
The code should use
preg_match(), as that function has been deprecated in PHP 5.3.Use a placeholder.
The menu definition is not correct; there is a
MENU_LOCAL_TASKwithout aMENU_DEFAULT_LOCAL_TASK.The menu definition is not correct, for the same reason I reported before. Then, what would happen if the user enables one sub-module, but not the other? There would be again one
MENU_LOCAL_TASKwithout aMENU_DEFAULT_LOCAL_TASK.I would rather use a single module, and define the menu in that module.
Strings used in the user interface as title of items should be in sentence case.
Comment #5
fabian.ruiz commentedWow. What a great review!! Thanks.
I've checked all 8 steps and updated my Briefcase module with corresponding corrections:
I attach here new Briefcase module version. It's important you know that it has some changes from last version. I've been working last week and I could finish Drush integration. It means that new Briefcase version (attached here) has new Drush commands for export and import CCK and Views.
Thanks again for your time.
Fabián
Comment #6
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #9
avpaderno