[uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in 
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together from 
those that explicitly have listed their git accounts [1] and account 
information for jasig SVN committers that was compiled from the 
Confluence/Jira services [2]. If you have ever commit to a Jasig project 
in the past and think you may ever commit to uPortal (or make a pull 
request) it would be great to have you setup a GitHub account and get 
the appropriate mapping information added to file [1].


[1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but have 
NOT yet setup an account on GitHub, meaning that their commit history 
won't transfer AND they won't be able to commit once we've moved. Please 
either email me your GitHub account info (should look like: Eric 
Dalquist ) or event better, get to know git and 
fork https://github.com/Jasig/svn2git-migration add yourself to 
mappedAuthors.txt and then make a pull request.


 * Andrew Wills (awills)
 * Andy Gherna (agherna)
 * Anthony Colebourne (acolebourne)
 * Brad Szabo (bszabo)
 * Cris Holdorph (holdorph)
 * Gary Thompson (gthompson)
 * Lennard Fuller (lfuller)
 * Matthew Polizzotti (mpolizzo...@unicon.net)
 * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available for uPortal committers


Unless there are objections the schedule will proceed as stated above. 
Realistically the GitHub repo should be available much earlier than 4pm 
but don't plan on making any commits to uPortal on Thursday 10/20 and if 
you have any work in progress make sure it is committed somewhere 
(create a temporary branch if needed) so that you don't have to re-apply 
the changes on the git side of things.


-Eric


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Cris J Holdorph]

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together from
those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig project
in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt

The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved. Please
either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know git and
fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and available
for uPortal committers

Unless there are objections the schedule will proceed as stated above.
Realistically the GitHub repo should be available much earlier than 4pm
but don't plan on making any commits to uPortal on Thursday 10/20 and if
you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to re-apply
the changes on the git side of things.

-Eric


--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Thought I had found a few people by guessing usernames but the accounts 
didn't have enough publicly available info for me to verify. So that 
email was likely from being added and then removed from the team. I'll 
still need the "Full Name " string for the 
conversion if you care about commit history.


-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together from
those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig project
in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt

[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt 



The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved. Please
either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know git and
fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and available
for uPortal committers

Unless there are objections the schedule will proceed as stated above.
Realistically the GitHub repo should be available much earlier than 4pm
but don't plan on making any commits to uPortal on Thursday 10/20 and if
you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to re-apply
the changes on the git side of things.

-Eric






smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Cris J Holdorph]

I don't see any way to submit a pull request for 
https://github.com/Jasig/svn2git-migration


 Cris J H

ps.  I tried to do it the github way, but in any case, my github email 
address was/is holdo...@unicon.net


On 10/13/2011 03:51 PM, Eric Dalquist wrote:

Thought I had found a few people by guessing usernames but the accounts
didn't have enough publicly available info for me to verify. So that
email was likely from being added and then removed from the team. I'll
still need the "Full Name " string for the
conversion if you care about commit history.

-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together from
those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig project
in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1]
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved. Please
either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know git and
fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and available
for uPortal committers

Unless there are objections the schedule will proceed as stated above.
Realistically the GitHub repo should be available much earlier than 4pm
but don't plan on making any commits to uPortal on Thursday 10/20 and if
you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to re-apply
the changes on the git side of things.

-Eric






--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

The "Step-by-step (the short version)" section here 
https://github.com/diaspora/diaspora/wiki/Git-Workflow has good info, 
for something as simple as this you can skip a bunch of the steps 
(setting upstream remote and creating dev branch) and boil it down to:


1. Fork on GitHub (click Fork button)
2. Clone to computer ($ git clone g...@github.com:you/diaspora.git )
3. Don't forget to cd into your repo: ($ cd diaspora/ )
4. Make changes//
5. Commit changes to issue branch. ($ git add . ; git commit -m 'commit
   message')
6. Push branch to GitHub ($ git push)
7. Issue pull request (Click Pull Request button)

Post migration I'm going to be encouraging people to follow the full set 
of steps and do all development on branches. That should let everyone 
get the work they are doing out into a visible location earlier in the 
development cycle and keep trunk (master) more stable.


-Eric

On 10/13/11 6:12 PM, Cris J Holdorph wrote:
I don't see any way to submit a pull request for 
https://github.com/Jasig/svn2git-migration


 Cris J H

ps.  I tried to do it the github way, but in any case, my github email 
address was/is holdo...@unicon.net


On 10/13/2011 03:51 PM, Eric Dalquist wrote:

Thought I had found a few people by guessing usernames but the accounts
didn't have enough publicly available info for me to verify. So that
email was likely from being added and then removed from the team. I'll
still need the "Full Name " string for the
conversion if you care about commit history.

-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:
Details of the uPortal SVN to GitHub migration, reasoning, and FAQ 
is in

the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together from
those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig 
project

in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1]
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt 


[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt 




The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved. 
Please

either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know 
git and

fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available

for uPortal committers

Unless there are objections the schedule will proceed as stated above.
Realistically the GitHub repo should be available much earlier than 
4pm
but don't plan on making any commits to uPortal on Thursday 10/20 
and if

you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to 
re-apply

the changes on the git side of things.

-Eric








smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Right after I sent this I saw the pull request :)

On 10/13/11 6:28 PM, Eric Dalquist wrote:
The "Step-by-step (the short version)" section here 
https://github.com/diaspora/diaspora/wiki/Git-Workflow has good info, 
for something as simple as this you can skip a bunch of the steps 
(setting upstream remote and creating dev branch) and boil it down to:


 1. Fork on GitHub (click Fork button)
 2. Clone to computer ($ git clone g...@github.com:you/diaspora.git )
 3. Don't forget to cd into your repo: ($ cd diaspora/ )
 4. Make changes//
 5. Commit changes to issue branch. ($ git add . ; git commit -m
'commit message')
 6. Push branch to GitHub ($ git push)
 7. Issue pull request (Click Pull Request button)

