Tracking the original contributor is an important point. The nice thing about git is that every commit has a UUID so even as that commit is pulled from one repository to another the contributor and other details can be tracked. In SVN as things go from one repo to another this is lost (unless it's something like a full repository import).
-David > On 22 Apr 2015, at 10:31, Ean Schuessler <e...@brainfood.com> wrote: > > That raises another irritating thing about the JIRA SVN workflow vs GIT > pull requests. > > If you look at the contributor graph on GitHub for OFBiz you will see > that it currently has only 3 contributors. Foremost this is because the > project committers have mostly not configured their Apache addresses into > their GitHub accounts. Secondly, however, it is caused by the fact that > all JIRA committed patches will show the name of the person who merged > the patch rather than its original author. > > https://github.com/apache/ofbiz/graphs/contributors > > We can make up stories about why this is desirable but I think any honest > assessment would conclude that it is an inconvenience at best and a hazard > at worst. Eventually if these dots are not connected the origins of some > OFBiz code could become as mysterious as the early CVS commits. With the > GIT pull request workflow we would not only know who wrote the code but > would still know who performed the merge. We could also sign the commits > so that their origin is cryptographically confirmed. > > ----- Original Message ----- >> From: "Gil Portenseigne" <gil.portensei...@nereide.fr> >> Subject: Re: move to git. > >> Yes, but these are commiters contributions, i mean non-commiters one should >> go >> thru jira.
