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

 <!--
 	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
  -->

 <html>
 <head>

 <!--
 	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.
  -->

 <title>Skalli</title>
 </head>

 <!--
 	We make use of the 'classic' HTML Definition List (dl) tag to specify
 	committers. I know... you haven't seen this tag in a long while...
  -->

 <style>
 dt {
 	display: list-item;
 	list-style-position: outside;
 	list-style-image:
 		url(/eclipse.org-common/themes/Phoenix/images/arrow.gif);
 	margin-left: 16px;
 }

 dd {
 	margin-left: 25px;
 	margin-bottom: 5px;
 }
 </style>

 <body>

 <p>The Skalli project is a proposed open source incubator project
 under the <a
 	href="http://www.eclipse.org/projects/project_summary.php?projectid=technology">Eclipse
 Technology Project</a>.</p>
 <!--
 	The communication channel must be specified. Typically, this is the
 	"Proposals" forum. In general, you don't need to change this.
  -->
 <p>This proposal is in the Project Proposal Phase (as defined in the
 Eclipse Development Process) and is written to declare its intent and
 scope. We solicit additional participation and input from the Eclipse
 community. Please send all feedback to the <a
 	href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse
 Proposals</a> Forum.</p>

 <p>This proposal is structured as follows. Section <a
 	href="#background">Background</a> gives the motivation of the project
 and provides some background information about the origins of the
 proposed project. Section <a href="#contribution">Initial
 Contribution</a> describes the current state of the project and the initial
 contributions that will be made. Section <a href="#scope">Scope</a>
 outlines the initial set of tools and platforms this project aims to
 deliver to its users; <a href="#description">Description</a> gives
 little more details on the intermediate goals. Section <a
 	href="#related">Related Eclipse Projects</a> describes potential future
 connections between current eclipse.org projects and the proposed
 project as well as likely collaborations. The remaining sections (<a
 	href="#committers">Committers</a>, <a href="#mentors">Mentors</a>, <a
 	href="#interested">Interested Parties</a>) describe what their names
 suggest.</p>

 <h2 id="background">Background</h2>

 <!--
 	Optionally provide the background that has lead you to creating this project.
  -->
 <p>The tentative name of the project is Skalli which comes from
 Norse mythology.</p>

 <pre>
 In Norse mythology, Skalli is a wolf that pursues the chariot
 of the sun goddess Sol across the skies every day.
 He has a twin brother Hati that pursues M&aacute;ni, the moon.

 </pre>

 <p>Project management in open source varies from community to
 community. There are no good open source solutions out there that help
 manage your project and the Eclipse community has grown out of the
 current project management infrastructure at eclipse.org. The Skalli
 project aims at closing this gap.
 <p>
 <h2 id="scope">Scope</h2>

 <!--
 	All projects must have a well-defined scope. Describe, concisely, what
 	is in-scope and (optionally) what is out-of-scope. An Eclipse project
 	cannot have an open-ended scope.
  -->

 <p>One of the major goals of this project is to make a new
 generation project management tool accessible and usable by the Eclipse
 community and other open source projects.</p>

 <p>Thereby Skalli forms the central entry point to all projects and
 creates transparency over the existing projects. It leverages search
 technologies and social network mechanisms in order to structure and
 find them.</p>

 <p>This project however does not aim at replacing existing tools
 like wiki, bugtracker and source code management system. It merely links
 to them and integrates their data and services as far as needed in order
 to let users - and through a REST API also other tools - gain an
 overview on each project's state and locate its resources.</p>

 <h2 id="description">Description</h2>

 <!--
 	Describe the project here. Be concise, but provide enough information that
 	somebody who doesn't already know very much about your project idea or domain
 	has at least a fighting chance of understanding its purpose.
  -->

 <p>The goal of the project is to build an extensible system for
 organizing projects.</p>

 <p>This includes support for creation of new projects and all the
 little processes (e.g. committer election) needed within the lifecycle
 of a project. Additionally, maintenance of project data must be simple.
 Committers should be enabled to request additional infrastructure
 according to the rules of the community in a seamless way. This should
 be realized by offering self-services within Skalli as much as feasible
 and integrating them with the corresponding community infrastructure.</p>

 <p>Existing projects can be browsed and searched for, so users can
 find what they are looking for easily. Project details like source code
 location, bugtracker and quality metrics can be maintained by the
 corresponding committers, so that everyone is able to locate them
 instantly. Social media features like tagging and recommending projects
 help guiding users to the projects they are looking for.</p>

 <p>Technically, the flexibility and extensibility is achieved by
 leveraging the mechanisms provided by OSGi. So modules introducing new
 UI building blocks or connections to additional services can be added as
 required.</p>

 <p>The data about projects maintained within Skalli is also
 available via a REST API. This enables an ecosystem of loosely coupled
 tools that can use this data to provide additional services (e.g.
 quality reporting).</p>

 <p>The short-term target is to reflect project related workflows
 (e.g. committer election and other voting) as well as the integration
 into major development infrastructure tools like Hudson, Git and Gerrit.
 By doing that, self-services can be provided to the teams that will
 reduce the administrative overhead of running a development
 infrastructure.</p>

 <h2 id="related">Relationship with other Eclipse projects</h2>
 <p>The project so far does not yet have strong relationships to
 existing Eclipse projects. It does however run on <a
 	href="http://www.eclipse.org/virgo/">Eclipse Virgo</a> and uses the
 Eclipse preference store.</p>

 <p>Furthermore, once the foundation is laid and the project matures,
 the goal is to provide a suitable replacement for the current
 eclipse.org foundation portal in alignment with the Phoenix project.</p>

 <p>The <a href="http://www.eclipse.org/emf">EMF</a> toolset and <a
 	href="http://www.eclipse.org/eclipselink">EclipseLink</a> could also be
 useful for this project and will potentially be used in future.</p>

 <!--
 <h2>Why Eclipse?</h2>
 -->

 <!--
 	Answer these two questions:	What value does this project bring to the Eclipse
 	community? What value do you expect to obtain from hosting your project at Eclipse?

 	What value do you get by having your project at Eclipse over and above the value
 	of hosting at Eclipse Labs?
  -->

 <h2 id="contribution">Initial Contribution</h2>

 <!--
 	Projects are expected to arrive at Eclipse with existing code.

 	Describe the existing code that will be contributed to the project. Please provide
 	a couple of paragraphs describing the code with modest detail, including important
 	information like code ownership (who holds the copyright?), and some consideration
 	of community that exists around the code. Include a listing of third-party libraries
 	and associated licenses.
  -->
 <p>The Skalli project will be seeded with an initial contribution
 coming from SAP. It contains the basic set of features that already can
 be used productively and provides the foundation for integration of
 additional services and processes.</p>

 <p>The contribution already includes project maintenance and data
 validation, searching for projects and contained components, a REST API
 for data retrieval. It runs on the <a
 	href="http://www.eclipse.org/virgo/">Eclipse Virgo</a> server. For the
 web interface, it currently uses JSP and <a
 	href="http://vaadin.com/home">Vaadin</a> as UI technologies.</p>

 <!--
 <h2>Legal Issues</h2>
 -->

 <!--
 	Please describe any potential legal issues in this section. Does somebody else
 	own the trademark to the project name? Is there some issue that prevents you
 	from licensing the project under the Eclipse Public License? Are parts of the
 	code available under some other license? Are there any LGPL/GPL bits that you
 	absolutely require?
  -->

 <h2 id="committers">Committers</h2>

 <!--
 	List any initial committers that should be provisioned along with the
 	new project. Include affiliation, but do not include email addresses at
 	this point.
  -->

 <p>The following individuals are proposed as initial committers to
 the project:</p>

 <dl>
 	<dt><b>Simon Kaufmann, SAP (Project Lead)</b></dt>
 	<dd></dd>
 	<dt><b>Matthias Sohn, SAP (Project Lead)</b></dt>
 	<dd></dd>
 	<dt>Chris Aniszczyk, Red Hat</dt>
 	<dd></dd>
 	<dt>Michael Ochmann, SAP</dt>
 	<dd></dd>
 	<dt>J&uuml;rgen Schneider, SAP</dt>
 	<dd></dd>
 	<dt>Jochen Hiller, Deutsche Telekom AG</dt>
 	<dd></dd>
 	<dt>Bernd Kolb, SAP</dt>
 	<dd></dd>
 </dl>

 <p>We welcome additional committers and contributions.</p>

 <!--
 	Describe any initial contributions of code that will be brought to the
 	project. If there is no existing code, just remove this section.
  -->

 <h2 id="mentors">Mentors</h2>

 <!--
 	New Eclipse projects require a minimum of two mentors from the Architecture
 	Council. You need to identify two mentors before the project is created. The
 	proposal can be posted before this section is filled in (it's a little easier
 	to find a mentor when the proposal itself is public).
  -->

 <p>The following Architecture Council members will mentor this
 project:</p>

 <ul>
 	<li><a href="http://aniszczyk.org/">Chris Aniszczyk (Red Hat)</a></li>
 	<li>Bernd Kolb (SAP)</li>
 </ul>

 <h2 id="interested">Interested Parties</h2>

 <!--
 	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.
  -->

 <p>The following individuals, organisations, companies and projects
 have expressed interest in this project:</p>

 <ul>
 	<li><a href="http://aniszczyk.org/">Chris Aniszczyk (Red Hat)</a></li>
 	<li>Jochen Hiller (Deutsche Telekom AG)</li>
 	<li>Holger Staudacher (EclipseSource)</li>
 	<li>Sopot &Ccedil;ela</li>
 </ul>

 <!--
 <h2>Project Scheduling</h2>
 -->

 <!--
 	Describe, in rough terms, what the basic scheduling of the project will
 	be. You might, for example, include an indication of when an initial contribution
 	should be expected, when your first build will be ready, etc. Exact
 	dates are not required.
  -->

 <h2>Changes to this Document</h2>

 <!--
 	List any changes that have occurred in the document here.
 	You only need to document changes that have occurred after the document
 	has been posted live for the community to view and comment.
  -->

 <table>
 	<tr>
 		<th>17-December-2010</th>
 		<th>Initial Version</th>
 	</tr>
 	<tr>
 		<th>07-February-2011</th>
 		<th>Updated Interested Parties</th>
 	</tr>
 </table>

 </body>
 </html>
	<!--
	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
	-->

	<html>
	<head>

	<!--
	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.
	-->

	<title>Skalli</title>
	</head>

	<!--
	We make use of the 'classic' HTML Definition List (dl) tag to specify
	committers. I know... you haven't seen this tag in a long while...
	-->

	<style>
	dt {
	display: list-item;
	list-style-position: outside;
	list-style-image:
	url(/eclipse.org-common/themes/Phoenix/images/arrow.gif);
	margin-left: 16px;
	}

	dd {
	margin-left: 25px;
	margin-bottom: 5px;
	}
	</style>

	<body>

	<p>The Skalli project is a proposed open source incubator project
	under the <a
	href="http://www.eclipse.org/projects/project_summary.php?projectid=technology">Eclipse
	Technology Project</a>.</p>
	<!--
	The communication channel must be specified. Typically, this is the
	"Proposals" forum. In general, you don't need to change this.
	-->
	<p>This proposal is in the Project Proposal Phase (as defined in the
	Eclipse Development Process) and is written to declare its intent and
	scope. We solicit additional participation and input from the Eclipse
	community. Please send all feedback to the <a
	href="http://www.eclipse.org/forums/eclipse.proposals">Eclipse
	Proposals</a> Forum.</p>

	<p>This proposal is structured as follows. Section <a
	href="#background">Background</a> gives the motivation of the project
	and provides some background information about the origins of the
	proposed project. Section <a href="#contribution">Initial
	Contribution</a> describes the current state of the project and the initial
	contributions that will be made. Section <a href="#scope">Scope</a>
	outlines the initial set of tools and platforms this project aims to
	deliver to its users; <a href="#description">Description</a> gives
	little more details on the intermediate goals. Section <a
	href="#related">Related Eclipse Projects</a> describes potential future
	connections between current eclipse.org projects and the proposed
	project as well as likely collaborations. The remaining sections (<a
	href="#committers">Committers</a>, <a href="#mentors">Mentors</a>, <a
	href="#interested">Interested Parties</a>) describe what their names
	suggest.</p>

	<h2 id="background">Background</h2>

	<!--
	Optionally provide the background that has lead you to creating this project.
	-->
	<p>The tentative name of the project is Skalli which comes from
	Norse mythology.</p>

	<pre>
	In Norse mythology, Skalli is a wolf that pursues the chariot
	of the sun goddess Sol across the skies every day.
	He has a twin brother Hati that pursues Máni, the moon.

	</pre>

	<p>Project management in open source varies from community to
	community. There are no good open source solutions out there that help
	manage your project and the Eclipse community has grown out of the
	current project management infrastructure at eclipse.org. The Skalli
	project aims at closing this gap.
	<p>
	<h2 id="scope">Scope</h2>

	<!--
	All projects must have a well-defined scope. Describe, concisely, what
	is in-scope and (optionally) what is out-of-scope. An Eclipse project
	cannot have an open-ended scope.
	-->

	<p>One of the major goals of this project is to make a new
	generation project management tool accessible and usable by the Eclipse
	community and other open source projects.</p>

	<p>Thereby Skalli forms the central entry point to all projects and
	creates transparency over the existing projects. It leverages search
	technologies and social network mechanisms in order to structure and
	find them.</p>

	<p>This project however does not aim at replacing existing tools
	like wiki, bugtracker and source code management system. It merely links
	to them and integrates their data and services as far as needed in order
	to let users - and through a REST API also other tools - gain an
	overview on each project's state and locate its resources.</p>

	<h2 id="description">Description</h2>

	<!--
	Describe the project here. Be concise, but provide enough information that
	somebody who doesn't already know very much about your project idea or domain
	has at least a fighting chance of understanding its purpose.
	-->

	<p>The goal of the project is to build an extensible system for
	organizing projects.</p>

	<p>This includes support for creation of new projects and all the
	little processes (e.g. committer election) needed within the lifecycle
	of a project. Additionally, maintenance of project data must be simple.
	Committers should be enabled to request additional infrastructure
	according to the rules of the community in a seamless way. This should
	be realized by offering self-services within Skalli as much as feasible
	and integrating them with the corresponding community infrastructure.</p>

	<p>Existing projects can be browsed and searched for, so users can
	find what they are looking for easily. Project details like source code
	location, bugtracker and quality metrics can be maintained by the
	corresponding committers, so that everyone is able to locate them
	instantly. Social media features like tagging and recommending projects
	help guiding users to the projects they are looking for.</p>

	<p>Technically, the flexibility and extensibility is achieved by
	leveraging the mechanisms provided by OSGi. So modules introducing new
	UI building blocks or connections to additional services can be added as
	required.</p>

	<p>The data about projects maintained within Skalli is also
	available via a REST API. This enables an ecosystem of loosely coupled
	tools that can use this data to provide additional services (e.g.
	quality reporting).</p>

	<p>The short-term target is to reflect project related workflows
	(e.g. committer election and other voting) as well as the integration
	into major development infrastructure tools like Hudson, Git and Gerrit.
	By doing that, self-services can be provided to the teams that will
	reduce the administrative overhead of running a development
	infrastructure.</p>

	<h2 id="related">Relationship with other Eclipse projects</h2>
	<p>The project so far does not yet have strong relationships to
	existing Eclipse projects. It does however run on <a
	href="http://www.eclipse.org/virgo/">Eclipse Virgo</a> and uses the
	Eclipse preference store.</p>

	<p>Furthermore, once the foundation is laid and the project matures,
	the goal is to provide a suitable replacement for the current
	eclipse.org foundation portal in alignment with the Phoenix project.</p>

	<p>The <a href="http://www.eclipse.org/emf">EMF</a> toolset and <a
	href="http://www.eclipse.org/eclipselink">EclipseLink</a> could also be
	useful for this project and will potentially be used in future.</p>

	<!--
	<h2>Why Eclipse?</h2>
	-->

	<!--
	Answer these two questions: What value does this project bring to the Eclipse
	community? What value do you expect to obtain from hosting your project at Eclipse?

	What value do you get by having your project at Eclipse over and above the value
	of hosting at Eclipse Labs?
	-->

	<h2 id="contribution">Initial Contribution</h2>

	<!--
	Projects are expected to arrive at Eclipse with existing code.

	Describe the existing code that will be contributed to the project. Please provide
	a couple of paragraphs describing the code with modest detail, including important
	information like code ownership (who holds the copyright?), and some consideration
	of community that exists around the code. Include a listing of third-party libraries
	and associated licenses.
	-->
	<p>The Skalli project will be seeded with an initial contribution
	coming from SAP. It contains the basic set of features that already can
	be used productively and provides the foundation for integration of
	additional services and processes.</p>

	<p>The contribution already includes project maintenance and data
	validation, searching for projects and contained components, a REST API
	for data retrieval. It runs on the <a
	href="http://www.eclipse.org/virgo/">Eclipse Virgo</a> server. For the
	web interface, it currently uses JSP and <a
	href="http://vaadin.com/home">Vaadin</a> as UI technologies.</p>

	<!--
	<h2>Legal Issues</h2>
	-->

	<!--
	Please describe any potential legal issues in this section. Does somebody else
	own the trademark to the project name? Is there some issue that prevents you
	from licensing the project under the Eclipse Public License? Are parts of the
	code available under some other license? Are there any LGPL/GPL bits that you
	absolutely require?
	-->

	<h2 id="committers">Committers</h2>

	<!--
	List any initial committers that should be provisioned along with the
	new project. Include affiliation, but do not include email addresses at
	this point.
	-->

	<p>The following individuals are proposed as initial committers to
	the project:</p>

	<dl>
	<dt><b>Simon Kaufmann, SAP (Project Lead)</b></dt>
	<dd></dd>
	<dt><b>Matthias Sohn, SAP (Project Lead)</b></dt>
	<dd></dd>
	<dt>Chris Aniszczyk, Red Hat</dt>
	<dd></dd>
	<dt>Michael Ochmann, SAP</dt>
	<dd></dd>
	<dt>Jürgen Schneider, SAP</dt>
	<dd></dd>
	<dt>Jochen Hiller, Deutsche Telekom AG</dt>
	<dd></dd>
	<dt>Bernd Kolb, SAP</dt>
	<dd></dd>
	</dl>

	<p>We welcome additional committers and contributions.</p>

	<!--
	Describe any initial contributions of code that will be brought to the
	project. If there is no existing code, just remove this section.
	-->

	<h2 id="mentors">Mentors</h2>

	<!--
	New Eclipse projects require a minimum of two mentors from the Architecture
	Council. You need to identify two mentors before the project is created. The
	proposal can be posted before this section is filled in (it's a little easier
	to find a mentor when the proposal itself is public).
	-->

	<p>The following Architecture Council members will mentor this
	project:</p>

	<ul>
	<li><a href="http://aniszczyk.org/">Chris Aniszczyk (Red Hat)</a></li>
	<li>Bernd Kolb (SAP)</li>
	</ul>

	<h2 id="interested">Interested Parties</h2>

	<!--
	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.
	-->

	<p>The following individuals, organisations, companies and projects
	have expressed interest in this project:</p>

	<ul>
	<li><a href="http://aniszczyk.org/">Chris Aniszczyk (Red Hat)</a></li>
	<li>Jochen Hiller (Deutsche Telekom AG)</li>
	<li>Holger Staudacher (EclipseSource)</li>
	<li>Sopot Çela</li>
	</ul>

	<!--
	<h2>Project Scheduling</h2>
	-->

	<!--
	Describe, in rough terms, what the basic scheduling of the project will
	be. You might, for example, include an indication of when an initial contribution
	should be expected, when your first build will be ready, etc. Exact
	dates are not required.
	-->

	<h2>Changes to this Document</h2>

	<!--
	List any changes that have occurred in the document here.
	You only need to document changes that have occurred after the document
	has been posted live for the community to view and comment.
	-->

	<table>
	<tr>
	<th>17-December-2010</th>
	<th>Initial Version</th>
	</tr>
	<tr>
	<th>07-February-2011</th>
	<th>Updated Interested Parties</th>
	</tr>
	</table>

	</body>
	</html>