-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ownership of requests, requests3 #5
Comments
Taking over requests would be something that we can do (and were essentially formed to do). It's maintenance burden is security fixes only so it's an easy candidate for long-term support under the org. requests3 I don't really care about. There's no large user-base to look after. Any of the other requests peripheral libraries are also things we'd be willing to take maintenance of. |
It sounds like requests will be housed under the @psf organization per the thread. Users are safe and it's out of our hands. |
It may work out the same, once we finish setting up python-http as an official PSF working group... |
Yeah, that's kind of what I'm expecting to happen. :) |
Well, maybe it's not entirely settled: not-kennethreitz/team#21 (comment) I'm not going to post in that thread, but I think the PSF might be a better option in any case for right now. AFAIK the two valuable requests-related resources that Kenneth currently owns are the repo, and the |
Yes, definately happy to see the PSF step in there. Either so that they can take ownership, or so that they can be involved in vetting any handover. |
Agreed. It'll be a goal of ours to be able to handle complete transfers properly. :) @tomchristie I think KR is waiting for a reply from you in that thread? |
So, this: not-kennethreitz/team#21
I've proposed
python-http
forrequests
- can put together something more significant as a proposal if we want to go for that.I've also proposed that I'd like to take admin over
requests3
. (Not as a decision on "that's what I think http3 should end up as", but so that we have it as an open option.)The text was updated successfully, but these errors were encountered: