Return-Path: 
 <repository-return-590-apmail-repository-archive=apache.org@apache.org>
Delivered-To: apmail-repository-archive@www.apache.org
Received: (qmail 70932 invoked from network); 15 Mar 2004 22:33:56 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 15 Mar 2004 22:33:56 -0000
Received: (qmail 18411 invoked by uid 500); 15 Mar 2004 22:33:43 -0000
Delivered-To: apmail-repository-archive@apache.org
Received: (qmail 18366 invoked by uid 500); 15 Mar 2004 22:33:42 -0000
Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:repository-help@apache.org>
list-unsubscribe: <mailto:repository-unsubscribe@apache.org>
list-post: <mailto:repository@apache.org>
Reply-To: repository@apache.org
Delivered-To: mailing list repository@apache.org
Received: (qmail 18338 invoked from network); 15 Mar 2004 22:33:42 -0000
Received: from unknown (HELO smtp-out5.blueyonder.co.uk) (195.188.213.8)
  by daedalus.apache.org with SMTP; 15 Mar 2004 22:33:42 -0000
Received: from [10.0.0.2] ([82.38.65.173]) by smtp-out5.blueyonder.co.uk with
 Microsoft SMTPSVC(5.0.2195.5600);
	 Mon, 15 Mar 2004 22:33:48 +0000
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <40510DD3.2060901@latte.harvard.edu>
References: <NBBBJGEAGJAKLIDBKJOPAEOGHOAB.noel@devtech.com>
 <40510DD3.2060901@latte.harvard.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D265F616-76D0-11D8-82FD-003065DC754C@apache.org>
Content-Transfer-Encoding: 7bit
From: robert burrell donkin <rdonkin@apache.org>
Subject: Re: adding jaxme jars
Date: Mon, 15 Mar 2004 22:33:46 +0000
To: repository@apache.org
X-Mailer: Apple Mail (2.612)
X-OriginalArrivalTime: 15 Mar 2004 22:33:48.0296 (UTC)
 FILETIME=[9559D880:01C40ADD]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

On 12 Mar 2004, at 01:09, Mark R. Diggory wrote:

<snip>

> 2.) It's next to impossible to enforce a directory structure/naming 
> policy with the contents of the directories writable (let alone the 
> fact that its an actual directory structure). Even those intimate with 
> the project and effort end up doing things they consider minor which 
> in turn effect the entire community adversely.

it wouldn't be unreasonable to request that infrastructure create a 
group for the repository administrators.


mark - what's the current status?

(i'd like to be able to use these jars in a jelly tag library.)

i'm a bit confused because the jar's were simply unpacked from the 
tar-balled 0.2 incubation release. there has been a vote in the ws pmc 
but i'm also more than a little unclear as to why a separate release 
vote is necessary for adding jars which have already been released into 
the repository. is this also the case for new releases? (for example, 
would separate pmc votes be required to release the jaxme 0.3 
distributions and to add the jar within them to the repository?)

BTW i do appreciate you work in getting the repository up and running. 
these kinds of roles are difficult and energy sapping but are important 
to the ASF.

- robert