Project
Phoenix - identified audience personas and
Information needs
The following outlines the 5
identified Eclipse.org audience members and their individual highest
priority information needs:
1. User
Ø
person
who makes use of one or more Eclipse projects (tools) to perform some function,
including support resources
Ø
a
subset of users are consumers who make use of the downloads but do not use Eclipse support resources
Identified Needs
v
Downloads
o
want
to use Eclipse (download specific Eclipse tool, specific
information)
o
specific
developers [C++/J2EE/PHP...] need to download:
·
download
tools and updates
·
download
the platform
·
download
a project
v
What’s
New info
o
learn
about (via push technology) updates to
·
tools
·
plug-ins
·
new
projects
v
Search
for extra plug-ins
o
Learn
about :
·
places
to source commercial solutions , OS extensions to problems read about tools,
plans
·
download:
Eclipse plug-ins & Eclipse.org plug-ins
v
Help
Info
o
Eclipse
Software help: how to’s, FAQ
o
submit
help questions on newsgroups and get answers
o
report
bugs
o
join
discussions
- User
documentation
o
How
to:
·
first
time installation instructions and pointers
·
start
using Eclipse for Java, C++, PHP, etc…project/projects
·
use
tools
·
get
started
·
understand
best practices
·
understand
what other people are doing with Eclipse
·
join
the community (i.e. become a committer)
o
Articles
o
White
papers
o
Technology
instructions
2. Committer
Ø
contributor
who works on one or more Eclipse projects with the ability to write to Eclipse’s
CVS repositories
Identified Needs
v
Code
access (CVS) read and write
1.
Self
management of content publication within the context of a general
framework
o
Easy
to access download
o
Access
to development tools
o
Self
management to development tools
v
Bugzilla
feedback from Users (R+W)
o
access
to CVS & Bugzilla
o
bugzilla
mailing lists
o
bugzilla
newsgroups
v
Provisioning
o
How
to work with the eclipse.org infrastructure tools info ( e.g. create a plug-in,
create a website)
o
Infrastructure
status (is anything down?)
o
How
to signal a problem
o
make
a request to the webmaster
v
Change
Tracking See
and indicate what’s new – and event driven review (e.g. RSS)
of:
·
news
releases
·
news
·
cross
project info
o
project
dashboard stats
o
follow
release plans
o
contribute
release plans
o
How
to signal a problem
o
make
a request to the webmaster
v
API
documents and deltas
o
follow
and contribute architecture documents
o
exchange
cross project information (via a push technology):
·
release
changes
·
architectural
changes
·
API
changes
v
Collaborative
Tools Fourms
for community development discussions. (Read/Post information to generate;
collaborative discussion and documentation about a project and its code
ability)
·
BLOGS
·
WIKIS
·
Newsgroups
·
Mailing
Lists
3. .
Contributor
Ø
provides
content on the Eclipse website including: newsgroup postings, emails to mailing
lists, posts a news article
Ø
works
full time contributing code to one or more Eclipse
projects
Ø
files
a bug using bugzilla
Identified Needs
v
Code
Access (R + patch submissions
o
access
downloads
o
access
to CVS and Bugzilla
o
access
to source code
v
Bugzilla
(R+W)
o
Read/write
to bugzilla newsgroups, mailing lists
o
Access
to CVS and bugzilla
o
create
a bug report
o
follow status on their opened bugs access
downloads
v
Plan/roadmap/status
of projects/timeline (R)
o
find
and comment on release plans
o
find
and comment on architecture documents
v
Change
Tracking See
and indicate what’s new – and event driven review (e.g. RSS)
of:
·
news
releases
·
news
·
cross
project info
o
project
dashboard stats
o
follow
release plans
o
contribute
release plans
o
How
to signal a problem
o
make
a request to the webmaster
v
Plan/roadmap/status
of projects/timeline (R)
o
Find
out about cross project information of interest such as: release and
architectural and API changes
o
Roadmap
info so they understand the opportunity for their plug-in
v
Change
Tracking See
and indicate what’s new – and event driven review (e.g. RSS)
of:
·
news
releases
·
news
·
cross
project info
v
API
documents and deltas
o
understand
API’s and how to use frameworks
o
project
specific information on extensibility:
·
release
changes
·
architectural
changes
·
API
changes
5. Corporate
and Individual Member
Ø
Companies
that support Eclipse and have joined the Foundation as Strategic members, an add-in provider
and/or associate member
Ø
Committer
who has joined the foundation as a voting member of the committer member
class
Identified Information Needs
v
Membership
and governance info:
o
how
to join
o
how
to participate
o
new
member jumpstart info
v
Promote
their company/products:
o
publicise
membership
o
publicise
contribution to Eclipse
o
publish
info about their commercial products
o
upload
their plug-ins for download by:
§
???
§
???
v
Promote
their company/products:
o
publicize
membership
v
Membership
benefits:
o
networking
opportunities
o
marketing
opportunities
o
members
only opportunities
v
Membership
recognition
|