Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 8FBA29FB661; Fri, 8 Jun 2007 09:42:52 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 39594-08; Fri, 8 Jun 2007 09:42:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sn.sai.msu.ru (sn.sai.msu.ru [195.208.220.215]) by postgresql.org (Postfix) with ESMTP id 757A79FB5F0; Fri, 8 Jun 2007 09:42:45 -0300 (ADT) Received: from sn.sai.msu.ru (localhost [127.0.0.1]) by sn.sai.msu.ru (8.12.8/8.12.8) with ESMTP id l58CfuqR007775; Fri, 8 Jun 2007 16:41:56 +0400 Received: from localhost (megera@localhost) by sn.sai.msu.ru (8.12.8/8.12.8/Submit) with ESMTP id l58CfmiL007753; Fri, 8 Jun 2007 16:41:48 +0400 X-Authentication-Warning: sn.sai.msu.ru: megera owned process doing -bs Date: Fri, 8 Jun 2007 16:41:48 +0400 (MSD) From: Oleg Bartunov X-X-Sender: megera@sn.sai.msu.ru To: Kevin Hunter cc: Nikolay Samokhvalov , Magnus Hagander , Alvaro Herrera , PostgreSQL WWW List , PostgreSQL Documentation List Subject: Re: [DOCS] Users comments don't migrate to docs for new version? In-Reply-To: Message-ID: References: <20070606164029.GB11800@alvh.no-ip.org> <46670885.1050207@hagander.net>

MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/18 X-Sequence-Number: 12057 The possible solution would be a forum with specific page as an originated message and users comments as a thread messages. We use this approach for many years. Oleg On Fri, 8 Jun 2007, Kevin Hunter wrote: > At 5:18p -0400 on 07 Jun 2007, Nikolay Samokhvalov wrote: > >> But I suppose there are some cases when it's not possible to move the >> comment to the main text -- e.g. if the comment concerns too narrow >> area, is very specific and is useful not for all people (but still >> useful for some!). >> >> Moreover, moving good comments to the main text makes the text bloated >> -- what if we have 10 examples of using function aaa() and all of them >> are illustrations for different areas? We (ok, sorry, Tom because only >> he knows English) will choose only 1 of them to avoid bloating of the >> main text, even if all 10 use cases has some specific features... > > Hrm. If they're still good comments, what about including a hyperlink to a > pop-up or separate page with some specific information about that particular > point? ("There is more discussion on the many uses of the > function aaa()") Bloat for the main documentation could still avoided, > but if read on-line (as the docs are meant to be read?) then access to > other's wisdom need not lost/weeded out. > >> I could help with (yeah, not with reworking comments -- I do not know >> English well :-) ) creating a simple patch that adds a notice "this >> comment was originally created for version 8.0" and maybe something > > Although, short of above, perhaps this'd be an easier en masse solution? > >> BTW, then we would add some marking/rating system to the comments to allow >> other users see what comment is really useful. > > Kind of like digg or something? Where the higher-rated float to the top? > > Kevin > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly Regards, Oleg _____________________________________________________________ Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru), Sternberg Astronomical Institute, Moscow University, Russia Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(495)939-16-83, +007(495)939-23-83