June 12, 2007
June 12, 2007 – Provided update based on mid-year view
November 30, 2006 – Added content for budgeted program spend
November 8, 2006 – Sent to Finance Committee for review and feedback
November 6, 2006 – Second draft for review by EMO staff
November 4, 2006 – First draft
The purpose of this document is to provide a high-level overview of the program spending projected by the Eclipse Foundation in 2007 for feedback from the Finance Committee. These programs will be used by the EMO to drive the 2007 fiscal budget for the Foundation.
As per the Strategic Plan, the major goals of the Eclipse Foundation are:
Demonstrate technology leadership and innovation.
Drive industry perception.
Foster growth and adoption.
Cultivate commercial success
Demonstrate operational excellence.
Please note that this document does not describe the content of the programs. Those will be defined by the EMO working in conjunction with the relevant communities (e.g. committer, add-in provider), working groups (e.g. marketing, embedded marketing) and those members interested in supporting a specific program.
Priority Codes:
P1 – Must have or in some cases “hygiene”
P2 – Should haves
P3 – Nice to haves
Prio |
Title |
Description |
$'s out |
$'s in |
Notes |
---|---|---|---|---|---|
P1 |
Development Infrastructure Improvements |
Continue to evolve and improve the development tools made available to the committer community. Examples include:
|
|
|
This will be primarily addressed via headcount rather than program spending. Update: Good progress being made.
|
P1 |
Project Workshops |
More Portland-hosted workshops like the Europa Build Workshop to get cross-project interactions around specific topics. |
15,000 |
|
The Ganymede build workshop was held. Intend to schedule more this year. CDT and Equinox summits happening in the Fall. DSDP and DTP project meetings happening in conjunction with the September members meeting.
|
P1 |
Symposiums |
Facilitate project-oriented (e.g. CDT) and topic-oriented (e.g. multi-language support) technical symposiums. |
(shared with above) |
|
Numerous technical symposiums being scheduled to run at Eclipse Summit Europe. |
P1 |
Cross-Project Sharing |
Support for better cross-project sharing of:
|
|
|
This will be primarily addressed via headcount rather than program spending. |
P1 |
Development Process Refinements |
Improve development process so that project reviews result in useful feedback and ultimately higher project quality. Development Process Improvement: Easier project creation. Better support for mentoring, and new review process |
|
|
Have rolled out new development process. For example, votes are required now for reviews. |
P2 |
Committer Meetings |
Schedule committer meetings at least once per quarter in various locales where we pull together people from a number of projects in a particular city. Location choices include Boston, Ottawa, San Francisco, Toronto, Portland. The Foundation would send someone to attend and facilitate, and pay for the meeting room (if needed) and pizza, etc. |
10,000 |
|
One committer meeting held in Portland. |
P2 |
New Project Kick-Starts and Project Mentoring |
Invite new project members to committer meetings and code camps to help them get started. Investigate the possibility of running a new distinct events for new projects at pre-determinted locations. (We cannot scale enough to travel out to each new project to help them get started, they will need to come to us.) In addition, look at ways to better mentor new and/or struggling projects from EMO and community resources. |
|
|
Committer bootcamp held at EclipseCon with great reviews. Mentor elections and process starting in June |
P3 |
Web-Based New Project Kick-Starts and Project Mentoring |
Considering that not everyone is willing/able to travel to these meetings, EMO should look at also arranging a few online events |
|
|
Not funded. (Therefore not done.) |
P3 |
Project Meetings |
Upon request, help facilitate project meetings. In particular, provide the necessary support for virtual and face-to-face Europa release train coordination meetings beyond the scope of the council meetings if required. |
5,000 |
|
This is effectively a duplicate of “Project Workshops” from above. |
Prio |
Title |
Description |
$'s out |
$'s in |
Notes |
---|---|---|---|---|---|
P1 |
Market Research |
Fund on-going market research with Evans Data on the growth of the Eclipse installed base and ecosystem. Approximately 50% of this research will be funded jointly with interested member companies. Purchase additional studies (e.g. IDC, BZ Media) as appropriate. |
45,000 |
40,000 |
Only funding the annual Evans Data research. |
P1 |
Giveaways |
Maintain a stock of Eclipse logoware. |
15,000 |
|
|
P1 |
Analyst Relations |
Maintain relationships with RedMonk and Forrester. Fund analyst research. |
58,500 |
|
|
P1 |
Public Relations (Europe) |
Continue to maintain an active European PR presence. |
22,000 |
|
|
P1 |
Public Relations (North America) |
Continue to maintain an active N.Am PR presence. |
98,000 |
|
|
P2 |
Event Sponsorship |
Provide a pool of money to sponsor Eclipse-specific events. The events could be short lunch ‘n learn sessions, symposiums, project summits or day long seminars. The events would be organized by Eclipse member companies and/or committers. |
35,000 |
|
At risk, due to lack of headcount resources to drive program. |
P2
|
Trade Shows and Conferences |
Arrange for booths and staffing for members to exhibit at events such as JavaOne, LinuxWorld and Embedded Systems. Ensure that the Eclipse Foundation has a presence at open source events such as OSCON. |
63,000 |
23,000 |
|
P3 |
Public Relations (Asia) |
Add a public relations presence in Asia. (Japan, India, Singapore have all been suggested.) |
|
|
|
Prio |
Title |
Description |
$'s out |
$'s in |
Notes |
---|---|---|---|---|---|
P1 |
EclipseForge |
Currently there are a number of hurdles facing a developer interested in creating and distributing Eclipse plug-ins. In addition, there are hurdles to creating a project at Eclipse. To help foster a greater community around the Eclipse plug-in architecture (especially for RCP), we will create an “EclipseForge” --- not to be hosted on eclipse.org --- which will make it easier for developers to build and deploy plug-ins. |
40,000 |
|
Funding removed, as this is no longer required. The Spaces project has been started with help from AOL. |
P1 |
Webinars, Flash demos and Podcasts |
In conjunction with interested members, develop and execute a series of webinars focused additional areas. (These will be likely hosted on EclipseLive. This line item is to cover the spending for the multimedia content generation.) |
105,500 |
20,000 |
|
P1 |
Approachability |
Continue to support and encourage out-of-the-box user experience improvements. Continue to support improvements to the Eclipse overall ease-of-learning and approachability. Continue to support and encourage website improvements. |
|
|
This will have to be driven by the projects and committer community. The EMO's role is to encourage and influence. The Eclipse Packaging Project is defining the packages and the download page for Europa. |
P2 |
Code Camps |
Leverage participation in conferences and events to arrange code camps for developers interested in learning more about Eclipse technologies. |
|
|
Not funded |
P2 |
Content Creation |
Continue to look for, and where appropriate fund, the development of quality Eclipse technical content. |
20,000 |
|
|
P2 |
EclipseLive! |
Establish a multi-media web site that promotes webinars, podcasts, Flash demos and videos clips specific to Eclipse and Eclipse-based products. Create a regular schedule of the content, so people can expect a regular flow of material. |
30,000 |
|
Up and running! |
P2 |
Project Maturity |
Work to have all top-level projects be heavily used by end-users and developers, and recognized as industry leading in their respective area. Also work to have existing incubator projects matured to achieve greater developer and user usage, and recognized as industry leading also |
|
|
This will be primarily addressed via headcount rather than program spending. No progress to date. |
P3 |
Developer Contests |
Develop and execute a series of contests targeted as growing awareness within the user developer community. For one example of such a contest, see the MySQL 5.0 contest. |
5,000 |
|
Under development. |
Prio |
Title |
Description |
$'s out |
$'s in |
Notes |
---|---|---|---|---|---|
P1 |
EPIC |
Continue to enhance our Eclipse community portal for plug-ins with a focus on driving value for plug-in providers via the eclipse.org website. Spend on advertising and other marketing programs to drive demand to the portal. |
40,000 |
|
One full-time staff dedicated to this. |
P1 |
Member Meetings |
Continue to grow and evolve our member meetings as important and worthwhile activities. |
30,000 |
|
|
P1 |
Technical Evangelism |
Increase investment in personnel, content and resources for technical evangelism of Eclipse technology and products. (Both in Europe and North America.) |
|
|
Currently have one employee working on evangelism. |
P2 |
Business Model Development |
Develop public collateral documents illustrating the various business models successfully applied by member companies. |
0 |
|
|
P2 |
Member Value Content |
Develop content which illustrates how member companies have achieved commercial success by their participation with Eclipse. |
0 |
|
|
P2 |
Case Studies |
Develop customer success case studies which illustrate the success of commercial products based on Eclipse technology. |
20,000 |
|
|
P2 |
Marketing Symposiums |
Arrange for at least two marketing symposiums for the Eclipse Membership in 2006. (One in North America, one in Europe.) |
12,500 |
|
|
P3 |
Common Collateral |
Develop common Eclipse marketing collateral for use by all member companies. |
|
|
|
Prio |
Title |
Description |
$'s out |
$'s in |
Notes |
---|---|---|---|---|---|
P1 |
Website |
Continue to invest in constantly improving our website as a source of information for users, and a service to our membership. |
|
|
Three full-time staff dedicated to website and IT. |
P1 |
Infrastructure Improvements |
Continue to evolve and improve the development tools made available to the projects. Examples include:
|
|
|
Three full-time staff dedicated to website and IT. |
P1 |
IP Process |
Continue to invest in improving and streamlining the approvals process for contributions to projects. |
6,200 |
|
Three full-time staff dedicated to this. Parallel approval process for incubators is up and running. Europa reviews completed on time. Still an on-going struggle to meet demand and expectations. |