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 "April2016" by niq
Date Wed, 06 Apr 2016 22:37:25 GMT
Dear Wiki user,

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

The "April2016" page has been changed by niq:
https://wiki.apache.org/incubator/April2016?action=diff&rev1=37&rev2=38

  = Incubator PMC report for April 2016 =
- 
  === Timeline ===
  ||Wed April 06 ||Podling reports due by end of day ||
  ||Sun April 10 ||Shepherd reviews due by end of day ||
@@ -42, +41 @@

  ||[none] ||Sirona ||
  ||[none] ||Toree ||
  
+ 
  === Report content ===
  {{{
  Incubator PMC report for April 2016
@@ -71, +71 @@

  * Graduations
  
    The board has motions for the following:
-   
+ 
    - Johnzon
  
  
@@ -180, +180 @@

  
  How has the community developed since the last report?
  
-   The community is very engaged with the development of the project. 
+   The community is very engaged with the development of the project.
    We see continious uptick in mailing list participaton (2180 messages on dev@ for March,
122+ subscribers).
-   
+ 
    The community discussed graduation, addressed outstanding issues and completed VOTE.
  
    The community has been active building additional meetup groups: http://s.apache.org/jKT
    Many presentations and uptick in engagement.
-   
+ 
  How has the project developed since the last report?
  
    Release 3.3.1-icubating of Malhar on 2016-03-02
-   
+ 
    Various metrics for March are as follows:
    +---------------------------------------------------+
    |   Metric                         | Core  | Malhar |
@@ -204, +204 @@

    | Pull Requests proposed           |   2   |   11   |
    +---------------------------------------------------+
  
-   We are anticipating patch release 3.2.1 in April. 
+   We are anticipating patch release 3.2.1 in April.
  
  Date of last release:
  
    2016-03-02 Apex (Malhar) 3.3.1-incubating
-   
+ 
  When were the last committers or PMC members elected?
  
    2 PPMC members and 1 committer were added since December.
@@ -369, +369 @@

  Shepherd/Mentor notes:
  
    Julian Hyde (jhyde):
-   
+ 
      No report, despite prodding from Chris, and no activity on lists.
      I think this one's dead.
  
@@ -433, +433 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1.Finalising the initial release 
+   1.Finalising the initial release
    2.Improve the communication around the differences between the previous MifosX project
and the new Fineract project, especially in the MifosX community, website etc.
    3.With the first initial release, encourage the community to use the proper infastructure
(mailing lists, issue tracker) for the ongoing collaboration within the community.
    4.Change management towards less 'key-man' dependency on previous tech/community leaders
from MifosX, more towards community driven consensus.
@@ -442, +442 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
- On the mailinglist there have been discussions around the lack of traffic on it. This is
part of the switchover from the current MifosX community and mailinglists towards the new
Fineract lists. At the same time the recent meet-up of Mifosx and Fineract devs and people
interested in it (see community development), has also triggered a lot of offline interaction.

+ On the mailinglist there have been discussions around the lack of traffic on it. This is
part of the switchover from the current MifosX community and mailinglists towards the new
Fineract lists. At the same time the recent meet-up of Mifosx and Fineract devs and people
interested in it (see community development), has also triggered a lot of offline interaction.
  
  How has the community developed since the last report?
  
  While activity on the mailinglist has been pretty low, we've had a great meet-up in Amsterdam
where a nice mix of existing MifosX community members and a group of new interested people
was present. This has boosted interest in Fineract.
  
- We have a high level of interest from new contributors throughout Africa - we are working
to properly engage them and guide them to the correct collaboration channels in our Fineract
community. 
+ We have a high level of interest from new contributors throughout Africa - we are working
to properly engage them and guide them to the correct collaboration channels in our Fineract
community.
  
  How has the project developed since the last report?
  
- Individual members of the leading partner organizations building solutions using the Fineract
platform have begun to effectively use the Fineract issue tracker to communicate and track
the requirements and enhancements they're building and contributing to Fineract. These individuals
are setting a good example that other individuals from our partner community should follow.

+ Individual members of the leading partner organizations building solutions using the Fineract
platform have begun to effectively use the Fineract issue tracker to communicate and track
the requirements and enhancements they're building and contributing to Fineract. These individuals
are setting a good example that other individuals from our partner community should follow.
  
  Date of last release:
  
@@ -799, +799 @@

  How has the community developed since the last report?
  
    There have been no additions to the committer or PMC lists since
-   incubation began. We continue to see an uptick in external contributions, with two patches
from new contributors this month. One contributor pleasingly reported it was "great to work
closely with Impala community". 
+   incubation began. We continue to see an uptick in external contributions, with two patches
from new contributors this month. One contributor pleasingly reported it was "great to work
closely with Impala community".
  
  How has the project developed since the last report?
  
    We have put together a list of tasks required to move development of Impala from
-   Cloudera's infrastructure to the ASF. Since Impala was already a well-established project
before the Incubator proposal, there is perhaps more decoupling required than for more nascent
projects. The list is at https://issues.cloudera.org/browse/IMPALA-3221, and is being actively
worked on. Note that this doesn't cover the standard podling tasks (like name search, etc).

+   Cloudera's infrastructure to the ASF. Since Impala was already a well-established project
before the Incubator proposal, there is perhaps more decoupling required than for more nascent
projects. The list is at https://issues.cloudera.org/browse/IMPALA-3221, and is being actively
worked on. Note that this doesn't cover the standard podling tasks (like name search, etc).
  
  Date of last release:
  
@@ -936, +936 @@

  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
-   None that come to mind. We are occupied with the issues above, and 
+   None that come to mind. We are occupied with the issues above, and
    things are proceeding nicely.
  
  How has the community developed since the last report?
  
-   We have voted in two new committers and invitations have been 
+   We have voted in two new committers and invitations have been
    extended to them.
  
  How has the project developed since the last report?
  
-   A large pull request was accepted reporting large speed increases due to 
+   A large pull request was accepted reporting large speed increases due to
    caching, and increasing the usability of Joshua as a library.
  
  Date of last release:
@@ -1052, +1052 @@

   - We added support for indexing enriched sensor capture data into Apache Solr indexing
as well as Elasticsearch
  
  Signed-off-by:
-  
+ 
   [X](metron) Billie Rinaldi
   [ ](metron) Chris Mattmann
   [ ](metron) Owen O'Malley
@@ -1066, +1066 @@

  --------------------
  Milagro
  
- Distributed Cryptography; M-Pin protocol for Identity and Trust
+ Distributed Cryptography;
+ M-Pin and other pairing protocols for Identity and Trust
  
  Milagro has been incubating since 2015-12-21.
  
  Three most important issues to address in the move towards graduation:
  
-   1.
-   2.
-   3.
+   1. Import the software: The source code is already prepared and placed in
+ repositories on GitHub – soon to be imported to Apache repositories. This
+ includes a full Milagro MFA implementation.
+   2. Awareness among developers: Milagro announcement – during ApacheCon
+ North America – May 2016
+   3. General Awareness
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
  aware of?
  
+ n/a
  
- 
- How has the community developed since the last report?
- 
- 
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+ No substantial developments to report.  The project is targeting
+ community development following Apachecon presentations.
  
+ How has the project developed since the last report?
  
- Date of last release:
+ Project members are preparing to present the project at ApacheCon
+ with a view to connecting with the wider Apache community and
+ finding synergies with other projects.
  
-   XXXX-XX-XX
+ Date of last release:
  
- When were the last committers or PMC members elected?
+   n/a
  
+ When were the last committers or PMC members elected?
  
+ February, as reported.
  
  Signed-off-by:
  
    [ ](milagro) Sterling Hughes
    [ ](milagro) Jan Willem Janssen
-   [ ](milagro) Nick Kew
+   [x](milagro) Nick Kew
  
  Shepherd/Mentor notes:
  
@@ -1117, +1124 @@

  
   Various metrics for March are as follows:
    +--------------------------------------------+
-   |   Metric                         | counts  | 
+   |   Metric                         | counts  |
    +--------------------------------------------+
-   | Non Merge Commits                |  82     | 
+   | Non Merge Commits                |  82     |
-   | Contributors                     |  10     | 
+   | Contributors                     |  10     |
    | Jira New Issues                  |  13     |
-   | Resolved Issues                  |   4     | 
+   | Resolved Issues                  |   4     |
    | Pull Requests merged             |         |
-   | Pull Requests proposed           |   3     | 
+   | Pull Requests proposed           |   3     |
    +--------------------------------------------+
  
  Three most important issues to address in the move towards graduation:
@@ -1154, +1161 @@

  
  When were the last committers or PMC members elected?
  No election, since the project is just starting.
- As part of incubation process, initial committers and contributors were proposed and added.

+ As part of incubation process, initial committers and contributors were proposed and added.
  
  
  Signed-off-by:
@@ -1179, +1186 @@

  
  Three most important issues to address in the move towards graduation:
  
-   1. Make further releases capable of producing a downloadable RTOS image with support for
multiple peripherals and network connectivity. Do subsequent releases to indicate thorough
understanding, repeatability, and maturity of process. 
+   1. Make further releases capable of producing a downloadable RTOS image with support for
multiple peripherals and network connectivity. Do subsequent releases to indicate thorough
understanding, repeatability, and maturity of process.
-   2. Continue to develop and execute policies that enable project contributors to achieve
self-governance 
+   2. Continue to develop and execute policies that enable project contributors to achieve
self-governance
    3. Expand community - attract new project contributors and users, grow committer base
  
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
@@ -1197, +1204 @@

  How has the project developed since the last report?
  
  1. Releases:  Two releases so far - first on 22nd Feb, next on 18th March
- 	- Identified and fixed license issues, regular process established to check for license
issues esp. with third party software
+         - Identified and fixed license issues, regular process established to check for
license issues esp. with third party software
- 	- Tagging process and release candidate naming process tested and used
+         - Tagging process and release candidate naming process tested and used
- 	- Voting process and timelines established and used
+         - Voting process and timelines established and used
  2. Documentation support: Several committers added documentation either through direct git
pushes or pull requests on github mirror.
- 3. Effort towards self governance: 
+ 3. Effort towards self governance:
- 	- Two releases completed successfully. 
+         - Two releases completed successfully.
- 	- Two committer candidates going through voting for committer status after meeting threshold
of patch submissions.
+         - Two committer candidates going through voting for committer status after meeting
threshold of patch submissions.
  
  Date of last release:
  
@@ -1333, +1340 @@

  aware of?
  Nothing jumps to mind.
  
- How has the community developed since the last report?	
+ How has the community developed since the last report?
  The Quarks community is keeping dev-related conversations on the mailing list. Because of
this, it's allowed for the participation of independent contributors in mailing list discussions.
Although our list of independent contributors is small, Quarks is still very new as an Apache
project and we aim to actively grow our list in the near future.
  
  How has the project developed since the last report?
- * The project has successfully migrated from Github-based development to using the Apache
git repo, Jira, and the mailing lists.	
+ * The project has successfully migrated from Github-based development to using the Apache
git repo, Jira, and the mailing lists.
  
  Date of last release:
  
@@ -1416, +1423 @@

    1. Become familiar with the release process and have a first release as part of the Apache
Foundation
    2. Expand the "how to" document to explain the ways new contributors can become involved
in the project, so we increase the size of the community.
    3. Add new committers to the project.
-   
+ 
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
  
  No
  
  How has the community developed since the last report?
  
-    * We have a Rya "office hour" teleconference every other week. We had some technical
difficulties with screen sharing, but we had a working solution for the last meeting. Users
and developers can ask questions, receive answers, discuss ideas for future developments.
The minutes are sent to the dev@ list.  
+    * We have a Rya "office hour" teleconference every other week. We had some technical
difficulties with screen sharing, but we had a working solution for the last meeting. Users
and developers can ask questions, receive answers, discuss ideas for future developments.
The minutes are sent to the dev@ list.
     * We have more PRs from non-committers which are integrated into the repository. We expect
some of these non-committers to continue to submit PRs and become committers.
     * There were several ideas from Rya for Google Summer of Code, and a few students expressed
interest; one of them submitted a proposal
-  
+ 
  How has the project developed since the last report?
  
    * Created a quick-start VM for users to try out Rya.
    * Created a website for the project.
    * Resolved a handful of issues that users have encountered.
    * Committed features: incremental update for precomputed join indices, extensions to query
planning to support more complex precomputed join indices, free text search support for MongoDB,
additional Geo indexing for MongoDB, extensions of examples for both Accumulo and MongoDB
backed Rya
-     
+ 
  
  Date of last release:
  
@@ -1442, +1449 @@

  When were the last committers or PMC members elected?
  
    Not applicable
-   
+ 
  Signed-off-by:
  
    [x](rya) Josh Elser
@@ -1452, +1459 @@

  
  Shepherd/Mentor notes:
  
- sb: project activity was a little slow, due to other time commitments for    
+ sb: project activity was a little slow, due to other time commitments for
-     the dev community, but folks had a great discussion around next steps   
+     the dev community, but folks had a great discussion around next steps
      when it came time for a draft report.
  
  --------------------
@@ -1621, +1628 @@

  How has the community developed since the last report?
  - We made our first release.
  - Elected new committer.
- - Previously private fork (wiab.pro) opened the source code that includes many improvements
that can be integrated back into main project. 
+ - Previously private fork (wiab.pro) opened the source code that includes many improvements
that can be integrated back into main project.
  - Also, there's an active development in additional open source fork (swellrt) that potentially
allows us to integrate back important features.
  
  
@@ -1644, +1651 @@

  [ ](wave) Upayavira
  
  Shepherd/Mentor notes:
- 
- 
  }}}
  

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


Mime
View raw message