Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 965B4D4B8 for ; Tue, 13 Nov 2012 04:12:09 +0000 (UTC) Received: (qmail 73949 invoked by uid 500); 13 Nov 2012 04:12:09 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 73630 invoked by uid 500); 13 Nov 2012 04:12:08 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 73608 invoked by uid 99); 13 Nov 2012 04:12:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 04:12:07 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of radhika.puthiyetath@citrix.com designates 203.166.19.134 as permitted sender) Received: from [203.166.19.134] (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Nov 2012 04:12:01 +0000 X-IronPort-AV: E=Sophos;i="4.80,764,1344211200"; d="scan'208";a="13481433" Received: from banpmailmx01.citrite.net ([10.103.128.73]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 13 Nov 2012 04:11:33 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.72]) by BANPMAILMX01.citrite.net ([10.103.128.73]) with mapi; Tue, 13 Nov 2012 09:41:32 +0530 From: Radhika Puthiyetath To: "cloudstack-dev@incubator.apache.org" CC: Jessica Tomechak Date: Tue, 13 Nov 2012 09:41:24 +0530 Subject: RE: [Discuss] User Comment Functionality for the ASFCS Doc Pages Thread-Topic: [Discuss] User Comment Functionality for the ASFCS Doc Pages Thread-Index: Ac3A+o7oASzyahyrRQWYQdN0w5iGDgAWE4Cg Message-ID: <97F4356AEA71904482CD192135C038F90113046EDE25@BANPMAILBOX01.citrite.net> References: <97F4356AEA71904482CD192135C038F90113046EDDFF@BANPMAILBOX01.citrite.net> <1352741029.28690.140661152681001.4E22DA32@webmail.messagingengine.com> In-Reply-To: <1352741029.28690.140661152681001.4E22DA32@webmail.messagingengine.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi, Improving documentation is always our priority. What I am suggesting is a "= nice-to-have" feature in the future.=20 This was one of the earlier items that the doc team charted along with othe= r things, such as auto-build.=20 The comments are usually monitored and responded by the doc team itself. W= e can definitely do some R&D around Publican to devise such a mechanism. I felt receiving comments from readers is as important as getting the numbe= r of random visits. Jessica, please share your suggestions as well. Thanks -Radhika -----Original Message----- From: Joe Brockmeier [mailto:jzb@zonker.net]=20 Sent: Monday, November 12, 2012 10:54 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [Discuss] User Comment Functionality for the ASFCS Doc Pages On Mon, Nov 12, 2012, at 11:09 AM, Radhika Puthiyetath wrote: > Hi Community, >=20 > Analytics discussion reminded me of this functionality of most product=20 > documentation pages: Leave a Comment/ User comments. >=20 > Could we integrate "Leave a Comment" functionality to the Apache=20 > CloudStack Documentation pages? The questions that come to mind immediately: - Technically, how would you accomplish this? We use Apache CMS for the sit= e - it does not have commenting functionality. The docs are published with = Publican, which doesn't provide any commenting functionality.=20 Now - it's not impossible, but it's a feature that seems less important to = me than working to improve the state of the docs in general. (Which still n= eed work.)=20 - Who's going to monitor, and respond to, the comments? Who's going to mana= ge spam filtering?=20 Best,=20 Joe -- Joe Brockmeier jzb@zonker.net Twitter: @jzb http://www.dissociatedpress.net/