Hi!

вт, 11 черв. 2024 р. о 16:26 <smooney@redhat.com> пише:
On Tue, 2024-06-11 at 14:09 +0000, Dmitry Tantsur wrote:
> Hi,
>
> On 6/10/24 10:30 PM, Daniel Bengtsson wrote:
> >
> >
> > On 2024-06-10 16:28, Dmitry Tantsur wrote:
> > > If we go with this proposal (which sounds reasonable), we need to
> > > carefully look at cotyledon's maintenance. It seems to be on life
> > > support by only one volunteer:
> > > https://github.com/sileht/cotyledon/commits/main/
> > You're right but he is pretty active and I don't think it's a big issue.
>
> How do you judge that? Herve mentioned a PR merging quickly, but that's
> not a perfect criteria. I have a pet project (rust-openstack) where I
> also tend to merge PRs quickly. Except when I'm on a vacation or very
> busy at work, then I can forget about PRs for a month or more.
>
> Note that I'm not saying "let's not use it". I think a reasonable next
> step, if we decide to research this part, would be to get in touch with
> the maintainer, understand their plans and their position on adding more
> maintainers in the future.

i think in one of the other replies they mentioned propsoing it as a deliverbale
under the oslo project so if that happens i think the maintainer ship and
co installablity (use of upper constratits) issues as well as goverance issues
go away

Why do we still rely on SQLAlchemy and do not request Michael Bayer to move the library under OpenStack governance? Most contributions come from a single maintainer. The project already uses Gerrit, so the contribution flow will be similar, right?

Also, do you believe that moving projects under OpenStack governance magically increases project aliveness?
Let's discuss the "ldappool" library. It is under OpenStack governance and is required for LDAP integration in Keystone. Is it alive? The last release was on February 26, 2021. This release includes a bug: the usage of a dependency that is missed in requirements.txt - the "six" library.
The fix waited for two years to be merged https://review.opendev.org/c/openstack/ldappool/+/805495 , and there is no new release with it.
Hm... So, magic OpenStack governance did not help?! How did this happen?

Sorry for these sarcastic questions. I only tried to say that independently of project governance, the project may die and become unmaintained. The only valuable thing is the contributors.
Asking a project maintainer to move from "his" development flow to work under OpenStack governance before reducing "his real maintainer's costs" sounds strange.
If openstackers start actively contributing to Cotyledon, moving under OpenStack governance as Cotyledon community decision sounds reasonable to me. Otherwise, it doesn't sound nice. It is not "a chicken&egg problem"; the primary action should be obvious.
 
>
> Dmitry
>
> >
> > --
> > Daniel Bengtsson
> > Software Engineer
> >
>



--
Best regards,
Andriy Kurilin.