Fantastic, thanks! On Tuesday, February 10, 2015, Henry Saputra <henry.sapu...@gmail.com> wrote:
> BIll, > > I helped built Telemetry RESTful APIs before so I could help. > > Count me in please. > > - Henry > > On Tue, Feb 10, 2015 at 4:55 PM, Bill Farner <wfar...@apache.org > <javascript:;>> wrote: > > Reviving this thread. I would love to see a non-Twitter employee > > collaborate on this for a more diverse panel. > > > > -=Bill > > > > On Tue, Feb 10, 2015 at 11:14 AM, Joe Stein <joe.st...@stealth.ly > <javascript:;>> wrote: > > > >> Chris, > >> > >> We are primarily hoping to integrate Apache Storm. > >> > >> It is important for us that the task preemption and quotas and all that > >> great stuff is available from Aurora with the other frameworks we work > >> with. > >> > >> ~ Joe Stein > >> > >> On Tue, Feb 10, 2015 at 12:06 AM, Chris Lambert < > >> clamb...@twitter.com.invalid> wrote: > >> > >> > Just curious, what kind of frameworks do you want to run on Aurora? > >> > > >> > Chris > >> > > >> > > >> > On Mon, Feb 9, 2015 at 7:26 PM, Joe Stein <joe.st...@stealth.ly > <javascript:;>> wrote: > >> > > >> > > Hey, this looks really interesting. We have been toying with "how > do we > >> > run > >> > > frameworks on aurora" and I think that is a good use case for this > >> also. > >> > > > >> > > Can the pieces be broken up across a few different folks? > >> > > > >> > > Can we preserve the thrift objects and have that also as an option > >> (along > >> > > with json at least) to go over a http 2.0 end point? > >> > > > >> > > ~ Joestein > >> > > > >> > > On Mon, Feb 9, 2015 at 5:31 PM, Brian Wickman <wick...@apache.org > <javascript:;>> > >> > wrote: > >> > > > >> > > > +1 > >> > > > > >> > > > On Mon, Feb 9, 2015 at 1:55 PM, Joshua Cohen < > >> jco...@twopensource.com <javascript:;>> > >> > > > wrote: > >> > > > > >> > > > > I'd love to help out with this as well. > >> > > > > > >> > > > > On Mon, Feb 9, 2015 at 1:25 PM, Bill Farner <wfar...@apache.org > <javascript:;>> > >> > > wrote: > >> > > > > > >> > > > > > Hi folks, > >> > > > > > > >> > > > > > Before embarking on work [1] to build a REST* API for the > >> > scheduler, > >> > > > it's > >> > > > > > important that we come up with a sound design. Following up > from > >> > > > today's > >> > > > > > IRC meeting, i would like to gather a small contingent (<=4 > >> people) > >> > > to > >> > > > > > collaborate on an RFC to drive a broader design discussion. > >> > > > > > > >> > > > > > Note that the RFC will be published to this mailing list, > where > >> it > >> > > will > >> > > > > be > >> > > > > > completely open for discussion to change (it's a Request For > >> > > Comments, > >> > > > > > after all). > >> > > > > > > >> > > > > > Volunteers must be willing to research the landscape for > patterns > >> > and > >> > > > > best > >> > > > > > practices in designing web application APIs; prior experience > in > >> > this > >> > > > > area > >> > > > > > is a plus. > >> > > > > > > >> > > > > > Several people volunteered in the IRC meeting, but to keep the > >> > > > canonical > >> > > > > > discussion in one place i ask those still interested to > volunteer > >> > > again > >> > > > > on > >> > > > > > this thread. > >> > > > > > > >> > > > > > I'll start by volunteering myself. > >> > > > > > > >> > > > > > > >> > > > > > -=Bill > >> > > > > > > >> > > > > > * Used as shorthand, whether it turns out to be REST, > JSON-RPC, > >> > > > HATEOAS, > >> > > > > > etc. > >> > > > > > > >> > > > > > [1] https://issues.apache.org/jira/browse/AURORA-987 > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > -- -=Bill
