Hey all, I'm looking into cleaning up the cross-project spec reviews. The following appear to be inactive specs and need the original author to revive and eventually propose for wider discussions in the cross-project meeting [1], or someone that's interested in leading the spec needs to communicate with the current author on taking things over. Otherwise I will be proposing to the TC to abandon these: * Stop running testr in the environment under test (robert Collins) - https://review.openstack.org/#/c/218070/ * Replace eventlet + monkey-patching with ?? (Joshua Harlow) - https://review.openstack.org/164035 * Super Scheduling (Joshua Harlow) - https://review.openstack.org/#/c/210549/ * Backwards compat for libraries and clients. (Robert Collins) - https://review.openstack.org/226157 * Event message format (Thomas Therve) - https://review.openstack.org/231382 * Instance users for cloud interaction (Kevin Fox) - https://review.openstack.org/#/c/222293/1 * DNS and SSL certificates (Kevin Fox) - https://review.openstack.org/#/c/228074/2 * No global admin (Adam Young) - https://review.openstack.org/#/c/205629/ * OpenStack wide error codes for log messages (Rochelle Grober) - https://review.openstack.org/#/c/172552/5 * Add asynchronous user event support to OpenStack (Angus Salkeld) - https://review.openstack.org/#/c/185822/2 ---------------- This spec needs someone to take lead in the cross-project meeting: * Instance Auto Evacuation (Timofey Durakov) - https://review.openstack.org/#/c/257809/2 ---------------- This spec needs someone technical to fill in the gaps. Keep in mind this spec should just cover the concept of rolling upgrades the projects should follow. Projects can still do individual specs in their spec-repo to discuss technical details around their specific services. The point here is to agree on the concept and already existing solutions to solve the problem: * Rolling Upgrades (Ken Johnston) - https://review.openstack.org/#/c/290977/1 -- Mike Perez