how about because of the size of the list, somehow placing them into
catagories. and even having a submit option where if someone experiances a
problem not listed, and when they figure it out, allow them to send their
q & a. it would be a good idea to have all the submitted ones approved
first, to prevent dup's... but i know i ran into some interesting things,
where i would think i would share my problem and solution to the KB, for
others to read.
-----Original Message-----
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>;
[EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, October 25, 1999 5:36 PM
Subject: Soliciting feedback about the Devzone Knowledge Base...
>
>
>Hey Everyone,
>
>I'm beginning to write a requirements document for version 2.0 of the
Devzone
>Knowledge Base. We're trying to make the Knowledge Base as useful a tool
as
>possible so I would like to get some feedback from the group.
>
>What features would you like to see added to the Knowledge Base (Mailing
list
>archiving is already on the list!)?
>What features would you like to see droped from the KB (if any)?
>What do you really like or dislike about the KB?
>What other comments do you have?
>
>Please email me directly ([EMAIL PROTECTED]) instead of spaming the
list.
>
>Thanks!
>
>Ryan Robertson
>Information Gatherer and Distributor
>
>
>
