On 27.01.2013 16:17, Daniel Shahaf wrote:
> Branko Čibej wrote on Sat, Jan 26, 2013 at 15:30:04 +0100:
>> On 26.01.2013 14:27, Benson Margulies wrote:
>>> Brane, are you currently using the pickled clutch metadata? If we just
>>> need to add a field to it we can.
>> Nope, I'm currently walking the incubator archive tree. The clutch
>> metadata is in general good enough, since if clutch can generate
>> target/current.ent, I can certainly get the information I need from
>> that. The only question is the conversion from
>> l...@podling.incubator.apache.org (which clutch knows about) to
>> archive/podling.apache.org/list (which is where the podling mail
>> archives will be in future) is consistent.
>>
> Yes, it is, for all *@p.i.a.o lists.
Well, I've found an inconsistency while changing the scripts to parse
the content/podlings.xml and content/projects/<podling-name>.xml.
Onami's dev list is the old-style:
onami-...@incubator.apache.org
but its archive is new-style:
onami.incubator.apache.org/dev
I don't want to special-case the script for this; can we make the
archive consistent with the mailing list address?
I also found two other problems: flex and photark removed the
'id="mail-dev"' attributes from their status XML files, and also
replaced the list address with the web archive address, so there's no
machine-readable way to find their mailing list address. I think it
would be a good idea to require that the <podling-name>.xml files are
machine-readable in the sense that all relevant information about a
podling can be extracted from them without special-casing scripts.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
