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 "February2017" by MarvinHumphrey
Date Sat, 04 Feb 2017 19:06:58 GMT
Dear Wiki user,

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

The "February2017" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/February2017?action=diff&rev1=62&rev2=63

Comment:
Reflow Fineract through PredictionIO.

  
  Three most important issues to address in the move towards graduation:
  
-   1. Addressing areas of concern raised by community based on our Maturity Evaluation including:
+   1. Addressing areas of concern raised by community based on our Maturity
+      Evaluation including:
-     * Full documentation of our release management process
+      * Full documentation of our release management process
-     * Implementation of Findbugs to show commitment to quality of code
+      * Implementation of Findbugs to show commitment to quality of code
-     * Preparation of our community to respond any security threats or vulnerabilities that
are reported.
+      * Preparation of our community to respond any security threats or
+        vulnerabilities that are reported.
-     * Improvement of backwards compatibility of APIs and communication of breaking changes
with each release.
+      * Improvement of backwards compatibility of APIs and communication of
+        breaking changes with each release.
-     * Updating Apache Fineract webpage with latest releases. 
+      * Updating Apache Fineract webpage with latest releases. 
    2. Adding new committers and contributors to the project.  
-   3. Continuing to move over additional documentation and providing full clarity to our
community on how and where to report issues via the issue tracker.
+   3. Continuing to move over additional documentation and providing full
+      clarity to our community on how and where to report issues via the
+      issue tracker.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
  
  
- How has the community developed since the last report?
- 
- * Community continues to stay strongly engaged on the mailing lists with active reporting
of issues via the mailing list and issue tracker. 
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   * Community continues to stay strongly engaged on the mailing lists with
+     active reporting of issues via the mailing list and issue tracker. 
+ 
+ How has the project developed since the last report?
+ 
- * The community has made 2 additional releases since the last report.
+   * The community has made 2 additional releases since the last report.
-  * Our second release was made on December 21, 2016 with three binding votes from the community.
+     * Our second release was made on December 21, 2016 with three binding
+       votes from the community.
-  * Our third release was made on January 17, 2017  with three binding votes from the community.

+     * Our third release was made on January 17, 2017  with three binding
+       votes from the community. 
- 
- 
  
  Date of last release:
  
@@ -519, +524 @@

    
    2016-05-16
  
- 
  Signed-off-by:
  
    [ ](fineract) Ross Gardler
@@ -547, +551 @@

  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?
  
-  * Its been quiet.
+   * Its been quiet.
  
  How has the project developed since the last report?
  
-  * Wrote two blog post to help raise awareness of Fluo.
+   * Wrote two blog post to help raise awareness of Fluo.
-    - http://fluo.apache.org/blog/2016/12/22/spark-load/
+     - http://fluo.apache.org/blog/2016/12/22/spark-load/
-    - http://fluo.apache.org/blog/2016/11/10/immutable-bytes/
+     - http://fluo.apache.org/blog/2016/11/10/immutable-bytes/
-  * Made many improvements and bug fixes. Need to start planning for next release.
+   * Made many improvements and bug fixes. Need to start planning for next
-  * Experimented with setting Apache Logo as twitter header.  Shared this with members list
and a few other Apache projects did something similar. https://twitter.com/apachefluo
+     release.
+   * Experimented with setting Apache Logo as twitter header.  Shared this
+     with members list and a few other Apache projects did something similar.
+     https://twitter.com/apachefluo
  
- 
  Date of last release:
  
-    2016-10-28
+   2016-10-28
  
  When were the last committers or PPMC members elected?
  
@@ -612, +618 @@

  How has the community developed since the last report?
  
    Frequency and complexity of contributions seem to be increasing. Community
-   presence and activity on the mailing lists has also increased due to the use
+   presence and activity on the mailing lists has also increased due to the
-   of Nabble to provide a forum-like interface.
+   use of Nabble to provide a forum-like interface.
  
  How has the project developed since the last report?
  
-   The project has succeeded in producing its first release under the Incubator,
+   The project has succeeded in producing its first release under the
-   0.9.10-incubating, and the process is already underway for producing the
+   Incubator, 0.9.10-incubating, and the process is already underway for
-   next, with the IPMC vote for release having been started on 2017-01-26.
+   producing the next, with the IPMC vote for release having been started on
+   2017-01-26.
  
    With the first release out of the way, development is finally moving
-   smoothly again. We have adopted a branching workflow which allows development
+   smoothly again. We have adopted a branching workflow which allows
-   to continue unhindered, with only the release scope being frozen.
+   development to continue unhindered, with only the release scope being
+   frozen.
  
  Date of last release:
  
