Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 45824 invoked from network); 19 Jan 2001 09:24:53 -0000 Received: from bodewig.bost.de (root@195.227.98.11) by h31.sny.collab.net with SMTP; 19 Jan 2001 09:24:53 -0000 Received: (from bodewig@localhost) by bodewig.bost.de (8.9.3/8.9.3) id KAA02187; Fri, 19 Jan 2001 10:25:05 +0100 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@bost.de using -f To: ant-dev@jakarta.apache.org Subject: Re: So, The Show Must Go On References: <20010118163052.28748.qmail@web2302.mail.yahoo.com> From: Stefan Bodewig Date: 19 Jan 2001 10:25:05 +0100 Message-ID: Lines: 26 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Simeon Fitch wrote: > I'm thinking that it might be a really good idea if the contents of > some of these emails where extracted and checked into some part of > the cvs tree so that there is some centralized point for people to > reference. I've gone ahead and checked in Pete's mail together with my comments from December and some additional stuff in docs/ant2/. This is just the brainstorming that it is, no ordering of items, no formal description. I want to see this as a starting point, where anybody is welcome to contribute. This should be formalized into a functional requirements doc after we've settled on a feature set and _after_that_ we should start talking about implementation issues. > Since this is brainstorming, anything is allowed: requirements, > designs, implementation approaches, whatever. I'm not sure I want to talk about implementation at this point, but if anybody else wants to do so, please use a different document in the same directory, keep the requested-features.txt just what the name implies. Stefan