Main Page

From RuntimeWiki

Jump to: navigation, search

Contents

Welcome to the OpenAjax Runtime Wiki!

This wiki is used by the various members of the greater Ajax community to collaborate on a unified, prioritized list of feature requests from the Ajax community to the browser vendors.

This initiative is open to the general public (i.e., you don't have to join OpenAjax Alliance to contribute to this wiki). Despite being open to non-members, there will be strong participation from various members of OpenAjax Alliance, most particularly the alliance's Runtime Advocacy Task Force, chaired by Coach Wei.

Who can participate and how to join the effort

People from the community can participate in this effort, whether you are a member of OpenAjax Alliance or not. To gain write access to this wiki:

  • Go to http://www.openajax.org/runtime/wiki/Special:Userlogin
  • Click "Create an account"
  • Fill in all of the fields and press "Create account"
  • Check your mail for a confirmation email. Click on the link in the email to activate your account.
  • Refresh any browser windows that are open to Runtime wiki pages

We believe that it is important for the industry to know who has expressed what opinions on various topics, so we request that your wiki login somehow convey your real identity clearly, such as making your wiki user name match your real name, as in "NapoleonBonaparte" (i.e., if your name matched that of the former emperor of France).

How To Participate and Vote

We are now in Phase I (see Timeline at the bottom of this page), where participants not only add comments, but also are asked to identify their Top 5 features (i.e., those features that are most critical for inclusion in next-generation browsers).

In addition to voting, please help us perfect the list and the write-ups for the various features. It is OK to add new features to the list if you see something important that is missing.

Why this effort was launched

At the OpenAjax 2007 September Members Meeting, the members of OpenAjax Alliance discussed the challenges for future Ajax growth and adoption, in particular, issues directly related to the various Ajax runtime environments. For example, browsers allow only two connections per domain, and browsers do not provide a good infrastructure for secure mashups (hence all the hack we are doing with SMash etc...). Similar topics have come up many times in different working groups and task forces. Such conversations typically concluded that we should talk to browser vendors on such issues, but so far very little action has been taken from OpenAjax Alliance as an organization on this front - though various individual members have done a lot of work on their own.

The collective wisdom was that OpenAjax Alliance,should do something in this area. We should collect the key issues not only from the 100 or so OpenAjax Alliance members but also from leading members of the community who do have not joined OpenAjax Alliance. Then we should communicate the prioritized feature list to the browser vendors as well as the outside community at large. This will help educate the community in large, help browser vendors better plan for their product roadmap, and help OpenAjax members better use Ajax. In the end, creating a better Ajax eco-system.

How to join OpenAjax Alliance

While it is not a requirement to become a member of OpenAjax Alliance in order to participate in this particular effort, we do encourage the community to become OpenAjax members in order to stay informed about the many important initiatives happening at OpenAjax Alliance and to help contribute to some of those initiatives. There are no fees and the application process is simple. Here are some links:

Documents

Projected timeline

Legend:

  • Tasks done by OpenAjax Alliance leadership
  • Public announcements
  • Collaborative work done by the community
Time periodMilestone
Until March 2008 Develop an initial list of feature requests, collected by researching various blogs, soliciting suggestions from the OpenAjax Alliance members, and reaching out to interview representatives from leading Ajax toolkits
~April 1 Public announcements to the community first pass review on our initial feature list
April 2008 First pass community review, where participants:
  • Review and collaborate on our initial feature list
  • Identify the top <n> most important features needed in future browsers. This will help us to trim down the list to a more manageable number for the ranking exercise in the next phase

Please vote here Phase I Voting wiki page.

May 2008 Cleanup and re-organize the feature list to take into account industry feedback and those features identified as most important
~June 1 Public announcements to the community for final review of the feature list
June 2008 Second pass community review, where participants:
  • Review and collaborate once again on our (recently trimmed) feature list
  • Rank all of the remaining features according to importance
July 2008 Cleanup and re-organize the feature list one last time. Develop an executive summary. Finally, publish and declare victory.
Personal tools