approved! (binding)... (will 'sign-off' when posted on the wiki)
> On Apr 3, 2017, at 9:33 PM, aditi hilbert <[email protected]> wrote:
>
>
> Hi Mentors,
>
> Here’s the first draft of Mynewt’s board report for April.
> Please review it and comment. The board meeting is scheduled for Wed, 19
> April 2017, and
> we need to submit the report 2 weeks before that (Wed, April 5).
>
> thanks,
> aditi
>
> ==================
> 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.
> 3. Vigorous discussions, feature proposals, optimizations, code behavior
> analysis, user interface improvements,
> and implementation debates on @dev mailing list.
>
> 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.
> 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.
>
> Date of last release:
>
> 2017-03-22
>
> When were the last committers or PPMC members elected?
>
> 2016-12-6
>
> Signed-off-by:
>
> [ ](mynewt) Sterling Hughes
> [ ](mynewt) Jim Jagielski
> [ ](mynewt) Justin Mclean
> [ ](mynewt) Greg Stein
> [ ](mynewt) P. Taylor Goetz
>
> Shepherd/Mentor notes:
