Apache Logo
The Apache Way Contribute ASF Sponsors

Formal board meeting minutes from 2010 through present. Please Note: The board typically approves minutes from one meeting during the next board meeting, so minutes will be published roughly one month later than the scheduled date. Other corporate records are published, as is an alternate categorized view of all board meeting minutes.

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

Mynewt

19 Apr 2017

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

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: