Attachment 193911 Details for Bug 339398 – last update before creation review :)

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

[patch] last update before creation review :)

clipboard.txt (text/plain), 14.76 KB, created by Benjamin Cabé

on 2011-04-22 08:25:26 EDT

(hide)

Description:

Filename:

MIME Type:

Creator: Benjamin Cabé

Created: 2011-04-22 08:25:26 EDT

Size: 14.76 KB

patch

obsolete

>### Eclipse Workspace Patch 1.0
>#P technology.koneki
>Index: proposal.html
>===================================================================
>RCS file: /cvsroot/org.eclipse/www/proposals/technology.koneki/proposal.html,v
>retrieving revision 1.3
>diff -u -r1.3 proposal.html
>--- proposal.html	8 Apr 2011 17:20:01 -0000	1.3
>+++ proposal.html	22 Apr 2011 12:22:23 -0000
>@@ -45,6 +45,38 @@
> 	margin-left: 25px;
> 	margin-bottom: 5px;
> }
>+
>+.archiBlock {
>+	font-family: sans-serif;
>+	font-variant: small-caps;
>+	color: #FFF;
>+	padding: 5px;
>+	margin-bottom: 0.8em;
>+	margin-top: 1em;
>+	display: inline-block;
>+	border: solid 3px;
>+	display: inline-block;
>+}
>+
>+#embdd {
>+	background-color: #A48FC0;
>+	border-color: #62457C;
>+}
>+
>+#protocols {
>+	background-color: #51BBCE;
>+	border-color: #008498;
>+}
>+
>+#server {
>+	background-color: #A8C377;
>+	border-color: #73903A;
>+}
>+
>+#appModel {
>+	background-color: #FEA664;
>+	border-color: #C4782E;
>+}
> </style>
> 
> <body>
>@@ -93,13 +125,14 @@
> 			- Because it is very close to the underlying hardware, embedded
> 			development can turn out to be a complex task, especially considering
> 			the fact that people developing M2M solutions are domain experts
>-			(healthcare, smart grid, ...), not necessarily software specialists.</li>
>+			(healthcare, smart grid, &#8230;), not necessarily software
>+			specialists.</li>
> 		<li>Variety of M2M embedded modules - There are
> 			many M2M-capable devices available on the market, and they all come
> 			with different operating systems (although Linux seems to become the
> 			norm), different APIs to communicate with a distant server (over
> 			HTTP, TCP, or whatever) or with a "local" asset (serial protocol,
>-			Modbus, ZigBee&reg;, ...). This fragmentation makes it very difficult
>+			Modbus, ZigBee&reg;, &#8230;). This fragmentation makes it very difficult
> 			to come up with reusable, portable, software.</li>
> 	</ul>
> 
>@@ -115,15 +148,22 @@
> 		Machine-to-Machine solutions developers with tools easing the
> 		development, simulation, testing/debugging and deployment of such
> 		solutions.
>+	More specifically, Koneki aims at:
> 
> 	<ul>
>-		<li>Establish a programming component-based model for embedded
>-			development</li>
>-		<li>Provide exemplary, model-based, tooling, giving developers
>-			the ability to design (either using visual or "classical"
>-			programming) embedded applications.</li>
>-		<li>Provide support for M2M targets interactions: file
>-			deployment, remote debugging, shell access, etc.</li>
>+		<li>Enabling M2M development
>+			<ul>
>+				<li>support for languages and runtimes used to develop M2M
>+					applications, with a specific focus on Lua (ligthweight language,
>+					very well-suited for M2M applications)</li>
>+				<li>support for communication protocols used in M2M
>+					applications</li>
>+				<li>smooth integration of M2M servers</li>
>+			</ul>
>+		<li>Establishing an M2M application model</li>
>+		<li>Providing tooling built on top of this application model to
>+			improve M2M development experience.</li>
>+		
> 	</ul>
> 
> 	
>@@ -142,38 +182,78 @@
> -->
> 
> 	The Koneki project goal will be to deliver a first-class
>-		development environment for M2M solutions developers
>+		development environment for M2M solutions developers.
>+
>+	
>+		<img src="images/koneki-architecture.png">
>+	
>+
> 	Here are the key features that the Koneki project aims at
> 		providing:
> 	<ul>
>-		<li>M2M component model - The Koneki project
>-			will expose a data/event-driven component model allowing the
>-			programmer to design a modular application. The development
>-			environment will include the ability to validate the consistency of
>-			an M2M application according to the specification of the components
>-			it is made of.</li>
>-		<li>Lua language support - Several
>-			Machine-to-Machine modules and devices available on the market are
>-			programmable using the Lua language. The Koneki project will provide
>-			the developer with Lua tooling (editor, content-assistance, outline,
>-			...) based on DLTK.</li>
>-		<li>M2M and industrial protocols support - The
>-			Koneki project will provide the user with utilities to manipulate M2M
>-			&amp; industrial protocols: encode/decode binary frames, perform
>-			bandwidth usage simulation according to different communication
>-			scenarios, etc.</li>
>-		<li>M2M devices integration - In order to ease
>-			the development of Machine-to-Machine applications, the proposed
>-			project will include a strong integration of the embedded device
>-			within the IDE, and will therefore allow easy shell access, remote
>-			file copy, and remote launch of M2M application using the Eclipse
>-			"Launch Configuration" mechanism.</li>
>-		<li>User Assistance - Given that a person
>-			involved in the development of a Machine-to-Machine solution is not
>-			necessarily a skilled embedded developer (e.g. a solution to remotely
>-			control an industrial equipment will likely be developed by a control
>-			engineer), the Koneki project will focus on providing the user with
>-			application templates, examples, ready-to-use libraries, etc.</li>
>+		<li>M2M Embedded
>+				Development
>+			<ul>
>+				<li>Language tools &mdash; Koneki will rely
>+					on existing language development tools (CDT, JDT, DLTK-based
>+					editors, &#8230;) to give the M2M developer access to usual editing
>+					features (syntax highlighting, content assist, outlines, &#8230;).</li>
>+				<li>M2M embedded runtimes &mdash; Koneki will
>+					ease the use of M2M embedded runtimes: remote configuration, remote
>+					application deployment/debugging, shell access, &#8230;</li>
>+				<li>M2M application generation &mdash; Koneki
>+					will provide an extensible generation infrastructure built on top
>+					of the M2M application model.</li>
>+				<li>Application examples &mdash;
>+					Machine-to-Machine solution developers are not necessarily skilled
>+					embedded developers (e.g. a solution to remotely control an
>+					industrial equipment will likely be developed by a control
>+					engineer), the Koneki project will therefore focus on providing the
>+					developer with embedded application templates and examples.</li>
>+			</ul>
>+		</li>
>+		<li>Protocols
>+			<ul>
>+				<li>Koneki project will provide the user with utilities to
>+					manipulate M2M &amp; industrial protocols: encode/decode binary
>+					frames, perform bandwidth usage simulation according to different
>+					communication scenarios, etc.</li>
>+				<li>Simulation &mdash; Koneki will provide
>+					extension points enabling the creation of a consistent UI on top of
>+					existing protocol simulators/emulators.</li>
>+			</ul>
>+		</li>
>+		<li>M2M Server
>+				Development
>+			<ul>
>+				<li>Koneki will define an abstraction (a la WST Server Adapter)
>+					of what an M2M server is. It will allow M2M services providers to
>+					implement their own connector, and developers to easily configure
>+					the server-side model of their application, discover the Web
>+					Services exposed by the server, etc.</li>
>+				<li>Simulation &mdash; Koneki will provide a
>+					generic simulation infrastructure to allow developer to test
>+					different communication policies (and their consequences on
>+					bandwidth consumption), monitor data transfers, simulate
>+					communication failures, etc.</li>
>+				<li>Application examples &mdash; Koneki may
>+					package exemplary end-user applications to illustrate the use of
>+					M2M server APIs.</li>
>+			</ul>
>+		</li>
>+		<li>M2M Model
>+			<ul>
>+				<li>Application model &mdash; Koneki will
>+					implement an M2M application model allowing an M2M solution
>+					developer to create an abstract definition of the capabilities of
>+					an M2M application (communication capabilities, exposed variables,
>+					communication policy, supported remote commands, &#8230;).</li>
>+				<li>Application editors &mdash; Koneki will
>+					provide high-level editors (forms, diagrams, DSL-based editors) of
>+					M2M application models, assisting the developer with the design of
>+					his/her embedded application.</li>
>+			</ul>
>+		</li>
> 	</ul>
> 
> 	<h2>Why Eclipse?</h2>
>@@ -186,19 +266,30 @@
> 	of hosting at Eclipse Labs?
> -->
> 
>-	The Koneki project would benefit from being hosted at Eclipse
>-		Foundation in that:
>+	The Koneki project has relationships with many Eclipse projects
>+		and the Koneki team will closely collaborate with these projects
>+		since:
> 	<ul>
>-		<li>it will closely collaborate with the teams of other Eclipse
>-			Projects (DLTK, TM, RSE, Linux Tools, ...),</li>
>-		<li>an M2M Industry Working Group will likely be created to help
>-			industrial partners and tool vendors to come up with a reference
>-			environment to develop M2M solutions. Having Koneki at eclipse.org is
>-			the best way to ensure a good collaboration between the Koneki team
>-			and the members of the Working Group in charge of identifying M2M
>-			tooling requirements.
>+		<li>Lua tooling relies on DLTK 2,</li>
>+		<li>&#8220;EMF Forms&#8221; (PDE Incubator) is used for easing
>+			the development of form-based editors,</li>
>+		<li>Tools TM (Terminal and RSE components) is used to communicate
>+			with embedded devices,</li>
>+		<li>Modeling projects (EMF, EMF Transaction, GMF) support the
>+			M2M application model,</li>
> 	</ul>
> 
>+	Koneki will work even more closely with eTrice (MDT project) and
>+		Yakindu (EclipseLabs project at the moment) teams to establish an M2M
>+		application/component model.
>+
>+	In addition, an Eclipse M2M Industry Working Group will likely
>+		be created to help industrial partners and tool vendors to come up
>+		with a reference environment to develop M2M solutions. Having Koneki
>+		at eclipse.org is the best way to ensure a good collaboration between
>+		the Koneki team and the members of the Working Group in charge of
>+		identifying M2M tooling requirements.
>+
> 	<h2>Initial Contribution</h2>
> 
> 	
> 
> 	<ul>
>-		<li>May 2011 &ndash; creation review and initial contribution</li>
>-
>-		<li>Q3 2011 &ndash; first builds for early adopters</li>
>+		<li>May 2011 &ndash; Sierra Wireless initial contribution
>+			<ul>
>+				<li>&#8220;Enablers&#8221;</li>
>+				<li>Lua tooling</li>
>+				<li>Modeling environment prototype</li>
>+			</ul>
>+		</li>
>+
>+		<li>June 2011
>+			<ul>
>+				<li>Convert Koneki's build to Tycho</li>
>+				<li>Make Lua Tooling available at Eclipse Marketplace</li>
>+			</ul>
>+		</li>
>+
>+		<li>Q3 2011
>+			<ul>
>+				<li>Call for community participation to define an M2M
>+					application model</li>
>+				<li>Improve Lua Tooling: LuaRocks support</li>
>+			</ul>
>+		</li>
>+
>+		<li>Q4 2011
>+			<ul>
>+				<li>Communicate at EclipseCon Europe</li>
>+				<li>Setup M2M server simulation infrastructure</li>
>+				<li>Lua Tooling component to be moved to its own Technology
>+					project</li>
>+			</ul>
>+		</li>
> 
>-		<li>Q4 2011 &ndash; improve Lua support, API stabilization</li>
>-
>-		<li>Q1 2012 &ndash; release a 0.9 version</li>
>-
>-		<li>June 2012 &ndash; graduate</li>
>+		<li>Q2 2012 &ndash; First release of an &#8220;end-to-end&#8221;
>+			M2M IDE</li>
> 	</ul>
> 
> 	<h2>Changes to this Document</h2>
>@@ -357,6 +490,12 @@
> 			<td>07-Apr-2011</td>
> 			<td>Added new Interested Parties and Mentors</td>
> 		</tr>
>+		<tr>
>+			<td>20-Apr-2011</td>
>+			<td>Detailed the functional architecture. Refined the
>+				project plan and relationships with other Eclipse projects. 
>+				Added K&eacute;vin Kin-Foo to initial committers list.</td>
>+		</tr>
> 	</table>
> </body>
> </html>
>\ No newline at end of file

Actions: View | Diff

Attachments on bug 339398: 191123 | 192798 | 193911 | 193912