Marketing Minutes 2006-12-12
From MemberWiki
URL: http://www.openajax.org/member/wiki/Marketing_Minutes_2006-12-12
Contents |
OpenAjax Alliance Marketing Committee meeting minutes 2006-12-12
Attendees
- Chris Prichard <cprichard(at)opsource.net>
- David Frankel <david.frankel(at)sap.com>
- Eric Thomas <ethomas(at)goetc.net>
- Erwan Paccard <epaccard(at)ilog.fr>
- Jim Driscoll <jim.driscoll(at)sun.com>
- Joseph Becker <bjoseph(at)us.ibm.com>
- Jon Ferraiolo <jferrai(at)us.ibm.com>
- Mike Wagner <mikew(at)jackbe.com>
- Seshubabu Simhadri <ssimhadri(at)gce2000.com>
- Sharat Chander <sharat.chander(at)sun.com>
- Shel Finkelstein <shel.finkelstein(at)sap.com>
- Ted Thibodeau <tthibodeau at openlinksw.com>
- Todd Hay <thay(at)activegrid.com>
Original Agenda
- Agenda
- News from Interoperability Committee and Open Source project at SourceForge
- Open Source project at SourceForge - Source code and automated tests nearly feature-complete
- Interoperability Committee now focused on new issues
- Interoperability WG proposal and charter in early January - per our Development Process
- Skeleton draft of Hub spec: http://www.openajax.org/member/wiki/OpenAjax_Hub_Specification
- OpenAjax Official Registry of Toolkits/Libraries and Associated Global Variables
- Best practices
- Marketing committee priorities for next couple of months
- Marketing WG proposal and charter in early January - per our Development Process
- What should we try to have ready and announce by AJAXWorld (March 19-21)?
- What should be nature of InteroperabilityFest on second day of our face-to-face (March 22-23)?
- Make progress on OpenAjax Conformance and OpenAjax Best Practices?
- 2nd Generation White Papers
- Jon promises to have initial drafts of all white papers for next Marketing meeting (Jan. 9).
- Next meeting: Jan 9
- News from Interoperability Committee and Open Source project at SourceForge
Minutes
Topic: News from Interoperability Committee and Open Source project at SourceForge
- Open Source project at SourceForge - Source code and automated tests nearly feature-complete
- Interoperability Committee now focused on new issues
- Interoperability WG proposal and charter in early January - per our Development Process
- Skeleton draft of Hub spec: http://www.openajax.org/member/wiki/OpenAjax_Hub_Specification
- OpenAjax Official Registry of Toolkits/Libraries and Associated Global Variables
- Best practices
(Jon describes the above)
?: Who manages the official list of global objects?
Jon: Interop committee / wg
(on subject of best practices)
Sharat: Can broad community contribute to best practices?
Jon: Here is the model, which is pretty much how everything works with OpenAjax. Public can submit proposed best practices via public forums such as public@openajax.org. Members can submit proposed best practices by adding entries to the appropriate wiki page. (Only members can write to our wiki.) The Interop WG will decide which best practices are approved as official OpenAjax best practices.
Topic: Marketing committee priorities for next couple of months
- Marketing WG proposal and charter in early January - per our Development Process
- What should we try to have ready and announce by AJAXWorld (March 19-21)?
- What should be nature of InteroperabilityFest on second day of our face-to-face (March 22-23)?
- Make progress on OpenAjax Conformance and OpenAjax Best Practices?
- 2nd Generation White Papers
- Jon promises to have initial drafts of all white papers for next Marketing meeting (Jan. 9).
(Jon discusses points above. Points out that 2006 was focused on setting up the OpenAjax Alliance organization, deciding what we wanted to do, and then implementing the Hub. 2007 will be about pushing our efforts out into Ajax products and achieving real interoperability.)
Jon: What do people think about how to take advantage of the March events?
DavidF: Make sure I understand. 2nd day of FTF would be demos of Hub working?
Jon: That's the general idea.
DavidF: Getting people who are non-members to hang around until the end of the week to join our interop day might be difficult. Perhaps we could do interop demos during the conference, before the FTF?
Jon: Makes sense. I could do demos of progress during my talk at AJAXWorld.
Joe: Maybe we could have an OpenAjax Alliance table at the conference where we demonstrate OpenAjax interoperability. At the table we could hand out press releases and recent white papers.
Jon: Great idea.
Erwan: Is there a connection between the AJAXWorld activities and the process activities such as the Marketing Charter?
Jon: Not really. Pretty much independent. But the Marketing committee needs to work on both tasks in January.
Erwan: Should we make a wiki page about ideas for AJAXWorld?
Jon: We could do that. I suggest starting off with people making suggestions via email to marketing@openajax.org.
Erwan: Do any draft charters exist yet?
Jon: A couple of months ago, when Mike Milinkovich delivered his very first drafts of the Development Process, I created initial draft charters for the Interoperability and Marketing WGs. The draft charter for Marketing is at the Marketing_Charter wiki page Marketing Charter. I haven't looked at the draft charters since then. Probably we will need some significant editing on them.
Joe: Where is FTF?
Jon: IBM offices in NYC unless someone else volunteers.
Jon: At our FTF meeting, in its breakout session, the marketing committee decided that we should define OpenAjax Conformance. In phone calls since then, we have talked about a logo for companies that deliver conformant products, but wanted to wait until we had a concrete definition of conformance before using the logo. Now it is time to start defining conformance.
Erwan: Needed by challenging. Perhaps a never-ending story.
Jon: I suggest that the first version of "OpenAjax Conformance" consists of two things: (1) You support the Hub, and (2) You conform to all of the MUST items in our best practices documents.
Erwan: Who would test to ensure conformance?
Jon: W3C approach is that they define conformance criteria but do not have police force to certify. Instead, vendors can make conformance claims and it is up to industry to call out false claims. That's what I am thinking .
Erwan: We talked about an OpenAjax-managed list of vendors that are conformant.
Jon: Yes. Something we have talked about. I would describe this as a list of Members who claim to be conformant. The only policing would be that if we know the claims are wrong, we would remove them from the list. But I doubt if we would ever need to remove anyone.
DavidF: What we did with other efforts was we got everyone in a room with a designated project manager. With a project manager, manager made sure there was some sort of test methodology ready for the event. When any glitches came up, the participants would work through them. Sometimes the spec needed clarification. Sometimes products needed fixes. Gradually worked things out. Helped to create test suites. Sometimes standards organizations have teams with labs that build and maintain test suites. Need some sort of agreed suite of test cases.
Jon: Great suggestions. Two comments. 1) The real-time event could be the main focus of the Interop-athon Friday activities at our March FTF.
DavidF: Need to have someone agree to manage it and will take responsibility.
Jon: I can take that on. It is consistent with my primary objectives for 2007, which is to get OpenAjax rolled out into industry products. I can find the time for this.
David: Need a procedure for verifying interoperability.
Jon: I can make a strawman proposal.
Ted: seems we have a couple of different goals for conformance and interoperability. 1) What does it mean to be conformant? This will focus on toolkits being compatible with the Hub. 2) Achieving industry interoperability. This is likely to be the focus of the Interop-athon. For example, this widget must work inside your framework. Have a demo set up where you push a button and it either works or doesn't.
Jon: Fantastic suggestions.
DavidF: I was project manager for IIOP. We had programmers locked in room for 3 days.
Ted: Yes. Not a small task. OAT, for example, is not a trivial thing.
Jon: I forgot to preface my overall comments about the March events. We need to establish low expectations for the industry. Explain that we are just crawling as in crawl, walk, run. Just getting started in March, but explain the roadmap, and state that we expect much greater interoperability by the time our next event happens in Oct 2007.
Jon: But we should be able to have some progress in March. The Hub is far along now and there is a lot of industry prior art that we can use, such as jMaki.
Jon: Back to conformance. What do people think of my proposal that the first version of "OpenAjax Conformance" means supporting the Hub and supporting our Best Practices?
Ted: Maybe need something like SQL, where there is core conformance and then higher levels. Core might mean you use the Hub. Maybe core conformance would be very easy such as somehow saying I am supreme and no one else can run.
Jon: I definitely agree that we will probably need conformance levels.
DavidF: Yes, very common to have conformance levels. But I didn't understand the first suggestion and how that would provide value to the industry.
Jon: Me neither but Ted was just brainstorming. We can discuss details later.
Jon: Once again, what do people think of my proposal that the first version of "OpenAjax Conformance" means supporting the Hub and supporting our Best Practices? Any objections?
(silence)
Jon: I will make a wiki page with this as a straw man. (Note: wiki page has been created - http://www.openajax.org/member/wiki/OpenAjax_Conformance)
Topic: Next meeting: Jan 9
Jon: We will cancel the next meeting - Dec. 26 is the day after Christmas.
Jon: I commit to having drafts of white papers for the next meeting.
DavidF: Regarding white papers, I volunteer to help, even if just doing editing reviews.
Jon: Your editing reviews were great help for the AJAXWorld article.
DavidF: That turned out really well.
Jon: Certainly minimally adequate.
