workinggroups/content/en_mobilewg.php - www.eclipse.org/org - Git at Google

 <?php
 /**
  * Copyright (c) 2008, 2018 Eclipse Foundation.
  *
  * This program and the accompanying materials are made
  * available under the terms of the Eclipse Public License 2.0
  * which is available at https://www.eclipse.org/legal/epl-2.0/
  *
  * Contributors:
  *   Christopher Guindon (Eclipse Foundation) - Initial implementation
  *   Mike Milinkovich (Eclipse Foundation)
  *   Eric Poirier (Eclipse Foundation)
  *
  * SPDX-License-Identifier: EPL-2.0
  */
 ?>
 <div id="maincontent">
   <div id="midcolumn">
     <h1><?php print $pageTitle; ?></h1>
     <strong>MOBILE WG HAS BEEN TERMINATED</strong>
     <h2>Charter</h2>
     <h3>Purpose and Scope</h3>
     <p>The application development tools used in the mobile phone industry are characterized by
       vendor-specific offerings. A common development tools integration platform, Eclipse-based or
       any other technology, has not been adopted across the mobile industry.</p>
     <p>A typical Eclipse based mobile application development environment contains components
       sourced and adapted from many different Eclipse Projects (e.g. CDT, JDT, WTP). There are few
       mobile specific projects within Eclipse (Mobile Tools for Java, Tools for Mobile Linux) which
       have not yet gained the momentum or industry leadership for mobile application development
       because these projects are narrowly focused on specific parts of an overall solution. This
       constrains the value of the Eclipse platform for mobile application developers, mobile tooling
       developers, and companies in the mobile industry.</p>
     <p>The intent of the Mobile Industry Working Group (MIWG) will be to define, implement and
       promote a common Mobile Application Development Kit (MADK) which can be easily augmented with
       handset -specific profiles. The MIWG will be the forum for collaboration between the industry
       players to define and deliver a common platform, it will facilitate collaboration between
       existing Eclipse projects applicable to Mobile developers, and initiate new projects based on
       identified un-met requirements.</p>
     <h3>Description of Deliverables</h3>
     <p>The Mobile Industry Working Group (MIWG) will focus on four areas:</p>
     <ol>
       <li>The MIWG will define and maintain requirements and a roadmap that defines a complete
         mobile offering and encourage broader participation for different solution providers.</li>
       <li>The MIWG will define the technical requirements for a packaged distribution (e.g. the
         Eclipse MADK). The MADK will collaborate with other Eclipse projects (e.g. the Eclipse
         packaging project), or create new projects as needed to implement new technology required
         for the MADK, to deliver an extensible MADK package.</li>
       <li>The MIWG will create a set of best practices and extension mechanisms that simplify the
         use of Eclipse by a wide range of mobile application developers and tools vendors through a
         common set of test suites, training materials and documentation.</li>
       <li>The MIWG will develop a consistent messaging and promotion program to help raise the
         awareness of MADK and Eclipse in the mobile industry.</li>
     </ol>
     </p>
     <p>The MIWG will not create or publish a specification as part of its deliverables.</p>
     <h3>Mobile Industry Working Group (MIWG) Participation Guidelines</h3>
     <p>The MIWG participation guidelines define the obligations for participants. MIWG participants
       are expected to full-fill these obligations to be considered in good standing.</p>
     <p>Steering Committee Members are required to:</p>
     <ul>
       <li>Be Strategic or Enterprise member</li>
       <li>Appoint at least 1 developer/technical resource to contribute to the creation of MIWG
         technologies, roadmaps and/or technical documents.</li>
       <li>Regularly participate in all MIWG meetings and provide timely feedback on the MIWG
         documents.</li>
       <li>Provide announcement support for the Mobile Application Development Kit (MADK) and ongoing
         promotion to mobile application developers.</li>
     </ul>
     </p>
     <p>Member Participants are required to:</p>
     <ul>
       <li>Be an Eclipse Foundation Member (Solution, Associate, or Committer)</li>
       <li>Regularly participate in all MIWG meeting and provide timely feedback on the MIWG
         documents.</li>
       <li>For corporate members, provide announcement support for the Mobile Application Development
         Kit (MADK) and ongoing promotion to mobile application developers.</li>
     </ul>
     </p>
     <h3>Proposed Schedule</h3>
     <ul>
       <li>Q4/08 - Q1/09 Publish MIWG Charter; Gather bigger community and recruit two or more
         (Expectation of 4) mobile industry players.</li>
       <li>Q4/08 Define technical roadmap. The goal is to create the following documents by end of
         December
         <ul>
           <li>Detailed use-cases outlining the user experience of a "Eclipse Mobile ADK"</li>
           <li>High level requirements with straw man architecture</li>
           <li>List of dependencies on existing Eclipse Projects</li>
           <li>List of missing components (Plug-in granularity) and a brief description of each</li>
         </ul>
       </li>
       <li><p>Q1/Q2 09 - Work with the existing projects (e.g. MTJ, TML and EPP) to create a
           pre-packaged Eclipse Mobile ADK in Galileo release.</p>
         <p>Create an Eclipse Mobile Integration project to implement the identified missing
           components. Examples include:</p>
         <ul>
           <li>implement a missing "SDK download / integration" UI</li>
           <li>P2 extensions to integrate vendor SDKs into MADK</li>
           <li>signing / deployment framework which can be extended in MTJ, TML and others</li>
         </ul></li>
       <li>Q2/09: Work on Galileo coordinated MADK Release</li>
       <li>Q3/09: Unify mobile specific features (e.g. Sign, Package, Deploy)</li>
       <li>Q3/Q4/09: Plan for Post Galileo release</li>
     </ul>
     </p>
     <h3>Feedback</h3>
     <p>
       Please send comments and feedback to <a href="mailto:mobile-iwg@eclipse.org">mobile-iwg@eclipse.org</a>.
       Please also use the mailing list to express your desire to participate in the working group.
       Go <a href="https://dev.eclipse.org/mailman/listinfo/mobile-iwg">here</a> to subscribe to the
       mailing list and view the archives.
     </p>
     <h3>Industry Working Group Process</h3>
     <p>
       The Mobile Industry Working Group will follow the <a
         href="http://www.eclipse.org/org/industry-workgroups/industry_wg_process.php"
       >Eclipse Industry Working Group Process</a>.
     </p>
   </div>
 </div>
	<?php
	/**
	* Copyright (c) 2008, 2018 Eclipse Foundation.
	*
	* This program and the accompanying materials are made
	* available under the terms of the Eclipse Public License 2.0
	* which is available at https://www.eclipse.org/legal/epl-2.0/
	*
	* Contributors:
	* Christopher Guindon (Eclipse Foundation) - Initial implementation
	* Mike Milinkovich (Eclipse Foundation)
	* Eric Poirier (Eclipse Foundation)
	*
	* SPDX-License-Identifier: EPL-2.0
	*/
	?>
	<div id="maincontent">
	<div id="midcolumn">
	<h1><?php print $pageTitle; ?></h1>
	<strong>MOBILE WG HAS BEEN TERMINATED</strong>
	<h2>Charter</h2>
	<h3>Purpose and Scope</h3>
	<p>The application development tools used in the mobile phone industry are characterized by
	vendor-specific offerings. A common development tools integration platform, Eclipse-based or
	any other technology, has not been adopted across the mobile industry.</p>
	<p>A typical Eclipse based mobile application development environment contains components
	sourced and adapted from many different Eclipse Projects (e.g. CDT, JDT, WTP). There are few
	mobile specific projects within Eclipse (Mobile Tools for Java, Tools for Mobile Linux) which
	have not yet gained the momentum or industry leadership for mobile application development
	because these projects are narrowly focused on specific parts of an overall solution. This
	constrains the value of the Eclipse platform for mobile application developers, mobile tooling
	developers, and companies in the mobile industry.</p>
	<p>The intent of the Mobile Industry Working Group (MIWG) will be to define, implement and
	promote a common Mobile Application Development Kit (MADK) which can be easily augmented with
	handset -specific profiles. The MIWG will be the forum for collaboration between the industry
	players to define and deliver a common platform, it will facilitate collaboration between
	existing Eclipse projects applicable to Mobile developers, and initiate new projects based on
	identified un-met requirements.</p>
	<h3>Description of Deliverables</h3>
	<p>The Mobile Industry Working Group (MIWG) will focus on four areas:</p>
	<ol>
	<li>The MIWG will define and maintain requirements and a roadmap that defines a complete
	mobile offering and encourage broader participation for different solution providers.</li>
	<li>The MIWG will define the technical requirements for a packaged distribution (e.g. the
	Eclipse MADK). The MADK will collaborate with other Eclipse projects (e.g. the Eclipse
	packaging project), or create new projects as needed to implement new technology required
	for the MADK, to deliver an extensible MADK package.</li>
	<li>The MIWG will create a set of best practices and extension mechanisms that simplify the
	use of Eclipse by a wide range of mobile application developers and tools vendors through a
	common set of test suites, training materials and documentation.</li>
	<li>The MIWG will develop a consistent messaging and promotion program to help raise the
	awareness of MADK and Eclipse in the mobile industry.</li>
	</ol>
	</p>
	<p>The MIWG will not create or publish a specification as part of its deliverables.</p>
	<h3>Mobile Industry Working Group (MIWG) Participation Guidelines</h3>
	<p>The MIWG participation guidelines define the obligations for participants. MIWG participants
	are expected to full-fill these obligations to be considered in good standing.</p>
	<p>Steering Committee Members are required to:</p>
	<ul>
	<li>Be Strategic or Enterprise member</li>
	<li>Appoint at least 1 developer/technical resource to contribute to the creation of MIWG
	technologies, roadmaps and/or technical documents.</li>
	<li>Regularly participate in all MIWG meetings and provide timely feedback on the MIWG
	documents.</li>
	<li>Provide announcement support for the Mobile Application Development Kit (MADK) and ongoing
	promotion to mobile application developers.</li>
	</ul>
	</p>
	<p>Member Participants are required to:</p>
	<ul>
	<li>Be an Eclipse Foundation Member (Solution, Associate, or Committer)</li>
	<li>Regularly participate in all MIWG meeting and provide timely feedback on the MIWG
	documents.</li>
	<li>For corporate members, provide announcement support for the Mobile Application Development
	Kit (MADK) and ongoing promotion to mobile application developers.</li>
	</ul>
	</p>
	<h3>Proposed Schedule</h3>
	<ul>
	<li>Q4/08 - Q1/09 Publish MIWG Charter; Gather bigger community and recruit two or more
	(Expectation of 4) mobile industry players.</li>
	<li>Q4/08 Define technical roadmap. The goal is to create the following documents by end of
	December
	<ul>
	<li>Detailed use-cases outlining the user experience of a "Eclipse Mobile ADK"</li>
	<li>High level requirements with straw man architecture</li>
	<li>List of dependencies on existing Eclipse Projects</li>
	<li>List of missing components (Plug-in granularity) and a brief description of each</li>
	</ul>
	</li>
	<li><p>Q1/Q2 09 - Work with the existing projects (e.g. MTJ, TML and EPP) to create a
	pre-packaged Eclipse Mobile ADK in Galileo release.</p>
	<p>Create an Eclipse Mobile Integration project to implement the identified missing
	components. Examples include:</p>
	<ul>
	<li>implement a missing "SDK download / integration" UI</li>
	<li>P2 extensions to integrate vendor SDKs into MADK</li>
	<li>signing / deployment framework which can be extended in MTJ, TML and others</li>
	</ul></li>
	<li>Q2/09: Work on Galileo coordinated MADK Release</li>
	<li>Q3/09: Unify mobile specific features (e.g. Sign, Package, Deploy)</li>
	<li>Q3/Q4/09: Plan for Post Galileo release</li>
	</ul>
	</p>
	<h3>Feedback</h3>
	<p>
	Please send comments and feedback to <a href="mailto:mobile-iwg@eclipse.org">mobile-iwg@eclipse.org</a>.
	Please also use the mailing list to express your desire to participate in the working group.
	Go <a href="https://dev.eclipse.org/mailman/listinfo/mobile-iwg">here</a> to subscribe to the
	mailing list and view the archives.
	</p>
	<h3>Industry Working Group Process</h3>
	<p>
	The Mobile Industry Working Group will follow the <a
	href="http://www.eclipse.org/org/industry-workgroups/industry_wg_process.php"
	>Eclipse Industry Working Group Process</a>.
	</p>
	</div>
	</div>