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: Mon, 03 Apr 2017 02:52:05 -0000
Message-ID: <149118792562.24901.11328529554465954893@moin-vm.apache.org>
Subject: =?utf-8?q?=5BIncubator_Wiki=5D_Update_of_=22April2017=22_by_MarvinHumphre?=
 =?utf-8?q?y?=
Auto-Submitted: auto-generated
archived-at: Mon, 03 Apr 2017 02:52:13 -0000

Dear Wiki user,

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

The "April2017" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/April2017?action=3Ddiff&rev1=3D17&rev2=3D=
18

Comment:
Reflow Gobblin, Gossip, Griffin, HAWQ, MADlib.

  ecosystems.
  =

  Gobblin has been incubating since 2017-02-23.
+ =

  Few first steps has been made:
+ =

  * mailing list setup
  * jira setup
  * few Apache account creation for new committers.
@@ -437, +439 @@

  =

  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?
+ =

- We are very first steps of the project
+   We are very first steps of the project
  =

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

- First report :-)
+   First report :-)
  =

  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
@@ -459, +465 @@

  =

  When were the last committers or PPMC members elected?
   =

-  N/A
+   N/A
- =

- =

  =

  Signed-off-by:
  =

@@ -484, +488 @@

  =

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

-   1. A project leveraging Apache Gossip such as https://issues.apache.org=
/jira/browse/IGNITE-4837
+   1. A project leveraging Apache Gossip such as
+      https://issues.apache.org/jira/browse/IGNITE-4837
-   2. Two additional active committers to handle management tasks like cod=
e review
+   2. Two additional active committers to handle management tasks like code
+      review
    3. Continued releases
  =

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

-   Two students are submitting proposals for Google Summer of Code. Both h=
ave already
+   Two students are submitting proposals for Google Summer of Code. Both h=
ave
-   contributed features which were committed to the project. We are hopefu=
lly they both proposals
+   already contributed features which were committed to the project. We are
-   will be accepted.
+   hopefully they both proposals will be accepted.
  =

  How has the community developed since the last report?
  =

-   The mailing list has been active with several people who were drawn to =
the project by
+   The mailing list has been active with several people who were drawn to =
the
-   GSOC 17 labels placed on our tickets. Two of them have contributed feat=
ures that have
-   been committed, and a third person (who will not be doing GSOC) has ask=
ed to be assigned
-   a ticket. Our last release had roughly 5 different contributors, The ma=
iling list is =

+   project by GSOC 17 labels placed on our tickets. Two of them have
+   contributed features that have been committed, and a third person (who =
will
+   not be doing GSOC) has asked to be assigned a ticket. Our last release =
had
+   roughly 5 different contributors, The mailing list is fairly active as =
we
-   fairly active as we review GSOC proposals. We have more than 50 stars o=
n github which
+   review GSOC proposals. We have more than 50 stars on github which shows
-   shows that visibility is making a steady climb.
+   that visibility is making a steady climb.
  =

  How has the project developed since the last report?
  =

-   A release 0.1.1 was completed right before our last report. We made an =
aggressive list of =

+   A release 0.1.1 was completed right before our last report. We made an
-   features for 0.1.2. We de-prioritized some of the items, but we complet=
ed far
-   more than we expected. We had improvements in performance, testing, =

-   and features. CRDT support seemed to be the biggest 'splash' feature.
+   aggressive list of features for 0.1.2. We de-prioritized some of the it=
ems,
+   but we completed far more than we expected. We had improvements in
+   performance, testing, and features. CRDT support seemed to be the bigge=
st
+   'splash' feature.
  =

  How would you assess the podling's maturity?
  =

-   I am happy with the continued feature development and code/test improve=
ment. We are attracting
+   I am happy with the continued feature development and code/test
-   interest of some new developers who seem likely to stay involved and po=
tentially be committers =

+   improvement. We are attracting interest of some new developers who seem
+   likely to stay involved and potentially be committers in the future. Wh=
ile
-   in the future. While the majority of management and reviews is done by =
a few, others are beginning
+   the majority of management and reviews is done by a few, others are
-   to help with tasks like code reviews. As pointed out in the "move towar=
ds graduation" section, =

+   beginning to help with tasks like code reviews. As pointed out in the "=
move
-   having a couple other highly active reviewers/committers would be a pos=
itive next step.
+   towards graduation" section, having a couple other highly active
+   reviewers/committers would be a positive next step.
  =

  Please feel free to add your own commentary.
  =

@@ -540, +550 @@

    [ ](gossip) P. Taylor Goetz
       Comments:
    [x](gossip) Josh Elser
+      Comments:
-      Comments: The podling is still working to attract new members, but t=
hose involved so far are doing well.
+         The podling is still working to attract new members, but those
+         involved so far are doing well.
    [ ](gossip) Drew Farris
       Comments:
  =

@@ -567, +579 @@

  =

      None
  =

- =

  How has the community developed since the last report?
  =

-     Two new contributors on-boarded, several developers had contacted us =
for plan, milestones, status and use cases.
+     Two new contributors on-boarded, several developers had contacted us =
for
+     plan, milestones, status and use cases.
  =

  How has the project developed since the last report?
    - Active development started in the community. 24 commits in last month.
    - The project setup is going quite well. Initial committers are onboard=
