Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107298 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 97522 invoked from network); 23 Sep 2019 16:49:32 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 23 Sep 2019 16:49:32 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 1F6632CC68B for ; Mon, 23 Sep 2019 07:28:12 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Mon, 23 Sep 2019 07:28:11 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id s1so6993718pgv.8 for ; Mon, 23 Sep 2019 07:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iAt3EH+Zm1+FQWl08qF0sxgieng+84F5ljK5JLBVfJ8=; b=iOnvuzWvEJW9fYWOz02S5HwrEYfCOc+/1oTi/gvVz+gNZYmZlbvtv1rRTfojbYyr2g UlvQelJYztyjlIC5wLelW0DKa4Z2sJOY6zWUV5t6/ICH5U0gUdDAw9OGfw9a7aiJeWtx ACTx/KBZHk825IAZ8jFqSAhZf7eWYMNrrjLCtfa2LmUKNOnnFS0ySsta2bWZrpCkRuXs Cg/wOcwp/ItJeYfO70VJAa0u24fJcq2c9YkKSfDsEWjFVa0uawj/42WWV406brkZUPhu upBWyFcRzcz8FzmkYPOdau95TXrd9FKHWPNaCGUIFBZWQvFIqeqKzeyIoh1twoQwGV1+ GY6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iAt3EH+Zm1+FQWl08qF0sxgieng+84F5ljK5JLBVfJ8=; b=BgbDlu4Gf2Z27z6vg3HQV7KAy12NyeA+K/8VuXiiwkcqUIdZZyzJCtCXHbUoqL95km WtmPyecEH0IGPEJ9dExGFzzLIB5PdInH0JG+T4xDo6eDnBR6G9QNNpHna/7TiXKWfNkp XZkhh6mHhDJtJXlMbrgdthoMJZSAfNvGj+utIeCcSOO2hYf5tB+WsPieM7hclJFOvS65 w67Fl0WuP8l39sgGF5MMB1VX5FoKuhr7Q+o4MdczvVZP7tps0Oo3vCHAah9u7PjE7PlR JhXnYv2BSOKfbCf+1SqGVd6q1sMDwkPZqoROygk2AN5uiQP18tj1+X2R/H3IKx8JvAwj Lw1Q== X-Gm-Message-State: APjAAAVt7ykx3UrJNGgQyJiEUhPd6SWZzbfQ9cLoe4b2x7T9FDlOYYDt eZo/8xDF5vJ+5iKv668rTkItDtmr6vNJErZ23emesg== X-Google-Smtp-Source: APXvYqxzi1VWWT/z+3jbfo62geYw/0l7HfnmlJh5Bpr2vbkFB9vqLYv/5ZyrVbniik2qxNC7xCR3vIy/0FyFazbqDyg= X-Received: by 2002:a62:1955:: with SMTP id 82mr33490515pfz.256.1569248889983; Mon, 23 Sep 2019 07:28:09 -0700 (PDT) MIME-Version: 1.0 References: <24f5fac7-fafc-c4df-7521-683b56247f37@heigl.org> <2a91ef8a-fdf0-9cd7-ac50-c1ec511a0b83@gmail.com> In-Reply-To: <2a91ef8a-fdf0-9cd7-ac50-c1ec511a0b83@gmail.com> Date: Mon, 23 Sep 2019 15:27:59 +0100 Message-ID: To: Stanislav Malyshev Cc: PHP internals Content-Type: text/plain; charset="UTF-8" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Prevent disruptions of conversations From: Danack@basereality.com (Dan Ackroyd) Hi Stas, On Fri, 20 Sep 2019 at 19:36, Stanislav Malyshev wrote: > This has absolutely nothing to do with successful 7.4 > release. If from now on internals became so bad we could > literally agree on nothing, pass no RFCs, make no > decisions, etc. - we still could very well release 7.4 > without much trouble. You're right that 7.4 will probably come out, I remain concerned that fixing any bugs that are found during the release process, or inevitably those found after the 7.4.0 release occurs, would be more difficult if people are hesitant to discuss issues on internals. But your point is right, that wording was a commentary and not a required part of the RFC, so I have removed it. I've also added some words to help focus the goal on making conversations more productive, rather than addressing disruption. ---------------------------------------------------------------- # Guidance for 'disruption points of contact' People who are 'disruption points of contact' should: * focus on helping people understand how they are communicating could be disrupting conversations and/or making it hard for other people to have their voices heard. They shouldn't focus on suspending people. * avoid trying to address disruptions for discussions they are taking part in. It's really hard for someone to objectively think about someone's behaviour when you're also taking part in a discussion with them. * avoid acting rashly or unilaterally. Where possible the 'disruption points of contact' should talk through the situation and how best to handle it with at least one other 'disruption point of contact', before addressing it. ---------------------------------------------------------------- cheers Dan Ack