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 "March2016" by MarvinHumphrey
Date Wed, 02 Mar 2016 23:58:06 GMT
Dear Wiki user,

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

The "March2016" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/March2016?action=diff&rev1=38&rev2=39

Comment:
Reflow.

  How has the project developed since the last report?
  
    * The JPL team developed the following new services:
-     . Time series for multiple datasets
+     * Time series for multiple datasets
-     . Conditional probability density function calculation
+     * Conditional probability density function calculation
-     . Empirical orthogonal function calculation
+     * Empirical orthogonal function calculation
-     . Random forest feature importance calculation
+     * Random forest feature importance calculation
-     . Anomaly calculation
+     * Anomaly calculation
    * The JPL team improved these features:
-     . A new color scheme of data visualization of some services
+     * A new color scheme of data visualization of some services
-     . The URL for a RestFul service call has been constructed
+     * The URL for a RestFul service call has been constructed
    * The JPL team is working on
-     . supporting a workflow with CMDA services. identified first examples to work on.
+     * supporting a workflow with CMDA services. identified first examples to
+       work on.
-       modifying the CMDA services to be “chainable” (callable in a workflow).
+     * modifying the CMDA services to be “chainable” (callable in a
+       workflow).
    * The CMU team created a unified github repository that
      has both the CMU and JPL code bases. Needs cleanup;
    * The CMU team created a new Docker container that has
@@ -333, +335 @@

    happen, we have started to discuss options to find a viability for the
    project https://s.apache.org/oxqb
  
-   By the next reporting period we should have something more concrete towards
+   By the next reporting period we should have something more concrete
-   the future, or we could think about a possible exit strategy.
+   towards the future, or we could think about a possible exit strategy.
  
  Date of last release:
  
@@ -363, +365 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1.Inform the non-technical part of the existing Mifos.org community of the change in project
structure
+   1. Inform the non-technical part of the existing Mifos.org community of
+      the change in project structure
-   2.Getting licensing issues figured out for our first release
+   2. Getting licensing issues figured out for our first release
-   3.Replacing dependencies that are not compliant with the license policies
+   3. Replacing dependencies that are not compliant with the license policies
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- None, currently.
+   None, currently.
  
  How has the community developed since the last report?
  
- Since the code was initially pushed over, the community is working on the first release.
+   Since the code was initially pushed over, the community is working on the
+   first release.
  
- In addition to the initial committer new contributors started to work on the project.
+   In addition to the initial committer new contributors started to work on
+   the project.
  
- There is a technical conference in Amsterdam in the second week of March during which some
contributors and some community members will be introduced to developing under the Apache
model.
+   There is a technical conference in Amsterdam in the second week of March
+   during which some contributors and some community members will be
+   introduced to developing under the Apache model.
  
  How has the project developed since the last report?
  
- The initial code is now available and the work to meet the license policies has started.
+   The initial code is now available and the work to meet the license
+   policies has started.
  
  Date of last release:
  
- N/A
+   N/A
  
  When were the last committers or PMC members elected?
  
@@ -454, +462 @@

  Impala
  
  Impala is a high-performance C++ and Java SQL query engine for data stored
- in
- Apache Hadoop-based clusters.
+ in Apache Hadoop-based clusters.
  
  Impala has been incubating since 2015-12-03.
  
  Three most important issues to address in the move towards graduation:
  
    1. Movement of existing JIRA / Git / wiki resources to Apache
- equivalents
+      equivalents
    2. Initial release as incubating project.
    3. Community growth
  
  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?
  
- There have been no additions to the committer or PMC lists since incubation
+   There have been no additions to the committer or PMC lists since
- began. However, we have seen an uptick in external contributions, both through code, and
in discussion on the mailing list. One contributor has been attempting to port Impala to PPC,
and has reported some success after asking many questions.
+   incubation began. However, we have seen an uptick in external
+   contributions, both through code, and in discussion on the mailing list.
+   One contributor has been attempting to port Impala to PPC, and has
+   reported some success after asking many questions.
  
  How has the project developed since the last report?
  
- We have made some slow progress with our initial infrastructure tasks. Code review traffic
is now copied to dev@impala.incubator.apache.org, which means that developer discussions are
now happening on the mailing lists.
- We have a number of infrastructure tasks ahead of us which are blocked on the current Impala
team at Cloudera being very busy with an internal release (this is one reason we look forward
to a more diverse community!). For example:
- 1. We would like to move our Git repository to .apache.org in short order, but as it stands
the existing repo is 10GB large and historically contains many binary artifacts that, while
acceptably licensed, have no useful place in Impala's repository. We need to strip these artifacts
from the Git history, and then adjust Gerrit to commit to the new branch in the new repo.
This is not hard but takes some time.
- 2. We would also like to move our JIRA tickets from issues.cloudera.org to issues.apache.org.
Experience in a sister podling has shown that this isn't straightforward if we wish to preserve
existing release labels, user assignments and so on, so requires some time.
- We anticipate having much more time to work on these basic issues after the end of February.
We look forward to getting Impala into a position where it is easier for the larger community
to collaborate on these kinds of project management issues.
+   We have made some slow progress with our initial infrastructure tasks.
+   Code review traffic is now copied to dev@impala.incubator.apache.org,
+   which means that developer discussions are now happening on the mailing
+   lists.
+ 
+   We have a number of infrastructure tasks ahead of us which are blocked on
+   the current Impala team at Cloudera being very busy with an internal
+   release (this is one reason we look forward to a more diverse community!).
+   For example:
+ 
+   1. We would like to move our Git repository to .apache.org in short order,
+      but as it stands the existing repo is 10GB large and historically
+      contains many binary artifacts that, while acceptably licensed, have no
+      useful place in Impala's repository. We need to strip these artifacts
+      from the Git history, and then adjust Gerrit to commit to the new
+      branch in the new repo. This is not hard but takes some time.
+   2. We would also like to move our JIRA tickets from issues.cloudera.org to
+      issues.apache.org. Experience in a sister podling has shown that this
+      isn't straightforward if we wish to preserve existing release labels,
+      user assignments and so on, so requires some time.
+ 
+   We anticipate having much more time to work on these basic issues after
+   the end of February. We look forward to getting Impala into a position
+   where it is easier for the larger community to collaborate on these kinds
+   of project management issues.
+ 
  --------------------
  iota
  
@@ -804, +835 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- The Initial Committer list is being revised (see below).
+   The Initial Committer list is being revised (see below).
  
  How has the community developed since the last report?
  
- We have identified shortcomings in the Initial Committer list,
+   We have identified shortcomings in the Initial Committer list, and adopted
- and adopted a fast-track process to add new members, valid for
+   a fast-track process to add new members, valid for the project's first
- the project's first three months (until March 20th).  We have
- welcomed our first genuinely new committer and are inviting
- another.  Initial committers are familiarising with Apache.
+   three months (until March 20th).  We have welcomed our first genuinely new
+   committer and are inviting another.  Initial committers are familiarising
+   with Apache.
  
  How has the project developed since the last report?
  
- Both companies MIRACL and NTT are now readying their initial contributions into the Milagro
repositories.
+   Both companies MIRACL and NTT are now readying their initial contributions
+   into the Milagro repositories.
  
  Date of last release:
  
@@ -824, +856 @@

  
  When were the last committers or PMC members elected?
  
- We have no distinction between committers and PMC.
+   We have no distinction between committers and PMC.
  
- The following have accepted invitations during the period:
+   The following have accepted invitations during the period:
+ 
-   Peter Scanlon
+     Peter Scanlon
-   Tomasz Matecki
+     Tomasz Matecki
-   Anthony Shaw
+     Anthony Shaw
-   Vladislav Mitov
+     Vladislav Mitov
-   Nikolai Stoilov
+     Nikolai Stoilov
  
- All except Anthony Shaw are Miracl employees, and should
+   All except Anthony Shaw are Miracl employees, and should have been on the
+   Initial Committer list.  We anticipate improving diversity soon.
- have been on the Initial Committer list.  We anticipate
- improving diversity soon.
  
  Signed-off-by:
  
