+1 from my side.

As discussed yesterday with Luigi (tosky) it makes sense to me to host that under the Oslo scope, however I would appreciate to get feedback from other Oslo team members before doing anything.

Even if this project seems stable we still need to continue to maintain the current code base to keep the code up-to-date and compatible with the next Python versions.

Concerning the "release" point of view of this topic, if this project is stable enough I think we can adopt directly the release independent model [1]. It would help us to reduce the maintenance related to stable branches (backport fixes etc...). Do you have any opinion on this?

Hervé

[1] https://releases.openstack.org/reference/release_models.html#independent

Le mar. 15 déc. 2020 à 06:01, Brian Rosmaita <rosmaita.fossdev@gmail.com> a écrit :

Hello Oslo Team,

Nova, Glance, and Cinder all make use of the 'cursive' library for
image-signature-validation. The library is currently in the 'x'
namespace: https://opendev.org/x/cursive

The current cursive-core team entirely consists of members of the Johns
Hopkins University Applied Physics Laboratory, which ended its
involvement with OpenStack in July 2018 [0].

This leaves us in a position where three of the major openstack projects
depend on a library to which no one currently around can approve code
changes.

I'd like to propose that the cursive library be moved back to the
'openstack' namespace and be put under Oslo governance with the
consuming teams sharing the maintenance of the library. I don't think
this will make much new work for the Oslo team--the library has been
very stable and hasn't changed in over 2 years--but it will ensure that
should any bugfixes be required, there will be oslo team members who can
approve the patches.

Thanks for thinking this over,
brian

[0] http://lists.openstack.org/pipermail/openstack-dev/2018-July/131978.html

Hervé Beraud

Senior Software Engineer at Red Hat

irc: hberaud

https://github.com/4383/

https://twitter.com/4383hberaud