Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of hgranqvist@verisign.com
 designates 65.205.251.74 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Specifications as (part of) ASF projects (was RE: Too many
 licenses?  Was: [vote] Accept Glasgow)
Date: Mon, 14 Aug 2006 09:56:17 -0700
Message-ID: 
 <45D459DDA07DC442A499A4D46F4939BA01FD7D4D@MOU1WNEXMB02.vcorp.ad.vrsn.com>
Thread-Topic: Specifications as (part of) ASF projects (was RE: Too many
 licenses?  Was: [vote] Accept Glasgow)
Thread-Index: Aca/AOZ+L0nBCfk2Rpa54tHsygd+ggAvRZPA
From: "Granqvist, Hans" <hgranqvist@verisign.com>
To: <general@incubator.apache.org>, <cctrieloff@redhat.com>

> ...
> I would be in favor of such an approach.  Honestly, I would=20
> vastly prefer to have Open Specifications managed under ASF=20
> processes than under the JCP, OASIS, etc.

Yea, I think it could be a good idea.=20

Just a few thoughts on the process:  How do you envision editorship=20
of the spec?  Would all committers be editors? =20

I would propose a different set of 'spec committers' for two main
reasons.=20

1. Specifications are different:  Code can be modularized (and
   hidden by APIs) to a higher degree, so coders can work on=20
   independent sections.  This view doesn't work well for
   specifications where you need a fuller view. =20

2. The skills needed to write a good spec are not necessarily=20
   those needed to write good code, e.g., linguistic clarity.=20

Hans

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org