OpenAjax Hub 2.0 Release Review

From MemberWiki

Jump to: navigation, search

The Release Review phone call for OpenAjax Hub 2.0 occured on July 7 at 9am US-PT, noon US-ET, 6pm Paris.

See Release Review Minutes below for a record of the minutes from that phone call.

Contents

Background

The Interoperability Working Group at OpenAjax Alliance is in the final approval phase for OpenAjax Hub 2.0 after many months of work. Here is what we have:

The Interoperability Working Group devoted significant effort towards:

Additionally, we have implementation experience from member companies who have integrated recent versions of the Hub 2.0 open source into commercial products.

"Release Review" is a required part of the OpenAjax Alliance Development Process [5] and happens just before finalization and approval of all OpenAjax Specifications. The process requires a 3-week freeze period on the specification, followed by a Release Review phone call open to all OpenAjax members. One of the reasons for the Release Review milestone is to allow member companies an opportunity to review the given specifications for potential intellectual property issues. The phone call allows members to hear each others feedback on the Specification. If no major problems are raised during the Release Review phone call, then OpenAjax Hub 2.0 will be submitted to the members and the Steering Committee shortly afterwards for approval.

Release Review Minutes

Date/time: July 7 at 9am US-PT, noon US-ET, 6pm Paris.

Attendees

  • Howard Weingram, TIBCO
  • Jon Ferraiolo, IBM
  • Javier Pedemonte, IBM

Minutes

Jon: I'm not surprised at the low attendance. We have been working on Hub 2.0 in a very visible manner for over two years. Our plans have been discussed and reviewed at face-to-face meetings. We haven't veered off of the path decided at these meetings. Just finished all of the work.

Jon: The main reason for Release Review phone calls as part of our process was to alert member companies about potential IP issues within new specifications. The worry is that a renegade Working Group might attempt to produce a spec that might invalidate member patents. However, with Hub 2.0, the technologies have been well-known by the members for a long time.

Jon: Any issues with the spec or open source?

Howard: Javier had one. I don't have any.

Javier: A couple of minor spec things. One is that a value needs to be String, instead of something else. The other is that we are missing documentation for the log feature. All minor.

Jon: Any problems with updating the API chapter to fix these things?

Howard: No

Jon: OK. Are we ready to proceed onto member voting after making these changes?

Howard: Yes. Send email telling about the changes. See if anyone complains within a day. If not, then start voting.

Jon: OK. I had set up the PHP script to time out on Monday July 13, but I'll add another day so it will time out on Tuesday July 14.

Howard: OK, works for me.

Jon: And then send to Steering Committee for voting.

Jon: For promotion of the Hub 2.0 release, I see 3 things that we need to do. First, we need to pull together a press release. The press release would be facts and quotes. Very straightforward. We are announcing completion of Hub 2.0. The tricky part is making sure we get the words right about why this announcement is important. Any chance TIBCO could provide a quote?

Howard: We would be happy to.

Jon: I've written a draft. I wanted IBM PR to do a first pass review to make sure there weren't any really bad things in the way it is written. Once they do their review, I'll send it around. I hope this will have sometime soon.

Jon: The other two things are the white papers. As we discussed, we need two white papers, one which is already mostly there on mashup assembly applications. But we also need a more generic white paper on Hub 2.0.

Howard: Right

Jon: I'll try to have drafts of the white papers ready by Monday. Then run through Interop WG.

Jon: I think it's OK if the press release is a small number of weeks after approval. I don't think the press is monitoring our daily activities. OK to wait for press release, quotes, and white papers to be ready.

Howard: Yes, that's fine.

Jon: I think it's appropriate to promote how Hub 2.0 can be integrated with OpenSocial Gadgets. It's a natural because Shindig is more of a sample implementation rather than commercial-ready. There is likely to be a lot of interest with Enterprise vendors in integrating Hub 2.0 with the Gadgets runtime.

Howard: Yes, I agree.

Jon: What's the plan for future releases of the Hub?

Howard: For next release, security features are likely to be important

Jon: Beyond single sign-on, what else do you have in mind?

Howard: I have a list, but I can't remember it now. I'll send it in.

Jon: One thing on the open source side is the clicking on older versions of IE. Just open source changes. Spec stays the same.

Howard: Alternative to FIM?

Jon: Yes. Lots of ways to do this, but the one we are looking at is the technique used by OpenSocial. Looks good to me, but I wanted to have an independent review by someone who knows security issues and VBScript but is independent of OpenSocial. Suresh meets those requirements and has promised to look at it. We have been very careful about security in our open source so far and I only wanted to include this feature if it has been verified.

Jon: Javier, anything else?

Javier: The FIM implementation could be re-implemented. We just put a layer on top of the original SMash code. Right now it is bigger than it needs to be.

Howard: But that's becoming legacy.

Javier: Rewriting could save half of the code.

(after 30 minutes, meeting closed)

Retrieved from "http://www.openajax.org/member/wiki/OpenAjax_Hub_2.0_Release_Review"
Personal tools