Steering Committee Minutes 2007-01-11

From MemberWiki

Jump to: navigation, search

URL: http://www.openajax.org/member/wiki/Steering_Committee_Minutes_2007-01-11

(These minutes have been approved by Steering Committee vote.)

Contents

OpenAjax Alliance Steering Committee meeting minutes 2007-01-11

Attendees

  • Jon Ferraiolo
  • IBM/David Boloker
  • ZEND/Michael Pinette
  • NEXAWEB/Coach Wei
  • ECLIPSE/Mike Milinkovich
  • ZIMBRA/Scott Dietzen

Original Agenda

  • Agenda
    • Vote to accept new members (if not approved already via email)
      • MobileAware - Historically, server-side adapter software for Mobile HTML. Now wants to expand into Mobile Ajax. They are active members of W3C's Mobile Web Initiative (MWI).
      • iPolipo- Extranet calendaring using Ajax (Ruby on Rails, actually). For example, Outlook users from different companies can do joint calendaring. They are "Ajax users", but they also might pursue calendaring API standards via OpenAjax Alliance.
    • Development Process
      • As of Dec. 8 (the deadline), no feedback on proposed changes (color-coded)
      • Proposal:
        • Remove color-coding
        • Proceed with member voting (+1, -1) immediately. Send email to participants@openajax.org on Monday, Jan. 15.
        • Member voting period ends Friday night, Jan. 19.
        • If all responses are positive then SC can approve via email voting between Jan. 22-26.
        • Final version will be posted as HTML (not wiki) at http://www.openajax.org/process/Development_Process.html
        • Then begin Proposal Phase for Marketing Working Group and Interoperability Working Group
          • Draft charters will be ready for next week
    • Status report (on the agenda for every SC meeting)
      • OpenAjax Hub
      • OpenAjax Registry
        • List of Ajax libraries and their globals
        • Barely started, but should make lots of progress in January
      • OpenAjax Best Practices: libraries, applications, IDEs, servers, browsers
      • "OpenAjax Conformance" defined as the...
        • union ( OpenAjax Hub, OpenAjax Registry, OpenAjax Best Practices )
      • Interoperability event March 15-19
        • Proposal:
          1. InteropAthon Test Suite (version 1.0)
            For March, the InteropAthon Test Suite contains only one test which verifies that a given Ajax library integrates with the Hub properly by proper calls to OpenAjax.registerLibrary(), OpenAjax.registerGlobals(), OpenAjax.addOnLoad(), and that the library does not interfere with the Hub's optional features (publish/subscribe event hub and markup scanner). Visually, this test will print out the words OPENAJAX CONFORMANCE TEST <blah> PASSED for each conformance criteria that the library passes. As much as possible, the checks will match the list of conformance criteria in the Hub spec (e.g., see http://www.openajax.org/member/wiki/OpenAjax_Hub_Specification_Libraries#Conformance_Requirements). This test case would consist of some boilerplate HTML that loads two things: OpenAjax Hub and a mini Ajax library built just for the purposes of the Interopathon (this mini Ajax library would print out all of the OPENAJAX CONFORMANCE TEST <blah> PASSED strings. The boilerplate HTML would need to be modified for each of the libraries that participate in the InteropAthon.
          2. Vendor Showcases of OpenAjax Conformance
            Vendors are encouraged to showcase the ability to integrate other Ajax libraries via the OpenAjax Hub. For example, TIBCO and Nexaweb might want to showcase the ability to integrate several Ajax components.
      • sysadmin
        • Need to update home page
          • Terms of Use
          • Logos and Trademarks
          • Link to blog
      • New member activity
        • Waiting for Redmonk's members agreement
        • Google, Microsoft, Apple, Vodafone, Nokia, ...
        • With Hub done and Registry in works, definitely time to outreach to Prototype, Scriptaculous, RoR guys
      • Marketing committee
        • Needs to work on WG proposal and charter in early January
        • Planning the InteroperabilityFest
        • 2nd Generation White Papers
      • Interoperability committee
        • Only meeting every two weeks now
        • Open source implementation issues moved to SourceForge
        • Now focused on new issues
          • Needs to work on WG proposal and charter in early January
          • OpenAjax Official Registry of Toolkits/Libraries and Associated Global Variables
          • Best practices (applications, browsers, IDEs, runtime libraries, servers)
      • Task forces
        • IDE - jMaki likely to provide starting point
        • Server - Different Oracle person will chair. jMaki likely to provide starting point
        • Communications Hub - Moving quickly. Pursuing a communications hub feature to be added to OpenAjax Hub which will be a general framework to support both XHR and server push. Greg Wilkins will write up detailed proposals.
        • Security - No meetings yet. Homework and preparation happening in the background.


Minutes

Topic: Vote to accept new members

