Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106883 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 70418 invoked from network); 6 Sep 2019 00:11:21 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 6 Sep 2019 00:11:21 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 5FF662D2067 for ; Thu, 5 Sep 2019 14:45:35 -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,URIBL_BLOCKED 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-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 ; Thu, 5 Sep 2019 14:45:34 -0700 (PDT) Received: by mail-io1-xd31.google.com with SMTP id m11so8266170ioo.0 for ; Thu, 05 Sep 2019 14:45:34 -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 :cc; bh=KSK9Ee9yKG76nYInY3UDs/F7PbWJN0QAwfwbCz2883w=; b=YtVkSJyqjhMVVWZ+4ijCnCgGEOQTwxNxYBTPVHz5EQgZD9NIUFx7bdYOCwFyE02Tec /r/AkL7kh5wcBMeyBrDdAYyyxMvUfNLWux6vuSEr/bgVf6XWOaRgG/Zx13W6LTpbtD9/ /Tru+84ShycF7mR4KFLOM0VEuMCnWVU1DBA/vhiNtZTBo+cDdH5JgVu7QdzrQ5SZwq6f Uvb2C5FN0j1ZOSfl63tkpKoer6BPfOZf+Bw/BGwM7Hm7qhVYJb8F2oxddvXUrzfMy2vL BZh3Q1UFwUUekhcB5NWzXhrAZmxuUvZoGSpTrs/W+muWiqInII5dVGgKNXNpN6kPSQpI VOKQ== 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=KSK9Ee9yKG76nYInY3UDs/F7PbWJN0QAwfwbCz2883w=; b=e4THeEfIg9Kq++N+GUw7CoWtmdzjQv5JTTyYDKqJUeV6F0RQjwICtFVCMNGfFDInfD CKVqOoY3jNWF1tIrW4zocTVZsN17d27FLMudRnYnsnofuc5TtfQGy70UVviqWgZbBtGb oZAbmbDTJ/ofhfTUottf8+nPrrgcU+r2gzmbuKgG1+7Lse85Ro6CjSOANloUwrhk0Br7 kSy8AQk1X9qvXqHmNgYUF+LJoAY1lqUvxsiPYeEpO7xn7Lg44scDZ7I7nMK3r7FiajGG TqKd/ZaReNTKu0Y3slfrmp4jG9xkQk/4q0U8b2sw8A9E63TNJTMS4w9dQ4B+TKMgwA/f XoKQ== X-Gm-Message-State: APjAAAWC/UP1bcdb4k4SdLWb4+15mlwn4YpF3hGdncR5LwN6s1PaQKn2 LhwjfNuU6VydbtsVbFrSPQNfZ5U3tVTWrCPmpVA= X-Google-Smtp-Source: APXvYqwrFqIB1yTqnz5bQjEEBpVDrOGz2lR8DFpMSqa/TEEBVhaVnhWklaljP3AXopozG3Hl4DEDCX12Hk10sfdDUJs= X-Received: by 2002:a6b:8d09:: with SMTP id p9mr6990337iod.176.1567719934067; Thu, 05 Sep 2019 14:45:34 -0700 (PDT) MIME-Version: 1.0 References: <1686643.PblvKQRnJp@mcmic-probook> <190b7291-812e-4337-bd09-950dc30c655a@Spark> <2157489.0uZv62oTo4@mcmic-probook> <5d70fa17.1c69fb81.3b882.827eSMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Thu, 5 Sep 2019 23:45:21 +0200 Message-ID: To: Rowan Tommins Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000c708b80591d53d1c" X-Envelope-From: Subject: Re: [PHP-DEV] [RFC] Union Types v2 (followup on github usage) From: benjamin.morel@gmail.com (Benjamin Morel) --000000000000c708b80591d53d1c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I've thought about this many times while reading messages on internals, but from another perspective: the inability to "+1" a message without having to reply. I very often find myself agreeing (or disagreeing) with someone, but refrain myself from posting a one-liner to show my support. Having something like GitHub reactions to be able to "+1" or "-1" a message could be invaluable to get the overall sentiment of the participants (even the silent readers) when browsing through the thread. When I browse an issue or a PR on GitHub, the reactions help me quickly see which messages stand out of the crowd, be it positively or negatively, and usually help me get quickly a good idea of what's going on there, when I don't have the time to read through every single message. IMO, replacing the mailing list with a GitHub-like discussion would bring several advantages: - no more top-posting, etc.: this would be a web app, not a dumb email software that (sometimes unreliably) quotes everything by default. - possibility to use markdown: invaluable to make a message more readable - possibility to add reactions to messages, even from silent readers - possibility to react to previous messages, for someone who just joined the list, without having to invoke ezmlm black magic Also, I think this would lower the level of entry to internals for a lot of PHP developers who aren't otherwise interested in participating in discussions, but could appreciate being able to give their opinion on the future of PHP. And for maintainers, this would represent invaluable feedback to see the sentiment from the crowd, not only from the usual suspects. Externals.io does a pretty good job, but suffers from many drawbacks that can hardly be solved: - it's still reading emails, so while it does a good job at putting everyting together quite nicely, it's sometimes confused by the syntax, especially quoting - you can vote on threads (stackoverflow-style), but not on individual messages; and because externals.io is not everyone's main way of reading through internals, this lowers the number of potential reactions - there is no way to reply to a message, you have to get back to your email - there is no real support for markdown; a few things are supported, but I find them quite unreliable and am never really happy with how my hand-crafted message looks over there Ideally, we could create a custom web app to move the discussions to. I'd love to participate in creating it, even initiate the project, if time permits. This would also allow adding interesting stuff, like user statistics, user post history, etc.) Finally, regarding GitHub, I'm personally not against moving the discussions there; I'm using it every day and find it very convenient to discuss software; I do understand the concerns expressed above though. One thing that could be checked, is whether their API allows retrieving the whole discussion history programmatically. If so, one could setup a database to sync all messages to on a regular basis, so that the PHP project could move the discussions back to their own system should something bad happen. =E2=80=94 Benjamin --000000000000c708b80591d53d1c--