Attendees:
←Older revision
Revision as of 15:24, 27 August 2013
(One intermediate revision not shown.)
Line 19:
Line 19:
* Presentation of Eclipse Smart Home Project, and discussion about collaboration with other projects
* Presentation of Eclipse Smart Home Project, and discussion about collaboration with other projects
* EclipseCon US 2014: MQTT interop hackathon, “M2M day”, …
* EclipseCon US 2014: MQTT interop hackathon, “M2M day”, …
-
* m2m.eclipse.org website: new content? Infrastructure update (blog, news, examples, ...)?
…
+
* m2m.eclipse.org website: new content? Infrastructure update (blog, news, examples, ...)
and relationship with the M2M Top-level project
+
+
== Participants ==
+
+
* Jens Reimann
+
* Kai Kreuzer
+
* Thomas Eichstädt-Hengelen
+
* Hilary Tomasson
+
* Benjamin Cabé
+
+
== Eclipse Smart Home ==
+
+
* Thomas, co-lead of the Smart Home project
+
** Running a mid-sized company in Germany
+
** Java and OSGi technologies
+
** 2010, joined openHAB
+
** Community kept growing since then!
+
* Kai Kreuzer
+
** Java and OSGi developer for many years
+
** Working for Deutsche Telekom in the Home Automation department
+
+
* History
+
** The project was started early 2010. Open-source right from the beginning
+
** It's pure software
+
** Based on OSGi, Equinox, Jetty as a webserver, EMF for different modeling aspects, Eclipse RCP for configuration of the system
+
* Home automation = many different local protocols (KNX, enocean, zwave, ...) and Smart Home wants to combine them
+
+
* Data handling
+
** Type system (roller shutter, heater, ...)
+
** Event mechanism
+
** Bindings: translate events from/to a certain system/protocol
+
+
* Ability to define complex automation rules
+
** The rule engine is text-based (== scripting). It's a DSL based on Xtext
+
** Concise and short expressions to do powerful rules
+
+
* User interfaces
+
** Declarative approach
+
** EMF model for "sitemaps" describing pages containing widgets, possibly linking to other pages
+
*** There can be different renderers for a sitemap (android, iphone, web, ...)
+
+
* REST API
+
** Possible relationship with Eclipse Ponte here
+
+
* Persistence
+
** Events, status updates, etc can be processed/persisted to databases, and/or logged, and/or sent to IoT cloud services, ...
+
+
* Who
?
+
** Core framework is maintained by Kai and Thomas
+
** Lots of contributors for bindings and persistence bundles.
+
+
* New release in two weeks, with 12+ new bundles!
+
+
* Not the whole codebase will be transferred to Eclipse
+
** Some bindings rely on 3rd party libraries that would not clear IP.
+
** Most bindings would be kept outside of Eclipse, in the current openHAB project. openHAB would then become a distribution of Smart Home.
+
+
* Cooperation with other Eclipse projects
+
** MQTT binding will be part of the next openHAB release. Obvious connection with Paho.
+
** Ponte: REST API
+
** Kura: provides many things that could be used in Smart Home: watchdog, IO access, ...
+
** Concierge: lightweight OSGi container for embedded systems
+
** Eclipse SCADA: similar approach, but for a different market (industrial vs. home automation/end-user)
+
+
* Timeline
+
** Sept 8th: release 1.3 of openHAB. After that:
+
*** Refactoring of the namespaces
+
*** License will change from GPL to EPL.
+
** Next release of openHAB in early 2014 should then be based on top of Smart Home
+
+
== m2m.eclipse.org ==
+
+
* Benjamin describes the current process for maintaining the content of m2m.eclipse.org website today
+
** We have a static HTML website that can be updated through git https://github.com/kartben/m2m.eclipse.org
+
** Only Benjamin can actually push to the prod. website (ssh://m2m.eclipse.org/srv/git/m2m.eclipse.org.git) , but this hasn't be a problem so far
+
** There have been very few requests to update the website to this day, besides the community section (upcoming events/conferences)
+
+
* How do we want to update the website in the light of the new projects coming?
+
* Benjamin suggests to initiate a discussion on the mailing list for getting thoughts around evolving the website
+
+
* Jens: having simple technical implementation seems to be the most reasonable approach
+
* Kai: how is the redesign of the website linked with the top-level project?
+
* Hilary: it would be good to update the current marketecture material to something like "Eclipse M2M 2.0"
+
+
== EclipseCon 2014 ==
+
+
* This item is deferred to the next call.
-
== Attendees ==
-
* x
= July 16, 2013 =
= July 16, 2013 =