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 "January2017" by MarvinHumphrey
Date Thu, 12 Jan 2017 01:37:41 GMT
Dear Wiki user,

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

The "January2017" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/January2017?action=diff&rev1=58&rev2=59

Comment:
Reflow second half of report.

  
  Three most important issues to address in the move towards graduation:
  
-   1. Need guidance from Incubator PMC on how to resolve the BSD licensing switch over to
Apache License.  What should be the content of the license headers for files that were previously
BSD licensed and then granted to ASF?  Related legal-discuss threads:
+   1. Need guidance from Incubator PMC on how to resolve the BSD licensing
+      switch over to Apache License.  What should be the content of the license
+      headers for files that were previously BSD licensed and then granted to
+      ASF?  Related legal-discuss threads:
- http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201609.mbox/%3CCALGG8z03zHhbFegXoi4fH+vXtF+9m7x6hak9RjKQjapuzi67gQ@mail.gmail.com%3E
+      http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201609.mbox/%3CCALGG8z03zHhbFegXoi4fH+vXtF+9m7x6hak9RjKQjapuzi67gQ@mail.gmail.com%3E
- http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201603.mbox/%3C9D1AF43C-370B-4E58-B0EF-2E29D242F50B%40jaguNET.com%3E
+      http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201603.mbox/%3C9D1AF43C-370B-4E58-B0EF-2E29D242F50B%40jaguNET.com%3E
    2. Continue to produce regular Apache (incubating) releases.
-   3. Continue to execute and manage the project according to governance model of the "Apache
Way”.
+   3. Continue to execute and manage the project according to governance model
+      of the "Apache Way”.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
  
-  1. Yes-please see #1 above and provide guidance.
+   1. Yes-please see #1 above and provide guidance.
-  2. The next release v1.10 will be the 4th as an incubating project.  After that, the community
would ideally like to move towards top level status.
+   2. The next release v1.10 will be the 4th as an incubating project.  After
+      that, the community would ideally like to move towards top level status.
  
  How has the community developed since the last report?
  
    1. Some related events in Q4 2016 and upcoming: 
-         * Feb 4, 2017 - Presentation accepted at FOSDEM’17 Graph devroom.  Topic:  Graph
Analytics on Massively Parallel Processing Databases (Frank McQuillan)
- 	* Dec 1, 2016 - MADLib community call.  Topic:  New features in R interface and MADlib
user survey results (hosted by Greg Chase, Orhan Kislal, Frank McQuillan)
- 	* Nov 16, 2016 - Presentation at PGConf Silicon Valley.  Topic:  Distributed In-Database
Machine Learning with Apache MADlib (incubating) (Frank McQuillan)
- 	* Nov 14, 2016 - Presentation at Apache Big Data Europe.  Topic:  Distributed In-Database
Machine Learning with Apache MADlib (incubating) (Roman Shaposhnik)
+      * Feb 4, 2017 - Presentation accepted at FOSDEM’17 Graph devroom.
+        Topic:  Graph Analytics on Massively Parallel Processing Databases
+        (Frank McQuillan)
+      * Dec 1, 2016 - MADLib community call.  Topic:  New features in R
+        interface and MADlib user survey results (hosted by Greg Chase, Orhan
+        Kislal, Frank McQuillan)
+      * Nov 16, 2016 - Presentation at PGConf Silicon Valley.  Topic:
+        Distributed In-Database Machine Learning with Apache MADlib
+        (incubating) (Frank McQuillan)
+      * Nov 14, 2016 - Presentation at Apache Big Data Europe.  Topic:
+        Distributed In-Database Machine Learning with Apache MADlib
+        (incubating) (Roman Shaposhnik)
-   2. Material technical conversations on user/dev mailing lists and in the appropriate JIRAs
and pull requests.
+   2. Material technical conversations on user/dev mailing lists and in the
+      appropriate JIRAs and pull requests.
-   3. New contributors to the project have been working on KNN module and Python interface.
+   3. New contributors to the project have been working on KNN module and
+      Python interface.
  
  How has the project developed since the last report?
  
-   1. Active work in progress for 4th ASF release MADlib v10 scheduled for Jan 2017.  Features
include: single source shortest path graph algorithm, completely new module for encoding categorical
variables, R interface update, grouping support in elastic net and PCA, cross validation in
elastic net, verbose output option for decision tree visualization.
+   1. Active work in progress for 4th ASF release MADlib v10 scheduled for Jan
+      2017.  Features include: single source shortest path graph algorithm,
+      completely new module for encoding categorical variables, R interface
+      update, grouping support in elastic net and PCA, cross validation in
+      elastic net, verbose output option for decision tree visualization.
    2. Mailing list activity in Q4:  227 postings to dev, 66 postings to user.
  
  Date of last release:
