Thread: Techdocs v2
Hi Guys, Is anyone working on v2 of techdocs? The last 'new' version I saw was http://techdocs.postgresql.org/v2 which looks promising, if a little stagnant at the moment (not surprising given the lack of advertising it's had). Any thoughts how we could move things forward? Regards, Dave.
On Wed, 2004-06-02 at 08:24, Dave Page wrote: > Hi Guys, > > Is anyone working on v2 of techdocs? The last 'new' version I saw was > http://techdocs.postgresql.org/v2 which looks promising, if a little > stagnant at the moment (not surprising given the lack of advertising > it's had). > > Any thoughts how we could move things forward? > IIRC that is the wiki site that Justin started but later abandoned due to software issues and then "retirement", so no one is working on that v2. Josh was leading some folks on a bricolage version of the site but I believe that sputtered out due to lack of time to actually get everything working under bric. I've currently got things in CVS in an effort to keep things up and running, though haven't put any major effort into new development whilst waiting for www-v3 to be finished up. I have been investigating some wikis myself for a new version of techdocs, and I think I could settle on twiki, or at least if Marc wants to install it (it should be in ports) I'd be willing to put some content up. My other leaning is toward mediawiki, though it is my$ql based so probably not the best option. I've recently started kicking around the code, and if anyone is interested in porting it to postgresql please lmk, but from a realistic time sense twiki seems like my personal pick Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
<div dir="ltr" id="idOWAReplyText18407"><div dir="ltr"><font color="#000000" face="Arial" size="2"></font> </div></div><divdir="ltr"><br /><hr tabindex="-1" /><font face="Tahoma" size="2"><b>From:</b> Robert Treat<br/><b>Sent:</b> Thu 6/3/2004 1:53 PM<br /><b>To:</b> Dave Page<br /><b>Cc:</b> pgsql-www@postgresql.org<br /><b>Subject:</b>Re: [pgsql-www] Techdocs v2<br /></font></div><div><p><font size="2">I have been investigating some wikismyself for a new version of</font><br /><font size="2">techdocs, and I think I could settle on twiki, or at least ifMarc wants</font><br /><font size="2">to install it (it should be in ports) I'd be willing to put some content</font><br/><font size="2">up. </font><p><font color="#0000ff">No problem - it's installed now.</font><p><font color="#0000ff">Regards,Dave.</font></div>
Dave, Robert: > IIRC that is the wiki site that Justin started but later abandoned due > to software issues and then "retirement", so no one is working on that > v2. V2 was based on Zope/Plone, which we discovered to have abysmal performance on the postgresql.org BSD VM. Certainly it wouldn't be able to sustain the thousands of people a day that buzz through Techdocs (or used to, anyway). >Josh was leading some folks on a bricolage version of the site but > I believe that sputtered out due to lack of time to actually get > everything working under bric. Yeah. The holdup is the templating, which requires a knowledge of Mason. Unforntunately, I've been unable to locate anyone who knows Mason and has any free time at all. > I have been investigating some wikis myself for a new version of > techdocs, and I think I could settle on twiki, or at least if Marc wants > to install it (it should be in ports) I'd be willing to put some content > up. A wiki would be fine in general. I like what we have up for "guides". One request, though: I'd like it to be possible to flag some pages as "modifiable only by owner". The issue is that sometimes I will want to put content on Techdocs that has special copyright restrictions (such as magazine article reprints). This would mean preventing most users from modifying that page. I know that others have similar content up. That's the main issue that prevented me from being gung-ho about a wiki for techdocs earlier. -- Josh Berkus Aglio Database Solutions San Francisco
> -----Original Message----- > From: Josh Berkus [mailto:josh@agliodbs.com] > Sent: 04 June 2004 00:44 > To: Robert Treat; Dave Page > Cc: pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Techdocs v2 > > > A wiki would be fine in general. I like what we have up for > "guides". > > One request, though: I'd like it to be possible to flag some > pages as > "modifiable only by owner". The issue is that sometimes I > will want to put > content on Techdocs that has special copyright restrictions > (such as magazine > article reprints). This would mean preventing most users > from modifying > that page. I know that others have similar content up. > > That's the main issue that prevented me from being gung-ho > about a wiki for techdocs earlier. Yes, that's the one thing that has always put me off Wikis - the ability for some random wannabe 'h@x0r' to come and deface bits of the site. /D
> Yes, that's the one thing that has always put me off Wikis - the ability > for some random wannabe 'h@x0r' to come and deface bits of the site. > > /D Horde now has a wiki that allows you to restrict access using Horde's general permissions. Their wiki is called 'Wicked' and can use PostgreSQL to store pages. It's not production yet, but seems to run fine. We have it installed at work. For an example see: http://wiki.horde.org CVS Web: http://cvs.horde.org/browse.php/wicked/ Nightly Snapshot: http://ftp.horde.org/pub/snaps/ George Essig
From: George Essig
Sent: Fri 6/4/2004 5:24 PM
To: Josh Berkus; Robert Treat; Dave Page
Cc: pgsql-www@postgresql.org
Subject: Re: Techdocs v2
> Yes, that's the one thing that has always put me off Wikis - the ability > for some random wannabe 'h@x0r' to come and deface bits of the site. > > /D Horde now has a wiki that allows you to restrict access using Horde's general permissions. Their wiki is called 'Wicked' and can use PostgreSQL to store pages. It's not production yet, but seems to run fine. We have it installed at work. Hi George,
It looks nice (as to be expected from Horde), but in my experience their code tends to be quite slow. With the limited resources available to postgresql.org (at the moment, dunno how things will be with Marc's new server), that's a problem we could do without :-(
Regards, Dave