Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106898 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 66635 invoked from network); 6 Sep 2019 16:05:31 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 6 Sep 2019 16:05:31 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 9ECC62C0457 for ; Fri, 6 Sep 2019 06:39:55 -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=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (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 ; Fri, 6 Sep 2019 06:39:55 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id x4so12695199iog.13 for ; Fri, 06 Sep 2019 06:39:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=tr+cQrEy0Ssd0w3x6T6ylN6A3AlhtmnJppfsDfrypkw=; b=LQShTSNBqYdsWj0twJHmL+p1xFuAKoNMHtCd8wmreloqosID85ebNx6fx0XsnmPFdr 6lwLVA0FDoGTvou2ohNkjyaZ8WShVN8JP5lWv37RzCMfcwbLQv1b6KEwpGPsx8gmohgE 5JK1DAAzS5NnGvK/vdeJQ2NnZwzqz1wKqlwDTTF3+Pl9TAO7o8wjR6ESfihzlCzCc3ID qvfUPlWqZpwhl6lcCTKQn2py+zTCdsD5gOHy3wRW4VNi9dfKLASAMRMUB3h3Ljx/SWrn uzvhqUwTcKz0EDIUwXbj3Sl0zpGLihVwNGk0BBLKgPx6aAIevA5akEWHnW/aWYAsWl1g LukQ== 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; bh=tr+cQrEy0Ssd0w3x6T6ylN6A3AlhtmnJppfsDfrypkw=; b=D48B5emu20vRXPIDJruK5TGgnNjATh/DyzGUTEVBvxBQMvQSiAeR4uVCMh0b+tNYSR r/kyG8HC1nxP3g6X3tCUoCvPPwCHWEVIxA5gIr3x7eGgnazGUyRiE5E4n0yWzMO7saUx +93RTpK+S7jxRk7eL7YXWT4BOYRehY2p4iUv6FZeQ0J9p9BjG/m2x6THp5aWNVGPXDkV 1E2FyH/mObFl0KydMxSCDoOLqRm50JdNR7pBDr1Pbo4ECkJdWCX0Wp0KQFeWuVEB4vnD Ls09x4gunZEd+NJQZ+T9WYnIrddXL4pQoNm249H2G8LfZm1B8INzrX3Up7aKcmBaNAi6 M6TQ== X-Gm-Message-State: APjAAAUyzABoqUeh+u/1UTE0lqJlhYrrTS54eolCSbsemioxF9OBn626 XSQdw4V8+yM5nYvtdWKW0zCPFX1n6stKFoKhrnQ3NWab X-Google-Smtp-Source: APXvYqzlBHZA/2Cc15jEhTwuPbXezDZuj5FTs2D8FebOmIsZXstRP0TMkItYNxSNFszMdVjIi7Q85p3O7i1rj9GI2wE= X-Received: by 2002:a05:6602:25d3:: with SMTP id d19mr10638110iop.206.1567777194356; Fri, 06 Sep 2019 06:39:54 -0700 (PDT) MIME-Version: 1.0 References: <1686643.PblvKQRnJp@mcmic-probook> <190b7291-812e-4337-bd09-950dc30c655a@Spark> <2157489.0uZv62oTo4@mcmic-probook> In-Reply-To: Date: Fri, 6 Sep 2019 14:39:43 +0100 Message-ID: To: Internals Content-Type: multipart/alternative; boundary="000000000000c1b4170591e292a7" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Union Types v2 (followup on github usage) From: rowan.collins@gmail.com (Rowan Tommins) --000000000000c1b4170591e292a7 Content-Type: text/plain; charset="UTF-8" On Fri, 6 Sep 2019 at 14:14, Benjamin Morel wrote: > As a code collaboration platform, GitHub is pretty good, but it's not built >> as a discussion forum, and there are plenty of limitations to using it as >> one. > > > Could we work on agreeing on a set of requirements for such a discussion > "forum" to replace mailing lists? > That could be an interesting exercise, yes. Ideally, we should consider RFC drafting, voting, and bug tracking as well - not because we have to replace all of them with one platform, but because we might want to divide things up differently from how we do at the moment. > Using GitHub Issues as a starting point, what would you change? > That's pretty much the opposite of your previous question. For one thing, it's unanswerable without knowing the scope - e.g. would it just be for RFCs, or all discussions? Besides that, if we're going to introduce an anchor that we compare everything to, surely we should say "using the setup we have as a starting point, what would you change?" Until we know what we're looking for, I'm really not clear why GitHub issues should have any starting advantage over Discourse, or PHPBB, or Trac, or Phabricator, or Bugzilla, or probably hundreds of suggestions we could evaluate. Regards, -- Rowan Tommins [IMSoP] --000000000000c1b4170591e292a7--