@@ -726, +745 @@

  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:
  
@@ -749, +767 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Trigger a community discussion to graduate from incubation.  We have received a lot
of value from the incubation process and after speaking to our mentors and going through the
Apache Project Maturity Model we believe that we will soon be ready to graduate.  
+   1. Trigger a community discussion to graduate from incubation.  We have
+      received a lot of value from the incubation process and after speaking
+      to our mentors and going through the Apache Project Maturity Model we
+      believe that we will soon be ready to graduate.  
-   2. Vote to ratify our Development Guidelines and Process for Reporting Issues 
+   2. Vote to ratify our Development Guidelines and Process for Reporting
+      Issues 
    3. Vote to ratify our Release Process 
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- 
- We refreshed our website to be more compliant with Apache policies 
+   We refreshed our website to be more compliant with Apache policies 
  
  How has the community developed since the last report?
  
- - We added 2 committers 
+   - We added 2 committers 
- - We had a clean Apache build
+   - We had a clean Apache build
  
  How has the project developed since the last report?
  
- - We closed 63 PRs as of our last build
+   - We closed 63 PRs as of our last build
- - We integrated with Apache Ambari to make the project easier to deploy
+   - We integrated with Apache Ambari to make the project easier to deploy
- - We modified and re-voted on our Bylaws 
+   - We modified and re-voted on our Bylaws 
- - We successfully filed our Name Search Jira.  
+   - We successfully filed our Name Search Jira.  
  
  Date of last release:
  
@@ -803, +824 @@

  
  Three most important issues to address in the move towards graduation: 
  
- 1. Make further point releases capable of producing a downloadable RTOS image
+   1. Make further point releases capable of producing a downloadable RTOS
- with support for multiple MCU architectures, peripherals, and network connectivity protocols
- with the goal of the first major (1.0) release in the first quarter of 2017. These point
releases
+      image with support for multiple MCU architectures, peripherals, and
+      network connectivity protocols with the goal of the first major (1.0)
+      release in the first quarter of 2017. These point releases are intended
- are intended to demonstrate and solidify the repeatability, usability, and maturity of process.
+      to demonstrate and solidify the repeatability, usability, and maturity
- 
- 2. Continue to develop and execute policies that enable project contributors to achieve
self-governance.
- 
+      of process.
+   2. Continue to develop and execute policies that enable project
+      contributors to achieve self-governance.
- 3. Expand community - attract new project contributors, get users with diverse backgrounds
applying 
+   3. Expand community - attract new project contributors, get users with
- project to new use cases and encouraging adoption, grow committer base.
+      diverse backgrounds applying project to new use cases and encouraging
+      adoption, grow committer base.
  
  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? 
  
- 1. Active mailing lists with increasing numbers of subscribers. 23 new subscribers on dev@
mailing 
+   1. Active mailing lists with increasing numbers of subscribers. 23 new
+      subscribers on dev@ mailing list since last report.
- list since last report.
- 
- 2. Increased participation by several new contributors through pull requests for new MCU
support, new 
+   2. Increased participation by several new contributors through pull
+      requests for new MCU support, new BSP support, features, and test cases
- BSP support, features, and test cases and test results. Increased usage of the project for
3rd-party 
+      and test results. Increased usage of the project for 3rd-party products
- products or demos. Outreach continues via conferences, exhibits, one on one meetings, tutorials,
beta testers.
- 
+      or demos. Outreach continues via conferences, exhibits, one on one
+      meetings, tutorials, beta testers.
- 3. Vigorous discussions on feature proposals, code behavior analysis, API, code usability,
and implementation specifics 
+   3. Vigorous discussions on feature proposals, code behavior analysis, API,
- on @dev mailing list.
+      code usability, and implementation specifics on @dev mailing list.
  
  How has the project developed since the last report? 
  
