Return-Path: 
 <forrest-dev-return-7215-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org
Received: (qmail 73060 invoked from network); 15 Sep 2003 12:35:14 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 15 Sep 2003 12:35:14 -0000
Received: (qmail 60103 invoked by uid 500); 15 Sep 2003 12:35:10 -0000
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 60063 invoked by uid 500); 15 Sep 2003 12:35:10 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 60050 invoked from network); 15 Sep 2003 12:35:09 -0000
Received: from unknown (HELO grunt21.ihug.com.au) (203.109.249.141)
  by daedalus.apache.org with SMTP; 15 Sep 2003 12:35:09 -0000
Received: from p56-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.140.56]
	by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 19ysZR-0000NV-00; Mon, 15 Sep 2003 22:35:09 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 19ysbU-0001G9-00
	for <forrest-dev@xml.apache.org>; Mon, 15 Sep 2003 22:37:16 +1000
Date: Mon, 15 Sep 2003 22:37:16 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: Project definition. (Re: [RT] Status.xml, changes.xml,
 todos.xmlm, news and other descriptors])
Message-ID: <20030915123716.GB3987@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <3F64B47F.2060302@che-che.com> <bk3ntn$r1b$1@sea.gmane.org>
 <20030915094149.GA1505@expresso.localdomain> <3F658EBD.3030108@che-che.com>
 <20030915101930.GC1505@expresso.localdomain> <3F659961.4090907@che-che.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F659961.4090907@che-che.com>
User-Agent: Mutt/1.5.4i
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 Mon, Sep 15, 2003 at 12:50:09PM +0200, Juan Jose Pablos wrote:
> Jeff Turner wrote:
> >>>1) Deprecate the <todo> section in favour of using an issue tracker.
> >>>Even in Forrest, no-one bothers to keep it up to date.
> >>
> >>Even if you add a issue tracker you need to keep a scheme so you can 
> >>imported in the same fashion as you do with changes.rss.
> >
> >
> >Er, say again?  JIRA has RSS feeds..
> >
> 
> we are talking about definition of the format to use, it is not 
> important if our source is a file, another source (wiki) or rss feed.

Oh I see.  We can create a common intermediate XML format if you like.
IMHO live issues (bugs and todo items) are best displayed in an issue
tracker, where users can run queries and add comments to them.

> What is important at this point if to ensure that we have the right xml 
> schema for our projects.
> 
> >
> >
> >We don't need to _replace_ it, just support additional text-based
> >formats, that would be transformed internally into the XML format.
> >
> >--Jeff
> 
> still, to give you an example, we have been adding all these action 
> items on status.xml, now we are able to:
> 
> 
> Order and display content by  @dev @type @context
> Divide for contributed actions
> count number of bug fixed.
> 
> 
> are you able to do that with wiki?

Possibly, probably not in general.  It's a tradeoff:

text -> XML -> database + issue tracker

Each step gives up convenience for increased detail and queryability.
Forrest should support whatever our users want.  From observation, I'd
say most value a simple syntax over queryability.


--Jeff


> Cheers,
> Cheche
>