On Friday 30 May 2008 08:32:18 am Lucas Nussbaum wrote: > How much static content will you have? I mean: it's not like this > service will receive millions of requests per day. It could be better to > have only a few static pages, and do everything else on-demand. well, i'm taking a fairly conservative approach, at least for starting off, at trying to pre-generate everything. the less dynamic stuff going on the less chance for "bad things" happening with shoddy code, and the less one can be distracted by various other unrelated problems and instead put the focus on what should be presented and how. i'm sure that we'll inevitably need some level of interactiveness, like having a way to query the patches for a package, add/remove patch metadata, interacting with external sources, etc, but starting simple with something that can hopefully have smaller portions gutted later to do this. again, had less time than hoped for on this, but i've been making enough progress that i can at least share the humble beginnings of the code. there's not a whole lot to see, just a breakdown of the patch info from the diff.gz in various ways (./debian , non-./debian, series patch listing and info) and downloadable/marked-up versions of all the patches: http://git.debian.org/?p=users/seanius/patch-tracker.git;a=summary there's a README with some brief info. and i've rsync'd a copy of my "partial" source archive tracking data (okay, so it's three semi-randomly chosen source packages, one native, one diff.gz. only, one with quilt-like series) here: http://people.debian.org/~seanius/pts/patches/ the design is fairly spartan at this point, but it's all xhtml compliant and using a centralized stylesheet, so that can be fixed later :) anyway, the lines are open for comments/suggestions/patches/etc :) sean
Attachment:
signature.asc
Description: This is a digitally signed message part.