Re: Some news from the website :)
On Sat, 13 Oct 2007, David Paleino wrote:
Hi *,
seems kinda strange, but... I got it! :P
Before going to University, I spent *days* in trying to figure out the
information retrieval from BTS... now you can see the result of a single day
of coding on [1] ;)
I've also added a per-package page. Try to click on a link in that page!
I really like both (with the minor nitpicking that line spacings on the
overview page could be a little bit more dense).
I think I could add more fields to the single-package-pages, please let me know
what you wish to be added!
At the moment I have no suggestions for the single package pages but I
would like to see the bug severity listed on the overview page (perhaps
even using some kind of color code (red for RC, yellow for normal, green
for wishlist - or something like that, I'm just spoiling rugh ideas).
Further work to be done: in the per-package page, do not list only the bugs,
but retrieve information also from apt (python-apt probably). This will give a
full overview of a package just by pointing to
http://debian-med.alioth.debian.org/pkgs/<package>.php .
This would be really great and would definitely save some time (I was just
trying to learn how python-apt works and the "documentation by example" is
a little bit uhmm - well it might work ...)
I'm still thinking on how to use the task files: Andreas, do you have any
concrete proposal? :)
I'm working on this now I obviousely do not have to care about the python-apt
stuff. There is one thing I'm wondering about: How did you choose the packages
on the bug page? I would love if this list would be read from the meta package
dependency list. This would easily enable us to build those pages for all
existing meta packages.
[1] http://debian-med.alioth.debian.org/bugs.php
P.S.: if we'll want to include also pkg-emboss, or any other team, in the
website, things will get a bit harder and I'll need to hack something (i.e.
update-bugs, update-website, check-static, ...)
Well, you do not seem to base your package selection from the meta packages
obviousely because emboss is in the dependency list. Is there any principal
reason to do it otherwise?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: