esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <>
Subject AW: January Apache Incubator Report
Date Fri, 02 Jan 2009 14:58:19 GMT

Call next week is fine. 7pm is ok.

Regarding features: we could list two - federation and access rights. I wouldn't go into great
detail in the apache report - it really isn't the best place for such discusions. 


-----Urspr√ľngliche Nachricht-----
Von: Anne Kathrine Petteroe []
Gesendet: Fr 1/2/2009 15:46
Betreff: Re: January Apache Incubator Report
For the next period I think we should capture new features requests  
too and not only existing issues.

I also suggest we have a call next week, would Tuesday work for  
What about 7 pm CET, 6 pm GMT, 1 pm EST, 10 am PST?

- Anne

On 2. jan.. 2009, at 13.08, Hirsch, Richard wrote:

> Our first report is due on January 12  (

> ) and I wanted to get a list started:
> Enterprise Social Messaging Experiment (ESME) is a secure and highly  
> scalable microsharing and micromessaging platform that allows people  
> to discover and meet one another and get controlled access to other  
> sources of information, all in a business process context.
> ESME entered the incubator in 2008-12-02. This report is ESME's  
> first since it joined the incubator and the following items have  
> been performed since its acceptance
>    * Jira has been established and initial issues have been created
>    * A creation of Apache Wiki for ESME has been ordered
>    * Initial website has been created with Apache Forrest
>    * ESME Core source code has been transfered to the Apache SVN  
> from the Google Code site. This drop is based on the latest version  
> of Scala and includes a more optimal separation of UI and server  
> code to ease customization.
>    * Three committers have already been accepted (dpp, vassil, dhague)
> The following items are planned for the next reporting period:
>    * Acceptance of fourth original committer (Mrinal?)
>    * Inclusion of existing svn branches (actions, etc.) from Google  
> Code into Apache SVN trunk
>    * Submission of Apache CLAs by two other team members.
>    * Next version of Apache Incubator web site was more details
>    * Collection of feature requests for the next version
>    * Transfer of existing issues in Google Code to Apache Jira
>    * Focus on evolving the design and building a larger community.
> Suggestions / comments?
> D.

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message