team
team copied to clipboard
not-kennethreitz
find a new home for all repos
In the spirit of transparency, I'd like to (publicly) find a new home for my repositories. I want to be able to still make contributions to them, but no longer be considered the "owner" or "arbiter" or "BDFL" of these repositories.
Some notable repos:
- https://github.com/kennethreitz/requests
- https://github.com/kennethreitz/records
- https://github.com/kennethreitz/requests-html
- https://github.com/kennethreitz/setup.py
- https://github.com/kennethreitz/legit
- https://github.com/kennethreitz/responder
tl;dr: all repositories under the 'not-kennethreitz' org on github (https://github.com/not-kennethreitz) are effectively 'up for grabs'.
Considerations for maintainer selection:
- I will select you (or your organization) to maintain the project if you have a standing history of contributing to open source software, show enthusiasm / meager eagerness to learn, or have an interest in keeping the given project alive.
- Some projects have domains associated with them. These are included in the transfer.
- I am currently looking for a job ([email protected]!), and my operating funds are very low. Therefore, if you or your organization are open to the idea of monetary exchange for ownership of a repo / pypi project, please email me. I am considering this an unlikely and rare situation. Only serious offers will be considered, and money won't influence maintainer-ship decisions.
As these are now community projects, I want the future of these projects to be influenced by the community — so please say something if you feel strongly about the future of any of these projects.
Many thanks, Kenneth Reitz ☤
Process
- Be interested in maintaining a repository.
- Leave a comment on this issue, stating your intentions.
- (optional) email [email protected] with any additional information required.
@mitsuhiko that'd be an interesting outcome :)
In all seriousness, are you still interested in the Python community? I haven't talked to you in a while. If you want it, it's yours to take care of. But, it's a large burden to bear. Perhaps the modern rendition of Pocoo would be able to handle it?
I can help to take care of requests-html, I follow you in contributions to that projects and would like to keep improving it once async/requests library support is defined.
@oldani excellent. Many thanks. I'll wait to see if anyone else is interested in Requests-HTML before initiating the transfer.
If @byk is willing Sentry can offer management of requests-related repositories. He's the first member of our open source team here, which will certainly be growing over time. We'd leave core contributions and management up to the community, but we'd help maintain the larger organizational aspects (such as CoC, any financial concerns).
@navdeep-G transfer initiated! :sparkles: :cake: :sparkles: enjoy the github stars!!
@oldani you must delete your fork in order for me to transfer to you.
Done and many thanks for creating the package initially, I will keep it great for sure:)
Yo. The python-http organization would also be a excellent place for requests to land up. I can put together a proper proposal about how we'd plan to tackle funding, maintainance etc.
I'd really like to deal with requests3, since that's pretty much what I've been working towards with http3 anyways.
mead is being taken over by @abdounasser202
I deleted the forked mead repo. Now i'm waiting for transfer
Can you explain what you mean in more detail, @kobayashi?
I mean I do want to take care of one of not-kennethreitz. Is there chance to do that? All of them are great! @kennethreitz
I can look over tablib! camelot's export API was inspired from tablib :) Would love to integrate tablib more closely with camelot to support more export formats!
Hello @kennethreitz! Given the cumulative impact that these projects have on the Python ecosystem at large, the Python Software Foundation would like to offer to accept transfers of these repositories into the @psf GitHub organization.
This organization was recently acquired by the Python Software Foundation and intended to provide administrative backstopping for projects in the ecosystem; existing maintainers of various projects will remain and the PSF staff will be available to manage repositories and teams as necessary.
We are working to finalize a few things but could be ready as soon as early next week. Thoughts?
I really would like to see @tomchristie taking the reins of requests3 either under encode or the psf, regarding requests I think many cool orgs like the psf, encode or pocoo can provide the long term support and handle the burden !
and I support @ewdurbin proposition !
Hi @ewdurbin. Since @python's recent acquirement of black, and the fact that a lot of other core community projects exist in that organisation, it'd be nice if you, or someone else, could elaborate on the difference between that and the new @psf organisation?
Sorry to bother if you were already planning on doing so 😉
@madsmtm that's an excellent point! Indeed black moved to /python recently and was actually the impetus for the creation of the /psf namespace. The /psf organization is intended to support broader Python ecosystem interests that don't relate to the core language itself. Overtime we'll be moving many repos out of /python into /psf (for community projects) and /pyfound (for internal PSF concerns) to better namespace our GitHub presence.
Assuming these are the remaining up for grab repos? https://github.com/not-kennethreitz?utf8=%E2%9C%93&q=&type=source&language= @kennethreitz
~I'd be happy to maintain dj-database-url. Having another django package wouldn't be too bad :smile:~
On second thought, maybe not. I knew django-environ used it, but I didn't know it was that popular.
