Sorry for my late update. The governance change was approved and now yaql is under heat's governance. I managed to reach out the previous maintainer of this project and got access to its gerrit group and lp team. I've also merged a few bug fixes and clean ups and created the yaql 2.0.1 release because we haven't had a release for a while. As I said earlier, I'm very open to anyone from Mistral joining the group to help maintenance of the repository. May I ask someone from the mistral project to discuss the members who I can add to the group and share the list ? I'm usually available in irc (nick: tkajinam) so please feel free to contact me there. Thank you, Takashi On 12/14/23 10:39, Takashi Kajinami wrote:
Hi Arnaud,
Having some people from Mistral side would be very helpful. I'm still waiting for feedback from Murano PTL but will include Axel (and a few other people if you want) when we actually make the change.
Also, thank you for the alternative yaqluator site !
On 11/28/23 01:45, Arnaud Morin wrote:
Hello,
Mistral is heavily relying on yaql, so maybe it could be nice to have at least PTL of mistral (Axel) as core reviewer for it.
BTW, since the old yaqluator website was down, we (OVHcloud) hosted a temporary yalquator here: https://yaqluator.ovh/
My 2c, Arnaud.
On 27.11.23 - 16:13, Takashi Kajinami wrote:
Hello,
The yaql library is currently maintained under murano's governance and is used by not only murano but a few other projects such as heat and mistral. In heat the library is essential since we introduced yaql function support. Looking at gerrit groups, I noticed the yaql library is maintained by a very small core group[1] and release group[2], but I'm afraid most of the people in these groups are no longer active in the community.
Because heat is dependent on the library, I'm wondering if some of the heat cores can be added to these two groups so that we (at least I) can help maintaining the library.
I've checked the changes merged into murano repo for these two years but iiuc all of these changes are gate fix. Also a dummy change[3] indicates that its CI is currently broken. If the murano project is no longer active then I'm also willing to take over yaql and bring it to heat's governance (of cause only if it's acceptable).
I'll add the current PTL as cc, but please let me know if anyone has any opinion or concern.
# I'll add mistral tag because the project is also dependent on yaql. # Also tc is added because this discussion is related to project governance.
Thank you Takashi Kajinami
[1] https://review.opendev.org/admin/groups/cba4f6fd54c3cc0d5706fc50b5ebd758860d... [2] https://review.opendev.org/admin/groups/d5e894b34e5ab5a9fc2938a0d4e7bc76fd25... [3] https://review.opendev.org/c/openstack/murano/+/901888