Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-10-16 20:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Mynewt

20 Sep 2017 [Justin Mclean / Rich]

Report was filed, but display is awaiting the approval of the Board minutes.

16 Aug 2017 [Justin Mclean / Bertrand]

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

- Move to TLP  complete
- Made first release as a TLP
- Community work in several areas including new PWM driver and support for
other boards

## Health report:

- PMC and committers are active
- Users questions and contributor's pull requests are dealt with in a timely
manner

## PMC changes:

- Currently 19 PMC members
- No new PMC members added since last report
- Last PMC addition was everyone on 21st June

## Committer base changes:

- Currently 23 committers
- No new committers added since last report
- Last committer addition was Jacob Rosenthal on 13th June 2017

## Releases:

- 1.1 was released on  Aug 01 2017

## Mailing list activity:

- Activity a little down on last month.

## JIRA activity:

- Activity less than last month with more JIRAs closed than raised.

19 Jul 2017 [Justin Mclean / Ted]

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

- Just become a TLP. Move to TLP has been fairly smooth with minimal
infrastructure issues.
- Took part in the Apache IoT track at ApacheCon Miami with 3 talks on Mynewt
- Work on how to report security issues
- Community work on porting to new platforms and supporting new languages
(MicroPython) is on going
- Working towards a mid-July release of 1.1

## Health report:

- PMC and committers are active
- Users questions and contributor's pull requests are dealt with in a timely
manner

## PMC changes:

- Currently 19 PMC members
- Last PMC addition was everyone on 21st June

## Committer base changes:

- Currently 23 committers
- Last committer addition was Jacob Rosenthal on 13th June 2017

## Releases:

- Last release was 1.0 on March 22nd, 2017

## Mailing list activity:

- Compared to previous period activity down a little on list as user some user
question are being answered on Slack (mynewt.slack.com) but there's 26 new
subscribers.

## JIRA activity:

- Activity about the same as previous period (100 odd JIRAs) with more JIRAs
closed than raised.

21 Jun 2017

Establish the Apache Mynewt Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to the
 public, related to an embedded OS optimized for networking and built
 for remote management of constrained devices that are incapable
 of running either Linux or Android.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache Mynewt Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache Mynewt Project be and hereby is
 responsible for the creation and maintenance of software
 related to an embedded OS optimized for networking and built
 for remote management of constrained devices that are incapable
 of running either Linux or Android.

 RESOLVED, that the office of "Vice President, Apache Mynewt" be
 and hereby is created, the person holding such office to
 serve at the direction of the Board of Directors as the chair
 of the Apache Mynewt Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache Mynewt Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache Mynewt Project:
     Justin Mclean <jmclean@apache.org>
     P. Taylor Goetz <ptgoetz@apache.org>
     Greg Stein <gstein@apache.org>
     Jim Jagielski <jim@apache.org>
     Sterling Hughes <sterling@apache.org>
     Marko Kiiskila <marko@apache.org>
     Will Sanfilippo <wes3@apache.org>
     Christopher Collins <ccollins@apache.org>
     Vipul Rahane <vipulrahane@apache.org>
     Fabio Utzig <utzig@apache.org>
     Andrzej Kaczmarek <andk@apache.org>
     Michał Narajowski <naraj@apache.org>
     Szymon Janc <janc@apache.org>
     Łukasz Rymanowski <rymek@apache.org>
     Neel Natu <neel@apache.org>
     Peter Snyder <peterfs@apache.org>
     Paul Dietrich <paulfdietrich@apache.org>
     Julian Ingram <julian@apache.org>
     Aditi Hilbert <aditi@apache.org>

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Justin Mclean
 be appointed to the office of Vice President, Apache Mynewt, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache Mynewt PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache Mynewt Project; and be it further

 RESOLVED, that the Apache Mynewt Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator Mynewt podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Mynewt podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

 Special Order 7F, Establish the Apache Mynewt Project, was
 approved by Unanimous Vote of the directors present.

