Hi, I've talked about this a bit with a few developers in the #DSpace IRC channel, and I added it to the agenda for today's meeting, but the consensus was it was a good topic for the DSpace-devel mail list, so, here I am. My proposal is this:
I think we should move a few of the DSpace themes to their own Git repositories. This will make it much easier to include the theme code in our own DSpace repositories as Git submodules. Here a bit more information on Git submodules: http://git-scm.com/book/en/Git-Tools-Submodules And here's a writeup on how some people manage Wordpress themes as Git submodules, to give you an idea of what I'm proposing: http://clintberry.com/2011/speed-up-your-wordpress-development-cycle-with-g it/ I am part-way through a little experiment, doing a sparse checkout of the DSpace/DSpace.git repository, filtered to just the Mirage theme folder. My intention is to subtree merge this folder into a new bare repository, and see if I can work out a workflow where I can utilize this new repository, while still incorporating changes to Mirage coming from DSpace/DSpace.git It's possible there's an easier way to do this... I have been known to over-think things. :-\ I'll keep you all informed as to the outcome of this experiment. In the meantime, I'd like to hear from anyone who might be interested in working with DSpace themes in this way. -- HARDY POTTINGER <[email protected]> University of Missouri Library Systems http://lso.umsystem.edu/~pottingerhj/ https://MOspace.umsystem.edu/ "The bigger the smile you give, the bigger the smile you get. Works every time." --Alan Shapiro ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
