incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: [VOTE] release deltacloud 0.3.0
Date Sat, 09 Apr 2011 02:16:55 GMT
On Fri, Apr 08, 2011 at 05:03:45PM -0700, David Lutterkort wrote:
> For my education: is there a good checklist for what needs to be in a
> release ? 

Many (most?) projects roll their own release checklists.  Over at the Lucy
podling, we've chosen to create three separate wiki pages: -- collective tasks -- tasks for the RM specifically -- PMC vetting aid

We broke out ReleasePrep for tasks which are the collective responsibility of
the community because we don't want the RM to get stuck cleaning up
everybody's accumulated mess -- like you're doing now.

> It seems that the requirements are fairly well distributed across the Apache
> website.

That's true.  The most comprehensive page is the most sprawling and the least

I suggest starting with that page and distilling it down into your own release

Here are some other relevant pages:

> > Many of the source files contain "Copyright (C) 2009-2011  Red Hat,
> > Inc." or other copyright attributions.
> > 
> > AFAIK, you need to ask the owner for permission to remove them, or at
> > least to move them to the NOTICE file.
> > 
> > There are some other files with non AL headers; these may also need to
> > be attributed in the NOTICE file.
> I find this extremely confusing - why remove the copyright attribution ?
> Isn't it clearer if each file states who holds copyright in it ?

Once other people start contributing and a file becomes a collective work,
having a notice which only refers to one of many copyright holders becomes
*more* confusing.  :)

> In any event, I assume I can move the copyright notices for the files
> that were part of the initial grant, and that come from contributors;

You might consider encouraging all subsequent contributors to remove their
copyright notices as well. 

Here's a thread on the Lucene developer's list from last year where we discuss
how to deal with a request from a book publisher for credit:

And here's a recent thread on the Perl 5 porters list (outside Apache
obviously) where they wrestle with the same issues:

> there's also a handful of files that we use under the MIT license - can
> I leave the copyright attribution in them ?

Indeed, you must *not* remove those.

> Also, it seems to me that the boilerplate text of the NOTICE file is
> incorrect since it states 'Copyright YYYY The Apache Software
> Foundation' but the contributor license agreement does not actually
> assign copyright to the ASF (which would be impossible in some
> jurisdictions anyway) - what exactly does the NOTICE file accomplish ?

The ASF owns the collective work.

    Apache products are composed of lots of pieces of code across numerous
    source files, licensed to the ASF by various authors who maintain
    ownership of their contributions. When a PMC goes through the process of
    selecting, coordinating, and arranging all these various contributions
    into a single product, the collective work is also protected by copyright
    law and is owned by the ASF -- even though each individual piece of code
    is still owned by the contributor.


Marvin Humphrey

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message