On Fri, 12 Apr 2002, Ceki [iso-8859-1] G�lc� wrote:
>
> The results of a recent vote show that the log4j community has strong interest
> in the donation. Is there a document that I can present to the donator for
> signature?
> I assume this document is NOT the Contributor License Agreement because
> that document applies to individuals, not corporations. Correct? To whom do I
> (or the donator) send the signed document? Thanks in advance, Ceki
>
> At 23:58 11.04.2002 +0200, [EMAIL PROTECTED] wrote:
>
> >There are several reasons why this needs a contributors license (assuming
> >people want the code)
...cut...
I think the refence got cut out :-) you want:
cvs.apache.org:/home/cvs/foundation
software-grant.txt/pdf
Some hints on filling it out:
-> Get the committers all synced up and in agreement (seems
to be the case) that this is a cool thing they want.
-> Make sure your PMC is fine with it.
(if the committers are fine - usually not an issue! PMC
tend to worry about licenses and boring things.)
-> Get the document to the licensor early or in parallel
so they know what is coming. You may need some extensive
communication to explain things.
-> Notice that most bulk sourced code contains some text like
"this code started its live as a contribution of Foo Bar.
etc..". just below the license. You may want to suggest/negotiate
such a text prior to the grant work.
Once you are ready - put something like a short description of the
software and something like an md5 or an ls -lR in exhibit A; get it
signed and have the licensor send it to the secretary; Address, Fax, email
and phone are all on the web site and in members. We will want a paper
version at some point.
If the licensor wants to be very careful about what is in the exhibit A -
they of course you can make it more elaborate; add a floppy or CD with a
signature, etc. The whole point is that it should be reasonably easy to
establish later what we got and at what point. Use as many pages as you
need :-).
Once all is done (and not a moment earlier) - import into private CVS with
a clear import message referencing the above. Obviously this should
correspond with exhibit A. If the secretary got a zip file or something on
a physical media - then he can move that onto cvs.apache.org for the
committers to take further.
Now before you allow any committer access or to download things - you will
need to put in the right license info; i.e. a file LICENSE in the root -
and the commented out blocks in each and every source file. (We do not as
of yet have a referencable license - this is worked on) and add any
attribution clauses or readme's.
Once the license is in - you can have the committers have access to it -
the group will then have to work out how public things should be -
sometimes it makes sense to let a few commiters restructure and cleanse
before bestowing it on the world.
Feel free to contact me if you need a hand with things - and know that
we/secretariat can always help with logistics, fedex shipping, phone
costs, faxes and what not. My experience is that there is a fair amounth
needed usually.
Dw.
License Agreement
This License Agreement is entered into as of the ___ day of
____________, 2001 by ___________________________ ("Licensor"), in
favor of The Apache Software Foundation, a Delaware nonstock
membership corporation (the "Foundation").
WHEREAS, Licensor owns or has sufficient rights to contribute the
software source code and other related intellectual property as
itemized on Exhibit A ("Software") under the terms of this agreement
to the Foundation for use within Foundation software development
projects ("Projects").
NOW, THEREFORE, FOR GOOD AND VALUABLE CONSIDERATION, the receipt
and legal sufficiency of which are hereby acknowledged, the parties
hereto, intending to be legally bound, agree as follows:
1. Licensor hereby grants to the Foundation a non-exclusive,
irrevocable, perpetual, worldwide, no-charge, royalty-free,
transferable, sublicensable copyright license to use, execute, prepare
derivative works of, and distribute the Software and such derivative
works.
2. Licensor represents that Licensor is legally entitled to grant the
above license. Licensor agrees to notify the Foundation of any facts
or circumstances of which Licensor becomes aware and which makes or
would make Licensor's representations in this License Agreement
inaccurate in any respect.
3. This Software is provided AS-IS, without warranty of any kind
(either express or implied) including, without limitation, any implied
warranty of merchantibility and fitness for a particular purpose and
any warranty of non-infringement.
IN WITNESS WHEREOF, Licensor has executed this License Agreement
as of the date first written above.
LICENSOR:
By: ________________________________
Print Name: _________________________
Representing: _______________________
Title: ______________________________
Exhibit A
List of software and other intellectual property covered by this agreement:
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
