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 <[email protected]
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 <[email protected]>
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
<[email protected]>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:[email protected]]
Sent: Sun 2/15/2009 23:38
To: [email protected]
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:[email protected]]
Sent: Sun 2/15/2009 15:23
To: [email protected]
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 <
[email protected]
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