- 1. The first beta release of the first major release (1.0.0-b1) was completed on December
13, 2016. A 
+   1. The first beta release of the first major release (1.0.0-b1) was
+      completed on December 13, 2016. A second beta is being considered before
- second beta is being considered before the first release in Q1, 2017 to facilitate a smooth
major release.
+      the first release in Q1, 2017 to facilitate a smooth major release.
- 
- 2. Planning: Issues including bug reports, features, and wish list captured and tracked
in ASF JIRA 
+   2. Planning: Issues including bug reports, features, and wish list captured
+      and tracked in ASF JIRA by members of the community. 
- by members of the community. 
- 
- 3. Effort towards self governance: Voting successfully completed to grant committer
+   3. Effort towards self governance: Voting successfully completed to grant
- status to two new candidates since last report.
+      committer status to two new candidates since last report.
  
  Date of last release: 
  
- 2016-12-13
+   2016-12-13
  
  When were the last committers or PPMC members elected? 
  
- 2016-12-6
+   2016-12-6
  
  Signed-off-by: 
  
@@ -872, +894 @@

  Three most important issues to address in the move towards graduation:
  
    1. Licensing, i.e., identifying and solving GPL-related code.
-   2. Coming up with a process of contributing code that makes sense to everyone.
+   2. Coming up with a process of contributing code that makes sense to
+      everyone.
    3. Working on roadmaps, features, and plans together as a community.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -886, +909 @@

  
  How has the project developed since the last report?
  
-   The 1st (out of 12) repository has been cleared by Oracle legal / technical review for
donation.
+   The 1st (out of 12) repository has been cleared by Oracle legal / technical
+   review for donation.
  
-   Dependencies optionally downloaded from Maven Central instead of the project's own public
dependencies server.
+   Dependencies optionally downloaded from Maven Central instead of the
+   project's own public dependencies server.
  
-   Converted Git repositories pushed to GitHub by a community contributor. These are not
canonical since we are waiting for the Code Grant to be signed.
+   Converted Git repositories pushed to GitHub by a community contributor.
+   These are not canonical since we are waiting for the Code Grant to be
+   signed.
  
    First community member pull request on the GitHub repository.
  
@@ -927, +954 @@

  
  Most important issues to address in the move towards graduation:
  
-   1. Get companies backing up the project as part of a commercial story, to get a long-term
momentum
+   1. Get companies backing up the project as part of a commercial story, to
+      get a long-term momentum
-   2. Do recurrent releases - some semi-automation would be helpful - for the 3rd party users
+   2. Do recurrent releases - some semi-automation would be helpful - for the
- 
+      3rd party users
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
+   A discussion has been started about the cancellation of the project due to
+   lack of developers on the private odf-toolkit and private incubator list. 
- A discussion has been started about the cancellation of the project due to lack of developers
on the private odf-toolkit and private incubator list. 
- A general issue of the project is that it 'just' a toolkit of an office file format, which
in addition is far from leading on the business market, so likely never being used by the
mass market - a very niche product.
- Still the toolkit seems to be working well for most common use cases, but is repeatedly
updated by developers on changes of the ODF, like Red Hat developers enhancing the ODF validator
as part of LibreOffice regression tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/)
most often quite ahead of one of the international ODF Plugfests - http://odfplugfest.org/2016-paris/programme/.

- Since there are still some game changing features in the pipeline (e.g. collaboration) which
are expected to strengthen the acceptance and develop the community but on the other hand
the mentorship / infrastructure of the project could be better, a decision needs to be made
on the future.
  
+   A general issue of the project is that it 'just' a toolkit of an office
+   file format, which in addition is far from leading on the business market,
+   so likely never being used by the mass market - a very niche product.
+ 
+   Still the toolkit seems to be working well for most common use cases, but
+   is repeatedly updated by developers on changes of the ODF, like Red Hat
+   developers enhancing the ODF validator as part of LibreOffice regression
+   tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/)
+   most often quite ahead of one of the international ODF Plugfests -
+   http://odfplugfest.org/2016-paris/programme/. 
+ 
+   Since there are still some game changing features in the pipeline (e.g.
+   collaboration) which are expected to strengthen the acceptance and develop
+   the community but on the other hand the mentorship / infrastructure of the
+   project could be better, a decision needs to be made on the future.
  
  How has the community developed since the last report?
   
- We clarified on the ApacheCon Europe that a merge with the Open-XChange fork is
+   We clarified on the ApacheCon Europe that a merge with the Open-XChange
- possible, which extended the original sources still using AL2 and having done several releases
with the new AL2 sources.
+   fork is possible, which extended the original sources still using AL2 and
+   having done several releases with the new AL2 sources.
+ 
- So, we are working on the next release including the fixes and planning a follow-up release
adding new features.
+   So, we are working on the next release including the fixes and planning a
+   follow-up release adding new features.
+ 
- Those features should be able to attract companies to back the project.
+   Those features should be able to attract companies to back the project.
+ 
- In addition, those will be used as reference implementation for the "OASIS Advanced Document
Collaboration" subcommittee.
+   In addition, those will be used as reference implementation for the "OASIS
- 
+   Advanced Document Collaboration" subcommittee.
  
  Date of last release:
  
