incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "April2012" by JukkaZitting
Date Fri, 06 Apr 2012 14:52:28 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "April2012" page has been changed by JukkaZitting:
http://wiki.apache.org/incubator/April2012?action=diff&rev1=55&rev2=56

Comment:
Unify formatting of podling reports. No content changes.

  
    We expect these projects to graduate within the next quarter.
  
- TODO: Any23, Cordova, Celix, Chukwa, AWF, DeviceMap, DirectMemory, EasyAnt, Flex, Giraph,
JSPWiki, Kafka, Kitty, Mesos, ODF Toolkit, Oozie, OpenOffice, Syncope, Tashi, VXQuery
+ TODO: Any23, Cordova, Celix, Chukwa, AWF, DeviceMap, DirectMemory, EasyAnt,
+       Flex, Giraph, JSPWiki, Kafka, Kitty, Mesos, ODF Toolkit, Oozie,
+       OpenOffice, Syncope, Tashi, VXQuery
  
  -------------------- Detailed Reports --------------------
  Any23
  
- Anything To Triples (any23) is a library, a web service and a command line tool that extracts
+ Anything To Triples (any23) is a library, a web service and a command line
- structured data in RDF format from a variety of Web documents. Currently it supports the
following
- input formats:
+ tool that extracts structured data in RDF format from a variety of Web
+ documents. Currently it supports the following input formats:
  
-     RDF/XML, Turtle, Notation 3
+   - RDF/XML, Turtle, Notation 3
-     RDFa with RDFa1.1 prefix mechanism
+   - RDFa with RDFa1.1 prefix mechanism
-     Microformats: Adr, Geo, hCalendar, hCard, hListing, hResume, hReview, License, XFN and
Species
+   - Microformats: Adr, Geo, hCalendar, hCard, hListing, hResume, hReview,
+     License, XFN and Species
-     HTML5 Microdata: (such as Schema.org)
+   - HTML5 Microdata: (such as Schema.org)
-     CSV: Comma Separated Values with separator autodetection.
+   - CSV: Comma Separated Values with separator autodetection.
  
- - The community has seen steady levels of traffic with the dev list receiving 281 hits in
March; an
+ The community has seen steady levels of traffic with the dev list receiving
- increase from the previous month.
+ 281 hits in March; an increase from the previous month.
+ 
- - One very interesting thread related to the webdatacommons.org project, which recently
used Apache
+ One very interesting thread related to the webdatacommons.org project, which
- Any23 to extract embedded structured data from web pages. The project scales to cover several
billion
+ recently used Apache Any23 to extract embedded structured data from web
+ pages. The project scales to cover several billion web pages, so we are
- web pages, so we are very confident that the Any23 community is growing interest, this news
reflects
+ very confident that the Any23 community is growing interest, this news
- that view.
+ reflects that view.
+ 
- - We were recently contacted by the W3C's Semantic Web Activity Lead (Ivan Herman), and
have been
+ We were recently contacted by the W3C's Semantic Web Activity Lead
- invited to provide an EARL report of Any23's test results with regards to the RDFa test
suite,
+ (Ivan Herman), and have been invited to provide an EARL report of Any23's
+ test results with regards to the RDFa test suite, so that we could include
- so that we could include it into http://rdfa.info/earl-reports/ We have been given until
the end of April
+ it into http://rdfa.info/earl-reports/ We have been given until the end of
- to submit.
+ April to submit.
+ 
- - We are very close to VOTE'ing on the 0.7.0-incubating release (1st during incubation),
and Simone
+ We are very close to VOTE'ing on the 0.7.0-incubating release (1st during
- Tripodi has stepped up as release manager. We are currently discussing when to push for
the RC.
+ incubation), and Simone Tripodi has stepped up as release manager. We are
+ currently discussing when to push for the RC.
+ 
- - Chris Mattmann is investigating the use of Any23 as one potential component in implementing
GeoSPARQL,
+ Chris Mattmann is investigating the use of Any23 as one potential component
+ in implementing GeoSPARQL, along with Jena, Tika and Apache SIS.
- along with Jena, Tika and Apache SIS.
- 
  
  Signed off by mentor: mattmann
  
  --------------------
  Cordova
  
- Apache Cordova is a platform for building native mobile applications using HTML, CSS and
JavaScript. The project entered incubation as Apache Callback in October, 2011, before changing
its name to Cordova.
+ Apache Cordova is a platform for building native mobile applications using
+ HTML, CSS and JavaScript. The project entered incubation as Apache Callback
+ in October, 2011, before changing its name to Cordova.
  
    - continued code migration to Cordova namespace
    - documentation updated for migration inc getting started guides
    - cordovajs migration for: ios, android, blackberry complete; 
    - cordovajs migration remains for: wp7, bada, webos and qt
