This was extracted (@ 2017-09-20 19:10) from a list of minutes
which have been approved by the Board. Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.

## Description:
- Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Issues:
- None to report this quarter.
## Activity:
- As a community we made 9 releases this quarter.
- We have added a new project: Aries Containers for manage container
deployments from a Java API.
## Health report:
- The dev@ list traffic is back to the level from 2 quarters after a spike
last quarter.
- The dev@ mailing list seems to be the channel most people communicate
over.
## PMC changes:
- Currently 38 PMC members.
- Dominik Przybysz was added to the PMC on Tue May 30 2017
## Committer base changes:
- Currently 55 committers.
- New commmitters:
- Raymond Augé was added as a committer on Mon Apr 24 2017
- Tom De Wolf was added as a committer on Wed May 03 2017
## Releases:
- aries-rsa 1.11.0 was released on Fri Jul 07 2017
- blueprint-core 1.8.1 was released on Fri May 12 2017
- blueprint-core 1.8.2 was released on Thu Jul 06 2017
- blueprint-maven-plugin 1.7.0 was released on Fri May 19 2017
- blueprint-maven-plugin-spring-handlers 1.0.0 was released on Fri May 19 2017
- blueprint-spring 0.4.0 was released on Thu Jul 06 2017
- proxy-impl 1.1.1 was released on Fri May 12 2017
- transaction-manager 1.3.3 was released on Fri May 12 2017
- tx-control 0.0.3 was released on Mon Jun 26 2017
## Mailing list activity:
- dev@aries.apache.org:
- 137 subscribers (up 0 in the last 3 months):
- 324 emails sent to list (586 in previous quarter)
- user@aries.apache.org:
- 241 subscribers (up 4 in the last 3 months):
- 34 emails sent to list (38 in previous quarter)
## JIRA activity:
- 15 JIRA tickets created in the last 3 months
- 22 JIRA tickets closed/resolved in the last 3 months

- Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
- The PMC apologises for missing the April 2017 board report deadline and
offers this report to cover the period between the April board meeting
and now in addition to the months of the previous reporting period (mid
Jan to mid Apr).
## Issues:
- One issue for the Board to consider is how to add new committers when
the PMC lead is not available, see below in committer base changes.
## Activity:
- As a community we made 12 releases this quarter.
- Raymond Augé and Tom de Wolf have been voted in as new committers.
## Health report:
- The PMC were requested by the board to consider if there are any
potential PMC candidates among the current committers. The PMC have
invited Dominik Przybysz and will continue to consider new PMC members.
- A new contribution of CDI integration has been donated by Raymond Augé.
- The dev@ list traffic is increasing, user@ traffic has been quite low.
- The dev@ mailing list seems to be the channel most people communicate
over.
## PMC changes:
- Currently 37 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christian Schneider on Fri Apr 10 2015
- Dominik Przybysz has accepted an invitation and is in the process of
being added
## Committer base changes:
- Currently 55 committers.
- New commmitters:
- Grzegorz Grzybek was added as a committer on Tue Feb 28 2017
- Raymond Augé was added as a committer on Mon Apr 24 2017
- Tom De Wolf was added as a committer on Wed May 03 2017
- We voted Raymond Augé and Tom de Wolf in as committers, but it took
*some time* for Raymond (already a committer) to be added to the
committer group and for Tom's ID to be created while the PMC chair was
unavailable for 4 weeks.
In retrospect, https://www.apache.org/dev/pmc.html#newcommitter
indicates Tom could have had his ID created in the absence of the Chair:
"...ASF member can use the same form in his/her stead. .... If the ICLA
included the PMC name, normally the account will already have been set up
in the correct LDAP group that will grant access to the project source
repository."
But Raymond, who already has an Apache ID, couldn't be added to the
aries unix group without an action by the Chair:
"To grant or deny access to directories in SVN, the PMC chair needs to
update the appropriate [group] entry."
This seems like an anomaly and we'll start a discussion to see what we
can do to resolve.
## Releases:
- Aries JPA (jpa) 2.6.1 - 3-Apr-2017
- Aries Proxy API (proxy-api) 1.1.0 - 24-Mar-2017
- Aries Proxy (proxy) 1.1.0 - 24-Mar-2017
- Aries Blueprint Core (blueprint-core) 1.8.0 - 24-Mar-2017
- Aries Blueprint CM (blueprint-cm) 1.1.0 - 24-Mar-2017
- Aries ESA Maven Plugin (esa-maven-plugin) 1.0.2 - 15-Mar-2017
- Aries JPA (jpa) 2.6.0 - 27-Feb-2017
- Aries Blueprint Maven Plugin Annotations
(blueprint-maven-plugin-annotation) 1.1.0 - 27-Feb-2017
- Aries Blueprint Maven Plugin (blueprint-maven-plugin) 1.6.0 -
27-Feb-2017
- Aries Remote Service Admin 1.10.0 (aries-rsa) 27-Feb-2017
- Aries Blueprint Spring (blueprint-spring) 0.3.0 - 7-Feb-2017
- Aries Aries Blueprint Spring Extender Support
(blueprint-spring-extender) 0.3.0 - 1-Feb-2017
## Mailing list activity:
- dev@aries.apache.org:
- 137 subscribers (up 2 in the last 3 months):
- 539 emails sent to list (398 in previous quarter)
- user@aries.apache.org:
- 237 subscribers (up 0 in the last 3 months):
- 30 emails sent to list (99 in previous quarter)
## JIRA activity:
- 40 JIRA tickets created in the last 3 months
- 47 JIRA tickets closed/resolved in the last 3 months

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- As a community we made 3 releases this quarter and 3 further releases
currently under vote, and added Johannes Utzig as a new committer.
## Health report:
- The PMC were requested by the board to consider if there are any
potential PMC candidates among the current committers. There was some
discussion, but no people were decided upon. This will be discussed
again in the coming days.
- A new contribution of the JAX-RS Services OSGi specification Reference
Implementation has been contributed from Carlos Sierra Andrés. This
specification is currently in draft.
- The number of subscribers to the dev@ user@ private@ and commits@ lists
are roughly consistent (down by 0-3 in the last 3 months).
- The dev@ list traffic is consistent, while the user@ traffic has been
down over last three months. However, there has been a wide variety of
discussion across the different modules within Aries.
- Despite 32 issues being closed off, the number opened was slightly
higher in the past 3 months.
## PMC changes:
- Currently 37 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christian Schneider on Fri Apr 10 2015
## Committer base changes:
- Currently 52 committers.
- No new committers added in the last 3 months
- Last committer addition was Johannes Utzig at Wed Sep 14 2016
## Releases:
- Aries Blueprint Core 1.7.1 (blueprint-core) 2016-10-19
- Aries JMX Core 1.1.7 (jmx-core) 2016-10-19
- Aries Util 1.1.3 (util) 2016-10-20
- Aries Transaction Control service (tx-control) 2016-10-21
- Aries JPA 2.5.0 (jpa) 2016-10-31
- Aries Apache Aries Blueprint Plugin SPI 1.0.0
(blueprint-maven-plugin-spi) 2016-12-05
- Aries Blueprint Plugin Annotations 1.0.0
(blueprint-maven-plugin-annotation) 2016-12-05
- Aries Blueprint Maven Plugin 1.5.0 (blueprint-maven-plugin)
2016-12-05
- Aries Transaction Manager 1.3.2 (transaction-manager) 2017-01-03
- Aries Proxy Service 1.0.6 (proxy-impl) 2017-01-03
## Mailing list activity:
- dev@aries.apache.org:
- 135 subscribers (up 1 in the last 3 months):
- 481 emails sent to list (546 in previous quarter)
- user@aries.apache.org:
- 239 subscribers (up 0 in the last 3 months):
- 269 emails sent to list (91 in previous quarter)

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
Releases
* No releases done this quarter.
Project update
* The Aries Subsystem implementation now works on Apache Felix 4.4.0.
* Discussion held about decoupling Subsystems from Blueprint.
* Discussion held about the process of applying Github pull requests.
JIRA Issues
* Issues created: 26
* Issues resolved: 8
Community
* PMC: No changes. The last PMC member was added on 28th July 2013.
* A number of issues originally filed as Github Pull Requests have been
applied to the Apache Aries codebase.
There are no issues requiring board attention at this time.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
* Apache Aries Subsystems Bundle 1.0.0
This is an 'uber' bundle form of the API and implementation (core) bundles
of Aries Subsystems. Together these are the reference implementation of
the OSGi Subsystem Service Specification which "provides a declarative
model for defining resource collections, including bundles, and an API for
installing and managing those collections of resources." See OSGi
Enterprise Release 5 specification chapter 134. The 'uber' bundle is
released for a convenience for people starting out with Subsystems.
##Project update
We have voted in John Ross as a member of the PMC. No new committers since
the last report. Usage questions and interactions with other non-ASF
projects continue to be asked on the user list, showing users are putting
Aries to use in real world scenarios.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Releases
* Apache Aries Subsystem 1.0.0
This is the reference implementation of the OSGi Subsystem Service
Specification which "provides a declarative model for defining resource
collections, including bundles, and an API for installing and managing
those collections of resources." See OSGi Enterprise Release 5
specification chapter 134.
subsystem-api, subsystem-core, and subsystem-obr 1.0.0 were released.
* Apache Aries SPI-Fly 1.0.0
This is the reference implementation of the OSGi Service Loader Mediator
Specification which "defines a mediator that ensures that the Java SE 6
Service Loader is useful in an OSGi Framework, allowing programs that
leverage the Service Loader to be used in OSGi frameworks almost as-is."
See OSGi Enterprise Release 5 specification chapter 133.
All the spi-fly bundles were released.
* Apache Aries Blueprint no-OSGi 1.0.0
Provides the ability to use Blueprint Schema, xml and injection outside of
the OSGi environment.
* Apache Aries Blueprint Web 1.0.0
Provides a web context listener to bootstrap the no-OSGi Blueprint
container inside a WAR.
* Apache Aries JMX 1.1.0 & 1.1.1
This implements the OSGi JMX Management Model Specification and has been
updated to V1.1 of that spec (which requires V1.2 of JMX).
* Apache Aries Semantic Versioning Checker 0.1.0
This compares the bytecode of a module's previous release, with that being
built to determine whether the package and bundle versions are
semantically versioned correctly.
##Project update
No new committers since the last report. Contributions are coming through
on the dev list through git pull requests and patches to JIRAs and we
continue to have varied discussions across the variety of our sub
components.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
##Project update
* The SPI Fly component now fully implements the ServiceLoader Mediator
Specification 1.0 from the OSGi Enterprise R5 spec (chapter 133). It is
the Reference Implementation of this spec and passes all the OSGi TCK
tests for it.
* The JMX component in Aries now fully implements OSGi/JMX 1.1 from the
OSGi Enterprise R5 spec (chapter 124). As of this version it is the
Reference Implementation of this spec and passes all the OSGi TCK tests
for JMX.
Both components are available in SNAPSHOT versions in the Aries code
base. They are waiting to be released.
* The Semantic Versioning maven plugin component is now being used in our
own builds - for modules that have 1.0 or above releases. For those
modules, the bytecode output to the target directory will be checked for
semantic changes since the last release. If the semantic version is
incorrect, the build will fail.
* Apache Karaf 2.3.0 - one of our significant consumers - has moved up to
include Apache Aries 1.0.0 releases.
No releases this quarter.
##Project Branding Board Report Checklist
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to www.apache.org
included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your
site (pending)
* Project Metadata : DOAP file checked in and up to date (done)
##Community update
No new committers since the last report. The user/dev lists and JIRAs have
had some varied discussions across the Aries modules.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
== Releases ==
Several release vote threads during the last three months saw the release of
88 bundles at version 1.0. These can be found from the downloads link on the
Aries home page. Subsequently, the following micro version update bundles
have been released:
* Apache Aries Blueprint Core 1.0.1
* Apache Aries JMX Core 1.0.1
* Apache Aries Transaction Manager 1.0.1
* Apache Aries JPA Container Managed Contexts 1.0.1
In addition, these new bundles were released.
* Apache Aries JMS Pool 1.0.0
* Apache Aries Transaction Enlisting JDBC Datasource 1.0.0
Many thanks to the release managers for their persistence in getting these
important releases out.
== Project Branding Board Report Checklist ==
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to www.apache.org
included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in footers,
etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your site
(pending)
* Project Metadata : DOAP file checked in and up to date (done)
== Community update ==
Jeremias Maerki has proposed, and posted a patch for, an addition to the
spi-fly module called SPI Catcher. Its objective is along the lines of the
OSGi Connect work in the OSGi Alliance to make it easier to get started with
OSGi dynamic services technology. The SPI Catch approach is complementary by
introducing OSGi APIs much later, if at all, ensuring "runnability totally
outside of OSGi" is preserved.
No new committers since the last report. The user/dev lists and JIRAs have
had some varied discussions across the Aries modules.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
Releases
The following bug fix releases:
* Apache Aries Proxy 0.3.1
* Apache Aries Proxy 0.4.1
As indicated in the last report, bundles and packages are now being
brought up from 0.x to 1.0 to better reflect the stability and level of
confidence we have in them. This will also bring our versioning policy
inline with that described in the OSGi Alliance semantic versioning
whitepaper.
The 1.0 releases have started. We have approx 118 OSGi bundles so these
are being done in logical phases. These have completed:
* Apache Aries Test Support 1.0.0
* Apache Aries JNDI API 1.0.0
* Apache Aries JMX API 1.0.0
* Apache Aries JPA Container API 1.0.0
* Apache Aries Quiesce API 1.0.0
In addition there has been significant activity in the Aries Subsystems
module which will be an implementation of the OSGi Subsystem Service
Specification.
Project Branding Board Report Checklist
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to www.apache.org
included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your site
(pending)
* Project Metadata : DOAP file checked in and up to date (done)
Community update
No new committers since the last report. The user/dev lists and JIRAs
continue to be moderately active, with new patches being posted by
contributors.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
Releases
After the significant number of releases last quarter there were no new
releases this quarter. Work is going on in a branch in preparation for a
1.0 release. Bundles and packages will be brought up from 0.x to 1.0 to
better reflect the stability and level of confidence we have in them. This
will also bring our versioning policy inline with that described in the
OSGi Alliance semantic versioning white paper.
Project Branding Board Report Checklist
Little progress:
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to www.apache.org
included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in footers,
etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your site
(pending)
* Project Metadata : DOAP file checked-in and up to date (done)
Community update
No new committers since the last report. The user/dev lists and JIRAs
continue to be moderately active.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
A new module called versioning has been created for a utility to byte
code analyse latest binaries with the last release of those binaries to
find changes that should cause an OSGi Export-Package version attribute
change, according to the OSGi Semantic Versioning whitepaper.
It looks as though Apache Aries JMS will become the reference
implementation of the update to the OSGi JMX spec for which an early draft
was released by the OSGi Alliance in September.
Releases
--------
Bug fix releases:
* Apache Aries Application 0.2.2
* Apache Aries Util 0.2.1
We have been putting together a functional release from trunk but it's
taking longer than we'd hoped. Due to our objective of getting the OSGi
versioning correct, we're having to release more modules and correct more
OSGi version ranges than we had hoped. A fully staged release of Apache
Aries Blueprint and its dependencies is imminent.
Project Branding Board Report Checklist
---------------------------------------
A little progress here. Unfortunately there's been little progress here.
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to
www.apache.org included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your
site (pending)
* Project Metadata : DOAP file checked in and up to date (done)
No new committers since the last report.
There are no board level issues.

Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
=== Development ===
Users have asked for a release of the Aries JPA bundles and hence the
snapshot bundles it depends on (Aries Util) - in particular due to:
* the new 'runtime enhancer' that will mean entities can be enhanced as
they are used in the runtime, rather than at development time.
* the support for EclipseLink (in addition to Apache OpenJPA) as a JPA
provider
The release process has just started. This will exercise our per bundle
release process adhering to the OSGi Alliance Semantic Versioning
recommendations.
There have also been enhancements to the Aries JMX (whiteboard pattern)
and Aries Subsystem (to use OSGi Core 4.3).
Apache Geronimo, which consumes Apache Aries to implement its enterprise
OSGi application programming model, has been readying a release. The
performance enhancements in the Aries Proxy module which now makes use
of the new Weaving Hooks OSGi specification, has had a few teething
problems for Geronimo. All known problems are now resolved.
=== Project Branding Board Report Checklist ===
We've been reminded of this work and are reporting this checklist for
the first time. We appreciate we're a bit behind the curve here, and
are doing our best to catch up.
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to
www.apache.org included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your
site (pending)
* Project Metadata : DOAP file checkedin and up to date (pending - some
minor updates needed)
=== Community update ===
Roughly same number of dev@ subscribers at 119, user@ 148 subscribers up
14 since last report. John Ross was voted in as a committer after his
significant work to the 'subsystem' module.
There are no board level issues.

