April 20, 2010

On Hacking Drupal Core and Contributing Back to the Open Source Community Project

Here's an article by Ron Miller that expounds on Seth Gottlieb's blog on the drawbacks of hacking Drupal core. The Onion implemented version 4.7 of Drupal several years back and mightily hacked core for the functionality and performance it needed. Recently, the Onion - a company with a number of staff developer resources - decided to migrate to a different WCMS (Django) that they felt was more of a programmers' framework than that of Drupal.

The Onion got its return on investment many times over by using available technology - they also have bragging rights to actually having done something impressive with Drupal 4.x. However, had the Onion implementation team gotten more involved in contributing back to the main project, they may indeed have reduced the risk of a branched version. Their decision to abandon Drupal for a different project is regrettable, since their team's experience could really have helped improve Drupal these past few years and The Onion would have benefited in the process.

The situation holds true for contrib modules as well as core code. When implementing Drupal, during module selection (and after requirements documentation) the team needs to perform a gap analysis on what modules need to be customized/modified. You can then contribute those customizations back to the project, or at least document the changes that you'll need to maintain in the future.

Also, periodically you may find that you'll use and/or customize a module that is no longer maintained by someone in the community. At that entry point you could decide whether you'd like to become the maintainer, or look to migrate to a different module that is maintained.

Posted at 12:12 pm by Joseph Bachana


More Blogs From Author:

Case study:
Drupal Consulting at NYU Langone Medical Center - Department of Pathology Labs

The Department of Pathology at the NYU Langone Medical Center hired DPCI to implement a self-service public and private Web portal platform for Labs that is connected to the existing Department of Pathology Drupal Website. > more

All case studies


Press Release:

DPCI Nominated as an Adobe Digital Publishing Suite Reseller
DPCI will focus on implementation, training and support services as well as integrating Adobe Digital Publishing Suite with InDesign Server, K4 Publishing System, and customer Web content management and digital asset management systems. > more
IDEAlliance Bulletin: "One Size Fits All? Not in MultiChannel Publishing" Lead Article by DPCI CEO Joe Bachana > more

DPCI Events:

DPCI a Bronze Sponsor of Drupalcon Denver 2012
Come visit us in the exhibition hall, see the work we have done around integrating Drupal with Entermedia DAM and InDesign Server, and get some SWAG and chocolate on us! > more
DPCI R&D Team to Present InDesign Integration with Drupal at DrupalcampNJ
Members of the DPCI R&D Team will present integrations we have accomplished between Drupal 7 and both InDesign desktop and server software. > more
Alltop, all the top stories