Return-Path: Delivered-To: apmail-incubator-river-dev-archive@locus.apache.org Received: (qmail 95918 invoked from network); 18 Jan 2007 09:30:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jan 2007 09:30:02 -0000 Received: (qmail 27048 invoked by uid 500); 18 Jan 2007 09:29:59 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 26982 invoked by uid 500); 18 Jan 2007 09:29:59 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 26950 invoked by uid 99); 18 Jan 2007 09:29:59 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 01:29:59 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: 216.86.168.178 is neither permitted nor denied by domain of geir@pobox.com) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 01:29:48 -0800 Received: from [192.168.0.127] (unknown [200.82.100.154]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 804825197F for ; Thu, 18 Jan 2007 04:29:26 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <7E41A2F4-FD8F-4614-A57D-760CC00845D2@artima.com> References: <71A27A98-689D-4A83-A7A8-73040DCBBBB7@pobox.com> <459AC85E.7010400@Sun.COM> <20F6A6B9-763F-47D7-9649-125CCAFA0829@SUN.com> <97DBB557-EEA3-458B-AEB0-8A2ABDD557AC@pobox.com> <969460FD-8A6A-49F2-AB66-0D884719E16F@pobox.com> <4F815342-36F1-44B9-BA87-8A2442D9CB1C@pobox.com> <208C94BE-79D9-4B93-901E-3AD7127E8A1F@artima.com> <3C76218A-F4F6-473E-A9D1-81D4A392CD6C@artima.com> <7E41A2F4-FD8F-4614-A57D-760CC00845D2@artima.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5B20FDD4-DF55-4AB1-AF04-28A3725FFBDA@pobox.com> Content-Transfer-Encoding: 7bit From: "Geir Magnusson Jr." Subject: Re: new site added to SVN and published Date: Thu, 18 Jan 2007 06:29:25 -0300 To: river-dev@incubator.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Sorry Bill... traveling this week and behind... You don't *have* to do it in that order, but I've discovered that having that JIRA key makes it clearer in the records, but it can be in either order. So - 1) Add the license header to each file as described here : http://www.apache.org/legal/src-headers.html In particular, remove any (c) Artima if that happens to be in the code, or any of your own license headers or statements of ownership that may be in each file. 2) Put a copy of the Apache License (http://www.apache.org/licenses/ LICENSE-2.0) into a file called LICENSE in the root of the distribution 3) If there are any pieces of software in the contribution that weren't created by you (came from elsewhere) and had any notice requirements in the license (such as a BSD notice requirement) then put those in a NOTICE file in the root of the distro. 4) If there were any (c) Artima, and you want that to persist somewhere, put a file COPYRIGHT in the root of the tree and put something like The following copyright notice(s) were affixed to portions of the code with which this file is now or was at one time distributed and are placed here unaltered. (C) Copyright XXXX Artima 5) Be sure that there is no code (c) anyone else - for example, one popular mistake is to submit schemas or such that may be (c) sun. 6) Bundle the tree into a tarball, create a new JIRA, then attach tarball to JIRA. 7) in the CCLA, where it has you list the contributions, put : as submitted to the ASF via JIRA as RIVER-XXX geir On Jan 18, 2007, at 3:05 AM, Bill Venners wrote: > Hello, > > Can someone point me to the JIRA instance where I'm supposed to > submit ServiceUI? I haven't heard back from anyone on how to do > this, or how to package it. According to Geir, I should first > submit the code then fax in the signed agreement with the JIRA ID > of the submission on it. > > Thanks. > > Bill > > On Jan 15, 2007, at 12:07 PM, Bill Venners wrote: > >> Hi Geir, >> >> On Jan 3, 2007, at 1:44 PM, Geir Magnusson Jr. wrote: >> >>> >>> yep - through the CCLA, Artima can license a copy to the ASF. >>> >> I've finally prepped these docs, but I'm afraid I need a bit of >> hand-holding for submitting the code. How should I package >> ServiceUI, and where do I submit it via JIRA? What should be >> included in the package? Once I get it submitted, I can stick the >> JIRA ID on the CCLA itself and fax or mail it (whichever is >> preferred). >> >> Thanks. >> >> Bill >> >>>> >>>>> 1) package and contribute via a JIRA >>>>> >>>>> 2) submit an CCLA to the ASF Scty where the contribution is >>>>> noted by JIRA ID (makes it much easier to figure out what is >>>>> what later...) >>>>> >>>>> 3) when the paperwork is done, project votes to accept the >>>>> contribution >>>>> >>>>> The last step is a way to clearly exercise active oversight on >>>>> the codebase - it means that people other than the committer >>>>> that eventually puts the code in SVN are paying attention to >>>>> what is entering SVN. >>>>> >>>> Thanks. >>>> >>>> Bill >>>> >>>> >>>> >>>> >>>>> geir >>>>> >>>>> >>>>> On Jan 3, 2007, at 11:05 AM, Bill Venners wrote: >>>>> >>>>>> Hi Geir, >>>>>> >>>>>> What's will be the process for contributing ServiceUI? I am >>>>>> guessing I need to sign a Software Grant and CLA on behalf of >>>>>> Artima, and then perhaps a CLA for myself as an individual too? >>>>>> >>>>>> Bill >>>>>> ---- >>>>>> Bill Venners >>>>>> President >>>>>> Artima, Inc. >>>>>> http://www.artima.com >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> Bill >>>> ---- >>>> Bill Venners >>>> President >>>> Artima, Inc. >>>> http://www.artima.com >>>> >>>> >>>> >>> >>> >> >> >> Bill >> ---- >> Bill Venners >> President >> Artima, Inc. >> http://www.artima.com >> >> >> >> >