Stas Bekman <[EMAIL PROTECTED]> wrote:
>On Sun, 16 Sep 2001, Jim wrote:
>> I am able to provide hosting at least during development. I'll put
>> out a URL when we get something together.
>
>That's great!
>
>Once it's working, we may start using it for all ASF projects and then
>it'll be easy to host it on ASF machines.
Sounds good.
>I've just stumbled upon SuSe knowledge base -- very nice:
>http://sdb.suse.de/en/sdb/html/index.html
I did look at it - initial impression is very favorable.
>Also check http://thingy.kcilink.com/modperlguide/, which is a special
>version of the guide that generates a page per section rather than having
>huge pages. So it should be able to take a document and split it into
>factoids/sections and while keeping them in relation, like the URL above.
>So when you search, each item gets searched separately, but when you view
>a section, you can still easily jump to the adjusent sections in the
>original doc.
This will take a little more thought, but I don't think it's unreasonable.
>and we have some docs in modperl-docs cvs rep already. Not much yet, but
>it's the beginning.
Good for testing with :)
>One thing I'd like to add is that the system should be capable of
>scratching its database and rebuilding everything from scratch. Consider
>some documentation being used as a source, getting modified, or some items
>become absolute and get removed, some items get added. Somehow the system
>should be able to handle this.
I should be able to track sufficient metadata that I can do this without
having to have the documents around (for the indices used in the interface)
or from the documents themselves (if *all* database files are wiped). This
also allows for arbitrary addition/deletion of arbitrary documents.
I started a project on sourceforge so I could use CVS and let others see
what's going on. I'll add RFEs that are mentioned on the list at some
point.
http://sourceforge.net/projects/perlkb/
I'm concentrating on the backend stuff. Someone else can focus on the
frontend(s) -- we can make the frontends subprojects just like the backend.
Each can have their subdirectory in cvs (basic future direction -- not
enough backend done yet for that). I'll put together a test interface at
some point - not meant to be functional, just testing.
I also haven't emailed the perl modules list yet, so the PerlKB name might
change at some point (the perl module, not the sub-project name).
------------------------------------+-----------------------------------------
James Smith - [EMAIL PROTECTED] | http://www.jamesmith.com/
[EMAIL PROTECTED] | http://cis.tamu.edu/systems/opensystems/
------------------------------------+------------------------------------------
