Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107955
To: Gabriel Caruso <carusogabriel34@gmail.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] "use global functions/consts" statement
Thread-Index: AQHVwNgGtev425C1jEaW2/fYCDQJoKfWQuWAgABJagc=
Date: Thu, 2 Jan 2020 01:37:45 +0000
Message-ID:
 <DM5PR07MB30676EF285944BE8BDEACCE0F9200@DM5PR07MB3067.namprd07.prod.outlook.com>
References:
 <DM5PR07MB3067B7578E3F04C5A20A221AF9210@DM5PR07MB3067.namprd07.prod.outlook.com>,<CAP=4hCK5-FR9=3aqODneACWu72e61K4vbsGyQjOVx02GAwp_Eg@mail.gmail.com>
In-Reply-To:
 <CAP=4hCK5-FR9=3aqODneACWu72e61K4vbsGyQjOVx02GAwp_Eg@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-CA
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [RtPZs+2RFbZ0oWcUUqbB+PoURdwqbi31EAs6wULdqQSyGshvY4e7g6Ti3tNH4HI8]
x-ms-publictraffictype: Email
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 00f89100-ffe3-49d9-3337-08d78f245dd1
x-ms-traffictypediagnostic: BN3NAM04HT124:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info:
 Uyc2nVppNTu2RVF5vP3fW4oBjoSPEJLnnYawRNwMDuto45/25nehmHr+M3IB9QgiCSyj3mz0guYSofB5/e7yU/iEdxcKNdecNStlWv9f8yoC8rnblvaRffQSMK5w/J/rLCTi7YdZjB0Tb/UtBNQ4ZujuJ829FAxgtgSOoO5/ipZH0484Yn19X/lkJvIYz1pfFi+N5eXkZT+M/5o4c8SZuywQ3cyh/vVV3AH0J170S40=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 00f89100-ffe3-49d9-3337-08d78f245dd1
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jan 2020 01:37:45.0505
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM04HT124
Subject: Re: [PHP-DEV] [RFC] "use global functions/consts" statement
From: tysonandre775@hotmail.com (tyson andre)

> Do you have plans to use the=A0https://github.com/php/php-rfcs to promote=
 the discussion as well, the same way=0A=
we did https://github.com/php/php-rfcs/pull/1 for the Typed Properties RFC?=
=0A=
=0A=
No, I have no plans to switch to GitHub. At the time of writing, https://gi=
thub.com/php/php-rfcs/blob/master/README.md has the following note about no=
t submitting PRs, so I decided against trying out the experimental RFC proc=
ess.=0A=
=0A=
> This is just a one-off experiment for now, we'll have to discuss whether =
we want to move the RFC process towards this separately. *This repository m=
ay be abandoned. Please don't submit PRs for now.*=0A=
=0A=
1. I'm not sure if there's a consensus on https://externals.io/message/1077=
47#107747 ("GitHub RFC workflow").=0A=
2. I expect this RFC to be smaller in scope (of discussion) than adding uni=
on types to the language.=0A=
=0A=
Other thoughts on "GitHub RFC workflow" (Sorry for this being off topic- I =
don't know how to reply to a mailing list thread I don't have in my inbox w=
hile preserving threading, from Outlook in a browser. The "In Reply To" hea=
der seems like what I'd want, but is impractical to set with this setup):=
=0A=
=0A=
- It seems slightly time consuming and error-prone for formatting (but doab=
le) to migrate from markdown to dokuwiki after the RFC is reviewed on GitHu=
b (I see this was already mentioned). Maybe publishing the dokuwiki markup =
as plain text, linking to the wiki, and having code review on that would be=
 a better option to write (but harder for reviewers unfamiliar with the dok=
uwiki format).=0A=
  Tooling (use pandoc or something else to convert from HTML (rendered by w=
iki) to markdown for the github PR) may help with that process - I'm not fa=
miliar with the best options. dokuwiki only has official support for export=
 to odt and xhtml, as far as I can tell=0A=
- If I linked to a GitHub PR as a secondary source of reviews to the email =
thread (instead of the main source), it might be splitting up the discussio=
n, and reviewers would miss or duplicate comments.=0A=
=0A=
Thanks,=0A=
- Tyson=