Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 64.74.244.71 is neither permitted nor
 denied by domain of geir@pobox.com)
Message-ID: <4411B1CD.6040107@pobox.com>
Date: Fri, 10 Mar 2006 12:05:17 -0500
From: Geir Magnusson Jr <geir@pobox.com>
Reply-To: geir@pobox.com
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: ITC's Contribution
References: <000401c643ad$3aa1c000$66204c40@irisnotebook>
 <4411AC9E.9020006@gmail.com>
In-Reply-To: <4411AC9E.9020006@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


Tim Ellison wrote:
> Iris Gasta�aga wrote:
>> Hi Tim, 
>>   We have read the contribution policy and we are ready to sign 
>> the following documents -we've questions on some of them, so please 
>> advice-:
> 
> I'll try to help, but with the standard disclaimer that IANAL, so you
> need to be comfortable with the terms and conditions and grants that you
> are signing no matter what I tell you!
> 
>> - SG & CCLA (http://www.apache.org/licenses/cla-corporate.txt ): 
>>     Signed by the CEO of ITC. The CCLA should list the team leaders 
>>     as authorized contributors 
> 
> Ok, thanks.  The list of designated employees on this form is an
> internal matter for you (essentially listing people who can contribute
> assets on behalf of the corporation).

Or you can just ignore that.  For the purposes of this contribution, the 
important critical part is Schedule B of the document.  Listing people 
in Schedule A is good too, but basically is there to protect those 
individuals by allowing them to prove that the corporation has given 
permission for them to participate in any apache project.

> 
>> - Bulk Contribution Checklist
>>   (http://incubator.apache.org/harmony/bulk_contribution_checklist.txt):
>>
>>     One for each package, signed by the team leader, and specifying 
>>     the list of developers (authors) 
> 
> You really only need one checklist per bulk contribution (which may be a
> set of packages); but no harm, just more paperwork!

Which is harm :)

Please only send one document that covers the single contribution, 
unless there is some problem which prevents this and requires multiple, 
but I can't see a situation where that is the case.

> 
>> - ICLA (http://www.apache.org/licenses/icla.txt): 
>>     One for each person designated as authorized contributor (or 
>>     should it be one for each author?) 
> 
> The Software Grant and checklist cover the bulk contribution, so ICLA's
> should be completed for people who will be making an ongoing
> contribution to the code.  The ICLA works for contributors, the
> foundation, and code consumers to define the terms under which
> contributions are made to the project.

Right.

> 
>> - ACQ (http://incubator.apache.org/harmony/auth_cont_quest.txt ): 
>>     One for each person designated as authorized contributor (or 
>>     should it be one for each author?) 
> 
> The bulk contribution checklist ensures that incoming code, created
> outside the day-to-day development of the project, has a traceable and
> acceptable IP provenance.  If you can provide an ACQ for each of the
> original authors(*) and each ongoing contributor(+) that would be ideal.
> 
> (*)otherwise see the bulk contribution checklist for details
> (+)otherwise they are probably out of luck, see the ACQ for details

Yes please provide one for every author of the code contribution.

> 
>> Is this ok? where should we send this documents?
> 
> To date these forms have been sent directly to Geir.  I won't put his
> fax number out on the list  -- I'll let him send it to you directly.

+1 203 665 6400

geir

> 
> 
> Regards
> Tim
> 
>> -----Mensaje original-----
>> De: Tim Ellison [mailto:t.p.ellison@gmail.com] 
>> Enviado el: Lunes, 06 de Marzo de 2006 01:54 p.m.
>> Para: harmony-dev@incubator.apache.org
>> Asunto: Re: ITC's Contribution
>>
>> Iris Gasta�aga wrote:
>>> Hi all,
>>>  
>>>     On behalf of ITC (Cordoba Institute of Technology)from Argentina.I
>>> want to offer a code contribution of the 
>>> following packages:
>>>  
>>> - java.math    (led by Daniel Fridlender)
>>> - java.crypto  (led by Miguel Montes)
>>> - java.rmi     (led by Daniel G�ndara)
>>>  
>>> Last year the ITC decided to start a "clean-room" java package
>>> development 
>>> project; now we are proud to make this donation and we hope it be
>>> accepted as a valid 
>>> contribution (which we believe it is).
>> That is fantastic Iris! thanks.
>>
>>> Having said this, I do have a few questions:
>>>  
>>> a) Next Steps?
>>>   which are the next steps? we have read the contribution policy and
>> we
>>> are 
>>> ok with that; we'll send aditional questions regarding documents to be
>>> signed on a separated email.
>> We can help with a quick overview of the contribution requirements for
>> acceptance -- that would be the logical next steps.  Looks like the
>> other questions have been pulled out into separate threads, so let's
>> deal with them there.
>>
>> Regards,
>> Tim
>>
>>> b) Harmony 1.5?
>>> we have developed J2SE 1.5 compliant/dependant packages -following the
>>> specs 
>>> of harmony project-; but we see that currently Harmony is not 1.5 but
>>> 1.4. 
>>> Is there an schedule or plan to get Harmony J2SE 1.5?
>>>
>>> c) Some still missing components...
>>> we have checked some pre-conditions before making this announcement
>> and
>>> we 
>>> found that there are some components we need (i.e.: concurrent) which
>>> are 
>>> not on Harmony yet.  Is someone working on those missing components?
>>>  
>>> we'll be waiting for comments,
>>>  
>>> Sincerely,
>>>  
>>> Ing. Iris Gasta�aga
>>> --------------------------------------------------
>>> Executive Director
>>> Instituto Tecnol�gico C�rdoba
>>> C�rdoba Business Tower, Piso 15
>>> Tel: +54 (351) 5710022 / 23
>>> www.fitc.unc.edu.ar
>>> ---------------------------------------------------
>>> PS: we will send mails with specific package information.
>>> PS1: we do know that java.math and java.crypto have already been
>>> donated, 
>>> but we do believe our code is a valid donation.
>>> PS2: for each package we have developed a set of test cases (public
>> api)
>>> that we are willing to donate too.
>>>  
>>>  
>>>  
>>>  
>>>
>