Post migration I'm going to be encouraging people to follow the full 
set of steps and do all development on branches. That should let 
everyone get the work they are doing out into a visible location 
earlier in the development cycle and keep trunk (master) more stable.


-Eric

On 10/13/11 6:12 PM, Cris J Holdorph wrote:
I don't see any way to submit a pull request for 
https://github.com/Jasig/svn2git-migration


 Cris J H

ps.  I tried to do it the github way, but in any case, my github 
email address was/is holdo...@unicon.net


On 10/13/2011 03:51 PM, Eric Dalquist wrote:

Thought I had found a few people by guessing usernames but the accounts
didn't have enough publicly available info for me to verify. So that
email was likely from being added and then removed from the team. I'll
still need the "Full Name " string for the
conversion if you care about commit history.

-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:
Details of the uPortal SVN to GitHub migration, reasoning, and FAQ 
is in

the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together 
from

those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig 
project

in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1]
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt 


[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt 




The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved. 
Please

either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know 
git and

fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available

for uPortal committers

Unless there are objections the schedule will proceed as stated 
above.
Realistically the GitHub repo should be available much earlier 
than 4pm
but don't plan on making any commits to uPortal on Thursday 10/20 
and if

you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to 
re-apply

the changes on the git side of things.

-Eric








smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Cris J Holdorph]

I followed those instructions before I sent my message.  However, there 
are two problems.


One, it's not clear that you have to do the pull request from your fork. 
 If you're viewing the original repository, you see a 'pull requests' 
tab, and so as a NEW UNFAMILIAR user, you might be there, click on that 
tab, see the 'list' of requests (or empty list) and not know how to 
submit one.  You must be on your own repo fork, but that's not clear in 
those instructions.


Two, even when you get to your own repo and find the right screen to 
submit a pull request, you end up at this screen:


http://img.skitch.com/20100831-qit9sjhuqk42t4ww91ifm5tm81.png

Except in your case those two text fields will be blank, with NO 
indication what information should go in those text fields and no 
mention in the instructions about what should go in there.


I guessed and submitted mine, but I had no idea if it would even work, 
when I pressed the 'send pull request' button.


 Cris J H

On 10/13/2011 04:28 PM, Eric Dalquist wrote:

The "Step-by-step (the short version)" section here
https://github.com/diaspora/diaspora/wiki/Git-Workflow has good info,
for something as simple as this you can skip a bunch of the steps
(setting upstream remote and creating dev branch) and boil it down to:

   1. Fork on GitHub (click Fork button)
   2. Clone to computer ($ git clone g...@github.com:you/diaspora.git )
   3. Don’t forget to cd into your repo: ($ cd diaspora/ )
   4. Make changes//
   5. Commit changes to issue branch. ($ git add . ; git commit -m
  ‘commit message’)
   6. Push branch to GitHub ($ git push)
   7. Issue pull request (Click Pull Request button)

Post migration I'm going to be encouraging people to follow the full set
of steps and do all development on branches. That should let everyone
get the work they are doing out into a visible location earlier in the
development cycle and keep trunk (master) more stable.

-Eric

On 10/13/11 6:12 PM, Cris J Holdorph wrote:

I don't see any way to submit a pull request for
https://github.com/Jasig/svn2git-migration

 Cris J H

ps. I tried to do it the github way, but in any case, my github email
address was/is holdo...@unicon.net

On 10/13/2011 03:51 PM, Eric Dalquist wrote:

Thought I had found a few people by guessing usernames but the accounts
didn't have enough publicly available info for me to verify. So that
email was likely from being added and then removed from the team. I'll
still need the "Full Name " string for the
conversion if you care about commit history.

-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ
is in
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together from
those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig
project
in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and get
the appropriate mapping information added to file [1].

[1]
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt

[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt



The following people currently have commit access to uPortal but have
NOT yet setup an account on GitHub, meaning that their commit history
won't transfer AND they won't be able to commit once we've moved.
Please
either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know
git and
fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and
available
for uPortal committers

Unless there are objections the schedule will proceed as stated above.
Realistically the GitHub repo should be available much earlier than
4pm
but don't plan on making any commits to uPortal on Thursday 10/20
and if
you have any work in progress make sure it is committed somewhere
(create a temporary branch if needed) so that you don't have to
re-apply
th

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Carroll, Timothy Dale]

do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in the 
wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest

Account Mapping
This is using best author mapping data that we could put together from those 
that explicitly have listed their git accounts [1] and account information for 
jasig SVN committers that was compiled from the Confluence/Jira services [2]. 
If you have ever commit to a Jasig project in the past and think you may ever 
commit to uPortal (or make a pull request) it would be great to have you setup 
a GitHub account and get the appropriate mapping information added to file [1].

[1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt

The following people currently have commit access to uPortal but have NOT yet 
setup an account on GitHub, meaning that their commit history won't transfer 
AND they won't be able to commit once we've moved. Please either email me your 
GitHub account info (should look like: Eric Dalquist 
) or event better, get 
to know git and fork https://github.com/Jasig/svn2git-migration add yourself to 
mappedAuthors.txt and then make a pull request.

  *   Andrew Wills (awills)
  *   Andy Gherna (agherna)
  *   Anthony Colebourne (acolebourne)
  *   Brad Szabo (bszabo)
  *   Cris Holdorph (holdorph)
  *   Gary Thompson (gthompson)
  *   Lennard Fuller (lfuller)
  *   Matthew Polizzotti (mpolizzo...@unicon.net)
  *   Susan Bramhall (susan.bramh...@yale.edu)

Scheduling
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and available 
for uPortal committers

Unless there are objections the schedule will proceed as stated above. 
Realistically the GitHub repo should be available much earlier than 4pm but 
don't plan on making any commits to uPortal on Thursday 10/20 and if you have 
any work in progress make sure it is committed somewhere (create a temporary 
branch if needed) so that you don't have to re-apply the changes on the git 
side of things.

-Eric


-- 
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Drew Wills]

On 10/13/2011 5:49 PM, Carroll, Timothy Dale wrote:

do the email addresses used in file [1] and [2] need to match?



