Local community domains
This page gives some informal guidance on how Fedora communities in different locales can establish Internet domains with the word "Fedora" in them. The Fedora trademark guidelines have specific requirements that must be met for setting up these domains, in order to preserve the value of the Fedora trademarks. The Fedora trademarks are owned by Red Hat worldwide, and apply to all Internet domains regardless of their country of origin or registrar.
Buying a separate domain
Not every local community requires a local domain. Many local communities can function perfectly well in the existing Fedora Project domain(s). Fedora already offers the ability for communities to provide complete translations for our main web site and other pages. We are also working on the capability to have a translated MediaWiki that will not require as much manual work on the part of translators.
In addition, splitting off a domain has the tendency to keep local community members from getting up to date information that flows on the official Fedora channels. It multiplies the number of areas a community member needs to monitor and thus takes away from the time they could otherwise spend on contribution directly to Fedora.
However, there are some good reasons for local domains to exist, and the Fedora Project realizes the importance of enabling the community to grow Fedora in localities around the world. Therefore we have a few options available to people who want to set up a domain to support this effort.
There are essentially two options open to local communities who want to purchase a domain with the word "Fedora" in the name for purposes of Fedora community work.
The Fedora Project or Red Hat can provide a subdomain in the *.fedoracommunity.org domain, and arrange for it to point to the fedoraproject.org domain name servers. Since we control those name servers, it is very easy for the Infrastructure team to then direct host queries to the appropriate community server(s).
To use this option:
- If you are to be responsible for the hosts for the community site, ensure your Fedora Account System account is up to date. If someone else is to be responsible, make sure you have their name and complete contact information available.
- Email the fedora-advisory-board with your request. Use the subject Community domain request. Indicate whether you or someone else is to be responsible for the hosts. Do not post any personal information in the email.
- The Fedora Board will respond as quickly as possible, and ask for any further information needed.
- The Fedora Board will take a rapid "consensus vote."
- The consensus vote essentially answers the question, "Can the community set up this domain?"
- In most cases, it's expected the Board will answer "Yes."
- A Board member will file a ticket in the Fedora Infrastructure issue tracker, and send you a link.
- After review, you will be assigned an appropriate subdomain and contacted for required host information.
Note that we cannot guarantee availability of a domain other than *.fedoracommunity.org, nor that we will provide more than one domain for a particular community group.
Communities may purchase their own domains, but only after receiving a trademark license from Red Hat, pursuant to the trademark guidelines.
To use this option, email the fedora-advisory-board with your request, before you purchase any domain. The Fedora Board will respond as quickly as possible, consider the request, and arrange for a license agreement as appropriate.
In all cases, community domains must adhere to the Fedora trademark guidelines, and if they choose to display a Fedora logo consistent with those guidelines, they must also adhere to the Fedora logo usage guidelines.
- Examples of costs that would not be reasonable and expected include unusually high extra registration fees imposed by a locality, or prices for a domain demanded by a current owner.
- This is very much like the matrimonial audience question, "Is there any reason why these two shall not be joined...?" Absent a good reason not to approve the domain, requests should be granted. Reasons to deny might include lack of clear domain ownership or good faith, or perceived intent to disparage, for example.