> So who is going to contribute and maintain it?
My hope is that debian user, who have already set up the system, can
provide some information how they did it. It is true, there has to be
some more information, how the system is set up and what kernel he is
using. Someone using the manual should have the possibility to rate the
entry. And that way you can see what is going wrong. (I hope)
That information has to be also entered. (and the system behind has to
figure out, what is useful). I want also a rating of the different parts
of the manual, thus errors can be found quickly without getting
everybody frustrated.
> I think if you can get many success stories of people describing hardware
> setup together and serve them verbatim to the audience interested in them
> you would just have to write a search tool.
It is true, that the purpose of this could be done by a search engine,
but only to some content:
you will have many links to follow up. (it is not one piece, whereas the
upper thing should generate only one peace of paper and should take the
user from the boot floppies up to kde/gnome whatsoever. (it is sometimes
hard to know which modules make sense to load, and so on (already with
the boot floppy disk)). Most documents found do not suite debian to
100%, that would not be the case in that generator.
i want the user to have one source of information, thus he can be pretty
suer that works and that does not work. It should be a source for
hardware I want to by (I can look it up in the manual, if there is
information, it says how well it is supported (that is information
somebody has to provide)).
(I came up with the idea, because I am myself sometimes to lazy to
search, not because I would not find anything, but nothing that matches
exact what I need. I also watch people get frustrated, if they do not
know, where the first place is to go.)
It is right, there is a lists-search, but th bad thing about it:
It sometimes just does not give you the best hit or information you
just look for. That is why I was looking for something, that collects
information by topic, does not have any information 10000 times in
there. and in my mind, the propossed was one solution I saw.
But I see also many difficulties for the project:
-> Wrong information provided (how can I possibly know, if the
inforamtion is right)
-> Software changes (kernel - user software)
-> new Hardware
-> things that just have problems when are together on a system
-> printer: more then one possible driver (CUPS, lpr, ...)
and as you said is you said, the scripts searching for valid information
is pretty easy, but the structure of the database will have the most
importance for the whole thing to work.
Thank you, matthias
PS.: Thank you for your input :-)
PS.: If i missed a but, just send it. :-)
--
__ _ __ *********************
/\_/\ \ \_/ \_/ / * Matthias Wieser *
/ \ \ / * ICQ#: 12597522 *
/ /\_/\ \ \_/^\_/ * [EMAIL PROTECTED] *
WW WW *********************
