Re: Moving to Git

; great. Not sure it dramatically increased contributions, but it does feel > modern... > > -Original Message- > From: Greg Woolsey [mailto:greg.wool...@gmail.com] > Sent: Wednesday, June 28, 2017 9:37 AM > To: POI Developers List <dev@poi.apache.org> &g

RE: Moving to Git

Developers List <dev@poi.apache.org> Subject: Re: Moving to Git I'd be all for that. Not particularly proficient, but I can Google like everyone else. On Wed, Jun 28, 2017, 01:35 Javen O'Neal <one...@apache.org> wrote: > A fair increase in Github PR's. Having a git repo might increas

Re: Moving to Git

I'm 0 - although I haven't done much with git/-hub, it seems to be the (new) standard ... > Then we'd be able to have github show merged PR's with credit to the > author rather than closed PR's. I wonder what is our stance at credits? ... I usually remove the author tags when I rework code -

Re: Moving to Git

I'd be all for that. Not particularly proficient, but I can Google like everyone else. On Wed, Jun 28, 2017, 01:35 Javen O'Neal wrote: > A fair increase in Github PR's. Having a git repo might increase the > number of (good) PR's we get, as that seems to be where a lot of >

Moving to Git

A fair increase in Github PR's. Having a git repo might increase the number of (good) PR's we get, as that seems to be where a lot of developers are at. Then we'd be able to have github show merged PR's with credit to the author rather than closed PR's. Looks like some of Apache Commons is going