Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90808 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19709 invoked from network); 21 Jan 2016 21:24:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2016 21:24:30 -0000 Authentication-Results: pb1.pair.com header.from=ronabop@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ronabop@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.179 as permitted sender) X-PHP-List-Original-Sender: ronabop@gmail.com X-Host-Fingerprint: 209.85.217.179 mail-lb0-f179.google.com Received: from [209.85.217.179] ([209.85.217.179:35316] helo=mail-lb0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/42-09073-D8C41A65 for ; Thu, 21 Jan 2016 16:24:29 -0500 Received: by mail-lb0-f179.google.com with SMTP id bc4so30705983lbc.2 for ; Thu, 21 Jan 2016 13:24:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qirLl2q+W2RlohMyGtSd8XQQSK2+c/8MlJYme+hLMz4=; b=EmRcRSSKHayg5ENwEHD6+1cDL4gmUazFw38LSH7aNpNq3ch5hFumySYtamkbCaum1W DcUEBQms1hWWEv51NNmS9iqQe6LrLCkMHWyBZ4233RRnSYNNT4NMMfFXyOSBcRYeW35A Ag/kcO1yGM0JrzXvJnl+LfKjp4pfN5A5W+NwsAHpIfhy9MDJA8wpDWOCv5Cvpeib+OuD yzfucyiMkUitTpfzbxC6KG9PPIKUazRUBOTicwj+e8hOMpWOz4ozH4CzWU0iqd4BrUhF AgjyZrvvAZfYEKMV+aUjXxtwjzI54lcx6SDnDvBIzF+CyoqOUSxBQKr2j8BtFd2I+3o9 A7Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qirLl2q+W2RlohMyGtSd8XQQSK2+c/8MlJYme+hLMz4=; b=fPWaGo7nOhTq+GryXEaa4MXNy5FYxUkbG8olbV/b3R3XWghAPj56ux590pLXdEMT/J B4Ou6+LYmoondc1oNmiQhC825dFZUhGkqFcZPLYAHYwRHRLCTeLvu7cWClGqNuTVTLy4 UDzeSX2H1mryFU77eox4ldMpjl/Y49KyDt/eNM5G61R6PuxMvvYhRJlFLXDeblxUjV8I +mFCZaKnZlkbtLkZmAM3xCdE2+2hvvqABiHvFqbrj7TCZuzlNyC+1g1Zx4d7JcIZ9RhP LunLgcPeT0xssCS+x3MsidDbTlBnrGnSreLTGmtQ3TZ/6JoWNap7DoZaPSzsRr3VJ4Xm ll/g== X-Gm-Message-State: ALoCoQli+mBJ9qODPv0blRjx4o0dojach6qKiZmXDobzVGd3Hl9EgfDynjl+lgcMqmM57sWbw6+7TRKPngmIb+AnzD6+l3e4Eg== MIME-Version: 1.0 X-Received: by 10.112.61.226 with SMTP id t2mr16860540lbr.33.1453411465896; Thu, 21 Jan 2016 13:24:25 -0800 (PST) Received: by 10.114.172.16 with HTTP; Thu, 21 Jan 2016 13:24:25 -0800 (PST) In-Reply-To: References: <59.F0.09073.49041A65@pb1.pair.com> Date: Thu, 21 Jan 2016 13:24:25 -0800 Message-ID: To: Peter Lind Cc: Flyingmana , internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Handling of withdrawn RFCs From: ronabop@gmail.com (Ronald Chmara) On Thu, Jan 21, 2016 at 12:59 PM, Peter Lind wrote: > On 21 January 2016 at 21:53, Ronald Chmara wrote: >> On Thu, Jan 21, 2016 at 12:33 PM, Flyingmana >> wrote: >> > Is there any way to abuse the taking over of an withdrawn RFC? Snip_> >> An RFC being used primarily for ongoing debate/argument/trolling >> purposes could live indefinitely, generating hundreds, or thousands, >> of messages, and changesets/PR's, and list churn, in the name of >> "making sure an issue is adequately discussed and resolved". >> Even as individual trolls, marks, and sockpuppets were knocked down, >> new ones could pick up the mantle of "but we're discussing important >> things, here!", and continue the loop... Snip_> > This thread being about withdrawn/re-proposed RFCs, how is that comment > relevant? The relevance is in ways to "abuse the taking over of an withdrawn RFC". > Seeing as anyone wanting to debate/argument/troll indefinitely can > do so using their own RFC - Creating a new RFC has a higher barrier to entry, requiring additional effort. > or, for that matter, without an RFC. I would suggest that random email trolling does not have the same audience, impact, or formal trappings of a public RFC process. -Ronabop