Good question.  Mine currently  don't.

drew

--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

File 2 is the automated output of looking up the name and email address 
for each svn account name from Crowd. File 1 is overlayed on top of File 
2 to come up with the mapping file used for doing the migration.


-Eric

On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:

do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is 
in the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together 
from those that explicitly have listed their git accounts [1] and 
account information for jasig SVN committers that was compiled from 
the Confluence/Jira services [2]. If you have ever commit to a Jasig 
project in the past and think you may ever commit to uPortal (or make 
a pull request) it would be great to have you setup a GitHub account 
and get the appropriate mapping information added to file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but have 
NOT yet setup an account on GitHub, meaning that their commit history 
won't transfer AND they won't be able to commit once we've moved. 
Please either email me your GitHub account info (should look like: 
Eric Dalquist ) or event better, get to know 
git and fork https://github.com/Jasig/svn2git-migration add yourself 
to mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available for uPortal committers


Unless there are objections the schedule will proceed as stated 
above. Realistically the GitHub repo should be available much earlier 
than 4pm but don't plan on making any commits to uPortal on Thursday 
10/20 and if you have any work in progress make sure it is committed 
somewhere (create a temporary branch if needed) so that you don't 
have to re-apply the changes on the git side of things.


-Eric


--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Good notes, I'll work on getting a more complete version of the workflow 
document published.


-Eric

On 10/13/11 6:35 PM, Cris J Holdorph wrote:
I followed those instructions before I sent my message.  However, 
there are two problems.


One, it's not clear that you have to do the pull request from your 
fork.  If you're viewing the original repository, you see a 'pull 
requests' tab, and so as a NEW UNFAMILIAR user, you might be there, 
click on that tab, see the 'list' of requests (or empty list) and not 
know how to submit one.  You must be on your own repo fork, but that's 
not clear in those instructions.


Two, even when you get to your own repo and find the right screen to 
submit a pull request, you end up at this screen:


http://img.skitch.com/20100831-qit9sjhuqk42t4ww91ifm5tm81.png

Except in your case those two text fields will be blank, with NO 
indication what information should go in those text fields and no 
mention in the instructions about what should go in there.


I guessed and submitted mine, but I had no idea if it would even work, 
when I pressed the 'send pull request' button.


 Cris J H

On 10/13/2011 04:28 PM, Eric Dalquist wrote:

The "Step-by-step (the short version)" section here
https://github.com/diaspora/diaspora/wiki/Git-Workflow has good info,
for something as simple as this you can skip a bunch of the steps
(setting upstream remote and creating dev branch) and boil it down to:

   1. Fork on GitHub (click Fork button)
   2. Clone to computer ($ git clone g...@github.com:you/diaspora.git )
   3. Don’t forget to cd into your repo: ($ cd diaspora/ )
   4. Make changes//
   5. Commit changes to issue branch. ($ git add . ; git commit -m
  ‘commit message’)
   6. Push branch to GitHub ($ git push)
   7. Issue pull request (Click Pull Request button)

Post migration I'm going to be encouraging people to follow the full set
of steps and do all development on branches. That should let everyone
get the work they are doing out into a visible location earlier in the
development cycle and keep trunk (master) more stable.

-Eric

On 10/13/11 6:12 PM, Cris J Holdorph wrote:

I don't see any way to submit a pull request for
https://github.com/Jasig/svn2git-migration

 Cris J H

ps. I tried to do it the github way, but in any case, my github email
address was/is holdo...@unicon.net

On 10/13/2011 03:51 PM, Eric Dalquist wrote:
Thought I had found a few people by guessing usernames but the 
accounts

didn't have enough publicly available info for me to verify. So that
email was likely from being added and then removed from the team. I'll
still need the "Full Name " string for the
conversion if you care about commit history.

-Eric

On 10/13/11 5:06 PM, Cris J Holdorph wrote:

I got an email from github that said:

View team: https://github.com/organizations/Jasig/teams/68892

but when I got there, I get a github 404.

Any ideas?

 Cris J H

On 10/13/2011 02:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ
is in
the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to:
https://github.com/edalquist/uPortal-GitTest

*Account Mapping*
This is using best author mapping data that we could put together 
from

those that explicitly have listed their git accounts [1] and account
information for jasig SVN committers that was compiled from the
Confluence/Jira services [2]. If you have ever commit to a Jasig
project
in the past and think you may ever commit to uPortal (or make a pull
request) it would be great to have you setup a GitHub account and 
get

the appropriate mapping information added to file [1].

[1]
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt 



[2]
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt 





The following people currently have commit access to uPortal but 
have
NOT yet setup an account on GitHub, meaning that their commit 
history

won't transfer AND they won't be able to commit once we've moved.
Please
either email me your GitHub account info (should look like: Eric
Dalquist ) or event better, get to know
git and
fork https://github.com/Jasig/svn2git-migration add yourself to
mappedAuthors.txt and then make a pull request.

* Andrew Wills (awills)
* Andy Gherna (agherna)
* Anthony Colebourne (acolebourne)
* Brad Szabo (bszabo)
* Cris Holdorph (holdorph)
* Gary Thompson (gthompson)
* Lennard Fuller (lfuller)
* Matthew Polizzotti (mpolizzo...@unicon.net)
* Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
4:00pm CDT - https://github.com/Jasig/uPortal will be live and
available
for uPortal committers

Unless there are objections the schedule will proceed as stated 
above.

Realistically the GitHub repo should be available much earlier than
4pm
but don't plan on making any commits to uPortal on 

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Carroll, Timothy Dale]

so... they should probably match then... right?  email is the common 
denominator to map between the accounts.


On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:

File 2 is the automated output of looking up the name and email address for 
each svn account name from Crowd. File 1 is overlayed on top of File 2 to come 
up with the mapping file used for doing the migration.

-Eric

On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:
do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in the 
wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest

