Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 55758 invoked from network); 3 Feb 2009 10:12:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Feb 2009 10:12:06 -0000 Received: (qmail 61123 invoked by uid 500); 3 Feb 2009 10:12:05 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 61085 invoked by uid 500); 3 Feb 2009 10:12:05 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 61074 invoked by uid 99); 3 Feb 2009 10:12:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 02:12:05 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [80.68.94.123] (HELO tumbolia.org) (80.68.94.123) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 10:11:56 +0000 Received: from nslater by tumbolia.org with local (Exim 4.69) (envelope-from ) id 1LUIFj-0000ke-CN for dev@couchdb.apache.org; Tue, 03 Feb 2009 10:11:35 +0000 Date: Tue, 3 Feb 2009 10:11:35 +0000 From: Noah Slater To: dev@couchdb.apache.org Subject: Re: Fwd: Code contribution to ASF - What are the minimum actions Message-ID: <20090203101135.GF2533@tumbolia.org> Mail-Followup-To: dev@couchdb.apache.org References: <0AB418F8-C6B1-429D-A73E-BE48C09F8E32@SUN.com> <4981553D.9000509@rowe-clan.net>

MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Noah: Awesome User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Checked: Checked by ClamAV on apache.org Hey Chris, I'm a bit confused. We went through all of this for our first release, and a lot of it only applies to Incubator first releases. As far as I know, the state of the current code-base is tip-top, and I will take care of any remaining problems during my standard release procedure. On Mon, Feb 02, 2009 at 03:38:36PM -0800, Chris Anderson wrote: > This is a very helpful document. If Apache were an office, I think it > would be hanging on the wall. This should make a good checklist for us > as we prepare the 0.9 release. > > > ---------- Forwarded message ---------- > From: Craig L Russell > Date: Mon, Feb 2, 2009 at 3:24 PM > Subject: Re: Code contribution to ASF - What are the minimum actions > To: legal-discuss@apache.org > > > Not unlike much of the [DRAFT] incubator documentation, some of the > information might appear to be self-contradictory; but reading it all > together it makes sense to me: > > ... > Once a JIRA has been created, the source should be cleaned up. > > > • Ensure source files use the standard Apache boilerplates. > This may mean replacing existing license headers. The tools > inhttps://svn.apache.org/repos/private/committers/tools and > https://svn.apache.org/repos/private/committers/relicense may be > useful. > • Ensure that NOTICE and LICENSE documents are present and correct > • Add any required notices. Consider moving copyright > attributions from source documents to the NOTICE. Read Apache policy > on headers . > • Audit the source for any potential licensing issues. Any > which are found should either resolved immediately (when required) or > noted in the status document for later. > > It is recommended that the initial clean up be is started before the > code is committed. It MUST be completed before any releases are cut. > > Clean Up Best Practice > It is recommended that version control is used to create a public > record of the process. This will assist anyone auditing the code > provenance (now or in the future) to easily perform due diligence > without contacting the people who performed the clean up. The clean up > process should therefore clearly document (using version control) the > evolution of the IP licensing. > > Particular care needs to be taken with commit messages during clean > up. The intended audience needs to include lawyers and code auditors. > Members of the public need to be able to follow and understand the > process from these messages alone. > > It is therefore recommended that the initial source is (after being > expanded from the archive) checked in as is into a special directory > (${project}/trunk/import is suggested). The original packaging, > copyright statements and license notices should be preserved. A > standard Apache LICENSE and appropriate NOTICE should be added at the > top for the copyright for the collective work (see policy ). Take > particular care with this commit message. As with any patch that > contains code which is not the original work of the committer, the > JIRA url (for the artifact imported) needs to be included together > with notes about the original copyright owner and any associated > paperwork. The fact that this is a exact import including original > headers should be noted to stop any queries about these foreign > headers. > > The cleanup should then proceed in a number of commits. If the source > provenance is complex, break the process up into a number of logical > steps committing each in turn with a good message. > > In particular, take care when relocating copyright statements and > license notices into the NOTICE in the root directory: consider moving > each copyright owner individually so that it is easier to audit. (See > policy .) > > Once a section of code has been cleaned up (and repackaged, if > necessary) normal development can begin. > > > > The way I read the above, it's recommended to do the actual cleanup in > the incubator svn. The initial cleanup is be started [sic] outside the > incubator, but checking on licensing issues, finding all contributors, > looking for copyright notices. > > But in the end, this is all just guideline. Mentors have the > responsibility to guide their podlings in The Way. > > more below... > > On Jan 29, 2009, at 12:01 AM, Niclas Hedhman wrote: > > > On Thu, Jan 29, 2009 at 8:05 AM, William A. Rowe, Jr. > > wrote: > >> > >> Craig L Russell wrote: > >>> > >>> This process provides an audit trail that answers the question "who > >>> changed the license and were they authorized to do so?" > >> > >> If the owner of the code or an agent thereof commits the code > >> (or submits it for svn import or migration) already correctly > >> branded, there is no problem. We don't need a trail, we have > >> a contribution agreement. > > > > Exactly. Craig, I don't see why it is ASF's problem to track IBM's > > internal affairs prior to Incubation. We should not go looking for > > problems (e.g. patents), and if we receive a paper from IBM, saying > > "We contribute this, already under Apache license...", why would we > > need to know what has happened prior to that? > > > >> The current incubator guidelines suggest that code *not* be > >> changed before contribution but be changed in svn. See > >> http://incubator.apache.org/guides/mentor.html#initial-ip-clearance > >> for details on the process. > > > > Uh.... It seems we read differently, "It is recommended that the > > initial clean up be is started before the code is committed." and by > > virtue of above, why not simply have that in place before it leaves > > the hands of a single contributor? Why make it harder than needed? > > The original question from Steve Poole was: > > > > Here is my list of whats required at minimum > > > > 1 - check that everything contained is intended for contribution > > 2 - remove any artifacts and source that are not original works by IBM > > > > I'm sure it can't be as simple as that - can someone help me by pointing out whats missing? > > And your reply was > > > > 3. Provide the contribution to the project under a Apache License. > > (Makes the incubation process smoother). > > I continue to maintain that it is as simple as Steve originally said. > Cleanup can/should/and *will* occur in the incubator svn prior to > release. > > Craig > > > > > > Cheers > > Niclas > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org > > For additional commands, e-mail: legal-discuss-help@apache.org > > > > Craig L Russell > Architect, Sun Java Enterprise System http://db.apache.org/jdo > 408 276-5638 mailto:Craig.Russell@sun.com > P.S. A good JDO? O, Gasp! > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org > For additional commands, e-mail: legal-discuss-help@apache.org > > > > -- Noah Slater, http://tumbolia.org/nslater