@@ -712, +720 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Getting a release out based on the current code base - will will commit to do that
this quarter
+   1. Getting a release out based on the current code base - will will commit
-   2. Using the mailing list to discuss current and future development and needs - we commit
more regular dialogue on the mailing list
-   3. Growing the community - we have been slow to get off the ground and need to put more
effort in here - we will commit to do more outreach to grow the community
+      to do that this quarter
+   2. Using the mailing list to discuss current and future development and
+      needs - we commit more regular dialogue on the mailing list
+   3. Growing the community - we have been slow to get off the ground and
+      need to put more effort in here - we will commit to do more outreach to
+      grow the community
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
- aware of?  We realize we have been a little slow is getting off the ground as an Apache
Project. I have spoken to Hadrian Zbarcea and explained to him why this has been the case.
We are really committed to iota as a technology and commit to put more effort into making
this a successful project.
+ aware of?
  
+   We realize we have been a little slow is getting off the ground as an
+   Apache Project. I have spoken to Hadrian Zbarcea and explained to him why
+   this has been the case. We are really committed to iota as a technology
+   and commit to put more effort into making this a successful project.
  
- 
  How has the community developed since the last report?
+ 
- No - we need to spend time on this and we will do so.
+   No - we need to spend time on this and we will do so.
  
- 
  How has the project developed since the last report?
+ 
- We have added global performers
+   We have added global performers
- 
  
  Date of last release:
  
    XXXX-XX-XX
  
  When were the last committers or PPMC members elected?
+ 
- Yes - Barbara Gomes was added as a committer on 12/02/2016
+   Yes - Barbara Gomes was added as a committer on 12/02/2016
- 
  
  Signed-off-by:
  
@@ -779, +794 @@

  
  How has the project developed since the last report?
  
-   Things have stalled a bit over the winter holidays, but we have recently started to pick
things up again. As always, a release is imminent.
+   Things have stalled a bit over the winter holidays, but we have recently
+   started to pick things up again. As always, a release is imminent.
  
  Date of last release:
  
@@ -789, +805 @@

  
    Per http://incubator.apache.org/projects/joshua.html:
  
-   - 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC + Committership.
+   - 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC +
+     Committership.
    - 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership.
    - 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership.
  
@@ -815, +832 @@

  Three most important issues to address in the move towards graduation:
  
    1. Develop MILAGRO toolbox
-   2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto library – further
research and development (IoT, blockchain, fractions etc.)
-   3. Building the MILAGRO community – engaging developers and cryptographers, raising
awareness and helping to secure future of internet.
+   2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto
+      library – further research and development (IoT, blockchain, fractions
+      etc.)
+   3. Building the MILAGRO community – engaging developers and
+      cryptographers, raising awareness and helping to secure future of
+      internet.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- No.
+   No.
  
- How has the community developed since the last report?
- 
- After ApacheCon in Spain – MILAGRO was in the scope of interest, and we can see the increasing
community interest in MILAGRO ecosystem.  In December 2016 MILAGRO ecosystem draft was published
on MILAGRO mailing list and now we are looking to begin development of new structure.
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
- In last few months the MILAGRO ecosystem proposal was developed and published in order to
organize, and prioritize the MILAGRO workflow. In order to develop new structure, we are discussing
new architecture of MILAGRO repositories.
+   After ApacheCon in Spain – MILAGRO was in the scope of interest, and we
+   can see the increasing community interest in MILAGRO ecosystem.  In
+   December 2016 MILAGRO ecosystem draft was published on MILAGRO mailing
+   list and now we are looking to begin development of new structure.
+ 
+ How has the project developed since the last report?
+ 
+   In last few months the MILAGRO ecosystem proposal was developed and
+   published in order to organize, and prioritize the MILAGRO workflow. In
+   order to develop new structure, we are discussing new architecture of
+   MILAGRO repositories.
  
  Date of last release:
  
@@ -973, +999 @@

    2015-10-05 - Damjan Jovanovic for Commiter/PPMC
  
  Signed-off-by:
+ 
    [ ](odftoolkit) Nick Burch
    [ ](odftoolkit) Yegor Kozlov
  
@@ -993, +1020 @@

  
  OpenWhisk has been incubating since 2016-11-23.
  
- 
  Three most important issues to address in the move towards graduation:
  
