incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Deboy" <sde...@comotivsystems.com>
Subject RE: FW: (qpid) Diversity
Date Thu, 06 Mar 2008 19:03:00 GMT
For the qpid folks who don't want to divulge their employer: are they
working on the project as part of their employment?  If so, it would
appear we need a CCLA, correct?

If we don't know the committer's employer (and they're working on the
project as an employee), we can't determine if a CCLA is on file.

>From http://www.apache.org/licenses/

---
For a corporation that has assigned employees to work on an Apache
project, a Corporate CLA (CCLA) is available for contributing
intellectual property via the corporation, that may have been assigned
as part of an employment agreement. Note that a Corporate CLA does not
remove the need for every developer to sign their own CLA as an
individual, to cover any of their contributions which are not owned by
the corporation signing the CCLA.
----


Scott Deboy


-----Original Message-----
From: Rajith Attapattu [mailto:rajith77@gmail.com] 
Sent: Thursday, March 06, 2008 10:48 AM
To: general@incubator.apache.org
Subject: Re: FW: (qpid) Diversity

On Thu, Mar 6, 2008 at 8:23 AM, Martin Ritchie <ritchiem@apache.org>
wrote:

> On 06/03/2008, Noel J. Bergman <noel@devtech.com> wrote:
> > Daniel Kulp write:
> >  > a quick svn log on their SVN repo for all commits since Jan 1
> [suggests
> >  that]
> >
> > > all but 4 commits since Jan 1 can easily be contributed to RedHat
> >  employees.
> >
> >
> > > I think the above should provide enough information about the
health
> and
> >  > diversity of the community that actually working on the code.
> >
> >
> > What is the Qpid community's response to these findings?
> >
> >
> >         --- Noel
>

I believe if a committer has signed the required legal documents then
thats
all what matters.
If they are uncomfortable disclosing their employer then perhaps we
should
respect that.
What is important is that these folks are contributing to the project in
a
legal manner.
The last thing we want is to discourage people from contributing.

As martin has pointed out, looking at the last 6 months and just the
trunk
is not a fair evaluation of diversity.
We should also not forget the significant contributions made by the
following folks in the last year or two.
Off the top of my head.

Colin Crist - Hermes JMS integration
Kevin Smith - SSL patch for the java broker.
Steve Vinoski - Maven build system
Tomas Restrepo - .NET client.
There was also a few individuals who made patches for the python client
to
get it interoperating with other open source implementations.

I am very optimistic that our community will continue to grow with more
contributions as we increase our visibility and efforts to integrate
with
other projects like Synapse, Axis2, Tuscany, CXF etc..

Regards,

Rajith Attapattu
Red Hat
blog: http://rajith.2rlabs.com/


>
> Ok I have a few comments in response to the findings:
>
> - Firstly not all work is done on trunk so purely looking at trunk is
> not a good metric
>
> - Looking at the last two months especially as that includes the start
> of the year which is typically a quite period also will show poor
> commit numbers.
>
> - We are preparing for an M2.1 release so a lot of effort is being
> expended on that branch.
>
> My take would be to look at the last 6 months, which admittedly
> includes a number of holiday periods so the count of commits may be a
> little low. Since 2007-09 for the commits on the qpid repository
> shows:
>
> aconway 272
> aidan 54
> arnaudsimon 230
> astitcher 16
> cctrieloff 45
> gsim 201
> kpvdr 11
> nsantos 8
> rajith 169
> rgodfrey 99
> rgreig 98
> rhs 151
> ritchiem 593
> rupertlssmith 468
>
> 1103    RedHat
> 1312    Non-Aligned
>
> So Redhat have less than half the commits to Qpid so I don't think
> this is something we should worry about. Keeping an eye on for sure,
> but over analysing the alignment of those people that don't want to or
> are not allowed to say who they work for is not something that Apache
> requires nor would it be beneficial. Saying that we are not diverse
> because a lot of work on trunk has been done by a small set of people
> over a two month period is not helpful to the discussion.
>
> It is also worth noting that volume of commits does not in anyway
> correspond to the quantity of code changed and even looking at lines
> changes cannot say anything for the quality. I think the fact that we
> have an active project that has matured to the point that where we
> feel as though we can self regulate in the Apache Way speaks far more
> to the community of the project than identifying who is paying the
> bills.
>
> The whole project worked very hard to pull together two servers and
> five client libraries for the M2 release all talking AMQP 0-8. We are
> again working as a community to provide a M2.1 release that will inter
> operate at AMQP 0-9 with other AMQP products outside the Apache world.
> I for one am looking forward to our future releases where we can again
> move the entire project on to the wholly different AMQP 0-10.
>
> --
> Martin Ritchie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message