Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 33079 invoked by uid 500); 5 Dec 2002 10:04:36 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 33063 invoked from network); 5 Dec 2002 10:04:35 -0000 Message-ID: <3DEF2498.5000108@apache.org> Date: Thu, 05 Dec 2002 05:04:08 -0500 From: Sam Ruby User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: general@xml.apache.org CC: board@apache.org, general@jakarta.apache.org Subject: Re: The organization of xml.apache.org References: <014801c29a47$8371e430$0a00a8c0@boo> <20021203123633.GD3501@expresso.localdomain> <018f01c29b65$bd944c10$0a00a8c0@boo> <20021204095056.GC3724@expresso.localdomain> <3DEDDE94.4000707@apache.org> <20021204120348.GA9245@expresso.localdomain> <01b801c29c27$49c378c0$0a00a8c0@boo> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ted Leung wrote: > Jeff's question below about the legal relevance of PMC's is a good one. > Does someone from the board have a definitive answer for this? IANAL. The simplest and most direct answer is that if the PMCs which were set up for this expressed purpose can not demonstrate that they have provided oversight, then the ASF itself is exposed. With that out of the way, two examples, assuming PMCs exercising proper oversight: 1) A person who is a committer explicitly and intentionally sets out to sabotage the ASF by introducing code which is owned by a third party without the permission of that third party. That code is quickly detected; the code and the committer are ejected. There never is a release with that code. The third party could decide to pursue legal action against the sabotager, but the ASF did its job. 2) Somebody attempts asserts ownership of a concept (say, hyperlinks), for which there is ample prior art, and an ASF codebase that provides an implementation of that concept. The ASF asserts ownership over that codebase and explicitly indemnifies its "shareholders", namely its membership. For these examples to work there needs to not be any nooks and crannies where unmonitored code may reside. I hope I got this right, but I am sure that Roy will correct me if I'm wrong. ;-) - Sam Ruby --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org