Re: [naviserver-devel] Documentation & website question

[Vlad S. <vl...@cr...>]

This sounds better solution than using SF wiki but still site will not 
be distinctive and look like "very spare time and not often used project".

I am still thinking a dedicated server running naviserver is the way to 
go but as it happen before i am not convincing anybody, just my opinion

Stephen Deasey wrote:
> On 9/7/06, Bernd Eidenschink <eid...@we...> wrote:
>>> If the API doc is always automatically uptodate on the website then
>>> that can be the single canonical location to find everything.
>> A little grouching from me: Not now, but sometime later, we need a faster
>> webpage. No matter what:  a dedicated server, a new or version of the Wiki or
>> another Wiki that allows caching in the sense of static HTML pages, or no
>> Wiki at all and from whatever produced HTML pages.
>> But currently THIS wiki is so slow at times, so r e a l l y slow, it kills
>> time you could better invest in doing real work.
>>
>> Bernd.
> 
> It is annoyingly slow, isn't it.  The MediaWiki does already cache to disk...
> 
> Here's a weird idea:  Why don't we use the Tcl wiki?
> 
>   http://wiki.tcl.tk/
> 
> NaviServer *is* a Tcl application, and our examples are mainly going
> to be Tcl applications.  We have a whole bunch of Tcl (NaviServer)
> modules.  We probably should be a bit more integrated into the Tcl
> community, and I'm sure there a are Tcl folks who would be interested
> in what we're doing.  It doesn't feel like we'd be spamming some one
> else wiki.
> 
> Doing this would maintain a very important advantage we currently have
> with sourceforge: very little maintenance on our part. In fact it
> would be better: zero maintenance!  Plus, presumably there would be
> more people to help clean up after spammers etc.
> 
> A disadvantage might be that the Tcl wiki is a little plain. We also
> don't have any control, should we need to change something.  Well, I
> guess we have as much control as the rest of the Tcl community -- we
> can ask.
> 
> 
> If we did this, I imagine we would turn the current front page into a
> static portal page.  It would point to key pages within the Tcl wiki
> which we would maintain, along with pointers to out mailing list
> interface, cvs, etc.
> 
> The rest of our current website would be auto generated.  The API
> docs, we've mentioned.  We should also auto generate a page for each
> module in cvs, using the DOAP file.
> 
> 
> Is this a crazy idea?  Should we ask someone at the Tcl wiki?
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/