search

jenkins-infra / helpdesk

Open your Infrastructure related issues here for the Jenkins project
https://github.com/jenkins-infra/helpdesk/issues/new/choose
17 stars 10 forks source link

[INFRA-243] jenkins-ci.org domain name still appears to be registered under Tyler's personal account #237

Closed jenkins-infra-bot closed 7 years ago

jenkins-infra-bot commented 9 years ago

I noticed that the request to acquire SSL certificates still need to be approved by Tyler and no other people, and the registration of the domain "jenkins-ci.org" appears to be still under his control.

This needs to be moved under SPI.

Originally reported by kohsuke, imported from: jenkins-ci.org domain name still appears to be registered under Tyler's personal account
  • assignee: rtyler
  • status: Closed
  • priority: Major
  • resolution: Won't Fix
  • resolved: 2016-12-31T00:41:07+01:00
  • imported: 2022/01/10
jenkins-infra-bot commented 9 years ago

rtyler:

We've spoken about this before. Is there any form of asset management that SPI supports? I think this would still probably require me to be tied as the administrative contact, but the account in the registrar, I'm not sure how that would be set up to allow multiple people access.

jenkins-infra-bot commented 9 years ago

orrc:

From whois debian.org, it looks like SPI holds domains in a Gandi.net account. Whether/how they then give project members/accounts access to that account is another question. But that should be rarely required, e.g. nameserver changes?

For the administrative email contact, like Debian, would it suffice to have a hostmaster@jenkins-ci.org alias which goes to some subset of the infra team?

jenkins-infra-bot commented 9 years ago

kohsuke:

Sent an email today to SPI.

I agree we should have a mailing list for this in the interim. We don't run our own mail server, though. Could it be jenkinsci-infra@googlegroups.com?

jenkins-infra-bot commented 9 years ago

rtyler:

I've got all the details and everything to transfer over to SPI

jenkins-infra-bot commented 9 years ago

rtyler:

I've requested the authorization codes and unlock for these domains from Namecheap

jenkins-infra-bot commented 9 years ago

rtyler:

Authorization codes for jenkins-ci.org sent along to the SPI folks in an encrypted email

jenkins-infra-bot commented 9 years ago

rtyler:

I've sent the authorization codes to some SPI folks, waiting (im)patiently so I've added a Blocked flag to this

jenkins-infra-bot commented 9 years ago

rtyler:

bumped the thread with SPI again today

jenkins-infra-bot commented 8 years ago

rtyler:

I bumped the thread with SPI

jenkins-infra-bot commented 8 years ago

rtyler:

I reached some folks from SPI on the #spi channel on OFTC and bumped the thread with them:

20:48  are you on the hostmaster alias?
20:48  yes
20:49  I'm pretty sure I had sent you the encrypted authorization code to transfer the jenkins-ci.org domain name over
20:51  ay, you did, and neither I nor Michael picked it up. :/
20:51  heh
20:52  so we run our own DNS servers at ns1 and ns2.jenkins-ci.org
20:52  I'm not sure what else you would need from your side to set this up
20:53  with you running your own NS - nothing. ill poke our registrar later, we will find out if the auth codes still work, and then it goes on. sorry for that ... delay.
jenkins-infra-bot commented 7 years ago

rtyler:

SPI hasn't been the easiest to get this done with. I'm going to close this out until such a point when we have a chance to revisit it with SPI