Account Mapping
This is using best author mapping data that we could put together from those 
that explicitly have listed their git accounts [1] and account information for 
jasig SVN committers that was compiled from the Confluence/Jira services [2]. 
If you have ever commit to a Jasig project in the past and think you may ever 
commit to uPortal (or make a pull request) it would be great to have you setup 
a GitHub account and get the appropriate mapping information added to file [1].

[1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt

The following people currently have commit access to uPortal but have NOT yet 
setup an account on GitHub, meaning that their commit history won't transfer 
AND they won't be able to commit once we've moved. Please either email me your 
GitHub account info (should look like: Eric Dalquist 
) or event better, get 
to know git and fork https://github.com/Jasig/svn2git-migration add yourself to 
mappedAuthors.txt and then make a pull request.

  *   Andrew Wills (awills)
  *   Andy Gherna (agherna)
  *   Anthony Colebourne (acolebourne)
  *   Brad Szabo (bszabo)
  *   Cris Holdorph (holdorph)
  *   Gary Thompson (gthompson)
  *   Lennard Fuller (lfuller)
  *   Matthew Polizzotti (mpolizzo...@unicon.net)
  *   Susan Bramhall (susan.bramh...@yale.edu)

Scheduling
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and available 
for uPortal committers

Unless there are objections the schedule will proceed as stated above. 
Realistically the GitHub repo should be available much earlier than 4pm but 
don't plan on making any commits to uPortal on Thursday 10/20 and if you have 
any work in progress make sure it is committed somewhere (create a temporary 
branch if needed) so that you don't have to re-apply the changes on the git 
side of things.

-Eric


--

You are currently subscribed to 
uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


-- 
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Sorry, my previous reply wasn't very clear.

So for the author mapping feature of svn2git to work we have to have 
"Name " format mappings for every SVN committer that the tool 
encounters. Since the chances of getting everyone that has ever 
committed to uPortal (all 74 of them) to create a GitHub account is very 
small I decided to put together two lists.


resolvedAuthors.txt - A best guess at GitHub account info made by 
looking up each SVN account in the Jasig Crowd directory and using the 
name and email address registered for the account. This doesn't even 
work for really old committers so those accounts get fake mappings that 
look like: aha...@committers.jasig.org . 
The important thing to remember is that this file is automatically 
generated, there was no hand editing of its data.


mappedAuthors.txt - Explicit SVN username to GitHub account mappings. 
Every existing Jasig committer that has a GitHub account should list the 
mapping between their accounts here.


When I run svn2git I first use the little mergeAuthors.groovy script 
which merges the two files with the mappings in mappedAuthors.txt 
replacing mappings from resolvedAuthors.txt.


So no, the email address don't need to match, the email address in 
resolvedAuthors.txt is a best guess for each svn account. The email 
address in mappedAuthors.txt is your actual GitHub account email address.


-Eric

On 10/13/11 10:34 PM, Carroll, Timothy Dale wrote:
so... they should probably match then... right?  email is the common 
denominator to map between the accounts.



On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:

File 2 is the automated output of looking up the name and email 
address for each svn account name from Crowd. File 1 is overlayed on 
top of File 2 to come up with the mapping file used for doing the 
migration.


-Eric

On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:

do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ 
is in the wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together 
from those that explicitly have listed their git accounts [1] and 
account information for jasig SVN committers that was compiled from 
the Confluence/Jira services [2]. If you have ever commit to a 
Jasig project in the past and think you may ever commit to uPortal 
(or make a pull request) it would be great to have you setup a 
GitHub account and get the appropriate mapping information added to 
file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but 
have NOT yet setup an account on GitHub, meaning that their commit 
history won't transfer AND they won't be able to commit once we've 
moved. Please either email me your GitHub account info (should look 
like: Eric Dalquist ) or event better, get 
to know git and fork https://github.com/Jasig/svn2git-migration add 
yourself to mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live 
and available for uPortal committers


Unless there are objections the schedule will proceed as stated 
above. Realistically the GitHub repo should be available much 
earlier than 4pm but don't plan on making any commits to uPortal on 
Thursday 10/20 and if you have any work in progress make sure it is 
committed somewhere (create a temporary branch if needed) so that 
you don't have to re-apply the changes on the git side of things.


-Eric


--

You are currently subscribed touportal-...@lists.ja-sig.org  
as:eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, 
seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev


--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Carroll, Timothy Dale]

okay. so i think the confusing part was that i don't put my github ID anywhere. 
 i just need to put one of the email addresses that is associated with my 
github ID in that file.  like this:

tim = tim carroll mailto:t...@logiclander.com>>

where the name part "tim carroll" is actually completely meaningless and 
arbitrary.  i was thinking that somewhere there would be a mapping of my jasig 
ID to my github ID directly.  like this:

tim = timit


On Oct 13, 2011, at 11:59 PM, Eric Dalquist wrote:

Sorry, my previous reply wasn't very clear.

So for the author mapping feature of svn2git to work we have to have "Name 
" format mappings for every SVN committer that the tool 
encounters. Since the chances of getting everyone that has ever committed to 
uPortal (all 74 of them) to create a GitHub account is very small I decided to 
put together two lists.

resolvedAuthors.txt - A best guess at GitHub account info made by looking up 
each SVN account in the Jasig Crowd directory and using the name and email 
address registered for the account. This doesn't even work for really old 
committers so those accounts get fake mappings that look like: 
aha...@committers.jasig.org 
. The 
important thing to remember is that this file is automatically generated, there 
was no hand editing of its data.

mappedAuthors.txt - Explicit SVN username to GitHub account mappings. Every 
existing Jasig committer that has a GitHub account should list the mapping 
between their accounts here.

When I run svn2git I first use the little mergeAuthors.groovy script which 
merges the two files with the mappings in mappedAuthors.txt replacing mappings 
from resolvedAuthors.txt.

So no, the email address don't need to match, the email address in 
resolvedAuthors.txt is a best guess for each svn account. The email address in 
mappedAuthors.txt is your actual GitHub account email address.

-Eric

On 10/13/11 10:34 PM, Carroll, Timothy Dale wrote:
so... they should probably match then... right?  email is the common 
denominator to map between the accounts.


