Marketing Minutes 2006-11-14

From MemberWiki

Jump to: navigation, search

URL: http://www.openajax.org/member/wiki/Marketing_Minutes_2006-11-14

Contents

OpenAjax Alliance Marketing Committee meeting minutes 2006-11-14

Attendees

  • David Frankel <david.frankel@sap.com>
  • Erwan Paccard <epaccard@ilog.fr>
  • Jon Ferraiolo <jferrai@us.ibm.com>
  • Ted Thibodeau <tthibodeau@openlinksw.com>

Agenda for Nov 14

Minutes

Topic: Legal updates to Web site (protected with guest/guest security)

Jon: Because so few people have shown up, let's push this off until next meeting. Anyways, I haven't received legal opinion yet on these pages.

Erwan: Nice that the pages show the changes visually.

Topic: Legal updates to Web site (protected with guest/guest security)

Ted: No need to make it a personal opinion. Nothing offensive. Make it an organizational entry.

Erwan: Agree.

RESOLUTION: Update the blog entry to make it the official opinion of OpenAjax Alliance and post the blog entry. (Pending Steering Committee review.)

Topic: White paper strategy and AJAXWorld article

Jon: AJAXWorld deadline for article at end of November. Marketing committee meets twice before then, counting this meeting. Best if we can get as much leverage as possible between our 2nd generation white papers and that article.

(Jon gives overview of comprehensive white paper plan, with four white papers which represent the new collection of OpenAjax white papers. White paper #2 would be repurposed for AJAXWorld.)

Erwan: I hope to find half a day to help with white papers within next two weeks. No promises.

DavidF: Will these white papers each be stand-alone documents or will they depend on previous ones.

Jon: I recommend loose dependencies, where we attempt to make each paper as standalone as possible, with caveat that we want to minimize redundancy.

DavidF: Develop documents in parallel or sequentially?

Jon: I was thinking that we work on them in parallel, developed as a collection of documents.

DavidF: Topics need some further clarification. There will be some redundancy if worked on in parallel. Sequential would achieve less overlap. For example, in Why Ajax, you need to say something about next-generation applications. Tricky to develop the documents in parallel.

Jon: I was thinking that the white papers would be done at the same time by the same people.

Ted: If primary author is the same, OK, but if different authors, will need more detailed outline before work begins.

DavidF: Detailed outline down to 3rd level headings. If outlines are that detailed, probably OK to do parallel work.

Jon: I will shoot for detailed outlines for the next meeting.

RESOLUTION: Jon will have detailed outlines for 4 white papers ready for next meeting

Erwan/Ted: The more you can do before the next meeting, the better.

Jon: I am confident I can pull documents together quickly because we have a lot of content around to repurpose. I just can't promise the results will be high quality.

Erwan/Ted/DavidF: Better to get strawman proposals for people to review than to have clean slates.

DavidF: Why parallel?

Jon: Mainly because there will be iteration requirements where sections might need to move between documents.

Ted: Not a problem to finish one document then go back and change it.

Jon: Because of AJAXWorld, we will have to work sequentially, at least for white paper #2.

Ted: Better to keep the work sequential.

Jon: How about I provide a detailed outline for all four white papers for the next meeting, and then we work on the words for each document in a sequential manner.

DavidF: Sounds good to me.

Erwan: Aren't we developing the documents on a wiki?

Jon: Yes. Sequential is just a guideline for primary authors but anyone can change anything at any time.

Topic: White paper #2 (Why Ajax) and AJAXWorld article

(Jon gives executive summary as mainly the union of Chris's outline and Erwan's outline, with textual content repurposed from existing proposals.)

DavidF: A Value Proposition focus?

(confusion about hyperlinks)

Jon: I would say more of an ROI focus. Therefore, a second on value proposition, plus a fess-up section on costs, and then a section on particular characteristics such as network bandwidth requirements.

Ted: Bandwidth might not be helped by Ajax.

Ted: How many words can the article be for AJAXWorld?

Jon: I believe 1000-1500.

DavidF: As it stands, the article is now 2500 words

Ted: Won't fit into a feature piece. Would tend to be higher level digest of what is there now.

Jon: For previous AJAXWorld articles, I have to cut sections and condense sections to fit, but I am not sure I had to cut anything in half.

DavidF: Is it an online or print magazine.

Jon: Hardcopy.

DavidF: When will the issue go out?

Jon: I don't know, but guess about two months after Nov deadline.

DavidF: Could point to the more detailed white paper on our web site.

Jon: My recommendation is to not do any references to future documents. We might change our mind.

DavidF: Maybe we should focus the Marketing committee on the shorter version needed for AJAXWorld.

Ted: Current article has too many headings. As it stands, it is just a set of fleshed-out headings. If we strip headings and flows, it shrinks. A full outline isn't as useful for magazine articles.

Jon: I agree that the short-term priority is the shorter version.

DavidF: Shorter version on its own wiki page?

Jon: Yes.

RESOLUTION: Make a wiki page for shorter version of white paper #2

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