docs(*): add roadmap section and rework contributing

Author: Gabriel Monroy

docs/contributing/index.rst

@@ -15,6 +15,3 @@ Contributing
     standards
     community
     conduct
-    schedule
-    releases
-    test_plan

docs/roadmap/index.rst

@@ -0,0 +1,16 @@
+:title: Roadmap
+:description: The Deis roadmap and open source planning process
+
+Roadmap
+=======
+
+:Release: |version|
+:Date: |today|
+
+.. toctree::
+
+    planning
+    roadmap
+    schedule
+    releases
+    test_plan

docs/roadmap/planning.rst

@@ -0,0 +1,37 @@
+:title: Planning Process
+:description: The open source planning process for the Deis project used to define the roadmap and its execution.
+
+.. _planning:
+
+Planning Process
+================
+Deis features a lightweight process that emphasizes openness and ensures every community member can be an integral part of the planning process.
+
+The Role of Maintainers
+-----------------------
+Maintainers lead the project. Their duties include proposing the Roadmap, reviewing and integrating contributions and maintaining the vision of the project.
+
+Open Roadmap
+------------
+The :ref:`roadmap` is a community document. While Maintainers propose the Roadmap, it gets discussed and refined in Sprint Meetings.
+
+Contributing to the Roadmap
+---------------------------
+Proposals and issues can be opened by anyone. Every member of the :ref:`community` is welcome to participate in the discussion by providing feedback and/or offering counter-proposals.
+
+Release Milestones
+------------------
+The Roadmap gets delivered progressively via the :ref:`release_schedule`.  Releases are defined during Sprint Meetings and managed using GitHub Milestones which track specific deliverables and work-in-progress.
+
+Sprint Meetings
+---------------
+Major decisions affecting the Roadmap are discussed during Sprint Meetings on the first Thursday of each month, aligned with our :ref:`release_schedule`.
+
+Sprint meetings are open to the public with access coordinated via the #deis IRC channel on Freenode.
+
+Credits
+-------
+Thanks to `Amy Lindburg`_ and our friends at `Docker`_ for their inspiration.
+
+.. _`Amy Lindburg`: https://twitter.com/amylindburg
+.. _`Docker`: https://www.docker.com/

docs/contributing/releases.rst docs/roadmap/releases.rstdocs/contributing/releases.rst renamed to docs/roadmap/releases.rst

@@ -0,0 +1,82 @@
+:title: Roadmap
+:description: The Deis project roadmap
+
+.. _roadmap:
+
+Deis Roadmap
+============
+The Deis Roadmap is a community document created as part of our open :ref:`planning`.
+Each roadmap item describes a high-level capability or grouping of features we deem
+important to the future of Deis.
+
+Given our rapid :ref:`Release Schedule, <release_schedule>` roadmap items are designed to provide a sense of
+direction over many releases.
+
+Update Service
+--------------
+Deis must support 100% automated, zero-downtime updates of the control plane.
+Like CoreOS, Deis clusters should be attached to an alpha, beta or stable channel and rely on an automatic update mechanism.
+To accomplish this, we plan to use the `Google Omaha Protocol`_ as implemented by `CoreUpdate`_.
+
+ - [ ] Update client/agent
+ - [ ] Update server
+ - [ ] CI Integration
+
+Scheduling and Orchestration
+----------------------------
+Today Deis uses `Fleet`_ for scheduling.  Unfortunately, Fleet does not support
+resource-based scheduling which results in poor cluster utilization at scale.
+
+Fortunately, Deis is composable and can easily hot-swap orchestration APIs.
+Because the most promising container orchestration solutions are under heavy development,
+we are currently focused on releasing "technology previews".
+
+These technology previews will help the community try different orchestration solutions easily,
+report their findings and help guide the future direction of Deis.
+
+ - [X] Swarm preview
+ - [ ] Mesos preview
+ - [ ] Kubernetes preview
+
+TTY Broker
+----------
+Today Deis cannot provide bi-directional streams needed for log tailing and interactive batch processes.
+By having the :ref:`Controller` drive a TTY Broker component, we can securely open WebSockets
+through the routing mesh.
+
+ - [ ] TTY Broker component
+ - [ ] Interactive Deis Run (deis run bash)
+ - [ ] Log Tailing (deis logs -f)
+
+Deis Push
+---------
+End-users should be able to push Docker-based applications into Deis from their local machine using ``deis push user/app``.
+This works around a number of authentication issues with private registries and ``deis pull``.
+
+ - [ ] Docker Registry v2
+ - [ ] Deis Push
+
+Service Broker
+--------------
+In Deis, connections to :ref:`concepts_backing_services` are meant to be explicit and modeled as a series of environment variables.
+We believe the Cloud Foundry `Service Broker API`_ is the best embodiment of this today.
+
+ - [ ] Deis Addons CLI (deis addons)
+ - [ ] PostgreSQL Service Broker
+ - [ ] Redis Service Broker
+
+Monitoring & Telemetry
+----------------------
+Deis installations today use custom solutions for monitoring, alerting and operational visibility.
+We will standardize the monitoring interfaces and provide open source agent(s) that can be used to ship telemetry to arbitrary endpoints.
+
+ - [ ] Host Telemetry (cpu, memory, network, disk)
+ - [ ] Container Telemetry (cpu, memory, network, disk)
+ - [ ] Platform Telemetry (control plane, data plane)
+ - [ ] Controller Telemetry (app created, build created, containers scaled)
+
+.. _`like CoreOS`: https://coreos.com/releases/
+.. _`Google Omaha Protocol`: https://code.google.com/p/omaha/wiki/ServerProtocol
+.. _`CoreUpdate`: https://coreos.com/docs/coreupdate/custom-apps/coreupdate-protocol/
+.. _`Fleet`: https://github.com/coreos/fleet#readme
+.. _`Service Broker API`: http://docs.cloudfoundry.org/services/api.html

docs/roadmap/roadmap.rst

@@ -17,6 +17,7 @@ This documentation has the following resources:
    managing_deis/index
    troubleshooting_deis/index
    customizing_deis/index
+   roadmap/index
    contributing/index
    reference/index
    faq