FWIW, I'm -1 on renaming anything. There's already enough confusion with why there's catchlog and capturelog, and now renaming catchlog to logging will IMHO just increase that confusion.
Good point. I would also recommend to consider this.
+1 if he's okay with that. I'm happy to be some kind of co-maintainer if you want, maybe with some similar workflow like with pytest core - everything happens via PRs so there's someone who can review the code.
Sorry, I thought it was obvious that you'll also be included in the maintainer group since you approached me long before and you're among the most experienced with pytest itself and currently involved with pytest-catchlog. :)
The PR workflow is how I usually work and prefer to work so I'm perfectly fine with this. Having someone else looking over the change set and sharing his opinion/experience is always a benefit.
I think everyone has less time on their hands than desired - so I'd personally like to keep you as maintainer/gatekeeper/releaser/ whateveryoucallit as well. Doesn't hurt to have someone more involved - even though you might end up not actually *doing* much in practise anymore, if you prefer.
I would be glad to help out this way if this level of engagement is enough and still desired.
-- Arthur Skowronek M: [email protected] _______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
