cycle. If the project chooses to copy the STATUS items into an issue tracker so that they'll receive periodic reminders of outstanding items, that would be their choice, but the only official document would be the STATUS file. Since you want to use XML, if the XML were defined properly, someone could write a tool to generate a report of all outstanding items. But I don't think that we want to get into the process of building yet another ad hoc issue tracker.
Or we could stick with plain text. From what I think we are saying (including below), the original status file could come from a template, customized if/as necessary by the PMC and placed into the incubator CVS module.
Apologies for coming in late on the conversation - have been away from e-mail.
I think everyone is agreeing - but one other thought that comes to mind that supports a text STATUS file is that it is the minimal possible requirement.
So if we want to put a process/policy requirement in place, this is the one that makes sense. It can be implemented using a status tracker, or by processing an XML file - i.e. in whatever way the mentor/podling think is best for their incubation effort. If we start saying we want this tool or that then things start getting messy.
Doesn't mean that the Incubator can't point people to a favourite tracker as a tool - just means it's a suggestion, not a requirement.
Cheers,
Berin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
