Marketing Minutes 2006-06-20

From MemberWiki

Jump to: navigation, search

Contents

OpenAjax Alliance Marketing Committee meeting minutes 2006-06-20

Attendees

  • Andre Charland <acharland@ebusiness-apps.com>
  • Dan Roberts <dan.roberts@sun.com>
  • David Frankel <david.frankel@sap.com>
  • Gary Horen <ghoren@bea.com>
  • John Janetos <jjanetos@laszlosystems.com>
  • John Lilly <lilly@mozilla.com>
  • Jon Ferraiolo <jferrai@us.ibm.com>
  • Joseph Becker <bjoseph@us.ibm.com>
  • Rob Vonderhaar <robv@jackbe.com>
  • Sharat Chander <sharat.chander@sun.com>

Absent

  • Alexei White <awhite@ebusiness-apps.com>
  • Cary Liu <cliu@mercedsystems.com>
  • Chris Erickson <chris.erickson@icesoft.com>
  • Coach Wei <coach@nexaweb.com>
  • David Boloker <boloker@us.ibm.com>
  • Dion Almaer <dion@ajaxian.com>
  • Dylan Schiemann <dylan@dojotoolkit.org>
  • Ian Wenig <ian@adventnet.com>
  • Javier Gallego <Javier.Gallego@softwareag.com>
  • Jochen Krause <jkrause@innoopract.de>
  • Luis Derechin <luisd@jackbe.com>
  • Mark Gally <mgally@mercedsystems.com>
  • Nolwen Mahe <nolwen.mahe@sap.com>
  • Paul Kim <pkim@mozilla.com>
  • Raju Vegesna <raju@adventnet.com>
  • Todd Hay <thay@adobe.com>
  • Torsten Preissler <tpreissler@innoopract.com>
  • William Shulman <will@mercedsystems.com>

Agenda

Topic: Chris unable to attend

Jon: Chris had a conflict and is unable to attend.

Topic: Brand Strategy Document

Andre/Sharat: Pretty good.

Jon: Any changes needed?

Andre: Doesn't match current logos. The brand strategy says it's all about "OpenAjax".

Jon: The current logos were done in parallel with the brand strategy doc. I met on Friday with Dylan and his graphics guy Torrey and we are now in sync. New logos will be coming soon.

Dan: Maybe too much open source. Isn't closed source open standards OK? How to define open standard? OK for open spec published by one company?

Jon: We will have a vocabulary page which defines our terms crisply. I assume a strict definition for "open standard" on that page where the spec is controlled by a legitimate standards body with a community process and implemented by multiple vendors, not a spec controlled by a single vendor even if openly published. I will add at least a placeholder on our vocabulary page. (See definition that has been added to http://www.openajaxalliance.org/member/wiki/index.php/Vocabulary, borrowing words heavily from the EU definition of "open standard".)

Andre: Some of the phrasing might be too strong on open source.

Dan: Yes, make sure that it is inclusive of open standards that might not be open source.

Dan: Make sure there is enough there about royalty free and unemcumbered.

ACTION: Jon to review brand strategy page regarding open source and royalty free.

Topic: Logos and graphics design of web site

Jon: Dylan has volunteered his colleague Torrey to help with graphics design. We met on Friday to go over brand strategy document. New logo proposals should appear soon. Also, Torrey will be making proposals on the look and behavior of the web site. Which brings up the question: how much Ajax and Web 2.0 should we have on the web site?

(someone): Didn't we decide at a previous meeting that we were going to model ourselves after a particular other web site?

Jon: Yes. At a previous meeting, you looked at 6-10 web sites and decided that vesa.org was the closest in terms of the sort of content that should be on the site. But this is a different question - the look and feel. Should the web site be straight HTML or all full of Ajax or what?

Joe: Need to show you are eating your own cooking

Rob: Whose and what? Which technology to use without showing favoritism

Gary: Agree. Important that the site show something with Ajax

Jon: My thinking was that it was OK to use HTML for most of the site and have showcase areas which show Ajax in action, but focus the showcase areas on Ajax interoperability, not just Ajax

Rob: Need to show open, but how

Andre: Need feedback features, such as wiki. Equally important to showcasing. Need to be transparent about the information.

Dan: Need RSS feeds for the news. Need to be Web 2.0 friendly. However, if Ajax is in the core, we indicate a particular position about how to use Ajax in practice.

(someone): Can we do homegrown Ajax so that we don't endorse one particular technology?

Jon: Sure. Steal and modify Ajax examples from the web. Just takes time.

Sharat: Need to ask what's in the store front? What are we trying to push out?

Jon: Good lead into next topic.

Topic: Web site content

Jon: I posted sample content at the above URL for people to review. Almost purposely has bad graphics so people know this is not what will get pushed to public site. Comments or suggestions? What's missing? We have talked about a showcase or example page.

Rob: Examples page: will it duplicate what's on the web?

Jon: I was thinking we would only showcase Ajax interoperability, not showcase Ajax. Thus, at least two technologies in combination.

Rob/others: Yes, that's good.

Rob: Showcase isn't needed for first version.

Rob: We as a group need to set a good example. Not gratuitous Ajax. Using Ajax universally is a bad example. Diminishes the value. Don't force fit into an informational site.

Jon/Andre: Agree.

Andre: Initially, main focus is progress of the committees. Maybe we need a content management capability.

Jon: Maybe with a wiki on public site?

DavidF: Need to keep things formal.

(someone): Ask the Interoperability committee whether wiki would help their process.

DavidF: Recommend that web site explains that limited demos is because Ajax interoperability isn't there today, why we don't eat our own dog food.

Jon: Very good advice. Yes, we need to put that on web site somewhere. Not sure exactly where right now.

Andre: Totally agree.

Topic: Whitepaper

Jon: I liked both the intro and the outline

(multiple): looks very good

(someone): should it say something about accessibility?

Jon: Needs to be in there somewhere

Jon: Chris suggested included something like Ray Valdes's 4 steps toward Ajax adoption, ultimately achieving desktop-like apps. I responded by saying that it fits into "what you can do with Ajax" section, but would become what you can do and what you will do

Andre: Yes, I agree.

(multiple): We have text to contribute from books and things. Don't need to write new text.

Jon: Can steal from Nexaweb's document: http://www.openajaxalliance.org/member/wiki/index.php/Image:NexawebAjaxCharacteristics.pdf

Jon: Any volunteers to help with whitepaper? Who will volunteer for which section?

(group decision): Everyone agrees to add a discussion item to the whitepaper wiki page within one week with statement about whether they can help with the writing and if so which sections

  • Note: non-attendees need to add an entry to the wiki page also
Retrieved from "http://www.openajax.org/member/wiki/Marketing_Minutes_2006-06-20"
Personal tools