[drupal-devel] CivicSpace development moving to Drupal

Kjartan Mannes kjartan at drupal.org
Wed Mar 16 10:48:39 UTC 2005

Wednesday, March 16, 2005, 9:46:34 AM, Dries Buytaert wrote:
> 1. The availability of the drupal.org infrastructure - and the CVS 
> repositories in particular - will become increasingly important.  Ditto
> for approving and managing CVS accounts.  It might make sense to move 
> the contributions repository to a dedicated machine.  Like that, system
> administrators can be recruited to help administer CVS.  Because the 
> way CVS integrates into drupal.org, this might be a bit of a challenge.
>   Anyway, food for thought.

I don't see fragmenting the cvs repos as necessary. There are plenty of
other ways to go (restricted ftp access, chrooted accounts, online
interface with backend scripts, etc). I am not 100% uptodate on how we
handle new cvs accounts but from how it looks i could now automate it
more with a few hours of work.

Dries: I'll be in Belgium from monday next week so you can update me
then over dinner ;)

> 2. We can create a 'Distribution vocabulary' and bind it to project 
> issues.  It lets you filter, track and syndicate CivicSpace related 
> issues.  It makes sense to invest in the project module a bit (e.g. and
> to look into Nedjo's project module patch).

The project module already has integration with taxonomy (just no search
interface since I got frustrated with taxonomy.module when I tried).
Issues should be taxonomy enabled as well, or its a quick addition to
the _form(), but again search is non existent. The only challenge would
be that you cant change the taxonomy in updates, just when initially
posted, again something that can probably be added. Releases are not
nodes and hence can not be taxonomized without applying some of the
patches that make taxonomy more generic.

Kjartan <kjartan at drupal.org>
:: "Life consists not in holding good cards but in playing
    those you hold well." - Josh Billings

More information about the drupal-devel mailing list