Hi,
I am the maintainer of a few Python libraries around the SCIM protol
[1]. I have implemented a re-usable pytest fixture that starts a SCIM
server in a thread, and let the test suite interact with it.
I would like to move the project to the pytest-dev organization.
What do you think?
Éloi
[1] https://github.com/python-scim/
[2] https://github.com/azmeuk/pytest-scim2-server
Hey,
Hopefully we're all aware of the Python Steering Council and its
relationship with various people and groups that do work on Python.
There's also now a proposed similar group for Packaging,
https://peps.python.org/pep-0772/
This got me thinking about the governance and decision process around
pytest and pytest plugins that are part of the pytest-dev umbrella.
So, my question is:
- What is the pytest governance model?
- What about the various pytest plugins under pytest-dev?
I've not too awfully long ago done some contribution to pytest-repeat, but
it's never been really very clear who's in charge.
It seems like we'd need it to be more formal for pytest, and gradually less
formal as we go down the list of popularity of plugins, maybe.
But at the very least, it seems like each plugin in pytest-dev should have
a first contact, maybe a second contact, and such, and a process for
replacement if/when people become uncontactable.
The packaging pep talks about "can't get hold of someone for a month" as a
decent thing to decide when to possibly find someone else.
I think we need something like that.
I also don't want plugins to just be "frozen at the time of when the
original maintainer left". Because that would really stifle growth.
Anyway, are there any answers to these questions?
Thanks,
Brian
