Hi, George. You should absolutely be using a git-based workflow. First, git is fun and cool and much better in every way than CVS/SVN, but it's also the official version control of the DSpace project itself since about 2014 or so. This is important for cherry-picking patches, rebasing your local changes on top of upstream point releases, etc.
Second, GitHub is great. We forked DSpace's DSpace repository there and I cherry-pick commits from their branch from time to time, as well as rebase on their point releases as I mentioned above. Even though I'm basically the only technical one doing DSpace on our team, I make *extensive* use of GitHub other features like issues, pull requests, and wikis. For example, when a user reports a bug or feature, I create an issue to track it, then when I get time to address it I make a pull request to my institution's repository from my personal repository. Here's our repo, where all of our code is (~25 Mirage 2 themes, custom input forms, etc): https://github.com/ilri/DSpace On Wed, Dec 7, 2016 at 9:34 PM, Luiz dos Santos <[email protected]> wrote: > Hi, > > We have code in github and svn. The svn is old version that Atmire > folks are updating now. Soon, it's gonna github only, most of the code of > the code is in a maven repository, as a jar files, only the local changes > and config file are in the github repository. The developers have their own > maven profile in the main pom.xml, it helps a lot. > > Luiz Claudio Santos > http://luizclaudiosantos.me/ > > On Wed, Dec 7, 2016 at 2:24 PM, Friesen, Darryl <[email protected]> > wrote: >> >> I’m very interested in this as well and would also love to hear what the >> community is doing. >> >> >> >> Our modifications have been very simple thus far -- a custom theme based >> on Mirage2; Shibboleth/authentication settings; facets (discovery.xml); OAI >> output formats; input forms (input-forms.xml); etc. No code changes, just >> config changes. >> >> >> >> Originally I tried keeping just changed files in our local SVN repo, but >> overlaying those changes onto the DSpace code, then building on out dev, >> test and prod boxes was a hassle. >> >> >> >> What I have now is a complete DSpace source tree committed to SVN. I make >> and test changes on our dev box, then commit to SVN when I have things >> working. Our test and prod boxes have working copies checked out from SVN, >> so I can do “svn update” to easily bring down my changes. I’m, not super >> happy with that either. >> >> >> >> We are moving from SVN to GitLab, so I’d like to investigate what the >> Continuous Integration features of GitLab might offer but I haven’t had the >> time. Another group on our campus is using Ansible to automate deployment >> of software (they specifically mentioned pulling code from Github, applying >> local customizations, then building and deploying – exactly what I want for >> DSpace). I haven’t had time to investigate that either. :( >> >> >> >> - Darryl >> >> >> >> >> >> ---------------------------------------------------------------------- >> >> Darryl Friesen, B.Sc., Programmer/Analyst [email protected] >> >> Library Systems & Information Technology, http://library.usask.ca/ >> >> University of Saskatchewan Library >> >> ---------------------------------------------------------------------- >> >> "Go not to the Elves for counsel, for they will say both no and yes" >> >> >> >> >> >> >> >> From: [email protected] [mailto:[email protected]] >> On Behalf Of George Kozak >> Sent: Wednesday, December 7, 2016 12:33 PM >> To: DSpace Technical Support <[email protected]> >> Subject: [dspace-tech] Question about DSpace code and version control of >> local mods >> >> >> >> Hi, >> >> I've been working with DSpace at Cornell University since 2002 and for the >> most part by myself, but now, with more people are working with me, we would >> like to have more version control over our local mods to the code base. I >> am curious as to how other people are dealing with this. Has anyone placed >> their local code mods in github and if so, what are they putting up in >> github? Just their local mods or the whole code base? >> >> >> >> -- >> >> *************************** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell University >> Ithaca, NY 14853 >> 607-255-8924 >> >> [email protected] >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. -- Alan Orth [email protected] https://englishbulgaria.net https://alaninkenya.org https://mjanja.ch "In heaven all the interesting people are missing." ―Friedrich Nietzsche GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
