Here’s the December report for Mynewt.
Mentors, please review and comment before I post it on the Incubator wiki page.
thanks,
aditi
===============
Mynewt
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. 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 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
documentation site
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:
[ ](mynewt) Sterling Hughes
[ ](mynewt) Jim Jagielski
[ ](mynewt) Justin Mclean
[ ](mynewt) Greg Stein
[ ](mynewt) P. Taylor Goetz
Shepherd/Mentor notes:
> On Nov 26, 2015, at 12:38 PM, Marvin Humphrey <[email protected]> wrote:
>
>
> Greetings, {podling} developers!
>
> This is a reminder that your report is due next Wednesday, December
> 2nd. Details below.
>
> Best,
>
> Marvin Humphrey, Report Manager for December, on behalf of the
> Incubator PMC
>
> ---------------
>
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 December 2015, 10:30 am PST.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, December 2nd).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/December2015
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>
