Hi All,
Since we're now ready to migrate all of the remainder code to GitHub, two
questions have popped up.
1) Should we stick with the existing Github.com/dspace/dspace repository,
or should we reimport (a fresh git svn clone) so that we can use the author
mapping to make old commits point to a
On Wed, Mar 14, 2012 at 11:53 AM, Peter Dietz wrote:
> Hi All,
>
> Since we're now ready to migrate all of the remainder code to GitHub, two
> questions have popped up.
>
> 1) Should we stick with the existing Github.com/dspace/dspace repository,
> or should we reimport (a fresh git svn clone) so
As I thought about this a bit more, I did somewhat have a change of heart,
and kind of think we ought to "properly" redo it.
Imagine when DSpace migrates to xyz-version-control in a decade. We'll all
be emeritus, and wondering where our place in history is. And the future
people migrating the cod
RE: the complete "rebuild" of the existing DSpace/DSpace GitHub.
I'm also OK with rebuilding it entirely (and re-mapping all SVN users ->
GitHub Users). However, I agree with Peter Dietz, that we should rename
the existing "DSpace/DSpace" to "DSpace/DSpace-pre-official" (or perhaps
"DSpace-pre