Steering Committee Minutes 2007-11-09
From MemberWiki
URL: http://www.openajax.org/member/wiki/Steering_Committee_Minutes_2007-11-09
(These minutes have been approved.)
Contents |
OpenAjax Alliance Steering Committee meeting minutes 2007-09-21
Attendees
- Dojo/Alex Russell
- Eclipse/Mike Milinkvovich
- IBM/David Boloker
- MICROSOFT/Bertrand Le Roy
- Nexaweb/Coach Wei
- TIBCO/Kevin Hakman
- Jon Ferraiolo
Original Agenda
- Agenda
- Update on fixing problems with OpenAjax.org domain
- Reminder about election nominations (Nov 12-25)
- Quick discussion of W3C Plenary
- Next steps with Runtime TF
- Discuss other committees to decide if they need additional activation
- Marketing, Interop, IDE, Security, Mobile, Gadgets, PAM, Search
Minutes
Topic: Update on OpenAjax.org
(Jon reports on the temporary hijacking of OpenAjax.org on Wednesday afternoon. As of Thursday afternoon, the Web site appears to have come back. No general announcement about the Web site being back until finishing off the discussion with the DNS authorities. Jon isn't sure why the Web site came back, but it was coincidental to two events, one which was notification from DNS folks that they have frozen the domain during their investigation and activation by our ISP of openajax.com as a last-resort backup to openajax.org. Jon has had to fill out various formal bits of paperwork including sending picture of driver's license. Right now they are asking for tax ids and fictitious business registrations and Jon sent a long explanation of how our legal standing works.)
Topic: Zimbra replacement election
(Jon reports that the election nomination process opens on Monday, assuming the Web site is stable then.)
Jon: Why reminds me - should we contact Scott & Yahoo about membership?
David: I'll send Scott a note, but he might be on vacation.
Topic: W3C Plenary
(Jon gave a quick summary of his liaison visit to W3C Plenary meeting. Impression is that HTML5 might actually get something done that gets implemented. Starting from WhatWG spec and then hammering on that bit by bit. Browser vendors are likely to implement what's in the spec in parallel with work on the spec. Jon did liaison work with WAF group. The leaders of the W3C Widgets spec were positive about collaboration and coordination. Jon heard discussion about Access Control to the point where he was able to understand features that are not yet documented, which has allowed email discussion this week about security implications within our Security TF. Finally, talked with John Resig, Chris Wilson, and Maciej about Runtime TF, and they were supportive of what I outlined. Which leads to next topic.)
Topic: Next steps with Runtime TF
Jon: Coach provided a URL with the list of requests that have been submitted so far. I provided a URL to a proposed process by which the task force which collect requests, assign priorities, and submit to the browser vendors. Should we proceed with the task force, try to do this work somewhere else, or wait?
Coach: Is there anyone else making progress?
(Jon/Alex say they aren't aware of anyone else taking leadership)
Alex: Caveat. Need to find a way for non-members to join the process. Need to find a way to get enough agreement to have a single voice that is brought to the browser vendors. Worry that some members might resist this for business reasons.
Jon: I have proposed that we create a second wiki that can be used by non-members.
Bertrand: There are two steps. Make a list. Prioritize the list. Maybe can make the list via email. It is during the prioritization that we need to get everyone involved.
Alex: How do we make sure that there is public pressure to take our list seriously?
(discussion that was not captured - sorry)
Jon: But should we take a shot at trying to make this work?
(Bertrand/David/Coach give affirmative answers)
Coach: Let's send the list around a couple of times. Then reach out to other toolkit vendors.
Jon: Regarding recruitment, I assume that will largely fall on me, but I hope Alex will help and anyone else with contacts.
Alex: Yes, I will help.
Jon: I don't think recruitment is all that involved. We will want to put our largest effort into the top 7-10 toolkits. Some are already in OpenAjax. Then there is Sam (Prototype), Thomas (Scriptaculous). Have already talked with John Resig (jQuery). Need to reconnect with Bruce (GWT). Easy to talk to Joe (DWR). Plus a couple of others.
Jon: OK, Coach, next steps are for you to get the task force moving.
Coach: Yep.
Topic: Committees: which activities need to be moving faster?
Marketing
(Jon talks about plans to have monthly phone calls for last two months. Work items are white papers, revised web site, OpenAjax Conformance 1.0.)
Jon: Web site needs an update. It was set up initially with just the list of members on the home page because that's all we had to show at the start. But we now have lots of accomplishments and activities and should highlight them.
David: Web site needs news, search, site map, conferences, Ajax-related developments, who is on Steering Committee, press activities. Need to look like a real Web site.
David: Next year, maybe a white paper on Hub 1.1. It will be a big event at OpenAjax.
Jon: I agree.
Jon: OK with having one call in Nov and one in Dec? I'm not sure we could fit in other calls, anyway.
David: Yes. Probably more frequent calls in new year.
Interoperability
Jon: Making good progress on Registry now. Probably will occupy committee through end of 2007. Then Registry will take less time and more time on Hub 1.1 as that starts to be solid enough for feedback and discussion. Sound OK?
(no comments)
IDE
Jon: Kevin?
Kevin: Jon has put together a comprehensive draft of the metadata formats. Next week we will step through that draft. Draft attempts to take into account requirements with gadgets and W3C Widgets efforts.
Jon: IDE group meets every week. I don't think we can accelerate activities there.
Security
Jon: Only two things that are active are the Ajax security resources wiki page and Access Control spec. Access Control discussion should be over within a week. That leaves resources wiki page.
David: Would like to see more progress and faster.
Jon: What things?
David: Resources page and work with Hub 1.1 effort.
Jon: Yes, the security tf needs to be consulted as the Hub 1.1 effort proceeds.
Mobile
Jon: Only active thing right now is white paper. For mobile device APIs, waiting for someone to take leadership and drive proposals. Until that happens, just wait. Any reason to change these plans?
(no comments)
Gadgets
Jon: Stew Nickolas of IBM, the chair, has submitted a strawman proposal. Was going to announce the kick-off phone call, but is probably waiting for the web site to come back.
David: Yes, that's right.
PAM and Searchability
Jon: Right now no visible activity. I haven't been pushing these two task forces. Is that OK?
Coach: OK. I'm neutral about PAM but curious about that activity.
