Hey, * Arthur Skowronek <[email protected]> [2015-10-19 23:17:24 +0200]: > It would be nice if the plugin could stay separated from the core package. > At least I am a huge fan of the modular plugin system as it can be found in > pytest. I find such a modular design more preferable compared to a > monolithic project that comes with everything attached. Such a large project > makes it harder for users to track what was changed between versions and > keep track of changes important to them. They don't need to care at all if > the API was changed but they don't use the plugin. > > Also different contributors stated that they still would like to improve the > code base and add more functionality. It would be nice to give them their > freedom to break the API if necessary to create something even more usable > with a sleeker API. I'm looking forward to it.
I used to have a different stance on this - but after reconsidering, I agree it'd be best to have a "recommended" plugin (i.e. catchlog, as it's maintained and under pytest-dev) rather than merge things into core. > As far as the naming goes I can understand that it makes sense to rename the > plugin to pytest-logging. The current name was chosen just to avoid naming > conflicts on the PyPI. But over time I've grown attached to it. :) I hoped > that we could find someone that would draw a nice dream catcher as a logo > for us that would decorate the documentation I also wanted to write. Maybe > we can a find a compromise here, something like pytest-logging-catcher or > so? 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. I love the idea with the dream catcher! > * Granting Access to PyPI and Github to more maintainers > > I would love to recommend Eldar Abusalimov as a maintainer for the plugin. > He contributed by far more than compared to me and he knows what he does. +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. > Optionally: > > * Taking my exit > > As stated above I don't see where I fit in the bigger picture. I'm not > important to continue the project at all. My day job keeps me busy enough > so I won't be able to land bigger improvements on the plugin. All I can > offer is to merge patches and take care of other issues. Then again these > chores can be done by anyone else with more time on his/her hands. 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. Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: Digital signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
