Hi Mike, all,
+1, definitely. I think a top-level project would really help to federate M2M projects under a common umbrella.
It would be good to discuss what domains we would like the top-level project to cover. At the moment the M2M IWG charter states that it coordinates the work around tools, frameworks and protocols for M2M ; which is probably a good basis for a top-level project charter. However, I think we should be more clear regarding the fact that some projects are targeting constrained embedded devices (Mihini, Paho clients), and some other target full-fledged servers (e.g. Ponte). Also, the M2M IWG as of today is very much focused on enabling M2M by providing the basic building blocks (device management, communication protocols etc.), while I think there should also be room for technologies that are further down the development chain, especially the ones allowing the development of end-user applications making use of M2M data.
From a very high-level perspective, I'd like to have a top-level project with a tagline that could be "Connecting". Connecting machines to machines (embedded agents, protocols, brokers, protocol "adapters"…), connecting developers to machines (tools, debuggers, simulators, code generators …), connecting end-users to machines (SCADA, visual dashboards, …). What are your thoughts?
All,
The M2M working group has been pretty successful in recruiting projects. Has the time come to consider creating a new top-level project to help create a cohesive project community for our M2M technologies?
For those who are unfamiliar with them, top-level projects are the mechanism which ties a collection of projects in a particular domain to the Eclipse development and IP processes. It requires the creation of a project management committee
(PMC), the appointment of a PMC leader, and having a written charter approved by the Board of Directors.
Mike Milinkovich
Executive Director
Eclipse Foundation
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223 mobile
+1.613.224.9461 x228 office
@mmilinkov