-   - Shaz crushed crazy iOS local storage bug; his solution getting a tonne of attention
in iOS community
+   - Shaz crushed crazy iOS local storage bug; his solution getting a tonne
+     of attention in iOS community
    - Tim Kim voted as committer
    - Intel contribution of initial Tizen src identified
  
@@ -96, +108 @@

  
  Signed off by mentor: 
  
- 
  --------------------
  Celix
  
@@ -104, +115 @@

  
  Celix entered incubation on November 2, 2010.
  
- The last month we received or first large code donation, the code still has to be added
to the project. This code is an implementation of the OSGi Device Access specification for
Celix and has been made by Thales Netherlands. Together with this donation a new committer
(Pepijn Noltes) is accepted. Pepijn has developed and will maintain the Device Access code.
+ The last month we received or first large code donation, the code still has
+ to be added to the project. This code is an implementation of the OSGi Device
+ Access specification for Celix and has been made by Thales Netherlands.
+ Together with this donation a new committer (Pepijn Noltes) is accepted.
+ Pepijn has developed and will maintain the Device Access code.
  
  We have also been working on a graduation plan which is included below.
  
  Most important issues are:
+ 
- * Improve robustness (APR, error handling etc), resulting in a first release
+  - Improve robustness (APR, error handling etc), resulting in a first release
- * Update/Implement remote services for interoperability with Java OSGi (Apache Felix)
+  - Update/Implement remote services for interoperability with Java OSGi
+    (Apache Felix)
- * Generate awareness and grow a community!
+  - Generate awareness and grow a community!
  
  Graduation Plan
  
- Celix is in incubation since November 2010. During the first one and a half year talks where
given at several conferences (EclipseCon, ApacheCon, OSGi User Group meetings, etc).
- Even though there seems to be an interest in the project, two important questions keep coming
up:
+   Celix is in incubation since November 2010. During the first one and a half
+   year talks where given at several conferences (EclipseCon, ApacheCon, OSGi
+   User Group meetings, etc). Even though there seems to be an interest in
+   the project, two important questions keep coming up:
+ 
- - What is the state of the project?
+   - What is the state of the project?
- - Why no support for C++?
+   - Why no support for C++?
  
- Trying to answer/solve these two questions might make it able to attract more community
members. So this plan will focus mostly on these two items.
+   Trying to answer/solve these two questions might make it able to attract
+   more community members. So this plan will focus mostly on these two items.
  
- = State of the project
+ State of the project
  
- == Releases
+  - Releases
+ 
- Celix entered incubation in its early stage. There was only a proof of concept, but no complete
implementation. 
+    Celix entered incubation in its early stage. There was only a proof of
- This is an important reason for people to hold back and not yet use/improve Celix, on the
other hand,  being hesitant also keeps Celix from growing towards a more stable/robust solution.
- To be able to use Celix the implementation has to reach, at least, a more stable state.
Over the past year lots of effort has been put into this.
- Within the next half year a release has to be made of the core component of Celix. Hopefully
this will attract more users/testers (and potentially committers).
- Since a formal release takes quite some effort, it might also make sense to provide snapshots
(with documentation) to be able to reach more people.
+    concept, but no complete implementation. This is an important reason for
+    people to hold back and not yet use/improve Celix, on the other hand,
+    being hesitant also keeps Celix from growing towards a more stable/robust
+    solution. To be able to use Celix the implementation has to reach, at
+    least, a more stable state. Over the past year lots of effort has been
+    put into this. Within the next half year a release has to be made of the
+    core component of Celix. Hopefully this will attract more users/testers
+    (and potentially committers). Since a formal release takes quite some
+    effort, it might also make sense to provide snapshots (with documentation)
+    to be able to reach more people.
  
- == Committers
+  - Committers
- During the last months there has been an interest from Thales Netherlands to use Celix in
its middleware. In a research project they are working on an implementation of the Device
Access specification. This implementation is donated to Celix, and the main developer has
expressed the intention to maintain the code base. Via this path a new committer has been
added to Celix [1][2].
- But to be able to have a diverse community more committers are needed.
- Having a release makes it easier for people to use and improve Celix. This is one step towards
more committers.
  
