Differences between revisions 1 and 25 (spanning 24 versions)
Revision 1 as of 2007-02-02 00:39:39
Size: 2151
Editor: 72
Comment:
Revision 25 as of 2009-09-20 23:07:06
Size: 5916
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
=== ActiveMQ === === log4php ===
Line 8: Line 8:
Apache ActiveMQ is a messaging broker and client. iPMC Reviewers: wrowe, jukka, bdelacretaz, yoavs, jim

log4php incubation was restarted in July. Three new committers have been
added and a JIRA project has been set up for bug tracking. A maven 2
generated web site has been published to http://incubator.apache.org/log4php.
The source tree was reorganized and an initial pass at migration to PHP 5 was
committed in July, but there has been little recent activity (possibly due to
vacations) and no published development plan. In the next period, the
development team needs to establish development plan for an initial snapshot.

----
=== Sling ===

iPMC Reviewers: wrowe, bdelacretaz, yoavs, jim

Sling is a framework to develop content centric web applications based on the
idea of modularizing the rendering of HTTP resources. Sling entered incubation
on September 5th, 2007.

The Sling project has just started. The basic infrastructure (mailing lists,
subversion, issue tracker, web site) is mostly in place; the only things still
missing are one committer account and a wiki space. The software grant for
Sling has been received and the initial source code is now available in svn.

iPMC Comments:
  Looking forward to a big picture of how Sling will move itself through the
  process to graduation, but we don't expect that quite yet. [wrowe]

----
=== Sanselan ===

iPMC Reviewers: yoavs, jim

Sanselan is a pure-java image library for reading and writing a variety of image formats.

The Sanselan project has just started. Mailing lists, subversion and Jira are setup
and we're currently working on getting the remaining bits of the infrastructure
running like the website etc.
The CLAs for all initial committers have been recorded and accounts are pending. The
software grant for Sanselan has been received and the code base will be committed to
svn as soon as the accounts are created.

----
=== River ===

iPMC Reviewers: wrowe, bdelacretaz, yoavs, jim

River is aimed at the development and advancement of the Jini technology core
infrastructure. River entered incubation on Dec 26, 2006.

Jini technology is a service oriented architecture that defines a programming
model which both exploits and extends Java technology to enable the
construction of secure, distributed systems which are adaptive to change.

The last artifact, the QA framework, has been voted in and landed in SVN. An
automated build environment has been put in place and finally all outstanding
issues from the Sun issue tracking system have been manually migrated in a
large group effort to JIRA.

The River community agreed to do a first release to show the larger Jini
community it is serious in its efforts. It ain't a very ambitious release and
will be almost an equivalent of the last release done by Sun but includes the
ServiceUI code. This release also allows the River community to get acquainted
and find out about many of the ASF procedures. No transformation of the
{{{com.sun.jini}}} namespace to {{{org.apache.river}}} will take place, but
the River community is aware it has to do that and will find an opportune
moment for that during incubation.

Perhaps as a side effect of the ambitions for the first release discussions on
new functionality don't seem to take off very well, but that time is used to
discuss the process the River project believes it needs to establish. Although
most committers have expressed their desire to have code-review before code is
committed, due to complexity of the codebase and the difficulty to test many
aspects properly, it seemed hard to decide to what extent to enforce that. A
proposal for the initial process guidelines is up for a vote now that combines
RTC for public API and CTR for implementation details.

US export regulations apply to the River codebase and although discussed in
the very early days we were living under the (wrong) impression that complying
with them only applied when we were about to release. We are aware now that we
should have taken care of it even before the code landed in SVN and we are
going to comply as soon as possible.

iPMC Comments:
  Good to see the crypto notice issues are being addressed. Since svn will
  change only once, but the artifacts can land in many places, it's easiest to
  base the notification's location on the svn source and then provide an update
  at graduation (when code moves from ../incubator/river -> ../river). [wrowe]

  Curious if it might be confusing to users going from the first to second
  milestone release to discover the com.sun. -> org.apache. update? [wrowe]

  The community should feel free to come up with some combination of CTR and RTC
  to suit their needs. It's not a one-size-fits-all thing necessarily. [yoavs]
Line 12: Line 105:
=== ADF Faces / Trinidad ===

Apache Trinidad is a library of JavaServer Faces components, runnable with every JSF-compliant implementation.
=== TripleSoup ===
Line 17: Line 108:
=== ODE === === Lokahi ===
Line 19: Line 110:
Apache ODE is an implementation of the BPEL4WS and WS-BPEL specifications for web services orchestration.
ODE entered incubation in March 2006.
iPMC Reviewers: jukka, bdelacretaz, yoavs, jim

The last word of discussion some 3 months ago was about infra, the
creation of the lokahi wiki site. It has since been unused. Some
banter on the tail end of ApacheCon EU/07 included ideas about docs
and deployment help, and some ideas about DB backends.

The last commit activity in the same timeframe were the beginnings
of a jackrabbit connector, no other activity for commits@ since then.

There has been no activity on private.

iPMC Comments:
  Mentors are seriously looking for ideas from the Lokahi community how we
  can help identify that this project still has energy, as mentors had to
  submit this belated report due back in Aug. Will expect to have something
  to report coming up in the November report. [wrowe]

  I'm personally concerned with the continued lack of energy. It's such a good
  project on paper. [yoavs]
Line 23: Line 132:
=== OpenEJB ===

OpenEJB is an open source, modular, configurable, and extendable EJB Container System and EJB Server.

Incubating since: 2006-07-10

We received some very excellent feedback we are all really proud of from a new face in the community. OpenEJB has always prided itself for being the kinder, gentler side of open source and it's really good to know this is coming through.

