Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-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 288176748 for ; Sat, 14 May 2011 10:20:39 +0000 (UTC) Received: (qmail 23068 invoked by uid 500); 14 May 2011 10:20:39 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 22891 invoked by uid 500); 14 May 2011 10:20:38 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 22773 invoked by uid 99); 14 May 2011 10:20:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 May 2011 10:20:38 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [82.71.204.226] (HELO cpanelsmarthost2.zen.co.uk) (82.71.204.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 May 2011 10:20:28 +0000 Received: from [82.71.204.9] (helo=zencphosting06.zen.co.uk) by cpanelsmarthost2.zen.co.uk with esmtp (Exim 4.69) (envelope-from ) id 1QLBx9-0007vi-Dv for dev@community.apache.org; Sat, 14 May 2011 10:20:07 +0000 Received: from 5ac6905f.bb.sky.com ([90.198.144.95] helo=[192.168.0.3]) by zencphosting06.zen.co.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1QLBx9-0005LI-07 for dev@community.apache.org; Sat, 14 May 2011 11:20:07 +0100 References: <4DCBF2D1.1090000@apache.org> <4DCC36CD.2000403@apache.org> <4DCC4BC0.3040005@apache.org> <4DCC620D.4030105@apache.org> <8C87C259-6282-40C3-8C18-B063E73F4C47@gmail.com> <3E26A879-0853-4904-A9AA-0DDA1EA67C26@gmail.com> In-Reply-To: <3E26A879-0853-4904-A9AA-0DDA1EA67C26@gmail.com> Mime-Version: 1.0 (iPhone Mail 8H7) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <68FF7D1A-4F9D-484F-B132-B0B13FFD6FBA@apache.org> Cc: "dev@community.apache.org" X-Mailer: iPhone Mail (8H7) From: Ross Gardler Subject: Capturing mail (was Re: Stackoverflow) Date: Sat, 14 May 2011 11:20:09 +0100 To: "dev@community.apache.org" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zencphosting06.zen.co.uk X-AntiAbuse: Original Domain - community.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - apache.org X-Virus-Checked: Checked by ClamAV on apache.org Sent from my mobile device (so please excuse typos) On 13 May 2011, at 02:31, David Blevins wrote: > For me tagging and voting and (i forgot) the marking the question answered= (thanks, Benson) are the parts I would love. >=20 > I write some really good responses sometimes and even *I* have a hard time= finding some of my old responses in the list archive haystack. Right. I always ask users to provide a patch if they find an answer in the m= ailing list useful. Of course it rarely happens (even with devs).=20 Keeping things simple, could we provide a feature in the CMS that simply cop= ies a mail from our archives (with backlinks) into the CMS system for the ap= propriate project? A link to this could also be provided in the footer of each mail (only works= for committers). In the CMS we could have some magic system to build an index.=20 I appreciate this has now moved away from stack overflow (I changed the subj= ect) but for any Perl hackers looking for something useful to do on a weeken= d I would certainly use such a feature.=20 This could grow to fancy tagging, tracking and more. But I believe thus is a= reasonably simple thin to do that would provide immediate benefits.=20 Ross >=20 > And to avoid the "tag names can be spam" issue having so that only committ= ers can introduce new tags would be fine for me. It could be a file in svn o= r something else equally lame but functional. >=20 >=20 > -David >=20 > On May 12, 2011, at 6:04 PM, Ted Dunning wrote: >=20 >> There is another factor that comes into play. QA sites like SO also blen= d >> in wiki and trust mechanisms. Thus, highly rated users can and do rewrit= e >> questions to be more answerable/understandable. They can also rewrite >> answers if necessary. >>=20 >> Without automated karma, the moderation function has to be granted manual= ly >> which is a process that doesn't scale as easily and is subject to attack b= y >> cabals. That way lies wikipedia's dictatorship of the editor proletariat= >> and associated drop in user participation. That is fine for a largely >> static knowledge base, but SO addresses much more dynamic topics in a way= >> that engages the readership much more strongly. Moreover, the feedback >> cycle essentially guarantees that the moderators reflect the interests of= >> the voting public. >>=20 >> On Thu, May 12, 2011 at 5:47 PM, David Blevins w= rote: >>=20 >>> Another thought. Sometimes I wonder how hard it would be to just allow >>> tagging and voting on top of a plain mailing list emails. A simple DB w= ith >>> the messageId as the key for tags and vote count then a slightly fancier= >>> archive view than we have now. And hey, markdown happens to look nice a= s >>> plain email. I've actually been indenting code snippets for years. >>>=20 >>> I admit I like getting SO points and badges but they do not factor in at= >>> all when looking for the right answer. >>>=20 >=20