Based on earlier input from everyone I suggest: 1) start a spec page on the wiki 2) file a Jira ticket for the overall feature (or change) with a link to the wiki page (you can add sub-tickets later on too if needed) 3) review, discuss and update wiki page (repeat) 4) when we're ready to begin actual code changes make an initial PDF snapshot of the wiki page, attach to the Jira ticket and change ticket status to In Progress 5) keep the wiki page updated as development progresses; consider attaching a 2nd PDF snapshot at the time the Jira ticket is resolved
The Jira ticket for off-heap has an initial PDF snapshot of the off-heap wiki page attached. -Kirk On Wednesday, July 1, 2015, William Markito <[email protected]> wrote: > I think we should have a live document on the wiki with the goals and > current ideas and start the discussion on the mailing list. > > Once some consensus is established we can write the spec and present it > using a hangout or some sort of live video solution (webex) given the > complexity such discussions can get for Q&A and etc... > > That would be a good open process for such spec IMHO. > > Talking about possible alternatives what about Akka + Netty ? > > Sent from my iPhone > > > On Jul 1, 2015, at 4:46 PM, Bruce Schuchardt <[email protected] > <javascript:;>> wrote: > > > > I've been working for a couple of weeks on a proposal to address this > issue. We can't use the old 2.2.9 JGroups code that is currently bundled > into Geode, so we need to either move to a newer version of JGroups or use > something else. > > > > My proposal discusses using JGroups, Zookeeper or building a custom > solution. > > > > Have we decided on a process to discuss and review project proposals > like this? There was an email thread about this a month ago but I don't > see any consensus/resolution. > > > > Since this is a gating issue for leaving incubation I'd like to get > things rolling soon. >
