Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=ElFHOKQB1WokvJQNpugY/tGcludzd9kUvzzfgn3vwosP9IzA2VUvxEXG5YjB/m0TqfQL6AvT45oD20COCZF1rCsstk79sN+18JAJreKw99zBdHVsXGsEE12f/Ha3t7rG3OLIA7kh9AlkdvCgXC7XV9+PUpucrXnG7lkcUyLed6M=;
Message-ID: <533036.34282.qm@web54410.mail.re2.yahoo.com>
References: <1284425758.5045.58.camel@avon.watzmann.net>
  <AANLkTimEiofzbhLFDeWX99K_TBN9Jid=qoa7-T1RseH=@mail.gmail.com>
  <20100914014309.GA17294@daniel3.local>
  <415361.43155.qm@web54402.mail.re2.yahoo.com>
  <AANLkTi=9qx1erBx64Ows+iQ0AAp=m1k0rGLmpQo+ftkW@mail.gmail.com>
  <20100914022228.GB17442@daniel3.local>
 <1284593625.10706.15.camel@avon.watzmann.net>
 <319754.59418.qm@web54409.mail.re2.yahoo.com>
 <DB3CA912-8289-4D88-BC5D-0635BF3E3398@oracle.com>
Date: Wed, 15 Sep 2010 17:09:58 -0700 (PDT)
From: Joe Schaefer <joe_schaefer@yahoo.com>
Subject: Re: Accepting patches in a podling
To: general@incubator.apache.org
In-Reply-To: <DB3CA912-8289-4D88-BC5D-0635BF3E3398@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

----- Original Message ----

> From: Craig L Russell <craig.russell@oracle.com>
> To: general@incubator.apache.org
> Sent: Wed, September 15, 2010 8:05:01 PM
> Subject: Re: Accepting patches in a podling
> 
> 
> On Sep 15, 2010, at 4:41 PM, Joe Schaefer wrote:
> 
> > ----- Original  Message ----
> > 
> >> From: David Lutterkort <lutter@redhat.com>
> >> To: general@incubator.apache.org
> >>  Sent: Wed, September 15, 2010 7:33:45 PM
> >> Subject: Re: Accepting  patches in a podling
> >> 
> >> On Tue, 2010-09-14 at 04:22 +0200,  Daniel Shahaf wrote:
> >>> FWIW, what  Subversion  uses:
> >>> 
> >>> 
> >>  
>http://subversion.apache.org/docs/community-guide/community-guide.html#patches
> >>> 
> >>  
>http://subversion.apache.org/docs/community-guide/community-guide.html#patch-manager
>
> >> 
> >>> ;
> >>> Briefly, all patches go to dev@, and only  the unlucky patches  that
> >>> were neither applied nor rejected  get stashed in the issue  tracker
> >>> to avoid being dropped on  the floor.
> >> 
> >> This seems a very  workable approach -  going through Jira for everything
> >> is too much work on the  part  of the contributer. I'll use that as the
> >> submission policy for   Deltacloud from now on:
> >> 
> >>      * Patch  submittes must have  a CLA on file
> > 
> > Well IMO this should  only be a requirement for "substantial" changes.
> > Minor bugfixes and such  aren't even copyrightable, so just take them
> > if they're posted to the  list without disclaimers.  If you use reasonable
> > judgement about  minor changes, you don't need to burden an occasional
> > contributor with  any paperwork- the license ensures your actions are
> >  defensible.
> 

> I'm mystified about what license you are talking about.

The Apache License.

> This  particular item proposes that patches posted to dev@ are ok if
> submitted by  someone who has a CLA on file. You say you don't need
> to burden an occasional  contributor with any paperwork.
> 
> So what license are you talking about?  The CLA that the contributor didn't 
>file?

Right, I'm saying that not every patch submission requires a iCLA on file.
If it's a minor patch and noone objects to its inclusion, just include it.


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