commit: e11343080f7df31dbbddb5643f2e4d52532f1ff2 Author: William Hubbs <william.hubbs <AT> sony <DOT> com> AuthorDate: Thu Jan 23 18:19:26 2020 +0000 Commit: William Hubbs <williamh <AT> gentoo <DOT> org> CommitDate: Thu Jan 23 18:22:42 2020 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1134308
sys-cluster/kubeadm: take maintainership I was advised that the proxy maintainer no longer has time to maintain this. Signed-off-by: William Hubbs <williamh <AT> gentoo.org> sys-cluster/kubeadm/metadata.xml | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/sys-cluster/kubeadm/metadata.xml b/sys-cluster/kubeadm/metadata.xml index 6833440b374..acebd7ff79e 100644 --- a/sys-cluster/kubeadm/metadata.xml +++ b/sys-cluster/kubeadm/metadata.xml @@ -2,23 +2,19 @@ <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd";> <pkgmetadata> <maintainer type="person"> - <email>[email protected]</email> - <name>Dan Molik</name> - </maintainer> - <maintainer type="project"> - <email>[email protected]</email> - <name>Proxy Maintainers</name> + <email>[email protected]</email> + <name>William Hubbs</name> </maintainer> <longdescription lang="en"> - kubeadm performs the actions necessary to get a minimum viable cluster up - and running. By design, it cares only about bootstrapping, not about - provisioning machines. Likewise, installing various nice-to-have addons, - like the Kubernetes Dashboard, monitoring solutions, and cloud-specific - addons, is not in scope. + kubeadm performs the actions necessary to get a minimum viable cluster + up and running. By design, it cares only about bootstrapping, not + about provisioning machines. Likewise, installing various + nice-to-have addons, like the Kubernetes Dashboard, monitoring + solutions and cloud-specific addons is not in scope. Instead, we expect higher-level and more tailored tooling to be built on - top of kubeadm, and ideally, using kubeadm as the basis of all deployments - will make it easier to create conformant clusters. + top of kubeadm, and ideally, using kubeadm as the basis of all + deployments will make it easier to create conformant clusters. </longdescription> <upstream> <remote-id type="github">kubernetes/kubernetes</remote-id>
