On Fri, 2007-01-05 at 18:00 +0100, Thorsten Leemhuis wrote: > Jesse Keating schrieb: > > On Friday 05 January 2007 10:57, Will Woods wrote: > > One thing that has been suggested before is that each package gets a wiki > > page, or some other sort of page, that has in formation regarding who > > maintains it, where is the upstream, Summary/Description all that, and also > > it could have information about how to use/test that package. > > > > I certainly think much of this info should be automatically generated out of > > the package database, and some of it user contributed. How to get there, I > > have no idea. > > My preferred solution: let some script/tool generate static pages with a > url that does not change, e.g. > > fedoraproject.org/packages/foo/ > > Some informations for those pages could come from the package database, > and some others from the SRPM (maybe a slightly enhanced or modified > version of repoview could do that). > > When that scripts runs let it check for the existence of > fedoraproject.org/wiki/Packages/foo > and integrate those parts and/or simply link to that page. The > maintainer or interested users could then maintain some further > informations (important bugs, known problems, ...) in the wiki easily. Right, my working theory was that there'd be a site (say qa.fedoraproject.org) to hold static test results and autogenerated info for each package and such, with links to the package page on the wiki. I've been meaning to talk to the infrastructure folks about getting the virtual host set up and a couple shell accounts for the automated tools to use.. -w
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ fedora-advisory-board mailing list fedora-advisory-board@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board
_______________________________________________ fedora-advisory-board-readonly mailing list fedora-advisory-board-readonly@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-advisory-board-readonly
