...
[16:20:45 CDT(-0500)] <EricDalquist> and you can interact with both of them
[16:21:08 CDT(-0500)] <drewwills1> er "i see" (well not entorely yet... but i willl)
[16:21:13 CDT(-0500)] <drewwills1> entorely
[16:21:16 CDT(-0500)] <drewwills1> blah
[16:21:19 CDT(-0500)] <EricDalquist> yeah, it takes a bit to get used to 
[16:21:21 CDT(-0500)] <drewwills1> entirely
[16:22:08 CDT(-0500)] <drewwills1> lol @"Hardcore Forking Action"
[16:22:16 CDT(-0500)] <EricDalquist>
[16:22:42 CDT(-0500)] <EricDalquist> I was just chatting with jen about how I want to use git here at UW for our uP4 implementation
[16:23:42 CDT(-0500)] <EricDalquist> my gradually increasing understanding is that we could essentially fork uPortal into our own git hosting server
[16:24:03 CDT(-0500)] <EricDalquist> then create a branch from master for our UW customizations to uP4
[16:24:18 CDT(-0500)] <EricDalquist> then as a developer I would have one uPortal repository checked out
[16:24:48 CDT(-0500)] <EricDalquist> with one remote pointing to github:Jasig/uPortal, one to github:edalquist/uPortal and one to uw:shared/uPortal
[16:25:28 CDT(-0500)] <EricDalquist> and it would let me easily merge in full updates or cherry pick certain commits from Jasig/uPortal into our branch
[16:25:42 CDT(-0500)] <EricDalquist> and I could easily push local features to edalquist/uPortal and make pull requests
[16:26:01 CDT(-0500)] <EricDalquist> so there is a lot of potential for even easier flow of patches between Jasig and deployers