Hi Ludo, On Sun, 16 Feb 2025 at 17:41, Ludovic Courtès <l...@gnu.org> wrote:
> I’ll be formally posting GCD #002 soon (“Migrating repositories, issues, > and patches to Codeberg”) As discussed elsewhere [1], we need a GCD process in order to amend Accepted GCDs without running a complete dance. My question is: Do you plan to start the process about Migration before the end of February? If the answer is yes, cool! And I delay a bit this GCD about amendment. If no, I kick myself and structure my procrastination for the end of this week. ;-) Obviously, the order does not matter much. Somehow, I would like to avoid to have too many GCDs under discussion in the same time – two \o/ are already open. Our love is infinite, not our attention. ;-) Cheers, simon PS: For one example of amendment, let imagine we would hypothetically change these two parts of GCD 001: --8<---------------cut here---------------start------------->8--- 1. Clone https://git.savannah.gnu.org/git/guix/guix-consensus-documents.git --8<---------------cut here---------------end--------------->8--- replace that by another location and --8<---------------cut here---------------start------------->8--- ## Communication Channels - The *draft* is sent by email to `guix-devel@gnu.org`. - Once *submitted*, the GCD is announced to `info-g...@gnu.org` and discussed using the assigned issue number. - The *final* document is published to `info-g...@gnu.org` and the deliberating replies are sent to the assigned issue number. --8<---------------cut here---------------end--------------->8--- replace info-guix by a dedicated mailing list. Therefore, we need a document to clarify how to process. :-) 1: GCDs on info-guix? Ludovic Courtès <l...@gnu.org> Fri, 21 Feb 2025 12:22:07 +0100 id:87r03r8rvk....@gnu.org https://lists.gnu.org/archive/html/guix-devel/2025-02 https://yhetil.org/guix/87r03r8rvk....@gnu.org
