Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-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 A08B6FB2B for ; Mon, 8 Apr 2013 17:45:23 +0000 (UTC) Received: (qmail 79690 invoked by uid 500); 8 Apr 2013 17:45:23 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 79673 invoked by uid 500); 8 Apr 2013 17:45:23 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 79664 invoked by uid 99); 8 Apr 2013 17:45:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 17:45:23 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of m.v.lunteren@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Apr 2013 17:45:17 +0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so4124498wib.3 for ; Mon, 08 Apr 2013 10:44:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=fvxO7YeULpNUs+TgCBks4j/h47y4L1M1xhjfd0lIy9o=; b=pSHmDkEP9y75JjOuIiAElfOD82L1qTGzSRvYpOA+5AdvsWpaS5mSvHSw8qmoE/6wRc RT5bUM5cHJG+X4d/IRkOni/jeeTGleAcmwObxeCYnwCyW/cx71GUHqw2nsIpGVk2oPQI ZwSbfDS++aKyAlluF15S5D+WW+5yA94eVnuiZvXl+WaMklPPMDIxyh+fo/4iaqP/LEib MiN4DHu7bIHimerj+6dFJotuLY326pAYtqmsDQ5Y0b5wcu4ZxbQwtXbOfhWjvICay2ad /j4lRL2w6J3GD9tq92uUDf4eS2AKJrqxMOHeynCwkN5LTw5dADT/Cokayzu7eMsspHHi Sk5g== MIME-Version: 1.0 X-Received: by 10.194.22.5 with SMTP id z5mr33247360wje.5.1365443097462; Mon, 08 Apr 2013 10:44:57 -0700 (PDT) Received: by 10.217.85.133 with HTTP; Mon, 8 Apr 2013 10:44:57 -0700 (PDT) In-Reply-To: <5162CA8D.5000000@oracle.com> References: <51558891.3020806@oracle.com> <51559E32.4000205@oracle.com> <5162CA8D.5000000@oracle.com> Date: Mon, 8 Apr 2013 10:44:57 -0700 Message-ID: Subject: Re: Fwd: [Db Wiki] Trivial Update of "FernandoO" by FernandoO From: Myrna van Lunteren To: derbydev Content-Type: multipart/alternative; boundary=047d7b5d34e8c9117d04d9dcfe0c X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5d34e8c9117d04d9dcfe0c Content-Type: text/plain; charset=ISO-8859-1 I believe we've gotten all the bad ones...I've been keeping track. Any that aren't there we can strip off later. So we can go with what we have now and if there's any bad ones we can remove them later. I'll log an issue, citing all active committers & Jean (as she responded to this message) to start with. Myrna On Mon, Apr 8, 2013 at 6:47 AM, Rick Hillegas wrote: > On 3/29/13 8:47 AM, Myrna van Lunteren wrote: > >> On Fri, Mar 29, 2013 at 6:59 AM, Kim Haase >> wrote: >> >>> I'm guessing it's would-be spammers trying to set up a legitimate-looking >>> URL. Thanks for continuing to delete the pages (to whoever is doing >>> that). >>> >>> Kim >>> >>> >>> On 3/29/2013 8:26 AM, Rick Hillegas wrote: >>> >>>> Does anyone know why we are seeing these changes to the wiki? Thanks >>>> >>>> Kim is right. >> There is/are manual spammers who are creating these. The automated >> spammers cannot cope with answering the question, but at this point, >> our wiki is open to anyone...and the answers to the questions are >> easily found. >> >> After the first one, which Knut Anders deleted, *I* have been deleting >> them, but depending on how many we get I might get very tired of this. >> We may at one point think of implementing the restrictions other >> projects have gone to already - see: >> >> http://wiki.apache.org/**general/OurWikiFarm#per_wiki_** >> access_control_-_tighten_your_**wiki_just_a_little.2C_benefit_** >> just_a_lot >> >> This suggests we could create an Admin group to which we'd have to >> request access to, and then only those with access can modify the >> wiki. >> >> It's a sad thing that this is necessary for an open source project, >> but there it is. >> >> > From other groups' questions to infra (specifically River) I noted the >> following further point: >> - we may need to log an issue like this: >> https://issues.apache.org/**jira/browse/INFRA-6010 >> >> For now, I'll just delete that puppy... >> >> Myrna >> >> Looks like we have a consensus building for locking down the wiki. If we > file an issue like INFRA-6010, then we'll need an initial list of legal > contributors. Anyone know how to get a list of current wiki names which we > could prune back to the ones we know? > > Thanks, > -Rick > --047d7b5d34e8c9117d04d9dcfe0c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I believe we've gotten all the bad ones...I'v= e been keeping track.
Any that aren't there we can strip = off later.

So we can go with what we have now and if ther= e's any bad ones we can remove them later.

I'll log an issue, citing all active committers & Jean (as she = responded to this message) to start with.

Myrna
=


On Mon, Apr 8, 2013 at 6:47 AM, Rick Hillegas <rick.hillegas@oracle= .com> wrote:
On 3/29/13 8:47 AM, Myrna van Lunteren wrote:
On Fri, Mar 29, 2013 at 6:59 AM, Kim Haase<camilla.haase@oracle.com> = =A0wrote:
I'm guessing it's would-be spammers trying to set up a legitimate-l= ooking
URL. Thanks for continuing to delete the pages (to whoever is doing that).<= br>
Kim


On 3/29/2013 8:26 AM, Rick Hillegas wrote:
Does anyone know why we are seeing these changes to the wiki? Thanks

Kim is right.
There is/are manual spammers who are creating these. The automated
spammers cannot cope with answering the question, but at this point,
our wiki is open to anyone...and the answers to the questions are
easily found.

After the first one, which Knut Anders deleted, *I* have been deleting
them, but depending on how many we get I might get very tired of this.
We may at one point think of implementing the restrictions other
projects have gone to already - see:

http://wiki.apache.org/general/OurWikiFarm#per_wiki_access= _control_-_tighten_your_wiki_just_a_little.2C_benefit_just_a_= lot

This suggests we could create an Admin group to which we'd have to
request access to, and then only those with access can modify the
wiki.

It's a sad thing that this is necessary for an open source project,
but there it is.

> From other groups' questions to infra (specifically River) I noted= the
following further point:
- we may need to log an issue like this:
https://issues.apache.org/jira/browse/INFRA-6010

For now, I'll just delete that puppy...

Myrna

Looks like we have a consensus building for locking down the wiki. If we fi= le an issue like INFRA-6010, then we'll need an initial list of legal c= ontributors. Anyone know how to get a list of current wiki names which we c= ould prune back to the ones we know?

Thanks,
-Rick

--047d7b5d34e8c9117d04d9dcfe0c--