+    During the last months there has been an interest from Thales Netherlands
+    to use Celix in its middleware. In a research project they are working on
+    an implementation of the Device Access specification. This implementation
+    is donated to Celix, and the main developer has expressed the intention
+    to maintain the code base. Via this path a new committer has been added
+    to Celix [1][2]. But to be able to have a diverse community more
+    committers are needed. Having a release makes it easier for people to use
+    and improve Celix. This is one step towards more committers.
+ 
- [1]: http://markmail.org/thread/hfwuspl3swoisenq
+    [1]: http://markmail.org/thread/hfwuspl3swoisenq
- [2]: http://markmail.org/message/q4n7562jvngd33s5
+    [2]: http://markmail.org/message/q4n7562jvngd33s5
  
- == Technical state
+  - Technical state
- One of the important aspects of Celix is interoperability with Java OSGi through remote
services. Currently Celix has basic support for Celix to Celix remote services, following
the Remote Service Admin specification of OSGi. This implementation has to be improved and
extended to comply better to the specification. Also a Java OSGi implementation has to be
made which can interact with the Celix implementation. Some existing opensource solutions
are available, but are either to large for our intended target platforms or rely on to many
other libraries (for example XML handling etc). To be able to have an implementation which
fits the environment ((de)serialization and protocol) it makes sense to implement a simple
solution ourselves.
- Having functional remote services makes it easier to use Celix in a mixed Java/C environment.
This solution can also be positioned as an alternative to JNI with the benefit that the Java
and C components are separate processes. If either one crashes the other part is kept running,
resulting in a more robust solution.
+ 
+    One of the important aspects of Celix is interoperability with Java OSGi
+    through remote services. Currently Celix has basic support for Celix to
+    Celix remote services, following the Remote Service Admin specification
+    of OSGi. This implementation has to be improved and extended to comply
+    better to the specification. Also a Java OSGi implementation has to be
+    made which can interact with the Celix implementation. Some existing
+    opensource solutions are available, but are either to large for our
+    intended target platforms or rely on to many other libraries (for
+    example XML handling etc). To be able to have an implementation which
+    fits the environment ((de)serialization and protocol) it makes sense to
+    implement a simple solution ourselves. Having functional remote services
+    makes it easier to use Celix in a mixed Java/C environment. This solution
+    can also be positioned as an alternative to JNI with the benefit that the
+    Java and C components are separate processes. If either one crashes the
+    other part is kept running, resulting in a more robust solution.
   
- = C++ Support
+ C++ Support
  
- == Technical Scope
+   - Technical Scope
- Currently Celix is limited to C only. This was a deliberate choice since Celix tries to
target  embedded/constrained platforms. But during talks people also seem to be interested
in C++ support. Extending the technical scope of the project might attract more users and
committers.
- Over the next half year we will work out a plan how C++ support can be added without impacting
the current supported platforms. A start with the discussions has been made on the mailinglist,
see [2] for more information.
  
+     Currently Celix is limited to C only. This was a deliberate choice since
+     Celix tries to target  embedded/constrained platforms. But during talks
+     people also seem to be interested in C++ support. Extending the technical
+     scope of the project might attract more users and committers. Over the
+     next half year we will work out a plan how C++ support can be added
+     without impacting the current supported platforms. A start with the
+     discussions has been made on the mailinglist, see [2] for more information.
+ 
- [3]: http://markmail.org/thread/a3qltqhsocmrnerd
+     [3]: http://markmail.org/thread/a3qltqhsocmrnerd
  
- == Cooperate with existing C++ OSGi like implementations
+   - Cooperate with existing C++ OSGi like implementations
- In [3] a list of similar projects is mentioned. Reaching out to these projects and trying
to find a common ground on requirements/API etc could benefit Celix (and those projects as
well). 
+ 
+     In [3] a list of similar projects is mentioned. Reaching out to these
+     projects and trying to find a common ground on requirements/API etc
+     could benefit Celix (and those projects as well).  To see if there is
- To see if there is a common ground we need to contact those projects and plan a meeting.
+     a common ground we need to contact those projects and plan a meeting.
  
  Signed off by mentor:
  
@@ -167, +224 @@

  toolkit for displaying, monitoring and analyzing results to make the best
  use of the collected data.
  
