| [phoenix-dev] Project Statement Ammendments v1.05 |
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.
This project will analyse
the information needs of the Eclipse.org audience[1]. 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 (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 thrives 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 –demonstrate that open source and commercial can co-exist to mutual
benefit
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)
[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.
Members