|
|
On 22/07/08 at 19:36 +0200, Filippo Giunchedi wrote:
> On Tue, Jul 22, 2008 at 09:29:49AM +0200, Stefano Zacchiroli wrote:
> > On Tue, Jul 22, 2008 at 12:45:34AM +0200, Filippo Giunchedi wrote:
> > > I've produced a script[0] to parse d-d-changes archives to a sane format
> > > so to
> > > produce an history of uploads made to debian[1] in this form:
> >
> > Very cool!
>
> Thanks :)
>
> >
> > > comments/ideas welcome as usual,
> >
> [...]
> > As the data encoded by d-d-changes is basically timed change
> > notifications, I would say that the more appropriate format to represent
> > it is a feed format, such as RSS or Atom, what do you think? Having such
> > a format would enable cool stuff to be created quite easily (e.g. even
> > using, say, Pipes), such as per-maintainer feed changes. Personally it
> > is something I would like to have linked from the DDPO.
> >
> > It shouldn't be to hard to convert (or maybe pair) your format to RSS,
> > with an appropriate XML encoding of its content, shout if you want to
> > discuss a potential DTD. Maybe a bit harder can be to provide more
> > lively updates, as if one then wants to use RSS as such, weekly updates
> > are too coarse grained ...
>
> Of course the idea of having more updated data is appealing, I'd myself
> welcome
> RSS/atom feeds per-package (almost the same as PTS' upload news) or
> per-maintainer (either changed-by or upload key or whatever). How to proceed
> for
> the XML encoding? And what might be the most interesting?
>
> The weekly update period is rather arbitrary, can be switched to daily
> effortlessly.
I'd like to avoid that the UDD gsoc project becomes the universal answer
in QA-dom, but it seems that it would make sense to do:
[d-d-c import] -> [UDD DB] --> [raw XML export]
`-> [RSS/atom export]
--
| Lucas Nussbaum
| lucas@xxxxxxxxxxxxxxxxxx http://www.lucas-nussbaum.net/ |
| jabber: lucas@xxxxxxxxxxx GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-qa-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
|
|