Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Tom King <ka6sox@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] locking down patchwork and wiki registrations
Date: Wed, 9 Jan 2013 16:12:27 -0600	[thread overview]
Message-ID: <50EDEB4B.1020009@windriver.com> (raw)
In-Reply-To: <CAHQecY7BzBxTJYbuXs_8qoPdeh-cfz3F4x186L1DqAgt-Lz95w@mail.gmail.com>

On 1/9/13 3:58 PM, Tom King wrote:
> There are many of us who watch and can do this (at least 10 "administrators")

As long as requests can avoid a black hole, I don't have any other concerns with 
manual registration.

--Mark

> Tom
>
> On Wed, Jan 9, 2013 at 1:55 PM, Mark Hatle <mark.hatle@windriver.com
> <mailto:mark.hatle@windriver.com>> wrote:
>
>     On 1/9/13 9:59 AM, Khem Raj wrote:
>
>         Hi
>
>         We receive tonne of spam in form of registrations everyday and some of
>         bots have become smarted that they even activate their
>         profiles. It has to be manually deleted and its tedious. I would
>         therefore like to remove the 'register' link from pw front page
>         that will stop the spam as I have already experimented with it a bit.
>
>         Same is also true for wiki. We should make the registration process to
>         be manual since that will put some end to registration spam.
>
>         I am open to other ideas to stop spam without locking registrations.
>
>         The registrations will still happen but should be done manually.
>
>
>     I don't have any problem w/ manual registration, but I do have a concern.
>     Manual registration often times becomes a black hole for people.  You send
>     off a request to get registered and if the one person, who in their spare
>     time monitors it happens to be on vacation for three weeks it just disappears.
>
>     If we do this, we need to come up with a way that a group of people can add
>     to the registered users.  Perhaps even allowing all registered e.V. members
>     to do it?
>
>     --Mark
>
>         Thanks
>         -Khem
>
>         _________________________________________________
>         Openembedded-devel mailing list
>         Openembedded-devel@lists.__openembedded.org
>         <mailto:Openembedded-devel@lists.openembedded.org>
>         http://lists.linuxtogo.org/__cgi-bin/mailman/listinfo/__openembedded-devel
>         <http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel>
>
>
>
>     _________________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.__openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.linuxtogo.org/__cgi-bin/mailman/listinfo/__openembedded-core
>     <http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core>
>
>




      reply	other threads:[~2013-01-09 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 15:59 locking down patchwork and wiki registrations Khem Raj
2013-01-09 21:55 ` Mark Hatle
2013-01-09 21:58   ` [OE-core] " Tom King
2013-01-09 22:12     ` Mark Hatle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50EDEB4B.1020009@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=ka6sox@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox