New PMC Member: Mohammad Nour El-Din accepted, having accepted the election that took place earlier in November.
Ex-PMC Member: Justin Erenkrantz left the PMC. We discussed mothballing Droids, but Torsten is asking for more time, and there do seem to people wanting to work with him, so we'll see what happens between now and the next Board report. Similarly, Gianugo has joined with the Stonehenge community to help it decide what to do. We've decided to broadly, rather than as an experiment, permit podlings to vote on Committers, as permitted by the Board some months ago. As long as at least one Mentor votes for the committer, and proper notification is sent to the private@, the vote will be deemed valid. There was some discussion about projects using real-time communication, but I believe that we've made it clear that all project decisions must be made via the mailing list, and that all back-channel discussion should be summarized on list. OpenNLP, a toolkit for natural language processing; Jena, a semantic web framework in Java that implements the key W3C recommendations for the core semantic web technologies of RDF and SPARQL; and Wave, "a hosted, live, concurrent data structure for rich communication", were voted into the Incubator. ESME and Aries were to request TLP status from the Board. River is in the process of preparing, and will likely request TLP status in January. Bean Validation & Celix did not report. ------------------------------------------------------------- = ALOIS = ALOIS stands for "Advanced Log Data Insight System" and is meant to be a fully implemented open source SIEM security information and event management system. ALOIS is incubating since 22nd October 2010. How has the project developed since the last report: * The ALOIS Debian packages are now available at http://debian.logintas.ch/all/ (for demonstration and development only, no official release yet) * Demo-Server is available in the amazon cloud (not published yet) * Local usage of ALOIS prepared (usage without installing files on the system) Three most important issues to address in the move towards graduation: * Create a public website with information on ALOIS * Review Code * Write a "Getting started" guide How has the community developed since the last report: * There is no community yet. = Aries = Aries delivers a set of pluggable Java components enabling an enterprise OSGi application programming model. Aries entered incubation on September 22, 2009. The Aries community and Incubator PMC have voted for Aries to graduate as a TLP. This is an agenda item in the Dec 15th 2010 Board meeting. There is discussion about making a release, which Karaf and Geronimo would consume, as soon as we have a decision from the board. There continues to be a vibrant community as shown by the activity on the mailing list in the last quarter. The Aries sub-components continue to be actively developed. Since the last board report we have 3 new committers (Bartosz Kowalewski, Chris Wilkinson and Emily Jiang) and one new PPMC member (Holly Cummins). We are close to moving our site from Confluence over to CMS. All that remains is for the site to be switched over. The CMS based site will allow us to update the site immediately after a change is made and more easily blend in non-wiki content such as that generated by the OSGi Enterprise Compliance Tests. There are no further issues to resolve before graduation - the Aries and Incubator communities have voted to graduate Aries to a TLP. = BeanValidation = Did not report. = Bluesky = BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. Current status of developing the next version of RealClass: *Complete testing of capture camera pictures with Opencv libaray; *Complete Message Parser API encapsulation and fundamental test; *Complete API encapsulation of Server and fundamental test; *Complete API encapsulation of en/decode/Audio & Video and Screen data transmission module; *Complete basic testing of communication between Server and Student/DTU; *Complete the first version of Teacher interface; *Finish testing all the third party library and they all work well with QT both under Windows/Linux platform. Next step: * Testing API of en/decode with testcase of record/playback function; * Evolve a final version Teacher interface; * Complete the first version of Student interface; * Discussion the broadcast algorithm in Server and DTU with certain developers and try to fufill it as quickly as possible; = Celix = Did not Report. = ESME = Enterprise Social Messaging Experiment (ESME) is a secure and highly scalable microsharing and micromessaging platform that allows people to discover and meet one another and get controlled access to other sources of information, all in a business process context. ESME entered the incubator in 2008-12-02. The following items have been performed since the last reporting period * Successful graduation votes on esme-dev and gene...@incubator * "Proposed Resolution to Establish TLP" email sent to Apache Board * Planning for Release 1.2 The following items are planned for the next reporting period: * Enjoy life as a TLP (Hopefully :->) Top 2 or 3 things to resolve prior to graduation * Increase community involvement in the project = Etch = Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. For the last 3 months the main effort has been by Holger Grandy and Michael Fitzner, who contributed integration of the C-binding and pumped out release 1.1. We also heard from Kay Weckemann, starting work on a udp transport and on security related topics. The BMW team also contributed an alpha version of a Google Go binding, and is working on a documentation framework. The three top issues from the last board report have been adressed: We published release 1.1, we updated the web site and documentation (although more needs to be done there) and we have set up a continous integration build. Although progress is now visible, we still need to get more user and development activity on our lists. Top issues currently are: - plan features and dates for release 1.2 / 1.1.1 - work on further language bindings - documentation = Gora = Gora is an ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop. A list of the three most important issues to address in the move towards graduation 1. Port Gora code and license headers into ASF license headers 2. Develop a strong community with organizational diversity and with infection into existing ASF projects like Nutch and Hadoop 3. At least one Gora incubating release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? Mailing lists activity is mainly from Gora committers and mentors at present. The Gora devs did answer a question from a user regarding how to build Gora over the past month and a few user requests (for Maven Central publishing and a bugfix) were filed as well. How has the project developed since the last report? Gora was voted into the Incubator by the IPMC on September 26, 2010. Enis Soztutar and Hentry Saputra contributed a tutorial on Gora and added it to the website in GORA-16 and GORA-17. Eugen Paraschiv posted an issue in GORA-19 requesting that the Gora artifacts be published to Maven Central. A bugfix issue was contributed in GORA-18 by Ioannis Canellos that addressed configuration issues in the trunk. Chris Mattmann posted a note to the dev list suggesting a 0.1-incubating release and volunteering to be the RM. Henry Saputra stepped up and suggested he would be willing to do it, so it looks like we have the RM situation taken care of. Chris suggested checking out the OODT release process doc on the OODT wiki for some pointers on how to get started. = Hama = Description: Hama was accepted into Incubator on 20 May 2008. Hama is a distributed computing framework based on BSP (Bulk Synchronous Parallel) computing techniques for massive scientific computations. Top 2 or 3 things to resolve prior to graduation: * Complete first release * Invite new active committers * Recruit more mentors Issues for the Incubator PMC or ASF Board: None. Community development: * Mailing list shows increased usage from previous report * Filipe Manana has contributed a great part in the development of BSP computing engine * A number of new individuals have expressed an interest in contributing in various areas * Hama workshop accepted at IEEE CloudCom 2010 Project development: * Our plan is now much more detailed * Work on creating the initial release * Maven building support added = Isis = Description Isis is an ASL 2.0 licensed implementation of the Naked Objects pattern. It is based on contributions of the original Naked Objects Framework along with a number of sister projects that were developed for the book "Domain Driven Design using Naked Objects". Isis was accepted into the Incubator in 2010, September 7th. Project development (month 3 of incubation): * setting up the build process has been finished. * Isis has now a Hudson build * Discussing the scope of the first Apache Isis release * Apache Isis website is up and running (see http://incubator.apache.org/isis/) Community Development (month 3 of incubation): * A few new names on isis-...@incubator.apache.org * new contributions from Mike Burton (wiki, reported issues and helped with build) and Sabine Winkler (site, TimePeriod) * Holding a public Skype conference led to highly controversial reaction from the ASF community and probably caused some irritation within the Isis community. * Wiki starting to get some useful content. * Lightning talk at LJC OpenConference, Nov 2010 . Top 3 Issues to address in move towards graduation: * Putting good documentation site out as start-off to building larger community. * Getting first release out to demonstrate credibility. * Ensuring existing committers all happy with transition to Apache and support existing users who like to move from NO to ISIS Issues for the Incubator PMC or ASF Board: None of these issues requires Board attention. New Releases: There is currently no incubator release yet. = Jena = Description: Jena was accepted into the Apache Incubator November 2010 (http://mail-archives.apache.org/mod_mbox/incubator-general/201011.mbox/%3C4 cec31e4.9080...@apache.org%3e). It is an existing project migrating to ASF. It has a large codebase that provides a semantic web framework in Java that implements the key W3C recommendations for the core semantic web technologies of RDF and SPARQL. Three most important issues to address for graduation: * Create a code base in Apache with legal clearance. * Establish the Apache-based community for developers, contributors and users * Create and communicate open project processes aligned to Apache Issues for the Incubator PMC or ASF Board: None. Community development: We have let our existing communities know that the project is moving from being an independent project to one based in ASF. Project development: The first step for the project is get the incubator infrastructure up and running, including ICLAs and user accounts. The project plans to make one last, non-Apache release to give it some space to setup in Apache with minimal disturbance to users. = Kitty = Kitty was accepted into the Incubator on 10 October 2010. The Kitty Project is a lightweight, production focused, Java-based application server performance diagnostic and management utility. The project has imported existing code, lists have been set up and committer karma assigned. Presentations were made at ApacheConNA 2010 and LAJUG to promote the existence of the project to the Java user community. The current challenges facing the project are: 1. Ensure the code satisfies ASF policies 2. To make the project is buildable 3. Generate interest and grow a community = Kato = 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. = OpenNLP = OpenNLP is a machine learning based toolkit for the processing of natural language text. It supports the most common NLP tasks, such as tokenization, sentence segmentation, part-of-speech tagging, named entity extraction, chunking, parsing, and coreference resolution. These tasks are usually required to build more advanced text processing services. OpenNLP entered incubation on 11/23 2010. Progress since then: * SVN and Jira set up complete * All committers now have ICLAs on file * Accounts have been created * Status page created * Initial web site created base on ASF CRM A list of the three most important issues to address in the move towards graduation: * Do the code import * Resolve potential IP issues * Do a release = RAT = RAT is a Java library that scans files for known licenses and reports files that lack any of them. Three frontends to said library exist in form of a command line client, an Ant task and a Maven plugin. RAT entered the Incubator in January 2008. There a has been zero activity in RAT during the last quarter. = River = Apache River is a distributed computing architecture, based on the JSK Starter Kit Source code donated by Sun Microsystems, for the Jini Specification. While generally referred to as a Service Architecture, it might be more easily explained to those familiar with Dependency Injection as a Protocol Independent, Distributed Dependency Injection Architecture, suited to both hardware and software. Instead of depending on Protocols directly for communication, everything is abstracted behind a Java interface, allowing protocols and implementations to be swapped freely, programming languages other than Java can also participate. River has been incubating since December 2006. The activity on the River project continues to grow and is seeing renewed interest from people who had previously fallen silent. The current development team feels that we are ready to start the Graduation process to a TLP The next release 2.2.0 is scheduled for January, this is likely to be a bug-fix release and will hopefully be our last release before graduation. New functionality and enhancements has currently been suspended in favour of bug-fixes and the work towards graduation. The following rough road map has been provisionally agreed * Graduation as top level project river.apache.org * Rename com.sun namespace to org.apache.river * Modular build & JDK policy After this has been completed then the previous work on new functionality and enhancements will be picked up again. These will include; * Dynamic Grants at Runtime, based on CodeSource, Code Signer Certificate chains , ProtectionDomain or ClassLoader * Dynamic Revoke of Grant's at Runtime * Securing proxy downloads and unmarshalling Additionally work is continuing on the build and test environments. The project has recently been able to run all the categories of the QA tests which is a significant accomplishment, but it does make for a rather long test sequence. They have highlighted several bugs which have been fixed. More of the JTREG tests are also passing after fixes to the environment and the tests themselves The website has been moved to the new Apache CMS environment and has seen further increases in the level of documentation available, particular articles which are useful to people starting to use and develop River 3 most important issues: * List future River PMC members and select the initial PMC chair * Prepare the TLP graduation resolution * Vote on graduation = Stanbol = Stanbol is a modular software stack and reusable set of components for semantic content management. Stanbol just entered incubation, on 2010-11-15. Mailing lists, SVN and JIRA are ready, most user accounts created, pre-existing code from the IKS project has been imported under a code grant. The Stanbol community has been invited to participate in a free workshop organized by the IKS project (*). It is a good opportunity to establish best practices for collaboration and communication between IKS (an EU-funded research project in which most current Stanbol committers are involved, http://iks-project.eu/) and the Stanbol podling. Branding requirements checked, see https://issues.apache.org/jira/browse/STANBOL-14 Next steps: * Cleanup dependencies and code as per ASF requirements * Make an initial release * Start establishing and growing the community (*) Workshop URL: http://wiki.iks-project.eu/index.php/Workshops/EAworkshopAmsterdam --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
