On Mon, Jul 18, 2011 at 08:19:15PM +0530, Rahul Sundaram wrote:
On 07/18/2011 08:17 PM, Paul W. Frields wrote:
> On Mon, Jul 18, 2011 at 06:16:03PM +0530, Rahul Sundaram wrote:
>> COD is basically a bundle of several Django modules and some
> ^^^^^^ Drupal?
>> customization settings. If we follow the usual Fedora packaging rules
>> and start unbundling and packaging each of the modules separately, we
>> would not finish this work on time I suspect
> +1.
Yes, Drupal ( I am spending too much time with Django modules because
of Askbot) I am not sure how to handle this. I can do a quick and
dirty package for our purposes now and working on unbundling it slowly
if that is a option. Otherwise, there are dozens of modules to
individually review and there is a lot to work on.
For those who aren't familiar with Drupal or COD and have no time to
go look it up, here's the story with how it works:
COD is one of many Drupal distributions, and COD is specifically aimed
at enabling event and conference management. A Drupal distribution is
the Drupal core packaged along with many contributed Drupal modules.
Often some preconfiguration is provided as well to make the modules
work well together so the end-user/system owner doesn't have to make
all the linkages required in the back end.
Note that all Drupal contributed modules carried in the Drupal project
are GPLv2+ so licensing is generally not a concern, even if the
bundling is. Disentangling the modules is counterproductive, though,
because the entire purpose of starting with a distribution of Drupal,
much like starting with a distribution of Linux such as Fedora, is to
keep the user from having to reinvent very low-level wheels when they
are really concerned about a higher purpose (in this case, event
management).
It is possible to start with a distribution and then customize it
further, just as with the Drupal core itself (or a Linux distro).
This model gives the lie to the usual "We must unbundle and package to
deploy this" strategy. I recommend that if you want to include this
on Fedora infrastructure, the infrastructure admins are going to need
to consider the model and whether/how to support it. (Hint: that
model seems no less maintainable in the long term than writing our own
apps from scratch.)
One potential sticking point is, of course, the long-term availability
of people to do that -- people with Drupal experience, in other words.
If you can provide that assurance it will make the conversation more
fruitful.
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
The open source story continues to grow:
http://opensource.com