Steering Committee Minutes 2008-02-22
From MemberWiki
URL: /member/wiki/Steering_Committee_Minutes_2008-02-22
(These minutes have not yet been approved.)
Contents |
OpenAjax Alliance Steering Committee meeting minutes 2008-02-22
Attendees
- Eclipse/Mike Milinkvovich
- IBM/David Boloker
- MICROSOFT/Bertrand Le Roy
- Nexaweb/Coach Wei
- Jon Ferraiolo
Original Agenda
- Agenda
- Kevin Hakman's move to TIBCO
- Steering Committee chair - need to choose someone
- (NEW) 1) An update to our Web site is staged and ready to deploy. The Marketing WG gave a thumbs up to the new site. Please take a look at the new Web site. If you see any problems, please report them ASAP. I would like to activate the new Web site in the next day. It's at:
- /index.php (Note: the old web site is still there, at , which maps to index.html)
- (NEW) We have been presented with an opportunity to sponsor the Great Indian Development Summit, a conference in Bangalore. Does anyone from the Steering Committee want to attend?
- Next face-to-face meeting: March 21 in NYC
- /member/wiki/2008_March_Members_Meeting
- Jon's thinking about the agenda
- Quick update on what's happened in last 6 months
- OpenAjax Conformance changes (per Yehuda feedback)
- Yehuda (of jQuery) wants a full conformance category
- Technical deep dive into our two big coordinated efforts around secure mashups: Hub 1.1 and OpenAjax Metadata
- Runtime TF town hall (allow non-members to attend)
- Review of current activities
- Marketing WG - web site update is only active topic
- Interop WG
- Final phases for OpenAjax Registry
- IBM contributors have produced Hub 1.1 strawman (initial spec and open source)
- Committee ill start WG discussion on Hub 1.1 at next phone call
- IDE WG - plowing through spec that unifies IDE work with Gadgets work
- Gadgets TF - Helping IDE WG, working on complementary open source for Hub 1.1
- Runtime TF
- Wiki is set up and populated with initial set of features
- Coach is trying to recruit community participation
- Mobile TF
- Finishing white paper on Mobile Ajax
- Launching new activity on Mobile Device APIs (this time we are serious)
- Security TF
- Dormant for now
- Might help with security framework for Mobile Device APIs
- Might pursue activities around federated authorization
- Production AJAX Management TF - not yet launched
- Searchability TF - not yet launched
Minutes
Topic: Kevin's move from TIBCO to Aptana
Jon: Two implications from process perspective. Kevin was on Steering Committee and was chair of IDE WG. Regarding SC, TIBCO will offer a substitute, probably Howard Weingram, but final approvals haven't been given yet. I'll be meeting with Howard on a different subject later today. I'll ask. Regarding IDE WG, the members of that committee didn't say anything when Kevin ran the meeting as an employee of Aptana. The question is whether it is OK to just change the chair from Kevin of TIBCO to Kevin of Aptana. Charter says its Kevin Hakman of TIBCO as chair. I think the Steering Committee can just decide that. No need to ask the OpenAjax membership for their opinion on that.
MikeM: Make sure that TIBCO is OK with allowing Aptana to chair.
Jon: I'll make sure it's OK with TIBCO.
DavidB: I talked with Kevin when he was still with TIBCO about these transitions and he said there was no problem.
MikeM: I would be surprised if they object.
David/Mike: OK if TIBCO agrees with this.
Bertrand: Fine with me.
Topic: Steering Committee chair
Jon: Members Agreement talks about the role of SC chair. Last year, it was David, but then we had an election and a special election. I put this on the agenda before the Kevin thing came up, so maybe it makes sense to postpone the decision.
David: Choices are vote now, vote via email, or postpone until next phone call. I am happy to take on the chair role until my term expires in October.
MikeM: Last time we just said David was chair.
Coach: I nominate David as chair.
MikeM: Second. There is logic behind this. Jon works for you. Whoever is chair would probably just delegate the meeting scheduling and agenda to him.
David: Yes, Jon technically works for me, but we keep at arm's length.
Resolution: Propose David as chair, vote through email.
Topic: New web site
Jon: It's up there now. Just go to www.openajax.org/index.php instead of www.openajax.org or www.openajax.org/index.html. To move to new site, just need to upload a file with some Apache redirects. The single biggest thing is that there is now a pulldown menu at the top with quick access to everything we are doing. Was discussed and reviewed within Mktg WG, who liked it. I used Dojo for the toolbar and then realized Dojo doesn't support Opera, so that forced me into building a mobile version of the web site and having everything but IE, Firefox and Safari go to that. This allowed me to send the mobile version to the iphone, where the regular desktop web site takes 25 seconds over EDGE, but now the iphone gets the mobile version which comes down in 2 seconds.
David: Mktg WG was very positive. Wonderful step forward. Looks really good overall. A couple of small things that need to be improved, but it's ready to go live. Also satisfies the attribution request from OpenDomain. Really good job. Is it accessible?
Jon: Short answer, yes. Because it uses Dojo, you can navigate through the UI using the keyboard. But I'll send a link to Becky Gibson for her review.
Jon: I would like to switch over to the new web site today so that I have the weekend for reports if there are problems. If there are big problems, switching back only requires changing the Apache redirects.
Resolution: Switch to new web site today.
Topic: Great Indian Developer Summit
(Discussion about the opportunity to partner with this event, which might result in discounts for the OpenAjax members and some promotion of OpenAjax. Coach attended the same conference last year and gave positive feedback as a worthwhile event, pointing out that most of the attendees were Indian employees of US companies and that it felt like a US conference. However, no one on the call will attend the conference.)
Resolution: Tell them thanks but not this time.
Topic: f2f agenda
Jon: I am proposing the day is spent on deep dives on 3 things. (1) Runtime TF town hall, including non-members, (2) Hub 1.1 and OpenAjax Metadata, and (3) OpenAjax Conformance, to work on final details and address topics that have come up in last month from Yehuda Katz and within OpenAjax Registry discussion.
Coach/David: Looks good.
Jon: I am thinking runtime at the beginning.
Mike/David: Yes
Mike: But be careful about the discussion where non-members are there. They haven't agreed to our IP policy.
Jon: Yes. At least preface the discussion by saying the discussion isn't covered by IP policy, so please don't make technical contributions. Should be OK because the runtime effort is to talk about gaps in the browser, not technical algorithms for addressing the gaps.
MikeM: Yes, usually OK with friends, but be careful.
Topic: What's going on these days in the various committees
(Jon repeats the executive summary found in the agenda about the various committees. The meaty discussion was about the Runtime TF)
Coach: With the runtime tf, we have set up a separate wiki that non-members can use. We have listed 15-16 issues, some taken from Bertrand, some from Alex, some from others. Not publicized yet. We are now reaching out to industry leaders and have had discussion with Douglas Crockford, Jack Slocum, and Joe Walker. Got good feedback from Doug, who is focused on security issues. Next week we will have conference calls with Jack and Joe. I reached out to the Prototype, Scriptaculous guys and John Resig, but no response yet. After these interviews, we'll update the wiki, and then reach out to the public.
Jon: With each AJAXWorld, we have a press release, and there will be one this time, also. Should our press release mention the Runtime TF? I think yes, but not as the lead.
Coach: My thinking is that it would be ok to mention if there aren't already too many things in the release.
Jon: Yes, I agree. The best mechanism for publicizing the Runtime TF would be Ajaxian.
Coach: Yes.
Topic: Next phone call
Resolution: Friday, March 14, 10amPT, 1pmET. One topic will be final review of agenda for F2F meeting
