Unsubscribing from pytest-dev/pytest notifications
Hi, (I accidentally sent this to pytest-dev@pytest.org rather than @python.org originally. It didn't bounce, but I have no idea where it went :D) this is a difficult step to take, but during three sleepless nights because of health issues last week (don't worry, it's getting better now) I realized a lot of things (also see this thread on Twitter: [1]) [1] https://twitter.com/the_compiler/status/984356385214394368 I really wish GitHub had a way to subscribe to issue labels, but until that happens, I need to unsubscribe from pytest-dev/pytest (which is what I just did) - I'm spending too much time working on things in pytest I'm somewhat interested in, but not really passionate about. This is probably best explained with some back story: I got into pytest because I started using it with qutebrowser[2] (which is still my main OSS project), started contributing on plugins (mostly pytest-qt) because I was missing some features, and got into the pytest community. Somehow I ended up first getting regarded as a contributor, later as a core contributor (or maintainer) - while I still feel like I have no idea of pytest's code base :D [2] https://www.qutebrowser.org/ There's a list of things I'm still very much interested in - if something happens in those areas, please don't hesitate to contact/mention/request a review from me, I'd very much like to hear about those: - Giving trainings and talks (probably what I liked doing most so far!) - Anything related to user-facing changes: The API, output, etc. I am still an avid user of pytest, and thanks to trainings and other involvement feel like I have a picture of what other users want, too. - The community, which is awesome! I'll still stay on this mailinglist and the IRC channel, and I'd very much like to go to another development sprint in the future. - Testing (pre-)releases - Some plugins, especially pytest-qt - Any code I've written Things I'm explicitly not interested in (and where I never really did anything anyways): - Anything internal and complex in the codebase: Markers, fixtures, pytest.code, capturing, etc. etc. - you get the idea. I'd like to keep my maintainer/commit/whatever flag, and I might revisit this in 1-2 years, where I might have more time on my hand for open-source work. If there's consensus that I should drop it, I'm not going to say no either, though. (If you want to answer something along the lines of "get well soon" - those replies are very much appreciated, but please consider sending them to me directly instead of the mailinglist, to cut down "noise" for others) Florian -- https://www.qutebrowser.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
Hey Florian, On Mon 16 Apr 2018 at 07:50 +0200, Florian Bruhin wrote:
this is a difficult step to take, but during three sleepless nights because of health issues last week (don't worry, it's getting better now) I realized a lot of things (also see this thread on Twitter: [1])
Thanks for being so open about this.
I really wish GitHub had a way to subscribe to issue labels, but until that happens, I need to unsubscribe from pytest-dev/pytest (which is what I just did)
That's no problem at all. I've not been receiving email for github activity in ages, and that blue dot on github is basically a permanent feature. Volume is pretty high (to me), occasionally I try to look at it but I mostly also rely on those of you who do keep up on mentioning me...
- I'm spending too much time working on things in pytest I'm somewhat interested in, but not really passionate about.
Prioritising your own time to what you enjoy most is more then sensible.
I'd like to keep my maintainer/commit/whatever flag, and I might revisit this in 1-2 years, where I might have more time on my hand for open-source work. If there's consensus that I should drop it, I'm not going to say no either, though.
No need to remove a commit flag! (unless you intend to turn malicious ;)) All the best, Floris
Hello, On Tue, Apr 17, 2018 at 10:55 PM, Floris Bruynooghe <flub@devork.be> wrote:
I really wish GitHub had a way to subscribe to issue labels, but until that happens, I need to unsubscribe from pytest-dev/pytest (which is what I just did)
That's no problem at all. I've not been receiving email for github activity in ages, and that blue dot on github is basically a permanent feature. Volume is pretty high (to me), occasionally I try to look at it but I mostly also rely on those of you who do keep up on mentioning me...
I use https://octobox.io to follow up on all my Github activity (mentions, subscriptions, ...) It helped me, so I hope it can help you too. *Ringo De Smet* ringo.de.smet@ontoforce.com
participants (3)
-
Florian Bruhin -
Floris Bruynooghe -
Ringo De Smet