On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:

File 2 is the automated output of looking up the name and email address for 
each svn account name from Crowd. File 1 is overlayed on top of File 2 to come 
up with the mapping file used for doing the migration.

-Eric

On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:
do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in the 
wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal

I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest

Account Mapping
This is using best author mapping data that we could put together from those 
that explicitly have listed their git accounts [1] and account information for 
jasig SVN committers that was compiled from the Confluence/Jira services [2]. 
If you have ever commit to a Jasig project in the past and think you may ever 
commit to uPortal (or make a pull request) it would be great to have you setup 
a GitHub account and get the appropriate mapping information added to file [1].

[1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt

The following people currently have commit access to uPortal but have NOT yet 
setup an account on GitHub, meaning that their commit history won't transfer 
AND they won't be able to commit once we've moved. Please either email me your 
GitHub account info (should look like: Eric Dalquist 
) or event better, get 
to know git and fork https://github.com/Jasig/svn2git-migration add yourself to 
mappedAuthors.txt and then make a pull request.

  *   Andrew Wills (awills)
  *   Andy Gherna (agherna)
  *   Anthony Colebourne (acolebourne)
  *   Brad Szabo (bszabo)
  *   Cris Holdorph (holdorph)
  *   Gary Thompson (gthompson)
  *   Lennard Fuller (lfuller)
  *   Matthew Polizzotti (mpolizzo...@unicon.net)
  *   Susan Bramhall (susan.bramh...@yale.edu)

Scheduling
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and available 
for uPortal committers

Unless there are objections the schedule will proceed as stated above. 
Realistically the GitHub repo should be available much earlier than 4pm but 
don't plan on making any commits to uPortal on Thursday 10/20 and if you have 
any work in progress make sure it is committed somewhere (create a temporary 
branch if needed) so that you don't have to re-apply 

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Yeah, it is a little weird but that is apparently how the git commit 
message stuff works. The name part is just decorative, the email address 
is what matters.


-Eric

On 10/13/11 11:28 PM, Carroll, Timothy Dale wrote:
okay. so i think the confusing part was that i don't put my github ID 
anywhere.  i just need to put one of the email addresses that is 
associated with my github ID in that file.  like this:


tim = tim carroll mailto:t...@logiclander.com>>

where the name part "tim carroll" is actually completely meaningless 
and arbitrary.  i was thinking that somewhere there would be a mapping 
of my jasig ID to my github ID directly.  like this:


tim = timit


On Oct 13, 2011, at 11:59 PM, Eric Dalquist wrote:


Sorry, my previous reply wasn't very clear.

So for the author mapping feature of svn2git to work we have to have 
"Name " format mappings for every SVN committer that the tool 
encounters. Since the chances of getting everyone that has ever 
committed to uPortal (all 74 of them) to create a GitHub account is 
very small I decided to put together two lists.


resolvedAuthors.txt - A best guess at GitHub account info made by 
looking up each SVN account in the Jasig Crowd directory and using 
the name and email address registered for the account. This doesn't 
even work for really old committers so those accounts get fake 
mappings that look like: aha...@committers.jasig.org 
. The important thing to remember is 
that this file is automatically generated, there was no hand editing 
of its data.


mappedAuthors.txt - Explicit SVN username to GitHub account mappings. 
Every existing Jasig committer that has a GitHub account should list 
the mapping between their accounts here.


When I run svn2git I first use the little mergeAuthors.groovy script 
which merges the two files with the mappings in mappedAuthors.txt 
replacing mappings from resolvedAuthors.txt.


So no, the email address don't need to match, the email address in 
resolvedAuthors.txt is a best guess for each svn account. The email 
address in mappedAuthors.txt is your actual GitHub account email address.


-Eric

On 10/13/11 10:34 PM, Carroll, Timothy Dale wrote:
so... they should probably match then... right?  email is the common 
denominator to map between the accounts.



On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:

File 2 is the automated output of looking up the name and email 
address for each svn account name from Crowd. File 1 is overlayed 
on top of File 2 to come up with the mapping file used for doing 
the migration.


-Eric

On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:

do the email addresses used in file [1] and [2] need to match?

On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:

Details of the uPortal SVN to GitHub migration, reasoning, and 
FAQ is in the wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository 
to: https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together 
from those that explicitly have listed their git accounts [1] and 
account information for jasig SVN committers that was compiled 
from the Confluence/Jira services [2]. If you have ever commit to 
a Jasig project in the past and think you may ever commit to 
uPortal (or make a pull request) it would be great to have you 
setup a GitHub account and get the appropriate mapping 
information added to file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but 
have NOT yet setup an account on GitHub, meaning that their 
commit history won't transfer AND they won't be able to commit 
once we've moved. Please either email me your GitHub account info 
(should look like: Eric Dalquist ) or 
event better, get to know git and fork 
https://github.com/Jasig/svn2git-migration add yourself to 
mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live 
and available for uPortal committers


Unless there are objections the schedule will proceed as stated 
above. Realistically the GitHub repo should be available much 
earlier than 4pm but don't plan on making any commits to uPortal 
on Thursday 10/20 and if you have any work in progress make sure 
it is committed somewhere (create a temporary branch if needed) 
so that you don't have to re-apply the changes on the git side of 
things.


-Eri

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Nicholas Blair]

I'm a bit stuck at the point where I push my changes back.

I've got my development environment setup completely, cloned the project,
created a local branch, and committed my changes to the local branch.

When I perform what I believe to be the "push" from my changed branch back
to my master (the original clone), I execute the following:

git push origin add-nblair-branch
Everything up-to-date

Here's my repo:
https://github.com/nblair/svn2git-migration

And you can see my change on the "add-nblair-branch:
https://github.com/nblair/svn2git-migration/branches

So what steps do I follow from here?

Thanks!

On Thu, Oct 13, 2011 at 11:42 PM, Eric Dalquist  wrote:

