incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gerhard Petracek <>
Subject Re: DeltaSpike IP clarifications
Date Tue, 17 Jan 2012 17:45:54 GMT
hi matt,

imo we have to care about it in case of other external contributions we are
going to get quite soon.

however, in case of seam3 i don't see any issue at all.
#1 redhat has a ccla on file
#2 they contacted us [1] to join forces (and they found out that the asf is
also a great place for them to do so) and they announced it as well [2]
#3 their employees who wrote the original source-code do the initial import
after we agreed on it from a technical point of view
#4 basically there isn't a license issue at all, because the source-code is
AL v2 licensed already (@our higher quality standard: see #1-#3)

if we think that #1-#4 isn't enough, imo it's faster to ask redhat to write
a formal letter that they grant us access explicitly.

for sure that's just my personal opinion.



2012/1/16 Matt Benson <>

> It may also be pertinent to note that the codebases here in question
> are also ALv2 licensed.
> Matt
> On Mon, Jan 16, 2012 at 1:49 PM, Matt Benson <> wrote:
> > Hi, all--per [1], "Generally, the mentors of a new project will need
> > to consult with or the Apache legal team
> > about the particular circumstances."  So, here I am.
> >
> > The situation can be read in detail at [2], but in short is this:
> > DeltaSpike is intended to amalgamate "best of" add-on solutions from
> > the Java EE community with regard to the "Contexts and Dependency
> > Injection for the Java EE platform" (CDI) specification.  Thus its
> > sources may incorporate code originating from numerous sources, but
> > due to a number of reasons including e.g. anticipated feature overlap,
> > it does not seem appropriate to include whole codebases under software
> > grants.  The specific question at the moment regards code to which Red
> > Hat holds the copyright.  The ASF has a filed CCLA from Red Hat, but I
> > have been taking the position that we still need some form of
> > assurance that code relating to CDI (primarily embodied in the Solder
> > and Seam) projects is *specifically* approved for contribution to
> > DeltaSpike.  I'll present the basic question in multiple-choice form
> > (with options shown in order of difficulty):
> >
> > What do we need to show provenance?
> >  a.  Nothing.  Stop being so damned paranoid.  The CCLA is enough.
> >  b.  DeltaSpike's Red Hat-employed committers' assurance that their
> > employer is "on board."
> >  c.  A signed statement from Red Hat to the effect that their
> > employees are authorized to contribute CDI-related code.
> >  d.  A software grant for any codebase, even if we only intend to
> > cherry-pick from it.
> >  e.  Jim Whitehurst's eternal soul.
> >  f.  Something else, namely _____.
> >
> > Thanks,
> > Matt on behalf of DeltaSpike
> >
> > [1]
> > [2]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message