Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of feeder.of.the.bears@gmail.com
 designates 209.85.217.10 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=cWH1PO/Oj3bhTkj3joY6YreA5KGNxZvjjDO9ilhMlUsrutKeVgH6tnDnJeWRSQvgVp
         17PCUj2RJGrgGCu9N2YGoolP/dzXX5v/jdfZX7bTeKZ+sZhCjRYOzZFDleAR4PCYq1Bk
         A6R7qnBLAApe8PFLXHfFWRpm+tfeSoDQAZR6A=
Message-ID: <cdbebedf0812151448rf22cfbah12b1e522e53161b8@mail.gmail.com>
Date: Mon, 15 Dec 2008 14:48:06 -0800
From: "David Pollak" <feeder.of.the.bears@gmail.com>
To: esme-dev@incubator.apache.org
Subject: Re: [ESME-dev] The ESME to-do list
In-Reply-To: <2bca8c350812151250x2d33b4c3pf07c343022a73c0a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_66405_30170044.1229381286495"
References: <cdbebedf0812151022g6fb842cfu8557a44cb66a6815@mail.gmail.com>
	 <2bca8c350812151250x2d33b4c3pf07c343022a73c0a@mail.gmail.com>

------=_Part_66405_30170044.1229381286495
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Mon, Dec 15, 2008 at 12:50 PM, Daniel Koller <dakoller@googlemail.com>wr=
ote:

> Hi all,
>
> thx for putting these tasks: which not coding related tasks do you see
> coming up?


I think there will be an installation guide that needs to be written.

Also... and this is a tough one to quantify, but I think there needs to be
an ESME best-practices guide.  It's very hard to describe this thing, but
the ESME champions within an organization have to set the tone of ESME use
and get folks in their organization jazzed about using ESME.  This is a tal=
l
and difficult order because ESME is obvious to micromessaging users (think
about how challenging it is for Anne or Dennis to describe ESME's value...
it often comes down to "it's great and you have to trust me.")  So, the
whole process of onboarding enough people such that the ESME instance
reaches critical mass is important for success and the tone of the messages
is important for service longevity (think about how many corporate wikis
have failed because nobody gardens them and pulls the weeds.)

So, those are the non-programming tasks that I've got in mind, but there ma=
y
be others.


>
>
> Btw. I can participate at the internal API topic,
>
> Kind regards,
>
> Daniel
>
>
>
> 2008/12/15 David Pollak <feeder.of.the.bears@gmail.com>
>
> > Folks,
> >
> > ESME is very exciting.  Barely 6 months ago, it was a twinkle in the ey=
e
> of
> > a few energetic people and now it's a project that's known to tens of
> > thousands, it's being incubated by the Apache foundation, and it's in
> active
> > use at a number of global 100 companies.  Wow!
> >
> > I believe that the ESME we see today is a mere glimpse of what ESME wil=
l
> > become over the next 5 years.  I believe that mixing the current
> foundation
> > and energy of the ESME community with a bunch of team-work, vision, and
> hard
> > work, we can make ESME the definitive micro-communications platform, ba=
r
> > none.
> >
> > There are a fair number of projects that need to be coordinated in orde=
r
> to
> > keep ESME growing and evolving.  I'd like to list what I think the
> projects
> > are and see if we can get some owners for the projects:
> >
> >    - Web-based User interface.  Create and manage a powerful, flexible
> >    web-based UI that has access to all the ESME features and can be
> customized
> >    easily.
> >    - Flash/AIR-based User interface.  The same power of the web-based U=
I
> >    in a desktop application.
> >    - The ESME REST-based API.  Manage and enhance ESME's REST API to
> >    support clients, support Twitter-API compatible clients, and allow
> >    interoperation with many other applications.
> >    - Internal message routing.  This is one of the features that
> currently
> >    distinguishes ESME for just about every other messaging platform: th=
e
> >    ability to define rules for managing messages.  I believe that this
> >    mechanism needs to become a full-fledged language and development
> system
> >    that does for information flow what HyperCard did for building
> end-user
> >    applications.
> >    - Information pools and access control.  In order for ESME to grow a=
nd
> >    thrive in the enterprise, we need to define a powerful, understandab=
le
> and
> >    usable mechanism for defining access control for messages and auditi=
ng
> for
> >    these mechanisms (who knew what, when?)
> >    - Internal APIs and plugin mechanism.  ESME needs a way for external
> >    code to be plugged into it beyond what's available via REST.  This
> might
> >    include mechanisms for authentication/authorization, hooks into
> message
> >    routing and access control, etc.  I expect that the internal
> API/plugin
> >    mechanism will lead to commercial ESME plugins that will allow a
> commercial
> >    ecosystem to evolve around ESME.
> >    - Attachments and search.  While I'm not personally keen on the
> >    concepts of attachments or searching for past messages, it's becomin=
g
> clear
> >    that micromessaging systems are information repositories and must
> allow for
> >    retention and mining of information.
> >    - Federation.  ESME instances do not exist in issolation.  They must
> >    interoperate with Twitter, the Open Microblogging architecture as we=
ll
> as
> >    interoperating with each other.  I have been working on a federation
> >    mechanism (along with information search and attachment distribution
> and
> >    caching) that is highly secure, cryptographically verifiable, etc.
> >
> > Who would like to add items to the above list?
> >
> > Who wants to volunteer to own particular items (I'd like to own
> federation
> > and attachments/search and participate in access control, message
> routing,
> > and internal APIs)?
> >
> > Thanks,
> >
> > David
> >
> > PS -- I'm bcc'ing this message to a number of ESME-related mailing list=
s
> > and people.  If you're interested in participating (or simply intereste=
d
> in
> > watching ESME grow and evolve), please participate by subscribing to th=
e
> > esme-dev@incubator.apache.org mailing list.  For more information see
> > http://incubator.apache.org/projects/esme.html
> >
> >
> > --
> > Lift, the simply functional web framework http://liftweb.net
> > Collaborative Task Management http://much4.us
> > Follow me: http://twitter.com/dpp
> > Git some: http://github.com/dpp
> >
> > --~--~---------~--~----~------------~-------~--~----~
> > You received this message because you are subscribed to the Google Grou=
ps
> > "esme-dev" group.
> > To post to this group, send email to esme-dev@googlegroups.com
> > To unsubscribe from this group, send email to
> > esme-dev+unsubscribe@googlegroups.com<esme-dev%2Bunsubscribe@googlegrou=
ps.com>
> <esme-dev%2Bunsubscribe@googlegroups.com<esme-dev%252Bunsubscribe@googleg=
roups.com>
> >
> > For more options, visit this group at
> > http://groups.google.com/group/esme-dev?hl=3Den
> > -~----------~----~----~----~------~----~------~--~---
> >
> >
>
>
> --
> ---
> Daniel Koller
> Jahnstrasse 20
> 80469 M=FCnchen * dakoller@googlemail.com
>


--=20
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

------=_Part_66405_30170044.1229381286495--