You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2010/06/14 19:22:20 UTC
Incubator Board Report June 2010
Felix Meschberger resigned as a Mentor for Chemistry. Jean Anderston was
removed (emeritus) from the Incubator PMC at her request. The PMC and Chair
thank them both for their service to the Incubator and the ASF.
On that same note, I'd like to thank Sebastian Bazley, Joe Schaefer, and
others for their continued efforts in striving for data and other
consistency within the Incubator and across the ASF.
Nuvem, a cross-clould API, has been proposed to the Incubator.
BlueSky's "lost" report from last month is included this month. The project
has had essentially no mailing list activity for two months, and no commits
since January. Both Lucene Connector Framework and River failed to report.
They have been active, are aware of, and apologize for, missing the report,
and plan to provide one next month.
Lucene Connector Framework just reported IP Clearence in late May.
-------------------
= Amber =
Amber is a project to develop a Java library which provides an API
specification for, and an unconditionally compliant implementation of the
OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows
users to authenticate and authorise access by another party to resources
they control while avoiding the need to share their username and password
credentials.
The most important issues that must be addressed before graduation are: 1.
One 2. Two 3. Three
The Incubator PMC / ASF Board should be aware that:
The community is in the first stages of formation and solely consists of the
developers.
The project has begun with the contribution of code from the initial
developers.
= Aries =
Aries will deliver a set of pluggable Java components enabling an enterprise
OSGi application programming model.
Aries entered incubation on September 22, 2009.
There are currently no issues requiring IPMC or Board attention.
The following sub-components are actively being developed:
* Application
* Subsystems
* Blueprint
* JMX
* JPA
Several new sample applications have been developed to demonstrate the Aries
functionality.
There continues to be a vibrant community as shown by the activity on the
mailing list this year.
On May 26th we released Apache Aries 0.1-incubating, our first release.
Top 2 or 3 things to resolve before graduation:
* Build community [done]
* Create a release [done]
* Address project scope concerns raised during acceptance vote
= 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
* Committer offer was extended and accepted by Carlos Vara.
* Apache Geronimo has started using our artifacts in their 3.0 builds for
Java EE 6.
* Apache OpenJPA has started creating a image-gallery sample that shows how
JPA2 and our Bean Validation implementation can be used together.
How has the project developed since the last report
* Rsync of Confluence content to our website is now setup.
* Code has been passing the Bean Validation TCK since May 21.
* We completed our first release on June 11, 2010, which was released as
0.1-incubating.
= Bluesky =
Originally posted for May, but somehow lost during Wiki edits.
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.
= Deltacloud =
Deltacloud defines a web service API for interacting with cloud service
providers and resources in those clouds in a unified manner. In addition,
it consists of a number of implementations of this API for the most popular
clouds.
Deltacloud entered the incubator in 2010-05-17.
Currently gathering initial contributors CLAs and working on setting up
project infrastructure.
= 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
* Finally got our new UI up and running which is the foundation of next
release
* Users from various enterprises are using ESME in test installations
* Received some patches from a new contributor in the last few weeks.
The following items are planned for the next reporting period:
* Next release based on UI code
* Other types of authentication
* Integrate Stax deployment in daily Hudson builds (more difficult than
expected)
Top 2 or 3 things to resolve prior to graduation
* Increase community involvement in the project
* Multiple Apache releases
= 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.
This last reporting period saw little activity (0 commits, 0 releases).
We're finding it hard to regain our momentum after the dissolution of our
team. James and Scott are using etch in their current projects, and Youngjin
would like to pick up the c-binding. What we lack is the organizational
energy to get things moving.
Holger Grandy and Michael Fitzner have submitted a c-binding for us to
examine. Youngjin is going to be looking at it. I've been shaking down the
etch 1.1 release candidate in my current project, and as soon as I can get
my head out I plan to fix the final administrative issues of the 1.1 release
and try to kick it out the door.
We recently voted to accept Holger Grandy and Michael Fitzner as committers
and ppmc members. They have submitted an Etch C Binding.
Release 1.1 is ready but needs some administrative polish before it is
*done*.
Release 1.2 is next in the pipeline.
Our continuous integration build problem will only be solved by one of us
hosting it at our new gigs. James and Scott are looking into this.
[GavinMcDonald adds: I'm looking into adding Etch to CI stuff at ASF]
Outstanding items:
More community.. we have been Cisco-centered with just a few nibbles outside
of Cisco. Things are definitely changing with members employed or so to be
employed in different places. Building a stronger community remains our key
task. We wish we knew how.
= Hama =
Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
scientific package on Hadoop for massive matrix and graph data.
We're trying to implement the M/R alternative, a new computation framework
for matrix/graphs based on BSP. We are doing this because the Hadoop M/R
model isn't suitable for the complex numerical/relational data processing
since it requires heavy communications among computing nodes.
Recently we made a progress in the design of the overall architecture, and
the development of the BSP cluster with programming interfaces. And, HAMA
project has drawn many interests from Hadoopers.
We are now focusing on the very first release of Hama to graduate from
incubator.
= 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:
* 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 =
*** Did not report.
= OODT =
OODT is a grid middleware framework for science data processing,
information integration, and retrieval. OODT is used on a number of
successful projects at NASA's Jet Propulsion Laboratory/California
Institute of Technology, 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?
Either Justin Erenkrantz or David Woollard will be giving a talk at the
TransferSummit 2010]] in Oxford, UK on Friday, June 25, 2010 - 3:50pm -
4:30pm on NASA and Apache. The talk will cover OODT in detail and the
transition of the first NASA project into the ASF Incubator and the
experience along the way. After some discussion with Justin, Chris added
himself as a mentor for the project on the OODT Proposal on the Incubator
wiki, since he is an ASF member and Incubator PMC member. 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 continues to focus on cleaning up the OODT code and config
license headers, with contributions from Andrew Hart and Sean McCleese, and
on one top-level build for OODT, and one trunk, tags and branches) with
contributions from Chris Mattmann. When OODT-15 and OODT-3 are finished, we
should be ready for 1st incubating release along with some documentation
transfering and getting the website up and running, tracked in
https://issues.apache.org/jira/browse/OODT-16, and assigned to Sean Kelly.
= RAT =
No IPMC or Board issues requring attention.
Both the Ant task (RAT-73) and Maven plugin (RAT-74) have been extended to
optionally create reports in RAT's XML format rather than plain text. This
will not only allow custom styling of the reports but also easy report
federations like the one currently created by BuildBot.
Discussion for a new release of RAT to make this feature available has
started but hasn't come to a conclusion, yet.
= River =
*** DID NOT REPORT
= SIS =
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:
Mailing list activity has been pretty bare, but should pick up since the
SIS'ers need to follow up after the meeting with ESRI last month to
determine if they are interested with participating in the community. Much
of the other activity continues to be from the mentors and committers.
Project progress since last report:
SIS was voted into the Incubator by the IPMC on February 21, 2010.
Development has slowed, but the intentions from last month still stand.
Chris Mattmann still needs to work on refactoring the LocalLucene code into
the SIS codebase and Sean McCleese needs to finish creating the SIS
incubator website. Patrick O'Leary is investigating map projections and
coordinate systems including transformations to Polar coordinates which
should help on the observational data side.
= Whirr =
Whirr provides code for running a variety of software services on cloud
infrastructure.
Whirr was accepted into the incubator on 11 May 2010. Status information is
available at http://incubator.apache.org/projects/whirr.html.
Progress since entry into the incubator:
All the initial Incubator infrastructure items are now complete. The code
hosted in the Hadoop contrib area has been moved to Whirr's subversion tree.
Associated JIRAs have been moved to Whirr's JIRA.
Plans for the next period:
* Import the Whirr Java source
Top three items to resolve before graduation:
* Increase community involvement in the project
* Make several incubating releases
* Support at least three services on Whirr
Any Issues that the Incubator PMC (IPMC) or ASF Board need to be aware of?
None at this time.
= Zeta Components =
Zeta Components is a high-quality library of loosely-coupled PHP components.
It has entered incubation on 2010-05-21. Therefore the project is still in
ramp up phase.
3 most important issues to be tackled:
* Create initial incubating infrastructure.
* Move project and community to ASF.
* Get developement based in ASF moving again.
Mailing lists have already been created. Available are:
* dev zeta-dev@incubator.apache.org
* user zeta-commits@incubator.apache.org
* commits zeta-users@incubator.apache.org
* private zeta-private@incubator.apache.org
Website space has been reserved. Jira has been requested. All CLAs have been
sent. Most of them have been processed and therefore most user accounts have
been requested.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Incubator Board Report June 2010
Posted by jean-frederic clere <jf...@gmail.com>.
On 06/14/2010 07:22 PM, Noel J. Bergman wrote:
> The most important issues that must be addressed before graduation are: 1.
> One 2. Two 3. Three
We should have removed that sentence I think.
Cheers
Jean-Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Incubator Board Report June 2010
Posted by Grant Ingersoll <gs...@apache.org>.
Sorry for the delay, I was traveling. I have updated the agenda as well.
Here is the Lucene Connector Framework section:
= 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
1. The first official release needs to be planned and executed
1. 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.
1. 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.
On Jun 14, 2010, at 1:22 PM, Noel J. Bergman wrote:
> Felix Meschberger resigned as a Mentor for Chemistry. Jean Anderston was
> removed (emeritus) from the Incubator PMC at her request. The PMC and Chair
> thank them both for their service to the Incubator and the ASF.
>
> On that same note, I'd like to thank Sebastian Bazley, Joe Schaefer, and
> others for their continued efforts in striving for data and other
> consistency within the Incubator and across the ASF.
>
> Nuvem, a cross-clould API, has been proposed to the Incubator.
>
> BlueSky's "lost" report from last month is included this month. The project
> has had essentially no mailing list activity for two months, and no commits
> since January. Both Lucene Connector Framework and River failed to report.
> They have been active, are aware of, and apologize for, missing the report,
> and plan to provide one next month.
>
> Lucene Connector Framework just reported IP Clearence in late May.
>
> -------------------
>
> = Amber =
>
> Amber is a project to develop a Java library which provides an API
> specification for, and an unconditionally compliant implementation of the
> OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows
> users to authenticate and authorise access by another party to resources
> they control while avoiding the need to share their username and password
> credentials.
>
> The most important issues that must be addressed before graduation are: 1.
> One 2. Two 3. Three
>
> The Incubator PMC / ASF Board should be aware that:
>
> The community is in the first stages of formation and solely consists of the
> developers.
>
> The project has begun with the contribution of code from the initial
> developers.
>
>
> = Aries =
>
> Aries will deliver a set of pluggable Java components enabling an enterprise
> OSGi application programming model.
>
> Aries entered incubation on September 22, 2009.
>
> There are currently no issues requiring IPMC or Board attention.
>
> The following sub-components are actively being developed:
>
> * Application
> * Subsystems
> * Blueprint
> * JMX
> * JPA
>
> Several new sample applications have been developed to demonstrate the Aries
> functionality.
>
> There continues to be a vibrant community as shown by the activity on the
> mailing list this year.
>
> On May 26th we released Apache Aries 0.1-incubating, our first release.
>
> Top 2 or 3 things to resolve before graduation:
>
> * Build community [done]
> * Create a release [done]
> * Address project scope concerns raised during acceptance vote
>
>
> = 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
> * Committer offer was extended and accepted by Carlos Vara.
> * Apache Geronimo has started using our artifacts in their 3.0 builds for
> Java EE 6.
> * Apache OpenJPA has started creating a image-gallery sample that shows how
> JPA2 and our Bean Validation implementation can be used together.
>
> How has the project developed since the last report
> * Rsync of Confluence content to our website is now setup.
> * Code has been passing the Bean Validation TCK since May 21.
> * We completed our first release on June 11, 2010, which was released as
> 0.1-incubating.
>
>
> = Bluesky =
>
> Originally posted for May, but somehow lost during Wiki edits.
>
> 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.
>
>
> = Deltacloud =
>
> Deltacloud defines a web service API for interacting with cloud service
> providers and resources in those clouds in a unified manner. In addition,
> it consists of a number of implementations of this API for the most popular
> clouds.
>
> Deltacloud entered the incubator in 2010-05-17.
>
> Currently gathering initial contributors CLAs and working on setting up
> project infrastructure.
>
>
> = 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
>
> * Finally got our new UI up and running which is the foundation of next
> release
> * Users from various enterprises are using ESME in test installations
> * Received some patches from a new contributor in the last few weeks.
>
> The following items are planned for the next reporting period:
>
> * Next release based on UI code
> * Other types of authentication
> * Integrate Stax deployment in daily Hudson builds (more difficult than
> expected)
>
> Top 2 or 3 things to resolve prior to graduation
>
> * Increase community involvement in the project
> * Multiple Apache releases
>
>
> = 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.
>
> This last reporting period saw little activity (0 commits, 0 releases).
> We're finding it hard to regain our momentum after the dissolution of our
> team. James and Scott are using etch in their current projects, and Youngjin
> would like to pick up the c-binding. What we lack is the organizational
> energy to get things moving.
>
> Holger Grandy and Michael Fitzner have submitted a c-binding for us to
> examine. Youngjin is going to be looking at it. I've been shaking down the
> etch 1.1 release candidate in my current project, and as soon as I can get
> my head out I plan to fix the final administrative issues of the 1.1 release
> and try to kick it out the door.
>
> We recently voted to accept Holger Grandy and Michael Fitzner as committers
> and ppmc members. They have submitted an Etch C Binding.
>
> Release 1.1 is ready but needs some administrative polish before it is
> *done*.
>
> Release 1.2 is next in the pipeline.
>
> Our continuous integration build problem will only be solved by one of us
> hosting it at our new gigs. James and Scott are looking into this.
> [GavinMcDonald adds: I'm looking into adding Etch to CI stuff at ASF]
>
> Outstanding items:
>
> More community.. we have been Cisco-centered with just a few nibbles outside
> of Cisco. Things are definitely changing with members employed or so to be
> employed in different places. Building a stronger community remains our key
> task. We wish we knew how.
>
>
> = Hama =
>
> Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
> scientific package on Hadoop for massive matrix and graph data.
>
> We're trying to implement the M/R alternative, a new computation framework
> for matrix/graphs based on BSP. We are doing this because the Hadoop M/R
> model isn't suitable for the complex numerical/relational data processing
> since it requires heavy communications among computing nodes.
>
> Recently we made a progress in the design of the overall architecture, and
> the development of the BSP cluster with programming interfaces. And, HAMA
> project has drawn many interests from Hadoopers.
>
> We are now focusing on the very first release of Hama to graduate from
> incubator.
>
>
> = 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:
>
> * 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 =
>
>
> *** Did not report.
>
>
> = OODT =
>
> OODT is a grid middleware framework for science data processing,
> information integration, and retrieval. OODT is used on a number of
> successful projects at NASA's Jet Propulsion Laboratory/California
> Institute of Technology, 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?
>
> Either Justin Erenkrantz or David Woollard will be giving a talk at the
> TransferSummit 2010]] in Oxford, UK on Friday, June 25, 2010 - 3:50pm -
> 4:30pm on NASA and Apache. The talk will cover OODT in detail and the
> transition of the first NASA project into the ASF Incubator and the
> experience along the way. After some discussion with Justin, Chris added
> himself as a mentor for the project on the OODT Proposal on the Incubator
> wiki, since he is an ASF member and Incubator PMC member. 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 continues to focus on cleaning up the OODT code and config
> license headers, with contributions from Andrew Hart and Sean McCleese, and
> on one top-level build for OODT, and one trunk, tags and branches) with
> contributions from Chris Mattmann. When OODT-15 and OODT-3 are finished, we
> should be ready for 1st incubating release along with some documentation
> transfering and getting the website up and running, tracked in
> https://issues.apache.org/jira/browse/OODT-16, and assigned to Sean Kelly.
>
>
> = RAT =
>
> No IPMC or Board issues requring attention.
>
> Both the Ant task (RAT-73) and Maven plugin (RAT-74) have been extended to
> optionally create reports in RAT's XML format rather than plain text. This
> will not only allow custom styling of the reports but also easy report
> federations like the one currently created by BuildBot.
>
> Discussion for a new release of RAT to make this feature available has
> started but hasn't come to a conclusion, yet.
>
>
> = River =
>
> *** DID NOT REPORT
>
>
> = SIS =
>
> 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:
>
> Mailing list activity has been pretty bare, but should pick up since the
> SIS'ers need to follow up after the meeting with ESRI last month to
> determine if they are interested with participating in the community. Much
> of the other activity continues to be from the mentors and committers.
>
> Project progress since last report:
> SIS was voted into the Incubator by the IPMC on February 21, 2010.
>
> Development has slowed, but the intentions from last month still stand.
> Chris Mattmann still needs to work on refactoring the LocalLucene code into
> the SIS codebase and Sean McCleese needs to finish creating the SIS
> incubator website. Patrick O'Leary is investigating map projections and
> coordinate systems including transformations to Polar coordinates which
> should help on the observational data side.
>
>
> = Whirr =
>
> Whirr provides code for running a variety of software services on cloud
> infrastructure.
>
> Whirr was accepted into the incubator on 11 May 2010. Status information is
> available at http://incubator.apache.org/projects/whirr.html.
>
> Progress since entry into the incubator:
>
> All the initial Incubator infrastructure items are now complete. The code
> hosted in the Hadoop contrib area has been moved to Whirr's subversion tree.
> Associated JIRAs have been moved to Whirr's JIRA.
>
> Plans for the next period:
> * Import the Whirr Java source
>
> Top three items to resolve before graduation:
> * Increase community involvement in the project
> * Make several incubating releases
> * Support at least three services on Whirr
>
> Any Issues that the Incubator PMC (IPMC) or ASF Board need to be aware of?
>
> None at this time.
>
>
> = Zeta Components =
>
> Zeta Components is a high-quality library of loosely-coupled PHP components.
> It has entered incubation on 2010-05-21. Therefore the project is still in
> ramp up phase.
>
> 3 most important issues to be tackled:
>
> * Create initial incubating infrastructure.
> * Move project and community to ASF.
> * Get developement based in ASF moving again.
>
> Mailing lists have already been created. Available are:
>
> * dev zeta-dev@incubator.apache.org
> * user zeta-commits@incubator.apache.org
> * commits zeta-users@incubator.apache.org
> * private zeta-private@incubator.apache.org
>
> Website space has been reserved. Jira has been requested. All CLAs have been
> sent. Most of them have been processed and therefore most user accounts have
> been requested.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem using Solr/Lucene: http://www.lucidimagination.com/search
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Incubator Board Report June 2010
Posted by Grant Ingersoll <gs...@apache.org>.
Sorry for the delay, I was traveling. I have updated the agenda as well.
Here is the Lucene Connector Framework section:
= 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
1. The first official release needs to be planned and executed
1. 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.
1. 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.
On Jun 14, 2010, at 1:22 PM, Noel J. Bergman wrote:
> Felix Meschberger resigned as a Mentor for Chemistry. Jean Anderston was
> removed (emeritus) from the Incubator PMC at her request. The PMC and Chair
> thank them both for their service to the Incubator and the ASF.
>
> On that same note, I'd like to thank Sebastian Bazley, Joe Schaefer, and
> others for their continued efforts in striving for data and other
> consistency within the Incubator and across the ASF.
>
> Nuvem, a cross-clould API, has been proposed to the Incubator.
>
> BlueSky's "lost" report from last month is included this month. The project
> has had essentially no mailing list activity for two months, and no commits
> since January. Both Lucene Connector Framework and River failed to report.
> They have been active, are aware of, and apologize for, missing the report,
> and plan to provide one next month.
>
> Lucene Connector Framework just reported IP Clearence in late May.
>
> -------------------
>
> = Amber =
>
> Amber is a project to develop a Java library which provides an API
> specification for, and an unconditionally compliant implementation of the
> OAuth v1.0, v1.0a and v2.0 specifications. OAuth is a mechanism that allows
> users to authenticate and authorise access by another party to resources
> they control while avoiding the need to share their username and password
> credentials.
>
> The most important issues that must be addressed before graduation are: 1.
> One 2. Two 3. Three
>
> The Incubator PMC / ASF Board should be aware that:
>
> The community is in the first stages of formation and solely consists of the
> developers.
>
> The project has begun with the contribution of code from the initial
> developers.
>
>
> = Aries =
>
> Aries will deliver a set of pluggable Java components enabling an enterprise
> OSGi application programming model.
>
> Aries entered incubation on September 22, 2009.
>
> There are currently no issues requiring IPMC or Board attention.
>
> The following sub-components are actively being developed:
>
> * Application
> * Subsystems
> * Blueprint
> * JMX
> * JPA
>
> Several new sample applications have been developed to demonstrate the Aries
> functionality.
>
> There continues to be a vibrant community as shown by the activity on the
> mailing list this year.
>
> On May 26th we released Apache Aries 0.1-incubating, our first release.
>
> Top 2 or 3 things to resolve before graduation:
>
> * Build community [done]
> * Create a release [done]
> * Address project scope concerns raised during acceptance vote
>
>
> = 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
> * Committer offer was extended and accepted by Carlos Vara.
> * Apache Geronimo has started using our artifacts in their 3.0 builds for
> Java EE 6.
> * Apache OpenJPA has started creating a image-gallery sample that shows how
> JPA2 and our Bean Validation implementation can be used together.
>
> How has the project developed since the last report
> * Rsync of Confluence content to our website is now setup.
> * Code has been passing the Bean Validation TCK since May 21.
> * We completed our first release on June 11, 2010, which was released as
> 0.1-incubating.
>
>
> = Bluesky =
>
> Originally posted for May, but somehow lost during Wiki edits.
>
> 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.
>
>
> = Deltacloud =
>
> Deltacloud defines a web service API for interacting with cloud service
> providers and resources in those clouds in a unified manner. In addition,
> it consists of a number of implementations of this API for the most popular
> clouds.
>
> Deltacloud entered the incubator in 2010-05-17.
>
> Currently gathering initial contributors CLAs and working on setting up
> project infrastructure.
>
>
> = 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
>
> * Finally got our new UI up and running which is the foundation of next
> release
> * Users from various enterprises are using ESME in test installations
> * Received some patches from a new contributor in the last few weeks.
>
> The following items are planned for the next reporting period:
>
> * Next release based on UI code
> * Other types of authentication
> * Integrate Stax deployment in daily Hudson builds (more difficult than
> expected)
>
> Top 2 or 3 things to resolve prior to graduation
>
> * Increase community involvement in the project
> * Multiple Apache releases
>
>
> = 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.
>
> This last reporting period saw little activity (0 commits, 0 releases).
> We're finding it hard to regain our momentum after the dissolution of our
> team. James and Scott are using etch in their current projects, and Youngjin
> would like to pick up the c-binding. What we lack is the organizational
> energy to get things moving.
>
> Holger Grandy and Michael Fitzner have submitted a c-binding for us to
> examine. Youngjin is going to be looking at it. I've been shaking down the
> etch 1.1 release candidate in my current project, and as soon as I can get
> my head out I plan to fix the final administrative issues of the 1.1 release
> and try to kick it out the door.
>
> We recently voted to accept Holger Grandy and Michael Fitzner as committers
> and ppmc members. They have submitted an Etch C Binding.
>
> Release 1.1 is ready but needs some administrative polish before it is
> *done*.
>
> Release 1.2 is next in the pipeline.
>
> Our continuous integration build problem will only be solved by one of us
> hosting it at our new gigs. James and Scott are looking into this.
> [GavinMcDonald adds: I'm looking into adding Etch to CI stuff at ASF]
>
> Outstanding items:
>
> More community.. we have been Cisco-centered with just a few nibbles outside
> of Cisco. Things are definitely changing with members employed or so to be
> employed in different places. Building a stronger community remains our key
> task. We wish we knew how.
>
>
> = Hama =
>
> Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
> scientific package on Hadoop for massive matrix and graph data.
>
> We're trying to implement the M/R alternative, a new computation framework
> for matrix/graphs based on BSP. We are doing this because the Hadoop M/R
> model isn't suitable for the complex numerical/relational data processing
> since it requires heavy communications among computing nodes.
>
> Recently we made a progress in the design of the overall architecture, and
> the development of the BSP cluster with programming interfaces. And, HAMA
> project has drawn many interests from Hadoopers.
>
> We are now focusing on the very first release of Hama to graduate from
> incubator.
>
>
> = 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:
>
> * 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 =
>
>
> *** Did not report.
>
>
> = OODT =
>
> OODT is a grid middleware framework for science data processing,
> information integration, and retrieval. OODT is used on a number of
> successful projects at NASA's Jet Propulsion Laboratory/California
> Institute of Technology, 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?
>
> Either Justin Erenkrantz or David Woollard will be giving a talk at the
> TransferSummit 2010]] in Oxford, UK on Friday, June 25, 2010 - 3:50pm -
> 4:30pm on NASA and Apache. The talk will cover OODT in detail and the
> transition of the first NASA project into the ASF Incubator and the
> experience along the way. After some discussion with Justin, Chris added
> himself as a mentor for the project on the OODT Proposal on the Incubator
> wiki, since he is an ASF member and Incubator PMC member. 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 continues to focus on cleaning up the OODT code and config
> license headers, with contributions from Andrew Hart and Sean McCleese, and
> on one top-level build for OODT, and one trunk, tags and branches) with
> contributions from Chris Mattmann. When OODT-15 and OODT-3 are finished, we
> should be ready for 1st incubating release along with some documentation
> transfering and getting the website up and running, tracked in
> https://issues.apache.org/jira/browse/OODT-16, and assigned to Sean Kelly.
>
>
> = RAT =
>
> No IPMC or Board issues requring attention.
>
> Both the Ant task (RAT-73) and Maven plugin (RAT-74) have been extended to
> optionally create reports in RAT's XML format rather than plain text. This
> will not only allow custom styling of the reports but also easy report
> federations like the one currently created by BuildBot.
>
> Discussion for a new release of RAT to make this feature available has
> started but hasn't come to a conclusion, yet.
>
>
> = River =
>
> *** DID NOT REPORT
>
>
> = SIS =
>
> 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:
>
> Mailing list activity has been pretty bare, but should pick up since the
> SIS'ers need to follow up after the meeting with ESRI last month to
> determine if they are interested with participating in the community. Much
> of the other activity continues to be from the mentors and committers.
>
> Project progress since last report:
> SIS was voted into the Incubator by the IPMC on February 21, 2010.
>
> Development has slowed, but the intentions from last month still stand.
> Chris Mattmann still needs to work on refactoring the LocalLucene code into
> the SIS codebase and Sean McCleese needs to finish creating the SIS
> incubator website. Patrick O'Leary is investigating map projections and
> coordinate systems including transformations to Polar coordinates which
> should help on the observational data side.
>
>
> = Whirr =
>
> Whirr provides code for running a variety of software services on cloud
> infrastructure.
>
> Whirr was accepted into the incubator on 11 May 2010. Status information is
> available at http://incubator.apache.org/projects/whirr.html.
>
> Progress since entry into the incubator:
>
> All the initial Incubator infrastructure items are now complete. The code
> hosted in the Hadoop contrib area has been moved to Whirr's subversion tree.
> Associated JIRAs have been moved to Whirr's JIRA.
>
> Plans for the next period:
> * Import the Whirr Java source
>
> Top three items to resolve before graduation:
> * Increase community involvement in the project
> * Make several incubating releases
> * Support at least three services on Whirr
>
> Any Issues that the Incubator PMC (IPMC) or ASF Board need to be aware of?
>
> None at this time.
>
>
> = Zeta Components =
>
> Zeta Components is a high-quality library of loosely-coupled PHP components.
> It has entered incubation on 2010-05-21. Therefore the project is still in
> ramp up phase.
>
> 3 most important issues to be tackled:
>
> * Create initial incubating infrastructure.
> * Move project and community to ASF.
> * Get developement based in ASF moving again.
>
> Mailing lists have already been created. Available are:
>
> * dev zeta-dev@incubator.apache.org
> * user zeta-commits@incubator.apache.org
> * commits zeta-users@incubator.apache.org
> * private zeta-private@incubator.apache.org
>
> Website space has been reserved. Jira has been requested. All CLAs have been
> sent. Most of them have been processed and therefore most user accounts have
> been requested.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
--------------------------
Grant Ingersoll
http://www.lucidimagination.com/
Search the Lucene ecosystem using Solr/Lucene: http://www.lucidimagination.com/search