Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-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 B095C778F for ; Thu, 11 Aug 2011 10:16:33 +0000 (UTC) Received: (qmail 4068 invoked by uid 500); 11 Aug 2011 10:16:27 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 1529 invoked by uid 500); 11 Aug 2011 10:16:19 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 1457 invoked by uid 99); 11 Aug 2011 10:16:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2011 10:16:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jogischmidt@googlemail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2011 10:16:08 +0000 Received: by bkbzu17 with SMTP id zu17so936360bkb.6 for ; Thu, 11 Aug 2011 03:15:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=kzkiZG/TVzEr66YS+oOjp3ZDzuIdDXfz/sRVFK7zv98=; b=Uq9kEJK0eVnVdHdSoy8Z7qT/PHkQAIH4ARkZ/1P3E8AeLutdvP7niBnfQXMzgMZQyT pLT7akMdZ0cER2DebQnMaAzDSmYL35/ae95rwq/m5IAtFFEQ/Rg86Ke2hAv7COba2mb7 tU71bkpIxQkZUKERBR/rYJUuBJRSnuI+mnn2E= MIME-Version: 1.0 Received: by 10.204.181.66 with SMTP id bx2mr667217bkb.386.1313057748210; Thu, 11 Aug 2011 03:15:48 -0700 (PDT) Received: by 10.204.101.196 with HTTP; Thu, 11 Aug 2011 03:15:48 -0700 (PDT) In-Reply-To: <7DE220F2-5AFE-4A01-AEEC-58CF1CA9F379@webmink.com> References: <7DE220F2-5AFE-4A01-AEEC-58CF1CA9F379@webmink.com> Date: Thu, 11 Aug 2011 12:15:48 +0200 Message-ID: Subject: Re: Making mailing lists useful (was Re: [Proposal]) From: =?UTF-8?Q?J=C3=BCrgen_Schmidt?= To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e6d78524a6d4ae04aa381464 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6d78524a6d4ae04aa381464 Content-Type: text/plain; charset=UTF-8 On Thu, Aug 11, 2011 at 12:21 AM, Simon Phipps wrote: > > On 10 Aug 2011, at 23:12, Rob Weir wrote: > > > On Wed, Aug 10, 2011 at 5:28 PM, Kay Schenk > wrote: > >> On Mon, Aug 8, 2011 at 9:01 AM, Ross Gardler < > rgardler@opendirective.com>wrote: > >> > >>> On 8 August 2011 16:14, Kay Schenk wrote: > >>> > >>> ... > >>> > >>>> From my perspective, I don't see the one BIG list as bad, but it would > be > >>>> VERY helpful if folks could label messages more succinctly and > restrict > >>>> discussion to rather specific aspects. > >>> > >>> +1 > >>> > >>> Not to mention useful subject lines (take a look at what the original > >>> subject was for the thread I took this from - I didn't edit the > >>> original and it is not truncated) > >>> > >>>> And, documenting what's been discussed is CRITICAL! It is madness to > try > >>> to > >>>> sift through these messages to get to the "implementable" aspects. > >>> > >>> +1 > >>> > >>> I really like the practice I see in some communities where someone > >>> will take long rambling threads and post a "[summary] foo bar" mail > >>> the the thread periodically. This is brilliant for those needing to > >>> catch up and also acts as a description of "impementable" conclusions > >>> and community consensus that is emerging. > >>> > >>> Ross > >>> > >> > >> Great idea if we could find a volunteer! I tried to do this (only once) > on > >> the "refactoring discussion" but I'll tell you some of these discussions > are > >> SO lengthy it's impossible. > >> > >> Maybe we'll do better (and some good soul will step up for the > documentation > >> aspects) if we can adhere to some discussion standards. > >> > > > > We have a mailing lists page: > > http://incubator.apache.org/openofficeorg/mailing-lists.html > > > > A list of proposed subject tags would fit very well there, after the > > first paragraph. Committers can easily edit this using the Apache > > CMS in their browsers: > > > > http://incubator.apache.org/openofficeorg/docs/edit-cms.html > > > > For example, I just added the link the email tips earlier today. > > It would be better to put the list of subject tags on the community wiki so > that those of us who've not been invited to be committers can also edit it. > where is the problem here, if you want to be a committer you know the rules and can follow them. I don't see a real problem if you contribute valuable content to the project. If you should have a problem with the iCLA then it is your problem. And by the way new tags will or should be discussed here anyway and probably some of the committers will add new approved tags quite fast. Juergen > > S. > > > --0016e6d78524a6d4ae04aa381464--