-
Notifications
You must be signed in to change notification settings - Fork 33
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 ownership of mybinder.org away from Chris's account? #424
Comments
We should definitely do that. I think jupyter.org registration is still on @fperez personal account. The DNS and all operations are on CloudFlare, on the same account as mybinder.org. We should probably consolidate all those on a registrar account that supports multi-user access, if one exists (or a single projectjupyter account, if necessary). |
Can CloudFlare be used to own the mybinder.org domain? If so, it feels like that'd make the most sense since we already use it for the other services you describe. If we need to use a different service, I've generally used NameCheap with good results, and I believe it supports multi-user access (though requires one account to be the "owner" account). If we need an "owner" account, perhaps the easiest thing to do would be: Option 1
Option 2
What do you think? |
I think as a first step I'd like to take Option 1 above. If we move to NameCheap I will still technically be the "owner" of the account, but I can give everybody else full privileges. It even sounds like we could pass the account to another person as "owner" if something happened to me (https://twitter.com/Namecheap/status/1411768877546094596). It also seems like transferring an account between NameCheap users is pretty straightforward, so that would leave this option open for the future. I believe I can do the transfer myself, but does anybody think that this transfer would affect mybinder.org uptime? CloudFlare is doing our DNS, but perhaps there is something I'd need to do upon transferring to NameCheap to ensure continuation of service? |
I'd suggest moving it to Google Domains, so it unifies access control in the Google Cloud binder project (https://cloud.google.com/blog/products/networking/introducing-cloud-domains) |
On Sun, Aug 8, 2021 at 11:58 PM Yuvi Panda ***@***.***> wrote:
I'd suggest moving it to Google Domains, so it unifies access control in
the Google Cloud binder project (
https://cloud.google.com/blog/products/networking/introducing-cloud-domains
)
Sorry, I'm finally getting more up to speed on my github notifications...
Just to record publicly that I'm 100% on board with moving all resources
that have historically been held by me personally to team orgs and shared
accounts. A lot of that was a natural process stemming from IPython's
beginnings, but today it makes no sense for domains, credentials, etc, to
be tied to me personally. It will take us a bit of time to disentangle all
this, but I want to clarify that other than logistics/slowness on my part
out of being busy, I have absolutely no objection here, and I think this is
what we should do!
|
We've received a notification that the domain expires in 59 days, and the registrar will attempt to autorenew it 15 days before. Are we in a position to transfer it somewhere? Otherwise @choldgraf are you happy to handle the renewal? |
I'm happy to do whatever including paying for a renewal, but i have minimal time to do anything so I'll prefer the path of least resistance |
I've opened an issue on jupyter/security#64 |
Hi, I'm going to work with the others on the Security Subproject to come up with a suggestion during our meeting next Tuesday. --Rick |
The EC has been moving all our domains over to one account that is accessible from the project password management system. So we are finally ready to do this. I've contacted @choldgraf to unlock the domain and generate a transfer authorization code. I will update here when the transfer is complete. |
Yesss I am very excited to get this one completed. Thanks @afshin for reaching out. |
I can confirm that |
Are there any JupyterHub team or mybinder docs we need to update, or can we close this? |
I don’t think there’s any meaningful thing that changed so we can probably
close the issue.
…On Fri, Oct 20, 2023 at 14:18 Simon Li ***@***.***> wrote:
Are there any JupyterHub docs we need to update, or can we close this?
—
Reply to this email directly, view it on GitHub
<#424 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABG6KMUL4G2PZ3YGUIQYEDYAJ2YNAVCNFSM47EQIN7KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGI3TENRQGM3A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
We currently use BlueHost for the DNS registration at mybinder.org, running off of my personal account. I think that this is not great for a number of reasons, most notably that I am personally a strong bus-factor for mybinder.org's long-term existence 😅
The mybinder.org registration is expiring in a month or so, and perhaps this is a good moment to transfer ownership to a multi-person account. Does anybody know if the Jupyter project has guidelines for this? Perhaps @minrk has experienced this with nbviewer?
I am happy to take whatever path is best for the team (including just renewing registration under my account, if that's what others want). Let me know what folks think
The text was updated successfully, but these errors were encountered: