What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
The Yoko community has decided that it's probably best to split the project in two and submit them to be housed as sub-projects of CeltixFire and Geronimo. The WS bindings, and the requisite support tools, of Yoko would move on to CeltixFire with everything else, e.g. ORB and RMI, moving on to Geronimo. A committer roll call was performed and a list of developers still interested with either/both of the two bodies of code. Proposals will be submitted to both the CeltixFire and Geronimo PMCs this month.
The Yoko project is a robust and high performance CORBA server which is usable from inside any JVM. Since our last report there have been some changes in mentorship and we have continued to improve the Binding runtime and type support for idltowsdl and wsdltoidl as listed below. 1) Items to resolve for graduation * We are also planning to improve the documentation for Yoko, with the goal of providing more in depth information to users of the Yoko project and to assist any future committers in understanding the existing code and functionality. * Work on stabilizing the code and get it ready for a 1.0 release which should improve overall quality. 2) Community aspects * We have a new mentor on board: Welcome Matt Hoggstrom! and thank Ken Coar for his contributions. * Discussion started about the project status and how it may work better and/or graduate into other projects like Geronimo, Harmony, and CXF. * Increased activity on user/dev list around the binding components, possibly due to the release of CXF driving some interest in the corba binding components. 3) Code aspects * Adding more new type support to the binding runtime. * Continual improvement of performance for the runtime binding in terms of marshaling and unmarshaling data. * Adding new type support to the IDLToWSDL and WSDLToIDL tools and adding quite a number of new tests. * Fixing some issues in the ORB core code. * Currently working on preparing Yoko for a 1.0 release. * Cleaning up the jira issues for the 1.0 release.
iPMC Reviewers: jukka, rdonkin, mvdb The Yoko project is a robust and high performance CORBA server which is usable from inside any JVM. Incubating since: 2006-01-31 Since our last report, the majority of the development work in Yoko has focused on: * Adding new type support to the binding runtime. * Improving performance of the runtime binding in terms of marshaling and unmarshaling data. * Adding new type support to the IDLToWSDL and WSDLToIDL tools. * Fixing minor issues in the ORB core code. * Started development of an IDL preprocessor for the tools module. * Prepared and completed a Milestone 2 release Yoko has also become a key component of the soon to ship Geronimo 2.0 release, which has just passed certification tests. Future plans: We are currently working to stabilize and finalize type support in the binding runtime and tools in preparation for a release which would like to put out shortly. We are also planning to improving the documentation for Yoko, with the goal of provide more in depth information to users of the Yoko project and to assist any future committers in understanding the existing code and functionality.
Yoko is active and failed to provide a report on time.
