Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22068 invoked from network); 21 Jan 2016 21:33:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2016 21:33:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=peter.e.lind@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=peter.e.lind@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: peter.e.lind@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-wm0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:33597] helo=mail-wm0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 58/A2-09073-29E41A65 for ; Thu, 21 Jan 2016 16:33:07 -0500 Received: by mail-wm0-f42.google.com with SMTP id 123so191365599wmz.0 for ; Thu, 21 Jan 2016 13:33:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qqkvCnvtAf4EVBVn/DcjcBpihJdo29MzGvg53aElAmM=; b=WREk7yz698IfZE8U+ibVVnXEcC7NtmwilLDfjdl/RdGSZH7sK3LRzcy+9aGbzQe4yY 2epH0NcrYhQnuUI0ZFG5wFZNRLP/WfFK7Wk9pWN4D7X0Rg8IaRIrtTKRC2geNzyL4W5j M8gZCOhxP0ElCFrzHuW5BrygUkKGxwp30cAlhXPnw3+xqyKkekWZethJqEVNVDgYTMLS mR0rqq/eNJ2MFnvq+tRVF3qZ/qYBE8QFC920Ok9+k9jLDALvroJZ/IA/DLIcnIxrMYl/ rdsZYlvh45cGL/7Nt799PcpieT8x0n2Y4f0CSdWsljEWqAI2+M2esTDIOkcS9vpQ4VHM 3fKg== 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:from:date :message-id:subject:to:cc:content-type; bh=qqkvCnvtAf4EVBVn/DcjcBpihJdo29MzGvg53aElAmM=; b=JRC9vBT+JzoYetbLHkRAH/Mlzp7Hz08uGWCJ4ytLeNT4k6D5HQYzztOK4mQ/0Rnn8G 5umwd9PUL5zrlbXIozYMmMOzvWzLrIKCQ/B9izzM5qJnl/Hzq+COBSk/Klk3AT3h1wNd 7SPO1//oQttsQv7jles4PjtEOkEr//0cFLCaak+EOsnR77jXpBGS/Fm0GPXLZVDpB+kS VMF+XcJ7Tj/R2k4obAYj8jKbdq0CkX7LxC0HIYFuCRKrRJM9m6RYf5fWsqbsbA0jnnOA kcCzSGTo1nYpb618G/X1NR7nswxVXMz3pKm64D5NJmK8aop4IsjhzTbWzNQnEZzY5GWw YHyw== X-Gm-Message-State: AG10YOT25+T+/3AI0IjZw07PZCb7V0lcZjg9i3l89kF1Fyw7DngVMBFQjR2xawqCOAXJ0MUQOlTqnYaxqdn4qA== X-Received: by 10.28.136.148 with SMTP id k142mr13224243wmd.41.1453411984405; Thu, 21 Jan 2016 13:33:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.28.41.132 with HTTP; Thu, 21 Jan 2016 13:32:44 -0800 (PST) In-Reply-To: References: <59.F0.09073.49041A65@pb1.pair.com> Date: Thu, 21 Jan 2016 22:32:44 +0100 Message-ID: To: Ronald Chmara Cc: Flyingmana , internals Content-Type: multipart/alternative; boundary=001a11444b580afd1c0529ded948 Subject: Re: [PHP-DEV] Handling of withdrawn RFCs From: peter.e.lind@gmail.com (Peter Lind) --001a11444b580afd1c0529ded948 Content-Type: text/plain; charset=UTF-8 On 21 January 2016 at 22:24, Ronald Chmara wrote: > 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". > > Ahhh good point, missed that. > > 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. > > If your aim is to clutter the mailing list indefinitely, that's really not going to get in your way. > > 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. > > Random email trolling, no. But then again, random email trolling is not really what we're talking about, is it? Plus, it's a mailing list, not a forum. The default is that you follow every thread, and have to actively mute them. Email trolling by splitting off of threads would actually be more effective than keeping to one RFC thread - not less effective. Regards Peter -- WWW: plphp.dk / plind.dk CV: careers.stackoverflow.com/peterlind LinkedIn: plind Twitter: kafe15 --001a11444b580afd1c0529ded948--