← Back to team overview

opencog-dev team mailing list archive

Re: OpenCog documentation

 

It'll be on the wiki site, yeah...

and, initially, what I mainly need to do is extract/repurpose some
stuff from existing NM documents, rather
than writing new docs from scratch...

ben

On Mon, May 5, 2008 at 5:31 AM, Joel Pitt <joel.pitt@xxxxxxxxx> wrote:
> Hi Ben et al.,
>
>  On Sun, May 4, 2008 at 7:09 AM, Ben Goertzel <ben@xxxxxxxxxxxx> wrote:
>  >  I hope that the documentation will evolve into a good state during the second
>  >  half of 2008, as a result of interactions with other OpenCog developers, once
>  >  the code and docs are released...
>  >
>  >  One of the tasks on my plate now is preparing the initial OpenCog conceptual
>  >  documentation...
>
>  Not sure what your plans are for distributing this, but might I
>  suggest putting it on the OpenCog.org wiki? I think the large number
>  of concepts and terms that people will have to learn naturally lends
>  itself to a wiki environment. e.g. "I don't know, or I've forgotten
>  what that concept was about" *click the wiki word* "ahh, I remember
>  now." <- this was a somewhat frequent occurrence for me while reading
>  docs.
>
>  Although I'm not sure what your preference for writing is (what
>  editor, writing in a linear or outlining manner), so perhaps it would
>  be easier to take a complete document and then wikify it, or let the
>  community do so. Only problem then is that then the writing doesn't
>  always take advantage of the benefits a wiki structure can provide.
>
>  But perhaps it's just me that likes reading things in a non-linear manner ;)
>
>  J
>



-- 
Ben Goertzel, PhD
CEO, Novamente LLC and Biomind LLC
Director of Research, SIAI
ben@xxxxxxxxxxxx

"If men cease to believe that they will one day become gods then they
will surely become worms."
-- Henry Miller



References