Naming Recap

This is a summary of all the decisions we have made so far with regard to naming.

Brand and Product Naming

• Decisions we have made....
  • The brand name is Chandler™.
  • Chandler: For describing the entire suite of products.
  • Chandler Desktop: When referring to the desktop client.
  • Chandler Server: When referring to the download-and-run-it-yourself Cosmo.
  • Chandler Hub: When referring to the hosted service.
  • Extending Chandler Desktop: When making references to the extensibility of the Chandler Desktop (writing plugins).

• Per Mimi's suggestion - as part of the landing page design and the content creation we will determine based on context when we use Chandler and when we use Chandler Project. We don't need to close on those rules now to move forward with the naming decisions.

Domain Name (and related)

• Decisions we have made...
  • Our product site will be at the domain www.chandlerproject.org.
  • We will not have a separate domain for the service/cosmo ui.
  • We are going to purchase www.chandlerhub.org and www.chanderserver.org as well - katie filed ticket.
  • Email addresses and mailing lists will remain at www.osafoundation.org.
  • Then landing pages will be at www.chandlerproject.org.
  • We will also have general audience blog at blog.chandlerproject.org.
  • Things we are not moving - pylucene, m2 crypto.
  • We will not create a news channel.

• Issues still open...
  • Pieter suggested some other domains that would redirect to www.chandlerproject.org - do we purchase all those?
    • chandler-project.com,org,net,info
    • chandler-hub.com,org,net,info
    • chandler-server,com,org,net,info
  • Should we move the wiki to the new domain wiki.chandlerproject.org
    • The foundation site will contain the mission statement, info about staff (bios), job descriptions and other info about the foundation.
    • We will link prominently back to the foundation site from the landing page and wiki templates - currently iterating on this
    • I think we are close enough to go forward with the wiki decision unless there are any other reasons we should not.
  • Still need a decision on moving the developer tools:
    • svn.osafoundation.org
    • builds.osafoundation.org
    • bugzilla, lxr, etc
  • Other project sites:
    • pyicu.osafoundation.org
  • Do we have a separate service status site? chandlerservice.info?
  • Do we have a separate service status blog?
  • Do we use a new blog back-end?
  • Do we provide BitTorrent^? or other non-http downloads
  • What dynamic content do we use. Do we have mirror sites for downloads?
  • Do we use sub sites or do we use a path?

-- SheilaMooney - 03 Mar 2007