- - Chukwa 0.5.0 has been released
+   - Chukwa 0.5.0 has been released
- - New committer Ahmed Fathalla has been voted in and granted proper karma
+   - New committer Ahmed Fathalla has been voted in and granted proper karma
- - Mentor William A. Rowe Jr resigned
+   - Mentor William A. Rowe Jr resigned
- - Alan D. Cabrera volunteer to become new mentor
+   - Alan D. Cabrera volunteer to become new mentor
- - For Chukwa 0.5.0 release, the majority of code has been contributed from single individual.
+   - For Chukwa 0.5.0 release, the majority of code has been contributed
- - There are questions raised by mentors that there should be more diversity of the contribution
from the community.
- - There are increased activities on user mailing list in the past month, but momentum and
traction is still a concern.
- - More to the point, we had a discussion whether or not to continue Incubation for Chukwa.
The consensus was that it's worthwhile to wait for the project to get traction a little longer.
+     from single individual.
+   - There are questions raised by mentors that there should be more
+     diversity of the contribution from the community.
+   - There are increased activities on user mailing list in the past
+     month, but momentum and traction is still a concern.
+   - More to the point, we had a discussion whether or not to continue
+     Incubation for Chukwa. The consensus was that it's worthwhile to wait
+     for the project to get traction a little longer.
  
+ Signed off by mentor: berndf, cdouglas
- Signed off by mentor:
- 
- berndf, cdouglas
  
  --------------------
  AWF
  
- AWF is a non-blocking, asynchronous, event driven high performance web framework running
on the JVM. The project entered incubation on 2011-07-08.
+ AWF is a non-blocking, asynchronous, event driven high performance web
+ framework running on the JVM. The project entered incubation on 2011-07-08.
  
- The project has been renamed from DEFT to AWF, all the mailing-lists, web site, JIRA etc
have been migrated.
+ The project has been renamed from DEFT to AWF, all the mailing-lists, web
+ site, JIRA etc have been migrated.
  
  We have had few activity this quarter:
+ 
    - Still working on getting our first release out
    - Some bugs have been fixed
  
  How has the community developed since the last report?
+ 
    - On one hand Roger does not have any more time to work on the project
-   - But on the other hand there is a new potential committer. His recommendation is being
under discussion 
+   - But on the other hand there is a new potential committer. His
+     recommendation is being under discussion 
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+ 
    - Not at this time.
  
  How has the project developed since the last report?
+ 
    - Still working on getting our first release out
  
- NOTE: It was questioned if this project was viable as the activity remains low, but the
team thinks that it's a temporary situation due to individuals being swamped into day job
and change in family situation, so the decision to pursue the effort has been agreed on.
+ NOTE: It was questioned if this project was viable as the activity remains
+ low, but the team thinks that it's a temporary situation due to individuals
+ being swamped into day job and change in family situation, so the decision
+ to pursue the effort has been agreed on.
  
+ Signed off by mentors: mnour, elecharny
- Signed off by mentors: 
- mnour, elecharny
  
  --------------------
  DeviceMap
  
- Apache DeviceMap is a data repository containing device information, images and other relevant
information for all sorts of mobile devices, e.g. smartphones and tablets.
+ Apache DeviceMap is a data repository containing device information, images
+ and other relevant information for all sorts of mobile devices, e.g.
+ smartphones and tablets.
  
  Entered incubation on January 3rd, 2012.
  
  There are no issues that require the Incubator PMC's or the board's attention.
  
- The project is still slowly ramping up. We have started to flesh out our website, created
some initial prototypes for data collection of mobile device data and setup a VM at http://devicemap-vm.apache.org/
to experiment with those prototypes.
+ The project is still slowly ramping up. We have started to flesh out our
+ website, created some initial prototypes for data collection of mobile
+ device data and setup a VM at http://devicemap-vm.apache.org/ to experiment
+ with those prototypes.
  
  Signed off by mentor: bdelacretaz, kevan
  
@@ -224, +298 @@

  
  (incubating since October 2011)
  
- Apache DirectMemory is a multi layered cache implementation featuring off-heap memory management
(a-la BigMemory) to enable efficient handling of a large number of java objects without affecting
jvm garbage collection performance.
+ Apache DirectMemory is a multi layered cache implementation featuring
+ off-heap memory management (a-la BigMemory) to enable efficient handling
+ of a large number of java objects without affecting jvm garbage collection
+ performance.
  
- There is only one important issue to address in the move towards graduation - understanding
process/decision making guidelines (new committer process is undergoing testing, release process
still yet to be worked out)
+ There is only one important issue to address in the move towards graduation
+ - understanding process/decision making guidelines (new committer process
+ is undergoing testing, release process still yet to be worked out)
  
  Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
  
- - None
+   - None
  
  How has the community developed since the last report
  
