Roadmap section in a separate document (#44)

* docs(README): includes roadmap section * docs(README): splits roadmap in a separate file * docs(README): splits roadmap in a separate file
Atos-Research-and-Innovation · Jan 22, 2019 · 4808f7d · 4808f7d
1 parent 1a150de
commit 4808f7d
Show file tree

Hide file tree

Showing 2 changed files with 31 additions and 24 deletions.
diff --git a/README.md b/README.md
@@ -147,30 +147,7 @@ Library [documentation](https://iotagent-node-lib.rtfd.io/).
 
 ## Roadmap
 
-This section elaborates on proposed new features or tasks which are expected to be added to the product in the foreseeable future.  There should be no assumption of a commitment to deliver these features on specific dates or in the order given. The development team will be doing their best to follow the proposed dates and priorities, but please bear in mind that plans to work on a given feature or task may be revised.  All information is provided as general guidelines only,  and this section may be revised to provide newer information at any time.
-
-This product is a FIWARE Generic Enabler.  If you would like to learn about the overall Roadmap of FIWARE, please check section `Roadmap` on the [FIWARE Catalogue](https://github.com/Fiware/catalogue).
-
-### Short term (next release of the product)
-
-The following list of features are planned to be addressed in the short term, and incorporated in the next release of the product:
-- Support to application servers MQTT configured with SSL certificates.
-- Inclusion of metadata provided by application servers in the payloads sent to the Context Broker (e.g., location, frequency, airtime, etc).
-- Integration of [Semantic-release](https://github.com/semantic-release/semantic-release) or [Versionist](https://www.npmjs.com/package/versionist).
-- Examples of deployment using Kubernetes.
-
-### Medium term (9 months following next release)
-
-The following list of features are planned to be addressed in the medium term, typically within the subsequent release(s) generated in the next 9 months after the next planned release:
-- Support to lazy attributes and commands for Class-C LoRaWAN devices.
-- Integration with [Multitech Conduit Gateway Network Server](http://www.multitech.net/developer/software/lora/lora-network-server/).
-
-### Long term (some time in the future)
-
-The following list of features are proposals regarding the longer-term evolution of the product even though the development of these features has not yet been scheduled for a release in the near future.  Please feel free to contact us if you wish to get involved in the implementation or influence the roadmap:
-- Examples with new devices and end-nodes.
-- Integration of application and/or network server functionalities within the IoT Agent.
-- Interoperability with corporate LoRa networks.
+The roadmap of this FIWARE GE is described [here](docs/roadmap.md)
 
 ## Quality Assurance
 

diff --git a/docs/roadmap.md b/docs/roadmap.md
@@ -0,0 +1,30 @@
+# IoT Agent for LoRaWAN protocol
+
+This product is a FIWARE Generic Enabler. If you would like to learn about the overall Roadmap of FIWARE, please check "Roadmap" on the [FIWARE Catalogue](https://www.fiware.org/developers/catalogue/).
+
+### Introduction
+
+This section elaborates on proposed new features or tasks which are expected to be added to the product in the foreseeable future.  There should be no assumption of a commitment to deliver these features on specific dates or in the order given. The development team will be doing their best to follow the proposed dates and priorities, but please bear in mind that plans to work on a given feature or task may be revised.  All information is provided as general guidelines only,  and this section may be revised to provide newer information at any time.
+
+This section has been last updated in January 2019. Please take into account is content could be obsolete.
+
+### Short term (next release of the product)
+
+The following list of features are planned to be addressed in the short term, and incorporated in the next release of the product:
+- Support to application servers MQTT configured with SSL certificates.
+- Inclusion of metadata provided by application servers in the payloads sent to the Context Broker (e.g., location, frequency, airtime, etc).
+- Integration of [Semantic-release](https://github.com/semantic-release/semantic-release) or [Versionist](https://www.npmjs.com/package/versionist).
+- Examples of deployment using Kubernetes.
+
+### Medium term (9 months following next release)
+
+The following list of features are planned to be addressed in the medium term, typically within the subsequent release(s) generated in the next 9 months after the next planned release:
+- Support to lazy attributes and commands for Class-C LoRaWAN devices.
+- Integration with [Multitech Conduit Gateway Network Server](http://www.multitech.net/developer/software/lora/lora-network-server/).
+
+### Long term (some time in the future)
+
+The following list of features are proposals regarding the longer-term evolution of the product even though the development of these features has not yet been scheduled for a release in the near future.  Please feel free to contact us if you wish to get involved in the implementation or influence the roadmap:
+- Examples with new devices and end-nodes.
+- Integration of application and/or network server functionalities within the IoT Agent.
+- Interoperability with corporate LoRa networks.