get he ICLA in sooner than later so we can do a group request for
accounts...
geir
On Jan 18, 2007, at 12:42 PM, Bill Venners wrote:
Hi Geir,
Great advice. Thanks. This is exciting. I'll get this in as soon as
I can, and then I'll fax the Corp CLA, and ICLA. I've got them both
signed here but I was waiting to fax them until after I submit the
ServiceUI code.
Bill
On Jan 18, 2007, at 1:29 AM, Geir Magnusson Jr. wrote:
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 :
<description> 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