- - Tasks and proposals contributed by non-committers
+   - Tasks and proposals contributed by non-committers
- - The team has upvoted a new committer
+   - The team has upvoted a new committer
  
  How has the project developed since the last report.
- - An important contribution (the integration with EHCache, the most used caching system)
could spread adoption and community attention
+ 
+   - An important contribution (the integration with EHCache, the most used
+     caching system) could spread adoption and community attention
- - A talk of DirectMemory should be presented at DevoXX France (thanks to Olivier Lamy)
+   - A talk of DirectMemory should be presented at DevoXX France (thanks to
+     Olivier Lamy)
  
  Signed off by mentor: twilliams
  
@@ -249, +331 @@

  Easyant is a build system based on Apache Ant and Apache Ivy. Incubating since 2011-01-31.
  
  Towards graduation, we need to:
+ 
- * Create a release
+   - Create a release
- * Build a community
+   - Build a community
  
  Since the last report:
- * in the last report we described that the activity of the podling was quite low. Some discussion
with developpers and mentors raised about this concern. Developpers acknowledged that the
current code refactoring make it's build break too much to keep people interested in contributing.
Developpers are still motivated even if most lack of time. The conclusion is that the focus
should be on doing a release ASAP to keep things going on and bring back stability.
+ 
+   In the last report we described that the activity of the podling was quite
+   low. Some discussion with developpers and mentors raised about this concern.
+   Developpers acknowledged that the current code refactoring make it's build
+   break too much to keep people interested in contributing. Developpers are
+   still motivated even if most lack of time. The conclusion is that the focus
+   should be on doing a release ASAP to keep things going on and bring back
+   stability.
+ 
- * Some discussion started about the last points to tackle before preparing a release.
+   Some discussion started about the last points to tackle before preparing
+   a release.
  
  Signed off by mentor: bodewig
  
@@ -271, +363 @@

  
  Top three items to resolve before graduation:
  
-   1. Resolve trademark donation or licensing
+   - Resolve trademark donation or licensing
-   2. Complete code and bug database donation
+   - Complete code and bug database donation
-   3. Make at least one release
+   - Make at least one release
  
  Is there anything that the Incubator PMC or ASF Board specifically needs
  to address?
@@ -298, +390 @@

  
  What has been done (releases, milestones, etc.) since the last report?
  
-   - The Flex compiler source code, including history,
+   - The Flex compiler source code, including history, was donated to Apache.
+     It is pending import into the SVN respository
-     was donated to Apache.  It is pending import into
-     the SVN respository
    - Other initial committers have donated code to the whiteboard.
    - Martin Heidegger was accepted as committer to the podling.
  
@@ -315, +406 @@

    Our mentors are great. We are wondering if Apache has considered giving
    large projects like Flex their own SVN and JIRA servers. Recently, we pushed
    really hard to get a software grant signed (An Adobe VP even came in
-   to sign it while he was taking time off to move to a new house) in order to try to
+   to sign it while he was taking time off to move to a new house) in order to
-   make the weekend deadline for getting code imported into SVN.  We are in
+   try to make the weekend deadline for getting code imported into SVN.  We
-   a hurry because we have seen signs we are losing momentum (mailing list
+   are in a hurry because we have seen signs we are losing momentum (mailing
-   traffic is much lower) and a key Flex conference is coming up on April 15.
+   list traffic is much lower) and a key Flex conference is coming up on
-   Being able to announce that new code was in SVN would be a good boost and
+   April 15. Being able to announce that new code was in SVN would be a good
-   good timing. 
+   boost and good timing.
  
    We submitted a software grant and code on Friday afternoon, but were 
    too late to have the secretary record the software grant and that meant 
@@ -351, +442 @@

  entered the incubator in August 2011.
  
  Project developments:
