dev/null |binary docs/_templates/indexcontent.html | 75 ++++ docs/conf.py | 25 + docs/contents.rst | 18 docs/copyright.rst | 13 docs/index.rst | 37 +- docs/license.rst | 685 ++++++++++++++++++++++++++++++++++++++ docs/main/Architecture.rst | 19 - docs/main/Consumers.rst | 8 docs/main/Features.rst | 72 +++ docs/main/Feeds.rst | 43 +- docs/main/GettingStarted.rst | 9 docs/main/Messaging.rst | 11 docs/main/Middleware.rst | 7 docs/main/MokshaApplications.rst | 4 docs/main/Vision.rst | 14 docs/main/Widgets.rst | 9 17 files changed, 988 insertions(+), 61 deletions(-)
New commits: commit 1d6c4ec363010966a1ff66c415719a620978f60c Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:23:36 2009 -0500
Remove some lame Mac DS_Store files :(
diff --git a/moksha/api/menus/static/css/.DS_Store b/moksha/api/menus/static/css/.DS_Store deleted file mode 100755 index 5008ddf..0000000 Binary files a/moksha/api/menus/static/css/.DS_Store and /dev/null differ diff --git a/moksha/api/menus/static/images/.DS_Store b/moksha/api/menus/static/images/.DS_Store deleted file mode 100644 index 5008ddf..0000000 Binary files a/moksha/api/menus/static/images/.DS_Store and /dev/null differ diff --git a/moksha/widgets/container/static/css/elements/.DS_Store b/moksha/widgets/container/static/css/elements/.DS_Store deleted file mode 100644 index 2cae975..0000000 Binary files a/moksha/widgets/container/static/css/elements/.DS_Store and /dev/null differ diff --git a/moksha/widgets/container/static/css/elements/skindef/.DS_Store b/moksha/widgets/container/static/css/elements/skindef/.DS_Store deleted file mode 100644 index 5008ddf..0000000 Binary files a/moksha/widgets/container/static/css/elements/skindef/.DS_Store and /dev/null differ
commit 5a6550107820fda4f8a4990ee56d01832931989b Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:23:15 2009 -0500
Improve our feed documentation
diff --git a/docs/main/Feeds.rst b/docs/main/Feeds.rst index ccbe062..b6e7bdb 100644 --- a/docs/main/Feeds.rst +++ b/docs/main/Feeds.rst @@ -14,48 +14,47 @@ automatically use a local sqlite database cache. The Moksha Feed Widget ----------------------
-.. code-block:: python - - from moksha.api.widgets.feed import Feed +.. autoclass:: moksha.api.widgets.feed.Feed + :members:
.. widgetbrowser:: moksha.widgets.demos.FeedDemo :tabs: demo, source, template :size: large
+Using the Feed widget +~~~~~~~~~~~~~~~~~~~~~
-API usage ---------- +.. code-block:: python
-The Feed object can be utilize in many ways. + from moksha.api.widgets.feed import Feed + feed = Feed('myfeed') + feed(url='http://lewk.org/rss')
Rendering a url with the Feed object ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. code-block:: python
- from moksha.api.widgets.feed import Feed feed = Feed('myfeed') feed(url='http://lewk.org/rss')
-:Note: Usually you would instantiate a single Feed object somewhere in your project, and just call it with a `url` when rendering it in your templates. +.. note:: + Usually you would instantiate a single Feed object somewhere in your + project, and just call it with a `url` when rendering it in your templates.
Subclassing ~~~~~~~~~~~
-You can easily subclass the Feed widget and provide your own url. - .. code-block:: python
- from moksha.api.widgets.feed import Feed - class MyFeed(Feed): url = 'http://foo.com/feed.xml'
- myfeed = MyFeed('myfeed') - myfeed() # renders the widget. usually done in the template. + myfeed = MyFeed() + myfeed() # renders the widget, usually done in the template
-As a child Widget -~~~~~~~~~~~~~~~~~ +As ToscaWidget children +~~~~~~~~~~~~~~~~~~~~~~~
By defining your Feeds as children to a widget, ToscaWidgets will automatically handle setting a unique id for your Feed object, as well as giving you the @@ -74,13 +73,8 @@ ability access it in your template from the `c` context object. As a generator ~~~~~~~~~~~~~~
-You can also utilize the Feed widget as a generator, giving you the ability -to iterate over the entries as necessary. - .. code-block:: python
- from moksha.api.widgets.feed import Feed - feed = Feed('myfeed', url='http://foo.com/feed.xml') print '%d entries' % feed.num_entries() for entry in feed.iterentries(): @@ -105,4 +99,9 @@ Here is an example of using the feed cache to manually fetch a feed. for entry in feed.entries: print entry
-:Note: The moksha.feed_cache object is a :class:`paste.registry.StackedObjectProxy` instance, and is setup by the :class:`moksha.middleware.MokshaMiddleware` before each request reaches your application. Thus, it only works during requests and cannot be used without using the MokshaMiddleware. +.. note:: + The moksha.feed_cache object is a + :class:`paste.registry.StackedObjectProxy` instance, and is setup by the + :class:`moksha.middleware.MokshaMiddleware` before each request reaches + your application. Thus, it only works during requests and cannot be + used without using the MokshaMiddleware.
commit dedfdc9fd0ecdf7e3b2a4ef57b2093336140ef49 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:16:44 2009 -0500
Lots of documentation improvements and refactoring.
diff --git a/docs/index.rst b/docs/index.rst index e41ef10..511db55 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -7,29 +7,28 @@ Moksha is a platform for creating live collaborative applications. It provides a layer of cohesion and collaboration between existing applications, services, and communities.
-The Vision ----------- +** Link to wiki, tickets, mailing lists, etc... +** be *the* homepage, let trac just be for tickets and wiki. + +:Homepage: http://moksha.fedorahosted.org +:Demo Dashboard: http://65.49.60.166 + +Vision +------
.. toctree:: - :maxdepth: 1 + :maxdepth: 2
- main/Introduction - main/MokshaPlatform - main/DataAggregation - main/DataInterpretation - main/DataPersistence - main/DataVisualization - main/Scalability + main/Vision
Architecture ------------
.. toctree:: - :maxdepth: 1 + :maxdepth: 2 + + main/Architecture
- main/Features - main/Technology - main/Infrastructure
Getting Started --------------- @@ -55,6 +54,7 @@ Messaging .. toctree:: :maxdepth: 1
+ main/Messaging main/MessageBrokers main/Topics main/Consumers @@ -69,6 +69,7 @@ Widgets main/Feeds main/LiveWidget main/MokshaContainerWidgets + main/Widgets .. Model ----- @@ -106,3 +107,11 @@ Third-party Documentation * `TurboGears http://turbogears.org/2.0/docs/index.html`_ * `ToscaWidgets http://toscawidgets.org/documentation`_ * `SQLAlchemy http://www.sqlalchemy.org/docs/05`_ + +Indices and tables +================== + +* :ref:`genindex` +* :ref:`modindex` +* :ref:`search` + diff --git a/docs/main/Architecture.rst b/docs/main/Architecture.rst index 0972325..53d72b8 100644 --- a/docs/main/Architecture.rst +++ b/docs/main/Architecture.rst @@ -1,12 +1,9 @@ -Architecture Goals -================== +Moksha Architecture +===================
-- `WSGI http://wsgi.org`_ (`PEP 333 http://www.python.org/dev/peps/pep-0333/`_) compliant application and `middleware http://www.wsgi.org/wsgi/Middleware_and_Utilities`_ stack -- A real-time messaging hub using the `Advanced Message Queuing Protocol (AMQP) http://http://amqp.org/`_ -- Highly-scalable `Orbited http://orbited.org`_ servers for asynchronous real-time web-browser<->server communication. -- A powerful widget creation API that trivializes the creation of modular, scalable, reusable real-time widgets that can efficiently acquire data from a variety of sources. -- A data aggregation layer that handles fetching feeds for the widgets, caching - them, and sending them to Orbited, and via AMQP messages. -- A resource layer that trivializes interacting with external services in an intelligent and efficient manner. -- A self-scaling architecture that can adapt to a variety of infrastructure environments. -- A highly-scalable plugin infrastructure that transparently handles initializing, dispatching, and manipulating applications and widgets -- allowing people to rapidly innovate without worrying about the under/over-lying software architecture. +.. toctree:: + :maxdepth: 2 + + Features + Technology + Infrastructure diff --git a/docs/main/Consumers.rst b/docs/main/Consumers.rst index 64eaaff..2f411d1 100644 --- a/docs/main/Consumers.rst +++ b/docs/main/Consumers.rst @@ -20,9 +20,11 @@ Creating def consume(self, message): print message
-:Note: The :class:`MokshaHub` currently executes each consumer in their own - Thread, so be sure to employ thread-safety precausions when implementing - your :class:`Consumer`. +.. note:: + + The :class:`MokshaHub` currently executes each consumer in their own + Thread, so be sure to employ thread-safety precausions when implementing + your :class:`Consumer`.
Installing ---------- diff --git a/docs/main/Features.rst b/docs/main/Features.rst index 256782a..8088b94 100644 --- a/docs/main/Features.rst +++ b/docs/main/Features.rst @@ -3,3 +3,75 @@ Moksha Features ===============
.. image:: ../_static/moksha-features.png + +WSGI Middleware Stack +--------------------- +Moksha provides a `WSGI http://wsgi.org`_ (`PEP 333 http://www.python.org/dev/peps/pep-0333/`_) compliant application and `middleware http://www.wsgi.org/wsgi/Middleware_and_Utilities`_ stack + +Messaging Hub +------------- + +Moksha provides a message hub that allows for other applications, services, or users to communicate over a low-latency topic-based publish/subscribe message bus. It's designed in such a way to facilitate a variety of different message flows, allowing for a combination of different message queueing brokers and protocols. + +Out of the box, Moksha utilizes `MorbidQ http://www.morbidq.com/`_, a lightweight message queue for bundled deployment, for it's message queueing needs. With a 1-line change to Moksha's configuration file, you can integrate it with an existing `AMQP http://amqp.org/`_ broker, such as `Qpid http://incubator.apache.org/qpid/`_ or `RabbitMQ http://rabbitmq.com`_. + +Low-latency Browser Socket +-------------------------- + +Moksha integrates with `Orbited http://orbited.org`_, a highly-scalable +server that allows for asynchronous browser <-> server communication. Moksha +then makes it simple to create LiveWidgets_ that can publish and subscribe to +arbitrary message topics in the MokshaHub_. This allows for the creation of +very rich live web applications. + +Plugin Infrastructure +--------------------- + +Moksha offers a highly-scalable plugin infrastructure that transparently +handles initializing, dispatching, manipulating, and scaling applications and +widgets -- allowing people to rapidly innovate without worrying about the +over or under-lying software architecture. + +Widget Creation API +------------------- + +`ToscaWidgets http://toscawidgets.org`_ provides a powerful API for creating +reusable "Widgets", which are essentially just bundles of HTML, JavaScript, +CSS, and render-time logic. The ToscaWidgets WSGI Middleware is also integrated +into Moksha, which handles intelligently injecting Widget resources. + +Moksha also provides a variety of other Widgets, including a LiveWidget_ API +for creating real-time message-driven widgets that can efficiently acquire data +from a variety of sources. + +Resource Connectors +------------------- + +Moksha offers a Resource Layer that trivializes interacting with external +services in an intelligent and efficient manner. + +Highly Scalable Architecture +---------------------------- + +Moksha architecture is self-scaling and can adapt to a variety of +infrastructure environments. + +Expert System +-------------- + +The MokshaHub_ gives you Expert System-like functionality by providing APIs for +interacting with a variety of knowledge bases (SQLAlchemy models, Resource +Connectors, Caches, Message Queues, etc), and can easily monitor and process +incoming data. One could then easily build state-machines, inference engines, +or even forward/backward-chaning rule-driven expert systems. + +Moksha also provides a simple yet powerful API for creating DataStreamers_ that +can do basically anything at anytime. It allows for the easy scripting of +periodic tasks such as fetching data, polling resources, warming caches, +sending notifications, analyzing databases, etc. For example, Moksha provides +a FeedStream_, that automatically handles fetching, parsing, caching, and +sending notifications for all known feeds at a regular interval. + +These are loaded by the MokshaHub_, and are executed outside of the WSGI +application stack, but they are still able to access the Database, Cache, +MessageHub, etc. diff --git a/docs/main/GettingStarted.rst b/docs/main/GettingStarted.rst index 7fc7774..3a7371b 100644 --- a/docs/main/GettingStarted.rst +++ b/docs/main/GettingStarted.rst @@ -48,7 +48,10 @@ Starting Moksha
$ ./start-moksha
-:Note: This script takes care of setting up your TurboGears2 virtual environment the first time it is run. To drop into the virtualenv manually you can run `source tg2env/bin/activate` to enter it, and `deactivate` to leave it. +.. note:: + This script takes care of setting up your TurboGears2 virtual environment + the first time it is run. To drop into the virtualenv manually you can run + `source tg2env/bin/activate` to enter it, and `deactivate` to leave it.
Stopping Moksha --------------- @@ -64,4 +67,6 @@ Now you can navigate your web browser to the following url:
`http://localhost:8080 http://localhost:8080`_
-:Note: Going to `127.0.0.1` will not work properly with the current Orbited setup, so you must make sure to go to `localhost`. +.. note:: + Going to `127.0.0.1` will not work properly with the current Orbited setup, + so you must make sure to go to `localhost`. diff --git a/docs/main/Middleware.rst b/docs/main/Middleware.rst index 93f9258..7d8d63e 100644 --- a/docs/main/Middleware.rst +++ b/docs/main/Middleware.rst @@ -39,4 +39,9 @@ how it looks in TurboGears2. If you're using Moksha as a stand-alone platform, full_stack, **app_conf) return app
-:Note: It currently requires to be wrapped in the `paste.registry http://pythonpaste.org/modules/registry.html`_ WSGI middleware. TurboGears2 allows us to easily insert middleware directly on top of the raw application, so we then have the ability to use the paste.registry, sessions, and caching. +.. note:: + It currently requires to be wrapped in the `paste.registry + http://pythonpaste.org/modules/registry.html`_ WSGI middleware. + TurboGears2 allows us to easily insert middleware directly on top of the raw + application, so we then have the ability to use the paste.registry, + sessions, and caching. diff --git a/docs/main/MokshaApplications.rst b/docs/main/MokshaApplications.rst index d6aa089..c58207a 100644 --- a/docs/main/MokshaApplications.rst +++ b/docs/main/MokshaApplications.rst @@ -1,5 +1,5 @@ -Moksha Plugins -============== +Moksha Applications +===================
When the :class:`moksha.middleware.MokshaMiddleware` is loaded, it will automatically load all applications and widgets from those entry points,
commit c9cdee9b664579bab93b9176874ddac961071c97 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:15:39 2009 -0500
Add an example intersphinx mapping to our Sphinx config
diff --git a/docs/conf.py b/docs/conf.py index c4f62ad..2a70ec7 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -164,3 +164,9 @@ try: extensions.append("widgetbrowser.sphinx_ext") except: print "Unable to import the `widgetbrowser`. Try doing `cd moksha/widgetbrowser; python setup.py develop` to install it." + +# +# example configuration for intersphinx: refer to the python standard library. +# +#extensions.append('sphinx.ext.intersphinx') +#intersphinx_mapping = {'http://docs.python.org/dev': none}
commit 4380e0c70f77f3be6ca46d86ad6c8ba247497723 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:15:09 2009 -0500
Update our Sphinx config to show the new index, module authors, and warn about the widgetbrowser
diff --git a/docs/conf.py b/docs/conf.py index 4e2bb91..c4f62ad 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -65,7 +65,7 @@ today_fmt = '%B %d, %Y'
# If true, sectionauthor and moduleauthor directives will be shown in the # output. They are ignored by default. -#show_authors = False +show_authors = True
# The name of the Pygments (syntax highlighting) style to use. pygments_style = 'default' @@ -98,17 +98,21 @@ 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 +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 = {} +html_additional_pages = { + 'index': 'indexcontent.html', +} + +#html_split_index = True
# If false, no module index is generated. -#html_use_modindex = True +html_use_modindex = True
# If true, the reST sources are included in the HTML build as _sources/<name>. #html_copy_source = True @@ -155,5 +159,8 @@ code_path = test_path = os.path.dirname(os.path.abspath(__file__)) + os.path.sep # # Enable the ToscaWidgets WidgetBrowser # -import widgetbrowser -extensions.append("widgetbrowser.sphinx_ext") +try: + import widgetbrowser + extensions.append("widgetbrowser.sphinx_ext") +except: + print "Unable to import the `widgetbrowser`. Try doing `cd moksha/widgetbrowser; python setup.py develop` to install it."
commit d85bdb1525b6135fdfe760fce027046b242904a8 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:14:01 2009 -0500
Create a toctree for our widget documentation
diff --git a/docs/main/Widgets.rst b/docs/main/Widgets.rst new file mode 100644 index 0000000..5ceb18a --- /dev/null +++ b/docs/main/Widgets.rst @@ -0,0 +1,9 @@ +Widgets +======= + +.. toctree:: + :maxdepth: 2 + + Feeds + LiveWidget + MokshaContainerWidgets
commit 1d5fd2ece75583ca883d31d5c6407a83e379d6f8 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:13:48 2009 -0500
Create a toctree for our vision documentation
diff --git a/docs/main/Vision.rst b/docs/main/Vision.rst new file mode 100644 index 0000000..b3b031c --- /dev/null +++ b/docs/main/Vision.rst @@ -0,0 +1,14 @@ +The Vision +---------- + +.. toctree:: + :maxdepth: 2 + + Introduction + MokshaPlatform + DataAggregation + DataInterpretation + DataPersistence + DataVisualization + Scalability +
commit 97651d21ffe2f93963531de4bac4c96846862652 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:13:25 2009 -0500
Create a toc tree for our messaging docs
diff --git a/docs/main/Messaging.rst b/docs/main/Messaging.rst new file mode 100644 index 0000000..194bbef --- /dev/null +++ b/docs/main/Messaging.rst @@ -0,0 +1,11 @@ +Messaging +========= + +.. toctree:: + :maxdepth: 2 + + MessageBrokers + Topics + Consumers + DataStreams + MokshaHub
commit 3032b48d10b717162003392fb996705c20b100fd Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:13:05 2009 -0500
Add a new index layout for our documentation
diff --git a/docs/_templates/indexcontent.html b/docs/_templates/indexcontent.html new file mode 100644 index 0000000..73cfca2 --- /dev/null +++ b/docs/_templates/indexcontent.html @@ -0,0 +1,75 @@ +{% extends "defindex.html" %} + +{% block tables %} + <table class="contentstable" align="center"><tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Vision") }}">The Vision</a><br/> + <span class="linkdescr">High-level goals and concepts</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Widgets") }}">Widgets</a><br/> + <span class="linkdescr">Details on creating Widgets</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/GettingStarted") }}">Getting Started</a><br/> + <span class="linkdescr">Instructions for diving in</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Messaging") }}">Messaging</a><br/> + <span class="linkdescr">Information on Moksha's real-time messaging layer</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Middleware") }}">WSGI Middleware</a><br/> + <span class="linkdescr">A description of Moksha's WSGI middleware</span></p> + </td><td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Architecture") }}">The Architecture</a><br/> + <span class="linkdescr">Features of and the technology behind them</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/MokshaApplications") }}">Applications</a><br/> + <span class="linkdescr">Details on creating applications using Moksha</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Development") }}">Development</a><br/> + <span class="linkdescr">A handbook for hacking on and with Moksha</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("main/Deployment") }}">Deployment</a><br/> + <span class="linkdescr">Recipies for efficiently deploying and scaling Moksha</span></p> + <p class="biglink"><a class="biglink" href="http://bit.ly/RICf">Demo Dashboard</a><br/> + <span class="linkdescr">A simple demo Moksha dashboard</span></p> + </td></tr> + </table> + + <p><strong>Indices and tables:</strong></p> + <table class="contentstable" align="center"><tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("modindex") }}">Global Module Index</a><br/> + <span class="linkdescr">quick access to all modules</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("genindex") }}">General Index</a><br/> + <span class="linkdescr">all functions, classes, terms</span></p> + </td><td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("search") }}">Search page</a><br/> + <span class="linkdescr">search this documentation</span></p> + <p class="biglink"><a class="biglink" href="{{ pathto("contents") }}">Complete Table of Contents</a><br/> + <span class="linkdescr">lists all sections and subsections</span></p> + </td></tr> + </table> + + <p><strong>Meta information:</strong></p> + <table class="contentstable" align="center"><tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="https://fedorahosted.org/moksha/newticket">Reporting bugs</a></p> + </td> + <td width="50%"> + <p class="biglink"><a class="biglink" href="https://fedorahosted.org/moksha/report/1">Active Tickets</a></p> + </td></tr> + <tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="https://fedorahosted.org/moksha/timeline">Timeline</a></p> + </td> + <td width="50%"> + <p class="biglink"><a class="biglink" href="https://fedorahosted.org/moksha/roadmap">Roadmap</a></p> + </td></tr> + <tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="http://moksha.fedorahosted.org">Wiki</a></p> + </td> + <td width="50%"> + <p class="biglink"><a class="biglink" href="https://fedorahosted.org/mailman/listinfo/moksha">Mailing List</a></p> + </td></tr> + <tr> + <td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("license") }}">License</a></p> + </td> + <td width="50%"> + <p class="biglink"><a class="biglink" href="{{ pathto("copyright") }}">Copyright</a></p> + </td></tr> + </table> +{% endblock %}
commit dfb677e42fef5d39666fd708561e149be4b85f55 Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:12:40 2009 -0500
Add our license and copyright to our docs
diff --git a/docs/copyright.rst b/docs/copyright.rst new file mode 100644 index 0000000..a81eee5 --- /dev/null +++ b/docs/copyright.rst @@ -0,0 +1,13 @@ +********* +Copyright +********* + + +Moksha and this documentation is: + +Copyright © 2008 Red Hat, Inc. + +----- + +See :ref:`license` for complete license and permissions information. + diff --git a/docs/license.rst b/docs/license.rst new file mode 100644 index 0000000..03331d0 --- /dev/null +++ b/docs/license.rst @@ -0,0 +1,685 @@ +.. _license: + +License +======= + +Moksha is licensed under the GPLv3. + +.. code-block:: none + + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for + software and other kinds of works. + + The licenses for most software and other practical works are designed + to take away your freedom to share and change the works. By contrast, + the GNU General Public License is intended to guarantee your freedom to + share and change all versions of a program--to make sure it remains free + software for all its users. We, the Free Software Foundation, use the + GNU General Public License for most of our software; it applies also to + any other work released this way by its authors. You can apply it to + your programs, too. + + When we speak of free software, we are referring to freedom, not + price. Our General Public Licenses are designed to make sure that you + have the freedom to distribute copies of free software (and charge for + them if you wish), that you receive source code or can get it if you + want it, that you can change the software or use pieces of it in new + free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you + these rights or asking you to surrender the rights. Therefore, you have + certain responsibilities if you distribute copies of the software, or if + you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether + gratis or for a fee, you must pass on to the recipients the same + freedoms that you received. You must make sure that they, too, receive + or can get the source code. And you must show them these terms so they + know their rights. + + Developers that use the GNU GPL protect your rights with two steps: + (1) assert copyright on the software, and (2) offer you this License + giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains + that there is no warranty for this free software. For both users' and + authors' sake, the GPL requires that modified versions be marked as + changed, so that their problems will not be attributed erroneously to + authors of previous versions. + + Some devices are designed to deny users access to install or run + modified versions of the software inside them, although the manufacturer + can do so. This is fundamentally incompatible with the aim of + protecting users' freedom to change the software. The systematic + pattern of such abuse occurs in the area of products for individuals to + use, which is precisely where it is most unacceptable. Therefore, we + have designed this version of the GPL to prohibit the practice for those + products. If such problems arise substantially in other domains, we + stand ready to extend this provision to those domains in future versions + of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. + States should not allow patents to restrict development and use of + software on general-purpose computers, but in those that do, we wish to + avoid the special danger that patents applied to a free program could + make it effectively proprietary. To prevent this, the GPL assures that + patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and + modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of + works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this + License. Each licensee is addressed as "you". "Licensees" and + "recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work + in a fashion requiring copyright permission, other than the making of an + exact copy. The resulting work is called a "modified version" of the + earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based + on the Program. + + To "propagate" a work means to do anything with it that, without + permission, would make you directly or secondarily liable for + infringement under applicable copyright law, except executing it on a + computer or modifying a private copy. Propagation includes copying, + distribution (with or without modification), making available to the + public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other + parties to make or receive copies. Mere interaction with a user through + a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" + to the extent that it includes a convenient and prominently visible + feature that (1) displays an appropriate copyright notice, and (2) + tells the user that there is no warranty for the work (except to the + extent that warranties are provided), that licensees may convey the + work under this License, and how to view a copy of this License. If + the interface presents a list of user commands or options, such as a + menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work + for making modifications to it. "Object code" means any non-source + form of a work. + + A "Standard Interface" means an interface that either is an official + standard defined by a recognized standards body, or, in the case of + interfaces specified for a particular programming language, one that + is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other + than the work as a whole, that (a) is included in the normal form of + packaging a Major Component, but which is not part of that Major + Component, and (b) serves only to enable use of the work with that + Major Component, or to implement a Standard Interface for which an + implementation is available to the public in source code form. A + "Major Component", in this context, means a major essential component + (kernel, window system, and so on) of the specific operating system + (if any) on which the executable work runs, or a compiler used to + produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all + the source code needed to generate, install, and (for an executable + work) run the object code and to modify the work, including scripts to + control those activities. However, it does not include the work's + System Libraries, or general-purpose tools or generally available free + programs which are used unmodified in performing those activities but + which are not part of the work. For example, Corresponding Source + includes interface definition files associated with source files for + the work, and the source code for shared libraries and dynamically + linked subprograms that the work is specifically designed to require, + such as by intimate data communication or control flow between those + subprograms and other parts of the work. + + The Corresponding Source need not include anything that users + can regenerate automatically from other parts of the Corresponding + Source. + + The Corresponding Source for a work in source code form is that + same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of + copyright on the Program, and are irrevocable provided the stated + conditions are met. This License explicitly affirms your unlimited + permission to run the unmodified Program. The output from running a + covered work is covered by this License only if the output, given its + content, constitutes a covered work. This License acknowledges your + rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not + convey, without conditions so long as your license otherwise remains + in force. You may convey covered works to others for the sole purpose + of having them make modifications exclusively for you, or provide you + with facilities for running those works, provided that you comply with + the terms of this License in conveying all material for which you do + not control copyright. Those thus making or running the covered works + for you must do so exclusively on your behalf, under your direction + and control, on terms that prohibit them from making any copies of + your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under + the conditions stated below. Sublicensing is not allowed; section 10 + makes it unnecessary. + + 3. Protecting Users' Legal Rights From Anti-Circumvention Law. + + No covered work shall be deemed part of an effective technological + measure under any applicable law fulfilling obligations under article + 11 of the WIPO copyright treaty adopted on 20 December 1996, or + similar laws prohibiting or restricting circumvention of such + measures. + + When you convey a covered work, you waive any legal power to forbid + circumvention of technological measures to the extent such circumvention + is effected by exercising rights under this License with respect to + the covered work, and you disclaim any intention to limit operation or + modification of the work as a means of enforcing, against the work's + users, your or third parties' legal rights to forbid circumvention of + technological measures. + + 4. Conveying Verbatim Copies. + + You may convey verbatim copies of the Program's source code as you + receive it, in any medium, provided that you conspicuously and + appropriately publish on each copy an appropriate copyright notice; + keep intact all notices stating that this License and any + non-permissive terms added in accord with section 7 apply to the code; + keep intact all notices of the absence of any warranty; and give all + recipients a copy of this License along with the Program. + + You may charge any price or no price for each copy that you convey, + and you may offer support or warranty protection for a fee. + + 5. Conveying Modified Source Versions. + + You may convey a work based on the Program, or the modifications to + produce it from the Program, in the form of source code under the + terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified + it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is + released under this License and any conditions added under section + 7. This requirement modifies the requirement in section 4 to + "keep intact all notices". + + c) You must license the entire work, as a whole, under this + License to anyone who comes into possession of a copy. This + License will therefore apply, along with any applicable section 7 + additional terms, to the whole of the work, and all its parts, + regardless of how they are packaged. This License gives no + permission to license the work in any other way, but it does not + invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display + Appropriate Legal Notices; however, if the Program has interactive + interfaces that do not display Appropriate Legal Notices, your + work need not make them do so. + + A compilation of a covered work with other separate and independent + works, which are not by their nature extensions of the covered work, + and which are not combined with it such as to form a larger program, + in or on a volume of a storage or distribution medium, is called an + "aggregate" if the compilation and its resulting copyright are not + used to limit the access or legal rights of the compilation's users + beyond what the individual works permit. Inclusion of a covered work + in an aggregate does not cause this License to apply to the other + parts of the aggregate. + + 6. Conveying Non-Source Forms. + + You may convey a covered work in object code form under the terms + of sections 4 and 5, provided that you also convey the + machine-readable Corresponding Source under the terms of this License, + in one of these ways: + + a) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by the + Corresponding Source fixed on a durable physical medium + customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product + (including a physical distribution medium), accompanied by a + written offer, valid for at least three years and valid for as + long as you offer spare parts or customer support for that product + model, to give anyone who possesses the object code either (1) a + copy of the Corresponding Source for all the software in the + product that is covered by this License, on a durable physical + medium customarily used for software interchange, for a price no + more than your reasonable cost of physically performing this + conveying of source, or (2) access to copy the + Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the + written offer to provide the Corresponding Source. This + alternative is allowed only occasionally and noncommercially, and + only if you received the object code with such an offer, in accord + with subsection 6b. + + d) Convey the object code by offering access from a designated + place (gratis or for a charge), and offer equivalent access to the + Corresponding Source in the same way through the same place at no + further charge. You need not require recipients to copy the + Corresponding Source along with the object code. If the place to + copy the object code is a network server, the Corresponding Source + may be on a different server (operated by you or a third party) + that supports equivalent copying facilities, provided you maintain + clear directions next to the object code saying where to find the + Corresponding Source. Regardless of what server hosts the + Corresponding Source, you remain obligated to ensure that it is + available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided + you inform other peers where the object code and Corresponding + Source of the work are being offered to the general public at no + charge under subsection 6d. + + A separable portion of the object code, whose source code is excluded + from the Corresponding Source as a System Library, need not be + included in conveying the object code work. + + A "User Product" is either (1) a "consumer product", which means any + tangible personal property which is normally used for personal, family, + or household purposes, or (2) anything designed or sold for incorporation + into a dwelling. In determining whether a product is a consumer product, + doubtful cases shall be resolved in favor of coverage. For a particular + product received by a particular user, "normally used" refers to a + typical or common use of that class of product, regardless of the status + of the particular user or of the way in which the particular user + actually uses, or expects or is expected to use, the product. A product + is a consumer product regardless of whether the product has substantial + commercial, industrial or non-consumer uses, unless such uses represent + the only significant mode of use of the product. + + "Installation Information" for a User Product means any methods, + procedures, authorization keys, or other information required to install + and execute modified versions of a covered work in that User Product from + a modified version of its Corresponding Source. The information must + suffice to ensure that the continued functioning of the modified object + code is in no case prevented or interfered with solely because + modification has been made. + + If you convey an object code work under this section in, or with, or + specifically for use in, a User Product, and the conveying occurs as + part of a transaction in which the right of possession and use of the + User Product is transferred to the recipient in perpetuity or for a + fixed term (regardless of how the transaction is characterized), the + Corresponding Source conveyed under this section must be accompanied + by the Installation Information. But this requirement does not apply + if neither you nor any third party retains the ability to install + modified object code on the User Product (for example, the work has + been installed in ROM). + + The requirement to provide Installation Information does not include a + requirement to continue to provide support service, warranty, or updates + for a work that has been modified or installed by the recipient, or for + the User Product in which it has been modified or installed. Access to a + network may be denied when the modification itself materially and + adversely affects the operation of the network or violates the rules and + protocols for communication across the network. + + Corresponding Source conveyed, and Installation Information provided, + in accord with this section must be in a format that is publicly + documented (and with an implementation available to the public in + source code form), and must require no special password or key for + unpacking, reading or copying. + + 7. Additional Terms. + + "Additional permissions" are terms that supplement the terms of this + License by making exceptions from one or more of its conditions. + Additional permissions that are applicable to the entire Program shall + be treated as though they were included in this License, to the extent + that they are valid under applicable law. If additional permissions + apply only to part of the Program, that part may be used separately + under those permissions, but the entire Program remains governed by + this License without regard to the additional permissions. + + When you convey a copy of a covered work, you may at your option + remove any additional permissions from that copy, or from any part of + it. (Additional permissions may be written to require their own + removal in certain cases when you modify the work.) You may place + additional permissions on material, added by you to a covered work, + for which you have or can give appropriate copyright permission. + + Notwithstanding any other provision of this License, for material you + add to a covered work, you may (if authorized by the copyright holders of + that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the + terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or + author attributions in that material or in the Appropriate Legal + Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or + requiring that modified versions of such material be marked in + reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or + authors of the material; or + + e) Declining to grant rights under trademark law for use of some + trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that + material by anyone who conveys the material (or modified versions of + it) with contractual assumptions of liability to the recipient, for + any liability that these contractual assumptions directly impose on + those licensors and authors. + + All other non-permissive additional terms are considered "further + restrictions" within the meaning of section 10. If the Program as you + received it, or any part of it, contains a notice stating that it is + governed by this License along with a term that is a further + restriction, you may remove that term. If a license document contains + a further restriction but permits relicensing or conveying under this + License, you may add to a covered work material governed by the terms + of that license document, provided that the further restriction does + not survive such relicensing or conveying. + + If you add terms to a covered work in accord with this section, you + must place, in the relevant source files, a statement of the + additional terms that apply to those files, or a notice indicating + where to find the applicable terms. + + Additional terms, permissive or non-permissive, may be stated in the + form of a separately written license, or stated as exceptions; + the above requirements apply either way. + + 8. Termination. + + You may not propagate or modify a covered work except as expressly + provided under this License. Any attempt otherwise to propagate or + modify it is void, and will automatically terminate your rights under + this License (including any patent licenses granted under the third + paragraph of section 11). + + However, if you cease all violation of this License, then your + license from a particular copyright holder is reinstated (a) + provisionally, unless and until the copyright holder explicitly and + finally terminates your license, and (b) permanently, if the copyright + holder fails to notify you of the violation by some reasonable means + prior to 60 days after the cessation. + + Moreover, your license from a particular copyright holder is + reinstated permanently if the copyright holder notifies you of the + violation by some reasonable means, this is the first time you have + received notice of violation of this License (for any work) from that + copyright holder, and you cure the violation prior to 30 days after + your receipt of the notice. + + Termination of your rights under this section does not terminate the + licenses of parties who have received copies or rights from you under + this License. If your rights have been terminated and not permanently + reinstated, you do not qualify to receive new licenses for the same + material under section 10. + + 9. Acceptance Not Required for Having Copies. + + You are not required to accept this License in order to receive or + run a copy of the Program. Ancillary propagation of a covered work + occurring solely as a consequence of using peer-to-peer transmission + to receive a copy likewise does not require acceptance. However, + nothing other than this License grants you permission to propagate or + modify any covered work. These actions infringe copyright if you do + not accept this License. Therefore, by modifying or propagating a + covered work, you indicate your acceptance of this License to do so. + + 10. Automatic Licensing of Downstream Recipients. + + Each time you convey a covered work, the recipient automatically + receives a license from the original licensors, to run, modify and + propagate that work, subject to this License. You are not responsible + for enforcing compliance by third parties with this License. + + An "entity transaction" is a transaction transferring control of an + organization, or substantially all assets of one, or subdividing an + organization, or merging organizations. If propagation of a covered + work results from an entity transaction, each party to that + transaction who receives a copy of the work also receives whatever + licenses to the work the party's predecessor in interest had or could + give under the previous paragraph, plus a right to possession of the + Corresponding Source of the work from the predecessor in interest, if + the predecessor has it or can get it with reasonable efforts. + + You may not impose any further restrictions on the exercise of the + rights granted or affirmed under this License. For example, you may + not impose a license fee, royalty, or other charge for exercise of + rights granted under this License, and you may not initiate litigation + (including a cross-claim or counterclaim in a lawsuit) alleging that + any patent claim is infringed by making, using, selling, offering for + sale, or importing the Program or any portion of it. + + 11. Patents. + + A "contributor" is a copyright holder who authorizes use under this + License of the Program or a work on which the Program is based. The + work thus licensed is called the contributor's "contributor version". + + A contributor's "essential patent claims" are all patent claims + owned or controlled by the contributor, whether already acquired or + hereafter acquired, that would be infringed by some manner, permitted + by this License, of making, using, or selling its contributor version, + but do not include claims that would be infringed only as a + consequence of further modification of the contributor version. For + purposes of this definition, "control" includes the right to grant + patent sublicenses in a manner consistent with the requirements of + this License. + + Each contributor grants you a non-exclusive, worldwide, royalty-free + patent license under the contributor's essential patent claims, to + make, use, sell, offer for sale, import and otherwise run, modify and + propagate the contents of its contributor version. + + In the following three paragraphs, a "patent license" is any express + agreement or commitment, however denominated, not to enforce a patent + (such as an express permission to practice a patent or covenant not to + sue for patent infringement). To "grant" such a patent license to a + party means to make such an agreement or commitment not to enforce a + patent against the party. + + If you convey a covered work, knowingly relying on a patent license, + and the Corresponding Source of the work is not available for anyone + to copy, free of charge and under the terms of this License, through a + publicly available network server or other readily accessible means, + then you must either (1) cause the Corresponding Source to be so + available, or (2) arrange to deprive yourself of the benefit of the + patent license for this particular work, or (3) arrange, in a manner + consistent with the requirements of this License, to extend the patent + license to downstream recipients. "Knowingly relying" means you have + actual knowledge that, but for the patent license, your conveying the + covered work in a country, or your recipient's use of the covered work + in a country, would infringe one or more identifiable patents in that + country that you have reason to believe are valid. + + If, pursuant to or in connection with a single transaction or + arrangement, you convey, or propagate by procuring conveyance of, a + covered work, and grant a patent license to some of the parties + receiving the covered work authorizing them to use, propagate, modify + or convey a specific copy of the covered work, then the patent license + you grant is automatically extended to all recipients of the covered + work and works based on it. + + A patent license is "discriminatory" if it does not include within + the scope of its coverage, prohibits the exercise of, or is + conditioned on the non-exercise of one or more of the rights that are + specifically granted under this License. You may not convey a covered + work if you are a party to an arrangement with a third party that is + in the business of distributing software, under which you make payment + to the third party based on the extent of your activity of conveying + the work, and under which the third party grants, to any of the + parties who would receive the covered work from you, a discriminatory + patent license (a) in connection with copies of the covered work + conveyed by you (or copies made from those copies), or (b) primarily + for and in connection with specific products or compilations that + contain the covered work, unless you entered into that arrangement, + or that patent license was granted, prior to 28 March 2007. + + Nothing in this License shall be construed as excluding or limiting + any implied license or other defenses to infringement that may + otherwise be available to you under applicable patent law. + + 12. No Surrender of Others' Freedom. + + If conditions are imposed on you (whether by court order, agreement or + otherwise) that contradict the conditions of this License, they do not + excuse you from the conditions of this License. If you cannot convey a + covered work so as to satisfy simultaneously your obligations under this + License and any other pertinent obligations, then as a consequence you may + not convey it at all. For example, if you agree to terms that obligate you + to collect a royalty for further conveying from those to whom you convey + the Program, the only way you could satisfy both those terms and this + License would be to refrain entirely from conveying the Program. + + 13. Use with the GNU Affero General Public License. + + Notwithstanding any other provision of this License, you have + permission to link or combine any covered work with a work licensed + under version 3 of the GNU Affero General Public License into a single + combined work, and to convey the resulting work. The terms of this + License will continue to apply to the part which is the covered work, + but the special requirements of the GNU Affero General Public License, + section 13, concerning interaction through a network will apply to the + combination as such. + + 14. Revised Versions of this License. + + The Free Software Foundation may publish revised and/or new versions of + the GNU General Public License from time to time. Such new versions will + be similar in spirit to the present version, but may differ in detail to + address new problems or concerns. + + Each version is given a distinguishing version number. If the + Program specifies that a certain numbered version of the GNU General + Public License "or any later version" applies to it, you have the + option of following the terms and conditions either of that numbered + version or of any later version published by the Free Software + Foundation. If the Program does not specify a version number of the + GNU General Public License, you may choose any version ever published + by the Free Software Foundation. + + If the Program specifies that a proxy can decide which future + versions of the GNU General Public License can be used, that proxy's + public statement of acceptance of a version permanently authorizes you + to choose that version for the Program. + + Later license versions may give you additional or different + permissions. However, no additional obligations are imposed on any + author or copyright holder as a result of your choosing to follow a + later version. + + 15. Disclaimer of Warranty. + + THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY + APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT + HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY + OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, + THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM + IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF + ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + 16. Limitation of Liability. + + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING + WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS + THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY + GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE + USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF + DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD + PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), + EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF + SUCH DAMAGES. + + 17. Interpretation of Sections 15 and 16. + + If the disclaimer of warranty and limitation of liability provided + above cannot be given local legal effect according to their terms, + reviewing courts shall apply local law that most closely approximates + an absolute waiver of all civil liability in connection with the + Program, unless a warranty or assumption of liability accompanies a + copy of the Program in return for a fee. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest + possible use to the public, the best way to achieve this is to make it + free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest + to attach them to the start of each source file to most effectively + state the exclusion of warranty; and each file should have at least + the "copyright" line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see http://www.gnu.org/licenses/. + + Also add information on how to contact you by electronic and paper mail. + + If the program does terminal interaction, make it output a short + notice like this when it starts in an interactive mode: + + <program> Copyright (C) <year> <name of author> + This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + + The hypothetical commands `show w' and `show c' should show the appropriate + parts of the General Public License. Of course, your program's commands + might be different; for a GUI interface, you would use an "about box". + + You should also get your employer (if you work as a programmer) or school, + if any, to sign a "copyright disclaimer" for the program, if necessary. + For more information on this, and how to apply and follow the GNU GPL, see + http://www.gnu.org/licenses/. + + The GNU General Public License does not permit incorporating your program + into proprietary programs. If your program is a subroutine library, you + may consider it more useful to permit linking proprietary applications with + the library. If this is what you want to do, use the GNU Lesser General + Public License instead of this License. But first, please read + http://www.gnu.org/philosophy/why-not-lgpl.html. + +
commit 238421bb9ebbf6d13564374f086646efffc4943f Author: Luke Macken lmacken@redhat.com Date: Mon Feb 16 00:12:11 2009 -0500
Add a full table of contents to our docs
diff --git a/docs/contents.rst b/docs/contents.rst new file mode 100644 index 0000000..a924210 --- /dev/null +++ b/docs/contents.rst @@ -0,0 +1,18 @@ +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + Moksha Documentation contents +%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% + +.. toctree:: + + main/Vision + main/Architecture + main/GettingStarted + main/Widgets + main/MokshaApplications + main/Messaging + main/Middleware + main/Development + main/Deployment + + copyright + license
moksha-commits@lists.fedorahosted.org