-   1. Moving github repos under the Apache Github Org (organization move, repository renames)
+   1. Moving github repos under the Apache Github Org (organization move,
+      repository renames)
-   2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org, update openwhisk.org
to be Apache compliant
+   2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
-   3. Review and update project checklist (http://incubator.apache.org/projects/openwhisk.html).
+      update openwhisk.org to be Apache compliant
+   3. Review and update project checklist
+      http://incubator.apache.org/projects/openwhisk.html
  
-   Some items should be mark done (around infra), CLA's have been confirmed for all Committers.
URL/links need to be updated.
+   Some items should be mark done (around infra), CLA's have been confirmed
+   for all Committers. URL/links need to be updated.
  
- Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
+ Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
+ aware of?
  
    - No issues so far 
  
  How has the community developed since the last report?
  
-   - All Initial Committers now have ICLA’s and have access to private email list
+   - All Initial Committers now have ICLA’s and have access to private email
+     list
-   - Nearly all pre-Incubator active contributors have signed ICLAs, a few new contributor
ICLAs have been received
+   - Nearly all pre-Incubator active contributors have signed ICLAs, a few
-   - Project GitHub (all repos.) now govern access via 3 “Teams” Committer (write), Contributor-CLA
(read), Contributor (read/default)
-   - “dev", “private” email list traffic continues to be healthy; positive discussion
of a few new code feature/change topics
+     new contributor ICLAs have been received
+   - Project GitHub (all repos.) now govern access via 3 “Teams” Committer
+     (write), Contributor-CLA (read), Contributor (read/default)
+   - “dev", “private” email list traffic continues to be healthy; positive
+     discussion of a few new code feature/change topics
-   - GitHub project “Stars” = 1024 (a nice binary number), up a couple dozen from last
month 
+   - GitHub project “Stars” = 1024 (a nice binary number), up a couple dozen
+     from last month 
  
  How has the project developed since the last report?
  
-   - Updated CONTRIBUTING.md to ref. Apache processes, Added CREDITS.txt to all repos., in
process of changing all code headers to use Apache approved text. Need to update Travis CI
checks to look for new header (per repo. basis)
+   - Updated CONTRIBUTING.md to ref. Apache processes, Added CREDITS.txt to
+     all repos., in process of changing all code headers to use Apache
+     approved text. Need to update Travis CI checks to look for new header
+     (per repo. basis)
+   - Confluence WIKI established:
-   - Confluence WIKI established: https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki
+     https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki
-     - added project overview and contributor/committer role/process descriptions
+     - added project overview and contributor/committer role/process
-   - website updates continue, now include “Incubator” disclaimer, working issues opened
by community to list “supporters” and provide a form to submit to request to be added.
-   - deprecated “whisk” object for Nodejs6 runtime (javascript) actions/functions in
favor of single dictionary and use of Nodejs built-in “promises”
-   - Size limits discussed and being updated for per-request/response for actions (and sequences)
to preserve performance/reliability
-   - Discussing proposals for the proper use and optimization of KV stores for configurations
information (along with Ansible for deployments)
-   - API gateway moved to support LUA as plug-in model, added OAuth support. Client ID/secret
validation, Dynamic upstream routing using Redis
-   - An OpenWhisk plug-in contribution was accepted for the serverless.com framework (https://serverless.com/blog/openwhisk-integration-with-serverless/)

+       descriptions
+   - website updates continue, now include “Incubator” disclaimer, working
+     issues opened by community to list “supporters” and provide a form to
+     submit to request to be added.
+   - deprecated “whisk” object for Nodejs6 runtime (javascript)
+     actions/functions in favor of single dictionary and use of Nodejs
+     built-in “promises”
+   - Size limits discussed and being updated for per-request/response for
+     actions (and sequences) to preserve performance/reliability
+   - Discussing proposals for the proper use and optimization of KV stores
+     for configurations information (along with Ansible for deployments)
+   - API gateway moved to support LUA as plug-in model, added OAuth support.
+     Client ID/secret validation, Dynamic upstream routing using Redis
+   - An OpenWhisk plug-in contribution was accepted for the serverless.com
+     framework
+     https://serverless.com/blog/openwhisk-integration-with-serverless/ 
  
  Date of last release:
  
    - No release yet
  
- 
  When were the last committers or PPMC members elected?
  
    - No activity
- 
  
  Signed-off-by:
  
@@ -1061, +1109 @@

  Three most important issues to address in the move towards graduation:
  
    1. Establish a formal release schedule and process, allowing for
- dependable release cycles in a manner consistent with the Apache way.
+      dependable release cycles in a manner consistent with the Apache way.
    2. Grow the community to establish diversity of background.
    3. Transition remaining former PredictionIO users from google-groups to
- ASF mailing lists.
+      ASF mailing lists.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
  of?
@@ -1074, +1122 @@

  How has the community developed since the last report?
  
    1. Both user and development mailing lists are more active than the last
- report.
+      report.
    2. There are major feature contributions from both new committers and the
- community.
+      community.
    3. The ecosystem around engine templates is gaining traction. There are
- several new templates added to the engine template gallery.
+      several new templates added to the engine template gallery.
    4. Local user groups are budding, e.g. Japan PredictionIO User Group.
  
  How has the project developed since the last report?
@@ -1086, +1134 @@

    1. Several major feature contributions are under review.
    2. The second release is on track for early February release.
    3. There have been active discussions which have driven a solid roadmap
- for future releases, especially centering around microservice architecture,
+      for future releases, especially centering around microservice
- stateless builds, and running from anywhere with a centralized metadata
- registry.
+      architecture, stateless builds, and running from anywhere with a
+      centralized metadata registry.
  
  Date of the last release:
  

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


Mime
View raw message