Re: Access to Git
Hello, Concerning the workflow, how about using Gitflow? [1] Advantages are: - keeps a clean master branch, work is on the develop branch - good for multiple (historical) versions - good integration with sourcetree Please consider. Thanks, Anthony [1] : https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow On Thu, Sep 15, 2016 at 8:34 AM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > Also please look at: http://wiki.apache.org/tika/UsingGit for a guide on > how > to migrate your OpenNLP SVN to Git.. > > ++ > Chris Mattmann, Ph.D. > Chief Architect, Instrument Software and Science Data Systems Section (398) > Manager, Open Source Projects Formulation and Development Office (8212) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Director, Information Retrieval and Data Science Group (IRDS) > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > WWW: http://irds.usc.edu/ > ++ > > > > On 9/14/16, 4:12 PM, "Joern Kottmann" wrote: > > Sorry, it took me a little to figure this out. > > This link explains how it works: > https://reference.apache.org/committer/git > > The reponame is opennlp, we will soon also have the other repos > opennlp-addons and opennlp-sandbox. > > Jörn > > On Fri, Sep 9, 2016 at 10:58 PM, Joern Kottmann > wrote: > > > Hello, yes you can use it. The add-ons and other things are not > setup yet > > as far as I know, have to ping the infra team about it. > > > > Please have a look at the issue I posted to see how to access it. > > > > I will work on this on Monday. > > > > HTH > > Jörn > > > > On Sep 9, 2016 19:10, "William Colen" > wrote: > > > >> Hello, > >> > >> Is the Git repository ready for use? > >> Do we need to wait for it to develop new stuff? > >> > >> Thank you, > >> William > >> > > > > > >
Re: Access to Git
Also please look at: http://wiki.apache.org/tika/UsingGit for a guide on how to migrate your OpenNLP SVN to Git.. ++ Chris Mattmann, Ph.D. Chief Architect, Instrument Software and Science Data Systems Section (398) Manager, Open Source Projects Formulation and Development Office (8212) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA WWW: http://irds.usc.edu/ ++ On 9/14/16, 4:12 PM, "Joern Kottmann" wrote: Sorry, it took me a little to figure this out. This link explains how it works: https://reference.apache.org/committer/git The reponame is opennlp, we will soon also have the other repos opennlp-addons and opennlp-sandbox. Jörn On Fri, Sep 9, 2016 at 10:58 PM, Joern Kottmann wrote: > Hello, yes you can use it. The add-ons and other things are not setup yet > as far as I know, have to ping the infra team about it. > > Please have a look at the issue I posted to see how to access it. > > I will work on this on Monday. > > HTH > Jörn > > On Sep 9, 2016 19:10, "William Colen" wrote: > >> Hello, >> >> Is the Git repository ready for use? >> Do we need to wait for it to develop new stuff? >> >> Thank you, >> William >> >
Re: Access to Git
Sorry, it took me a little to figure this out. This link explains how it works: https://reference.apache.org/committer/git The reponame is opennlp, we will soon also have the other repos opennlp-addons and opennlp-sandbox. Jörn On Fri, Sep 9, 2016 at 10:58 PM, Joern Kottmann wrote: > Hello, yes you can use it. The add-ons and other things are not setup yet > as far as I know, have to ping the infra team about it. > > Please have a look at the issue I posted to see how to access it. > > I will work on this on Monday. > > HTH > Jörn > > On Sep 9, 2016 19:10, "William Colen" wrote: > >> Hello, >> >> Is the Git repository ready for use? >> Do we need to wait for it to develop new stuff? >> >> Thank you, >> William >> >