Kevan, > Note that there are some serious gaps in the above -- I haven't seen > discussion of the two codebases on our dev list, discussion about why > one codebase over another, a transcript of the IRC discussion, or a > summary of the IRC discussion, etc. Hoping that we can fill in some of > these gaps?
Fair points. I take responsibility for not getting the summary and transcript out in time. The latter is available and I'm working on the summary right now. While I'm doing that, does someone else care to net out the discussion of why the HP code over the IBM code? -Nick Nicholas Gallardo WebSphere - REST & WebServices Development [email protected] Phone: 512-286-6258 Building: 903 / 5G-016 Kevan Miller <kevan.mil...@gma il.com> To [email protected] 06/23/2009 09:38 cc PM Subject Re: [VOTE] Selecting Wink baseline Please respond to wink-...@incubato r.apache.org On Jun 23, 2009, at 10:40 AM, Snitkovsky, Martin wrote: > Hi all, > > > I would like to launch the vote for selecting the HP code as a Wink > baseline. > > +1 to recommend HP codebase as a Wink baseline. I doubt that I would have any objection. And would be *extremely* hard- pressed to go against any community consensus on the subject. However... as a project mentor, the most important behavior that I'm looking for from a new community is clear and open communication on our dev list. And I'm not seeing it... I was traveling this morning and could not attend the IRC chat (which is probably just as well). From my perspective, here's what I've seen: 1) A call for a community conference call, which was properly morphed (IMO) into a community IRC chat 2) Postiing of some documentation of the separate codebases on the community wiki (I must confess that I haven't read this documentation) 3) I assume that the IRC chat took place 4) A call for a vote to select the HP code as the baseline for the Wink implementation. Note that there are some serious gaps in the above -- I haven't seen discussion of the two codebases on our dev list, discussion about why one codebase over another, a transcript of the IRC discussion, or a summary of the IRC discussion, etc. Hoping that we can fill in some of these gaps? --kevan
