Mailing-List: contact cvs-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 12 Dec 2017 14:06:19 -0000
Message-ID: <151308757967.16990.14588076088241859606@moin-vm.apache.org>
Subject: =?utf-8?q?=5BIncubator_Wiki=5D_Update_of_=22December2017=22_by_johndament?=
Auto-Submitted: auto-generated
archived-at: Tue, 12 Dec 2017 14:06:25 -0000

Dear Wiki user,

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

The "December2017" page has been changed by johndament:
https://wiki.apache.org/incubator/December2017?action=3Ddiff&rev1=3D50&rev2=
=3D51

Comment:
Posting AriaTosca, sign off and comments.

  =

  Three most important issues to address in the move towards graduation:
  =

-   1.
-   2.
-   3.
+   1. Grow the community and enroll new committers.
+   2. Have frequent Release cycles to be compliant with the Apache Way.
+   3. Grow the project=E2=80=99s contributions from existing contributors
  =

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  =

+   The project is ready for its third release as far as the code is concer=
ned.  Considerable functionality has been added since the last release in a=
ddition to a growth in diversity of contributions.
  =

- =

- How has the community developed since the last report?
- =

- =

- =

- How has the project developed since the last report?
+ How has the community developed since the last report?
  =

+   * All project communication takes now place on either the mailing list =
or ASF's Slack, and is open for everybody.  We have worked hard to make thi=
s the normal operating mode of the community. There have been some hiccups,=
 but in general the majority of discourse has taken place on the list.  Sla=
ck has been used as a secondary method.
+   * Increased chatter on the mailing list including new subscribers who a=
sk questions, make suggestions and are likely to become contributors themse=
lves in the near future.
+   * Weekly grooming meetings are now attended by the majority of the comm=
unity. This is not only a forum to review the weekly work items list, but a=
lso as a place for open discussion about issues, questions as well as for t=
he community to get to better know each other.
+   * Over the last 3 months we have seen an over %50 increase in contribut=
ors and the existing group of committers voted to elect a new Committer to =
the project.
+ =

+ How has the project developed since the last report?
+ =

+   - ARIA now has a robust parser testing framework (ARIA-1)
+   - Huge performance improvement (ARIA-1)
+   - Significant website and documentation improvements for usability and =
to enhance new user Usability in terms of =E2=80=9Cgetting started=E2=80=9D=
 instructions
+   - Clearwater IMS Example
+   - Package names fixed/made consistent
+   - Configuration loading mechanism
+   - Removed support for Python 2.6
+   - 42 JIRA issues have been resolved since the last report
+   - Moved project to gitbox
  =

  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
  =

    [ ] Initial setup
    [ ] Working towards first release
-   [ ] Community building
+   [X] Community building
    [ ] Nearing graduation
    [ ] Other:
  =

  Date of last release:
  =

-   XXXX-XX-XX
+   2017-07-13 0.1.1
  =

  When were the last committers or PPMC members elected?
  =

- =

+   Tom Nadeau was added to the PMC/committers on 2017-11-28
  =

  Signed-off-by:
  =

    [ ](ariatosca) Suneel Marthi
       Comments:
-   [ ](ariatosca) John D. Ament
+   [X](ariatosca) John D. Ament
-      Comments:  Activity on list is picking up over the slack conversatio=
ns.  A community member is planning to write a report, however it indicates=
 a corporate hierarchy issue within the project that needs to get solved.
+      Comments:  Activity on list is picking up over the slack conversatio=
ns.  A community member is planning to write a report, however it indicates=
 a corporate hierarchy issue within the project that needs to get solved.  =
In addition, the podling needs to figure out how to operate more on list (w=
ithout grooming meetings) and do things more asynchronously.
    [ ](ariatosca) Jakob Homan
       Comments:
 =20

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