On 09/22/2017 09:28 AM, Andrea Bolognani wrote: > While the "autoconfiscate" name is very clever and cute, the > de-facto standard name for this kind of script is "autogen", and > deviating from it means having to special-case the libvirt-cim > project when, for example, setting up a CI environment. > > Signed-off-by: Andrea Bolognani <abologna(a)redhat.com&gt; > --- > README | 2 +- > autoconfiscate.sh => autogen.sh | 0 > 2 files changed, 1 insertion(+), 1 deletion(-) > rename autoconfiscate.sh => autogen.sh (100%) > libvirt-cim has it's own mailing list (libvirt-cim(a)redhat.com) and achives: https://www.redhat.com/archives/libvirt-cim/index.html. The last email there (april 2015) and last patch (aug 2014) - I venture to say perhaps the "doesn't anyone really care" starts to factor in. Then of course, is there a way (need/desire) to kill it completely?

On Fri, 2017-09-22 at 17:17 +0100, Daniel P. Berrange wrote: >> libvirt-cim has it's own mailing list (libvirt-cim(a)redhat.com) and >> achives: https://www.redhat.com/archives/libvirt-cim/index.html. >> >> The last email there (april 2015) and last patch (aug 2014) - I venture >> to say perhaps the "doesn't anyone really care" starts to factor in. >> Then of course, is there a way (need/desire) to kill it completely? > > IBM was the only company that ever cared about CIM for virtualization. > Everyone else wanted an API that was easy to use instead ;-P Even IBM > has lost interest now, so it is mostly a historical curiosity at this > point. I wouldn't delete it, but also wouldn't spend alot of time in > it. If someone does have a desire to update the code in any way, go > at it and we can review it in the normal manner - no point waiting for > the original maintainers to review IMHO. I'm pretty sure John was referring to the mailing list, not the project itself :)

On Fri, 2017-09-22 at 12:58 -0400, John Ferlan wrote: > By killing it - I was thinking more along the lines of removing it from > our CI infrastructure and just letting the repo sit silently without > updates, but that ship sailed today. We could still remove it from the > CI mix as if something breaks - there's not going to be anyone that > really wants to fix it. Well, there hasn't been a single release since 2013, and any actual development since 2014... Maybe it's really time to move on and free up some cycles for the CI workers, especially since there are going to be more jobs running on there pretty soon.

The first patch will make it possible to have a nicer CI setup. The second one is just something that I couldn't help fixing while preparing the first one :) Andrea Bolognani (2): maint: Rename autoconfiscate.sh to autogen.sh README: Point to git repository README | 9 ++++++--- autoconfiscate.sh => autogen.sh | 0 2 files changed, 6 insertions(+), 3 deletions(-) rename autoconfiscate.sh => autogen.sh (100%)