Mailing-List: contact security-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: security-dev@xml.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <449A6A84.6070003@wingsofhermes.org>
Date: Thu, 22 Jun 2006 20:01:40 +1000
From: Berin Lautenbach <berin@wingsofhermes.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: board@apache.org
CC: pmc@xml.apache.org,  security-dev@xml.apache.org
Subject: Re: XML-Security TLP -> Santuario
References: <44992D7A.3000901@wingsofhermes.org>
 <8DDFAA2D-D1E4-4803-B8C8-7D992DA85E81@gbiv.com>
In-Reply-To: <8DDFAA2D-D1E4-4803-B8C8-7D992DA85E81@gbiv.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Roy T. Fielding wrote:

> It sounds like a decent idea for a federation, but a terrible idea
> for a project.  Projects need to be responsible for a product or they
> just end up in the weeds.  A federation of projects can simply maintain
> a general mailing list and website.

It would be responsible for code - the current xml-security stuff that
sits within the XML project/federation.  And it would look to start new
things as well - with an absolute intent to move them to TLP when
necessary (i.e. when it became clear the Santuario PMC did not have
direct oversite).

I know we are trying not to create umbrella projects - I'm trying to
walk a middle ground to see if we can make something like this work with
a community that fosters this area.  It's a bit of a community
experiment as well as a technical one.

Cheers,
	Berin