Plans, yeah, but not had any time to really look into it. We use minio in a very narrow way on our side, only to provide a basic S3 API on top of a regular filesystem and only in single mode. So we really just need to get an equivalent solution, either through one of the alternatives, or preferably just in-house as a S3 API exposed directly from the Go code.

Plans, yeah, but not had any time to really look into it. We use minio in a very narrow way on our side, only to provide a basic S3 API on top of a regular filesystem and only in single mode. So we really just need to get an equivalent solution, either through one of the alternatives, or preferably just in-house as a S3 API exposed directly from the Go code.

adamcstephens: regarding joining the LXC Team. There also is the following file: https://github.com/NixOS/nixpkgs/blob/f7f03dc67634247eb6787f664a6987c288b2da08/maintainers/github-teams.json#L610-L623

This looks like the newer way of handling team membership. So just joining/leaving via github and then a sync PR takes care of the rest.

Hoewer, for this to work i think the following change would be required:

diff --git a/maintainers/team-list.nix b/maintainers/team-list.nix
index bad67fd029fe..99d7727a4ab8 100644
--- a/maintainers/team-list.nix
+++ b/maintainers/team-list.nix
@@ -485,14 +485,7 @@ with lib.maintainers;
   };
 
   lxc = {
-    members = [
-      aanderse
-      adamcstephens
-      megheaiulian
-      mkg20001
-    ];
-    scope = "All things linuxcontainers. Incus, LXC, and related packages.";
-    shortName = "lxc";
+    github = "lxc"
   };
 
   lxqt = {

But this is just my current understanding of it and there might be further differences and considerations.

@adam:robins.wtf: definitely still a big user of lxd but of course as you said not maintaining

the issue is... i really appreciate getting email about all the PRs ... i wish there was a way to subscribe!