SVN for the OSDPL - using 3rd party SVN repository for core Drupal and modules

[Jonathan Hung]

I have been researching how to properly put the OSDPL into the Fluid
project's SVN repository in a way that is manageable and sustainable over
time.

The complicating factors are:
- Drupal uses CVS to manage core and module code.
- There are a number of 3rd party plugin modules currently being used. Each
module has its own code base and development cycles. All modules are managed
in Drupal's CVS repository.
- The core Drupal code also has it own code base which is in the Drupal CVS
repository.

To make management easier, all core and module should be defined as an
External property so we do not have to manage our own copies of the code.
However, this can only be done if Drupal is running in SVN (since Fluid is
using SVN and not compatible with CVS).

There are 3rd party SVN repositories managing copies of Drupal's core and
module code: http://drupal.org/node/355154

What I propose is that we use one of these 3rd party SVN repositories to
manage our Drupal code and modules, and manage our own customized files in
the Fluid repository.

The disadvantage to this is that we'll be at the mercy of a 3rd party SVN
repository, but it greatly simplifies our code management of the OSDPL.


Any thoughts or concerns?

- Jonathan.

---
Jonathan Hung / jhung.utoronto at gmail.com
Fluid Project - ATRC at University of Toronto
Tel: (416) 946-3002
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090327/cfb156d1/attachment.html>