@@ -970, +1016 @@

  --------------------
  OpenWhisk
  
- OpenWhisk is an open source, distributed Serverless computing platform able to execute application
logic (Actions) in response to events 
- (Triggers) from external sources (Feeds) or HTTP requests governed by conditional logic
(Rules). It provides a programming environment 
+ OpenWhisk is an open source, distributed Serverless computing platform able
+ to execute application logic (Actions) in response to events (Triggers) from
+ external sources (Feeds) or HTTP requests governed by conditional logic
+ (Rules). It provides a programming environment supported by a REST API-based
- supported by a REST API-based Command Line Interface (CLI) along with tooling to support
packaging and catalog services.
+ Command Line Interface (CLI) along with tooling to support packaging and
+ catalog services.
  
  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
+   1. Moving github repos under the Apache Github Org
- 2. Setup jenkins infra server to automate website deployment
+   2. Setup jenkins infra server to automate website deployment
+   3. Review and update project
- 3. Review and update project [checklist](http://incubator.apache.org/projects/openwhisk.html).
+      [checklist](http://incubator.apache.org/projects/openwhisk.html).
  
-    Some items should be mark done (around infra) and followup on committer that there is
a ICLA submitted. Additionally,
+   Some items should be mark done (around infra) and followup on committer
+   that there is a ICLA submitted. Additionally, we add links to the project
-    we add links to the project page to their respctive areas on our .org site and/or newly
created COnfluence Wiki.
+   page to their respctive areas on our .org site and/or newly created
+   COnfluence Wiki.
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
   
- - No issues so far
+   - No issues so far
  
  How has the community developed since the last report?
  
- - dev and private mailing list establish and initial activity healthy
+   - dev and private mailing list establish and initial activity healthy
- - New website deploy openwhisk.org with content from the Github repo
+   - New website deploy openwhisk.org with content from the Github repo
  
  How has the project developed since the last report?
  
- - TBD: gather stats from Github repos commits, issues and pull requests
+   - TBD: gather stats from Github repos commits, issues and pull requests
- - New in core: New API Auth Keys architecture, API Gateway experimental
+   - New in core: New API Auth Keys architecture, API Gateway experimental
- - New in packages: Kafka Feed
+   - New in packages: Kafka Feed
- - Added a "Dockerized" option for running the "wskdeploy" tool
+   - Added a "Dockerized" option for running the "wskdeploy" tool
  
  Date of last release:
  
- - No release yet
+   - No release yet
  
  When were the last committers or PMC members elected?
  
- - No one ha been elected or nominated yet.
+   - No one ha been elected or nominated yet.
  
  Signed-off-by:
  
@@ -1034, +1086 @@

  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?
  
- * Contributors have begun to appear and contribute to the code base
+   * Contributors have begun to appear and contribute to the code base
- * Discussions on dev@ mailing list is beginning
+   * Discussions on dev@ mailing list is beginning
  
  How has the project developed since the last report?
  
- * User accounts created for new folks
+   * User accounts created for new folks
- * ICLA documents submitted and recognized
+   * ICLA documents submitted and recognized
- * SGA document submitted and recognized
+   * SGA document submitted and recognized
- * Mailing lists created
+   * Mailing lists created
- * Git repo created
+   * Git repo created
- * Source code has been imported
+   * Source code has been imported
- * Work has begun on the code base using git pull requests
+   * Work has begun on the code base using git pull requests
  
  Date of last release:
  
- No releases yet
+   No releases yet
  
  When were the last committers or PPMC members elected?
  
- No elections have taken place yet
+   No elections have taken place yet
  
  Signed-off-by:
  
@@ -1076, +1127 @@

  Rya
  
  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
+ supports SPARQL queries. Rya is a scalable RDF data management system built
- top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
+ on top of Accumulo. Rya uses novel storage methods, indexing schemes, and
- processing techniques that scale to billions of triples across multiple nodes.
+ query processing techniques that scale to billions of triples across multiple
- Rya provides fast and easy access to the data through SPARQL, a conventional
+ nodes.  Rya provides fast and easy access to the data through SPARQL, a
- query mechanism for RDF data.
+ conventional query mechanism for RDF data.
  
  Rya has been incubating since 2015-09-18.
  
  Three most important issues to address in the move towards graduation:
  
-  1. Have more releases as part of the Apache Foundation
+   1. Have more releases as part of the Apache Foundation
-  2. Increase diversity of contributors.
+   2. Increase diversity of contributors.
-  3. Continue to harden and develop core Rya features to improve user experience
+   3. Continue to harden and develop core Rya features to improve user
+      experience
  
  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?
  
- * New committer and PPMC member, David Lotts,  was invited and accepted to join Apache Rya
PPMC.
+   * New committer and PPMC member, David Lotts,  was invited and accepted to
+     join Apache Rya PPMC.
- * Committer Caleb Meier joined Rya PPMC.
+   * Committer Caleb Meier joined Rya PPMC.
- * Sean Busbey resigned as mentor
+   * Sean Busbey resigned as mentor
- * Billie Rinaldi became a mentor for Rya
+   * Billie Rinaldi became a mentor for Rya
- * Talk on Rya at Accumulo Summit, October 11, 2016
+   * Talk on Rya at Accumulo Summit, October 11, 2016
- * PRs from non-committers which are integrated into the repository continue to be received
+   * PRs from non-committers which are integrated into the repository continue
+     to be received
  
  How has the project developed since the last report?
  
- * We had the first successful release as part of the ASF
+   * We had the first successful release as part of the ASF
- * Resolved an incompatible-licensed geospatial dependency so we can have the successful
ASF release - we refactored the code to isolate an optional module   
+   * Resolved an incompatible-licensed geospatial dependency so we can have
+     the successful ASF release - we refactored the code to isolate an
+     optional module   
- * Resolved a handful of issues that users have encountered
+   * Resolved a handful of issues that users have encountered
- * Committed features: implemented new commands for Rya console: AddUser (give perimssions
to users for the tables associated with Rya instance), RemoveUser , Uninstall, LoadStatementsFile.
Added merge tool to allow cloning between Mongo and Accumulo instances. Added initial Spark
support.
+   * Committed features: implemented new commands for Rya console: AddUser
+     (give perimssions to users for the tables associated with Rya instance),
+     RemoveUser , Uninstall, LoadStatementsFile. Added merge tool to allow
+     cloning between Mongo and Accumulo instances. Added initial Spark
+     support.
  
  Date of last release:
  
- 2016-10-28
+   2016-10-28
   
  When were the last committers or PMC members elected?
  
@@ -1136, +1196 @@

  
  Spot
  
- Apache Spot is a solution stack that provides the capability to ingest network related telemetry
(network flows, domain name service information and proxy server logs) and provide unsupervised
machine learning capabilities to identify suspicious activity.  The information is organized
and presented using operational analytics so that a security analyst can investigate the most
suspicious connections. Apache Spot is built on an open data model using Apache Spark and
Apache Hadoop.
+ Apache Spot is a solution stack that provides the capability to ingest
+ network related telemetry (network flows, domain name service information and
+ proxy server logs) and provide unsupervised machine learning capabilities to
+ identify suspicious activity.  The information is organized and presented
+ using operational analytics so that a security analyst can investigate the
+ most suspicious connections. Apache Spot is built on an open data model using
+ Apache Spark and Apache Hadoop.
  
  Spot has been incubating since 2016-09-23.
  
  Three most important issues to address in the move towards graduation:
  
-   1.  Move infrastructure and development to ASF (code, issues, mailing list, ...)
+   1. Move infrastructure and development to ASF (code, issues, mailing list, ...)
-   2.  Build diverse community
+   2. Build diverse community
-   3.  Demonstrate ability to create releases
+   3. Demonstrate ability to create releases
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
- Please elaborate on the process for code scanning and IP reviews. On the last report this
was brought to attention but no communication was received.
  
- How has the community developed since the last report?
- Community interaction continues ramping, as new adopters of the project have been posting
questions through Twitter and Slack. Now opening issues over ASF JIRA, and expanding to other
geographies such as Latin America and Europe.
+   Please elaborate on the process for code scanning and IP reviews. On the
+   last report this was brought to attention but no communication was
+   received.
  
- How has the project developed since the last report?
+ How has the community developed since the last report?
- Repo was moved last December, committers have worked over the last month establishing a
process, to get contributions reviewed and voted, which also will give give the opportunity
to get ICLA individuals voted as members of the project.
- In addition, we have been working on the new structure of the project webpage, and new documentation
schema facilitating both project information and documentation on the same site.
- Last but not least,  a convocatory  to discuss roadmap options and project objectives for
Q1 and Q2 will be launched, it will be posted on project webpage and social media.
  
+   Community interaction continues ramping, as new adopters of the project
+   have been posting questions through Twitter and Slack. Now opening issues
+   over ASF JIRA, and expanding to other geographies such as Latin America and
+   Europe.
+ 
+ How has the project developed since the last report?
+ 
+   Repo was moved last December, committers have worked over the last month
+   establishing a process, to get contributions reviewed and voted, which also
+   will give give the opportunity to get ICLA individuals voted as members of
+   the project.
+ 
+   In addition, we have been working on the new structure of the project
+   webpage, and new documentation schema facilitating both project information
+   and documentation on the same site.
+ 
+   Last but not least,  a convocatory  to discuss roadmap options and project
+   objectives for Q1 and Q2 will be launched, it will be posted on project
+   webpage and social media.
+ 
  Date of last release:
+ 
- N/A
+   N/A
  
  When were the last committers or PMC members elected?
+ 
- N/A
+   N/A
  
  Signed-off-by:
  
@@ -1184, +1269 @@

  
  Three most important issues to address in the move towards graduation:
  
- 1. Licenses and legal details. Traffic Control is a project made up of 
+   1. Licenses and legal details. Traffic Control is a project made up of 
       several different components, and includes or depends on an extensive
       list of software. We are working on making sure all source files have 
       the right headers, all the licenses of included software are compatible 
@@ -1202, +1287 @@

    We hosted a 2 day user / dev meetup in the Bay Area in October that was
    attended by 16 people representing 5 companies.
  
- 
  How has the project developed since the last report?
  
    All code has been move to Apache git. All new issues are being opened 
@@ -1219, +1303 @@

      had commit messages going to dev@ as well, so those numbers are not
      indicative of dev communications)
  
- 
- 
  Date of last release:
  
    None yet. We are addressing issues with release 1.8-incubating RC5.  
@@ -1228, +1310 @@

  When were the last committers or PPMC members elected?
  
    No new committers or PPMC members yet.
- 
  
  Signed-off-by:
  
@@ -1248, +1329 @@

  
  Weex has been incubating since 2016-11-30.
  
- This is our first report. Weex community is really excited about joining Apache community
and getting organized.
+ This is our first report. Weex community is really excited about joining
- Most of us are newbie of international open source community, Thanks everybody in ASF for
your patience and encouragement .
+ Apache community and getting organized.  Most of us are newbie of
+ international open source community, Thanks everybody in ASF for your
+ patience and encouragement.
  
  Most notable progress this first month;
+ 
-   1.  7 members of Weex team have submitted ICLAs.
+   1. 7 members of Weex team have submitted ICLAs.
-   2.  SGA & CCLA have been signed and have been mailed to secretary, of ASF.
+   2. SGA & CCLA have been signed and have been mailed to secretary, of ASF.
-   3.  Project maillist & JIRA have been activated &  we have volunteer JIRA administrator.
Our setup issue on JIRA[1] 
+   3. Project maillist & JIRA have been activated &  we have volunteer JIRA
+      administrator. Our setup issue on JIRA[1] 
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- * Code repository need be set up.
+   * Code repository need be set up.
  
  How has the community developed since the last report?
  
- * Weex Github star number was reached 10k on December 21.
+   * Weex Github star number was reached 10k on December 21.
  
  How has the project developed since the last report?
  
- Since our Apache code repository haven’t been setup, the project have not been developed
in Apache Way yet. But our pre-Apache development process are ongoing. Several bugs have been
fixed and some new features have been added (detail of information [2]). We will migrate code
to Apache repo as soon as possible.
+   Since our Apache code repository haven’t been setup, the project have not
+   been developed in Apache Way yet. But our pre-Apache development process
+   are ongoing. Several bugs have been fixed and some new features have been
+   added (detail of information [2]). We will migrate code to Apache repo as
+   soon as possible.
  
  Date of last release:
+ 
- None
+   None
    
  When were the last committers or PPMC members elected?
+ 
- None
+   None
  
  [1]:https://issues.apache.org/jira/browse/WEEX-1
  [2]:https://github.com/alibaba/weex/releases/tag/v0.9.4

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


Mime
View raw message