I received a request from @aeperezt to transfer the domain proyectofedora.org to the Fedora Project. I have never processed a request like this before, so I first started with a Red Hat Help ticket. I was asked the following questions, which I did not know how to answer:
proyectofedora.org
I wasn't sure how to answer these questions. Do we have a precedent for how Fedora domains are managed? In the case of this specific domain, we will just want to redirect it to fedoraproject.org. I don't think we want to publish unique content on this domain, but just keep it as a redirect.
fedoraproject.org
I am looking to understand how historical precedent has handled tasks like this in the past. Should we drive this effort through a Fedora Infrastructure ticket and have @aeperezt work with a CPE team member on transferring the domain into Fedora's DNS nameservers? If yes, what are the steps for transferring this to Fedora's DNS nameservers? If we should drive this through a Red Hat Help ticket, is there someone from Red Hat CPE that I can copy into my ticket and help make sure this domain is managed correctly?
Not urgent or a crisis, but @aeperezt has been patiently waiting some time already on this request—since last November to be exact. It would be good to help get this domain off his hands to save him some dollars every year in the renewal fees.
OK normally we handle these on the Fedora Project DNS servers. The usual steps needed by Fedora Project Infrastructure:
This is something we want for the Fedora Project.
@smooge @mattdm Thanks!
The current freeze ends on 14 March, correct? It would be nice to start this process earlier than then, but I guess it is not required. Given that this domain shouldn't interfere with anything releng or critical infrastructure and would just have a redirect, it seems very low-risk to me.
Any idea on the Red Hat business app code? Does FEDO-002 sound right?
FEDO-002
At what address or with whom should Alejandro work with for sharing the transfer code securely?
Usually at this point I would have opened a ticket with the internal DNS owner so that they could start working with the registrar. This would be a ticket cc'ing you all and the current owner. If the process is approved by Red Hat legal, then the following occur: 1. Add a zone to the DNS git repository 2. Add a change to the DNS servers (this is freeze break as previous moves like this have broken all of fedora) 3. Add a change to the websites (this is freeze break as.. well I have broken a lot of things ok?) 4. a day for reassignment is worked out and we ask for a code from the current owner via their registrar. That then gets sent to ours who does the transfer.
However I am not in infrastructure for a while so there may be new things and we need to get it on Kevin's shchedule.
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
So yes, we can submit freeze breaks for those things.
I would say we should get those changes in, then transfer the domain (so everything is ready for it).
In the past we have engaged with internal legal folks since they control domain registrations. I guess the internal ticket could do this? but we have typically in the past just mailed them. FEDO-002 should be fine for a app code.
@smooge @kevin I copied both of you to the support ticket with the Red Hat internal DNS owner so you have the visibility on the legal approvals and whatnot. I don't think any action is required there on your part, but if there is, feel free to participate directly.
Once the DNS changes are prepared, I can contact Alejandro again for him to work with either Fedora Infrastructure or the Red Hat internal DNS owner for the transfer code.
This is not direly urgent, so please schedule and prioritize this as makes sense for the Fedora Infrastructure team. I appreciate your time and support, as always! :pray:
DNS should all be done now.
Transfer anytime. There shouldn't be anything more for us to do from our end. If there is, feel free to reopen. We can track the transfer in the internal ticket. ;)
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
@kevin Just to make sure I understand right, should I reach out to Alejandro now for the registrar transfer code and have him share that over email? And then relay that information into the internal ticket? Just want to make sure that I am clear on the next steps here.
Yes, reach out and get the transfer code and either add it to the internal ticket or send it directly to Erin (the legal contact).
Got it. :thumbsup: I requested the transfer code.
Log in to comment on this ticket.