+ 
- * First incubator release (version 0.1)
+   - First incubator release (version 0.1)
- * Increased traffic on user list from new users
+   - Increased traffic on user list from new users
- * Committer/PPMC member Claudio gave talk on Giraph at FOSDEM
+   - Committer/PPMC member Claudio gave talk on Giraph at FOSDEM
- (http://bit.ly/ClaudioGiraphTalk)
+     (http://bit.ly/ClaudioGiraphTalk)
- * "Processing over a billion edges on Apache Giraph", a talk by
+   - "Processing over a billion edges on Apache Giraph", a talk by
- Committer/PPMC member Avery accepted for Hadoop Summit in June.
+      Committer/PPMC member Avery accepted for Hadoop Summit in June.
- * Community working with students at UC Irvine who are exploring
+   - Community working with students at UC Irvine who are exploring
- porting various algorithms to Giraph.
+     porting various algorithms to Giraph.
- * 53 new JIRA issues opened since last report
+   - 53 new JIRA issues opened since last report
- * 36 JIRA issues closed since last report
+   - 36 JIRA issues closed since last report
  
  Next steps:
+ 
- * Another incubator release
+   - Another incubator release
- * Adding new committers
+   - Adding new committers
  
  Signed off by mentor: omalley, mattmann
  
@@ -377, +470 @@

  
  JSPWiki is a JSP-based wiki program.
  
- As a result of discussing in the dev-list, the objectives
+ As a result of discussing in the dev-list, the objectives for graduation have
+ changed: the first Apache release will be based on 2.8 (package-renamed),
- for graduation have changed: the first Apache release
- will be based on 2.8 (package-renamed), which is 
- battle-tested, being the plan to evolve from there.
+ which is  battle-tested, being the plan to evolve from there.
  
- 4 JIRA issues were fixed since last period, and tests are
+ 4 JIRA issues were fixed since last period, and tests are now part of the
- now part of the main build.
+ main build.
  
- The main issues blocking graduation now are resolution 
+ The main issues blocking graduation now are resolution  acceptance, and
- acceptance, and community and IPMC graduation vote.
+ community and IPMC graduation vote.
  
- The developer list currently has ?? subscribers; and the
+ The developer list currently has ?? subscribers; and the user list has
- user list has ??? subscribers.
+ ??? subscribers.
  
  Signed off by mentor:
  
@@ -398, +490 @@

  
  (introduced to Apache incubator on Jul 4, 2011)
  
- Kafka provides an extremely high throughput distributed publish/subscribe messaging system.
Additionally, it supports relatively long term persistence of messages to support a wide variety
of consumers, partitioning of the message stream across servers and consumers, and functionality
for loading data into Apache Hadoop for offline, batch processing.
+ Kafka provides an extremely high throughput distributed publish/subscribe
+ messaging system. Additionally, it supports relatively long term persistence
+ of messages to support a wide variety of consumers, partitioning of the
+ message stream across servers and consumers, and functionality for loading
+ data into Apache Hadoop for offline, batch processing.
  
  A list of the most important issues to address in the move towards graduation
  
- - Invite diverse new active committers
+   - Invite diverse new active committers
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
  
- - None
+   - None
  
  How has the community developed since the last report?
  
- - Added a new committer.  Continued contribution to source code in fixes and features and
continued activity on the mailing lists.
+   - Added a new committer.  Continued contribution to source code in fixes
+     and features and continued activity on the mailing lists.
  
  How has the project developed since the last report?
  
- - Work was begun on 0.8 release which includes our replication feature and also requires
a breaking change for existing consumers/producer to the wiring protocol.
+   - Work was begun on 0.8 release which includes our replication feature and
+     also requires a breaking change for existing consumers/producer to the
+     wiring protocol.
  
- 
- Signed off by mentor:
+ Signed off by mentor: cdouglas, adc
- 
- cdouglas, adc
  
  --------------------
  Kitty
  
- The Kitty Project is a lightweight, production focused, Java-based application server performance
diagnostic and management utility.
+ The Kitty Project is a lightweight, production focused, Java-based
+ application server performance diagnostic and management utility. Kitty
- Kitty is written in Groovy.
+ is written in Groovy.
  
  The project entered incubation on 2010-10-03.
  
  In order to get graduated, Kitty needs the following features:
+ 
- 1) The ability to save profiles of commonly connected to jmx servers including groups of
tomcat servers
+   - The ability to save profiles of commonly connected to jmx servers
+     including groups of tomcat servers
- 2) The ability to collect metrics on an aggregate group of JMX servers
+   - The ability to collect metrics on an aggregate group of JMX servers
  
  There are no issues that require the Incubator PMC's or the board's attention.
  
  The community hasn't grown since the last report.
  
- The project had some contribution as far as code is concerned, but the mailing list had
+ The project had some contribution as far as code is concerned, but the
- no new threads started nor old threads had new contributions.
+ mailing list had no new threads started nor old threads had new contributions.
- Changes were related to the management of the console output, and some reengineering in
order to begin working on the missing features.
+ Changes were related to the management of the console output, and some
+ reengineering in order to begin working on the missing features.
  
  Signed off by mentor: kevan
  
  --------------------
  Mesos
  