>  Yeah, it is a little weird but that is apparently how the git commit
> message stuff works. The name part is just decorative, the email address is
> what matters.
>
> -Eric
>
>
> On 10/13/11 11:28 PM, Carroll, Timothy Dale wrote:
>
> okay. so i think the confusing part was that i don't put my github ID
> anywhere.  i just need to put one of the email addresses that is associated
> with my github ID in that file.  like this:
>
>  tim = tim carroll 
>
>  where the name part "tim carroll" is actually completely meaningless and
> arbitrary.  i was thinking that somewhere there would be a mapping of my
> jasig ID to my github ID directly.  like this:
>
>  tim = timit
>
>
>  On Oct 13, 2011, at 11:59 PM, Eric Dalquist wrote:
>
>  Sorry, my previous reply wasn't very clear.
>
> So for the author mapping feature of svn2git to work we have to have "Name
>  " format mappings for every SVN committer that the tool
> encounters. Since the chances of getting everyone that has ever committed to
> uPortal (all 74 of them) to create a GitHub account is very small I decided
> to put together two lists.
>
> resolvedAuthors.txt - A best guess at GitHub account info made by looking
> up each SVN account in the Jasig Crowd directory and using the name and
> email address registered for the account. This doesn't even work for really
> old committers so those accounts get fake mappings that look like:
> aha...@committers.jasig.org 
> .
> The important thing to remember is that this file is automatically
> generated, there was no hand editing of its data.
>
> mappedAuthors.txt - Explicit SVN username to GitHub account mappings. Every
> existing Jasig committer that has a GitHub account should list the mapping
> between their accounts here.
>
> When I run svn2git I first use the little mergeAuthors.groovy script which
> merges the two files with the mappings in mappedAuthors.txt replacing
> mappings from resolvedAuthors.txt.
>
> So no, the email address don't need to match, the email address in
> resolvedAuthors.txt is a best guess for each svn account. The email address
> in mappedAuthors.txt is your actual GitHub account email address.
>
> -Eric
>
> On 10/13/11 10:34 PM, Carroll, Timothy Dale wrote:
>
> so... they should probably match then... right?  email is the common
> denominator to map between the accounts.
>
>
>  On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:
>
>  File 2 is the automated output of looking up the name and email address
> for each svn account name from Crowd. File 1 is overlayed on top of File 2
> to come up with the mapping file used for doing the migration.
>
> -Eric
>
> On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:
>
> do the email addresses used in file [1] and [2] need to match?
>
>  On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:
>
>  Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in
> the wiki: 
> https://wiki.jasig.org/display/UPC/Git+Migration+Proposal
>
> I've done a final test migration of the uPortal SVN repository to:
> https://github.com/edalquist/uPortal-GitTest
>
> *Account Mapping*
> This is using best author mapping data that we could put together from
> those that explicitly have listed their git accounts [1] and account
> information for jasig SVN committers that was compiled from the
> Confluence/Jira services [2]. If you have ever commit to a Jasig project in
> the past and think you may ever commit to uPortal (or make a pull request)
> it would be great to have you setup a GitHub account and get the appropriate
> mapping information added to file [1].
>
> [1]
> https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
> [2]
> https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt
>
> The following people currently have commit access to uPortal but have NOT
> yet setup an account on GitHub, meaning that their commit history won't
> transfer AND they won't be able to commit once we've moved. Please either
> email me your GitHub account info (should look like: Eric Dalquist
>  ) or event better, get
> to know git and fork https://github.com/Jasig/svn2git-migration add
> yourself to mappedAuthors.txt and then make a pull request.
>
>- Andrew Wills (awills)
>- A

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Nicholas Blair]

That did the trick - thanks!

On Fri, Oct 14, 2011 at 10:10 AM, Eric Dalquist  wrote:

