incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1653430 - /incubator/public/trunk/data/reporting/2015-01.yaml
Date Wed, 21 Jan 2015 03:52:08 GMT
Author: adc
Date: Wed Jan 21 03:52:08 2015
New Revision: 1653430

Added ODF Toolkit report


Modified: incubator/public/trunk/data/reporting/2015-01.yaml
--- incubator/public/trunk/data/reporting/2015-01.yaml (original)
+++ incubator/public/trunk/data/reporting/2015-01.yaml Wed Jan 21 03:52:08 2015
@@ -625,7 +625,49 @@ reports:
       apurtell: true
       robweir: |
+        My concern is the same as before.   IMHO we've grown too comfortable
+        being a podling.   We're able to do everything we want to do as a
+        podling, have a website, check in code, make releases, etc.   I'm not
+        really feeling any urgency from committers or PPMC members to push
+        this project through to the next steps needed for graduation.
+        Advantages of being a Top Level Project at Apache include:
+        1) Less process overhead for releasing.   We still need to check all
+        of the items, but we're then trusted to do this on our own without
+        additional IPMC review.
+        2) Our releases would no longer have the Incubation disclaimer in the
+        release notes
+        3) We'd get a top level URL for the website, and a
+        shortened mailing list address,
+        4) We'd have more freedom to do publicity via press releases, etc.
+        5) We'd  still need to do quarterly reports, but these would go
+        directly to the Apache Board.
+        Although none of these by themselves are huge, take together it is a
+        nice bundle of perks.   And it really signifies that, as a community,
+        we understand The Apache Way, the release procedures and are able to
+        sustain the community.
+        In our report this month we list the three most important things to do
+        on the way to graduation:
+        1. Grow the community in terms of committers
+        2. Have regular releases
+        3. Decide if we would like to be a top level project or join an existing
+           project, or move to the attic.
+        Any proposals on what we can do for #1 and #2?   For example, do we
+        have any contributed patches we still need to integrate?   Are there
+        other ways we could think of for publicizing the project, and
+        attracting additional volunteers?
       tnachen: |
         It seems like the project is active in release and code (towards the low activity
         However the mailing list traffic and engagement has decreased overtime and the

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message