Community-led development "The Apache Way"
This was extracted (@ 2022-01-14 01:10) from a list of minutes
which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
The XAP project has been retired.
Advice of the Mentors is that there is no activity, and it should likely be suspended.
The project reports no activity.
XAP appears to have become essentially dead back in March or April. The Incubator PMC will investigate dormant status for it.
XAP has been almost entirely inactive for at least the last 4 months. A discussion about its status was attempted, and did not elicit much of a response. The Incubator PMC will look to vote it into a dormant status.
Failed to report.
XAP is an XML-based declarative framework for creating Ajax applications. Community * There was some movement to make a few more people committers who have been filing numerous bugs and bug fixes, we need to follow up on that. * Lack of activity on the mailing lists is a problem; we will have to do better there. Software * I (James M) was onsite at a real customer creating a production deployment. Ran into some bugs and performance issues, especially in IE6, which have been fixed and rolled into the XAP codebase. In particular data centric widgets like tables and comboBoxes should perform better, application startup time is greatly reduced and some stability issues with table were addressed. (No more crashing) * We are starting the process of doing another release that incorporates these changes. Issues before graduation * Aforementioned community issues as well as community diversity.
No report. Part of the "Projects in Trouble" e-mail to discuss future status.
iPMC Reviewers: jerenkrantz, yoavs, jukka, twl, noel Since our last report a number of people have begun contributing bug reports and fixes through JIRA, including some huge improvements to the widget tests that are now very robust. (Thank you Trevor) Hopefully some of these contributors will be converted to committers in short order. XAP is in the midst of getting out a first release - most issues have been resolved (file headers, etc), still working through a couple things like NOTICE file contents. The Wiki has been updated with more information for both developers and users. (But probably needs updating again) Technical changes include many bug fixes to individual widgets, replacement of the logging mechanism with a log4j-based approach (feedback on how close this is to log4j would be appreciated, the code is in xap/log/Logger.js), a cleaned up launch mechanism, conversion of config file from XML to JSON format, some performance improvements, etc. Future plans: More bug fixes, better samples and examples, constant code cleanup and maintenance, performance improvements. (Initial loading, memory use) Beyond that need to discuss as release winds down. iPMC Comments: * noel: As Justin has repeatedly told a number of projects, please follow the report template, e.g., "What is XAP?" ----
XAP is a declarative framework for building, deploying and maintaining Ajax-based rich internet applications with the goal of dramatically simplifying Ajax application development. XAP entered incubation in May 2006. Top three items to resolve before graduation: * Bring the codebase to a level that contributors can make contributions without significant pain; * Create a XAP incubating release with proper packaging and quality * Engage a higher level of community activity and contribution Community * Various discussions on the XAP dev list on technical issues such as application initialization and DOM model; * Attended ApacheCon and gave a lightening talk on XAP * A session called "Introduction to XAP" was presented at AjaxWorld Conference and Ajax Experience conference at Boston * Various third party expressed interest in learning more about XAP, but complained that not easy to get infomation and not easy to figure out what XAP code does. Code * Achieved milestone 3: added more widgets and streamlined initialization * Various bug submission and JS unit tests submitted by Trevor Oldak * Update demo applications with improved performance * Working towards the next milestone: more widgets and some appealing demos to attract more developers