blob: cc6a3575094111716624875129fe9eb19925fa64 [file] [log] [blame]
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:
Direct any questions about this template to
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.
dt {
display: list-item;
dd {
<p>The Vert.x project is a proposed open source project under the <a
href="">RT 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="">Eclipse Proposals</a>
Optionally provide the background that has lead you to creating this project.
<p>The inspiration for the project came from two main areas:</p>
<li>The growing interest in non blocking, asynchronous approaches to application design motivated by scalability.</li>
<li>The recent trend towards stripped down simplicity in APIs and a rejection of complexity that had dominated application platforms
in the previous 10 or more years.</li>
<p>In particular the project was influenced by Node.js. There was nothing similar
for the JVM and the idea was formed to create a project superficially similar to Node.js but running on the JVM, and which
could leverage the superior virtual machine. Since the JVM also supported multiple languages (unlike V8) the idea was that the user could choose
from multiple languages in which to code their application.</p>
<p>Initially the project was named 'Node.x' - the 'x' representing the fact that the platform was polyglot, but was renamed
a few months later in order to avoid any potential future trademark issues with Joyent who own the Node.js trademark.
The new name chosen was Vert.x (pronounced 'Vertex') - again the .x representing the polyglot nature of the project, and a vertex is
of course a synonym for a node.</p>
<p>The latest release of Vert.x is 1.3.1, and there is a healthy and growing community. Vert.x has attracted a lot of attention so far
and is currently <a href="">one of the most followed Java projects on GitHub</a>
<p>Work has already started on Vert.x 2.0 which aims to improve the platform in multiple areas and take the project to
the next level.</p>
Vert.x is a framework for the next generation of asynchronous, effortlessly scalable, concurrent applications.
<li>Vert.x provides primarily asynchronous APIs for writing truly scalable non-blocking applications</li>
<li>Vert.x is polyglot. Developers write their components using JVM languages. Multiple programming languages can be used in a single application</li>
<li>Vert.x has a very simple concurrency model. Vert.x allows you to write all your code as single threaded, this greatly simplifies development. (No more 'synchronized', 'volatile' or explicit locking)</li>
<p>Vert.x is an asynchronous application platform for the modern web and enterprise.</p>
<li>Vert.x has a very simple concurrency model. Vert.x allows you to write all your code as single threaded, this greatly simplifies development.
(No more 'synchronized', 'volatile' or explicit locking).</li>
<li>Vert.x includes a distributed event bus that spans the client and server side so your applications components can communicate incredibly easily.
The event bus even penetrates into in-browser JavaScript allowing you to create effortless so-called 'real-time' web applications.</li>
<li>Vert.x is modular. It provides a simple yet powerful module system, and a public module repository to encourage an ecosystem of modules published by the community.</li>
<li>Vert.x takes advantage of the JVM and scales seamlessly over available cores without having to manually fork multiple servers and handle inter process communication between them.</li>
<h2>Why Eclipse?</h2>
<p>The Eclipse foundation has a proven track record at building healthy environments for open source projects. It also has unique
ecosystem of individuals and organizations who wish to collaborate on commercially-friendly open source software.</p>
<p>For Vert.x to continue to flourish with a vibrant community, it's important that the project is hosted in a neutral
organisation where the aims of any one entity cannot steer the project. We believe the project is owned by the
community and it's up to the community, led by the project lead, to determine the course of the project.</p>
<p>We also believe that good IP management as provided by Eclipse will be a good thing for Vert.x as we aim to get more
use in large enterprises.</p>
<h2>Initial Contribution</h2>
<p>The code is written mainly in Java with smaller amounts of Ruby, Groovy, JavaScript and Python.</p>
<p>There have been around 68 contributors during the course of the project. Most of the contributions were in the form
of small pull requests.</p>
<h2>Legal Issues</h2>
<p>The code is mainly licensed under the ALv2. At Eclipse, Vert.x, will be dual-licensed under the ALv2 and EPL.</p>
The 'Vert.x' trademark is currently owned by VMWare. As part of joining the Eclipse Foundation, VMWare agrees to transfer rights to the mark to the Eclipse Foundation.
<p>The largest contributor to the project is Tim Fox - whose copyright is owned by VMware</p>
<p>For most larger contributions the SpringSource CLA should have be signed by the contributor. For small (few line) contributions,
contributors weren't asked to sign a CLA.</p>
<p>The code in the project is almost all licensed by VMware under the ASL 2.0. There a small number of exceptions including
a public domain source file ( and another licensed under the MIT license
<p>There are a few files in the project which were taken from previous Red Hat projects (mainly in the websockets implementation),
also licensed under ASL 2.0</p>
<p>Vert.x currently distributes the following third party libraries</p>
<li>Netty 3.5.9 final. License is ASL 2.0</li>
<li>Hazelcast 2.4.1. License is ASL 2.0</li>
<li>Jackson 1.9.4. License is ASL 2.0</li>
<li>Groovy 2.0.5. License is ASL 2.0</li>
<li>Mozilla Rhino 1.7R4. License is MPL 2.0</li>
<p>The following individuals are proposed as initial committers to the project:</p>
<li>Tim Fox, Red Hat (lead)</li>
<li>Stuart Williams, VMware</li>
<li>Norman Maurer, Red Hat</li>
<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.
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
<li>Chris Aniszczyk</li>
<li>John Arthorne</li>
<h2>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>
<li>Chris Aniszczyk, Twitter</li>
<li>Mark Little, Red Hat</li>
<li>Asher Tarnopolski, Exent Technologies</li>
<li>Janne Hietamaki, SparkBE</li>
<li>Daryl Teo</li>
<li>Mark Spritzler</li>
<li>Diego López León, IT Crowd Argentina</li>
<li>Nate McCall, Apigee</li>
<li>Paulo Lopes</li>
<li>Bruno Santos</li>
<li>Toshihiro Shimizu</li>
<li>Norman Maurer, Red Hat</li>
<li>Juergen Donnerstag</li>
<li>Adam Gent, SnapHop</li>
<li>Simone Scarduzio,</li>
<li>Craig McClanahan, Jive Software</li>
<li>Michael Li</li>
<li>Martijn Verburg, jClarity</li>
<li>Henry Saputra, Platfora (</li>
<li>Nathan Pahucki, Autodesk Inc.</li>
<li>Hannes, 3KOLOR GmbH</li>
<li>Chen Wang, Volcube</li>
<li>Prasad Y,</li>
<li>Istvan Pato,</li>
<li>Janth Hulha,</li>
<li>Min-Gyu Chung</li>
<li>Nathan Pahucki, Autodesk, inc</li>
<li>Ian Roughley</li>
<li>Vicky Kak</li>
<li>Raphael Cheun</li>
<li>Ken Yee</li>
<li>Bartek Zdanowski, TouK sp. z o.o. s.k.a. Poland</li>
<li>Igor Akulov,</li>
<li>Carter Youngblood</li>
<li>Arnold Schrijver, Adnovate</li>
<li>Stephan Mulhall, Osgo Solutions</li>
<li>Stephane Maldini, VMware</li>
<li>Jon Schneider, conundrum software (</li>
<li>Mikael.Karon and Adrian Gonzalez, English First (, Englishtown (</li>
<li>Rost Kanyuchenko</li>
<li>Pedro Fidalgo Machado</li>
<li>Alexander Battisti, Jambit GmbH</li>
<li>Joern Bernhardt, Company is Campudus (</li>
<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.
The project is starting an initial contribution in March 2013. We expect to have the existing code, site and documentation
migrated by end of April 2013 (this assumes that the IP process goes smoothly and quickly).
<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.
<td>Interested parties added.</td>
<td>Interested parties added.</td>
<td>Document created</td>