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 "January2019" by Justin Mclean
Date Wed, 09 Jan 2019 07:59:58 GMT
Dear Wiki user,

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

The "January2019" page has been changed by Justin Mclean:
https://wiki.apache.org/incubator/January2019?action=diff&rev1=63&rev2=64

Comment:
final and reflow

  = Incubator PMC report for January 2019 =
+ 
+ ** FINAL DO NOT EDIT **
  
  === Timeline ===
  ||Wed January 02 ||Podling reports due by end of day ||
@@ -45, +47 @@

  graduation. An incubator exit interview was sent to Airflow and the IPMC 
  got some feedback on the incubating process. It highlighted a known 
  issue with releases that needs to be made clear to mentors and PPMCs (as a 
- number of podlings have recently run into the same issue). A discussion will 
+ number of podlings have recently run into the same issue). A discussion 
+ will 
  be started soon about this.
  
  Several new podlings are off to a slow start. BatchEE is still stuck in 
  performing the last graduation steps, but the PPMC have said they will get 
  to it in February.
  
- One new podling Iceberg failed to report and will be asked to report next 
- month. Both podlings that failed to report last month reported this month.
+ One new podling Iceberg reported very late. Both podlings that failed to
+ report last month reported this month.
  
  There were 2 IP clearances.
  
@@ -119, +122 @@

    and develop training and related materials for ASF projects.
    - A release checklist application was created and has had a few people 
    take interest in it.
+ 
  ----------------------------------------------------------------------
                         Table of Contents
  Amaterasu
@@ -168, +172 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware 
  of?
  
-   There is still concern regarding the progress of the project, a discussion was re-initiated
by one of the mentors recently and is currently ongoing.
+   There is still concern regarding the progress of the project, a 
+   discussion was re-initiated by one of the mentors recently and is currently 
+   ongoing.
  
  How has the community developed since the last report?
  
@@ -204, +210 @@

    [X](amaterasu) Olivier Lamy
       Comments:
    [X](amaterasu) Davor Bonaci
-      Comments: No progress this quarter on project viability / graduation not in sight.
+      Comments: No progress this quarter on project viability / graduation 
+      not in sight.
  
  IPMC/Shepherd notes:
  
@@ -218, +225 @@

  
  Three most important issues to address in the move towards graduation:
  
-  1. Release initial versions
+   1. Release initial versions
-  2. Add active contributors
+   2. Add active contributors
-  3. Demonstrate good governance through voting on process improvements.
+   3. Demonstrate good governance through voting on process improvements.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
@@ -270, +277 @@

  Signed-off-by:
  
    [x](annotator) Nick Kew
