Skip to content
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

move to github.com/discorporate/blinker #45

Closed
ThomasWaldmann opened this issue Oct 30, 2018 · 11 comments
Closed

move to github.com/discorporate/blinker #45

ThomasWaldmann opened this issue Oct 30, 2018 · 11 comments

Comments

@ThomasWaldmann
Copy link
Contributor

@jek iirc you can click somewhere in the settings to move a repo to a new github org.

guess that is the easiest option to get it there.

i'ld offer to do some basic maintenance if i get the permissions (like for flatland, including a new pypi release with the new URL).

@hugovk
Copy link
Contributor

hugovk commented Oct 20, 2019

Alternatively, https://jazzband.co?

@sfdye
Copy link

sfdye commented Apr 27, 2020

I am a member of Jazzband, this project will make a good candidate for the jazzband umbrella projects. Let me know how I can help move this forward.

@sfdye sfdye mentioned this issue Apr 27, 2020
@sfdye
Copy link

sfdye commented Apr 27, 2020

What do you think? @jek

If you don't have the time to maintain this project, the community can help :)

@hugovk
Copy link
Contributor

hugovk commented Apr 27, 2020

If there's no reply, someone could consider a fork and a PEP 541 transfer of the PyPI name:

https://www.python.org/dev/peps/pep-0541/

@sfdye
Copy link

sfdye commented Apr 27, 2020

Let's give the owner some time to respond

@jek
Copy link
Contributor

jek commented Apr 27, 2020

what is the need driving this request?

@sfdye
Copy link

sfdye commented Apr 27, 2020

There is no need to move this project anywhere, if the project can still be actively maintained (triaging issues/pull requests, cutting new release to PyPI, etc)

What you can help as the owner is maybe considering granting collaborator permission to someone like @ThomasWaldmann @hugovk or myself. We'd love to help move this project forward 😄

@ThomasWaldmann
Copy link
Contributor Author

i think it is always better to have projects under some github org account than under a personal account (except, obviously, for purely personal projects or for very fresh stuff).

the reason is somehow the message that is communicated, like:

  • "this is my thing", vs.
  • "this a community thing maintained by this org" (which is open to all interested parties)

if one then thinks about stuff like bus factor and long term maintenance, the org way gets even better.

of course it still needs people actually doing something good for the project, but at least it is more "inviting".

@jek
Copy link
Contributor

jek commented Apr 27, 2020

I am very open to passing the torch on this project (lead or collaborator) to anyone working in this space with the cross-implemention know-how (especially understanding of which operations are atomic across Python implementations) and, crucially, can articulate why send_robust does not belong in the core.

@delijati
Copy link

delijati commented May 6, 2020

send_robust seams legit to me. It does not change existing api it only extends it and there are tests for it. So can this process of moving the repo or releasing at least a new version be triggered again.

@davidism
Copy link
Member

Blinker has moved to Pallets-Eco, a place for community maintenance of projects related to the Pallets projects (Flask, etc). If anyone is actively using this project and is interested in helping maintain it, please message us on our Discord server: https://discord.gg/pallets.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

6 participants