Not logged in
Log in now
Create an account
Subscribe to LWN
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
"We the people" source released
Posted Aug 24, 2012 9:35 UTC (Fri) by reddit (guest, #86331)
Posted Aug 24, 2012 9:43 UTC (Fri) by os3294 (guest, #86384)
Posted Aug 24, 2012 9:55 UTC (Fri) by rwst (guest, #84121)
Posted Aug 24, 2012 11:26 UTC (Fri) by Klavs (subscriber, #10563)
Have you checked that core Drupal and all the modules which have an upstream (different than the one who created the site) isn't just the same - but added to github to make it "simple" (ie. just duplicated code - nothing else) ?
Normally, Drupal developers are good at following the standard way of developing Drupal sites, which means NO core changes, and all changes done using hooks - in a module they write themselves, and in the theme itself.
So I don't think there's a lot of forking going on here - I actually highly doubt it.
I'm sure that's probably not the same for many other projects, but Drupal is actually a very well managed project with very sane development practicses IMHO. I particularly enjoy the fact, that new releases of same major version (f.ex. 6.0,6.1 etc.) just as RHEL does it, only contains severe bugfixes, and security updates - meaning you can actually upgrade rather safely, without getting featurechanges etc. They don't support each release for as many years, as RHEL does though - "only" until two new major releases has come out.
So Drupal is IMHO a very company friendly project, in that you get security upgrades ONLY - support for this for a long time - and security announcements as well.
PHP is in many ways not a well-designed language - but that does not mean Drupal isn't a great project or CMS Framework.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds