Closed thaJeztah closed 1 year ago
@AkihiroSuda @arkodg @cpuguy83 @mavenugo @tonistiigi @tianon PTAL
FWIW; I don't expect massive redesign/refactors to be done in this repository, but having more people to allow us to review/merge pending fixes / low-hanging fruit / safe-to-merge PRs at least allows us to move things if needed.
What's current status?
+1 to this
since its been years since Ive contributed on this project and spend cycles on it, prefer if I was removed (and moved into a emeritus
section), can raise a separate PR to do so
Thanks @arkodg! I considered asking the old maintainers to step down, but also considered that this repository will be archived once 20.10 fully reaches end of the line (I know Mirantis still continues support for their LTS runtime, and perhaps Azure (@cpuguy83 would probably know)).
With that in mind, I didn't want to spend too much time on that. (In short: I'm fine with the old maintainers to continue to be listed, but of course also happy to accept PRs for those that want to step down!).
(Should I mention the 3rd option? pst: we're hiring, and I'd be happy to have you on my team ❤️ 🤗 )
I'll be going ahead and bring this PR in; we discussed this in our maintainers call, and this change is mostly to allow us to backport changes from moby/moby (where the libnetwork code was moved to).
I'll send out an invite to those who were added (@akihirosuda @tianon @tonistiigi @vvoland @neersighted @rumpl @corhere @cpuguy83)
The current list of maintainers is quite outdated, and we plan to integrate libnetwork into the main Moby repository.
Before doing this, we may still need to review and merge fixes that are pending in this repository (as well as maintain a branch for the 20.10 release until it reaches EOL).
This patch adds some of the (currently) active maintainers of the moby project to the maintainers list.