>  From that branches list page click on add-nblair-branch which should take
> you to:
>
> https://github.com/nblair/svn2git-migration/tree/add-nblair-branch
>
> There should be a button on the upper right named Pull Request. There are
> two screenshots attached with more detail.
>
> -Eric
>
>
>
>
>
>
> On 10/14/11 9:40 AM, Nicholas Blair wrote:
>
> I'm a bit stuck at the point where I push my changes back.
>
> I've got my development environment setup completely, cloned the project,
> created a local branch, and committed my changes to the local branch.
>
> When I perform what I believe to be the "push" from my changed branch back
> to my master (the original clone), I execute the following:
>
> git push origin add-nblair-branch
> Everything up-to-date
>
> Here's my repo:
> https://github.com/nblair/svn2git-migration
>
> And you can see my change on the "add-nblair-branch:
> https://github.com/nblair/svn2git-migration/branches
>
> So what steps do I follow from here?
>
> Thanks!
>
> On Thu, Oct 13, 2011 at 11:42 PM, Eric Dalquist <
> eric.dalqu...@doit.wisc.edu> wrote:
>
>>  Yeah, it is a little weird but that is apparently how the git commit
>> message stuff works. The name part is just decorative, the email address is
>> what matters.
>>
>> -Eric
>>
>>
>> On 10/13/11 11:28 PM, Carroll, Timothy Dale wrote:
>>
>> okay. so i think the confusing part was that i don't put my github ID
>> anywhere.  i just need to put one of the email addresses that is associated
>> with my github ID in that file.  like this:
>>
>>  tim = tim carroll 
>>
>>  where the name part "tim carroll" is actually completely meaningless and
>> arbitrary.  i was thinking that somewhere there would be a mapping of my
>> jasig ID to my github ID directly.  like this:
>>
>>  tim = timit
>>
>>
>>  On Oct 13, 2011, at 11:59 PM, Eric Dalquist wrote:
>>
>>  Sorry, my previous reply wasn't very clear.
>>
>> So for the author mapping feature of svn2git to work we have to have "Name
>>  " format mappings for every SVN committer that the tool
>> encounters. Since the chances of getting everyone that has ever committed to
>> uPortal (all 74 of them) to create a GitHub account is very small I decided
>> to put together two lists.
>>
>> resolvedAuthors.txt - A best guess at GitHub account info made by looking
>> up each SVN account in the Jasig Crowd directory and using the name and
>> email address registered for the account. This doesn't even work for really
>> old committers so those accounts get fake mappings that look like:
>> aha...@committers.jasig.org 
>> .
>> The important thing to remember is that this file is automatically
>> generated, there was no hand editing of its data.
>>
>> mappedAuthors.txt - Explicit SVN username to GitHub account mappings.
>> Every existing Jasig committer that has a GitHub account should list the
>> mapping between their accounts here.
>>
>> When I run svn2git I first use the little mergeAuthors.groovy script which
>> merges the two files with the mappings in mappedAuthors.txt replacing
>> mappings from resolvedAuthors.txt.
>>
>> So no, the email address don't need to match, the email address in
>> resolvedAuthors.txt is a best guess for each svn account. The email address
>> in mappedAuthors.txt is your actual GitHub account email address.
>>
>> -Eric
>>
>> On 10/13/11 10:34 PM, Carroll, Timothy Dale wrote:
>>
>> so... they should probably match then... right?  email is the common
>> denominator to map between the accounts.
>>
>>
>>  On Oct 13, 2011, at 11:00 PM, Eric Dalquist wrote:
>>
>>  File 2 is the automated output of looking up the name and email address
>> for each svn account name from Crowd. File 1 is overlayed on top of File 2
>> to come up with the mapping file used for doing the migration.
>>
>> -Eric
>>
>> On 10/13/11 7:49 PM, Carroll, Timothy Dale wrote:
>>
>> do the email addresses used in file [1] and [2] need to match?
>>
>>  On Oct 13, 2011, at 5:20 PM, Eric Dalquist wrote:
>>
>>  Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in
>> the wiki: 
>> https://wiki.jasig.org/display/UPC/Git+Migration+Proposal
>>
>> I've done a final test migration of the uPortal SVN repository to:
>> https://github.com/edalquist/uPortal-GitTest
>>
>> *Account Mapping*
>> This is using best author mapping data that we could put together from
>> those that explicitly have listed their git accounts [1] and account
>> information for jasig SVN committers that was compiled from the
>> Confluence/Jira services [2]. If you have ever commit to a Jasig project in
>> the past and think you may ever commit to uPortal (or make a pull request)
>> it would be great to have you setup a GitHub account and get the appropriate
>> mapping information added to file [1].
>>
>> [1]
>> https://github.com/Jasig/svn2git-migration/blob/mas

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

A reminder that uPortal will be moving to GitHub tomorrow (Thursday 
10/19). If you have any uncommitted changes get them in tonight 
otherwise you'll have to create a patch and apply it to your git clone. 
I'll send out emails when the work starts and completes.


The following users still do not have mapping details:

 * Anthony Colebourne (acolebourne)
 * Gary Thompson (gthompson)
 * Lennard Fuller (lfuller)
 * Matthew Polizzotti (mpolizzo...@unicon.net)
 * Susan Bramhall (susan.bramh...@yale.edu)

-Eric

On 10/13/2011 04:20 PM, Eric Dalquist wrote:
Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is 
in the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together from 
those that explicitly have listed their git accounts [1] and account 
information for jasig SVN committers that was compiled from the 
Confluence/Jira services [2]. If you have ever commit to a Jasig 
project in the past and think you may ever commit to uPortal (or make 
a pull request) it would be great to have you setup a GitHub account 
and get the appropriate mapping information added to file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but have 
NOT yet setup an account on GitHub, meaning that their commit history 
won't transfer AND they won't be able to commit once we've moved. 
Please either email me your GitHub account info (should look like: 
Eric Dalquist ) or event better, get to know 
git and fork https://github.com/Jasig/svn2git-migration add yourself 
to mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available for uPortal committers


Unless there are objections the schedule will proceed as stated above. 
Realistically the GitHub repo should be available much earlier than 
4pm but don't plan on making any commits to uPortal on Thursday 10/20 
and if you have any work in progress make sure it is committed 
somewhere (create a temporary branch if needed) so that you don't have 
to re-apply the changes on the git side of things.


-Eric 


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Steve Swinsburg]

Is the whole repo moving, or just the uPortal part? I am getting ready to 
commit the source for a few incubating portlets so presume that still goes into 
SVN?

cheers,
Steve



On 20/10/2011, at 5:52 AM, Eric Dalquist wrote:

> A reminder that uPortal will be moving to GitHub tomorrow (Thursday 10/19). 
> If you have any uncommitted changes get them in tonight otherwise you'll have 
> to create a patch and apply it to your git clone. I'll send out emails when 
> the work starts and completes.
> 
> The following users still do not have mapping details:
> Anthony Colebourne (acolebourne)
> Gary Thompson (gthompson)
> Lennard Fuller (lfuller)
> Matthew Polizzotti (mpolizzo...@unicon.net)
> Susan Bramhall (susan.bramh...@yale.edu)
> -Eric
> 
> On 10/13/2011 04:20 PM, Eric Dalquist wrote:
>> 
>> Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is in the 
>> wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal
>> 
>> I've done a final test migration of the uPortal SVN repository to: 
>> https://github.com/edalquist/uPortal-GitTest
>> 
>> Account Mapping
>> This is using best author mapping data that we could put together from those 
>> that explicitly have listed their git accounts [1] and account information 
>> for jasig SVN committers that was compiled from the Confluence/Jira services 
>> [2]. If you have ever commit to a Jasig project in the past and think you 
>> may ever commit to uPortal (or make a pull request) it would be great to 
>> have you setup a GitHub account and get the appropriate mapping information 
>> added to file [1].
>> 
>> [1] https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
>> [2] 
>> https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt
>> 
>> The following people currently have commit access to uPortal but have NOT 
>> yet setup an account on GitHub, meaning that their commit history won't 
>> transfer AND they won't be able to commit once we've moved. Please either 
>> email me your GitHub account info (should look like: Eric Dalquist 
>> ) or event better, get to know git and fork 
>> https://github.com/Jasig/svn2git-migration add yourself to mappedAuthors.txt 
>> and then make a pull request.
>> Andrew Wills (awills)
>> Andy Gherna (agherna)
>> Anthony Colebourne (acolebourne)
>> Brad Szabo (bszabo)
>> Cris Holdorph (holdorph)
>> Gary Thompson (gthompson)
>> Lennard Fuller (lfuller)
>> Matthew Polizzotti (mpolizzo...@unicon.net)
>> Susan Bramhall (susan.bramh...@yale.edu)
>> 
>> Scheduling
>> 10/20 - Thursday
>> 10:00am CDT - https://source.jasig.org/uPortal is made read-only
>>   4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
>> available for uPortal committers
>> 
>> Unless there are objections the schedule will proceed as stated above. 
>> Realistically the GitHub repo should be available much earlier than 4pm but 
>> don't plan on making any commits to uPortal on Thursday 10/20 and if you 
>> have any work in progress make sure it is committed somewhere (create a 
>> temporary branch if needed) so that you don't have to re-apply the changes 
>> on the git side of things.
>> 
>> -Eric


