[NeXus-tech] transition to GIT for definitions and documentation

[Peterson, Peter F.]

They've recently (last year or so) redone much of the stuff related to
issues.

Quick version (of github workflow):
 - issues are where you track work to be done
 - create a branch to work on the issue (called a feature branch)
 - when it is done close the issue and make a pull request (this will
appear in the list with issues and a different icon)
 - merge the branch into master (in-web if you like) and delete the
feature branch

It sounds way more complicated than it actually is.
https://github.com/blog/1557-github-flow-in-the-browser explains how it
can be done (mostly) in browser.

P^2

On 9/3/13 9:41 AM, "Wintersberger, Eugen" <eugen.wintersberger at desy.de>
wrote:

>On Tue, 2013-09-03 at 09:37 -0400, Campbell, Stuart I. wrote:
>> I vote we move to github! :-)
>
>How good is the GIT integration with the issue-tracker on github? I can
>remember when I moved away from sourceforge I have chosen GoogleCode as
>a new home for my projects as the issue tracker integration was not as
>good on github. Does this work now?
>
>If this issue has been solved - I already have a github account ;)
>
>> 
>> On 9/3/13 9:28 AM, "freddie.akeroyd at stfc.ac.uk"
>> <freddie.akeroyd at stfc.ac.uk> wrote:
>> 
>> >I'm happy for NeXus code+docs to move to git (and github) is there is a
>> >consensus of opinion - I'm relatively new to git myself at the moment,
>> >but it is something I need to learn anyway. Should we just have a  vote
>> >on nexus-tech ?
>> >
>> >Regards,
>> >
>> >Freddie
>> >
>> >> -----Original Message-----
>> >> From: nexus-tech-bounces at nexusformat.org [mailto:nexus-tech-
>> >> bounces at nexusformat.org] On Behalf Of Campbell, Stuart I.
>> >> Sent: 03 September 2013 13:33
>> >> To: NeXus Technical sub-committee list
>> >> Subject: Re: [NeXus-tech] transition to GIT for definitions and
>> >> documentation
>> >> 
>> >> Hi Eugen,
>> >> 
>> >> The technical details of transferring are trivial, you could always
>>use
>> >> git-svn if you want to use git locally.
>> >> 
>> >> But, this raises a potential bigger question, if we were to move to
>>git,
>> >> why not consider moving wholesale to something like github ?  We
>>could
>> >> move from trac to github issues (I've been playing with migrating
>> >>tickets
>> >> for a different project).
>> >> 
>> >> It feels like there is a critical mass of companies and projects that
>> >>are
>> >> hosted on github - maybe we should be ? :-)
>> >> 
>> >> Cheers
>> >> Stu
>> >> 
>> >> On 9/3/13 8:06 AM, "Wintersberger, Eugen"
>> >> <eugen.wintersberger at desy.de>
>> >> wrote:
>> >> 
>> >> >Hi folks
>> >> >  I was just wondering if it would be possible to migrate the
>> >>repository
>> >> >holding the definitions and the documentation from SVN to GIT.
>> >> >I tried to work with the SVN repository several times, however,
>> >> >branching is a pain with SVN. Besides, GIT could be used offline
>>which
>> >> >is quite comfortable when working while traveling by train ;).
>> >> >I do not know how difficult it would be to make the transition to
>>GIT
>> >> >(at least the current version of Trac works with GIT).
>> >> >What is your opinion about moving to GIT?
>> >> >
>> >> >regards
>> >> >  Eugen
>> >> 
>> >> 
>> >> _______________________________________________
>> >> NeXus-tech mailing list
>> >> NeXus-tech at nexusformat.org
>> >> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>> >-- 
>> >Scanned by iCritical.
>> >
>> >_______________________________________________
>> >NeXus-tech mailing list
>> >NeXus-tech at nexusformat.org
>> >http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>> 
>> 
>> _______________________________________________
>> NeXus-tech mailing list
>> NeXus-tech at nexusformat.org
>> http://lists.nexusformat.org/mailman/listinfo/nexus-tech
>