On Tue, May 18, 2010 at 12:15 AM, Noel J. Bergman <n...@devtech.com> wrote: > *** Clerezza had been accidentally deleted during a wiki edit...
Still broken below and in board_agenda_2010_05_19.txt, Bluesky and Clerezza reports are broken, here's the correct section, also fixed in http://wiki.apache.org/incubator/May2010 : ******** = 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. We are still waiting for Bill to check the completeness of the release candidate. Things we've done recently: Coding to optimize DTU structure, still under going; Testing IPv6 and satellite module; One thing left to the first release: cast release vote in general list. = Clerezza = Clerezza (incubating since November 27th, 2009) is an OSGi-based modular application and set of components (bundles) for building RESTFul Semantic Web applications and services. The are currently no issues requiring board attention. Recent activity: Updated to the latest Felix framework (including security features) Improved typerendering with regex-pattern and renderlets for literal types Update to TDB 0.8.5 Presented Clerezza at the Apache Retreat Manuel Innerhofer participated in the IKS FISE hackathon (http://wiki.iks-project.eu/index.php/FISE), Clerezza modules are used in FISE. Next steps: Enhance UIMA integration Integration with Tika Top 2/3 Issues before graduation: Improve our website with tutorials and "getting started" content. Prepare some easy-to-run demos to get people interested in Clerezza. Prepare for a first release ******** > *** A HISE report was entered to indicate that the project had failed to > report. > *** No other changes from the original submission > > During the past month, the Incubator has added a fair number of new PMC > Members: > > Chris Mattmann > David Jencks > Gurkan Erdogdu > Tom White > Jean-Frederic Clere > Julien Vermillard > Christian Grobmeier (elected) > Donald Woods > > All of them joined with the specific intent of mentoring projects, of which > we have quite a few (reflected by all of the new PMC members). Proposed > projects included Whirr (libraries for running cloud services), Zeta (PHP > components), Amber (OAuth Java library), and Deltacloud (web service API for > cloud service clients/providers). > > WSRP4J was terminated at the mutual decision with the Portals PMC. > > ------------------------------------------------------------------- > > = BeanValidation = > Apache Bean Validation will deliver an implementation of the JSR303 Bean > Validation 1.0 specification. BVAL entered incubation on March 1, 2010. > > A list of the three most important issues to address in the move towards > graduation: > > First release of artifacts. Grow the community and committer base. > > Any issues that the Incubator PMC or ASF Board might wish/need to be aware > of: > > None at this time. > > How has the community developed since the last report: > > The community has been focused on resolving TCK failures, with lots of help > coming from contributor Carlos Vara. Apache OpenJPA trunk is now using our > artifacts as their default provider for Bean Validation testing. Two other > projects (one at the ASF) have mentioned they are using our artifacts > instead of Hibernate. > > How has the project developed since the last report: > > Confluence is setup as our website and has been fully populated. SNAPSHOT > artifacts are being published to repository.apache.org. TCK testing is being > run by 3 or 4 committers and contributors. > > > = 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. > > We are still waiting for Bill to check the completeness of the release > candidate. Things we've done recently: > > * Coding to optimize DTU structure, still under going; > * Testing IPv6 and satellite module; > > One thing left to the first release: > > * cast release vote in general list. > > * Improved typerendering with regex-pattern and renderlets for literal > types > * Update to TDB 0.8.5 > * Presented Clerezza at the Apache Retreat > * Manuel Innerhofer participated in the IKS FISE hackathon > (http://wiki.iks-project.eu/index.php/FISE), Clerezza modules are used in > FISE. > > Next steps: > > * Enhance UIMA integration > * Integration with Tika > > Top 2/3 Issues before graduation: > > * Improve our website with tutorials and "getting started" content. > * Prepare some easy-to-run demos to get people interested in Clerezza. > * Prepare for a first release > > > = Droids = > > Droids is an Incubator project arrived from Apache Labs. Droids entered > incubation on October, 2008. > > It's an intelligent standalone robot framework that allows one to create and > extend existing web robots. > > What we've completed in the last months: > > * new elected committers: Bertil Chapuis and Richard Frovarp; > * the community has organized a community day to fix nearly all open > tickets with patch > * release preparation are under going > > Issues before graduation : > > * Do a release > * IP clearance > > > = Clerezza = > > Clerezza (incubating since November 27th, 2009) is an OSGi-based modular > application and set of components (bundles) for building RESTFul Semantic > Web applications and services. The are currently no issues requiring board > attention. > > Recent activity: > > * Updated to the latest Felix framework (including security features) > * Improved typerendering with regex-pattern and renderlets for literal > types > * Update to TDB 0.8.5 > * Presented Clerezza at the Apache Retreat > * Manuel Innerhofer participated in the IKS FISE hackathon > (http://wiki.iks-project.eu/index.php/FISE), Clerezza modules are used in > FISE. > > Next steps: > > * Enhance UIMA integration > * Integration with Tika > > Top 2/3 Issues before graduation: > > * Improve our website with tutorials and "getting started" content. > * Prepare some easy-to-run demos to get people interested in Clerezza. > * Prepare for a first release > > > = HISE = > > The goal of HISE is to provide support for the WS-Human-Task 1.0 > Specification. HISE started Incubation in November 2009. > > HISE did not file a report. Checking the mailing lists shows that there > have been 5 messages in the past 2 1/2 months, a marked drop off from the > first quarter of 2010. Likewise there has been a single commit since the > end of March. The project will be pinged to find out what is going on > there. > > > = Libcloud = > > Libcloud is a unified interface into various cloud service providers, > written in python. Libcloud joined the Incubator on November 3rd, 2009. > > We're on the cusp of pushing 0.3.2 out the door, with our last release 0.3.1 > on 10 May 2010. > > Over the past few months we have: > > * Added driver support for new providers: Dreamhost, Eucalyptus, Enomaly > ECP, IBM Developer Cloud, and !SoftLayer > * Improved multi-threaded handling in Rackspace and !RimuHosting > * Created deployment and bootstrap API > * Expanded test coverage > * Augment documentation > > We look forward to further improving documentation and lowering the barrier > to entry with tutorials and a guide for writing drivers. We will continue > to add providers and keep the library updated with providers' changes. > > > = 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. End-user documentation conversion to usable form needs to be completed; > this is probably the biggest obstacle to developing a broader community at > this point 1. Javadoc and nightly builds need to be set up 1. The first > official release needs to be planned and 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? > > There's been a significant amount of discussion pertaining to the LCF > document security model, it's advantages and disadvantages. Offers of > assistance and advice abound. A non-Apache code submission has even been > made. > > How has the project developed since the last report? > > Preliminary security integration with Solr has been tackled. Online > end-user documentation is coming along and is perhaps 60% complete. Scripts > have been written to make using LCF easier for the less experienced > integrator. > > > = OODT = > > Description: > > OODT is a grid middleware framework for science data processing, > information integration, and retrieval. OODT is used on a number of > successful projects at Jet Propulsion Laboratory/ California Institute of > Technology (http://jpl.nasa.gov/, and many other research institutions and > universities. > > A list of the three most important issues to address in the move towards > graduation: > > 1. Port OODT code and license headers into ASF license headers > 1. OODT contributions from at least 2 other organizations besides JPL > 1. At least one OODT incubating release, hopefully in the first few months > > 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? > > Chris Mattmann mentioned OODT as a possible extension for Whirr, proposed by > Tom White in the Incubator. We had some input from Justin > (http://www.mail-archive.com/oodt-...@incubator.apache.org/msg00050.html) > progressing on OODT-3 (http://issues.apache.org/jira/browse/OODT-3), and > leveraging tools like RAT to do the license checking and verification needed > to close out the issue. Much of the other activity continues to be from the > mentors and committers. > > How has the project developed since the last report? > > OODT was voted into the Incubator by the IPMC]] on January 22, 2010. > > Development over the last month has centered > on[[https://issues.apache.org/jira/browse/OODT-3|OODT-3]] (cleaning up the > OODT code and config license headers), with contributions from Sean > !McCleese, and on[[https://issues.apache.org/jira/browse/OODT-15|OODT-15]] > (one top-level build for OODT, and one trunk, tags and > branches).[[https://issues.apache.org/jira/browse/OODT-15|OODT-15]] in > particular included some community discussion and a lazy consensus to move > forward. Chris Mattmann is nearly complete on this reorganization, which, > coupled with[[https://issues.apache.org/jira/browse/OODT-3|OODT-3]] should > provide for a great 1st incubating release along with some documentation > transfering and getting the website up and running > (https://issues.apache.org/jira/browse/OODT-16), which Sean Kelly has > volunteered to spearhead. > > > > = PhotArk = > > Apache PhotArk will be a complete open source photo gallery application > including a content repository for the images, a display piece, an access > control layer, and upload capabilities. > > * PhotArk was accepted for Incubation on August 19, 2008. > * Issues before graduation : > * PhotArk started as a project with no initial code-base, and we have > grown the community to the minimal 3 independent committer size required for > graduation and have been seeing slow but continuous interest in the project. > We might be soon in a position to discuss graduation if others don't see an > independent, active but small community as an issue. > > * Suhothayan Sriskandaraj has been voted as Committer for Apache PhotArk > * The PhotArk community continues to make good progress code wise > * Three project ideas has been accepted for GSoC 2010 program > * PhotArk M2 release is under review. > > > > = SIS = > > SIS was voted into the Incubator by the IPMC on February 21, 2010. > > Apache SIS is a toolkit that spatial information system builders or users > can use to build applications containing location context. This project > will look to store reference implementations of spatial algorithms, > utilities, services, etc. as well as serve as a sandbox to explore new > ideas. Further, the goal is to have Apache SIS grow into a thriving Apache > top-level community, where a host of SIS/GIS related software (OGC > datastores, REST-ful interfaces, data standards, etc.) can grow from and > thrive under the Apache umbrella. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware > of? > > Not at this time > > Community progress since the last report: > > Chris Mattmann, Patrick O'Leary and Kevan Miller participated in a meeting > with ESRI (http://www.esri.com) who may be interested in participating > within the project within some capacity. This would be a huge win as ESRI is > one of the major industry leaders in the development of GIS software, with > connections to standards bodies including the Open Geospatial Consortium > (OGC). Much of the other activity continues to be from the mentors and > committers. > > Project progress since last report > > Chris Mattmann is working on refactoring the LocalLucene code into the SIS > codebase and work continues on creating the SIS incubator website, with Sean > McCleese leading the charge. Patrick O'Leary is investigating map > projections and coordinate systems including transformations to Polar > coordinates which should help on the observational data side. > > > > = Stonehenge = > > Stonehenge has been incubating since December 2008. Stonehenge is a set of > example applications for Service Oriented Architecture that spans languages > and platforms and demonstrates best practices and interoperability by using > currently defined W3C OASIS standard protocols. > > Since the last report in February 2010, the Stonehenge project has > intensified its efforts around interop testing between the M2 implementation > of the claims-based security model extension to the Stock Trader > implementations. Testing between .NET, Axis2/Java and Metro/Glassfish > implementations have uncovered various bugs and were subsequently corrected > in the web services library and the application code. > > Milestone 2 (M2) > > M2 constituted of expanding the Stocktrader application to use claims-based > authentication using an active and a passive STS for each implementation. We > also upgraded the usage of the WS-* specs from the submitted versions to the > ratified one. Extensive documentation work was done in parallel to describe > the new feature set and simplify the installation and configuration process. > > In our last report we were preparing to vote for M2, unfortunately the > testing efforts are still underway and we continue to find issues that we > hope to resolve in the near future. We are currently investigating which if > any products or implementations are holding us up from releasing and > addressing them in an effort to release a stable version to our users. > > Milestone 3 (M3) > > A proposal has been sumbitted for creating "micro samples" for many common > WS-* scenarios, with the goal being around creating implementations with low > barriers to entry. The proposal can be found at > https://issues.apache.org/jira/browse/STONEHENGE-121. The community is > anxiously awaiting the release of M2 so that we can get started on this > project with hopes that releases can be made on a more frequent basis. > > Graduation Map: > > * Grow community around new claims based stocktrader implementations just > added > * More thorough documentation that empowers developers to replicate > interoperability scenarios demonstrated > * Demonstrate full interoperability between existing components, and > release > > > = Thrift = > > Thrift has been discussing what is required for it to move forwards - most > notably in relation to releases. While many developers work off their own > branches, and therefore do not require or need formal releases, they do > accept the need for releases. As a way to encourage releasing, a proposal > was made to have a release manager. As a result of this suggestion, Bryan > Duxbury was voted in as the Thrift release manager, and is intending to take > on regular releases. > > One-off report from Upayavira > > > = VCL = > > VCL has been incubating since December 2008. VCL is a cloud computing > platform for the management of physical and virtual machines. > > Community Involvement: > > * As stated in the previous report, the Apache VCL community continues to > grow. We're seeing more and more people start to contribute to our online > documentation and file JIRA issues. > * A few people from the community have been contacted by PPMC members > encouraging them to become more involved in the project. > * We continue to see people from new locations asking questions on the > vcl-dev list which shows that interest in VCL is continuing to grow. > * Interest from the community to have support for a more recent version of > VMWare Free Server drove the decision to swap that feature (originally > slated for VCL 2.3) with cluster reservation improvements (originally > slated for VCL 2.2). > > Plans for next Release: > > * We hope to have our next release out by the end of June. This would be > 1/2 the time it took to get our previous release out. We hope to continue > to shorten the time between releases as we move forward. > > Documentation: > > * Migration of official documentation to our second Confluence space has > started. The next step is to pick an autoexport template, and then set up a > cronjob to copy the autoexported content to our official documentation > location. > > Top Issues Before Graduation: > > * Continue to increase contributors from multiple institutions > > > = Wink = > > Apache Wink is a project that enables development and consumption of REST > style web services. The core server runtime is based on the JAX-RS (JSR 311) > standard. The project also introduces a client runtime which can leverage > certain components of the server-side runtime. Apache Wink will deliver > component technology that can be easily integrated into a variety of > environments. > > Apache Wink has been incubating since 2009-05-27. > > Notable Activity: > > * In the middle of a Wink 1.1 release. A few license issues were resolved > in the incubator regarding dual licensing. More bug fixes and JAX-RS 1.1 > changes for the non-Java EE 6 integration pieces were added. > > * Did some initial OSGi work. Looking for feedback here to see where to > expand. > > * Some work done to improve the syndication models. > > Planned Activity: > > * Continue the release > > Top issues before graduation: > > * Build community > > > = Wookie = > > No issues currently require IPMC or Board attention > > Notable activities: > > * Voted raido in as a committer > * Core W3C Widget parser has been split off into a standalone library for > use in other applications > * Implemented a connector framework to support developers building plugins > to add Wookie support to their applications. Versions created for Java, C#, > Python and PHP > * Implemented the W3C Widgets Access Request Policy candidate > recommendation: see http://www.w3.org/TR/widgets-access/ > * Work progressing on implementing the W3C Widget Updates draft > specification: see http://www.w3.org/TR/widgets-updates/ > * JIRA Activity continues to grow > * Interest from Android community in porting the Wookie parser library > * Fixed Shindig integration > > Items to be resolved before graduation: > > * Remove GPL dependencies > * Create a release > * Develop community > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.819 / Virus Database: 271.1.1/2871 - Release Date: 05/17/10 > 02:26:00 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
