Hi ! So yeah, as Dmitriy stated, Mistral is not an inactive project, I'm the current PTL. Even if the project doesn't evolve a lot, we keep it working with new OpenStack releases, don't let the version named 2015.1.0 fool you, there is a 18.0 release for Caracal. I also know it is used by some companies, we do here at OVH use it as a core component of our self healing, hence why we (on my behalf) took the PTL role. When we took it, some guys let me know that they were glad to hear the project didn't go inactive at this time. So, it's maintained, it's used, and there are processes in businesses that relies on this package with its name, at least we do here at OVH. You can give my name and address if you are in contact with them, maybe I should look at adding my name somewhere on pypi somehow, idk. Thank you for the forwarding still. Axel Vanzaghi Le vendredi 17 mai 2024 à 11:34 AM, Dmitriy Rabotyagov <noonedeadpunk@gmail.com> a écrit :
Um,
Mistral project is not considered as "inactive" project [1] and does have a PTL for the current cycle [2].
I am not sure how active development of Mistral is, but it is considered as active project at very least.
[1] https://governance.openstack.org/tc/reference/emerging-technology-and-inacti... [2] https://governance.openstack.org/election/results/2024.2/ptl.html
On Fri, May 17, 2024, 11:26 Renat Akhmerov <renat.akhmerov@gmail.com> wrote:
Hi!
I’m Renat who originally created the Mistral Workflow project and I was a PTL for many cycles. I’ve not been in the loop for more than 3 years now so I’m not sure what’s going on in the community now. Neither in OpenStack, nor particularly in Mistral. I heard the rumors though that Mistral upstream life is not longer active. I’d love to hear some feedback on that. The reason I’m asking is that I’ve been asked to let other folks with a big business to reuse the pypi name “mistral”. Seemingly, there’s no many unique active users now, but there are some probably. So before answering to them “no”, I’d like to understand if it’s really impossible (broken OpenStack CI pipelines, other businesses potentially suffering etc etc). Would it make sense also to consider moving “mistral” to something like “mistral-workflow” on pypi?
Would appreciate any input.
Thanks
Renat Akhmerov