Re: GitHub RFC workflow
| From: | Côme Chilliet | Date: | Tue, 05 Nov 2019 08:38:31 +0000 |
| Subject: | Re: GitHub RFC workflow | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-107753@lists.php.net to get a copy of this message | ||
Le samedi 2 novembre 2019, 19:40:56 CET Joe Watkins a écrit :
> I would like to question the reasoning behind wanting to "own" the RFC
> content: We don't require any such thing for any other kind of PR although
> we say we require a patch on bugsnet, we actually don't require it. So, I
> have a hard time telling the difference between a PR for an RFC and a PR
> for a bugfix or enhancement.
>
> Can anyone tell the difference ?
Whether there is a difference or not, «we already use too much github» is not a reasonable
argument for «let’s use more github».
It would of course be better if the PRs were not done through github, but as far as I know this is
not mandatory and people are allowed to do PR through other systems.
I’m still strongly against using github for RFCs, and missed most of the discussion on union types
because it was there and hard to follow (things are not chronological, I can’t know easily if
there are new comments and which ones are, usability is not the reason I’m against github but it
was also bad).
--
Côme Chilliet
FusionDirectory - https://www.fusiondirectory.org