Externally Hosted Services

There are services which are requested but not hosted using the traditional Fedora infrastructure. This SOP describes the process for getting those services integrated.

Contact Information

Owner

Fedora Infrastructure Team

Contact

#fedora-admin, sysadmin-main, sysadmin-dns

Purpose

Allow externally hosted services to appear as *.fedoraproject.org

Description

Allowing external services to have a *.fedoraproject.org DNS entry will be decided on a case-by-case basis. Regardless of where or how a service is hosted, if it can be accessed via a Fedora project domain, there is an impression that we are responsible and that the service represents us.

To submit a service for consideration, open an infrastructure ticket with the following information:

  • What is the promise of support?

  • Is there a point of contact for issues of normal priority?

    • If there are problems identified, this is the contact point that will deal with them.

    • Use common sense to decide whether the point of contact should be included in the ticket. If it’s not included, be ready to submit it via less public channels.

  • Is there a point of contact for emergency or sensitive issues?

    • This is for issues which either can’t wait for the normal support process or require more descretion.

    • This will frequently be contact information (email, phone number) for a specific person

    • Do not put contact information for individuals in the ticket

  • Acknowlegement that the service provider has been told who is authorized to ask for changes and a list of who those people are.

Once the infrastructure related issues are in order, submit a Fedora council ticket for final approval before a *.fedoraproject.org DNS entry will be allocated for the service.