An FYI for all committers: create an account on GitHub (if you don't already 
have one) and add your @apache.org email address to it, and within a few hours 
you'll show up in the contributor graphs. I tried this and am now showing up 
there:

https://github.com/apache/ofbiz/graphs/contributors

If nothing else it's entertaining, I had no idea that I had this volume of 
commits since OFBiz joined the ASF (750k lines added, 135k lines removed; note 
that changes to lines show up in both counts).

On a side note, my commit count is relatively low... ie most commits with a 
larger number of changes. I remember working more than way before using git... 
perhaps with its explicit approach to saying which files to include it 
encourages that more (unless you use git commit -a), or perhaps for other 
reasons my habits have changed.

I don't get nearly as fancy as what Adam described recently with his rebase 
approach, but to his point I find my commits being much cleaner and better 
organized.

-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.

Reply via email to