Re: [cmake-developers] gitlab or github? Which should I use for contribution?

2016-10-27 Thread Stuermer, Michael SP/HZA-ZSEP
> -Original Message-
> From: Brad King [mailto:brad.k...@kitware.com]
> Sent: Wednesday, October 26, 2016 5:13 PM
> To: Stuermer, Michael SP/HZA-ZSEP
> Cc: cmake-developers@cmake.org
> Subject: Re: [cmake-developers] gitlab or github? Which should I use for
> contribution?
> 
> On 10/26/2016 10:05 AM, Stuermer, Michael  SP/HZA-ZSEP wrote:
> > Which should I choose for future contributions?
> 
> GitLab, please.  We recently updated CONTRIBUTING.rst to prefer it even
> over patches on this list.
> 
> > My feeling is I could completely abandon the github repository and
> > pull and push only to gitlab.kitware.com.
> 
> Yes.
> 
> > I can't see all the other branches like maint, next, nightly-* etc.
> > on the gitlab repo. Still these branches get regularly updated on
> > github. This makes me feel like the gitlab repo is somehow "incomplete".
> 
> The `maint` branch has not proven useful and may be dropped one day.
> The `next` and `nightly` branches are only for the nightly testing
> infrastructure and not something developers need to use.
> 
> The GitHub repo is just a mirror of the cmake.org repo and has always had
> the extra branches and so still does.  The GitLab repo is where we are trying
> to move development so we're populating it only with the branches needed
> by developers.
> 
> -Brad
> .

thanks for the information, exactly what I needed!
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] gitlab or github? Which should I use for contribution?

2016-10-26 Thread Brad King
On 10/26/2016 10:05 AM, Stuermer, Michael  SP/HZA-ZSEP wrote:
> Which should I choose for future contributions?

GitLab, please.  We recently updated CONTRIBUTING.rst to prefer
it even over patches on this list.

> My feeling is I could completely abandon the github repository
> and pull and push only to gitlab.kitware.com.

Yes.

> I can't see all the other branches like maint, next, nightly-* etc.
> on the gitlab repo. Still these branches get regularly updated on
> github. This makes me feel like the gitlab repo is somehow "incomplete".

The `maint` branch has not proven useful and may be dropped one day.
The `next` and `nightly` branches are only for the nightly testing
infrastructure and not something developers need to use.

The GitHub repo is just a mirror of the cmake.org repo and has always
had the extra branches and so still does.  The GitLab repo is where
we are trying to move development so we're populating it only with the
branches needed by developers.

-Brad
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] gitlab or github? Which should I use for contribution?

2016-10-26 Thread Stuermer, Michael SP/HZA-ZSEP
I know the cmake repositories on github and gitlab are in sync, so I could base 
my work on any of them. Still I don't want to maintain two forks and would 
prefer to switch completely to gitlab.kitware instead.

Which should I choose for future contributions? My feeling is I could 
completely abandon the github repository and pull and push only to 
gitlab.kitware.com. All merge requests are handled there anyway. Is this right?

I can't see all the other branches like maint, next, nightly-* etc. on the 
gitlab repo. Still these branches get regularly updated on github. This makes 
me feel like the gitlab repo is somehow "incomplete".

Is there some kind of a distinction between "official" and "development" 
repository? 

I'm just trying to understand .

Viele Grüße
Michael Stürmer
   
SZ. Prozessdatenverarbeitung 
SP/HZA-ZSEP  Tel. +499132 82-86350  Mobil.: +49(171)6860010



-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers