[Insight-developers] Plan to host the SimpleITK git repo here at Kitware

[Brad King]

On 06/03/2011 11:54 AM, Bradley Lowekamp wrote:
> I would hope that we can use the staging area as a place to
> coordinate topics and the next branch. Basically, it should
> allow us to follow the well documented CMake processes using
> the ssh commands on the stage.

This is now configured.  See below.

On 06/06/2011 10:49 AM, Bradley Lowekamp wrote:
> I am in favor have having this done immediately

Done!  See here:

  http://itk.org/SimpleITK.git
  http://itk.org/SimpleITKData.git

and the topic stage:

  http://itk.org/stage/SimpleITK.git

Please stop using the Github histories and clone freshly from itk.org.
Once you are comfortable with the new history you can push it out to
the old github repos to replace the old history.

> We currently have no server side checks on github. This enables bad
> commits which merge next into working topics and other bad practices.
> I think the Kitware stage will help with a lot of these problems, and
> keep track of the open topics.

I cleaned up the commits previously mentioned.

The new itk.org repository hooks enforce use of the topic stage and
'next'.  All ITK developers may push topics to the SimpleITK Topic Stage
and merge them to 'next'.  Only you (Brad L.) can merge to master right
now, but I can enable access for more people.  Perhaps you can review
active topics during your weekly Tcon and choose which ones to merge to
master.

The SimpleITK devs will have to figure out what workflow documentation,
local hooks, and local setup scripts to add.  Currently this generic
documentation applies:

  http://public.kitware.com/Wiki/Git/Workflow/Topic
  http://public.kitware.com/Wiki/Git/Workflow/Stage

> Those changes sound find.

I also re-wrote ".gitmodules" to fix the data submodule URL historically
and added .gitattributes historically.

> How do you propose migrating next, and the topics in there but not merged
> to master? Only the topics really need to be preserved as a new next could
> be created from the head.

I added branches on the topic stage pointing at the existing topics.
One of them is based on next so I named it accordingly.  You'll have to
rebase that topic.

-Brad K