This was extracted (@ 2024-03-20 21: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.
WARNING: these pages may omit some original contents of the minutes.
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).
(Report by the Shepherd) Sadly, this podling seems to have expired. There has been no traffic on any mailing lists since last report, and the last words were to the effect that no one is left with time to spend. The IPMC will most likely wind this up and store it into the attic before the next report. Signed off by mentor: Shepherd: Benson Margulies
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: - Oracle finally stated its position on JSR 326 and the Kato project. In short, other technologies are a higher priority, and there is a limited audience for the API. - There was a lot of discussion on the status of this project and the reporting of that status. - Robert Burrell Donkin announced his resignation from the IPMC and as mentor for this project. - There was some discussion about the future of the project, but nothing concrete. The following is planned for next reporting period: - Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community. Signed off by mentor: ant
*** DID NOT REPORT! ***
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * Some JIRA items have been raised regarding the command-line tomcat commands. * Discussions with Oracle have been continuing. An individual from Oracle has been identified, but no discussions have come from this yet. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * Some JIRA items have been raised regarding the commandline tomcat commands. * Discussions with Oracle have been continuing. An individual from Oracle has been identified, but no discussions have come from this yet. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * There had been some discussion with Oracle regarding the future of JSR-326 in May this year, a definitive statement is expected from them in July. * The question has been raised as to the future of JSR-326 and the Apache Kato podling, the options being to keep both or continue only with one of them. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community. Sadly Kato seems still to be set on a holding pattern
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * While Oracle has expressed a continued interest in the JSR-326, there has been no change in the podling's status since the last report in June. * As in June, the project is effectively paused until Oracle's involvement in the Kato podling has been clarified. The credibility of the standard relies on there being more than one major Java VM vendor involved. The following is planned for next reporting period: * To be determined once Oracle's involvement has been established. Before this project can graduate we need to encourage more participation in the project and grow the community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * While Oracle has expressed a continued interest in the JSR-326, there has been no change in the podling's status since the last report in June. * As in June, the project is effectively paused until Oracle's involvement in the Kato podling has been clarified. The credibility of the standard relies on there being more than one major Java VM vendor involved. The following is planned for next reporting period: * To be determined once Oracle's involvement has been established. Before this project can graduate we need to encourage more participation in the project and grow the community. = ManifoldCF (nee Lucene Connector Framework) = Description: Lucene Connector Framework is now called ManifoldCF, by vote of the ManifoldCF community, and based on feedback from the Incubator PMC. ManifoldCF is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. ManifoldCF also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. ManifoldCF has been in incubation since January, 2010. It was originally a planned subproject of Lucene but is now a likely top-level project. A list of the three most important issues to address in the move towards graduation: 1. A 0.1 release needs to be finalized; a release candidate is currently available for the developer community to evaluate 2. We'd welcome additional active committers 3. We'd welcome long-term contributions to project testing, especially for newer versions of repository software Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?: All legal issues have be addressed to our satisfaction at this time. How has the community developed since the last report?: A book is being written, and we've had a number of extremely helpful contributions from the field. The active committer list is still pretty short, however. How has the project developed since the last report?: A release candidate is being evaluated. Online documentation is now much more detailed, and includes all javadoc as well. Contributions assessing project performance have been made. Contributions evaluating use of the FileNet connector for FileNet 4.5 have also been made.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * While Oracle has expressed a continued interest in the JSR-326, there has been no change in the podling's status since the last report in June. * As in June, the project is effectively paused until Oracle's involvement in the Kato podling has been clarified. The credibility of the standard relies on there being more than one major Java VM vendor involved. The following is planned for next reporting period: * To be determined once Oracle's involvement has been established. Before this project can graduate we need to encourage more participation in the project and grow the community. = Lucene Connector Framework = Apache Connectors Framework is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. Apache Connectors Framework also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. Apache Connectors Framework has been in incubation since January, 2010. It has recently been moved from a planned subproject of Lucene to a planned top-level project. A list of the three most important issues to address in the move towards graduation: 1. A final top-level-appropriate name choice for the project needs to be confirmed 2. Nightly builds and javadoc need to be set up, and a release process needs to be defined 3. The first official release needs to be executed Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web connectors properly. How has the community developed since the last report? We have had quite a lot of use of the software from most areas of the world, and offers of contribution of connectors as well. ACF now has several regular contributors, in addition to its dedicated user base. The name changes we are undergoing will likely inconvenience many of these users, which is why this is a critical issue to resolve promptly. A book is also planned and will be written over the next nine months. How has the project developed since the last report? Plans for a first release have been executed almost completely. Better tests have been added, although not for proprietary connectors. An API has been added to aid integration support. Tree reorganization has taken place to assist with Maven integration. Online end-user documentation is complete. A quick-start example, based on Jetty and Derby, has been written and should assist novice users in getting set up quickly.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API. Recent Activity: * The project has effectively paused until Oracle's involvement has been clarified. The credibility of the standard relies on there being more than one major Java VM vendor involved. Originally both Oracle and Sun were members of the JSR, but since then Oracle has bought Sun and is now owns both the HotSpot and JRockit Java VMs. The following is planned for next reporting period: * To be determined once Oracle's involvement has been established. Before this project can graduate we need to encourage more participation in the project and grow the community. = Lucene Connector Framework = Description Lucene Connectors Framework is an incremental crawler framework and set of connectors designed to pull documents from various kinds of repositories into search engine indexes or other targets. The current bevy of connectors includes Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), SharePoint (Microsoft), RSS feeds, and web content. Lucene Connectors Framework also provides components for individual document security within a target search engine, so that repository security access conventions can be enforced in the search results. Lucene Connectors Framework has been in incubation since January, 2010. A list of the three most important issues to address in the move towards graduation 1. Javadoc and nightly builds need to be set up 2. The first official release needs to be planned and executed 3. Unit tests need to be completed Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? 1. We'd like to know whether there is any official Apache position on inclusion of NTLM implementations in ASF projects, since we've gotten mixed signals on this from other developers. This represents a crucial piece of functionality needed to support LiveLink, Meridio, SharePoint, RSS, and Web connectors properly. How has the community developed since the last report? 1. A number of people outside the committers group have been using this project, and there are lively discussions in the newsgroups. 2. LCF was presented at Lucene/Solr Eurocon to quite a bit of interest. How has the project developed since the last report? Online end-user documentation is coming along and is perhaps 90% complete. Integration with Derby has been undertaken to allow for a robust Junit test framework.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Recent Activity: * The project's first release M1-incubating was finally released. The following is planned for next reporting period: * The completion of the JSR-326 specification. * Finalization of RI and JSR. Before this project can graduate we need to encourage more participation in the project and grow the community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Recent Activity: * The project is working towards making a milestone 1 release. Currently working through release candidates using a multi-staged audit process as suggested by Robert Burrell Donkin. * The JSR specification document has been accepted as an Early Draft Review and the review period has passed. * The Technology Compliance Kit (TCK) has been running against the hprof and CJVMTI implementations of the API. The following is planned for next reporting period: * Our first release of the RI, demos and TCK. * The 1.0 release of the RI in concert with the Final Draft Review (FDR) of the JSR. * Finalization of RI and JSR. Before this project can be graduated we need to produce a usable implementation of the API and more useful tools to encourage adoption and participation of a much needed community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Recent Activity: * We produced two implementations of the Apache Kato API - one based on Hprof and another on JVMTI using python. * A Developerworks article on Apache Kato and JSR-326 was published. * The API is being built and Javadoc is available on Hudson. * Builds are now being performed on the ASF's Hudson server * A presentation was given on the Apache Kato API. Recordings are available on the Wiki. * A BOF on Apache Kato and JSR-326 was held at Java One 2009 - BOF-4870. The following is planned for next reporting period: * We will produce an Early Draft Review for the JSR in time to meet it's deadline. * We will build all of the project on the ASF's Hudson server. * We will have a viable reference implementation of the API and TCK. Before this project can be graduated we need to produce a usable implementation of the API and more useful tools to encourage adoption and participation of a much needed community.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Recent Activity: * The corporate CCLA has been received by ASF. * Initial code contribution has been contributed. The following is planned for next reporting period: * Contributed code to be built. * API Java doc to be built and put onto website. * Development of reference implementation (RI) of Kato API. * Development of working TCK.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Recent Activity: * The discussions on users stories for the tools that will shape the API have been ongoing. * Work is being done to get the CCLA and initial code contribution prepared. Target is the end of February. The following is planned for next reporting period: * Wiki and Website setup. * Contribution of source code along with CCLA.
Quiet month with little progress due to vacation period. * JSR development has started in earnest with group working to define/prioritize major user stories. * CCLA from IBM is still outstanding. Current expectation is end of month.
Kato was accepted into the Incubator on 6 November 2008. Kato is a project to develop the Specification, Reference Implementation, and TCK for JSR 326: the JVM Post-mortem Diagnostics API Kato is just starting up; most of the infrastructure work has now been done; mailing lists, SVN, JIRA etc. created. Most initial committer user IDs have been requested, still waiting on the last couple of CLAs. The next steps for Kato are agreeing the highest level user stories that will drive the JSR design and seeding the repository with the code contributed by IBM.