[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

branch master updated: doc: Add 2022-03-01 maintainers meeting notes.

From: Maxim Cournoyer
Subject: branch master updated: doc: Add 2022-03-01 maintainers meeting notes.
Date: Thu, 03 Mar 2022 13:11:46 -0500

This is an automated email from the git hooks/post-receive script.

apteryx pushed a commit to branch master
in repository maintenance.

The following commit(s) were added to refs/heads/master by this push:
     new f385394  doc: Add 2022-03-01 maintainers meeting notes.
f385394 is described below

commit f38539495555aad3da4b2c231bf3cd2073a2be04
Author: Maxim Cournoyer <>
AuthorDate: Thu Mar 3 13:06:25 2022 -0500

    doc: Add 2022-03-01 maintainers meeting notes.
    * doc/maintainers/meetings/ New file.
 doc/maintainers/meetings/ | 34 +++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/doc/maintainers/meetings/ 
new file mode 100644
index 0000000..13ed238
--- /dev/null
+++ b/doc/maintainers/meetings/
@@ -0,0 +1,34 @@
+* Maintainers meeting
+** Schedule
+The 1st of March from 14:00 CET to 15:00 CET on Jami.
+** Agenda
+No fixed agenda -- discuss an action to take.
+** Notes
+Meeting was held on Jami. Efraim, Maxim and Tobias were present.
+- Discussed the recent events and what action was appropriate from the
+  Guix maintainers.
+- Berlin file system migration status: awaiting on-site person
+  availability to try a reboot again.  There was a problem where the
+  devices would not be available at the time 'btrfs device scan' was
+  run by the init ram disk, which caused the root file system to be
+  mounted in a degraded state.  It is assumed this is due to our init
+  ram disk not supporting hardware events/synchronization.  Using
+  rootdelay=20 or alternatively passing the
+  'device=/dev/sda3,/dev/sdb3,/dev/sdc3,/dev/sdd3,/dev/sde3,/dev/sdf3'
+  mount option should be a workaround (which can now be changed easily
+  via the rootflags kernel option from the GRUB interface).
+*Action* Draft and send an official statement regarding recent events.
+*Action* Update our Code of Conduct copy the latest version.
+*Action* Add a notice at the top of the Code of Conduct mentioning
+issues pertaining to it should be brought up with the maintainers, not
+in the other public Guix communication channels.
+*Action* Turn any release-related past (uncompleted yet) actions into
+ Debbugs issues tagged as blocking the 1.4.0 release issue (#53214).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]