edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Marshall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-415) Improve our message
Date Wed, 24 May 2017 17:53:04 GMT

    [ https://issues.apache.org/jira/browse/EDGENT-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023330#comment-16023330

Will Marshall commented on EDGENT-415:

If you look at the Spark homepage (spark.apache.org), it includes only the following critical
* A two sentence description of Spark
* A two line code example
* A list of other frameworks/projects it integrates with

By contrast, our page (edgent.apache.org) has:
*  the "Edgent is a programming model and micro-service style runtime" line
* An events section
* Two webcasts where, while informative, still refer to the project as "Quarks"
* Then, at the bottom, the "why edgent" section.

I think we could hone our message by more closely modeling our landing page on the Spark landing

Additionally, I think part of the disconnect comes from not understanding datastreaming as
a concept in the first place. We have this "streaming concepts" page, but it's easily overlooked:
http://edgent.apache.org/docs/streaming-concepts.html. Maybe the landing page could have a
sentence or two about datastreaming as well.

> Improve our message
> -------------------
>                 Key: EDGENT-415
>                 URL: https://issues.apache.org/jira/browse/EDGENT-415
>             Project: Edgent
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dale LaBossiere
>            Priority: Critical
> There's been more than one example of someone who after hearing and/or reading some about
Edgent says "I still don't know what Edgent is".
> We need to improve the messages on our Website landing page, doc website, and probably
Apache project page to more clearly get our message across.
> After further explanation of a sample, you can get:
>     "oh it's an SDK"
>     "oh... you're not running the topology, you're building it, then running it"
>     ... but still...
>     It's tied to Android?
>     It's tied to Watson IoT Platform?
>     It has an API for accessing sensors?
> Yeah, the the doc has content that addresses most of that.  It's apparently not as effective
as it needs to be.
> IMO, a phrase that we use in a few locations "Edgent is a programming model and micro-service
style runtime ..." seems to be the first place to start.  Perhaps something like this would
be better: _Edgent is an SDK for creating event driven stream processing style analytic applications
to embed in small footprint edge devices and IoT gateways.  Smarter Edgent-based devices and
gateways can do realtime analytics on continuous streams of data, ...._"  you get the idea.
> The website landing page also has wording that says Edgent (doesn't say an Edgent based
application) performs realtime analytics, makes devices more intelligent, Edgent can adjust
controls..., Edgent enables connected devices, etc.  Very misleading IMO.
> On the Documentation site landing page, it talks mostly (only?) in terms of reducing
data.  Nothing about how a smarter device (edge resident analytics) can make devices more
autonomous: reduce decision making / action latency and overall be more autonomous while disconnected
from the cloud.

This message was sent by Atlassian JIRA

View raw message