19 Apr 2017

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

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 RTOS images for multiple MCU architectures,
     peripherals, and network connectivity protocols. The goal of having a
     first major (1.0) release in the first quarter of 2017 was met. The
     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.
  3. Expand community - attract new project contributors, get users with
     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

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 the first major release - first on December
     13, 2016, the second on Feb 24, 2017, with the final month before the
     release (between beta2 and 1.0) focusing on bug fixes, performance
     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 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 since last report. New committer
     acceptance policy defined and followed:
     https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process
     Another example of policy developed and executed is the Release 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.

  [ ] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [x] Nearing graduation
  [ ] Other:

Date of last release:

  2017-03-22

When were the last committers or PPMC members elected?

 2017-03-28

Signed-off-by:

  [ ](mynewt) Sterling Hughes
     Comments:
  [X](mynewt) Jim Jagielski
     Comments:
  [X](mynewt) Justin Mclean
     Comments:
  [ ](mynewt) Greg Stein
     Comments:
  [x](mynewt) P. Taylor Goetz
     Comments:
         In my opinion Mynewt is ready to graduate. I will
         bring up that prospect with the podling.

18 Jan 2017

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

Three most important issues to address in the move towards graduation:

 1. Make further point releases capable of producing a downloadable RTOS
    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
    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.
 3. Expand community - attract new project contributors, get users with
    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

How has the community developed since the last report?

 1. Active mailing lists with increasing numbers of subscribers. 23 new
    subscribers on dev@ mailing list since last report.
 2. Increased participation by several new contributors through pull
    requests for new MCU support, new BSP support, features, and test cases
    and test results. Increased usage of the project for 3rd-party products
    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 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 second beta is being considered before
    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 by members of the community.
 3. Effort towards self governance: Voting successfully completed to grant
    committer status to two new candidates since last report.

Date of last release:

 2016-12-13

When were the last committers or PPMC members elected?

 2016-12-6

Signed-off-by:

[ ](mynewt) Sterling Hughes
[X](mynewt) Jim Jagielski
[x](mynewt) Justin Mclean
[ ](mynewt) Greg Stein
[x](mynewt) P. Taylor Goetz

19 Oct 2016

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

Three most important issues to address in the move towards graduation:

 1. Make further point releases capable of producing a downloadable RTOS image
   with support for multiple peripherals and network connectivity with the
   goals of the first major (1.0) release in the last quarter of 2016 and
   continued demonstration of thorough understanding, repeatability, and
   maturity of process.
 2. Continue to develop and execute policies that enable project contributors
   to achieve self-governance.
 3. Expand community - attract new project contributors and users with diverse
   backgrounds, grow committer base.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

None

How has the community developed since the last report?

1. Active mailing lists with increasing numbers of subscribers. 15 new
subscribers on dev@ mailing list since last report. 2. Increased participation
by 3rd parties through pull requests for new BSP support, features, and test
cases. Outreach continues via conferences, exhibits, one on one meetings, beta
testers, GSoC participation. 3. Vigorous discussions, feature proposals, and
implementation suggestions on @dev mailing list.

How has the project developed since the last report?

1. Releases: No new releases since June 6th but work on several branches are
being merged for first 1.0 beta release in October. The project has now closed
100+ pull requests. 2. Planning: Issues including bug reports, features, and
wish list captured and tracked in ASF JIRA by members of the community. Work
continues against 125 tickets opened for 1.0 releases (beta and GA). 3. Effort
towards self governance: Voting successfully completed to grant committer
status to one new candidate since last report.

Date of last release:

 2016-06-06

When were the last committers or PMC members elected?

 2016-10-04

Signed-off-by:

 [ ](mynewt) Sterling Hughes
 [X](mynewt) Jim Jagielski
 [X](mynewt) Justin Mclean
 [ ](mynewt) Greg Stein
 [X](mynewt) P. Taylor Goetz

-------------------- ODF Toolkit

Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents

ODF Toolkit has been incubating since 2011-08-01.

Three most important issues to address in the move towards graduation:

 1. Attract more developers
 2. Have frequent releases
 3. Decide on possible ways to graduate

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 None.