-- 
You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

Yes this only applies to https://source.jasig.org/uPortal

The source hosting (SVN or GitHub) of other projects is up to each 
project's developers.


-Eric

On 10/19/11 5:32 PM, Steve Swinsburg wrote:
Is the whole repo moving, or just the uPortal part? I am getting ready 
to commit the source for a few incubating portlets so presume that 
still goes into SVN?


cheers,
Steve



On 20/10/2011, at 5:52 AM, Eric Dalquist wrote:

A reminder that uPortal will be moving to GitHub tomorrow (Thursday 
10/19). If you have any uncommitted changes get them in tonight 
otherwise you'll have to create a patch and apply it to your git 
clone. I'll send out emails when the work starts and completes.


The following users still do not have mapping details:

  * Anthony Colebourne (acolebourne)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)

-Eric

On 10/13/2011 04:20 PM, Eric Dalquist wrote:
Details of the uPortal SVN to GitHub migration, reasoning, and FAQ 
is in the wiki: 
https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together 
from those that explicitly have listed their git accounts [1] and 
account information for jasig SVN committers that was compiled from 
the Confluence/Jira services [2]. If you have ever commit to a Jasig 
project in the past and think you may ever commit to uPortal (or 
make a pull request) it would be great to have you setup a GitHub 
account and get the appropriate mapping information added to file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but 
have NOT yet setup an account on GitHub, meaning that their commit 
history won't transfer AND they won't be able to commit once we've 
moved. Please either email me your GitHub account info (should look 
like: Eric Dalquist ) or event better, get 
to know git and fork https://github.com/Jasig/svn2git-migration add 
yourself to mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available for uPortal committers


Unless there are objections the schedule will proceed as stated 
above. Realistically the GitHub repo should be available much 
earlier than 4pm but don't plan on making any commits to uPortal on 
Thursday 10/20 and if you have any work in progress make sure it is 
committed somewhere (create a temporary branch if needed) so that 
you don't have to re-apply the changes on the git side of things.


-Eric 


--

You are currently subscribed to uportal-dev@lists.ja-sig.org as: 
eric.dalqu...@doit.wisc.edu
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [uportal-dev] Move uPortal source to GitHub Schedule

[Eric Dalquist]

uPortal SVN is now read only. I'll send a follow up when the GitHub 
repository is online.


-Eric

On 10/19/2011 01:52 PM, Eric Dalquist wrote:
A reminder that uPortal will be moving to GitHub tomorrow (Thursday 
10/19). If you have any uncommitted changes get them in tonight 
otherwise you'll have to create a patch and apply it to your git 
clone. I'll send out emails when the work starts and completes.


The following users still do not have mapping details:

  * Anthony Colebourne (acolebourne)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)

-Eric

On 10/13/2011 04:20 PM, Eric Dalquist wrote:
Details of the uPortal SVN to GitHub migration, reasoning, and FAQ is 
in the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal


I've done a final test migration of the uPortal SVN repository to: 
https://github.com/edalquist/uPortal-GitTest


*Account Mapping*
This is using best author mapping data that we could put together 
from those that explicitly have listed their git accounts [1] and 
account information for jasig SVN committers that was compiled from 
the Confluence/Jira services [2]. If you have ever commit to a Jasig 
project in the past and think you may ever commit to uPortal (or make 
a pull request) it would be great to have you setup a GitHub account 
and get the appropriate mapping information added to file [1].


[1] 
https://github.com/Jasig/svn2git-migration/blob/master/mappedAuthors.txt
[2] 
https://github.com/Jasig/svn2git-migration/blob/master/resolvedAuthors.txt


The following people currently have commit access to uPortal but have 
NOT yet setup an account on GitHub, meaning that their commit history 
won't transfer AND they won't be able to commit once we've moved. 
Please either email me your GitHub account info (should look like: 
Eric Dalquist ) or event better, get to know 
git and fork https://github.com/Jasig/svn2git-migration add yourself 
to mappedAuthors.txt and then make a pull request.


  * Andrew Wills (awills)
  * Andy Gherna (agherna)
  * Anthony Colebourne (acolebourne)
  * Brad Szabo (bszabo)
  * Cris Holdorph (holdorph)
  * Gary Thompson (gthompson)
  * Lennard Fuller (lfuller)
  * Matthew Polizzotti (mpolizzo...@unicon.net)
  * Susan Bramhall (susan.bramh...@yale.edu)


*Scheduling*
10/20 - Thursday
10:00am CDT - https://source.jasig.org/uPortal is made read-only
  4:00pm CDT - https://github.com/Jasig/uPortal will be live and 
available for uPortal committers


Unless there are objections the schedule will proceed as stated 
above. Realistically the GitHub repo should be available much earlier 
than 4pm but don't plan on making any commits to uPortal on Thursday 
10/20 and if you have any work in progress make sure it is committed 
somewhere (create a temporary branch if needed) so that you don't 
have to re-apply the changes on the git side of things.


-Eric 


smime.p7s
Description: S/MIME Cryptographic Signature