FWIW I usually use "origin" for the common repository (in this case that
would be git://github.com/geotools/geotools.git) and refer to all others by
user name (including my own.)
--
David Winslow
OpenGeo - http://opengeo.org/
On Sat, Jun 30, 2012 at 12:07 PM, Justin Deoliveira <jdeol...@opengeo.org>wrote:
>
>
> On Sat, Jun 30, 2012 at 10:03 AM, Jody Garnett <jody.garn...@gmail.com>wrote:
>
>> Great idea Justin - that is thinking on your feet. I have successfully
>> to fork, and get set up from github.
>>
>> Your instructions showed up here:
>> -
>> https://github.com/geotools/geotools/blob/master/docs/user/advanced/build/source.rst
>>
>> I took a detour to match how I do things for uDig (well actually the git
>> hub convention of "upstream" being used to refer to the upstream
>> repository):
>> - https://help.github.com/articles/fork-a-repo
>>
>> The extra steps were:
>> git clone g...@github.com:jive/geotools.git
>> cd geotools
>> git remote add upstream g...@github.com:geotools/geotools.git
>>
>> And then to "refresh" my fork:
>> git pull upstream master
>> git push
>>
>> Right... well if this is the recommended way to do its let's update the
> docs to reflect this. My personal preference is to make things explicit and
> always just use the github account id to name the remote. But i do see the
> sense in having origin point back to the developer fork, and upstream point
> to the canonical repo. But let's let other devs weigh in before making a
> choice and updating the official docs.
>
>> --
>> Jody Garnett
>>
>> On Sunday, 1 July 2012 at 12:43 AM, Justin Deoliveira wrote:
>>
>> OK, let's do it. For now I have just cleared out the svn commiter list
>> except for a select few folks so none should hopefully have commit rights
>> anymore.
>>
>> On Sat, Jun 30, 2012 at 3:06 AM, Jody Garnett <jody.garn...@gmail.com>wrote:
>>
>> For number 2 ask on OSGeo channel and/or email sac committee.
>>
>> --
>> Jody Garnett
>>
>> On 30/06/2012, at 12:09 PM, Justin Deoliveira <jdeol...@opengeo.org>
>> wrote:
>>
>> Hi all,
>>
>> So I think from my side everything is in order to do the switch. However
>> still a few things.
>>
>> 1. The proposal still lacks a couple of votes.
>>
>> http://docs.codehaus.org/display/GEOTOOLS/Transition+to+GitHub
>>
>> 2. Waiting on the osgeo folks to turn off commit to the svn repo.
>>
>> http://trac.osgeo.org/osgeo/ticket/913
>>
>> I believe (1) is mostly just a formality at this point, we have a
>> majority positive voice and there haven't been any major concerns raised
>> yet.
>>
>> (2) worries me though. I really don't want to flip the switch until the
>> svn repo is read only so there is no window where folks can be committing
>> to both repos. Although I guess it probably shouldn't be much of a problem
>> unless someone was actually to commit in both places. But still I would
>> rather be safe than sorry.
>>
>> I was hoping to do the switch tomorrow (Saturday) as it works best with
>> my weekend schedule, I won't have as much time on Sunday.
>>
>> Thoughts? Shall we go for it?
>>
>> -Justin
>>
>> --
>> Justin Deoliveira
>> OpenGeo - http://opengeo.org
>> Enterprise support for open source geospatial.
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>>
>>
>>
>> --
>> Justin Deoliveira
>> OpenGeo - http://opengeo.org
>> Enterprise support for open source geospatial.
>>
>>
>>
>
>
> --
> Justin Deoliveira
> OpenGeo - http://opengeo.org
> Enterprise support for open source geospatial.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
