Answers.Body: <p>You can pick anything you want as the domain name. I sense that these answers could get hilarious. Some suggestions from me (others please add your own):</p>
  
  <ul>
  <li><a href="http://lolcats.com" rel="nofollow noreferrer">lolcats.com</a></li>
  <li><a href="http://shouldiblamecaching.com" rel="nofollow noreferrer">shouldiblamecaching.com</a></li>
  <li><a href="http://dotcom.com" rel="nofollow noreferrer">dotcom.com</a></li>
  <li><a href="http://3.141592653589793238462643383279502884197169399375105820974944592.com" rel="nofollow noreferrer">3.141592653589793238462643383279502884197169399375105820974944592.com</a></li>
  <li><a href="http://thelongestdomainnameintheworldandthensomeandthensomemoreandmore.com" rel="nofollow noreferrer">thelongestdomainnameintheworldandthensomeandthensomemoreandmore.com</a></li>
  </ul>
  
  <p>But of those, lolcats.com says "extension developer" to me the most:</p>
  
  <p><a href="https://i.sstatic.net/WuSkU.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/WuSkU.jpg" alt="enter image description here"></a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-28T00:43:22.570Z
Answers.Text: RFC2606: `org.example`
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-10T03:49:48.350Z
Answers.LastActivityDate: 2017-02-11T14:05:20.253Z
Answers.LastEditDate: 2017-02-11T14:05:20.253Z
Answers.UserDisplayName: Coleman
Body: <p>I'm getting started with creating extensions and I see that each extension needs a "full name" or "fully qualified name" or "key", which often serves as the name of the git repository too. I see that the domain names used in these fully qualified names are either (1) <code>civicrm.org</code> or (2) the domain name of the development shop creating the extension. </p>
  
  <p>I'm not currently part of a development shop, but I'd like to create an extension which I can share with others later on. How should I pick a domain name to use within my extension's fully qualified name?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-11T02:00:04.143Z
Comments.Text: But seriously, you can just call it org.civicrm.myextension
Comments.UserDisplayName: Coleman
Tags: <extension><civix>
Title: What domain name should I use for my extension's fully qualified name?
ThreadText: # What domain name should I use for my extension's fully qualified name?
  
  (Asked by: username_0 on 2017-02-09)
  
  I'm getting started with creating extensions and I see that each extension needs a "full name" or "fully qualified name" or "key", which often serves as the name of the git repository too. I see that the domain names used in these fully qualified names are either (1) `civicrm.org` or (2) the domain name of the development shop creating the extension.
  
  I'm not currently part of a development shop, but I'd like to create an extension which I can share with others later on. How should I pick a domain name to use within my extension's fully qualified name?
  
  **Tags:** extension, civix
  
  > **Comments:**
  > **username_1**: But seriously, you can just call it org.civicrm.myextension  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-02-10. Score: 1
  
  You can pick anything you want as the domain name. I sense that these answers could get hilarious. Some suggestions from me (others please add your own):
  
  * [lolcats.com](http://lolcats.com)
  * [shouldiblamecaching.com](http://shouldiblamecaching.com)
  * [dotcom.com](http://dotcom.com)
  * [3.141592653589793238462643383279502884197169399375105820974944592.com](http://3.141592653589793238462643383279502884197169399375105820974944592.com)
  * [thelongestdomainnameintheworldandthensomeandthensomemoreandmore.com](http://thelongestdomainnameintheworldandthensomeandthensomemoreandmore.com)
  
  But of those, lolcats.com says "extension developer" to me the most:
  
  [![enter image description here](https://i.sstatic.net/WuSkU.jpg)](https://i.sstatic.net/WuSkU.jpg)
  
  > **Comments:**
  > **username_2**: RFC2606: `org.example`  
  
  ---
  
  