> > > > Not sure they all apply. The PWN stuff has to render
> > > natively, whereas
> > > > the FAQs are post-processed by the site code (because
> they have to
> > > > work both inside the siet as a wrapper and as standalone HTML
> > > > documents)
> > >
> > > I thought we were talking about the TODO list, not the FAQs?
> >
> > We are. But the TODO list is in the FAQ directory, and is
> handled just
> > like the FAQs.
> >
> >
> > > And let me pitch Bruce again to database the TODO list ....
> >
> > Um. Let me second that ;-) But I've also tried before :-)
>
> Go ahead. I find a database is more work but if someone else
> wants to try it, they are welcome. I will continue
> maintaining the TODO for a while just in case the new idea
> doesn't work out, like it didn't last time. :-)
Actually, the even more important things about this I beleive are:
1) Unless you, who are actually going to maintain it, think it's good,
it's never going to work. And I'm certainly no saying someone else
(expecially not me! :P) should maintain it... (while it could perhaps be
shared, but that can be done either way)
2) I *personally* think it should also be combined with being some kind
of bug tracker (more along the line of a general issue tracker), and
that's *definitly* going to fly unless the people who would use it most
(-core and other main developers) want it. And the archives are full of
discussinos about that ;-)
If you're interested in giving at least (1) a try, let me know. But
since you're the guy who maintains it (and has been for a long time),
you're the one who knows what the specs will have to be so it fullfills
your requiremetns :-)
//Magnus