@@ -1114, +1146 @@

  aware of?
  
    1. Graduation vote has been passed and the resolution has been proposed to
-   the board for consideration in the board meeting.
+      the board for consideration in the board meeting.
-   References:
+      References:
-   https://s.apache.org/dev_discuss
+      https://s.apache.org/dev_discuss
-   https://s.apache.org/dev_vote_result
+      https://s.apache.org/dev_vote_result
-   https://s.apache.org/general_discuss
+      https://s.apache.org/general_discuss
-   https://s.apache.org/Incubator_vote
+      https://s.apache.org/Incubator_vote
-   Other:
+      Other:
-   https://s.apache.org/general_notify
+      https://s.apache.org/general_notify
-   https://s.apache.org/8rty (Maturity Model assessment)
+      https://s.apache.org/8rty (Maturity Model assessment)
    2. Olivier Lamy resigned as a mentor.
  
  How has the community developed since the last report?
@@ -1393, +1425 @@

  Toree
  
  Toree provides applications with a mechanism to interactively and remotely
- access Apache Spark. It enables interactive workloads between applications and a Spark
+ access Apache Spark. It enables interactive workloads between applications
- cluster. As a Jupyter Notebook extension, it provides the user with a
+ and a Spark cluster. As a Jupyter Notebook extension, it provides the user
- preconfigured environment for interacting with Spark using Scala, Python, R
+ with a preconfigured environment for interacting with Spark using Scala,
- or SQL.
+ Python, R or SQL.
  
  Toree has been incubating since 2015-12-02.
  
@@ -1409, +1441 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- TOREE-262 - Progress on removal of LGPL dependency
+   TOREE-262 - Progress on removal of LGPL dependency
  
  How has the community developed since the last report?
  
-   1. Work with Jupyter community to update their docker stacks to include the latest Toree
+   1. Work with Jupyter community to update their docker stacks to include
+      the latest Toree
-   2. Blog post at http://www.spark.tc/announcing-apache-toree/ to announce the incubation
+   2. Blog post at http://www.spark.tc/announcing-apache-toree/ to announce
+      the incubation
    3. Active communication in mailing list and gitter with early adopters
-   4. Work with Brunel project (https://github.com/Brunel-Visualization/Brunel) to
-      make technology available on Toree
+   4. Work with Brunel project
+      (https://github.com/Brunel-Visualization/Brunel) to make technology
+      available on Toree
-   5. Still working on transitioning users from Spark Kernel project into Toree.
+   5. Still working on transitioning users from Spark Kernel project into
+      Toree.
  
  How has the project developed since the last report?
  
    1. Source package have been renamed to org.apache.toree
-   2. All original contributors are not actively developing and fixing issues on the
+   2. All original contributors are not actively developing and fixing issues
-      apache project
+      on the apache project
-   3. Project can be published and installed through Pypi (only snapshot/dev packaged made
+   3. Project can be published and installed through Pypi (only snapshot/dev
-      available for testing)
+      packaged made available for testing)
-   4. Added a plug-in framework to enable integration of 3rd party code to add capabilities
+   4. Added a plug-in framework to enable integration of 3rd party code to
+      add capabilities
-   5. Create Spark Streaming example notebook to feature many of the capabilities of Toree
+   5. Create Spark Streaming example notebook to feature many of the
-      in collaboration with Jupyter ecosystem (dashboards and widgets)
+      capabilities of Toree in collaboration with Jupyter ecosystem
+      (dashboards and widgets)
    6. Misc bug fixes and features
-   7. Actively working with JeroMQ community to further their transition into MPL v2
+   7. Actively working with JeroMQ community to further their transition into
-      and away from LGPL.
+      MPL v2 and away from LGPL.
  
  Date of last release:
  
- None since incubation.
+   None since incubation.
  
  When were the last committers or PMC members elected?
  
- No new additions since incubation
+   No new additions since incubation
  
  Signed-off-by:
  

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


Mime
View raw message