Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: local policy)
Subject: RE: Corporate Contributions
From: Santiago Gala <sgala@hisitech.com>
To: legal-discuss@apache.org
In-Reply-To: <32D5845A745BFB429CBDBADA57CD41AF0E752617@ussjex01.amer.bea.com>
References: <32D5845A745BFB429CBDBADA57CD41AF0E752617@ussjex01.amer.bea.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="=-NTBFDQIgvg/1WxfkgJZP"
Organization: High Sierra Technology, SLU
Date: Fri, 25 Mar 2005 03:22:37 +0100
Message-Id: <1111717357.25211.49.camel@localhost>
Mime-Version: 1.0

--=-NTBFDQIgvg/1WxfkgJZP
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

El jue, 24-03-2005 a las 16:43 -0800, Jim Barnett escribi=C3=B3:
(...snip...)
> It may be more likely that a UK employee will own the contributions he
> or she develops due to more pro-Employee invention ownership laws,
> that
> increased likelihood of a "clean" contribution still does not address
> the root question:  How does the ASF know that an employee's
> contribution is really "clean" in the absence of a CCLA from his or
> her
> employer?  Even under UK law the question of whether the employee
> worked
> exclusively on his or her own time using his or her own resources
> determines whether the employer or employee owns the contribution.

Basically we trust the signed ICLA we receive. Without further
knowledge, and having into account that Open Source work is done "in the
agora", as Bill said. I think we have a pretty good case, with public
archives of any and each contribution that the employer can spot and
tell us there's something wrong. It the IP was truly relevant to their
business line, they better have a good excuse why they were not able to
do any "corporate intelligence" around core IP, specially in cases where
contributions last years.

The "submarine" or "unaware" cases are far more probable in code
contributions, which is why we ask for a CCLA for those.

Regards
--=20
Santiago Gala <sgala@hisitech.com>
High Sierra Technology, SLU

--=-NTBFDQIgvg/1WxfkgJZP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
	digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCQ3XtMGY6e0B83Y0RApGTAKCU7A4JoutH4eVTG04l5rO2DzrE7gCeMXI2
HzBNUHMOmUo7mwneBjlZhho=
=bszq
-----END PGP SIGNATURE-----

--=-NTBFDQIgvg/1WxfkgJZP--