ing,
      JIRA, Website, mailing list were successfully done.
-   - Work toward next gen version (general enough) is progressing substant=
ially.
+   - Work toward next gen version (general enough) is progressing
+     substantially.
  =

  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
@@ -709, +722 @@

         * Bug Fixes
  =

    3. Paul Guo (paulguo@gmail.com - committer and recent HAWQ PPMC
-      member) is publishing (to dev email list) a regular HAWQ Graduation =
update for the
+      member) is publishing (to dev email list) a regular HAWQ Graduation
-      project.
+      update for the project.
    =

       * HAWQ graduation update (January, 17, 2017)
         https://lists.apache.org/thread.html/cd37e2b48d4bbc9fe4a9cea47f824=
7a2a614fa9643171937db9568ed@%3Cdev.hawq.apache.org%3E
@@ -893, +906 @@

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

    1. Continue to produce regular Apache (incubating) releases.
-   2. Continue to execute and manage the project according to governance m=
odel of the "Apache Way=E2=80=9D.
+   2. Continue to execute and manage the project according to governance m=
odel
+      of the "Apache Way".
    3. Continue to build community.
  =

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

-  1. The next release v1.11 will be the 5th as an incubating project.  We =
believe this release will meet all requirements for a clean ASF release, ba=
sed on listening to guidance from the IPMC over the previous releases.  Aft=
er that, the community would ideally like to move towards top level status.
-  2.  The licensing issues have been resolved.  Should anyone want to revi=
ew, we have summarized the issue and resolution with relevant links on the =
MADlib wiki at
+   1. The next release v1.11 will be the 5th as an incubating project.  We
+      believe this release will meet all requirements for a clean ASF rele=
ase,
+      based on listening to guidance from the IPMC over the previous relea=
ses.
+      After that, the community would ideally like to move towards top lev=
el
+      status.
+   2. The licensing issues have been resolved.  Should anyone want to revi=
ew,
+      we have summarized the issue and resolution with relevant links on t=
he
+      MADlib wiki at
- https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance
+      https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Gui=
dance
  =

  How has the community developed since the last report?
  =

    1. Some related events in Q1 2017: =

-       * Feb 4, 2017 - Presentation at FOSDEM=E2=80=9917 Graph devroom.  T=
opic:  Graph Analytics on Massively Parallel Processing Databases (Frank Mc=
Quillan)
- 	* Feb 2, 2017 - Greenplum meetup in SF.  Topic:  Machine Learning and Cy=
ber Security with Greenplum and Apache MADlib (Anirudh Kondaveeti, Frank Mc=
Quillan)
+      * Feb 4, 2017 - Presentation at FOSDEM=E2=80=9917 Graph devroom.  To=
pic:  Graph
+        Analytics on Massively Parallel Processing Databases (Frank McQuil=
lan)
+      * Feb 2, 2017 - Greenplum meetup in SF.  Topic:  Machine Learning and
+        Cyber Security with Greenplum and Apache MADlib (Anirudh Kondaveet=
i,
+        Frank McQuillan)
- 	* Mar 23, 2017 - MADlib community call.  Topic:  New Features in Apache =
MADlib 1.10 (Frank McQuillan)
+      * Mar 23, 2017 - MADlib community call.  Topic:  New Features in Apa=
che
+        MADlib 1.10 (Frank McQuillan)
-   2. See material technical conversations on user/dev mailing lists and i=
n the appropriate JIRAs and pull requests.
+   2. See material technical conversations on user/dev mailing lists and in
+      the appropriate JIRAs and pull requests.
  =

  How has the project developed since the last report?
  =

+   1. Build infra set up on Apache infra
-   1. Build infra set up on Apache infra https://builds.apache.org/job/mad=
lib-master-build/
+      https://builds.apache.org/job/madlib-master-build/
-   2. Docker image with necessary dependencies required to compile and tes=
t MADlib on PostgreSQL 9.6 https://cwiki.apache.org/confluence/display/MADL=
IB/Quick+Start+Guide+for+Developers#QuickStartGuideforDevelopers-Dock
-   3. Active work in progress for 5th ASF release MADlib v1.11 scheduled f=
or Apr 2017.  Features include: PageRank, connected components, stratified =
sampling, improvements to decision tree & random forest, array & sparse vec=
tor output for pivot
+   2. Docker image with necessary dependencies required to compile and test
+      MADlib on PostgreSQL 9.6
+      https://cwiki.apache.org/confluence/display/MADLIB/Quick+Start+Guide=
+for+Developers#QuickStartGuideforDevelopers-Dock
+   3. Active work in progress for 5th ASF release MADlib v1.11 scheduled f=
or
+      Apr 2017.  Features include: PageRank, connected components, stratif=
ied
+      sampling, improvements to decision tree & random forest, array & spa=
rse
+      vector output for pivot
-   4. Mailing list activity in Q1 to date:  274 postings to dev, 111 posti=
ngs to user.
+   4. Mailing list activity in Q1 to date:  274 postings to dev, 111 posti=
ngs
+      to user.
  =

  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
@@ -933, +965 @@

  When were the last committers or PMC members elected:
  =

    Orhan Kislal on 9/7/16 and Nandish Jayaram on 9/7/16.
- =

  =

  Signed-off-by:
 =20

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