How has the community developed since the last report?

 Patches had been provided from LibreOffice developers for the ODF validator.

How has the project developed since the last report?

Svante Schubert is working on the major collaboration feature, likely to
attract more developers. He aims to get the basic updates in before the next
release based on JDK6. The release is aimed to be before the ApacheCon EU and
one release afterwards on JDK 8 including the feature. He will attent the
ApacheCon EU to get in contact with people from the POI project in order to
evaluate possible ways to graduate.

Date of last release:

 2014-06-02

When were the last committers or PMC members elected?

 2012-10-29


Signed-off-by:

 [ ](odftoolkit) Sam Ruby
 [X](odftoolkit) Nick Burch
 [ ](odftoolkit) Yegor Kozlov

Shepherd/Mentor notes:

Nick Burch (nick) - hopefully the discussions at ApacheCon will let us
formulate a plan for where the project should go, to bring back to the list,
and hopefully get ODF Toolkit out of the incubator!

20 Jul 2016

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

Three most important issues to address in the move towards graduation:

 1. Make further point releases capable of producing a downloadable RTOS
    image with support for multiple peripherals and network connectivity
    with the goals of the first major (1.0) release in the last quarter of
    2016 and continued demonstration of thorough understanding,
    repeatability, and maturity of process.
 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
aware of?

 None

How has the community developed since the last report?

 1. Active mailing lists with increasing numbers of subscribers. The
    subscriber count more than doubled since the April report.
 2. Continued outside interest by 3rd parties as evidenced by use in
    multiple new devices, bug reporting and fixing, feature additions.
    Outreach via conferences, exhibits, one on one meetings, beta testers,
    GSoC participation.
 3. Vigorous discussions and implementation decisions via proposals and
    voting on @dev mailing list.

How has the project developed since the last report?

 1. Releases: Four releases so far, two since the last report. The latest
    was version 0.9 on June 9th.
    - Regular process established and followed to check for license issues
      esp. with third party software
    - Tagging process and release candidate naming process tested and used
    - Voting process and timelines established and used
 2. Documentation support: In addition to committers, several
    non-committers added documentation through pull requests on github
    mirror according to defined process.
    - Support for versioning of documents added - to be used starting next
      release.
 3. Effort towards self governance:
    - Four releases completed successfully.
    - Voting successfully completed to grant committer status to two
      candidates after meeting threshold of patch submissions. Several new
      committer candidates are in the pipeline.

Date of last release:

 2016-06-06

When were the last committers or PMC members elected?

 At the start

Signed-off-by:

 [ ](mynewt) Sterling Hughes
 [X](mynewt) Jim Jagielski
 [X](mynewt) Justin Mclean
 [ ](mynewt) Greg Stein
 [X](mynewt) P. Taylor Goetz

Shepherd/Mentor notes:

 Drew Farris:

   Three mentors active on mailing lists. High activity on mailing lists.

20 Apr 2016

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

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.
 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
aware of?

  None

How has the community developed since the last report?

 1. Healthy, active mailing lists with increasing numbers of subscribers
 2. Continual outside interest by 3rd parties. Outreach via conferences,
    exhibits, one on one meetings, beta testers, GSoC participation.
 3. Vigorous discussions and implementation decisions via proposals and
    voting on @dev mailing list.

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
    - Tagging process and release candidate naming process tested 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:
    - Two releases completed successfully.
    - Two committer candidates going through voting for committer status
      after meeting threshold of patch submissions.

Date of last release:

 2016-03-18

When were the last committers or PMC members elected?

 At the start

Signed-off-by:

 [ ](mynewt) Sterling Hughes
 [X](mynewt) Jim Jagielski
 [X](mynewt) Justin Mclean
 [ ](mynewt) Greg Stein
 [ ](mynewt) P. Taylor Goetz

20 Jan 2016

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

Three most important issues to address in the move towards graduation:

 1. Do a first Apache release capable of producing a downloadable RTOS
    image with support for multiple peripherals and network connectivity.
 2. 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
aware of?

 None

