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 Thu, 12 Apr 2012 23:52:14 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=79&rev2=80

Comment:
Finishing touches, including simple spell-checking and minor formatting

  
  ----
  {{{
- TODO: preamble
+ The biggest Incubator news since our last report is the CloudStack project
+ seeking to enter the ASF. This and other topics as summarized below have
+ kept us busy lately. At times the related discussions have gotten a bit
+ heated, but for the most part the Incubator is functioning reasonably well.
+ 
+ The overall trend currently is for more podlings to graduate than are coming
+ in as newly proposed projects. Given the backlog of stuck projects and the
+ recent focus on pushing then forward this trend can be expected to continue
+ at least for the next few months.
  
  o Community
  
@@ -33, +41 @@

  
    We received a proposal to accept the CloudStack project as a new podling.
    The proposal has received quite a bit of excitement and many volunteer
-   mentors. On the other hand there were some concerns regarding the handling
+   mentors. On the other hand there were some concerns about the publicity
-   of publicity around the proposal (current Incubator policy prohibits
+   around the proposal (current Incubator policy prohibits publicity-seeking
-   publicity-seeking in the proposal phase) and especially the handling of
+   in the proposal phase). Another issue of note is the handling of patents
-   patents was raised as a potential issue for the proposed podling. The
+   that was raised as a potential issue for the proposed podling. The vote
-   vote to accept CloudStack for incubation is currently in progress.
+   to accept CloudStack for incubation is currently in progress.
+ 
+ o Legal / Trademarks
+ 
+   The Flex podling continues working on a custom trademark licensing deal
+   with Adobe. See the Flex report for mode details.
+ 
+   A point was raised about including the project branding checklist in
+   podling graduation criteria. This seems like a useful change, though the
+   details are still to be worked out.
  
  o Releases
  
@@ -46, +63 @@

    - March 12th, 2012: Apache Tashi 201203-incubating
    - March 20th, 2012: Apache Rave 0.9-incubating
    - March 23rd, 2012: Apache Jena Fuseki 0.2.1-incubating
-   - March 27th, 2012: Apacle Flume 1.1.0-incubating
+   - March 27th, 2012: Apache Flume 1.1.0-incubating
    - April 2nd, 2012: Apache Bigtop 0.3.0-incubating
  
    Apache OpenOffice used Apache mirrors to distribute binary security
@@ -119, +136 @@

    IP clearance: -
    No release: Any23, Cordova, DirectMemory, Flex, JSPWiki, Mesos, OpenOffice
    Low activity: AWF, Celix, EasyAnt, Kitty, VXQuery
-   Low diversity: Chuckwa, Kafka, ODF Toolkit, Oozie, Tashi
+   Low diversity: Chukwa, Kafka, ODF Toolkit, Oozie, Tashi
  
    We expect the next quarterly report of projects in this category to
    include a summary of their actions and progress in solving these issues. 
@@ -142, +159 @@

    - Microformats: Adr, Geo, hCalendar, hCard, hListing, hResume, hReview,
      License, XFN and Species
    - HTML5 Microdata: (such as Schema.org)
-   - CSV: Comma Separated Values with separator autodetection.
+   - CSV: Comma Separated Values with separator auto-detection.
  
  Any23 was voted into the Incubator by the IPMC on October 1, 2011.
  
@@ -223, +240 @@

  
  Graduation concerns:
  
-  - official apache release remains to be verified
+  - official Apache release remains to be verified
  
  Signed off by mentor: jukka
  
@@ -244, +261 @@

  
  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
+   - Update/Implement remote services for interoperability with Java OSGi
-    (Apache Felix)
+     (Apache Felix)
-  - Generate awareness and grow a community!
+   - Generate awareness and grow a community!
  
  Graduation Plan
  
@@ -264, +281 @@

  
  State of the project
  
-  - Releases
+   - Releases
  
-    Celix entered incubation in its early stage. There was only a proof of
+     Celix entered incubation in its early stage. There was only a proof of
-    concept, but no complete implementation. This is an important reason for
+     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,
+     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
+     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
+     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
+     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
+     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
+     core component of Celix. Hopefully this will attract more users/testers
-    (and potentially committers). Since a formal release takes quite some
+     (and potentially committers). Since a formal release takes quite some
-    effort, it might also make sense to provide snapshots (with documentation)
+     effort, it might also make sense to provide snapshots (with documentation)
-    to be able to reach more people.
+     to be able to reach more people.
  
-  - Committers
+   - Committers
  
-    During the last months there has been an interest from Thales Netherlands
+     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
+     to use Celix in its middleware. In a research project they are working on
-    an implementation of the Device Access specification. This implementation
+     an implementation of the Device Access specification. This implementation
-    is donated to Celix, and the main developer has expressed the intention
+     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 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
+     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
+     committers are needed. Having a release makes it easier for people to use
-    and improve Celix. This is one step towards more committers.
+     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
+     One of the important aspects of Celix is interoperability with Java OSGi
-    through remote services. Currently Celix has basic support for Celix to
+     through remote services. Currently Celix has basic support for Celix to
-    Celix remote services, following the Remote Service Admin specification
+     Celix remote services, following the Remote Service Admin specification
-    of OSGi. This implementation has to be improved and extended to comply
+     of OSGi. This implementation has to be improved and extended to comply
-    better to the specification. Also a Java OSGi implementation has to be
+     better to the specification. Also a Java OSGi implementation has to be
-    made which can interact with the Celix implementation. Some existing
+     made which can interact with the Celix implementation. Some existing
-    opensource solutions are available, but are either to large for our
+     open source solutions are available, but are either to large for our
-    intended target platforms or rely on to many other libraries (for
+     intended target platforms or rely on to many other libraries (for
-    example XML handling etc). To be able to have an implementation which
+     example XML handling etc). To be able to have an implementation which
-    fits the environment ((de)serialization and protocol) it makes sense to
+     fits the environment ((de)serialization and protocol) it makes sense to
-    implement a simple solution ourselves. Having functional remote services
+     implement a simple solution ourselves. Having functional remote services
-    makes it easier to use Celix in a mixed Java/C environment. This solution
+     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
+     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
+     Java and C components are separate processes. If either one crashes the
-    other part is kept running, resulting in a more robust solution.
+     other part is kept running, resulting in a more robust solution.
   
  C++ Support
  
@@ -320, +337 @@

      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.
+     discussions has been made on the mailing list, see [2] for more information.
  
      [3]: http://markmail.org/thread/a3qltqhsocmrnerd
  
@@ -384, +401 @@

  
  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
+ 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
@@ -398, +415 @@

  How has the community developed since the last report
  
    - Tasks and proposals contributed by non-committers
-   - The team has upvoted a new committer
+   - The team has up-voted a new committer
  
  How has the project developed since the last report.
  
@@ -412, +429 @@

  --------------------
  EasyAnt
  
- Easyant is a build system based on Apache Ant and Apache Ivy. Incubating since 2011-01-31.
+ EasyAnt is a build system based on Apache Ant and Apache Ivy. Incubating since 2011-01-31.
  
  Towards graduation, we need to:
  
@@ -422, +439 @@

  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.
+   low. Some discussion with developers and mentors raised about this concern.
-   Developpers acknowledged that the current code refactoring make it's build
+   Developers acknowledged that the current code refactoring make it's build
-   break too much to keep people interested in contributing. Developpers are
+   break too much to keep people interested in contributing. Developers 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.
@@ -475, +492 @@

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

  The project had some contribution as far as code is concerned, but the
  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.
+ re-engineering in order to begin working on the missing features.
  
  Signed off by mentor: kevan
  
@@ -783, +800 @@

  Tashi has been incubating since September 2008.
  
  The Tashi project aims to build a software infrastructure for cloud computing 
- on massive internet-scale datasets (what we call Big Data). The idea is to 
+ on massive internet-scale data sets (what we call Big Data). The idea is to 
  build a cluster management system that enables the Big Data that are stored in 
  a cluster/data center to be accessed, shared, manipulated, and computed on by 
  remote users in a convenient, efficient, and safe manner.
@@ -818, +835 @@

  the advice posted to general@apache.incubator.org, as well as create
  web pages demonstrating the project's utility, provide sample VM images
  and disseminate other information relating to the deployments close to him.
- He will also urge others to make similar information publically available.
+ He will also urge others to make similar information publicly available.
  
  One of our users has requested the creation of a private branch for his
  team to work on. Perhaps this will result in a valuable feature addition
@@ -842, +859 @@

    - change of the focus of the project (the previous focus was to be
      flexible wrt the representation of the data model, the new focus
      is parallel processing of large amounts of XML data)
-   - re-newed development activity
+   - renewed development activity
    - 2 proposals for GSoC (1 person expressed interest in working on
      VXQuery for GSoC)
  

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


Mime
View raw message