Merge lp:~cjohnston/summit/adding-tons-of-docs into lp:summit

[Chris Johnston]

adding more docs

[Chris Johnston (cjohnston)]

review: Approve

=== added directory 'dev-docs'
=== added file 'dev-docs/Makefile'
--- dev-docs/Makefile	1970-01-01 00:00:00 +0000
+++ dev-docs/Makefile	2012-05-14 01:12:18 +0000
@@ -0,0 +1,153 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+PAPER         =
+BUILDDIR      = _build
+
+# Internal variables.
+PAPEROPT_a4     = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+# the i18n builder cannot share the environment and doctrees with the others
+I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
+
+help:
+	@echo "Please use \`make <target>' where <target> is one of"
+	@echo "  html       to make standalone HTML files"
+	@echo "  dirhtml    to make HTML files named index.html in directories"
+	@echo "  singlehtml to make a single large HTML file"
+	@echo "  pickle     to make pickle files"
+	@echo "  json       to make JSON files"
+	@echo "  htmlhelp   to make HTML files and a HTML help project"
+	@echo "  qthelp     to make HTML files and a qthelp project"
+	@echo "  devhelp    to make HTML files and a Devhelp project"
+	@echo "  epub       to make an epub"
+	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
+	@echo "  text       to make text files"
+	@echo "  man        to make manual pages"
+	@echo "  texinfo    to make Texinfo files"
+	@echo "  info       to make Texinfo files and run them through makeinfo"
+	@echo "  gettext    to make PO message catalogs"
+	@echo "  changes    to make an overview of all changed/added/deprecated items"
+	@echo "  linkcheck  to check all external links for integrity"
+	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
+
+clean:
+	-rm -rf $(BUILDDIR)/*
+
+html:
+	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
+
+dirhtml:
+	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
+
+singlehtml:
+	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
+	@echo
+	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
+
+pickle:
+	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
+	@echo
+	@echo "Build finished; now you can process the pickle files."
+
+json:
+	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+	@echo
+	@echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
+	@echo
+	@echo "Build finished; now you can run HTML Help Workshop with the" \
+	      ".hhp project file in $(BUILDDIR)/htmlhelp."
+
+qthelp:
+	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
+	@echo
+	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
+	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/SummitSchedulerDeveloper.qhcp"
+	@echo "To view the help file:"
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/SummitSchedulerDeveloper.qhc"
+
+devhelp:
+	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
+	@echo
+	@echo "Build finished."
+	@echo "To view the help file:"
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/SummitSchedulerDeveloper"
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/SummitSchedulerDeveloper"
+	@echo "# devhelp"
+
+epub:
+	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+	@echo
+	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo
+	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+	@echo "Run \`make' in that directory to run these through (pdf)latex" \
+	      "(use \`make latexpdf' here to do that automatically)."
+
+latexpdf:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through pdflatex..."
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+	@echo
+	@echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+	@echo
+	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+texinfo:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo
+	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
+	@echo "Run \`make' in that directory to run these through makeinfo" \
+	      "(use \`make info' here to do that automatically)."
+
+info:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo "Running Texinfo files through makeinfo..."
+	make -C $(BUILDDIR)/texinfo info
+	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
+
+gettext:
+	$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
+	@echo
+	@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
+
+changes:
+	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
+	@echo
+	@echo "The overview file is in $(BUILDDIR)/changes."
+
+linkcheck:
+	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
+	@echo
+	@echo "Link check complete; look for any errors in the above output " \
+	      "or in $(BUILDDIR)/linkcheck/output.txt."
+
+doctest:
+	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+	@echo "Testing of doctests in the sources finished, look at the " \
+	      "results in $(BUILDDIR)/doctest/output.txt."

=== added directory 'dev-docs/_build'
=== added directory 'dev-docs/_static'
=== added directory 'dev-docs/_templates'
=== added file 'dev-docs/conf.py'
--- dev-docs/conf.py	1970-01-01 00:00:00 +0000
+++ dev-docs/conf.py	2012-05-14 01:12:18 +0000
@@ -0,0 +1,242 @@
+# -*- coding: utf-8 -*-
+#
+# Summit Scheduler Developer documentation build configuration file, created by
+# sphinx-quickstart on Fri May 11 15:57:16 2012.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.insert(0, os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = []
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'Summit Scheduler Developer'
+copyright = u'2012, Chris Johnston'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '1.x'
+# The full version, including alpha/beta/rc tags.
+release = '1.x'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+html_theme = 'default'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+#html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'SummitSchedulerDeveloperdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+latex_elements = {
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'SummitSchedulerDeveloper.tex', u'Summit Scheduler Developer Documentation',
+   u'Chris Johnston', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('index', 'summitschedulerdeveloper', u'Summit Scheduler Developer Documentation',
+     [u'Chris Johnston'], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
+
+
+# -- Options for Texinfo output ------------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+  ('index', 'SummitSchedulerDeveloper', u'Summit Scheduler Developer Documentation',
+   u'Chris Johnston', 'SummitSchedulerDeveloper', 'One line description of project.',
+   'Miscellaneous'),
+]
+
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
+
+# If false, no module index is generated.
+#texinfo_domain_indices = True
+
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'

=== added file 'dev-docs/index.rst'
--- dev-docs/index.rst	1970-01-01 00:00:00 +0000
+++ dev-docs/index.rst	2012-05-14 01:12:18 +0000
@@ -0,0 +1,22 @@
+.. Summit Scheduler Developer documentation master file, created by
+   sphinx-quickstart on Fri May 11 15:57:16 2012.
+   You can adapt this file completely to your liking, but it should at least
+   contain the root `toctree` directive.
+
+Welcome to Summit Scheduler Developer's documentation!
+======================================================
+
+Contents:
+
+.. toctree::
+   :maxdepth: 2
+
+
+
+Indices and tables
+==================
+
+* :ref:`genindex`
+* :ref:`modindex`
+* :ref:`search`
+

=== added file 'dev-docs/installing.rst'
--- dev-docs/installing.rst	1970-01-01 00:00:00 +0000
+++ dev-docs/installing.rst	2012-05-14 01:12:18 +0000
@@ -0,0 +1,151 @@
+==================
+Installing Summit
+==================
+
+Before you start hacking on summit, you need to first setup your environment.
+We're going to set it up without breaking anything else in your current.
+
+
+Requirements
+------------
+To get started, you'll need:
+ * Python 2.6 (greater than 2.6.1)
+ * virtualenv
+
+virtualenv
+~~~~~~~~~~
+`virtualenv <http://pypi.python.org/pypi/virtualenv>`_ is a tool to create
+isolated Python environments.  We don't want to install packages system-wide
+because that can create quite a mess.  The following command will install the
+required development files on Ubuntu or, if you're running a recent version,
+you can `install them automatically <apt:python-virtualenv>`_::
+
+    sudo apt-get install python-virtualenv
+
+virtualenv is the only Python package you need to install system-wide.
+Everything else goes in a virtual environment.
+
+virtualenvwrapper
+~~~~~~~~~~~~~~~~~
+
+`virtualenvwrapper <http://www.doughellmann.com/docs/virtualenvwrapper/>`_
+is a set of shell functions that make virtualenv easy to work with.
+
+For Ubuntu Maverick Meerkat and above, `install virtualenvwrapper via apt
+<apt:virtualenvwrapper>`_::
+
+    sudo apt-get install virtualenvwrapper
+
+Once installed, ``exec bash`` and you're set to start!
+
+For earlier releases, install it like this::
+
+    wget http://bitbucket.org/dhellmann/virtualenvwrapper/raw/f31869779141/virtualenvwrapper_bashrc -O ~/.virtualenvwrapper
+    mkdir ~/.virtualenvs
+
+Then put these lines in your ``~/.bashrc``::
+
+    export WORKON_HOME=$HOME/.virtualenvs
+    source $HOME/.virtualenvwrapper
+
+``exec bash`` and you're set.
+
+.. note:: If you didn't have a ``.bashrc`` already, you should make a
+          ``~/.profile`` too::
+
+            echo 'source $HOME/.bashrc' >> ~/.profile
+
+Grab the source
+---------------
+
+Create the bzr environment for summit with::
+
+    bzr init-repo summit
+    cd summit
+    bzr branch lp:summit trunk
+    bzr branch trunk myfeaturex
+    cd myfeaturex
+
+From now on, you can simply `cd trunk && bzr pull` when you want to update your
+trunk.
+
+Getting Packages
+----------------
+
+Now we're ready to go, so create an environment for summit::
+
+    mkvirtualenv --no-site-packages summit
+
+That creates a clean environment named summit.  You can get out of the
+environment by restarting your shell or calling ``deactivate``.
+
+To get back into the summit environment later, type::
+
+    workon summit  # requires virtualenvwrapper
+
+.. note:: If you want to use a different Python binary, pass the path to
+          mkvirtualenv with ``--python``::
+
+            mkvirtualenv --python=/usr/bin/python2.6 --no-site-packages summit
+
+Finish the install
+~~~~~~~~~~~~~~~~~~
+
+From inside your activated virtualenv, run::
+
+    pip install -r requirements.txt
+
+pip installs all the dependencies with the exact revisions as our production
+environment.
+
+
+Settings
+--------
+
+Most of summit is already configured in ``ubuntu_settings.py``, ``linaro_settings.py`` and ``settings.py``, but there's some
+things you need to configure locally.  All your local settings go into
+``local_settings.py``. Just copy ``local_settings.py.sample`` to create
+``local_settings.py`` and everything should run fine.
+
+Get themes
+----------
+
+Get setup for the themes for Ubuntu and Linaro::
+
+    ./manage.py init-summit
+    ./manage.py pullapps
+
+Database
+--------
+
+Let Django sync up the database schema for you and run the migrations::
+
+    ./manage.py syncdb
+    ./manage.py migrate
+
+Run the Server
+--------------
+
+If you've gotten the system requirements, downloaded the source code, set up
+your virtualenv, and configured your settings and database, you're good to go.
+Summit is now split into two different 'sites,' Ubuntu and Linaro. You will
+need to call the proper settings for the site you wish to run.
+To run the server::
+
+    python manage.py runserver --settings ubuntu_settings
+    python maange.py runserver --settings linaro_settings
+
+Contact
+-------
+
+Come talk to us on irc://irc.freenode.net/#ubuntu-website if you have questions,
+issues, or compliments.
+
+Testing
+-------
+
+The quick way to run summit's tests::
+
+    ./manage.py test
+    
+Make sure to write tests for all new code your write and all the tests pass.

=== modified file 'docs/index.rst'
--- docs/index.rst	2012-04-27 15:12:58 +0000
+++ docs/index.rst	2012-05-14 01:12:18 +0000
@@ -4,13 +4,17 @@
    contain the root `toctree` directive.
 
 Welcome to The Summit Scheduler documentation!
-==================================
+==============================================
+
+The Summit Scheduler is a highly agile scheduling solution for conferences. Built originally for use at Ubuntu Developer Summits, the Summit Scheduler is now also used by Linaro at Linaro Connect and at the Linux Plumbers Conference.
+
+If you are interested in using the Summit Scheduler at your conference, please contact Chris Johnston <[e-mail]>.
 
 Contents:
 
 .. toctree::
-   :numbered:
    
+   running
    using
    scheduling
    lead

=== modified file 'docs/lead.rst'
--- docs/lead.rst	2012-02-29 13:35:15 +0000
+++ docs/lead.rst	2012-05-14 01:12:18 +0000
@@ -1,6 +1,6 @@
-==================
+======================
 Track Lead Permissions
-==================
+======================
 
 **Managing Meeting Proposals**
 

=== added file 'docs/running.rst'
--- docs/running.rst	1970-01-01 00:00:00 +0000
+++ docs/running.rst	2012-05-14 01:12:18 +0000
@@ -0,0 +1,146 @@
+==================
+Running a Summit
+==================
+
+----------------
+Create a Summit
+----------------
+
+In the Summit Scheduler
+-----------------------
+
+**Name**
+
+This field will become the URL of the summit. May only contain lowercase letters, numbers and hyphens.
+
+**Title**
+
+The display name of your summit. May contain uppercase and lowercase letters and numbers.
+
+**Description**
+
+A description of the event. You may use markdown styling.
+
+**Etherpad**
+
+The Summit Scheduler uses etherpad for taking notes during meetings. Please provide the base URL for the etherpad instance you would like to use.
+
+**QR**
+
+If your summit has a mobile application to display the schedule, you may enter the URL to the QR image here.
+
+**Hashtag**
+
+This is useful if you wish to display a twitter feed of a certain hashtag on the Summit page.
+
+**State**
+
+ * Sponsorship Requests  -  During this state users will be able to apply for sponsorship to the summit event.
+ * Sponsorship Reviews  -  This status will turn off the ability for users to request sponsorship to your summit and turn on the ability for a defined group of users to review the sponsorship requests and vote on them.
+ * Scheduling  -  This status is what should be used prior to and during the summit. It will give users the ability to propose new meetings and mark themselves as attending meetings.
+ * Public  -  This status should be set after the event is over. This will prevent users from being able to create new meetings and remove other features that are used prior to and during a summit.
+ 
+**Help**
+
+This field is used for displaying a message across the bottom of each page. Markdown styling is supported.
+
+**Sites**
+
+The Summit Scheduler is capable of running multiple different sites off of one code base while appearing to be completely seperate sites. This field is what defines which site the summit will appear on. Multiple selections are allowed for co-hosted events.
+
+**Managers**
+
+This field allows you to define users who will have manager permissions. For more information on the permissions given to a manager, view the Summit Scheduler Permissions page.
+
+**Schedulers**
+
+This field allows you to define users who are allowed to have scheduler permissions. For more information on the permissions given to a scheduler, view the Summit Scheduler Permissions page.
+
+**Tracks**
+
+ * Title  -  The display title of your track.
+ * Slug  -  The track slug may contain lowercase letters, numbers, and hyphens.
+ * Color  -  Adding a color allows for an obvious differentiation between different tracks.
+ * Description  -  A brief description of the track. This field supports markdown styling.
+ * Allow adjacent sessions  -  By default, the Summit Scheduler does not allow two sessions from the same track to be scheduled in the same room. This is to encourage participants to get up, move around, and have more interaction with other participants. If you would like to allow the Summit Scheduler to have sessions from the same track back to back in the same room, check this box.
+ * Delete  -  Check this box if you want to delete an already created track
+ 
+**Sprint**
+
+Add the export URL for the Launchpad sprint that was created for this event.
+
+In Launchpad
+------------
+
+------
+Rooms
+------
+
+**Name**
+
+Name of the room. May contain lowercase letters and numbers.
+
+**Title**
+
+Display title of the room. May contain uppercase and lowercase letters, numbers and spaces.
+
+**Type**
+
+ * Openly Scheduled  -  May contain any meeting other than a plenary.
+ * Plenary Events  -  May contain only plenaries.
+ * Closed  -  Room that will not be used.
+ * Private  -  A private room that is not displayed to people without the correct permissions or attendees to private meetings in the room.
+
+**Size**
+
+The number of people the room can hold.
+
+**Tracks**
+
+You are able to set the room up so that only certain tracks will be scheduled in the room. This is helpful for special setups for things like hacking sessions.
+
+**Icecast URL**
+
+This can be the URL to any type of audio or audio video link. Ex. Icecast, Google Hangouts
+
+**IRC Channel**
+
+The IRC channel name without the hash (#).
+
+**Has Dial In**
+
+If this room has dial in capabilities, meetings that require dial in will be scheduled here.
+
+**Availability**
+
+General starting and ending availability of the room. Must be entered in UTC time.
+
+**Busy**
+
+Used to set certain time periods throughout the sprint in which this room is not available.
+
+------------
+Track Leads
+------------
+
+-------
+Slots
+-------
+
+------
+Crew
+------
+
+----------------
+Crons
+----------------
+
+**Auto Schedule**
+
+**Reschedule**
+
+**Dead blueprints**
+
+----------------
+Track Lead
+----------------

=== modified file 'docs/scheduler.rst'
--- docs/scheduler.rst	2012-02-29 13:35:15 +0000
+++ docs/scheduler.rst	2012-05-14 01:12:18 +0000
@@ -1,5 +1,17 @@
-==================
-Scheduler Permissions
-==================
+============================
+Summit Scheduler Permissions
+============================
 
 Coming Soon!
+
+----------------
+Scheduler
+----------------
+
+----------------
+Manager
+----------------
+
+----------------
+Track Lead
+----------------

=== modified file 'docs/scheduling.rst'
--- docs/scheduling.rst	2012-05-05 00:48:19 +0000
+++ docs/scheduling.rst	2012-05-14 01:12:18 +0000
@@ -1,14 +1,14 @@
-==================
+====================
 Scheduling a Meeting
-==================
+====================
 
 You have two options to schedule a meeting. 
 
 You can either create a meeting in Summit or by using a blueprint in Launchpad.
 
-------------------
+----------------------------
 Creating a Meeting in Summit
-------------------
+----------------------------
 
 Creating a meeting in Summit is now easier than ever. All you need to do is fill out a simple form and the meeting will be created and scheduled for you automaticaly.
 
@@ -16,20 +16,20 @@
 
 .. _video: http://www.youtube.com/watch?v=Jr25brEMOuA
 
-------------------
+--------------------------------
 Creating a Meeting in Launchpad
-------------------
+--------------------------------
 
 If you've already defined a blueprint that needs discussing you can register it. You can also create one from scratch.
 
 Using an Existing Engineering Blueprint
----------------
+-------------------------------------------
 
 If your blueprint can fit into a single session, this is the route to choose. After creating your blueprint you may select the "Propose for sprint" option when viewing the blueprint in Launchpad.
 
 
 Creating a "Scheduling Blueprint"
----------------
+------------------------------------
 
 If your engineering blueprint is too big for a single session, you can break it up by using multiple "scheduling blueprints".
 
@@ -54,7 +54,7 @@
 The video is old so ignore the beginning about the wiki and just pay attention to the part where Jorge talks about Launchpad.
 
 Filling Out the Blueprint Fields
---------------
+-----------------------------------
 
 The following are fields on the "Register a blueprint" page.
 
@@ -106,7 +106,7 @@
 If your blueprint is not on the schedule during the week before the summit, please ask your track lead to approve it. If they don't have it then it means you didn't submit it to the correct sprint (see the video). Track leads will be approving specs on a regular basis, so if you don't see your meetings on the schedule it's up to YOU to bother the track lead.
 
 Ubuntu Developer Summit
----------------
+-----------------------
 
 Jono Bacon and Michael Hall keep an eye on the incoming specs for UDS, so if a track lead is particularly swamped we help keep the submissions going smoothly, but it helps tremendously when you check.
 

=== modified file 'docs/using.rst'
--- docs/using.rst	2012-02-29 13:14:51 +0000
+++ docs/using.rst	2012-05-14 01:12:18 +0000
@@ -1,18 +1,18 @@
-==================
+==========================
 Using The Summit Scheduler
-==================
+==========================
 
 The Summit Scheduler is a web tool utilized at Ubuntu Developer Summit and Linaro Connect.
 
 Registering to Attend a Summit
-==========
+==============================
 In order to use Summit for your personal schedule, you will need to register in Launchpad as attending the summit. To do this, click the "Register in Launchpad" link on the main page for the summit.
 
 *Note*: Once you register, it may take up to 20 minutes for you to be able to use Summit.
 
 
 Signing up to Attend a Meeting
-==========
+==============================
 After you have registered yourself as attending a Summit, you have the ability to "attend meetings." Signing yourself up to attend meetings will create your own personal schedule.
 
 To sign up to attend a meeting you have 2 options:
@@ -32,14 +32,14 @@
 To subscribe to a meeting in Summit, click on the meeting name and you will be sent to the meeting page. In the navigation near the top, you will see a link called ""Attend this meeting." Shortly after clicking this link, the meeting will show up in your personal schedule.
 
 Agenda View
-==========
+===========
 
 When you are logged into Summit, the agenda view will show your personal schedule. All of the meetings have a star infront of the name of the meeting. If this star is grey you are not subscribed to the meeting. If the star is gold, you are subscribed.
 
 If you mouseover the meeting name, you will see the details about the meeting. This includes the meeting description, participants, and tracks. Any participants with a red star next to their name are "Participation essential."
 
 Wide Screen View
-==========
+================
 
 The Wide Screen View is the traditional schedule view. This view is no longer recommended for use on personal computers.
 
@@ -51,6 +51,6 @@
 The Track View will show you all of the meetings for a particular track.
 
 Room View
-==========
+=========
 
 The Room View will show you all of the meetings for a particular room.