Aries delivers a set of pluggable Java components enabling an enterprise OSGi
application programming model.
Since the last board report, there have been enhancements to the 'proxy'
module to which has improved its performance by making use of the new
'Weaving Hook Service' OSGi specification (in 4.3) as an alternative to ASM.
This also removes some restrictions on final classes/methods imposed by use
the use of ASM. The 'spi-fly' module's OSGi service approach to
META-INF/services has also been updated to make use of the Weavking Hook
Service gaining similar benefits.
Some more documentation on the new release-by-bundle release process has
been written. This positions us nicely to demonstrate and make use of the
OSGi Semantic Versioning scheme. Now that the parent-0.4 module has been
released, we are in a position to use it for the next release.
Community update
----------------
Small increase in since last month dev@ 118 subscribers, user@ 134
subscribers. There has been a slight increase in user list traffic. The dev@
list continues to be active with less traffic on the user@ list. No new
committers or PMC members.
There are no board level issues.

Aries delivers a set of pluggable Java components enabling an enterprise OSGi
application programming model.
New releases
------------
These bug fix releases have been completed since the last board report:
* Aries Application 0.2.1
* Aries Blueprint 0.2.1
* Aries Blueprint 0.3.1
Release by bundle
-----------------
After some significant investigation and discussion, we recently concluded a
vote to switch to a release-by-bundle scheme. This is to enable us to follow
the guidance set out in the OSGi Alliance Semantic Versioning white paper.
Community update
----------------
Largely unchanged since last month dev@ 117 subscribers, user@ 129
subscribers. The dev@ list continues to be active with less traffic on the
user@ list. No new committers or PMC members.
There are no board level issues.

