You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by "Hirsch, Richard" <ri...@siemens.com> on 2009/02/15 11:20:40 UTC
Excellent REST API Suggestion from Ethan Jewett
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.
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
David,
Part of the reason that I was reading the AtomPub protocol today was for
help on this type of question. As I said in response to Dick's tweet, I
think the protocol might be able to help do some of our thinking for us.
In this case, AtomPub (
http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-17.html#rfc.section.5.5)
defines some 200-range response codes, but otherwise just specifies that
HTTP response codes should be used in conformance with the HTTP protocol.
So what does that mean? It looks to me like we get:
Syntax problem with a resource that exists and is accessible - 400 Bad
Request (usually only for PUT/POST requests, since you can't really have a
syntax problem with a GET or DELETE)
Authorization issue - 401 Unauthorized
Resource not accessible to any user via API - 403 Forbidden (for resources
that should only be accessible through the human interface - password reset,
for example)
Resource doesn't exist - 404 Not Found
I'm not sure if it ever really makes sense to return a 500-range error for a
request that doesn't actually cause an internal error.
I haven't really looked carefully at the way other REST APIs implement HTTP
response codes, so I'm not saying that this is the way to go, but it might
be a starting point for conversation.
Ethan
On Sun, Feb 15, 2009 at 6:33 PM, David Pollak <feeder.of.the.bears@gmail.com
> wrote:
> Ethan,
> This is very good stuff. I've been working through Sam Ruby's REST book,
> but you've boiled everything down for me... except... what kind of non-200
> error codes should happen when stuff is not specified correctly?
>
> Thanks,
>
> David
>
>
>
> On Sun, Feb 15, 2009 at 6:23 AM, Ethan Jewett <es...@gmail.com> wrote:
>
> > 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.
> > >
> > >
> > >
> >
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by David Pollak <fe...@gmail.com>.
Ethan,
This is very good stuff. I've been working through Sam Ruby's REST book,
but you've boiled everything down for me... except... what kind of non-200
error codes should happen when stuff is not specified correctly?
Thanks,
David
On Sun, Feb 15, 2009 at 6:23 AM, Ethan Jewett <es...@gmail.com> wrote:
> 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.
> >
> >
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
I sent an invite to the mailing list, but it looks like it's not going
through. You should be able to use this link to access the Google Doc:
I've shared a document with you called "RESTful ESME API - Design":
http://docs.google.com/Doc?id=ajc6q3nhgqqd_374dhxctqgs&invite=cjh665s
It's not an attachment -- it's stored online at Google Docs. To open this
document, just click the link above.
Sorry if this results in duplicate mails to the list.
Ethan
On Mon, Feb 16, 2009 at 7:34 AM, Hirsch, Richard <richard.hirsch@siemens.com
> wrote:
> Sounds good regarding Google Doc as an initial start.
>
> Details on iCLA are here: http://www.apache.org/licenses/
>
> I'm still working on submitting my iCLA.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Ethan Jewett [mailto:esjewett@gmail.com]
> Gesendet: Montag, 16. Februar 2009 14:30
> An: esme-dev@incubator.apache.org
> Betreff: Re: Excellent REST API Suggestion from Ethan Jewett
>
> Dick and Anne,
>
> On the iCLA front, I haven't really considered it because I am not familiar
> with the process. Sounds scary :-) I'll look into it, but I suspect I
> won't have a lot of time to get one in this week.
>
> As to Anne's suggestion, a Google Doc would work fine (I've already got a
> complete draft as a Google Doc, so I'd be happy to just paste that in). I
> would also be comfortable contributing to the wiki through comments.
>
> If it's okay with everyone, I'll make a copy of the relevant pieces of the
> original document as a separate Google doc and share that out to the list.
> Please let me know if this is how you'd like to proceed for the moment.
>
> Ethan
>
> On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
> <yo...@gmail.com>wrote:
>
> > So why don't we start a Google doc (the Assembla space is gone no?) for
> now
> > and then I can cross post it to the wiki until everyone has submitted
> iCLAs?
> >
> > /Anne
> >
> >
> >
> > On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
> >
> > 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.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >
>
AW: Excellent REST API Suggestion from Ethan Jewett
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Sounds good regarding Google Doc as an initial start.
Details on iCLA are here: http://www.apache.org/licenses/
I'm still working on submitting my iCLA.
D.
-----Ursprüngliche Nachricht-----
Von: Ethan Jewett [mailto:esjewett@gmail.com]
Gesendet: Montag, 16. Februar 2009 14:30
An: esme-dev@incubator.apache.org
Betreff: Re: Excellent REST API Suggestion from Ethan Jewett
Dick and Anne,
On the iCLA front, I haven't really considered it because I am not familiar
with the process. Sounds scary :-) I'll look into it, but I suspect I
won't have a lot of time to get one in this week.
As to Anne's suggestion, a Google Doc would work fine (I've already got a
complete draft as a Google Doc, so I'd be happy to just paste that in). I
would also be comfortable contributing to the wiki through comments.
If it's okay with everyone, I'll make a copy of the relevant pieces of the
original document as a separate Google doc and share that out to the list.
Please let me know if this is how you'd like to proceed for the moment.
Ethan
On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
<yo...@gmail.com>wrote:
> So why don't we start a Google doc (the Assembla space is gone no?) for now
> and then I can cross post it to the wiki until everyone has submitted iCLAs?
>
> /Anne
>
>
>
> On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
>
> 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.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
I've posted the design from the blog post on the wiki at
http://cwiki.apache.org/confluence/display/ESME/RESTAPI
Feel free to go to town on it :-)
I'll be checking in a bit over the weekend, hopefully. I think there were
some additional methods suggested that could be added to the wiki.
Ethan
On Mon, Feb 16, 2009 at 4:33 PM, Anne Kathrine Petteroe
<yo...@gmail.com>wrote:
> I will take care of creating the wiki tomorrow.
> I wanted to do it tonight, but then my Facebook group against the new Terms
> of Service got slightly out of hand so I had to spend my evening taking care
> of that instead.
>
>
>
> On 16. feb.. 2009, at 16.28, Ethan Jewett wrote:
>
> Sounds good then. So can someone who has access to the wiki take the
>> contents of the blog post (not the Google doc) and put it up there for
>> people to start working with? I'll be able to participate in comments and
>> on the mailing list. Once I get around to the iCLA I'll be able to
>> participate directly.
>>
>> Thanks,
>> Ethan
>>
>> On Mon, Feb 16, 2009 at 7:17 AM, David Pollak <
>> feeder.of.the.bears@gmail.com
>>
>>> wrote:
>>>
>>
>> Folks,
>>> The reason that we need an iCLA is that we have to trace IP ownership for
>>> every line of code that goes into ESME. Working around the system will
>>> not
>>> help a whole lot as I'm not going to create create code from material
>>> designs done outside of the Apache process because then I'm on the hook
>>> if
>>> someone decides to assert intellectual property rights (I'm a lawyer by
>>> training and my wife's an IP litigator and I take these things very
>>> seriously.)
>>>
>>> I would very much like Ethan's assistance in this process. He's
>>> definitely
>>> got a good handle on the whole REST thing, but without an iCLA, I'll take
>>> his blog post along with the contents of the RESTful Web Services book
>>> along
>>> with input from others in order to synthesize the correct REST api.
>>>
>>> Thanks,
>>>
>>> David
>>>
>>> On Mon, Feb 16, 2009 at 5:30 AM, Ethan Jewett <es...@gmail.com>
>>> wrote:
>>>
>>> Dick and Anne,
>>>>
>>>> On the iCLA front, I haven't really considered it because I am not
>>>>
>>> familiar
>>>
>>>> with the process. Sounds scary :-) I'll look into it, but I suspect I
>>>> won't have a lot of time to get one in this week.
>>>>
>>>> As to Anne's suggestion, a Google Doc would work fine (I've already got
>>>> a
>>>> complete draft as a Google Doc, so I'd be happy to just paste that in).
>>>>
>>> I
>>>
>>>> would also be comfortable contributing to the wiki through comments.
>>>>
>>>> If it's okay with everyone, I'll make a copy of the relevant pieces of
>>>>
>>> the
>>>
>>>> original document as a separate Google doc and share that out to the
>>>>
>>> list.
>>>
>>>> Please let me know if this is how you'd like to proceed for the moment.
>>>>
>>>> Ethan
>>>>
>>>> On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
>>>> <yo...@gmail.com>wrote:
>>>>
>>>> So why don't we start a Google doc (the Assembla space is gone no?) for
>>>>>
>>>> now
>>>>
>>>>> and then I can cross post it to the wiki until everyone has submitted
>>>>>
>>>> iCLAs?
>>>>
>>>>>
>>>>> /Anne
>>>>>
>>>>>
>>>>>
>>>>> On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
>>>>>
>>>>> 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.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Lift, the simply functional web framework http://liftweb.net
>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>> Follow me: http://twitter.com/dpp
>>> Git some: http://github.com/dpp
>>>
>>>
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
I will take care of creating the wiki tomorrow.
I wanted to do it tonight, but then my Facebook group against the new
Terms of Service got slightly out of hand so I had to spend my evening
taking care of that instead.
On 16. feb.. 2009, at 16.28, Ethan Jewett wrote:
> Sounds good then. So can someone who has access to the wiki take the
> contents of the blog post (not the Google doc) and put it up there for
> people to start working with? I'll be able to participate in
> comments and
> on the mailing list. Once I get around to the iCLA I'll be able to
> participate directly.
>
> Thanks,
> Ethan
>
> On Mon, Feb 16, 2009 at 7:17 AM, David Pollak <feeder.of.the.bears@gmail.com
>> wrote:
>
>> Folks,
>> The reason that we need an iCLA is that we have to trace IP
>> ownership for
>> every line of code that goes into ESME. Working around the system
>> will not
>> help a whole lot as I'm not going to create create code from material
>> designs done outside of the Apache process because then I'm on the
>> hook if
>> someone decides to assert intellectual property rights (I'm a
>> lawyer by
>> training and my wife's an IP litigator and I take these things very
>> seriously.)
>>
>> I would very much like Ethan's assistance in this process. He's
>> definitely
>> got a good handle on the whole REST thing, but without an iCLA,
>> I'll take
>> his blog post along with the contents of the RESTful Web Services
>> book
>> along
>> with input from others in order to synthesize the correct REST api.
>>
>> Thanks,
>>
>> David
>>
>> On Mon, Feb 16, 2009 at 5:30 AM, Ethan Jewett <es...@gmail.com>
>> wrote:
>>
>>> Dick and Anne,
>>>
>>> On the iCLA front, I haven't really considered it because I am not
>> familiar
>>> with the process. Sounds scary :-) I'll look into it, but I
>>> suspect I
>>> won't have a lot of time to get one in this week.
>>>
>>> As to Anne's suggestion, a Google Doc would work fine (I've
>>> already got a
>>> complete draft as a Google Doc, so I'd be happy to just paste that
>>> in).
>> I
>>> would also be comfortable contributing to the wiki through comments.
>>>
>>> If it's okay with everyone, I'll make a copy of the relevant
>>> pieces of
>> the
>>> original document as a separate Google doc and share that out to the
>> list.
>>> Please let me know if this is how you'd like to proceed for the
>>> moment.
>>>
>>> Ethan
>>>
>>> On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
>>> <yo...@gmail.com>wrote:
>>>
>>>> So why don't we start a Google doc (the Assembla space is gone
>>>> no?) for
>>> now
>>>> and then I can cross post it to the wiki until everyone has
>>>> submitted
>>> iCLAs?
>>>>
>>>> /Anne
>>>>
>>>>
>>>>
>>>> On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
>>>>
>>>> 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.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Git some: http://github.com/dpp
>>
Re: Web UI Help
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
Thaaaank you!!!
:-)
On 16. feb.. 2009, at 17.39, Hirsch, Richard wrote:
> I've created a first draft for the Help for the Web UI. This was long
> over-due and I wanted to start it.
>
> It is currently hosted on GoogleCode:
> http://code.google.com/p/esmeproject/wiki/Quick_Dirty_UI_Help. The
> documentation is based on the old UI but it should act as a foundation
> for the new UI when it is finished.
>
> My intention is to move it to the Apache ESME web site at a later
> date.
>
> D.
Web UI Help
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I've created a first draft for the Help for the Web UI. This was long
over-due and I wanted to start it.
It is currently hosted on GoogleCode:
http://code.google.com/p/esmeproject/wiki/Quick_Dirty_UI_Help. The
documentation is based on the old UI but it should act as a foundation
for the new UI when it is finished.
My intention is to move it to the Apache ESME web site at a later date.
D.
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
Sounds good then. So can someone who has access to the wiki take the
contents of the blog post (not the Google doc) and put it up there for
people to start working with? I'll be able to participate in comments and
on the mailing list. Once I get around to the iCLA I'll be able to
participate directly.
Thanks,
Ethan
On Mon, Feb 16, 2009 at 7:17 AM, David Pollak <feeder.of.the.bears@gmail.com
> wrote:
> Folks,
> The reason that we need an iCLA is that we have to trace IP ownership for
> every line of code that goes into ESME. Working around the system will not
> help a whole lot as I'm not going to create create code from material
> designs done outside of the Apache process because then I'm on the hook if
> someone decides to assert intellectual property rights (I'm a lawyer by
> training and my wife's an IP litigator and I take these things very
> seriously.)
>
> I would very much like Ethan's assistance in this process. He's definitely
> got a good handle on the whole REST thing, but without an iCLA, I'll take
> his blog post along with the contents of the RESTful Web Services book
> along
> with input from others in order to synthesize the correct REST api.
>
> Thanks,
>
> David
>
> On Mon, Feb 16, 2009 at 5:30 AM, Ethan Jewett <es...@gmail.com> wrote:
>
> > Dick and Anne,
> >
> > On the iCLA front, I haven't really considered it because I am not
> familiar
> > with the process. Sounds scary :-) I'll look into it, but I suspect I
> > won't have a lot of time to get one in this week.
> >
> > As to Anne's suggestion, a Google Doc would work fine (I've already got a
> > complete draft as a Google Doc, so I'd be happy to just paste that in).
> I
> > would also be comfortable contributing to the wiki through comments.
> >
> > If it's okay with everyone, I'll make a copy of the relevant pieces of
> the
> > original document as a separate Google doc and share that out to the
> list.
> > Please let me know if this is how you'd like to proceed for the moment.
> >
> > Ethan
> >
> > On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
> > <yo...@gmail.com>wrote:
> >
> > > So why don't we start a Google doc (the Assembla space is gone no?) for
> > now
> > > and then I can cross post it to the wiki until everyone has submitted
> > iCLAs?
> > >
> > > /Anne
> > >
> > >
> > >
> > > On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
> > >
> > > 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.
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >
> >
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>
Re: Next Sprint
Posted by David Pollak <fe...@gmail.com>.
I'm working on nothing ESME related until after 2/26.
On Mon, Feb 16, 2009 at 4:37 PM, Anne Kathrine Petteroe
<yo...@gmail.com>wrote:
> Any news on where we are with federation? Is David working on this?
>
>
> On 16. feb.. 2009, at 17.46, Hirsch, Richard wrote:
>
> The first sprint is over and I wanted to start thinking about the next
>> sprint. I saw that there was some email traffic a while back concerning
>> using Jira more in the sprints.
>>
>> I read that David isn't going to have a lot of time for this sprint.
>> What about Vassil and Darren?
>>
>> Besides the obvious choice of work on the UI (where we are way behind),
>> REST API and Twitter API, does anyone else have other suggestions.
>>
>> D.
>>
>
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Next Sprint
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
Any news on where we are with federation? Is David working on this?
On 16. feb.. 2009, at 17.46, Hirsch, Richard wrote:
> The first sprint is over and I wanted to start thinking about the next
> sprint. I saw that there was some email traffic a while back
> concerning
> using Jira more in the sprints.
>
> I read that David isn't going to have a lot of time for this sprint.
> What about Vassil and Darren?
>
> Besides the obvious choice of work on the UI (where we are way
> behind),
> REST API and Twitter API, does anyone else have other suggestions.
>
> D.
Re: AW: Next Sprint
Posted by Mrinal Wadhwa <mr...@gmail.com>.
Thank you Anne.
On Tue, Feb 17, 2009 at 1:45 PM, Anne Kathrine Petteroe
<yo...@gmail.com>wrote:
> I have created an account now ;-)
>
> I will break up the UI tasks later tonight and post them here on the group
> first as part of the UI sprint planning.
>
> /Anne
>
>
> On 17. feb.. 2009, at 09.02, Hirsch, Richard wrote:
>
> Does each person want to add their own items to Jira or should we collect
>> / discuss them via mailing list and then after a few days, I can collect
>> them and add them to Jira.
>>
>> Does everyone have an account in the Apache Jira? If you don't have a
>> user, then we can't assign tasks. You don't have to submit an iCLA to have
>> a Apache Jira account. I didn't see Mrinal or Anne. Could you both create
>> users on Jira.
>>
>> D.
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Hirsch, Richard
>> Gesendet: Dienstag, 17. Februar 2009 08:54
>> An: esme-dev@incubator.apache.org
>> Betreff: AW: Next Sprint
>>
>> I agree that Jira is probably best place to base the sprints. I think the
>> current tasks are too broad.
>>
>> For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is
>> "Support for Twitter API". Should we break this down into smaller Jira
>> tasks. If you look at the official wiki from twitter (
>> http://apiwiki.twitter.com/REST+API+Documentation), there are already
>> categories ("Status Methods", "User Methods", etc.). That might be easier.
>>
>> Ideas?
>>
>> P.S. I also like the way the twitter wiki is structured to document their
>> REST API. Maybe we can use it as a basis for our documentation.
>>
>> D.
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Vassil Dichev [mailto:vdichev@gmail.com]
>> Gesendet: Dienstag, 17. Februar 2009 07:08
>> An: esme-dev@incubator.apache.org
>> Betreff: Re: Next Sprint
>>
>> I read that David isn't going to have a lot of time for this sprint.
>>> What about Vassil and Darren?
>>>
>>
>> As usual, I have a moderate amount of time in the hours after son goes
>> to sleep :)
>>
>> Besides the obvious choice of work on the UI (where we are way behind),
>>> REST API and Twitter API, does anyone else have other suggestions.
>>>
>>
>> Twitter API is what I'm going to concentrate on, my todo list there is
>> fairly big and I don't want to bite off more than I can chew. Besides,
>> most other tasks influence all of ESME (groups, permissions), so it's
>> necessary for more than one person to agree on how we want it
>> implemented.
>>
>> To summarize my view on the topic of whether sprints are useful- like
>> Darren, I also think it's beneficial to set some short-term goals,
>> even if we're not 100% successful. One planning problem here is that
>> everyone is moving at a different pace every sprint. Prioritized lists
>> would be of real help here. JIRA could fit quite nicely in this case,
>> I think.
>>
>
>
Re: Next Sprint
Posted by Vassil Dichev <vd...@gmail.com>.
> For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is "Support for Twitter API". Should we break this down into smaller Jira tasks. If you look at the official wiki from twitter (http://apiwiki.twitter.com/REST+API+Documentation), there are already categories ("Status Methods", "User Methods", etc.). That might be easier.
>
> Ideas?
There are definitely more subtasks for a container task like this. I
have to move some of my tasks in my Freemind todo-list to JIRA. I'll
try to do this more regularly.
Re: Next Sprint
Posted by Mrinal Wadhwa <mr...@gmail.com>.
> Does everyone have an account in the Apache Jira?
I do have an account on Jira .. just checked ... my user name is mrinal
_
Mrinal
On Tue, Feb 17, 2009 at 1:32 PM, Hirsch, Richard <richard.hirsch@siemens.com
> wrote:
> Does each person want to add their own items to Jira or should we collect /
> discuss them via mailing list and then after a few days, I can collect them
> and add them to Jira.
>
> Does everyone have an account in the Apache Jira? If you don't have a user,
> then we can't assign tasks. You don't have to submit an iCLA to have a
> Apache Jira account. I didn't see Mrinal or Anne. Could you both create
> users on Jira.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Hirsch, Richard
> Gesendet: Dienstag, 17. Februar 2009 08:54
> An: esme-dev@incubator.apache.org
> Betreff: AW: Next Sprint
>
> I agree that Jira is probably best place to base the sprints. I think the
> current tasks are too broad.
>
> For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is
> "Support for Twitter API". Should we break this down into smaller Jira
> tasks. If you look at the official wiki from twitter (
> http://apiwiki.twitter.com/REST+API+Documentation), there are already
> categories ("Status Methods", "User Methods", etc.). That might be easier.
>
> Ideas?
>
> P.S. I also like the way the twitter wiki is structured to document their
> REST API. Maybe we can use it as a basis for our documentation.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Vassil Dichev [mailto:vdichev@gmail.com]
> Gesendet: Dienstag, 17. Februar 2009 07:08
> An: esme-dev@incubator.apache.org
> Betreff: Re: Next Sprint
>
> > I read that David isn't going to have a lot of time for this sprint.
> > What about Vassil and Darren?
>
> As usual, I have a moderate amount of time in the hours after son goes
> to sleep :)
>
> > Besides the obvious choice of work on the UI (where we are way behind),
> > REST API and Twitter API, does anyone else have other suggestions.
>
> Twitter API is what I'm going to concentrate on, my todo list there is
> fairly big and I don't want to bite off more than I can chew. Besides,
> most other tasks influence all of ESME (groups, permissions), so it's
> necessary for more than one person to agree on how we want it
> implemented.
>
> To summarize my view on the topic of whether sprints are useful- like
> Darren, I also think it's beneficial to set some short-term goals,
> even if we're not 100% successful. One planning problem here is that
> everyone is moving at a different pace every sprint. Prioritized lists
> would be of real help here. JIRA could fit quite nicely in this case,
> I think.
>
Re: AW: Next Sprint
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
I have created an account now ;-)
I will break up the UI tasks later tonight and post them here on the
group first as part of the UI sprint planning.
/Anne
On 17. feb.. 2009, at 09.02, Hirsch, Richard wrote:
> Does each person want to add their own items to Jira or should we
> collect / discuss them via mailing list and then after a few days, I
> can collect them and add them to Jira.
>
> Does everyone have an account in the Apache Jira? If you don't have
> a user, then we can't assign tasks. You don't have to submit an
> iCLA to have a Apache Jira account. I didn't see Mrinal or Anne.
> Could you both create users on Jira.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Hirsch, Richard
> Gesendet: Dienstag, 17. Februar 2009 08:54
> An: esme-dev@incubator.apache.org
> Betreff: AW: Next Sprint
>
> I agree that Jira is probably best place to base the sprints. I
> think the current tasks are too broad.
>
> For example, ESME-6 ( https://issues.apache.org/jira/browse/
> ESME-6 ) is "Support for Twitter API". Should we break this down
> into smaller Jira tasks. If you look at the official wiki from
> twitter (http://apiwiki.twitter.com/REST+API+Documentation), there
> are already categories ("Status Methods", "User Methods", etc.).
> That might be easier.
>
> Ideas?
>
> P.S. I also like the way the twitter wiki is structured to document
> their REST API. Maybe we can use it as a basis for our documentation.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Vassil Dichev [mailto:vdichev@gmail.com]
> Gesendet: Dienstag, 17. Februar 2009 07:08
> An: esme-dev@incubator.apache.org
> Betreff: Re: Next Sprint
>
>> I read that David isn't going to have a lot of time for this sprint.
>> What about Vassil and Darren?
>
> As usual, I have a moderate amount of time in the hours after son goes
> to sleep :)
>
>> Besides the obvious choice of work on the UI (where we are way
>> behind),
>> REST API and Twitter API, does anyone else have other suggestions.
>
> Twitter API is what I'm going to concentrate on, my todo list there is
> fairly big and I don't want to bite off more than I can chew. Besides,
> most other tasks influence all of ESME (groups, permissions), so it's
> necessary for more than one person to agree on how we want it
> implemented.
>
> To summarize my view on the topic of whether sprints are useful- like
> Darren, I also think it's beneficial to set some short-term goals,
> even if we're not 100% successful. One planning problem here is that
> everyone is moving at a different pace every sprint. Prioritized lists
> would be of real help here. JIRA could fit quite nicely in this case,
> I think.
AW: Next Sprint
Posted by "Hirsch, Richard" <ri...@siemens.com>.
Does each person want to add their own items to Jira or should we collect / discuss them via mailing list and then after a few days, I can collect them and add them to Jira.
Does everyone have an account in the Apache Jira? If you don't have a user, then we can't assign tasks. You don't have to submit an iCLA to have a Apache Jira account. I didn't see Mrinal or Anne. Could you both create users on Jira.
D.
-----Ursprüngliche Nachricht-----
Von: Hirsch, Richard
Gesendet: Dienstag, 17. Februar 2009 08:54
An: esme-dev@incubator.apache.org
Betreff: AW: Next Sprint
I agree that Jira is probably best place to base the sprints. I think the current tasks are too broad.
For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is "Support for Twitter API". Should we break this down into smaller Jira tasks. If you look at the official wiki from twitter (http://apiwiki.twitter.com/REST+API+Documentation), there are already categories ("Status Methods", "User Methods", etc.). That might be easier.
Ideas?
P.S. I also like the way the twitter wiki is structured to document their REST API. Maybe we can use it as a basis for our documentation.
D.
-----Ursprüngliche Nachricht-----
Von: Vassil Dichev [mailto:vdichev@gmail.com]
Gesendet: Dienstag, 17. Februar 2009 07:08
An: esme-dev@incubator.apache.org
Betreff: Re: Next Sprint
> I read that David isn't going to have a lot of time for this sprint.
> What about Vassil and Darren?
As usual, I have a moderate amount of time in the hours after son goes
to sleep :)
> Besides the obvious choice of work on the UI (where we are way behind),
> REST API and Twitter API, does anyone else have other suggestions.
Twitter API is what I'm going to concentrate on, my todo list there is
fairly big and I don't want to bite off more than I can chew. Besides,
most other tasks influence all of ESME (groups, permissions), so it's
necessary for more than one person to agree on how we want it
implemented.
To summarize my view on the topic of whether sprints are useful- like
Darren, I also think it's beneficial to set some short-term goals,
even if we're not 100% successful. One planning problem here is that
everyone is moving at a different pace every sprint. Prioritized lists
would be of real help here. JIRA could fit quite nicely in this case,
I think.
Re: AW: Next Sprint
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
I think breaking down the tasks is a great idea!
Smaller Jira tasks go much better together with our hybrid Jira-sprint
model way of working.
The same goes for the web UI, for instance "Partial Implemenation of
User Interface (UI) for the first sprint (Web Interface)" -> I will
break that into smaller tasks later.
/Anne
On 17. feb.. 2009, at 08.53, Hirsch, Richard wrote:
> I agree that Jira is probably best place to base the sprints. I
> think the current tasks are too broad.
>
> For example, ESME-6 ( https://issues.apache.org/jira/browse/
> ESME-6 ) is "Support for Twitter API". Should we break this down
> into smaller Jira tasks. If you look at the official wiki from
> twitter (http://apiwiki.twitter.com/REST+API+Documentation), there
> are already categories ("Status Methods", "User Methods", etc.).
> That might be easier.
>
> Ideas?
>
> P.S. I also like the way the twitter wiki is structured to document
> their REST API. Maybe we can use it as a basis for our documentation.
>
> D.
>
> -----Ursprüngliche Nachricht-----
> Von: Vassil Dichev [mailto:vdichev@gmail.com]
> Gesendet: Dienstag, 17. Februar 2009 07:08
> An: esme-dev@incubator.apache.org
> Betreff: Re: Next Sprint
>
>> I read that David isn't going to have a lot of time for this sprint.
>> What about Vassil and Darren?
>
> As usual, I have a moderate amount of time in the hours after son goes
> to sleep :)
>
>> Besides the obvious choice of work on the UI (where we are way
>> behind),
>> REST API and Twitter API, does anyone else have other suggestions.
>
> Twitter API is what I'm going to concentrate on, my todo list there is
> fairly big and I don't want to bite off more than I can chew. Besides,
> most other tasks influence all of ESME (groups, permissions), so it's
> necessary for more than one person to agree on how we want it
> implemented.
>
> To summarize my view on the topic of whether sprints are useful- like
> Darren, I also think it's beneficial to set some short-term goals,
> even if we're not 100% successful. One planning problem here is that
> everyone is moving at a different pace every sprint. Prioritized lists
> would be of real help here. JIRA could fit quite nicely in this case,
> I think.
AW: Next Sprint
Posted by "Hirsch, Richard" <ri...@siemens.com>.
I agree that Jira is probably best place to base the sprints. I think the current tasks are too broad.
For example, ESME-6 ( https://issues.apache.org/jira/browse/ESME-6 ) is "Support for Twitter API". Should we break this down into smaller Jira tasks. If you look at the official wiki from twitter (http://apiwiki.twitter.com/REST+API+Documentation), there are already categories ("Status Methods", "User Methods", etc.). That might be easier.
Ideas?
P.S. I also like the way the twitter wiki is structured to document their REST API. Maybe we can use it as a basis for our documentation.
D.
-----Ursprüngliche Nachricht-----
Von: Vassil Dichev [mailto:vdichev@gmail.com]
Gesendet: Dienstag, 17. Februar 2009 07:08
An: esme-dev@incubator.apache.org
Betreff: Re: Next Sprint
> I read that David isn't going to have a lot of time for this sprint.
> What about Vassil and Darren?
As usual, I have a moderate amount of time in the hours after son goes
to sleep :)
> Besides the obvious choice of work on the UI (where we are way behind),
> REST API and Twitter API, does anyone else have other suggestions.
Twitter API is what I'm going to concentrate on, my todo list there is
fairly big and I don't want to bite off more than I can chew. Besides,
most other tasks influence all of ESME (groups, permissions), so it's
necessary for more than one person to agree on how we want it
implemented.
To summarize my view on the topic of whether sprints are useful- like
Darren, I also think it's beneficial to set some short-term goals,
even if we're not 100% successful. One planning problem here is that
everyone is moving at a different pace every sprint. Prioritized lists
would be of real help here. JIRA could fit quite nicely in this case,
I think.
Re: Next Sprint
Posted by Vassil Dichev <vd...@gmail.com>.
> I read that David isn't going to have a lot of time for this sprint.
> What about Vassil and Darren?
As usual, I have a moderate amount of time in the hours after son goes
to sleep :)
> Besides the obvious choice of work on the UI (where we are way behind),
> REST API and Twitter API, does anyone else have other suggestions.
Twitter API is what I'm going to concentrate on, my todo list there is
fairly big and I don't want to bite off more than I can chew. Besides,
most other tasks influence all of ESME (groups, permissions), so it's
necessary for more than one person to agree on how we want it
implemented.
To summarize my view on the topic of whether sprints are useful- like
Darren, I also think it's beneficial to set some short-term goals,
even if we're not 100% successful. One planning problem here is that
everyone is moving at a different pace every sprint. Prioritized lists
would be of real help here. JIRA could fit quite nicely in this case,
I think.
Next Sprint
Posted by "Hirsch, Richard" <ri...@siemens.com>.
The first sprint is over and I wanted to start thinking about the next
sprint. I saw that there was some email traffic a while back concerning
using Jira more in the sprints.
I read that David isn't going to have a lot of time for this sprint.
What about Vassil and Darren?
Besides the obvious choice of work on the UI (where we are way behind),
REST API and Twitter API, does anyone else have other suggestions.
D.
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by David Pollak <fe...@gmail.com>.
Folks,
The reason that we need an iCLA is that we have to trace IP ownership for
every line of code that goes into ESME. Working around the system will not
help a whole lot as I'm not going to create create code from material
designs done outside of the Apache process because then I'm on the hook if
someone decides to assert intellectual property rights (I'm a lawyer by
training and my wife's an IP litigator and I take these things very
seriously.)
I would very much like Ethan's assistance in this process. He's definitely
got a good handle on the whole REST thing, but without an iCLA, I'll take
his blog post along with the contents of the RESTful Web Services book along
with input from others in order to synthesize the correct REST api.
Thanks,
David
On Mon, Feb 16, 2009 at 5:30 AM, Ethan Jewett <es...@gmail.com> wrote:
> Dick and Anne,
>
> On the iCLA front, I haven't really considered it because I am not familiar
> with the process. Sounds scary :-) I'll look into it, but I suspect I
> won't have a lot of time to get one in this week.
>
> As to Anne's suggestion, a Google Doc would work fine (I've already got a
> complete draft as a Google Doc, so I'd be happy to just paste that in). I
> would also be comfortable contributing to the wiki through comments.
>
> If it's okay with everyone, I'll make a copy of the relevant pieces of the
> original document as a separate Google doc and share that out to the list.
> Please let me know if this is how you'd like to proceed for the moment.
>
> Ethan
>
> On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
> <yo...@gmail.com>wrote:
>
> > So why don't we start a Google doc (the Assembla space is gone no?) for
> now
> > and then I can cross post it to the wiki until everyone has submitted
> iCLAs?
> >
> > /Anne
> >
> >
> >
> > On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
> >
> > 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.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >>
> >
>
--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
Dick and Anne,
On the iCLA front, I haven't really considered it because I am not familiar
with the process. Sounds scary :-) I'll look into it, but I suspect I
won't have a lot of time to get one in this week.
As to Anne's suggestion, a Google Doc would work fine (I've already got a
complete draft as a Google Doc, so I'd be happy to just paste that in). I
would also be comfortable contributing to the wiki through comments.
If it's okay with everyone, I'll make a copy of the relevant pieces of the
original document as a separate Google doc and share that out to the list.
Please let me know if this is how you'd like to proceed for the moment.
Ethan
On Mon, Feb 16, 2009 at 1:17 AM, Anne Kathrine Petteroe
<yo...@gmail.com>wrote:
> So why don't we start a Google doc (the Assembla space is gone no?) for now
> and then I can cross post it to the wiki until everyone has submitted iCLAs?
>
> /Anne
>
>
>
> On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
>
> 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.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
So why don't we start a Google doc (the Assembla space is gone no?)
for now and then I can cross post it to the wiki until everyone has
submitted iCLAs?
/Anne
On 16. feb.. 2009, at 08.01, Hirsch, Richard wrote:
> 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.
>>>
>>>
>>>
>>
>>
>
>
>
RE: Excellent REST API Suggestion from Ethan Jewett
Posted by "Hirsch, Richard" <ri...@siemens.com>.
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.
>>
>>
>>
>
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Anne Kathrine Petteroe <yo...@gmail.com>.
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.
>>
>>
>>
>
>
RE: Excellent REST API Suggestion from Ethan Jewett
Posted by "Hirsch, Richard" <ri...@siemens.com>.
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.
>
>
>
Re: Excellent REST API Suggestion from Ethan Jewett
Posted by Ethan Jewett <es...@gmail.com>.
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.
>
>
>