phoenix


The project has been created. Please visit the project page.

This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare the intent and scope of a proposed Technology PMC Project called Project Phoenix. In addition, this proposal is written to solicit additional participation and inputs from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.phoenix newsgroup.

Introduction

The scope of this project is to improve the accessibility and quality of the information needed by the community to perform their tasks and provide a single access point to that information. The "community" is the very broad set of constituents: consumers, committers, contributors and members who all have requirements which need to be met by the Eclipse.org website.

Keen observers of the Eclipse Foundation will have noticed that we have successfully completed our hardware migration. There is still work to be done as we have a few more servers to bring up. But we are now running the site on brand new servers.

Many thanks to our webmaster Denis Roy for several lost weekends and many long hours getting this done. Thanks also to HP, IBM, Intel and Novell for donating the hardware and software to run this new infrastructure. Thanks are also due to Susan Iwai and others who kept the website up and its content fresh during the past several years of wild growth in projects, members and users.

The next stage is to get started on improving the functionality of our website. We believe that it is fair to say that everyone agrees that an overhaul is needed.

Description


1. Background


The purpose of this project is to improve the usability of the eclipse.org site, improving productivity and reducing duplication of effort across the eclipse user community. One of the key goals of the project is to employ a Content Management System, in addition to making critical improvements to the website that will include: improved navigation and information support for an expanded user base; new channels for members to message and collaborate with each other and the community; new channels for developer interactions.

This project will analyse the information needs of the Eclipse.org audience[1]. Initial project findings include the following opportunities:

  1. Improve the accessibility and quality of the information needed by the community to perform their tasks; provide a single access point to that information; link and rationalise the information, thereby reducing duplication of information and removing access to out-of-date information
  2. Make technology available (easy to find, understand and download)
    a) Tools (such as plug-ins)
    b) Resources (support information for those tools)
  3. Establish publishing models (workflow) and guidelines for Eclipse.org
  4. Implement cross-jurisdictional collaborative tools (e.g. WIKI, Blogs) and make the most of networking opportunities
  5. Create a showcase for members and the community
  6. Establish user profile administration if necessary

This project addresses the first opportunity above – “Improve the accessibility and quality of the information…” - and aligns with the following vision statement and web site values…

Vision
The Eclipse.org web site should: enable collaboration and networking within the community, encourage usage, create opportunities and thrive on the active participation of its audience.

Values
The Eclipse.org web site should…

  1. Be community focused
  2. Place emphasis on clarity of content in its delivery
  3. Provide an open, meritocratic and equal playing field for users
  4. Reflect the character of the entire ecosystem.
[1] The audiences for Eclipse.org have been initially identified as:
1. Users
2. Committers
3. Contributors
4. Plug-In Developer
5. Members



2. Project Objectives


“Eclipse.org” is an essential part of the Eclipse Foundation’s initiative to share information and knowledge across its world-wide community. This requires the creation of an information system that can be easily used by community members of diverse skill levels. This information system will reside on one web site that will:

  1. Provide access to information across the Eclipse community in a manner that:
    · Enables easy processing – providing a hierarchical navigation scheme (taxonomy)
    · Providing multiple routes to information
    · Offers visual feedback
    · Meets the audience’s purpose
  2. Be a vehicle for community-wide communication, collaboration and networking
    · providing access to collaborative tools such as WIKIS, Blogs
    · storing information in English while supporting other language groups as required
  3. Places our audience at the focal point of design and development
  4. Seeks feedback (on the design & development) from the community by using the open source rules of engagement
  5. Reflect the professional character of the Eclipse development platform and its community
  6. Ensures CMS tool
    i. allows for easy additions & restructuring
    ii. has a clear separation of content and presentation
  7. Identify content ownership while enabling content owners to manage their own content, eliminate redundant and/or expired information, and be the key drivers in the site's development (e.g. projects)



3. Draft Deliverables


Phase Milestone Deliverables

  1. Visualisation and Analysis
    • Project proposal & objectives
    • Design & functional targets April 2005
  2. Site Architecture and Planning
    • Information Architecture Plan [site vocabulary, directory catalogue, information data model, use case analysis & storyboards]
    • User interface Plan [graphic specifications]
    • Systems Plan [CMS tool analysis technical specifications, enterprise architecture coordination} June 2005
  3. Initial Site Design
    • navigation design,
    • thematic development
    • site wireframes
  4. Site Design Refined
    • on line alpha testing
    • directory catalogue refinements
    • technical refinements
  5. Site Development and Testing
    • install development environment
    • implement data model
    • information and content migration
    • front and GUI development
    • admin GUI development
  6. Deploy to Production
    • online beta testing & refinements
  7. Site Launch
  8. Support and Maintenance
  9. Site Evaluation
  10. Prioritize ongoing enhancements October 2005

Organization

We are looking for others to participate in all aspects of this project. If you are interested in actively participating, please take part in the newsgroup discussions or ask to be added to the list of interested parties.
The proposed initial set of commiters will be:

  • Mike Milinkovich, Eclipse Foundation
  • Denis Roy, Eclipse Foundation
  • Susan Iwai, IBM
  • Bjorn Freeman-Benson, Eclipse Foundation
  • Ian Skerrett, Eclipse Foundation
  • Andrew Geraghty, Eclipse Foundation