How has the community developed since the last report?
 1. Mailing list activity since last report:
    @dev      52 messages (1 Dec to 5 Jan), 1 new subscribers (20 total)
    @commits  150+ messages
 2. Repo is being cloned and looked at by several outside parties - need
    to get all interested parties on the dev mailing list.
 3. Participation on the @dev mailing list covered a range of topics
    including feature implementation approaches, coding practices, website,
    and documentation rules discussions.

How has the project developed since the last report?

 1. Feature support: 2 new JIRA issues were created to facilitate feature
    implementation and website discussions
 2. Documentation support: Two new committers have started adding material
    to technical documentation.
 3. Effort towards community growth: We have redesigned the project website
    to organize and present content more clearly and to highlight upcoming
    events where the project will have exposure.
 4. Effort towards self governance: Consensus reached on how a potential
    contributor is accepted over time as a committer based on quality of
    work.

Date of last release:

 XXXX-XX-XX

When were the last committers or PMC members elected?



Signed-off-by:

 [ ](mynewt) Sterling Hughes
 [X](mynewt) Jim Jagielski
 [X](mynewt) Justin Mclean
 [X](mynewt) Greg Stein
 [X](mynewt) P. Taylor Goetz

Shepherd/Mentor notes:

16 Dec 2015

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

 1. Do a first Apache release capable of producing a downloadable RTOS
    image with support for multiple peripherals and network connectivity.
 2. Expand community - attract new project contributors and users & grow
    committer base
 3. Develop a roadmap and release schedule for the Mynewt Operating System

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None.

How has the community developed since the last report?

 1. Mailing list activity since last report:
    @dev      48 messages, 2 new subscribers
    @commits  140 messages
 2. Committer workflow was tested on documentation site.
 3. Participation on the @dev mailing list covered a range of topics
    including feature priorities, coding practices, Go package handling
    options, and logo discussions.

How has the project developed since the last report?

 1. Feature support: 12 JIRA issues were created and are in various stages
    of progress after discussion about relative priorities on @dev mailing
    list.
 2. Documentation support: non-committer workflow discussed and tested on
    site.
 3. Progress towards self-governance: We have a potential new committer
    already, and the community is discussing its policy/culture about
    adding committers and PMC members.

Date of last release:

 No release yet.

When were the last committers or PMC members elected?

 At the start of the project (2015-10-20)

Signed-off-by:

 [X](mynewt) Sterling Hughes
 [X](mynewt) Jim Jagielski
 [X](mynewt) Justin Mclean
 [X](mynewt) Greg Stein
 [X](mynewt) P. Taylor Goetz

Shepherd/Mentor notes:

18 Nov 2015

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

Three most important issues to address in the move towards graduation:

 1. Produce a first Apache release of downloadable RTOS image with
    support for multiple peripherals and network connectivity.
 2. Develop a roadmap and release schedule for the Mynewt Operating System
 3. Expand the community, increase dev list activity, and add new
    committers/pmc members.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 Just started incubation, nothing specific to report at this time.

How has the community developed since the last report?

 We are approximately 2 weeks into the incubation process.

 1. Core infrastructure has been set up. Core contributors have completed
    their ICLA’s. Apache accounts, mailing lists, JIRA, and website are in
    place.
 2. First drop of documentation is linked to the incubator website on AFS.
 3. Participation on the @dev mailing list was seen with installation
    queries and troubleshooting questions from mentors and 1 new
    subscriber.

How has the project developed since the last report?

 Early activity:

 1. Initial code drop on Apache git repository for Mynewt RTOS for M4 and
    M3 architectures in debug environment
 2. Initial code drop on Apache git repository for newt tool to build basic
    RTOS images
 3. Core infrastructure is set up

Date of last release:

 No release yet.

When were the last committers or PMC members elected?

 Initial list of committers have been on-boarded.
 No new members added on top of the initial committer list.

Signed-off-by:

 [x](mynewt) Sterling Hughes
 [x](mynewt) Jim Jagielski
 [x](mynewt) Justin Mclean
 [X](mynewt) Greg Stein
 [x](mynewt) P. Taylor Goetz

Shepherd/Mentor notes: