Return-Path: 
 <dev-return-8907-apmail-stdcxx-dev-archive=stdcxx.apache.org@stdcxx.apache.org>
X-Original-To: apmail-stdcxx-dev-archive@www.apache.org
Delivered-To: apmail-stdcxx-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 36D78F1BD
	for <apmail-stdcxx-dev-archive@www.apache.org>;
 Tue, 16 Apr 2013 11:00:07 +0000 (UTC)
Received: (qmail 36351 invoked by uid 500); 16 Apr 2013 11:00:07 -0000
Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org
Received: (qmail 36214 invoked by uid 500); 16 Apr 2013 11:00:05 -0000
Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@stdcxx.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@stdcxx.apache.org>
List-Post: <mailto:dev@stdcxx.apache.org>
List-Id: <dev.stdcxx.apache.org>
Reply-To: dev@stdcxx.apache.org
Delivered-To: mailing list dev@stdcxx.apache.org
Received: (qmail 36094 invoked by uid 99); 16 Apr 2013 11:00:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 11:00:04 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of msebor@gmail.com designates
 74.125.83.45 as permitted sender)
Received: from [74.125.83.45] (HELO mail-ee0-f45.google.com) (74.125.83.45)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 10:59:57 +0000
Received: by mail-ee0-f45.google.com with SMTP id c50so168915eek.18
        for <multiple recipients>; Tue, 16 Apr 2013 03:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:message-id:date:from:organization:user-agent
         :mime-version:to:subject:references:in-reply-to:content-type
         :content-transfer-encoding;
        bh=plo5K04T1yTqQeY92WHuY0d0oLIzNQ8MHDkf2RKvRdM=;
        b=G0QB1chAK/nYuznvk9aQspDVVN70UMwjvyTrs856IRmOIxhFLnZqux5Gf2W5fTqsMw
         qkCPjuLI1xNJAwQ90GkI6NGauW5b0iHuM4KVidqqs0CZfMxJq5yWKJoQRu+g7EzRDaUa
         iFqpd/QfrfFdzxREQdUGc8Ctf9XI/AWw1RcyouWAb5sP461X27y3VDYTr0TqrtfQ8i2/
         vabJTVOS431Os/5E/+3BVAcglGBpKDC/fdRl+UnT/CycFuHFFVNkCpi7TX8RKGTXxYia
         ElrLlkC2SIjXiiQqZW2H/J1TiTTH+RpTd4OTHZ4Dqwt9u/TBQnmYy3rhB2sWTg81MeSx
         jCHA==
X-Received: by 10.15.43.73 with SMTP id w49mr5319517eev.12.1366109976969;
        Tue, 16 Apr 2013 03:59:36 -0700 (PDT)
Received: from dhcp-10-61-100-158.cisco.com (64-103-25-233.cisco.com.
 [64.103.25.233])
        by mx.google.com with ESMTPS id i53sm2209094eeu.5.2013.04.16.03.59.35
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 16 Apr 2013 03:59:36 -0700 (PDT)
Message-ID: <516D2F17.2020104@gmail.com>
Date: Tue, 16 Apr 2013 04:59:35 -0600
From: Martin Sebor <msebor@gmail.com>
Organization: Cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "dev@stdcxx.apache.org" <dev@stdcxx.apache.org>,
 user@stdcxx.apache.org
Subject: Re: spam posted to stdcxx Wiki
References: <5159A3F6.6050608@gmail.com>
 <alpine.DEB.2.00.1304011707430.6735@urchin.earth.li>
 <516BF9AF.9090502@gmail.com>
 <alpine.DEB.2.00.1304152349350.6735@urchin.earth.li>
In-Reply-To: <alpine.DEB.2.00.1304152349350.6735@urchin.earth.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

[Removing infra for now]

To prevent all the spam on the Wiki I'd like to request
infra to create two groups for us: the AdminGroup and
the ContributorsGroup with the obvious meaning. If you
are a stdcxx Wiki contributor interested in being in
either of the two groups please respond to me in the
next 24 hours with your stdcxx Wiki user name.

I think the AdminGroup should be limited to stdcxx
committers only.

Martin

On 4/15/13 4:53 PM, Nick Burch wrote:
> On Mon, 15 Apr 2013, Martin Sebor wrote:
>>> There have a been a couple of projects in March that have tightened
>>> up their wiki permissions like that, so a quick browse through the
>>> infra archives should tell you more about how it works, what to do etc
>>
>> Could you point me to a relevant post in the archive? I've
>> searched infrastructure-dev and infrastrcture-issues but
>> can't find anything relevant there, and I'm having trouble
>> finding the archive for this list.
>
> You want infrastructure@
>
>  From a quick glance at the Archives, these are some of the threads on
> it from March:
> https://mail-search.apache.org/members/private-arch/infrastructure/201303.mbox/%3CCD60DF0D.BBE4B%25chris.a.mattmann@jpl.nasa.gov%3E
>
> https://mail-search.apache.org/members/private-arch/infrastructure/201303.mbox/%3CCALhtWkeOfk-d8gHsTvDmcrFipaE1n0_fEZHS5GbFKAmWrJeDtA@mail.gmail.com%3E
>
> https://mail-search.apache.org/members/private-arch/infrastructure/201303.mbox/%3CCAPFNckgJmrCFebcaDmXoS-bxywugd1j_-1upn-6XaYH8-+_XiA@mail.gmail.com%3E
>
> (Read in conjunction with the access control wiki section[1])
>
> Nick
>
> [1]
> http://wiki.apache.org/general/OurWikiFarm#per_wiki_access_control_-_tighten_your_wiki_just_a_little.2C_benefit_just_a_lot
>