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 "April2017" by MarvinHumphrey
Date Sat, 08 Apr 2017 00:52:14 GMT
Dear Wiki user,

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

The "April2017" page has been changed by MarvinHumphrey:
https://wiki.apache.org/incubator/April2017?action=diff&rev1=65&rev2=66

Comment:
Reflow Mynewt, NetBeans, ODF Toolkit, Pony Mail.

  
  Three most important issues to address in the move towards graduation:
  
-   1. Demonstrate the capability to do point and major releases that can be used to build
downloadable 
+   1. Demonstrate the capability to do point and major releases that can be
- RTOS images for multiple MCU architectures, peripherals, and network connectivity protocols.
The goal 
+      used to build downloadable RTOS images for multiple MCU architectures,
+      peripherals, and network connectivity protocols. The goal of having a
- of having a first major (1.0) release in the first quarter of 2017 was met. The releases
+      first major (1.0) release in the first quarter of 2017 was met. The
- are intended to demonstrate and solidify the repeatability, usability, and maturity of process.
- 
+      releases are intended to demonstrate and solidify the repeatability,
+      usability, 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, 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. 19 new subscribers on dev@
mailing 
- list since last report resulting in a total of 160 subscribers. 
- 
- 2. Increased participation by several new contributors through pull requests for new MCU
support, merges by
- new committers, new BSP support, connectivity features, and test cases and test results.
There is a measurable 
- increase in usage of the project for 3rd-party products and demos. Outreach continues via
conferences, exhibits, 
- one on one meetings, tutorials, beta testers, prototype and performance testing with multiple
organizations.
- For example, 255 Pull Requests have been closed on GitHub.
- 
- 3. Vigorous discussions, feature proposals, optimizations, code behavior analysis, user
interface improvements, 
- and implementation debates on @dev mailing list. Activity on dev@ list averaged 192 msgs/month
in 2016
- 
- How has the project developed since the last report?
+ How has the community developed since the last report?
  
+   1. Active mailing lists with increasing numbers of subscribers. 19 new
+      subscribers on dev@ mailing list since last report resulting in a total
+      of 160 subscribers. 
+   2. Increased participation by several new contributors through pull
+      requests for new MCU support, merges by new committers, new BSP support,
+      connectivity features, and test cases and test results. There is a
+      measurable increase in usage of the project for 3rd-party products and
+      demos. Outreach continues via conferences, exhibits, one on one
+      meetings, tutorials, beta testers, prototype and performance testing
+      with multiple organizations.  For example, 255 Pull Requests have been
+      closed on GitHub.
+   3. Vigorous discussions, feature proposals, optimizations, code behavior
+      analysis, user interface improvements, and implementation debates on
+      @dev mailing list. Activity on dev@ list averaged 192 msgs/month in 2016
+ 
+ How has the project developed since the last report?
+ 
- 1. The first major release (1.0) was successfully completed on March 22nd. Two beta releases
led up to 
+   1. The first major release (1.0) was successfully completed on March 22nd.
- the first major release - first on December 13, 2016, the second on Feb 24, 2017, with the
final month 
+      Two beta releases led up to the first major release - first on December
+      13, 2016, the second on Feb 24, 2017, with the final month before the
- before the release (between beta2 and 1.0) focusing on bug fixes, performance tuning, and
code cleanup 
+      release (between beta2 and 1.0) focusing on bug fixes, performance
- for a robust first release. An example of policy developed and executed is the Release Policy:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
- 
+      tuning, and code cleanup for a robust first release. An example of
+      policy developed and executed is the Release Policy:
+      https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
- 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
- by members of the community. Proposals for new features are posted on the dev@ mailing list
and voted on
- by community members. 
- 
+      and tracked in ASF JIRA by members of the community. Proposals for new
+      features are posted on the dev@ mailing list and voted on by community
+      members. 
- 3. Effort towards self governance: Voting successfully completed to grant committer status
to five new candidates 
+   3. Effort towards self governance: Voting successfully completed to grant
+      committer status to five new candidates since last report. New committer
- since last report. New committer acceptance policy defined and followed: 
+      acceptance policy defined and followed:
- https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process
+      https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process
- Another example of policy developed and executed is the Release Policy: 
+      Another example of policy developed and executed is the Release Policy:
- https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
+      https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
  
  How would you assess the podling's maturity?
  Please feel free to add your own commentary.
@@ -1403, +1411 @@

  
  How has the community developed since the last report?
  
+   - Several new entries added to Who's Who page:
-   - Several new entries added to Who's Who page: https://cwiki.apache.org/confluence/display/NETBEANS/Who%27s+Who
+     https://cwiki.apache.org/confluence/display/NETBEANS/Who%27s+Who
    - Ongoing discussions on the Apache NetBeans mailing list.
-   - Several updates to http://incubator.apache.org/projects/netbeans.html have been done.
+   - Several updates to http://incubator.apache.org/projects/netbeans.html
+     have been done.
    - Meetups planned in April: Athens, Bangalore, London
  
  How has the project developed since the last report?
  
-   - All repos relating to Java SE NetBeans IDE have been audited on Oracle's side (https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition).
+   - All repos relating to Java SE NetBeans IDE have been audited on Oracle's
+     side (https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition).
-   - Only the code that has been written since the audit started needs to be reviewed, of
the Java SE NetBeans IDE.
+   - Only the code that has been written since the audit started needs to be
+     reviewed, of the Java SE NetBeans IDE.
    - Regular updates on process to Apache NetBeans mailing list.
  
  How would you assess the podling's maturity?
@@ -1484, +1496 @@

    collaboration) which are expected to strengthen the acceptance and develop
    the community.
  
- 
  How has the community developed since the last report?
+ 
    We received with Tom Barber a new active Mentor
  
  How has the project developed since the last report?
+ 
    Update of documentation and bug fixing.
    Our release candidate is currently on a vote on the general incubator list.
  
@@ -1509, +1522 @@

  
    2015-10-05 - Damjan Jovanovic for Committer/PPMC
  
- 
  Signed-off-by:
  
    [ ](odftoolkit) Nick Burch
       Comments:
    [ ](odftoolkit) Yegor Kozlov
       Comments:
-   [ X ](odftoolkit) Tom Barber
+   [X](odftoolkit) Tom Barber
       Comments:
-       Svante is still pretty much the sole developer but there are people testing and voting
on releases. We'll ship this release and figure out how best to market it once the IPMC signs
off on the release.
+        Svante is still pretty much the sole developer but there are people
+        testing and voting on releases. We'll ship this release and figure out
+        how best to market it once the IPMC signs off on the release.
  
  IPMC/Shepherd notes:
  
@@ -1545, +1559 @@

  
  How has the community developed since the last report?
  
- Not much to report here. Community remains the same size.
+   Not much to report here. Community remains the same size.  We are
- We are discussing releasing a new version soon(ish).
+   discussing releasing a new version soon(ish).
  
  How has the project developed since the last report?
  
- Many bug fixes, but no new release yet. TBD.
+   Many bug fixes, but no new release yet. TBD.
- 
  
  How would you assess the podling's maturity?
  Please feel free to add your own commentary.

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


Mime
View raw message