- Mesos is a scalable cluster manager that can dynamically share resources between multiple
+ Mesos is a scalable cluster manager that can dynamically share resources
- computing frameworks, including Hadoop, Spark and MPI.
+ between multiple computing frameworks, including Hadoop, Spark and MPI.
  
  Mesos entered incubation on December 23, 2010.
  
  Progress since the last report:
- * Begun the process for our *first release!* (vote on mesos-dev list has passed, now moving
to vote on general@incubator)!
+ 
+   - Begun the process for our *first release!* (vote on mesos-dev list has
+     passed, now moving to vote on general@incubator)!
- * Discussion/vote thread started about adding two new committers
+   - Discussion/vote thread started about adding two new committers
- * Hadoop patch working and new tutorial written
+   - Hadoop patch working and new tutorial written
- * API improvements declineOffer
+   - API improvements declineOffer
- * Updates to cluster Deployment scripts
+   - Updates to cluster Deployment scripts
- * Committed major build system update (migrated to Autotools, build sped up by >2x)
+   - Committed major build system update (migrated to Autotools, build
+     sped up by >2x)
  
  Top priorities prior to graduation:
+ 
- * Finalizing addition of new committers to the project!
+   - Finalizing addition of new committers to the project!
  
  Issues for Incubator PMC or ASF Board:
+ 
-  * None at this time.
+   - None at this time.
  
  Signed off by mentor: tomwhite
  
  --------------------
  ODF Toolkit
  
- The ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and
manipulation of OpenDocument Format (ISO/IEC 26300 == ODF) documents. Unlike other approaches
which rely on runtime manipulation of heavy-weight editors via an automation interface, the
ODF Toolkit is lightweight and ideal for server use.
+ The ODF Toolkit is a set of Java modules that allow programmatic creation,
+ scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF)
+ documents. Unlike other approaches which rely on runtime manipulation of
+ heavy-weight editors via an automation interface, the ODF Toolkit is
+ lightweight and ideal for server use.
  
- * ODF Toolkit entered incubation on Aug 1st, 2011.
+ ODF Toolkit entered incubation on Aug 1st, 2011.
  
- * Most important issues to address.
+ Most important issues to address.
+ 
-   -- Growing the community, increasing diversity of committers
+   - Growing the community, increasing diversity of committers
  
- * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
+ Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
+ 
-   -- None at this time.
+   - None at this time.
  
- * How has the community developed since the last report
+ How has the community developed since the last report
+ 
-   -- We have two GSoC mentors and two proposals and are discussing these with students.
+   - We have two GSoC mentors and two proposals and are discussing these
+     with students.
-   -- Most recent new committer was voted in November 16th, 2011
+   - Most recent new committer was voted in November 16th, 2011
  
- * How has the project developed since the last report.
+ How has the project developed since the last report.
+ 
-    -- We did our first, successful podling release on January 12th
+   - We did our first, successful podling release on January 12th
-    -- Researched new crypto reporting requirements in preparation for checking in encryption/digital
signature support.
+   - Researched new crypto reporting requirements in preparation for
+     checking in encryption/digital signature support.
-    -- Working on next release, to feature the new crypto support, for later this Spring.
+   - Working on next release, to feature the new crypto support, for later
+     this Spring.
  
  Signed off by mentor: nick
  
  --------------------
  Oozie
+ 
  Oozie is a workflow management and scheduler primarily for Hadoop based jobs.
    
  Oozie entered the incubation on July 11, 2011.
    
- * A list of the three most important issues to address in the move towards graduation: 
+ A list of the three most important issues to address in the move towards
+ graduation:
+ 
-    * Add new committers.
+   - Add new committers.
-    * Further improve the documentations: user, development for quicker adoption.
+   - Further improve the documentations: user, development for quicker adoption.
-    * Automate the formal release process. 
+   - Automate the formal release process. 
  
- * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: 
+ Any issues that the Incubator PMC or ASF Board might wish/need to be aware of: 
+ 
-     * No issues.
+   - No issues.
  
- * How has the community developed since the last report:
+ How has the community developed since the last report:
+ 
-    * Oozie dev/users are active in the email lists (around 2000+ Emails in oozie-dev and
300+ in oozie-user).
+   - Oozie dev/users are active in the email lists (around 2000+ Emails in
+     oozie-dev and 300+ in oozie-user).
-    * In last one month, 67 JIRAs were created and 49 were resolved.
+   - In last one month, 67 JIRAs were created and 49 were resolved.
- * 2 new developers from 2 new companies are contributing to coding.
+   - 2 new developers from 2 new companies are contributing to coding.
         