Aries delivers a set of pluggable Java components enabling an enterprise
OSGi application programming model.
Aries 0.3 has now been released. Aries Application 0.2.1 is being
released to assist Geronimo. This is the first time Aries has released
a single module.
Now that the first full Aries release since graduation has happened,
and that there is a desire to consider OSGi semantic versioning
guidelines we are discussing whether releasing at a finer grained level
is more appropriate. There is much good discussion about what makes
sense for Aries, with input from what happens in Felix, Sling and ACE.
Community update: largely unchanged since last month dev@ 117
subscribers, user@ 127 subscribers. The dev@ list continues to be
active with less traffic on the user@ list. No new committers or PMC
members since the January report.
There are no board level issues.

Aries delivers a set of pluggable Java components enabling an enterprise
OSGi application programming model.
Aries graduated from the Incubator on 15th December 2010. The majority
of the items on the Incubator transfer to TLP list have been completed
but not all.
We are preparing our 0.3 release and are at the stage of removing
snapshot dependencies by working with the projects Aries depends on to
cut releases themselves. This is making good progress.
The Aries web site has now moved from Confluence to CMS. The speed to
put a page into production is much improved and very welcome.
Community update: dev@ 118 subscribers, user@ 127 subscribers. The dev@
list continues to be active with less traffic on the user@ list. No new
committers or PMC members since the December report.
There are no board level issues.

