Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:122015 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 52625 invoked from network); 19 Dec 2023 10:26:50 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 19 Dec 2023 10:26:50 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 09B8C180051 for ; Tue, 19 Dec 2023 02:27:11 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DMARC_MISSING, SPF_HELO_PASS,SPF_NEUTRAL autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) by php-smtp4.php.net (Postfix) with ESMTP for ; Tue, 19 Dec 2023 02:27:10 -0800 (PST) Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 9F21910C24D; Tue, 19 Dec 2023 10:26:48 +0000 (GMT) Date: Tue, 19 Dec 2023 10:26:48 +0000 (GMT) To: Jorg Sowa cc: PHP Developers Mailing List In-Reply-To: Message-ID: <133a5f7d-11a8-9afa-fdde-aee5784c99c9@php.net> References: <21ed7837-3cd4-98e5-8ec7-c97b0e2a2146@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: Re: [PHP-DEV] [RFC] Collecting All Policies Into One Repository From: derick@php.net (Derick Rethans) On Mon, 18 Dec 2023, Jorg Sowa wrote: > I have one question regarding the future changes. Do you see it would > be possible to make amendment to the accepted RFCs by the Pull > Requests (and formal RFC approach) making changes the existing > policies or adding the new policy replacing the old ones? In other > words, this repository would server as the collection of all ever > accepted policies or it would contain the unified policy > documentation? It should contain the consolidated unified policy documentation that is "currently" active. The other option is what we currently have, and I am proposing to go away from. So the idea is that this repository is not a collection of the accepted policy *amendments* (or *replacements*), as that's what the RFCs / PRs are still for. > I'm asking because I saw the directory `archive`, and it contains > expired RFC. I don't think this would help new contributors. For the > history purposes it would be nice to have it in the git history, but > for the PHP development process is not relevant anymore and is little > overhead. I didn't really know what to do with these documents in archive, as they were sortof related to the release process/timeline document. I suppose we don't need them, but they are not *wrong* or *outdated*. Simply no longer needed as the time frame has passed. cheers, Derick