Jump to: navigation, search

Difference between revisions of "Development Resources/HOWTO/Pre-Proposal Phase"

(Basic section)
(Basic section)
Line 36: Line 36:
===Basic section===
===Basic section===
* Provide a project name.
* Provide a project name.
* Read the linked "[[Development Resources/HOWTO/Starting A New Project|Starting A New Project]]" document and click "I know what I'm getting into" checkbox.
* Read the linked "[[Development Resources/HOWTO/Starting A New Project|Starting A New Project]]" document and click the "I know what I'm getting into" checkbox.
===Discussion section===
===Discussion section===

Revision as of 14:25, 7 July 2014




Project or Contribution?


  4. Is this new effort within the scope of the (optionally) enclosing parent Project and charter of the enclosing Top-Level Project? For example, a new "syntax highlighting editor for Pascal" would not be in scope of the "Web Standard Tools" project.

The new effort must be in scope with respect to its enclosing Project(s).

Project Name



Clear, Concise and Understandable Proposal

Create a proposal here.

We provide a template that you fill in with the proposal details.


  • Use plain non-technical English.
  • Describe all acronyms.
  • Provide urls where appropriate to direct reader for further information.


Basic section

  • Provide a project name.
  • Read the linked "Starting A New Project" document and click the "I know what I'm getting into" checkbox.

Discussion section


    • Describe where the project came from. What is the historical journey of the project; who/what company wrote the project. Did it go through any significant alterations/rewrites/language changes?


Provide an introductory paragraph describing what the project aims to be followed by several bullet points ie.


+ Provide both a stand-alone RCP application and a standard Eclipse plugin.
+ A core framework written in Java that exposes a generic interface for integration of trace types.
+ Support for custom text or XML parsers that can be added right from the graphical interface by the user.
+ Support for the following trace formats natively (no third-party libraries needed):
 + The Common Trace Format (CTF) (with specialized views for the LTTng kernel and user space tracers)
 + GDB traces
 + The Best Trace Format (BTF)
+ Provide support for the libpcap format. This is used in most network traces.
+ A repository of application-specific or problem-specific modules of all known trace type integration plugins.
+ Support for live trace readings.
+ Support for the new features in LTTng 2.5+.
+ Add more types of data-driven views and improve the existing ones.

Out of scope for the project //

The scope should allow for some flexibility, but still provide well-defined boundaries for the project.

  • What is in-scope?
  • What is out-of-scope?


  • Why Eclipse? The proposal should provide some discussion of why The Eclipse Foundation is the right place for the project to live. What do you expect to gain by having your project at Eclipse? What value does the project provide to the Eclipse community and eco-system?

Previous Proposals to Emulate


Proposal File Format and Submission

The proposal itself is a static HTML page (with a small fragment of PHP) using the standard Eclipse Proposal CSS style sheet (please use the template we provide). This template is heavily annotated with information and help; we suggest that you start there. Further, this document has been evolved to the point where it includes sufficient information to also serve as a Creation Review document.

We have found that there are a number of problems with HTML generated by Microsoft Word and thus ask that proposers use some other tool to create the page using only simple, static, standard HTML (let our stylesheet work its magic). Sorry, but the EMO does not have the time or resources to convert other file formats to the correct static HTML.





Posting and Declaration




*Project Declaration for the "XYZ Project"

    2. The Eclipse Foundation's Director of Committer Community
    3. The Eclipse Foundation's Executive Director

Press and Publicity




Legal Paperwork to Start Now




Next Steps

A proposal is generally posted for a minimum of two weeks. During this period, you should actively monitor the communication channel for the proposal and make sure that you address the needs of your burgeoning community. Provide updates to your proposal to the EMO.

Proposals that languish for more than three months will be withdrawn by the EMO.

When you are ready to create the project, inform the EMO. The proposal document itself can serve as the "Creation document" for the Creation Review. Prior to scheduling the creation review, however, the EMO will initiate a trademark search on the desired name for your project. This process may require trademark reassignment to the Eclipse Foundation. The trademark search must be completed before the review can be scheduled.

This page is moderated by the EMO