Posted by Arts and Ideas on August 5, 2010 at 9:52pm
- Is OpenPublish "open" or "closed?"
- What are the current shortcomings of a centrally managed open-source install profile, and how can they be overcome?
OpenPublish — Pros and Cons of Centrally Managed Profile
Group organizers
Group categories
Subsystem
- Design/Theme (238)
- Functionality (299)
- Information Architecture (32)
- Install Profile (75)
- Modules (62)
Comments
Being a Drupal distribution,
.............................................
http://twitter.com/inadarei
Open and Managed
OpenPublish is great. It allows an entire user-base to investigate, trial and implement very sophisticated semantic publishing tools. In that way it furthers the Drupal community's knowledge and understanding of rdf and web-based semantic content.
Still, because its implementation and install profile depends upon significant customization, it seem a hybrid of an open and commercial release — As bugs are discovered in interdependent contributed modules they must be squashed, tested, and a new profile released... This is complicated in a commercial setting and requires a significant buy-in from the community.
I suppose what is important is that the utility of these publishing tools and the feature-rich profile will encourage people to stick with OP through the bumpy upgrade/modification processes.
My particular implementation will be as "customized" as TNRs, and I worry that the modules you update and the theme updates will eventually trash css, tpl and .info files I may not remember customizing... In other words, I have to keep a backup of my backup just in case I accidentally pull in an OP module through Drush and blow out my site.... not to mention concerns about security updates of contributed modules that I cannot update...
This makes OP somewhat "closed" for me. I started this discussion to see if others felt the same way.