Establish the Apache Aries Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software related to a set of pluggable Java
components enabling an enterprise OSGi application programming
model for deployment to a variety of OSGi based runtimes, for
distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Aries Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Aries Project be and hereby is
responsible for the creation and maintenance of software
related to a set of pluggable Java components enabling an
enterprise OSGi application programming model for deployment to
a variety of OSGi based runtimes;
and be it further
RESOLVED, that the office of "Vice President, Apache Aries" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Aries Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Aries Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Aries Project:
* A. J. David Bosschaert <davidb@apache.org>
* Adam Wojtuniak <awojtuniak@apache.org>
* Alan Cabrera <adc@apache.org>
* Alan T Keane <atk@apache.org>
* Alasdair Nottingham <not@apache.org>
* Andrew Osborne <ozzy@apache.org>
* Bartosz Kowalewski <bkowal@apache.org>
* Bertrand Delacretaz <bdelacretaz@apache.org>
* Carsten Ziegeler <cziegeler@apache.org>
* Chris Wilkinson <cwilkin@apache.org>
* Davanum Srinivas <dims@apache.org>
* David Jencks <djencks@apache.org>
* Emily Jiang <ejiang@apache.org>
* Eoghan Glynn <eglynn@apache.org>
* Graham Charters <gcc@apache.org>
* Guillaume Nodet <gnodet@apache.org>
* Hiram R. Chirino <chirino@apache.org>
* Holly Cummins <cumminsh@apache.org>
* Ian Robinson <irobins@apache.org>
* J. Daniel Kulp <dkulp@apache.org>
* James Strachan <jstrachan@apache.org>
* Jarek Gawor <gawor@apache.org>
* Jean Sebastien Delfino <jsdelfino@apache.org>
* Jeremy Hughes <hughesj@apache.org>
* Joseph Alan Bohn <jbohn@apache.org>
* Kevan Lee Miller <kevan@apache.org>
* Kiril Malenkov Mitov <kmitov@apache.org>
* Lei Wang <rwonly@apache.org>
* Lin Sun <linsun@apache.org>
* Mark Nuttall <mnuttall@apache.org>
* Niklas Gustavsson <ngn@apache.org>
* Nikolai Dimitrov Tankov <nikolait@apache.org>
* Par Niclas Hedhman <niclas@apache.org>
* Richard McGuire <rickmcguire@apache.org>
* Sabine Heider <heidersab@apache.org>
* Sergey Beryozkin <sergeyb@apache.org>
* Stuart McCulloch <mcculls@apache.org>
* Timothy James Ward <timothyjward@apache.org>
* Valentin Mahrwald <mahrwald@apache.org>
* Violeta Georgieva Georgieva <violetagg@apache.org>
* Zhaohui Feng <rfeng@apache.org>
* Zoe Slattery <zoe@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jeremy
Hughes be appointed to the office of Vice President, Apache Aries,
to serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Aries PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Aries Project; and be it further
RESOLVED, that the initial Apache Aries Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Aries podling; and be it further
RESOLVED, that all responsibility pertaining to the Apache
Incubator Aries podling encumbered upon the Apache Incubator
PMC are hereafter discharged.
Approved unanimously by roll call vote.

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.

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
* JPA
* JNDI
* Transaction
* Quiesce
* Samples
There continues to be a vibrant community as shown by the activity on the
mailing list this year.
We have recently completed our 0.2-incubating release. This is our second
release since entering incubation. This release is in support of Geronimo
3.0 which uses Apache Aries.
The OSGi Enterprise Compliance Tests have been run against Blueprint, JMX,
JNDI and transactions modules and the results have been published to the
aries-dev mailing list and are available from the Aries web site
Top 2 or 3 things to resolve before graduation:
* Build community [done]
* Create a release [done]
* Address project scope concerns raised during acceptance vote

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

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
* Blueprint
* JMX
* JPA
Several new sample applications have been developed to demonstrate the Aries
functionality.
A new component has been created to feed experience into the OSGi standards
process.
There has been a lot of activity on the mailing list this year indicating a
vibrant community is being built.
One new committer, Rex Wang, has been added. Redhat have started to
participate in the project.
We have begun the process of doing a 0.1.0 release and aim to release
shortly.
Top 2 or 3 things to resolve before graduation:
* Build community
* Create a release
* Address project scope concerns raised during acceptance vote

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 svn area has been organized with a single trunk for now, though we still
need to settle the discussion about components lifecycle and the svn layout.
The following sub-components are actively being developed:
* Application
* Blueprint
* JMX
There has been a lot of activity on the mailing list this month indicating a
vibrant community is being built.
Top 2 or 3 things to resolve before graduation:
* Build community
* Create a release
* Address project scope concerns raised during acceptance vote

Aries will deliver a set of pluggable Java components enabling an enterprise
OSGi application programming model.
Aries entered incubation on September 22, 2009. This is our first board
report.
There are currently no issues requiring IPMC or Board attention .
All infra resources have been set up (svn / site / mailing lists) very
quickly. The svn area has been organized with a single trunk for now, though
we still need to settle the discussion about components lifecycle and the
svn layout. IBM has contributed some code that has been imported into svn
and the JNDI modules have already been imported into trunk. Both Geronimo
contribution (OSGi Blueprint Services) and ServiceMix contribution (OSGi
Transaction Manager) have been imported into trunk.
On the community side, we've already voted 3 additional committers (Adam
Wojtuniak, Alan Keane and Niclas Hedhman) who had expressed their interest
in joining the project just after the acceptance vote on the proposal was
launched.
There is a lot of discussions and activity on the mailing lists.
Top 2 or 3 things to resolve before graduation:
* Build community
* Create a release
* Address the project scope concerns raised during acceptance vote