Has there been discussion or plans to reorganize the project so that the profile, features and theme are in individual git repos?

This would allow usage of drush makefiles and no longer any need for storage of all of drupal and the required contrib modules.

I started on a stub makefile and proflle makefile to install but realized there is no cvs commits to grab that portion either.

Example stub makefile:

; stub makefile to install core and Watershed now profile

; Drush make API version
api = 2.x
; Drupal core API version
core = 6.x
; Core project
projects[] = drupal

; projects[pressflow][download][type] = "get"
; projects[pressflow][download][url] = "http://files.pressflow.org/pressflow-6-current.tar.gz"
; projects[pressflow][type] = "core"

;****************************************
; Profiles
;****************************************

; Install profile/distribution
projects[] = watershednow

Comments

seanberto’s picture

seanberto CreditAttribution: seanberto commented
Priority: Minor » Normal

I'd be totally down with this. Based upon our development deadlines before our first launch of a dozen WN clients, it was just easiest to keep everything in one repo rather than doing a Make file. Also, I sorta find regularly working with Git external modules a PITA. But since we're now largely in maintenance mode, it sounds like a good project to tackle. Plus, we'd be able to finally get some cod on the Drupal project page....

Can I ping you to get some help with testing? Not totally sure when I'm going to be able to get to this. Are you needing this asap for anything?

joestewart’s picture

joestewart CreditAttribution: joestewart commented

No hurry at all. Feel free to let me know when there is something to test.

BTW, none of these issues were gripes. It was just me getting introduced and hopefully participating soon. I started following some when I found the profiler module. An older project came back around and I'm moving it to WN. After getting my head wrapped around how things are setup, WN is proving easy to use. So, kudos to all involved - thanks.

seanberto’s picture

seanberto CreditAttribution: seanberto commented
Priority: Normal » Minor

Cool. I'm going to kick down the priority of this ticket, as we've got some work we need to focus on for a client code update.

joestewart’s picture

joestewart CreditAttribution: joestewart commented

I played around with this some. Here is the full distro makefile - https://github.com/joestewart/watershednow/blob/master/distro.make

Give it a try like:


drush make https://github.com/joestewart/watershednow/raw/master/distro.make watershednow

Just a first go round for sure. The individual projects might have issues in addition to makefile issues, I haven't really tested. I know not all the patches apply.

klamzo’s picture

klamzo CreditAttribution: klamzo commented

subscribing

seanberto’s picture

seanberto CreditAttribution: seanberto commented

Just a quick ping to say that this isn't completely forgotten. We're gearing up for another Watershed Now "web sprint" - an event where we get a dozen conservation organizations in a room for a weekend to build sites with WN. We'll be doing a pretty big bug-fix release as part of this and will hopefully get a makefile in there too.