Open Stack

For the reports on contributions to releases, we're counting individual
controbibutions (as gitdm guys do), and then we have a table (which
should have pretty much the same info that the gitdm table has), which
states that developer D works for company C for such and such period.
So, I guess we use basically the same methodology.

An Monty suggests, if a certain developer can be counted as working for
a certain company during a certain period, it really doesn't matter if
she/he is working subcontracted, or what.

I see two cases that could not be tracked with this schema:

- Developer D working for company B and C at the same time (maybe
because of subcontracting, or whatever). The only chance I see here is
to label each commit somehow, maybe with the "Contributed for:
<affiliation>" field suggested by Stefano.

- Developer D working for company C, which during a certain period is
subcontracting for company D. In this  case, both D and C could be
interested in appearing as "contributors", probably in different
classifications. If we come to direct affiliations, C would be the
contributor. If we come to "who is paying", it would be D. Probably
having both rankings would be important: company C would be interested
in others knowing that they have expertise in working in OpenStack,
while company D would be interested in showing their contributions. This
could be tracked with an extended table, including not only affiliation
(as we do now), but also subcontracting (for which company is really
working each developer, for each period).

Of course, both cases could happen at the same time, but I don't know if
that actually happens.

In addition, it is important to notice that we're also trying to track
closing tickets, messages, etc. which complicates things, since we would
need (in the case of tracking specific contributions) similar labels for
all of this.

Just my two (euro)cents,

	Jesus.

-- 
-- 
Bitergia: http://bitergia.com http://blog.bitergia.com

On Mon, 2013-06-17 at 20:50 +0000, Qing He wrote:
> [Qing] my  one cent:
> 
> -----Original Message-----
> From: Monty Taylor [mailto:mordred at inaugust.com] 
> Sent: Monday, June 17, 2013 1:39 PM
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [metrics] Code contribution by 3rd party consultant on behalf of a corporation
> 
> It depends on a little bit on where you want the stats to show up.
> 
> In gitdm, there is already a place you can put a date range on a
> person to attach them to a company. I'd start with just putting an
> entry into the gitdm files showing that, for instance, Contractor A
> worked for Company B for the Month of May.
> 
> If you think it's conceivable that a single contractor might be
> working in parallel for more than one company at the same time and
> that we might want to track that patch C was done for Company B but
> patch D was done for Company E, we might need to look in to something
> more complex - but honestly, that seems like a kindof unlikley
> situation, no?
> 
> [Qing] In one situation this could happen: Contractor A gets work from
> multiple companies and deals out tasks (e.g., offshore) and all the
> tasks dealt out would be checked in under contractor A when finished.
> 
> On 06/17/2013 04:33 PM, Chan, Winson C wrote:
> > Metrics team,
> > 
> >  
> > 
> > Is there a best practice for counting commits made by a 3^rd party 
> > consultants/contractors (with multiple affiliations) on behalf of 
> > another corporation?  I recently had a conversation with Stefano and 
> > he suggested adding a "Contributed for: <affiliation>" in the commit 
> > message.  Stefano recommended that I get the dialog started here...
> > 
> >  
> > 
> > Thanks.
> > 
> > Winson
[...]