[Building Sakai] Great Migration: Sakai trunk SVN->Git authors file (info requested)

Anthony Whyte arwhyte at umich.edu
Mon Sep 8 09:22:28 PDT 2014


*Sakai trunk committers take heed*
The Sakai PMC plans to migrate Sakai trunk code from Subversion to Git in
the coming weeks utilizing the popular Github hosting service. [1]  The
migration targets trunk code only (Sakai 11+) and is limited to those
modules that comprise the current core distribution. [2]  We have
identified 135 committers from the SVN logs who have committed code to
these modules since 2006. [3]  If you are one of these contributors, read
on because we need your assistance.

*History matters*
Subversion records the committer's username in each revision (e.g.,
arwhyte at umich.edu); Git differs by storing the revision author's full name
and email address (e.g., Anthony Whyte <anthwhyte at gmail.com>).  As part of
the migration process we need to create an "authors" text file for trunk
committers--both active and emeritus--that maps Sakai SVN usernames to a
corresponding Git author name and email address.

*Git / Github users*
If you are an active/emeritus Sakai trunk committer and you use Git /
Github we need your Git user name and email address.

1. Login to* https://confluence.sakaiproject.org/x/nQHBBQ
<https://confluence.sakaiproject.org/x/nQHBBQ>*
2. Scan the list, identify your SVN username(s)
3. Add/update your Git name and email address (format: *name* <*email addr*>)
[4]
4. Add "yes" or a green checkmark emoticon in the Confirm column

*New to Git / Github*
If you are an active Sakai trunk committer and are new to Git, we ask that
you install Git, create a Github account, provide us with your Git name and
email address.  Then start familiarizing yourself with Git commands and
workflows.

If you are an emeritus Sakai committer but still coding consider installing
Git, joining Github and providing us with your Git name and email address
so that we can map your revision history from Subversion to Git.

1. Install Git. [5]
2. Create a Github account (it's free). [6]
3. Login to https://confluence.sakaiproject.org/x/nQHBBQ
4. Follow the instructions above to add/update your mapping record

We value our history and your contributions.  Our goal is to map as many
Sakai trunk committers to Git authors as is possible.  Whether you are an
active or emeritus committer, you can help us by checking your record in
Confluence as well as assisting us in providing updated contact info for
emeritus committers you may know.

If you have questions regarding the mapping file or information on former
committers, please contact Anthony Whyte directly at arwhyte at umich.edu.

Cheers,

Anthony

__________________

[1] https://github.com/sakaiproject.

[2] See https://source.sakaiproject.org/svn/sakai/trunk/.externals for a
list of the trunk modules we plan to migrate.  We may also migrate the
contrib dashboard project, currently running in un-stealthed production at
Michigan.

[3] https://confluence.sakaiproject.org/x/nQHBBQ.  We transitioned from CVS
to SVN in early 2006.

[4] * Do not confuse your Git author name with your Github id (e.g.,
arwhyte), we want your Git user info as specified in your local .gitconfig
file:

[user]
name = Anthony Whyte
email = anthwhyte at gmail.com

[5] You can get Git from git-scm.com or consider using a package manager
like Homebrew for the Mac.  There's also no shortage of Git install howto's
online.  http://git-scm.com/downloads;
http://git-scm.com/book/en/Getting-Started-Installing-Git.

[6] https://github.com/join
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140908/acf0feff/attachment.html 


More information about the sakai-dev mailing list