If individual portlet projects are interested in moving that is up to them though the same username mapping info would likely be useful. I'm going to stick the svn2git authors file in the jasig svn repo after we move uPortal's active development so that other projects can use it as well if they are interested.
-Eric On 09/30/2011 02:22 PM, Bruce Tong wrote:
This includes portlet contributions, or just to the core of uPortal? On Fri, Sep 30, 2011 at 3:18 PM, Eric Dalquist <[email protected]> wrote:Great, so with that support I need anyone that has committed to uPortal in the past and is planning on contributing to uPortal in the future to go and sign up for an account on GitHub. Once that is done please either reply here or update the table on the wiki page with your account info: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal#GitMigrationProposal-UsernameMapping For example, I'm "edalquist" in SVN but on GitHub I'm "Eric Dalquist <[email protected]>" This isn't critical but if we don't map usernames when we do the switch your old commits won't be associated with your new GitHub username. -Eric On 09/29/2011 05:56 PM, Cris J Holdorph wrote:My vote after 4.0.1 is released, will be +1. ---- Cris J H On 09/29/2011 03:48 PM, Steve Swinsburg wrote:With the svn read-only mirror and the other discussions that have taken place around governance, my vote is now a +1. cheers, Steve On 30/09/2011, at 7:45 AM, Eric Dalquist wrote:The GitHub migration vote currently stands at: Binding: 3 +1 1 0 0 -0 NonBinding: 2 +1 0 0 0 -0 This is enough to pass by the project voting standards but I wanted to bring this up one last time before scheduling the migration for additional input. The 4.0.1 release will be cut Friday the 30th and announced on Monday. If there is no objection from this discussion I'll work on planning the migration to GitHub after the announcement. One thing I'd like anyone here who contributes code to uPortal, either directly or through patches, is to take a look at this REALLY good git workflow documentation: https://github.com/diaspora/diaspora/wiki/Git-Workflow It is a great example of how get helps provide a much nicer workflow for both developers and the project/branch leads as far as committing and merging in changes. The full proposal is on the wiki: https://wiki.jasig.org/display/UPC/Git+Migration+Proposal -Eric
smime.p7s
Description: S/MIME Cryptographic Signature
