High level features and "feature leads"

[Manik Surtani]

One of the things we spoke about on the kick-off call a few weeks back was to break down this JSR into high level features, and for each feature to have a "lead".  Feature leads will be responsible for driving discussion and owning the API (if any) for that feature, and would collaborate with the expert group (using the usual process of voting on conflicts, etc) to build out the feature.  Feature leads will work with the overall spec lead (myself) to ensure it all works together as a coherent whole.

I've just updated the wiki with a summary of high level features:

https://github.com/datagrids/spec/wiki/Proposed-features

Please take a look, and nominate yourself as feature lead if you're interested in taking any section on.  Leading more than one feature is fine if you have the bandwidth.  To sum things up, the features we have so far:

1.  Async API

2.  Distributed code execution

3.  Group API

4.  Annotations

5.  Non-API features (spec only)

6.  Eventually consistent API

7.  Querying

8.  Configuration

Cheers

Manik

[Rich Midwinter]

I'll put myself forward for the Group API as a starter.

> --
> You received this message because you are subscribed to the Google Groups "JSR 347 discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jsr347+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>

[Ben.Cotton=MorganStanley.com]

Hi Manik,

 

Though I am not technically qualified to fully lead all parts of item  "5. Non-API features" , I would offer to help lead "5.1 transactions (JTA) integration".

 

Thx,

Ben

[Jim Bethancourt]

Although I'm not yet sure exactly how I'll be able to particpate (I have been unable to get an Exhibit B signed by my employer), I'd like to point out that for the Querying feature, there is a project called Espresso that a Houston JUG member had open sourced too long ago (less than a year ago) that provides a SQL interface to JSR 107 compliant caches and might provide a good starting point.  The URL for it on GitHub is https://github.com/aantenan/Espresso

I'll try to see if I can get the slides from him that he used for his talk.

Cheers,

Jim

[Manik Surtani]

@Jim - great!  In fact, ask if he is interested in participating in JSR 347.

[Jim Bethancourt]

Will do :-)

[Zacarias]

I´m really interested in Queries and Group. So I propose myself for 7.  Querying.

Rich count on me for Group API we work a lot on this in my company.

[Jim Bethancourt]

I've heard back from Alberto and he's interested in helping out with the search portion.  I'll do my best to shepherd him through the process of joining the JCP, signing the JSPA, etc.  I'm not sure what his employer will do with respect to the Exhibit B document, but I imagine he'll be glad to at least act in an advisory role.  Since his Espresso project was released as open source before he joined his current employer, he may be able to indicate that it was code that was written "a priori", but I'm not sure.

Jim

--

[Manik Surtani]

Thanks for stepping up, Rich, Zacarias and Ben.

Yes, I expect everyone in the EG to help steer each feature, just that I am nominating a single lead per feature to drive it.

@Ben - remember, everyone in the EG will contribute to each feature as well, so you still could take on all of #5 as long as you have an interest.  :)

More volunteers?

https://github.com/datagrids/spec/wiki/Feature-Leads

Cheers

Manik

--

[ben.c...@morganstanley.com]

@Ben - remember, everyone in the EG will contribute to each feature as well, so you still could take on all of #5 as long as you have an interest.  :)

OK -  and yes, interested!