Nick,
No disagreement we need to add
quantifiable metrics. I just wanted to make sure we are all in agreement of
what we are trying to accomplish. I think Bjorn has already made some
suggestions on metrics that could be mapped to these goals.
From:
phoenix-dev-bounces@xxxxxxxxxxx [mailto:phoenix-dev-bounces@xxxxxxxxxxx] On Behalf Of Nick Boldt
Sent: Thursday, April 17, 2008
2:58 PM
To: For developers on the new
Eclipse.org website project.
Subject: Re: [phoenix-dev] Re:
First steps towards a better eclipse.org website
Certainly good goals, but there's still a little too
much unquantifiable text in there.
* Define "easy" -- for a first time vistor? for a project lead? for a
releng nerd? for a scriptkiddy? for a frequent visitor?
* Define "valuable" -- who decides what constitutes valuable
marketing, how is it measured, and who benefits?
* Define "support" -- does the website itself provide support, or is
it the staff (@eclipse.org) and the tools
(portal.eclipse) that provide support?
With each goal stated, the obvious question in terms of implementation,
quanitifcation, testing, and analysis must be "HOW?" -- how is the
website &/or the Foundation accomplishing this, how do we know it's being
accomplished, and how much better/different is it from before?
Nick
On Thu, Apr 17, 2008 at 2:35 PM, Bjorn Freeman-Benson
<bjorn.freeman-benson@xxxxxxxxxxx>
wrote:
·
Make it easy for members and other
ecosystem entities to _adopt_ Eclipse project technology for their product and
service offerings. (Note: different from individuals downloading)
·
Make it
easy for our individuals to find and download the different Eclipse project
technology.
·
Be an
information source on how to use and adopt Eclipse project technology.
·
Promote
the wider Eclipse ecosystem and be a valuable marketing resource for our Eclipse
member organizations.
·
Provide
the infrastructure to support the Eclipse projects.
