mpc/proposal.html - www.eclipse.org/proposals - Git at Google

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML>
 <HEAD>
 	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
 	<TITLE>Marketplace Client Project (MPC)</TITLE>
 	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.1  (Win32)">
 	<META NAME="CREATED" CONTENT="0;0">
 	<META NAME="CHANGED" CONTENT="0;0">
 	<!-- This document is provided as a template along with some guidance for creating
 	your project proposal. This is just a template. Feel free to change it as
 	you see fit (add sections, remove section). We feel, however, that the
 	suggestions represented in this document represent the reasonable minimum
 	amount of information to move forward.

 	Please keep the formatting in this document simple. Please do not edit
 	this document in Microsoft Word as it adds huge piles of markup that make
 	it difficult to restyle.

 	More information is available here:

 	http://wiki.eclipse.org/Development_Resources/HOWTO/Pre-Proposal_Phase

 	Direct any questions about this template to emo@eclipse.org
  -->
 	<!-- Include the title here. We will parse it out of here and include it on the
 	rendered webpage. Do not duplicate the title within the text of your page.
  -->

 </HEAD>
 <BODY LANG="en-US" DIR="LTR">
 <P>Eclipse Marketplace Client Project (MPC) is a proposed open source
 project under the <a href="http://www.eclipse.org/epp/">Eclipse Packaging Project (EPP)</a> project. MPC will be open-sourced under the
 EPL.</P>
 <P>This proposal is in the Project Proposal Phase (as defined in the
 Eclipse Development Process document) and is written to declare its
 intent and scope. This proposal is written to solicit additional
 participation and input from the Eclipse community. You are invited
 to comment on and/or join the project. Please send all feedback to
 the <a href="http://www.eclipse.org/forums/eclipse.mpc">MPC forum</a>.
 </P>
 <H2>Background</H2>
 <P>The Eclipse community has hundreds, if not thousands, of
 third-party plugins that users can add to their Eclipse installation.
 Unfortunately, there is not easy way to discover and install these
 solutions from within Eclipse.
 </P>
 <P>The Eclipse Foundation has recently launched a new website, called
 Eclipse Marketplace, that provides a listing of Eclipse-based
 solutions. The listings allow each solution provider to specify a p2
 update site for their solution. Eclipse users now have a central
 repository to find Eclipse solutions but the install process is still
 not tightly integrated with the Eclipse workspace.
 </P>
 <P>MPC will provide the tight install integration between the Eclipse
 workspace and Eclipse Marketplace, plus other third party solution
 listings.
 </P>
 <H2>Scope</H2>
 <P>The scope of MPC is to:
 </P>
 <UL>
 	<LI><P STYLE="margin-bottom: 0in">Provide an Eclipse-based rich
 	client for installing solutions listed in the Eclipse Marketplace.
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Provide a workflow for finding and
 	installing solutions, layering on top of the Eclipse P2 and
 	providing a streamlined and simplified workflow that does not
 	require users to enter and manage update sites.
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Support different external sources
 	of solution listing catalogs (ex. Eclipse release train catalog,
 	third party catalog, internal corporate catalog)
 	</P>
 	<LI><P>Awesome end-user experience for uninstalling eclipse
 	solutions
 	</P>
 </UL>
 <H2>Description</H2>
 <P>The following are the goals and plan items for the MPC project:
 </P>
 <P>1. Awesome end user experience for finding and installing Eclipse
 solutions
 </P>
 <UL>
 	<LI><P STYLE="margin-bottom: 0in">Easily ability to navigate up to
 	5000 different catalog entries:
 	</P>
 	<UL>
 		<LI><P STYLE="margin-bottom: 0in">support for browsing different
 		markets and categories of MP
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">search-based navigation and
 		filtering, including 1) license types, 2) maturity of product, 3)
 		provider name and 4) maybe some others?
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">Navigation by recently added and
 		updated
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">Navigation by community favorite
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">Find by same author/vendor
 		</P>
 	</UL>
 	<LI><P STYLE="margin-bottom: 0in">Display relevant information
 	</P>
 	<UL>
 		<LI><P STYLE="margin-bottom: 0in">Each solution listing in the MP
 		client should be able to present the following: 1) logo of listing,
 		2) Solution name, 3)Provider name, 4) short description and 5) a
 		link to more detailed information.
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">Optionally show screen shots
 		and/or videos; depending on bandwidth this might be just
 		</P>
 	</UL>
 	<LI><P STYLE="margin-bottom: 0in">Guaranteed Single click install
 	</P>
 	<UL>
 		<LI><P STYLE="margin-bottom: 0in">One click install button will
 		result in the solution being added to Eclipse
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">MP Client needs to be smart
 		enough to only show solutions that can successfully install into
 		the existing Eclipse installation. This includes checking for valid
 		update sites, version compatibility, pre-requisites, etc. We need
 		to get as close as possible to a guaranteed install.
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">A user should be able to select
 		multiple solutions for installation.
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">When multiple solutions are
 		picked for integration, their compatibility should be checked.
 		</P>
 		<LI><P STYLE="margin-bottom: 0in">After a user has installed a
 		solution, they should have the option to add the solution to their
 		favorite list on MP. This would require the user to log into MP.
 		</P>
 		<LI><P>If a solution listing doesn't have an install option, there
 		should be an option to be able to show the listing but for 'more
 		info' redirect to the listing web site.
 		</P>
 	</UL>
 </UL>
 <P>2. Support for different external sources of solution listings
 (ex. Eclipse release train repo, third party repos)
 </P>
 <UL>
 	<LI><P STYLE="margin-bottom: 0in">Client should have an option to
 	switch to different listing providers. This would be list switching
 	search providers in a browser.
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">If the provider is changed, the
 	provider UI and data would be presented.
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">The client search functionality
 	should be able to work with other providers. Getting more
 	information after the search results, like a browse more or more
 	details, would take the user to the external provider UI.
 	</P>
 	<LI><P>the MP client needs to have the ability to accept incoming
 	requests from external providers to install a solution. This needs
 	to include support from an html page.
 	</P>
 </UL>
 <P>3. Awesome end-user experience for uninstalling Eclipse solutions
 </P>
 <UL>
 	<LI><P STYLE="margin-bottom: 0in">MP Client should be able to
 	remember what solutions have already been installed. Previously
 	installed solutions should visually show this in the listings.
 	</P>
 	<LI><P>MP Client should allow the user to uninstall a solution.
 	</P>
 </UL>
 <H2>Contribution</H2>
 <P>The initial contribution will be made by Tasktop.</P>
 <H2>Committers</H2>
 <UL>
 	<LI><P STYLE="margin-bottom: 0in">Project Leader: Ian Skerrett,
 	Eclipse Foundation
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Steffen Pingel (Tasktop)
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Mik Kersten (Tasktop)
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">David Green (individual)
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Henrik Lindberg (Cloudsmith)
 	</P>
 	<LI><P STYLE="margin-bottom: 0in">Thomas Hallgren (Cloudsmith)
 	</P>
 </UL>

 	<H2>Mentors</H2>

 	<p>
 	<ul>
 	<li>Wayne Beaton, Eclipse Foundation</li>
 	<li>Chris Aniszczyk, EclipseSource</li>

 	</ul>

 	<H2>Interested Parties</H2>
 	</UL>
 	<P><!-- Provide a list of individuals, organisations, companies, and other Eclipse
 	projects that are interested in this project. This list will provide some
 	insight into who your project's community will ultimately include. Where
 	possible, include affiliations. Do not include email addresses.
  -->The
 	following individuals, organisations, companies and projects have
 	expressed interest in this project:</P>
 	<UL>
 		<LI>Ian Bull (EclipseSource)</LI>
 		<li>Pascal Rapicault (Sonatype)</li>
 	</ul>

 <H2>Project Scheduling</H2>
 <ul>
 <li>      March 19, 2010. Feature complete beta available (Helios M6)
 <li>      June 23, 2010. Production release (Helios GA)
 </ul>

 </BODY>
 </HTML>
	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
	<HTML>
	<HEAD>
	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
	<TITLE>Marketplace Client Project (MPC)</TITLE>
	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.1 (Win32)">
	<META NAME="CREATED" CONTENT="0;0">
	<META NAME="CHANGED" CONTENT="0;0">
	<!-- This document is provided as a template along with some guidance for creating
	your project proposal. This is just a template. Feel free to change it as
	you see fit (add sections, remove section). We feel, however, that the
	suggestions represented in this document represent the reasonable minimum
	amount of information to move forward.

	Please keep the formatting in this document simple. Please do not edit
	this document in Microsoft Word as it adds huge piles of markup that make
	it difficult to restyle.

	More information is available here:

	http://wiki.eclipse.org/Development_Resources/HOWTO/Pre-Proposal_Phase

	Direct any questions about this template to emo@eclipse.org
	-->
	<!-- Include the title here. We will parse it out of here and include it on the
	rendered webpage. Do not duplicate the title within the text of your page.
	-->

	</HEAD>
	<BODY LANG="en-US" DIR="LTR">
	<P>Eclipse Marketplace Client Project (MPC) is a proposed open source
	project under the <a href="http://www.eclipse.org/epp/">Eclipse Packaging Project (EPP)</a> project. MPC will be open-sourced under the
	EPL.</P>
	<P>This proposal is in the Project Proposal Phase (as defined in the
	Eclipse Development Process document) and is written to declare its
	intent and scope. This proposal is written to solicit additional
	participation and input from the Eclipse community. You are invited
	to comment on and/or join the project. Please send all feedback to
	the <a href="http://www.eclipse.org/forums/eclipse.mpc">MPC forum</a>.
	</P>
	<H2>Background</H2>
	<P>The Eclipse community has hundreds, if not thousands, of
	third-party plugins that users can add to their Eclipse installation.
	Unfortunately, there is not easy way to discover and install these
	solutions from within Eclipse.
	</P>
	<P>The Eclipse Foundation has recently launched a new website, called
	Eclipse Marketplace, that provides a listing of Eclipse-based
	solutions. The listings allow each solution provider to specify a p2
	update site for their solution. Eclipse users now have a central
	repository to find Eclipse solutions but the install process is still
	not tightly integrated with the Eclipse workspace.
	</P>
	<P>MPC will provide the tight install integration between the Eclipse
	workspace and Eclipse Marketplace, plus other third party solution
	listings.
	</P>
	<H2>Scope</H2>
	<P>The scope of MPC is to:
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">Provide an Eclipse-based rich
	client for installing solutions listed in the Eclipse Marketplace.
	</P>
	<LI><P STYLE="margin-bottom: 0in">Provide a workflow for finding and
	installing solutions, layering on top of the Eclipse P2 and
	providing a streamlined and simplified workflow that does not
	require users to enter and manage update sites.
	</P>
	<LI><P STYLE="margin-bottom: 0in">Support different external sources
	of solution listing catalogs (ex. Eclipse release train catalog,
	third party catalog, internal corporate catalog)
	</P>
	<LI><P>Awesome end-user experience for uninstalling eclipse
	solutions
	</P>
	</UL>
	<H2>Description</H2>
	<P>The following are the goals and plan items for the MPC project:
	</P>
	<P>1. Awesome end user experience for finding and installing Eclipse
	solutions
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">Easily ability to navigate up to
	5000 different catalog entries:
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">support for browsing different
	markets and categories of MP
	</P>
	<LI><P STYLE="margin-bottom: 0in">search-based navigation and
	filtering, including 1) license types, 2) maturity of product, 3)
	provider name and 4) maybe some others?
	</P>
	<LI><P STYLE="margin-bottom: 0in">Navigation by recently added and
	updated
	</P>
	<LI><P STYLE="margin-bottom: 0in">Navigation by community favorite
	</P>
	<LI><P STYLE="margin-bottom: 0in">Find by same author/vendor
	</P>
	</UL>
	<LI><P STYLE="margin-bottom: 0in">Display relevant information
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">Each solution listing in the MP
	client should be able to present the following: 1) logo of listing,
	2) Solution name, 3)Provider name, 4) short description and 5) a
	link to more detailed information.
	</P>
	<LI><P STYLE="margin-bottom: 0in">Optionally show screen shots
	and/or videos; depending on bandwidth this might be just
	</P>
	</UL>
	<LI><P STYLE="margin-bottom: 0in">Guaranteed Single click install
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">One click install button will
	result in the solution being added to Eclipse
	</P>
	<LI><P STYLE="margin-bottom: 0in">MP Client needs to be smart
	enough to only show solutions that can successfully install into
	the existing Eclipse installation. This includes checking for valid
	update sites, version compatibility, pre-requisites, etc. We need
	to get as close as possible to a guaranteed install.
	</P>
	<LI><P STYLE="margin-bottom: 0in">A user should be able to select
	multiple solutions for installation.
	</P>
	<LI><P STYLE="margin-bottom: 0in">When multiple solutions are
	picked for integration, their compatibility should be checked.
	</P>
	<LI><P STYLE="margin-bottom: 0in">After a user has installed a
	solution, they should have the option to add the solution to their
	favorite list on MP. This would require the user to log into MP.
	</P>
	<LI><P>If a solution listing doesn't have an install option, there
	should be an option to be able to show the listing but for 'more
	info' redirect to the listing web site.
	</P>
	</UL>
	</UL>
	<P>2. Support for different external sources of solution listings
	(ex. Eclipse release train repo, third party repos)
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">Client should have an option to
	switch to different listing providers. This would be list switching
	search providers in a browser.
	</P>
	<LI><P STYLE="margin-bottom: 0in">If the provider is changed, the
	provider UI and data would be presented.
	</P>
	<LI><P STYLE="margin-bottom: 0in">The client search functionality
	should be able to work with other providers. Getting more
	information after the search results, like a browse more or more
	details, would take the user to the external provider UI.
	</P>
	<LI><P>the MP client needs to have the ability to accept incoming
	requests from external providers to install a solution. This needs
	to include support from an html page.
	</P>
	</UL>
	<P>3. Awesome end-user experience for uninstalling Eclipse solutions
	</P>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">MP Client should be able to
	remember what solutions have already been installed. Previously
	installed solutions should visually show this in the listings.
	</P>
	<LI><P>MP Client should allow the user to uninstall a solution.
	</P>
	</UL>
	<H2>Contribution</H2>
	<P>The initial contribution will be made by Tasktop.</P>
	<H2>Committers</H2>
	<UL>
	<LI><P STYLE="margin-bottom: 0in">Project Leader: Ian Skerrett,
	Eclipse Foundation
	</P>
	<LI><P STYLE="margin-bottom: 0in">Steffen Pingel (Tasktop)
	</P>
	<LI><P STYLE="margin-bottom: 0in">Mik Kersten (Tasktop)
	</P>
	<LI><P STYLE="margin-bottom: 0in">David Green (individual)
	</P>
	<LI><P STYLE="margin-bottom: 0in">Henrik Lindberg (Cloudsmith)
	</P>
	<LI><P STYLE="margin-bottom: 0in">Thomas Hallgren (Cloudsmith)
	</P>
	</UL>

	<H2>Mentors</H2>

	<p>
	<ul>
	<li>Wayne Beaton, Eclipse Foundation</li>
	<li>Chris Aniszczyk, EclipseSource</li>

	</ul>

	<H2>Interested Parties</H2>
	</UL>
	<P><!-- Provide a list of individuals, organisations, companies, and other Eclipse
	projects that are interested in this project. This list will provide some
	insight into who your project's community will ultimately include. Where
	possible, include affiliations. Do not include email addresses.
	-->The
	following individuals, organisations, companies and projects have
	expressed interest in this project:</P>
	<UL>
	<LI>Ian Bull (EclipseSource)</LI>
	<li>Pascal Rapicault (Sonatype)</li>
	</ul>

	<H2>Project Scheduling</H2>
	<ul>
	<li> March 19, 2010. Feature complete beta available (Helios M6)
	<li> June 23, 2010. Production release (Helios GA)
	</ul>

	</BODY>
	</HTML>