This weekend I will attempt to locate or write a script that moves all
of our core Trac issues to Github, and automates the process of
obtaining nightly archives of the source.
The svn repo url for core will either be shut down or redirect to the
svn mirror on Github, through which you can check out projects from
Github via svn as read-only. Users that use svn to update blogs should
need only execute a simple `svn switch` to continue as they have been.
We're going to need time to work out what to do with the -extras repo,
but I expect that ultimately those projects will also be available via
Github. This will not happen this week.
I realize that there is still a lot of uncertainty about what using git
and Github means. Everyone is likely to have questions, but trust me
when I say that git is just another SCM tool. At worst, you have to
learn a few different commands. At best, we reap great rewards from the
collaborative coding features that Github offers, gain efficiency from
the features that git has that aren't present in svn, and release some
of our otherwise more prolific contributors from frequent server
maintenance tasks. I firmly believe that this move will benefit the
project.
Please +1 this thread if you're in support. If you still have
reservations to the point where you can't +1 the thread, please ask
specific, positive questions that we can help answer. We should only
delay this process if there is a credible reason not to move the core
repo before the weekend - let's not let bureaucracy hinder innovation.
I'm hoping that a couple of folks familiar with git can step up and
draft a wiki page that outlines some of the changes from svn to git,
specific to our project (using our URLs and likely tasks to get things
moving) and link to some good external resources for learning git from
an svn user's perspective.
Thanks,
Owen
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