- * How has the project developed since the last report: 
+ How has the project developed since the last report: 
+ 
-        * The first Oozie release (3.1.3) from Apache incubator has been successfully released.

+   - The first Oozie release (3.1.3) from Apache incubator has been
+     successfully released. 
-         * A new release (3.2) process is started. The new branch is created. 
+   - A new release (3.2) process is started. The new branch is created. 
-         * Cookbook like documentation was added to Oozie product web page.
+   - Cookbook like documentation was added to Oozie product web page.
- 
- 
  
  Signed off by mentor: Devaraj Das
  
@@ -524, +646 @@

  
  Out-of-Band Report
  
- On March 22nd we issued a security bulletin and patch for a vulnerability reported in OpenOffice.org
3.3, the last released pre-Apache version of OpenOffice.
+ On March 22nd we issued a security bulletin and patch for a vulnerability
+ reported in OpenOffice.org 3.3, the last released pre-Apache version of
+ OpenOffice.
  
  Technical details of the issue and patch can be found in this announcement:
  
  http://mail-archives.apache.org/mod_mbox/incubator-ooo-announce/201203.mbox/%3CCAP-ksoj7o5%2B2YH-E4XzR044V0e3YZfZvuef7eJuNGhdy%2Bk9kyA%40mail.gmail.com%3E
  
- The IPMC and Board should note that this extraordinary patch was made available, as a courtesy
to the ecosystem, based on the severity of the reported vulnerability and the ease of exploiting
it.  The patch was made available under ALv2, and distribution was done via the Apache mirrors,
although this did not constitute an official release.
+ The IPMC and Board should note that this extraordinary patch was made
+ available, as a courtesy to the ecosystem, based on the severity of the
+ reported vulnerability and the ease of exploiting it.  The patch was made
+ available under ALv2, and distribution was done via the Apache mirrors,
+ although this did not constitute an official release.
  
- Because of the required secrecy around the preparation of such security patches, a minimum
number of Apache members were involved in vetting this release, though we did try to touch
all bases by involving mentors, Infra and Legal Affairs.
+ Because of the required secrecy around the preparation of such security
+ patches, a minimum number of Apache members were involved in vetting this
+ release, though we did try to touch all bases by involving mentors, Infra
+ and Legal Affairs.
  
  Signed off by mentor: joes
  
  --------------------
- 
- 
  Syncope
  
  Apache Syncope is an Open Source system for managing digital identities in
@@ -547, +676 @@

  
  Community Development:
  
- Older Syncope users-base is (not really quickly) migrating to the new ASF infrastructure,
user@ ML activity is low.
+   Older Syncope users-base is (not really quickly) migrating to the new ASF   infrastructure,
user@ ML activity is low.
  
  Project Development:
  
- Commits activity is healthy, commits@ ML activity is high.
+   Commits activity is healthy, commits@ ML activity is high.
  
- Committers are working towards the first release.
+   Committers are working towards the first release.
  
  Web Site/Communication Development:
  
- The website is kept up-to-date on http://incubator.apache.org/syncope/
+   The website is kept up-to-date on http://incubator.apache.org/syncope/
- Status page http://incubator.apache.org/projects/syncope.html is updated
+   Status page http://incubator.apache.org/projects/syncope.html is updated
  
- It introduces Syncope and provide first content.
+   It introduces Syncope and provide first content.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of:
  
- None so far.
+   None so far.
  
  Signed off by mentor: simonetripodi
  
@@ -583, +712 @@

  
  Recent activities:
  
- * change of the focus of the project (the previous focus was to be
+   - change of the focus of the project (the previous focus was to be
-   flexible wrt the representation of the data model, the new focus
+     flexible wrt the representation of the data model, the new focus
-   is parallel processing of large amounts of XML data)
+     is parallel processing of large amounts of XML data)
- * re-newed development activity
+   - re-newed development activity
- * 2 proposals for GSoC (1 person expressed interest in working on
+   - 2 proposals for GSoC (1 person expressed interest in working on
-   VXQuery for GSoC)
+     VXQuery for GSoC)
  
  Top issues before graduation:
  
- * Build community
+   - Build community
+ 
-   - VXQuery's community is still the initial (very small) community
+     VXQuery's community is still the initial (very small) community
-   - The goal of the change of focus to attract more interest in the
+     The goal of the change of focus to attract more interest in the
      project and to increase the size and diversity of the community
+ 
- * Create a release
+   - Create a release
  
  Signed off by mentor:
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message