incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hirsch, Richard" <richard.hir...@siemens.com>
Subject RE: Excellent REST API Suggestion from Ethan Jewett
Date Mon, 16 Feb 2009 07:01:58 GMT
Fine except that those without signed iCLAs can just comment and not edit the content. This
is a known issue which we have discussed on this list before.
 
Until I get my iCLA signed, I have no probs with contributing via comments. 
 
@ethan: Have you considered submitting an iCLA?
 
D. 
 
________________________________

From: Anne Kathrine Petteroe [mailto:yojibee@gmail.com]
Sent: Sun 2/15/2009 23:38
To: esme-dev@incubator.apache.org
Subject: Re: Excellent REST API Suggestion from Ethan Jewett



Thank you for an excellent blog post Ethan!

What about using the Apache ESME wiki?
http://cwiki.apache.org/confluence/display/ESME/Index

/Anne

On 15. feb.. 2009, at 18.17, Hirsch, Richard wrote:

> We need a place to be able to collaborate on it. I'd like to do it 
> somewhere where an iCLA from Apache isn't required in order to bring 
> in others from the external communit (especially those that gave us 
> the scathing review before).
>
> Once we are further we could move it to Apache.   Is this sort of 
> collaboration against the Apache collaboration style?
>
> Any suggestions? Ideas?
>
> D.
>
>
>
> ________________________________
>
> From: Ethan Jewett [mailto:esjewett@gmail.com]
> Sent: Sun 2/15/2009 15:23
> To: esme-dev@incubator.apache.org
> Subject: Re: Excellent REST API Suggestion from Ethan Jewetta
>
>
>
> Thanks for the kind words Dick.  I'd definitely be interested in 
> discussing
> the suggestion and working on extending it into something more 
> useful to the
> project.
>
> Thanks,
> Ethan
>
> On Sun, Feb 15, 2009 at 4:20 AM, Hirsch, Richard <richard.hirsch@siemens.com
>> wrote:
>
>> Ethan has written a blog with a suggestion for a REST API for ESME (
>> http://www.esjewett.com/blog/a-restful-esme-api). Ethan's ideas are 
>> quite
>> good and I think would improve our API. The more REST-ful API would 
>> also
>> make our API more similar to that of other microblogging platforms.
>>
>> Take a look - I think it is an excellent start
>>
>> D.
>>
>>
>>
>
>




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