Thanks Kevin. IMHO this is a significantly important group to the
overall success so communicating effectively is important.
Clarification. One paragraph or so is the desired content length. I
don't think you can do much better for any audience with one sentence.
Think elevator pitch in a low-rise building :-)
As much as we would like to think that the value of e4 is inherent in
"its the next Eclipse", most of the rest of the community wants to know
what does it do for them. This requires a move from the techno-geek
"cool" factor to identifying the business value delivered to someone
building on top of the platform. What pain points are addressed?
Jeff
Kevin McGuire wrote:
I realize that my comment might've
come
across as being uncooperative, so just to clarify:
We're clearly failing at communicating to that audience. We're
technical
people and write, with some success, to other technical people. For
my part, I never write something for business people to consume. I
don't know how to communicate to that audience [1], and though I'd like
to do better, me trying again without guidance is unlikely to produce a
better result.
Someone with business/marketing knowledge who *does* know how to
communicate
to that audience could help guide. I was guessing that by the time they
explain what we need to communicate, they're likely to have just
written
the one sentence. :)
Seems like a lot of discussion when
all that was asked for was a single sentence but I'm concerned by the
larger
issue of communication and I'd like to see a more coordinated,
coherent,
and, well, professional approach, so lets start now. If I had an
"e4 Inc" company, I'd expect the marketing department to be quite
involved in such an endeavour (and I'm guessing it wouldn't be staffed
by developers). So how do we get the next best thing?
Regards,
Kevin
[1] As proof of this, when I spell
checked
this email I discovered I misspelled "marketing".
Maybe those putting together the survey could provide guidance on how
the
information can be tuned to that target audience (say, by taking the
proposal
and reworking it as an example :> ).
Kevin
All I can say is that the people putting together the survey feel that
the information in its current form is not readily consumable by their
target audience. Providing tuned information for this audience will
improve the quality of the feedback we receive.
Jeff
Oberhuber, Martin wrote:
Why not have them "pull" any background technical information
rather than trying to "push" something that's bound to be incomplete
when it should just be one sentence. So what about this:
e4 is the community effort for building the next generation of the
Eclipse
Platform. For any details, see the e4
project proposal
[1].
[1] http://www.eclipse.org/proposals/e4/
Of course we should eventually prepare something on the web or the wiki
that's more current but still as informative as the project proposal.
But
for now, I still find the proposal most appropriate for persons seeking
a higher-level understanding of e4.
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind
River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
From: e4-dev-bounces@xxxxxxxxxxx
[mailto:e4-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jeff McAffer
Sent: Sunday, January 11, 2009 8:18 PM
To: E4 Project developer mailing list
Subject: [e4-dev] e4 Survey
At a recent board meeting we had a discussion about e4 and what it
means
to the Eclipse membership. The results were quite mixed with widely
differing opinions and thoughts. One thing that did come out was
the idea of polling the membership for some feedback. Mike Taylor,
an elected Solution Provider director on the board volunteered to poll
the Solution Providers on this topic and has set about creating a
survey.
As part of this there should be a description of e4. I'll quote
Mike on this.
"I had seen the e4 description on the wiki page, but didn't find it
satisfying for the purposes of this survey. This survey will go to the
contact (often a "business" person) who is the designated EMO
contact point for a particular Solution Provider company. Its primary
intent
is to get a high-level feeling for what people know and think about e4
right now. Its not really designed to be a technical or feature
survey."
It would be great if as a community we can provide a brief (one
paragraph)
description of e4. Something a bit deeper than "the next generation
of Eclipse" but a bit shallower than what's on the wiki.
This is a really good opportunity to raise awareness of e4 and
simultaneously
get valuable feedback and input.
Jeff
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
|