http://mail-archives.apache.org/mod_mbox/incubator-openejb-dev/200701.mbox/%3cac85de250701201929x2de78662r57de9d62fa30642f@mail.gmail.com%3e

Recent New Contributors: Karan Malhi and Raj Saini contributed their first patches.



----
=== log4net ===
log4net is an implementation of the Apache log4j for the .NET Framework.

Incubating since: 2004-01-15

----
=== mod_ftp ===

mod_ftp is an FTP protocol module for Apache 2.0 and 2.2.

Incubating since: 2005-08-06

----
=== NMaven ===
NMaven develops plugins and integration for Maven to make building and using .NET languages a first-class citizen in Maven.

Incubating since: 2006-11-17

----
=== Wicket ===

Web development framework focusing on pure OO coding, making the creation of new components very easy. Wicket entered the incubator in October 2006.

----
=== UIMA ===

UIMA is a component framework for the analysis of unstructured content such as text, audio and video.

----
=== Woden ===

Woden is a Java class library for reading, validating, manipulating, creating and writing WSDL documents, initially to support WSDL 2.0 and with the longer term aim of supporting past, present and future versions of WSDL.

----

September 2007 Reports (see ReportingSchedule)

These reports are due to the Incubator PMC by 12 September 2007


log4php

iPMC Reviewers: wrowe, jukka, bdelacretaz, yoavs, jim

log4php incubation was restarted in July. Three new committers have been added and a JIRA project has been set up for bug tracking. A maven 2 generated web site has been published to http://incubator.apache.org/log4php. The source tree was reorganized and an initial pass at migration to PHP 5 was committed in July, but there has been little recent activity (possibly due to vacations) and no published development plan. In the next period, the development team needs to establish development plan for an initial snapshot.


Sling

iPMC Reviewers: wrowe, bdelacretaz, yoavs, jim

Sling is a framework to develop content centric web applications based on the idea of modularizing the rendering of HTTP resources. Sling entered incubation on September 5th, 2007.

The Sling project has just started. The basic infrastructure (mailing lists, subversion, issue tracker, web site) is mostly in place; the only things still missing are one committer account and a wiki space. The software grant for Sling has been received and the initial source code is now available in svn.

iPMC Comments:

  • Looking forward to a big picture of how Sling will move itself through the process to graduation, but we don't expect that quite yet. [wrowe]


Sanselan

iPMC Reviewers: yoavs, jim

Sanselan is a pure-java image library for reading and writing a variety of image formats.

The Sanselan project has just started. Mailing lists, subversion and Jira are setup and we're currently working on getting the remaining bits of the infrastructure running like the website etc. The CLAs for all initial committers have been recorded and accounts are pending. The software grant for Sanselan has been received and the code base will be committed to svn as soon as the accounts are created.


River

iPMC Reviewers: wrowe, bdelacretaz, yoavs, jim

River is aimed at the development and advancement of the Jini technology core infrastructure. River entered incubation on Dec 26, 2006.

Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems which are adaptive to change.

The last artifact, the QA framework, has been voted in and landed in SVN. An automated build environment has been put in place and finally all outstanding issues from the Sun issue tracking system have been manually migrated in a large group effort to JIRA.

The River community agreed to do a first release to show the larger Jini community it is serious in its efforts. It ain't a very ambitious release and will be almost an equivalent of the last release done by Sun but includes the ServiceUI code. This release also allows the River community to get acquainted and find out about many of the ASF procedures. No transformation of the com.sun.jini namespace to org.apache.river will take place, but the River community is aware it has to do that and will find an opportune moment for that during incubation.

Perhaps as a side effect of the ambitions for the first release discussions on new functionality don't seem to take off very well, but that time is used to discuss the process the River project believes it needs to establish. Although most committers have expressed their desire to have code-review before code is committed, due to complexity of the codebase and the difficulty to test many aspects properly, it seemed hard to decide to what extent to enforce that. A proposal for the initial process guidelines is up for a vote now that combines RTC for public API and CTR for implementation details.

US export regulations apply to the River codebase and although discussed in the very early days we were living under the (wrong) impression that complying with them only applied when we were about to release. We are aware now that we should have taken care of it even before the code landed in SVN and we are going to comply as soon as possible.

iPMC Comments:

  • Good to see the crypto notice issues are being addressed. Since svn will change only once, but the artifacts can land in many places, it's easiest to base the notification's location on the svn source and then provide an update

    at graduation (when code moves from ../incubator/river -> ../river). [wrowe] Curious if it might be confusing to users going from the first to second

    milestone release to discover the com.sun. -> org.apache. update? [wrowe] The community should feel free to come up with some combination of CTR and RTC to suit their needs. It's not a one-size-fits-all thing necessarily. [yoavs]


TripleSoup


Lokahi

iPMC Reviewers: jukka, bdelacretaz, yoavs, jim

The last word of discussion some 3 months ago was about infra, the creation of the lokahi wiki site. It has since been unused. Some banter on the tail end of ApacheCon EU/07 included ideas about docs and deployment help, and some ideas about DB backends.

The last commit activity in the same timeframe were the beginnings of a jackrabbit connector, no other activity for commits@ since then.

There has been no activity on private.

iPMC Comments:

  • Mentors are seriously looking for ideas from the Lokahi community how we can help identify that this project still has energy, as mentors had to submit this belated report due back in Aug. Will expect to have something to report coming up in the November report. [wrowe] I'm personally concerned with the continued lack of energy. It's such a good project on paper. [yoavs]


September2007 (last edited 2009-09-20 23:07:06 by localhost)