| RE: [phoenix-dev] Audience Persona Sheet |
|
Andrew, I think it is great that we are
starting to identify the needs for each user. This seems like a great
start. Here are some comments. 1. I really don’t understand the
difference between consumer and user? Just saying a user actually uses
support resources seems to be pretty specific. I would
suggest that we have no idea if someone will actually use support
resources. In fact, we should always strive for making sure
Consumers are aware and take advantage of the support resources. That way
we can help ensure they are successful. In my mind these seem to be the
same category. 2. Why does a user care about membership
information? We actually don’t offer membership to users. 3. Users are interested in communicating
with other users to share experiences or learn from other people.
We need to create an environment to make this happen. Things like
ranking systems for white papers, documentation, even Eclipe projects. 4. I believe we will have different types
of users. Off the top of my head we have Java developers, J2EE
develoeprs, embedded developers, C/C++ developers, Linux developers,
architects, testers. We need to present information that is relevant to
what they are trying to do. 5. Is the neeed ‘How to start a
project’ meant to be ‘How to start an Eclipse open source
project?’ or How to use the Eclipse IDE and use the project
wizard. I think you mean the ‘start an open source project’?
If so, then I think the majority of users will not care about this. If
fact I think very few people care about how to start an open source
project. 6. Users will want to know other
resources for support. Where can they get help and information that might
not be on eclipse.org. For instance, what seminars/trade shows are
available. 7. For Plug-in developers, I don’t
see them posting release plans or architecture documents on
eclipse.org. Plug-in developers have no formal relationship with
eclipse.org and are focus on creating ‘products’.either for
commerical sale or open source distribution. 8. Plug-in developers will be interested
in promoting their ‘product’ on eclipse.org. 9. Member companies are interested in
promoting their products via eclipse.org. I think we can do this via a
product catalog, membership listing, and highlighting their news items.
We will also provide ‘members only’ marketing opportunities for
participating in trade shows, advertising, editorial content, market research,
etc. 10. Member companies also want to get
credit for being associated with Eclipse and providing resources to eclipse. 11. A benefit of being a member is the
ability to network with other member companies. We can do this via
f2f meeting but it would also be interesting to find options to do it via the
internet. 12. Member companies would like to have
insight into the user community, ie stats on usage of projects. I hope this helps. Ian From:
phoenix-dev-admin@xxxxxxxxxxx [mailto:phoenix-dev-admin@xxxxxxxxxxx] On Behalf Of andrew geraghty Susan, I have compiled emails/discussions info this chart. Obviously we are currently working from the general and
slowly getting more specific and detailed. In tandem with this exercise, and
the benchmark site analysis, we need a content audit so we can document
the volume and complexity of the current state of the content and functionality
on Eclipse.org The three documents combined will be useful for the core
team to form preliminary design and functional targets (optimisation and
efficiency recommendations) Comments Welcome Andrew
|