Main Page
From RuntimeWiki
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.
Current status
We completed the first version of the OpenAjax browser wishlist on July 13, 2008, and it looks like we will push towards a second version in the first half of 2009.
The 2009 Browser Wishlist
Right now it looks like we will do a refresh on the browser wishlist sometime in 2009. Here is a wiki page that holds single-line bullet items for any feature requests that people would like to see on the 2009 browser wishlist:
The 2008 Browser Wishlist
We have completed the voting phases for the initiative (see Timeline at the bottom of this page). In Phase II voting, participants provided 0-10 rankings for the proposed features.
The initiative's moderators have produced a summary report on the feature list and the voting:
The list of features that have been submitted (along with voting totals on the features that were part of Phase II Voting) can be found at:
The 37 "Phase II" features have been sorted in the order of which features received the most votes on the following wiki page:
A long page that captures all of the votes that were cast, with a few assorted supplemental comments, can be found at:
Please help us to continue to 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.
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).
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:
- OpenAjax Alliance home page: http://www.openajax.org
- OpenAjax Alliance member wiki: http://www.openajax.org/member/wiki
- How to join: http://www.openajax.org/join.html
Historical Documents
- Ajax Runtime Issue List Working Draft
- Call with Joe Walker Minutes Feb 26 2008
- Call with Jack Slocum Minutes Feb 26 2008
Timeline
Legend:
- Tasks done by OpenAjax Alliance leadership
- Public announcements
- Collaborative work done by the community
| Time period | Milestone |
|---|---|
| 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:
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 10 | Public announcements to the community for final review of the feature list |
| June 10 - July 13, 2008 | Second pass community review, where participants:
|
| late July 2008 | Cleanup and re-organize the feature list one last time. Develop an executive summary. Finally, publish and declare victory. |