-      Comments: Memory is hazy (I've been unwell the past week).  I think the above is a
fair summary: the successful effort to recruit new mentors was a positive episode.  The subject
of growing the PMC has been raised, and the project wishes to distinguish between those with
a real interest (PMC) vs those whose contributions may have been of a more drive-by nature
but who might nevertheless be made committers.
+      Comments: Memory is hazy (I've been unwell the past week).  I think 
+      the above is a fair summary: the successful effort to recruit new mentors 
+      was a positive episode.  The subject of growing the PMC has been raised, 
+      and the project wishes to distinguish between those with a real interest 
+      (PMC) vs those whose contributions may have been of a more drive-by nature 
+      but who might nevertheless be made committers.
    [ ](annotator) Steve Blackmon
       Comments:
    [ ](annotator) Tommaso Teofili
@@ -284, +296 @@

  --------------------
  BatchEE
  
-              BatchEE projects aims to provide a JBatch implementation (aka
+ BatchEE projects aims to provide a JBatch implementation (aka
- JSR352)             and a set of useful extensions for this specification.
+ JSR352) and a set of useful extensions for this specification.
  
  BatchEE has been incubating since 2013-10-03.
  
@@ -366, +378 @@

  
  How has the project developed since the last report?
  
-   We have finished the sign of SGA and ICLA, setup dev@brpc.apache.org email 
+   We have finished the sign of SGA and ICLA, setup dev@brpc.apache.org 
-   list, and add Gosling Von as our mentors.
+   email list, and add Gosling Von as our mentors.
    And begin to transfer repo.
  
  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
  
-   [X ] Initial setup
+   [X] Initial setup
    [ ] Working towards first release
    [ ] Community building
    [ ] Nearing graduation
@@ -489, +501 @@

  
  IPMC/Shepherd notes:
    Justin Mclean: Given that 92% of commit are from non-committers why does
-   the project not vote more committers in? I can only see one committer voted
+   the project not vote more committers in? I can only see one committer 
-   in in the previous year. For a project nearing graduation I'd expect to
+   voted in in the previous year. For a project nearing graduation I'd expect
-   see a lot more people voted in. I also don't see what is discussed in the
+   to see a lot more people voted in. I also don't see what is discussed in the
    video conferences being brought back to the list.
  
  --------------------
@@ -504, +516 @@

  Three most important issues to address in the move towards graduation:
  
    1. Finish the name clearance and trademark agreement.
+   2. Make the first Apache release. 
-   2. Make the first Apache release. (https://github.com/apache/incubator-iceberg/milestone/1)
+ (https://github.com/apache/incubator-iceberg/milestone/1)
    3. Grow the Iceberg community
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
-   * Gitbox traffic is now going to issues@. The community was losing dev@ subscribers
+   * Gitbox traffic is now going to issues@. The community was losing dev@ 
-     because of the high volume of traffic from Gitbox. However, now all updates are sent
+     subscribers because of the high volume of traffic from Gitbox. However,
-     to issues@. It would be nice to have emails from creation go to dev@, while updates
-     and resolutions would go the issues@.
+     now all updates are sent to issues@. It would be nice to have emails
+     from creation go to dev@, while updates and resolutions would go the
+     issues@.
-   * The trademark agreement proposed by Netflix was not acceptable to the ASF. It
+   * The trademark agreement proposed by Netflix was not acceptable to the 
-     would be helpful if the ASF published the terms that the ASF requires to avoid trial
+     ASF. It would be helpful if the ASF published the terms that the ASF
-     and error. Netflix is drafting a new agreement.
+     requires to avoid trial and error. Netflix is drafting a new agreement.
  
  How has the community developed since the last report?
  
-   * Moved gitbox notifications to avoid loss of dev@ subscribers (self-reported leaving
dev@).
+   * Moved gitbox notifications to avoid loss of dev@ subscribers 
+   (self-reported leaving dev@).
    * New contributor activity: 3 new issues opened, 4 PRs submitted
    * 5 PRs from non-committers merged
    * 2 contributors started reviewing PRs
@@ -531, +546 @@

  
    * Planned blockers for first release, 0.1.0, in milestone 1
    * Partial python implementation submitted
-   * Manifest listing file added to the spec and implementation committed (blocker for initial
release). Resulted in a significant improvement in query planning time for large tables.
+   * Manifest listing file added to the spec and implementation committed 
+   (blocker for initial release). Resulted in a significant improvement in 
+   query planning time for large tables.
    * Abstracted file IO API to support community use cases
-   * Reviewing community proposal for external plugins to support file-level encryption
+   * Reviewing community proposal for external plugins to support file-level 
+   encryption
    * Added doc strings to schemas
  
  How would you assess the podling's maturity?
@@ -558, +576 @@

  that need to be addressed.
  
    Last month was December, so traffic has been low and both PPMC members and
-   mentors were slow to respond. This is not abnormal, but the PPMC missed the
+   mentors were slow to respond. This is not abnormal, but the PPMC missed 
-   deadline to file this report. We will ensure this doesn't recur.
+   the deadline to file this report. We will ensure this doesn't recur.
  
  Signed-off-by:
  
@@ -595, +613 @@

  
  How has the community developed since the last report?
  
-   - A meetup titled by "The way of Open Source Software in China" is hold at 
+   - A meetup titled by "The way of Open Source Software in China" is hold 
-   2018.12.19. 
+   at 2018.12.19. 
    - 122 emails are archived in the dev mail list
    - The website is available (http://iotdb.apache.org) now
    - Have a  touch with Apache RocketMQ community
  
  How has the project developed since the last report?
  
-   - Many ICLA files have signed, and the SGA is signed. So, the IP clearance 
+   - Many ICLA files have signed, and the SGA is signed. So, the IP 
-   is done.
+   clearance is done.
    - 29 PR are merged.
  
  How would you assess the podling's maturity?
@@ -615, +633 @@

    - We will speed up to move codes to apache repository and try to release 
    the first version. 
  
-   [ x ] Initial setup
+   [X] Initial setup
    [ ] Working towards first release
    [ ] Community building
    [ ] Nearing graduation
@@ -655, +673 @@

  
  Livy is web service that exposes a REST interface for managing long running
  Apache Spark contexts in your cluster. With Livy, new applications can be
- built on top of Apache Spark that requires fine grained interaction with many
+ built on top of Apache Spark that requires fine grained interaction with 
+ many
  Spark contexts.
  
  Livy has been incubating since 2017-06-05.
@@ -874, +893 @@

    (C) Guide how the output code/document should be.
  
    Mentors or a person who will lead the communication are requested to 
-   submit a ping message on the mailing list regularly that asks any blockers.
+   submit a ping message on the mailing list regularly that asks any 
+ blockers.
  
  Signed-off-by:
  
    [x](milagro) Nick Kew
-      Comments: Great summary.  Sadly the author appears to be the only community
+      Comments: Great summary. Sadly the author appears to be the only 
-      member still to have a really active interest.
+      community member still to have a really active interest.
  
  IPMC/Shepherd notes:
    Justin Mclean:Rather than asking the mentors to ping you I suggest you ask
@@ -951, +971 @@

    2) Completed vote for 1.4.0 release on dev@: 
    https://github.com/apache/incubator-mxnet/releases/tag/1.4.0; 
     
-   https://lists.apache.org/thread.html/236554041a412415df783d652830272beb21d36
+ https://lists.apache.org/thread.html/236554041a412415df783d652830272beb21d36
  660e8e0d5e0237f58@%3Cdev.mxnet.apache.org%3E
     Started vote on general@ on December 28, 2018: 
  https://lists.apache.org/thread.html/a645bdb72bc55e05ec57f5b07a95c2579971f0a
@@ -998, +1018 @@

  When were the last committers or PPMC members elected?
    New committer:
    Qin Lang (November 21, 2018; 
+   
-   https://lists.apache.org/thread.html/27a2943240180666ce9e9219a049322966c851a259d908e241103d7a@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/27a2943240180666ce9e9219a049322966c851a
+ 259d908e241103d7a@%3Cdev.mxnet.apache.org%3E)
    Thomas Delteil (November 20, 2018; 
+   
-   https://lists.apache.org/thread.html/d4ad366e81852547a732b4c31b7f3f020132e20ba9c4cae7fd908f31@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/d4ad366e81852547a732b4c31b7f3f020132e20
+ ba9c4cae7fd908f31@%3Cdev.mxnet.apache.org%3E)
    Kellen Sunderland (November 21, 2018; 
+   
-   https://lists.apache.org/thread.html/4f18f85e627c7c0db5ad9ea46b1c277ef304f9d445be6b7e1e3ae3af@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/4f18f85e627c7c0db5ad9ea46b1c277ef304f9d
+ 445be6b7e1e3ae3af@%3Cdev.mxnet.apache.org%3E)
    Tao Lv (Novmember 21, 2018; 
+   
-   https://lists.apache.org/thread.html/3b14dadf32c84b0249758f25db52602527311ec0efc7bf94c93aaeee@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/3b14dadf32c84b0249758f25db52602527311ec
+ 0efc7bf94c93aaeee@%3Cdev.mxnet.apache.org%3E)
    Rahul Huilgol (December 4, 2018: 
+   
-   https://lists.apache.org/thread.html/1b30b460d4bbc2ddb7a0bc7113e8d064ba752414d7d97a6e54d442f3@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/1b30b460d4bbc2ddb7a0bc7113e8d064ba75241
+ 4d7d97a6e54d442f3@%3Cdev.mxnet.apache.org%3E)
    Aaron Markham (December 4, 2018; 
+   
-   https://lists.apache.org/thread.html/f807eaa4e6477c6133e4949b7b38428adff57268620343d4c7c1e7ce@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/f807eaa4e6477c6133e4949b7b38428adff5726
+ 8620343d4c7c1e7ce@%3Cdev.mxnet.apache.org%3E)
    Da Zhang (December 17, 2018; 
+   
-   https://lists.apache.org/thread.html/ffaa9425c9f5da77176e0ad92d136e70179720e4f485456daf6d7231@%3Cdev.mxnet.apache.org%3E)
+   https://lists.apache.org/thread.html/ffaa9425c9f5da77176e0ad92d136e70179720e
+ 4f485456daf6d7231@%3Cdev.mxnet.apache.org%3E)
  
    No new PPMC members got elected in the reporting period.
  
@@ -1031, +1065 @@

    [X](mxnet) Jim Jagielski
       Comments:
    [X](mxnet) Michael Wall
-      Comments: Discussion on unapproved releases started, but needs resolution.  Good effort
on community building.
+      Comments: Discussion on unapproved releases started, but needs 
+      resolution.  Good effort on community building.
    [ ](mxnet) Bob Paulin
       Comments:
    [X](mxnet) Jason Dai
       Comments:
  
  IPMC/Shepherd notes:
-   Justin Mclean: The issue with unapproved releases and issues around that should of been
mentioned
+   Justin Mclean: The issue with unapproved releases and issues around that 
-   in this report.
+   should have been mentioned in this report.
  
  --------------------
  NetBeans
@@ -1052, +1087 @@

  Three most important issues to address in the move towards graduation:
  
    1. Completion of Maturity Model Assessment: 
+   
-   https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Maturity+Model+Assessment+for+NetBeans

+ https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Maturity+Model+A
+ ssessment+for+NetBeans 
    2. Understanding other steps that need to be taken, e.g., put together a 
    list of PMC members
    3. Vote to graduate.
@@ -1067, +1104 @@

    - Received Duke's Choice Award 2018 at Oracle Code One conference: 
    https://blogs.apache.org/netbeans/entry/duke-s-choice-award-2018
    - Several community members presented about NetBeans at Oracle Code One 
+   2018: 
-   2018: https://blogs.apache.org/netbeans/entry/apache-netbeans-at-oracle-code
+   https://blogs.apache.org/netbeans/entry/apache-netbeans-at-oracle-code
    - Currently 651 (622 in last report) on Apache NetBeans users mailing 
    list and 455 (438 in last report) on Apache NetBeans dev mailing list.
  
@@ -1199, +1237 @@

  
    1. Building the community: The PPMC and committer group has a large 
    percentage of codecentric employees, we have been recruiting people from 
-   other companies, but will have to continue these efforts for establishing a 
+   other companies, but will have to continue these efforts for establishing 
-   healthy Apache community.
+   a healthy Apache community.
    2. With PLC4X several people on the team are not very familiar with the 
    Apache Way. We have started and will continue our efforts on this 
    onboarding.
@@ -1233, +1271 @@

    * 15.11.2018: „RheinJUG“ Meetup, Düsseldorf
    * 06.12.2018: „IoTHessen“ Meetup, Frankfurt
  
-   From 22.11.2018-26.11.2018 we had our second official community event: This 
+   From 22.11.2018-26.11.2018 we had our second official community event: 
-   time we meet at the codecentric finca on Mallorca for 4 days of hacking, 
+   This  time we meet at the codecentric finca on Mallorca for 4 days of
-   coding, discussions and community building.
+   hacking, coding, discussions and community building.
  
    All in all 3 PPMC members participated and one new person.
  
@@ -1248, +1286 @@

    Our Twitter followers increased by 57 (almost doubled) to 116 followers 
    (Mainly as a direct result of @Java tweeting about us).
  
-   On GitHub we now have 42 “Stars” (increase of 18) and 20 “Forks” (increase 
+   On GitHub we now have 42 “Stars” (increase of 18) and 20 “Forks” 
-   of 6)
+   (increase of 6)
  
    We have successfully performed two major POCs with customers from the 
    industry (Companies in the pharmaceutical and automotive sectors) and the 
@@ -1260, +1298 @@

    order to spread the word.
  
    Also have we had first paid contracts where the companies were paying 
-   members of the project to implement some general purpose features that were 
+   members of the project to implement some general purpose features that 
-   missing as well as bug fixing and allowing those results to become part of 
+   were missing as well as bug fixing and allowing those results to become
-   the open-source project (Which I think is pretty surprising as the concept 
+   part of the open-source project (Which I think is pretty surprising as
-   of Open-Source is quite new to these companies)
+   the concept of Open-Source is quite new to these companies)
  
    How would you assess the podling's maturity?
  
@@ -1274, +1312 @@

    However, we still need to continue: the on-boarding increasing the 
    diversity of the team.
    Also we are currently trying to enable other team members to take over 
-   vital roles (Like being a release manager) so we no longer have areas with 
+   vital roles (Like being a release manager) so we no longer have areas 
-   personal singularities.
+   with personal singularities.
  
  Please feel free to add your own commentary.
  
@@ -1311, +1349 @@

  
  Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
  supports SPARQL queries. Rya is a scalable RDF data management system built 
- on
- top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
+ on top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
  processing techniques that scale to billions of triples across multiple 
  nodes.
  Rya provides fast and easy access to the data through SPARQL, a conventional
@@ -1390, +1427 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
  of?
  
-   Following a successful VOTE in favor of changing the Podling name [2], the 
+   Following a successful VOTE in favor of changing the Podling name [2], 
-   community submitted 12 nominations for new Podling names [2]. The names are 
+   the community submitted 12 nominations for new Podling names [2]. The names 
-   collected for easy reference on our confluence space [3].  The community 
+   are collected for easy reference on our confluence space [3].  The community 
-   downselected the names [2] JIRA tickets have been written to track progress 
+   downselected the names [2] JIRA tickets have been written to track 
-   on research on PODLINGNAMESEARCH board [4].  
+   progress on research on PODLINGNAMESEARCH board [4].  
  
  How has the community developed since the last report?
  
@@ -1409, +1446 @@

  
  How has the project developed since the last report?
  
-   Project maturity roadmaps (Wiki) and version release plans (JIRA) continue 
+   Project maturity roadmaps (Wiki) and version release plans (JIRA) 
+ continue 
    to be maintained.
    JIRA boards continue to be maintained
  
@@ -1453, +1491 @@

    [ ](senssoft) Atri Sharma
        Comments:
  
-   [1] https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps <https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps>
-   [2] https://lists.apache.org/thread.html/9a971fee3b17ac401cf76b16e5dc026c10a299591ee93329117a3cec@%3Cdev.senssoft.apache.org%3E

+   [1] https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps 
+ <https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps>
+   [2] 
- <https://lists.apache.org/thread.html/9a971fee3b17ac401cf76b16e5dc026c10a299591ee93329117a3cec@%3Cdev.senssoft.apache.org%3E>
+ https://lists.apache.org/thread.html/9a971fee3b17ac401cf76b16e5dc026c10a2995
-   [3] https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH <https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH>
-   [4] https://issues.apache.org/jira/browse/SENSSOFT-312 <https://issues.apache.org/jira/browse/SENSSOFT-312>
+ 91ee93329117a3cec@%3Cdev.senssoft.apache.org%3E 
+ <https://lists.apache.org/thread.html/9a971fee3b17ac401cf76b16e5dc026c10a299
+ 591ee93329117a3cec@%3Cdev.senssoft.apache.org%3E>
+   [3] 
+ https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH 
+ <https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH>
+   [4] https://issues.apache.org/jira/browse/SENSSOFT-312 
+ <https://issues.apache.org/jira/browse/SENSSOFT-312>
  
  IPMC/Shepherd notes:
  
@@ -1478, +1523 @@

  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
+ 
    None.
  
  How has the community developed since the last report?
@@ -1488, +1534 @@

  How has the project developed since the last report?
  
    Released 3.1.0.M1, contributors are from different companies. In 3.1.0.M1 
-   release milestones, there are 148 issues and pull requests solved. This is 
+   release milestones, there are 148 issues and pull requests solved. This 
+ is 
    a legacy release not for Apache.
  
  How would you assess the podling's maturity?
@@ -1543, +1590 @@

  aware of?
    The development of Weex is based on the Weex Github Repo, but none of the 
    PPMC members have maintainer or administration privilege on the 
-   repo (https://github.com/apache/incubator-weex), which makes it time costing 
+   repo (https://github.com/apache/incubator-weex), which makes it time 
-   or impossible to add Webhook、PR Review Rules, etc. as INFRA member might 
+   costing or impossible to add Webhook、PR Review Rules, etc. as INFRA member
-   response to a JIRA issue several days or weeks later.
+   might response to a JIRA issue several days or weeks later.
  
  How has the community developed since the last report?
    New Committer: Qianyuan Wang(wqyfavor) and Douma Fang

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


Mime
View raw message