Chris, This makes sense to me. I think with git there's a lot of different ways to do things so I think as long as we have a documented way of getting patches from the community that's what's important. Thanks!
- Bob On Wed, Nov 18, 2015 at 8:57 AM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > Thanks Bob. We don’t always have to do patches right now in Tika. > Use CTR if it’s a new area of the code base, and/or if you feel > reasonable about it being a small enough change to go ahead. Use > RTC If you’d like a review and your peers to look at it - if it’s > a long standing area of the code base, etc etc. > > So either way is fine with me and yes, we’d be moving into that > type of workflow. I don’t see getting rid of JIRA though - for > example this workflow: > > https://github.com/apache/tika/#contributing-via-github > > > is what I was thinking just instead of the last (not shown) steps > being e.g., > > git apply < http://github.com/apache/tika/pull/#.patch > svn add * > svn commit > > something instead being > > git pull http://github.com/user/tika/branch > git push -u origin master > > where origin are the ASF writeable repos. > > HTH! > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > 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/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > -----Original Message----- > From: Bob Paulin <b...@bobpaulin.com> > Reply-To: "dev@tika.apache.org" <dev@tika.apache.org> > Date: Wednesday, November 18, 2015 at 9:52 AM > To: "dev@tika.apache.org" <dev@tika.apache.org> > Subject: Re: [DISCUSS] Moving to Git > > >+1 from Me. Most of my work today is also on Git. Just to be clear we'd > >be moving from an SVN workflow patch -> trunk to git workflow PR -> > >master. \ > >- Bob > > > >On Wed, Nov 18, 2015 at 8:48 AM, Tyler Palsulich <tpalsul...@gmail.com> > >wrote: > > > >> +1 from me. > >> > >> Tyler > >> On Nov 18, 2015 6:46 AM, "Mattmann, Chris A (3980)" < > >> chris.a.mattm...@jpl.nasa.gov> wrote: > >> > >> > Hey Team, > >> > > >> > I propose we move to writeable git repos for Tika for our repository. > >> > I mostly interact with Git & Github nowadays even with Tika using the > >> > mirroring and PR interaction support. > >> > > >> > Thoughts? > >> > > >> > Cheers, > >> > Chris > >> > > >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> > Chris Mattmann, Ph.D. > >> > Chief Architect > >> > Instrument Software and Science Data Systems Section (398) > >> > 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/ > >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> > Adjunct Associate Professor, Computer Science Department > >> > University of Southern California, Los Angeles, CA 90089 USA > >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> > > >> > > >> > > >> > > >> > >
