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

Transfer repo ownership to absinthe? #27

Open
sax opened this issue Feb 19, 2024 · 14 comments
Open

Transfer repo ownership to absinthe? #27

sax opened this issue Feb 19, 2024 · 14 comments

Comments

@sax
Copy link
Collaborator

sax commented Feb 19, 2024

Hey @jasonwc! I was wondering if we could start a conversation to try to transfer ownership of this repository to someone actively involved with Absinthe. I am not building anything using GraphQL, and it seems as if nobody else with write access to geometerio repos is able to maintain this. If the org is amenable, then maybe we could start a conversation in the Elixir slack #absinthe-graphql channel to see if someone could take over maintenance.

@jasonwc
Copy link
Collaborator

jasonwc commented Feb 21, 2024

I'm amenable to this! Let me bring it up internally tomorrow but I expect no objection.

@sax
Copy link
Collaborator Author

sax commented Feb 25, 2024

Any word on this? I just saw another issue come up about the library come up on the Elixir slack, so people are definitely using this library.

@jasonwc
Copy link
Collaborator

jasonwc commented Feb 27, 2024

Hey @sax we see no problems! Best to have this in the hands of folks actively using and able to maintain it. How would you like to proceed?

@kaogire
Copy link

kaogire commented Jun 13, 2024

Hey @sax Any progress on this?

@sax
Copy link
Collaborator Author

sax commented Jun 16, 2024

I had some quick responses when I originally asked in the Elixir Slack, but have not gotten anyone to follow through. It seems like there's active movement to get more contributors/maintainers on the core Absinthe projects, so I just re-posted to see if I can get any more movement.

@benwilson512
Copy link
Collaborator

Hey folks, apologies for the delayed response. This sounds great, and we have some new contributors to Absinthe who are happy to help. What all is involved?

@sax
Copy link
Collaborator Author

sax commented Jun 25, 2024

I think that @jasonwc will have to transfer the repo. If he can't move it directly to the absinthe-graphql organization then I think he should move it to you, @benwilson512 and you can move it on.

@benwilson512
Copy link
Collaborator

We'll also need to sort out the hex pm package.

@sax
Copy link
Collaborator Author

sax commented Jun 25, 2024

I think that can be done with mix hex.owner transfer absinthe_graphql_ws benwilson512, and then leave it to you to add owners or move it under an organization.

@jasonwc
Copy link
Collaborator

jasonwc commented Jun 26, 2024

Thanks for taking this on @benwilson512! I think the best course of action is for us to find a time we can walk through the handover process together. That can be async during a window or I'm happy to jump on a call.

I think in general we should:

  • Transfer the github repo to you personally, then you can move it into the correct org
  • Transfer the hex package to you personally, then you can move it into the correct org

Let me know if that makes sense and how you'd like to proceed.

@benwilson512
Copy link
Collaborator

Hey @jasonwc go ahead and just initiate the transfer, and I'll get things sorted from there.

@jasonwc
Copy link
Collaborator

jasonwc commented Jul 9, 2024

Hey @benwilson512! Sorry for the delay. I'll initiate the transfer and ping you tomorrow during business hours.

@jasonwc
Copy link
Collaborator

jasonwc commented Jul 9, 2024

@benwilson512 I have requested the repo transfer. Working to do the hex package now.

@jasonwc
Copy link
Collaborator

jasonwc commented Jul 9, 2024

@benwilson512 the hex package has been transferred!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants