There are at least two things that make this project not for me: I don't need more etcd in my life: https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#

There are at least two things that make this project not for me: I don't need more etcd in my life: https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#why-did-you-use-etcd-what-about-consul https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#w... (and then, as if to drive home my point, they even have a separate FAQ entry for "etcd shit itself, what do" https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#on-startup-mgmt-hangs-after-etcd-server-starting https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#o... ) There is lot of noise about tracking upstream tip branches for dependencies as justification for not using go.mod (https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#why-arent-you-using-glide-godep-or-go-mod-for-dependency-management https://github.com/purpleidea/mgmt/blob/0.0.21/docs/faq.md#w...) but then vendoring a docker fork from 2018 (https://github.com/purpleidea/mgmt/blob/0.0.21/.gitmodules#L27 https://github.com/purpleidea/mgmt/blob/0.0.21/.gitmodules#L...). As best I can tell the submodules commits haven't moved since April. So, rather than use go.mod like a modern golang project, it forces one to use the old GOPATH setup just cause