<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 8, 2020 at 6:08 AM Caleb Maclennan <<a href="mailto:caleb@alerque.com">caleb@alerque.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>And before anybody chimes in, yes I'm aware there are yet more namespaces already floating around on launchpad. There is a "crosswire-misc" project, a "~pkg-crosswire-devel" team, and half a dozen "xiphos-something" projects users have spawned building their own PPAs. I would ignore all the bits except the ones I mentioned before and gradually hope to cleanup/consolidate/obsolete them in favor of clearly named canonical namespaces for the various resources.<br></div><div><br></div><div>I also forgot to mention my third recommendation: the least disruptive solution(s) possible are to use the existing "xiphos-devel" or "pkgcrosswire" team team space and add a new PPA (either "xiphos-devel/ppa" or "pkgcrosswire/xiphos" and setup packaging there. No renames to existing launchpad stuff, just a new new fresh PPA and leave the existing archaic Crosswire PPAs to be cleaned up later.<br></div></div></blockquote><div><br></div><div>I would say don't re-invent the wheel, and don't try to rename it to "round rolly thing", either. Use pkgcrosswire, as ugly as that might be to us. It has history, I believe it's where packages have long been held. Follow the KISS principle.</div><div><br></div><div>--Greg</div></div></div>