| [phoenix-dev] Project Statement Updates V1.04 - thus far |
In March 2005,
The Eclipse Foundation identified the business need to redesign an Internet site
available to all Eclipse Foundation ‘Member Organisations’, ‘Software Users’ and
‘Committers’ in any jurisdiction at any time. The first site created under this
direction will develop the operating and development process that will move the
existing site content to a new Internet site that will provide a context
sensitive navigation, a consistent and appealing interface and new functionality
as required.
The purpose
of this document is to:
·
Reflect the overall intent of the
project that is, to summarise its key elements such as scope, objectives,
constraints, cost/benefits, etc.
·
Provide a basis for the project
evaluation, after the project has completed.
This
project is one of progressive elaboration as information becomes available and
decisions are made as to its direction.
This document will be updated and re-issued to reflect developments in
the project.
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 expanded user base; new channels for members to message and
collaborate with each other and the community; new channels for developer
interactions.
Currently the initial project’s
findings and recognised the opportunities to:
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 (i.e. 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 thrives on the active participation of its
audience.”
Values
1 - demonstrate that open source
and commercial can co-exist to mutual benefit
2 – provide an open,
meritocratic and equal playing field for users
3 – remain objective -
focus on facts and clarity of delivery
4 – be
community focused
1.
Provide access to information across the Eclipse community
in a manner that:
·
Enable 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
3.
Be a showcase for the Eclipse
development platform and its community
4.
Identify content ownership while
enabling content owners to manage their own content and be the key drivers in
the site's development (i.e. projects)
5.
Puts our audience at the focal point of
design and development.
6.
Identify information ownership and
eliminate redundant or expired information.
7.
Store information in English and other
languages as required.
8.
Ensure CMS tool
i.
allows for easy additions &
restructuring
ii.
has a clear separation of content and
presentation
9.
Involves the community (seeking
feedback) in the design & development by using the open source rules of
engagement
[1] At this
time the Eclipse.org audience has been identified as
1.
Consumers
2.
Users
3.
Committers
4.
Contributors
5.
Plug-In
Developer
6. Member Organisations