Skip to content

Community Rules

Nikos Kefalakis edited this page Nov 24, 2015 · 3 revisions

OpenIoT Open Source Governance

Structure

OpenIoT open source project has selected a proper governance scheme, which regulates the interactions between the members of the open source community, including key roles and responsibilities for the development and expansion of the project’s software code. OpenIoT adopts an incremental, iterative and evolutionary software development process, notably based on agile development techniques. Such a development process alleviates the limitations of conventional waterfall software engineering processes, while at the same time enables the continued development and evolution of the open source software beyond the end of the FP7 OpenIoT project (i.e. as part of the sustainability phase of the project). Agile methodologies go beyond central planning, which facilitate the expansion of the project towards additional innovative directions. Such directions include the development of components, which were not foreseen at the first place in the scope of the OpenIoT architecture. Furthermore, agile methodologies are in generally in-line with the iterative nature of the OpenIoT work plan, which foresees iterative incremental delivery of key deliverables in WP4, WP5 and WP6. Last but not least, agile methodologies allow OpenIoT contributors (both teams and/or individual contributors) to incrementally plan, design and deliver open source software. The OpenIoT consortium made the following decisions:

  • A master-governed approach is the starting scheme associated with the establishment, governance and initial evolution of the OpenIoT open source project. The goal of this decision is to ensure proper integration of the various parts of the project, at least in the initial phase of the project where some critical mass has to be developed.
  • EPFL members act as master(s) for the part of the project that concerns the lower-level sensor/ICO information acquisition and filtering (X-GSN) and the Security integration in the OpenIoT platform.
  • NUIG Insight (formerly DERI) members act as master(s) for the part of the project dealing with semantic annotation of sensors/ICO and related discovery and filtering processes (LSM-Light).
  • AIT members act as master(s) for the part of the project dealing with service requests formulation and delivery (Scheduler and SDUM).
  • CSIRO members act as master(s) to the sensor schema editor component used to describe new sensor types and create sensor instance definitions (Schema Editor).
  • FER members act as master(s) to mobile publish-subscribe middleware development (CUPUS).
  • SENSAP members act as masters(s) to the OpenIoT user interface notably the Request Definition and Request Presentation modules.
  • All the teams mentioned above are coordinated by the AIT members that also manage the OpenIoT Open Source Community.

The Contributions to Github repository is provided here.

Clone this wiki locally