Marketing Minutes 2006-10-17

From MemberWiki

Jump to: navigation, search

Contents

OpenAjax Alliance Marketing Committee meeting minutes 2006-10-17

Attendees

Present

  • Andre Charland <andre.charland@nitobi.com>
  • Chor-Ching Fan <chor-ching.fan@jackbe.com>
  • John Janetos <jjanetos@laszlosystems.com>
  • Jon Ferraiolo <jferrai@us.ibm.com>
  • Joseph Becker <bjoseph@us.ibm.com>
  • Shel Finkelstein <shel.finkelstein@sap.com>
  • Ted Thibodeau <tthibodeau@openlinksw.com>


Absent

  • Alexei White <awhite@nitobi.com>
  • Bradley Sipes <Bradley.Sipes@ikivo.com>
  • Chris Erickson <chris.erickson@icesoft.com>
  • Chuck Allen <chucka@hr-xml.org>
  • Coach Wei <coach@nexaweb.com>
  • Dan Roberts <dan.roberts@sun.com>
  • David Boloker <boloker@us.ibm.com>
  • David Frankel <david.frankel@sap.com>
  • Dominic Porter <dominic.porter@edgeipk.com>
  • Dylan Schiemann <dylan@dojotoolkit.org>
  • Eric Thomas <ethomas@goetc.net>
  • Erwan Paccard <epaccard@ilog.fr>
  • Espen Antonsen <ea@24sevenoffice.com>
  • Ian Wenig <ian@zoho.com>
  • Javier Gallego <Javier.Gallego@softwareag.com>
  • Jim Driscoll <jim.driscoll@sun.com>
  • Jochen Krause <jkrause@innoopract.de>
  • John (JB) Brock <john.brock@sun.com>
  • John Lilly <lilly@mozilla.com>
  • John Sheridan <john.sheridan.dublin@gmail.com>
  • Jonathan Daly <jdaly@nexaweb.com>
  • Joonas Lehtinen <joonas.lehtinen@itmill.com>
  • Juho Risku <juho.risku@helmitechnologies.com>
  • Luis Derechin <luisd@jackbe.com>
  • Matt Durham <matt.durham@softwareag.com>
  • Paul Kim <pkim@mozilla.com>
  • Raju Vegesna <raju@zoho.com>
  • Sharat Chander <sharat.chander@sun.com>
  • Stephen Maryka <steve.maryka@icesoft.com>
  • Thomas Stoesser <Thomas.Stoesser@softwareag.com>
  • Tony Ng <tony.ng@sun.com>
  • Torsten Preissler <tpreissler@innoopract.com>

Agenda

  • Agenda
    • Home page items
      • Proposal: have new Web site ready to review at next meeting. Here are the updates that are needed:
      • Removing non-Members from home page listing
      • New process and realignment of committees (fixes to about.html, white paper, and futures.html)
        • Minor mods to white paper to reflect Members Agreement
        • Merging of Interoperability/Markup committees
        • Investigating new activities in the areas of IDE integration, server framework integration, security and communications hub
        • Not starting a mobile committee, at least not quite yet
      • Update Coming Events (get rid of past items, add info on April AJAXWorld and next f2f)
        • Assuming we get mailman on openajax.org, update lists to mail lists
    • Market Overview Whitepaper - progress report
    • OpenAjax "Mark" and member logo (i.e., current logo with the word "Member" at the bottom)
    • Quotes from OpenAjax Alliance for vendors who support OpenAjax Hub
      • Chris Erickson would like a quote from OpenAjax Alliance, such as: "“The Open Ajax Alliance is dedicated to the successful adoption of open and interoperable Ajax-based Web technologies and to accelerate customer success with Ajax by promoting a customer's ability to mix and match solutions from Ajax technology providers. To those ends, we are pleased to see ICEsoft Technologies, Inc. announcement today to support interoperability with the Open Ajax Hub”
    • David Temkin's suggestions around new/revised architecture classifications
      • Only discuss this if Laszlo attends this week's meeting
      • Email from David forwarded on 2006-09-12
      • Punch line: "...We believe that 'compiled Ajax' is an appropriate (and popular) solution for a broad range of applications, and should be listed as a top-level classification supported/described by OAA. We're happy to sign up to add the appropriate material to the white paper if there's consensus around this."

Topic: Home page items

  • Proposal: have new Web site ready to review at next meeting. Here are the updates that are needed:
  • Removing non-Members from home page listing
    • At f2f, we decided to clean up participant/member list in "2 weeks".
    • Adobe/Backbase/BEA/Google looking at proposed Development Process on Thursday
    • Change "Participant wiki" to "Wiki"
      • New process and realignment of committees (fixes to about.html, white paper, and futures.html)
    • Minor mods to white paper to reflect Members Agreement
    • Merging of Interoperability/Markup committees
    • Investigating new activities in the areas of IDE integration, server framework integration, security and communications hub
    • Not starting a mobile committee, at least not quite yet
  • Update Coming Events (get rid of past items, add info on April AJAXWorld and next f2f)
    • Assuming we get mailman on openajax.org, update lists to mail lists

(Jon reviews the above agenda. Proposes to update Web site per above in staging area over next two weeks and announce via email to Marketing committee for review/approval at next phone call, Oct. 31.)

Chor-Ching: Announce to everyone who will be removed from Web site to give them 2 weeks to complete Members Agreement.

Jon: I can do that.

Ted: Sounds like a good plan. Allow people to fax the agreement, also.

