- add `codegenerator` repository used to generate OpenAPI specs from
service sources and client API bindings from the OpenAPI
- add `openapi` repository with documents describing OpenStack
flavouring of OpenAPI and Sphinx extension to render them similar to
os-api-ref
- slightly adapt the overall team mission to better match the reality
Depends-On: https://review.opendev.org/c/openstack/project-config/+/910580
Change-Id: I3513c3363eed62155291f2d9bf094bf07725df64
Removing myself from the release liaison list
as I'm not currently one of the most active oslo
members so I prefer to redirect possible release
intercolutors to right persons.
Change-Id: I55ad510078b01a11dd24a0c8d7c52cdf913a5622
OpenStack-Chef project which provides the Chef cookbooks
for OpenStack life cycle management, does not have maintainers
and leaders to keep this project healthy. During the Caracal development
cycle election, this project is on the leaderless list.
- https://etherpad.opendev.org/p/2024.1-leaderless
A few of the stats about this project are below, which are discussed
during leadership project task:
- gate health unclear, no activity for > 1y in openstack/openstack-chef repo
- most recent branch is stable/train
- zuul config errors fixed by frickler
Previous PTL Lance Albertson indicated that they would not be able to
continue its maintenance and are ok with the retirement. (notes in above
etherpad)
Seeing no leader or maintainers for this project and its recent activities,
this change proposes to retire this project.
Change-Id: Icaf68a43028c9c49bc2bbb9dadcc9a1550bc9168
The yaql library has been maintained under murano's governance, but
the murano project has been inactive for several cycles. Because this
library is used by heat and mistral, we have to maintain it as long
as these two projects are maintained.
This proposes moving the yaql project to heat's governance as the first
step. Later we'll update the core reviewer of the repository so that
both heat team and mistral team can maintain it.
This transition was earlier proposed in the mailing list[1] but we
haven't received any feedback from the murano project, unfortunately.
[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/KFTPG45LEB5QYY4NELA7EQJ56MSOWULK/
Change-Id: If5d3ed3a8314a8f650cd90416b53e02a84e4ed44
This has been announced on the openstack-discuss mailing list:
https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/L6HJW55SEUL4NYQVOESJ22KFDW5SGZAE/
Needed-by: I081cd363117671eaab6a3193094d5872f9820354
Needed-by: I4722b869033ad1bd357e36c4a258b6d3ea61f5d6
Needed-by: I28b777dccbcd15b0960ac3fe3e95021633fa8dd7
Needed-by: If2b9a82cddb20543b176ee22765049db257c89b9
Needed-by: I1143e5e5ccf8103e386fe1ce614a554e7f152d9a
Change-Id: Ib186ac5830e5920e264d79be946995e63e960426
Currently each sunbeam charm is in its own repo. This approach
is going to be replaced by having a single monolithic repo that
will contain all the sunbeam charms.
Depends-On: I79e5efca77a49b1cd2b0706d37a39cbbab4a19dd
Change-Id: Ie72e31f8375371b87c97d9264aa4b92344efa0d9
Zuul