This is the mail archive of the
ecos-patches@sourceware.org
mailing list for the eCos project.
Re: atHTTPD new patch
- From: "Anthony Tonizzo" <atonizzo at gmail dot com>
- To: ecos-patches at ecos dot sourceware dot org
- Date: Tue, 18 Dec 2007 07:19:18 -0800
- Subject: Re: atHTTPD new patch
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=Eh1emxo6X9w1D3OE1UcJVdT+6V1RGEfzLbb6XtjMzDA=; b=jQhjYtZa3LAX8lcCD4Vr4pLiiJ6nQiy12SFjhmgBI0AcfL28dv308XnA3O1Vj6uAa7nIIXOlqHByXE1Kfgc0bXJozL6H0cknRY35GbMVo8CmDtdLORTIonmCKU73dlGAYBKV0O2zTaIcnJdLq8VHGTD91JTGqSqzR+gvTfn+V8A=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=vDPC/vGd+QyWX5FBvg1Sp9b4hbTK6Nqhpkdr5+2acLmzgrunrDt/jIbPN9ynRNi1BehhcrPBqlrld6EBXOYWaSgWxcpp0WRakkFG0wT4pw1S7uOSFnd2WqHctAq1kAwOEatyLCtl3xjeplIPACk4dS+p7BdfqgpdMnxHR5QpJJY=
Andrew:
Me moved the development to ecosforge because it would
be much simpler to test new code as it is developed by different
parties. Currently only Oyvind and myself can check new code
in, but you will still receive new patches for the eCos tree from
me.
Just to clarify the issue of copyright assignments. Is there
any lithmus test to determine which contributions need an
assignment and which do not?
Somewhere I read something like "10 original lines of code"
make up the breakwater. Is this the accepted standard or do
you reserve the right to change this on a per-case basis?
> If one or more of the people contributing to the current patch cannot
> get a copyright assignment you then have a problem. Effectively you
> need to throw their part of the patch out and re-implement it with
> code you can get an assignment for.
Understood.
Sorry if I sound like a sticlker for details, but I want to make sure
that even after moving the development to ecosforge, there will be
no problems in the future to submit patches to eCos.
> Secondly, please keep tight control and records for everything you add
> to your ecosforge tree. When you want to contribute a patch we have
> the same copyright issues.
> You need to be able to convince the eCos
> maintainers that all the patch is covered by appropriate copyright
> assignments. The more open and visible your process is the easier you
> will find it to convince us.
The only way to record what is added is through the changelog. And
because we (as opposed to the eCos maintainers) modify the changelog,
it means that it still boils down to a matter fo trusting the contributors to
eCos, right? Or are you suggesting that we save all e-mail and individual
patches that were received from all contributors?
If we need to ask for a copyright assignment, do we ask the submitter
to send it to eCosCentric?
Thanks
Tony