Jon: MobileAware has sent signed agreement. (Jon repeats info from agenda: Historically, server-side adapter software for Mobile HTML. Now wants to expand into Mobile Ajax. They are active members of W3C's Mobile Web Initiative (MWI).) Do people approve?

(all five attendees vote yes)

RESOLUTION: MobileAware is a Member.

Topic: Development Process

(Jon repeats proposal from agenda:)

  • Proposal:
    • Remove color-coding
    • Proceed with member voting (+1, -1) immediately. Send email to participants@openajax.org on Monday, Jan. 15.
    • Member voting period ends Friday night, Jan. 19.
    • If all responses are positive then SC can approve via email voting between Jan. 22-26.
    • Final version will be posted as HTML (not wiki) at http://www.openajax.org/process/Development_Process.html
    • Then begin Proposal Phase for Marketing Working Group and Interoperability Working Group
      • Draft charters will be ready for next week

Jon: No one has commented since I updated the Development Process document with changes from our phone call. I have now removed the color coding. Is this proposal OK?

(all attendees agree)

Jon: I have updated the draft charters for future Mktg WG and future Interop WG. OK if email includes links to the draft charters.

MikeM: Sounds OK.

Jon: Any objections?

(none)

RESOLUTION: Jon will send email to members on Jan 15 asking for voting on Development Process, with links to draft charters. If voting goes well, SC will vote electronically the week of Jan 22. If SC approves, Jon will post Development Process on public web site.

Topic: OpenAjax Hub, Registry, Best Practices, OpenAjax Conformance

(Jon reports that Hub spec, reference implementation and test suite is roughly feature complete, ready for integration with toolkits. Says that there has been discussion within mktg and interop committees about having the concrete definition of OpenAjax Conformance being union of support for Hub, Registry and Best Practices.

Coach: Gone through Hub spec and looked at source code. Spec is well-written. Source code is fairly good. Represents very good progress. Important progress within the industry.

Jon: Registry will say things like Dojo reserves window.dojo and window.djconfig, and will deal somehow with practical reality that Prototype is widely used and extends core JavaScript objects such as array. Registry is still in early stages of discussion. We have talked generally about how to approach things, but lots of details to work out. Should have some initial progress to show at F2F.

Jon: Best Practices are not even as far as Registry. Some skeleton wiki pages. Probably start getting momentum on these things after the F2F.

MikeM: I am confident about have conformance be union of Hub and Registry but not as sure about Best Practices. BP often are not as well thought-through and can be contradictory. Perhaps conformance should be union of members, Hub and Registry.

Jon: Membership requirement has legitimacy because it shows that the given organization agrees with our IP policy.

Jon: Regarding Best Practices, I was thinking that there would be a small number of MUSTs and more SHOULDs and that conformance only requires support for MUSTs.

MikeM: What is process for defining BPs? On wiki page, it only says that Interop committee defines it.

Jon: I was assuming that BPs would be published within specs, and thus would be covered by Development Process. Regardless, this should be an open issue.

MikeM: My main concern is that there is a careful process and all conformance requirements are defined and reviewed carefully.

Topic: Interoperability Event at F2F

(Jon reviews the proposal of a simple test case which prints 5 strings that show that a toolkit has successfully integrated the Hub)

Jon: This proposal was discussed within both the mktg and interop committees this week. Only feedback was positive. No one expressed objections. Alex said he was very positive about how it might be possible to pass with as little as 3 lines of JavaScript. But it will be more involved than just 3 lines. Toolkits will need some adaptation.

Coach: Approve is very good. Going forward we would add additional code to test additional features.

David: Sounds good.

Jon: The second part of my proposal was an optional part that might get no success or if we are lucky would get 1-3 vendors to support. This would be where a toolkit provider not only integrates with the Hub but also is able to showcase using the Hub to integrate and interoperate with a different toolkit. Good candidates are Nexaweb/XAP and TIBCO.

Coach: XAP already supports Dojo.

Jon: But not using the Hub. The requirement is that the framework leverages the Hub to integrate other toolkits.

Jon: Interop committee liked this. Of course, there was some angst from some companies. They agree that this is a good thing for OpenAjax, but realize that this puts pressure on their products.

MikeM: Gotta do this. A big item in press is that Ajax is fragmented. We need to show that interoperability is happening.

Topic: Current status with sysadmin, prospective new members, Mktg committee, Interop committee

Jon: I haven't updated the Web site yet for Terms of Use and Logos/Trademarks. Other things have had priority. Sometime in January.

Jon: Several big companies are in various stages of joining up. With progress on Registry, time to engage with Prototype, Scriptaculous and RoR.

Jon: We have already talked about main things within Marketing and Interop committees.

Topic: Current status with Task Forces

Jon: IDE task force seems likely to use jMaki as starting point.

Jon: Server task force might have overlap with IDE task force and also leverage jMaki as starting point.

Coach: Communications Hub task force is gravitating around proposals from Greg Wilkins. Interop charter already updated to include likely new features from communications hub. Probably TF will finish in a few months and work will transition to Interop WG.

David: Regarding Security TF, I have a a group within IBM looking at Ajax security issues where we will list our key issues. Then we will go around to the other companies within the task force to compare notes and get agreement on what issues need to be addressed. First thing is likely to be a white paper that identifies Ajax security issues and talks about fixes that are available. So, first everyone lists issues, and then work on those issues.

Jon: White paper draft for f2f?

David: Maybe, or maybe April or June.

Jon: I am thinking that there will be a Web site update around time of F2F, and that this is our likely pattern.

David: Press is focused on the Web site. Asking questions about membership.

MikeM: It's good to have them focused. Shows interest.

Topic: Next meeting

(people check calendars. not enough people are available in 2 weeks or 3 weeks)

Jon: OK. Next meeting will be Feb. 8.

Retrieved from "http://www.openajax.org/member/wiki/Steering_Committee_Minutes_2007-01-11"
Personal tools