Jon: Yes. What we have decided is that an electronic version that shows physical signature is sufficient to join, pending Steering Committee approval, but that we still want signed original hardcopies to keep things clean and simple for the open source project, where state of the art for contributor agreements at Apache and Eclipse is signed original hardcopies.

RESOLUTION/ACTION: Jon to send email to participants whose names would be removed from our home page telling them that unless we receive signed agreement their companies will be removed from home page.

(Jon explains Development Process document.)

(URL: http://www.openajax.org/member/wiki/Development_Process)

Jon: How about my proposal to create staged web site for review/approval in two weeks?

All: Sounds good.

RESOLUTION/ACTION: Jon to updated staged web site before Oct 31 with changes as described above.

Jon: Assuming I get mailman installed at openajax.org, I suggest we move our public mailing list to an openajax.org address. How about public@openajax.org?

Andre: As good as anything else.

Jon: Any objections?

(No objections)

Topic: Market Overview Whitepaper - progress report

Jon: Chris promises an outline for next meeting. He talked with Ian Wenig and others about this at the f2f and everyone agreed to see if Chris can do the same magic he did with the Technical Overview white paper.

Topic: OpenAjax "Mark" and member logo (i.e., current logo with the word "Member" at the bottom)

Ted: Having something that indicates compliance makes sense. Shows that there is something to shoot for.

Jon: We have decided to go for conformance not compliance.

Ted: ok

Shel: Conformance or compliance is tricky. This was lots of work on Java side. If you create a brand you need something to verify it.

Jon: We have decided to adopt a looser approach than JCP. One of the reasons we are using the term conformance rather than compliance.

Chor-Ching: Need to define clearly what it means to be conformant.

Shel/Jon: Agreed.

Jon: My sense from previous discussion is that we will be adopted a method similar to W3C where each spec defines its conformance requirements but we let vendors claim conformance and let the industry regulate itself.

Ted: W3C does have validators.

Jon: Yes. That matches the consensus we have so far both in marketing and technical committees. For example, we have talked about a collision detection tool that verifies whether an Ajax toolkit's claims about its global objects are accurate.

Jon: I expect that our conformance approaches will evolve iteratively over a period in collaboration between marketing committee and technical committees. The technical committees will contriubute detailed conformance requirements within the specs and will develop validators.

Ted: Sounds accurate.

Chor-Ching: Agreed.

Jon: How about the Member logo question. Requested by TIBCO and Seagull.

Ted: Need to address soon. Could define a policy for this.

Andre/Ted: Need to have official logo files available.

Jon: I can make that happen, but may need to get original files from Dylan.

Jon: Proposal on policy. Any official Member can use our official Member logo, but Steering Committee must approve this first.

(multiple) OK

RESOLUTION/ACTION: Jon to propose to Steering Committee that it is OK for any official Member to use our Member logo.

RESOLUTION/ACTION: Jon to work with Dylan to prepare artwork files.


Topic: Quotes from OpenAjax Alliance for vendors who support OpenAjax Hub

  • Chris Erickson would like a quote from OpenAjax Alliance, such as: "“The Open Ajax Alliance is dedicated to the successful adoption of open and interoperable Ajax-based Web technologies and to accelerate customer success with Ajax by promoting a customer's ability to mix and match solutions from Ajax technology providers. To those ends, we are pleased to see ICEsoft Technologies, Inc. announcement today to support interoperability with the Open Ajax Hub”

Shel/JohnJ: What does it mean to support OpenAjax Hub and how do we know that they are supporting it?

Jon: We only know that they are claiming to support it. That's it. We would say that we are pleased that they are announcing that they support it.

Ted: Sounds like they are announcing conformance. Otherwise it is an empty statement.

Andre: Yes.

Chor-Ching: Natural for vendors to want to communicate. My take is that we need further work on Hub before we can say too much. Not enough meat yet. Ahead of ourselves. Great that members support it, but too early for formal statements.

Jon: My guess is that it will take about 6 months before we have an OpenAjax-approved definition of OpenAjax Hub conformance. A few months to develop the Hub and then a review/approval period before spec goes final per the Development Process.

RESOLUTION: Probably will want to provide such quotes in future, but it is too early. We need further definition of conformance requirements around Hub.

Ted: For now, just say you are in the Alliance.

Topic: David Temkin's suggestions around new/revised architecture classifications

  • Only discuss this if Laszlo attends this week's meeting
  • Email from David forwarded on 2006-09-12
  • Punch line: "...We believe that 'compiled Ajax' is an appropriate (and popular) solution for a broad range of applications, and should be listed as a top-level classification supported/described by OAA. We're happy to sign up to add the appropriate material to the white paper if there's consensus around this."

Jon: Was this discussed at f2f?

Andre: No

Jon: My feeling is that we should incorporate "compiled ajax" into taxonomy.

Jon: Proposal: (1) agree to incorporate "compiled ajax" into taxonomy somehow, (2) wait until next meeting, after Chris's outline for second white paper, before decide how to incorporate "compiled ajax" into our communications materials.

Shel: I agree to incorporate

Jon: Any objections to second part of my proposal?

(none)

RESOLUTION: Discuss how to incorporate "compiled ajax" at next meeting.

Jon: Probably we will decide to do a minor update to existing white paper on web site because it will probably be a minor update and it will take time to work on other materials.

Jon: Maybe Laszlo can show their suggested changes to wiki page for Technical Overview White Paper. We already have it captured on Web site, so ok to change it in place.

JohnJ: I will talk to people about how to propose changes.

Retrieved from "http://www.openajax.org/member/wiki/Marketing_Minutes_2006-10-17"
Personal tools