Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.
The "TempoProposal" page has been changed by TonyFaustini:
https://wiki.apache.org/incubator/TempoProposal?action=diff&rev1=6&rev2=7
Comment:
Updated to reflect a new name Tempo => iota
- = Tempo Proposal =
+ = iota Proposal =
== Abstract ==
@@ -15, +15 @@
important area of growth for the foreseeable future. This new dynamic
will eventually become manifest in a growing number of Apache projects
that enable this to occur. Our wish is to contribute to this movement
- by contributing the Tempo system to the Open Source Community via the
+ by contributing the iota system to the Open Source Community via the
- Apache Foundation. Tempo is an open platform to interconnect any and
+ Apache Foundation. Apache iota is an open platform to interconnect any and
all devices, sensors, people, and applications, henceforth referred to
as points, through a scalable, secure, and modular architecture,
enabling applications to generate analysis, create actions and/or add
@@ -29, +29 @@
global company orchestrating millions of devices and people across
different continents. Either way you face the same fundamental
problem; namely, how do you manage many points in a secure robust and
- meaningful manner? Tempo is an open source software system that
+ meaningful manner? Apache iota is an open source software system that
enables homeowners and global companies to download a software system
that provides secure and robust orchestration.
- The Tempo system consists of a variety of components:
+ The iota system consists of a variety of components:
* A basic but extensible desktop
* An extensible mechanism for capturing data from a variety of sources
@@ -58, +58 @@
OSS (Open Source Software) solution that can harness the
potentialities of this increasingly important trend. Manufacturers of
IoT devices, both in the consumer and industrial spaces, continue to
- develop proprietary systems. Tempo is an open source IoT system that
+ develop proprietary systems. Apache iota is an open source IoT system that
creates an open source solution enabling the orchestration of IoT
- devices that brings the benefits of OSS to this space. Tempo was
+ devices that brings the benefits of OSS to this space. Apache iota was
initially developed by Litbit and is deployed in a growing number of
Industrial contexts, especially in the context of Data Center
Infrastructure.
== Rationale ==
- Tempo is a general platform for orchestrating IoT devices in both
+ Apache iota is a general platform for orchestrating IoT devices in both
consumer and industrial contexts. It is complementary to the existing
Apache projects and is itself built using of a number of Apache
- projects. Bringing Tempo into Apache is very beneficial to both the
+ projects. Bringing iota into Apache is very beneficial to both the
Apache community and the IoT community.
The rapid growth of IoT needs to be harnessed in the Open Source
Community. We believe the Apache Foundation is a great fit as the
- long-term home for Tempo, as it provides an established process for
+ long-term home for iota, as it provides an established process for
community-driven development and decision making by consensus. This is
- exactly the model we want for future Tempo development.
+ exactly the model we want for future iota development.
== Initial Goals ==
@@ -88, +88 @@
== Current Status ==
- Tempo has undergone a major release (0.1) and is being used in
+ Apache iota has undergone a major release (0.1) and is being used in
- production by several global organizations. The Tempo codebase is
+ production by several global organizations. The iota codebase is
currently hosted at github.com, which will seed the Apache git
repository.
@@ -99, +99 @@
=== Community ===
- The need for an open source IoT orchestration system is tremendous. Tempo is currently being
used by several organizations worldwide. By bringing Tempo into Apache, we believe that the
community will quickly grow and become a significant Apache offering.
+ The need for an open source IoT orchestration system is tremendous. Apache iota is currently
being used by several organizations worldwide. By bringing iota into Apache, we believe that
the community will quickly grow and become a significant Apache offering.
=== Core Developers ===
- Tempo was initially developed at Litbit by the following individuals:
+ iota was initially developed at Litbit by the following individuals:
* Rutvij Clerk
* Miron Costant
@@ -119, +119 @@
=== Alignment ===
IoT orchestration is in need of an Open Source Solution. We believe
- Tempo can be that solution and fill this need in the Apache
+ iota can be that solution and fill this need in the Apache
- Foundation's offerings. We believe that Tempo will remove the barriers
+ Foundation's offerings. We believe that iota will remove the barriers
imposed by proprietary solutions and usher in significant growth for
the Apache Foundation. The alignment is also beneficial to other
Apache communities (such as Zookeeper, Kafka, and Mesos). We could
@@ -134, +134 @@
robustness of an initial offering so that contributors and users are
highly incentivized to continue development. To this extent,
organizations can be encouraged to build critical business
- applications around Tempo and the risk of the project being abandoned
+ applications around iota and the risk of the project being abandoned
will be minimized.
=== Inexperience with Open Source ===
@@ -148, +148 @@
=== Homogenous Developers ===
The initial committers will be from Litbit, a well funded startup. We
- plan to grow Tempo with an active community of developers, and we are
+ plan to grow iota with an active community of developers, and we are
committed to recruiting additional committers based on their
contributions to the project.
=== Reliance on Salaried Developers ===
- It is expected that Tempo development will occur on both salaried time
+ It is expected that iota development will occur on both salaried time
and on volunteer time, after hours. The majority of initial committers
are paid by Litbit to contribute to this project. However, they are
all passionate about the project, and we are confident that the
@@ -164, +164 @@
=== Relationships with Other Apache Products ===
- As mentioned in the Alignment section, Tempo is closely integrated
+ As mentioned in the Alignment section, iota is closely integrated
with Zookeeper, Kafka, and Mesos. We look forward to collaborating
with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
- Tempo will become a healthy and well known open source project. This
+ iota will become a healthy and well known open source project. This
proposal is not for the purpose of generating publicity. Rather, the
primary benefits to joining Apache are those outlined in the Rationale
section.
@@ -179, +179 @@
The reader will find these websites highly relevant:
- * Tempo website: Coming soon
+ * iota website: Coming soon
- * Tempo documentation: Coming soon
+ * iota documentation: Coming soon
* Codebase: Becoming public soon
* User group: Coming soon
== Source and Intellectual Property Submission Plan ==
- The Tempo codebase is currently hosted on Github. To give you some
+ The iota codebase is currently hosted on Github. To give you some
idea of what we will be contributing here are some basic statistics
from our current Github
@@ -270, +270 @@
This is the exact codebase that we would migrate to the Apache foundation.
- Upon entering Apache, Tempo will migrate to an Apache License 2.0 with
+ Upon entering Apache, iota will migrate to an Apache License 2.0 with
all contributions licensed to the Apache Foundation. In certain cases
if individuals or organizations hold copyright, we will ensure they
grant a license to the Apache Foundation. Going forward, all commits
@@ -280, +280 @@
== External Dependencies ==
- To the best of our knowledge, all of Tempo dependencies (except 0MQ)
+ To the best of our knowledge, all of iota dependencies (except 0MQ)
are distributed under Apache compatible licenses. Upon acceptance to
the incubator, we would begin a thorough analysis of all transitive
dependencies to verify this fact and introduce license checking into
the build and release process (for instance integrating Apache Rat).
- Tempo has used 0MQ for some types of internal messaging, and 0MQ is
+ iota has used 0MQ for some types of internal messaging, and 0MQ is
licensed under the GNU Lesser General Public License. We are in the
- process of making the Tempo messaging layer pluggable, and plan to use
+ process of making the iota messaging layer pluggable, and plan to use
Netty (which is licensed under Apache License v2) as our default
messaging plugin (while keeping 0MQ as an optional plugin).
== Cryptography ==
- We do not expect Tempo to be a controlled export item due to the use
+ We do not expect iota to be a controlled export item due to the use
- of encryption. Tempo enables encryptions via a digital envelope using:
+ of encryption. iota enables encryptions via a digital envelope using:
* RSA 128 Bits
* AES 128 Bits
@@ -304, +304 @@
=== Mailing lists ===
- * tempo-user
- * tempo-dev
+ * iota-user
+ * iota-dev
- * tempo-commits
+ * iota-commits
- * tempo-private (with moderated subscriptions)
+ * iota-private (with moderated subscriptions)
=== Subversion Directory ===
- Git is the preferred source control system: git://git.apache.org/tempo
+ Git is the preferred source control system: git://git.apache.org/iota
=== Issue Tracking ===
- JIRA Tempo (TEMPO)
+ JIRA iota (IOTA)
== Initial Committers ==
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org