You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by aditi hilbert <ad...@runtime.io> on 2016/04/06 03:22:11 UTC
April board report for Mynewt
Hi Mentors,
Here’s the first draft of Mynewt’s board report for April. Please review it.
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. Do a first Apache release 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. Mailing list activity since last report in January:
@dev 500+ messages exchanged, 26 new subscribers (46 total)
@commits 400+ messages, 3 new committers (19 total)
2. Repo is being cloned and looked at by external parties including 5+ device/chip vendors, student community, and researchers.
3. Active participation on the @dev mailing list covered a range of topics including feature implementation approaches (e.g. Hardware Abstraction Layer, Newt build tool options, logs and stats amongst several others), code size concerns and mitigations of those concerns, coding practices, documentation fixes and enhancements. Feedback from beta testers received and discussed.
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. Feature support: several new OS, BLE features and new board support added
3. Documentation support: Several committers added documentation either through direct git pushes or pull requests on github mirror.
4. Effort towards self governance: Two releases completed successfully.
Date of last release:
18 March, 2016
When were the last committers or PMC members elected?
At the start.
Signed-off-by:
[ ](mynewt) Sterling Hughes
[ ](mynewt) Jim Jagielski
[ ](mynewt) Justin Mclean
[ ](mynewt) Greg Stein
[ ](mynewt) P. Taylor Goetz
Shepherd/Mentor notes:
Re: April board report for Mynewt
Posted by Jim Jagielski <ji...@jaguNET.com>.
+1
Thx!
> On Apr 6, 2016, at 1:33 AM, aditi hilbert <ad...@runtime.io> wrote:
>
> Justin,
>
> Thanks for the review. Here is the revised draft. I am trying to upload it to the Apache site now.
>
> I misspoke actually. Three new people started adding code via pull requests/patches. We decided on the process to add committers but never formally put the two largest contributors (committer candidates) to vote. I’ll send out the formal request for vote.
>
> 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. 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:
> 18 March, 2016
>
> When were the last committers or PMC members elected?
> At the start.
>
> Signed-off-by:
> [ ](mynewt) Sterling Hughes
> [ ](mynewt) Jim Jagielski
> [ ](mynewt) Justin Mclean
> [ ](mynewt) Greg Stein
> [ ](mynewt) P. Taylor Goetz
>
> Shepherd/Mentor notes:
Re: April board report for Mynewt
Posted by aditi hilbert <ad...@runtime.io>.
Justin,
Thanks for the review. Here is the revised draft. I am trying to upload it to the Apache site now.
I misspoke actually. Three new people started adding code via pull requests/patches. We decided on the process to add committers but never formally put the two largest contributors (committer candidates) to vote. I’ll send out the formal request for vote.
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. 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:
18 March, 2016
When were the last committers or PMC members elected?
At the start.
Signed-off-by:
[ ](mynewt) Sterling Hughes
[ ](mynewt) Jim Jagielski
[ ](mynewt) Justin Mclean
[ ](mynewt) Greg Stein
[ ](mynewt) P. Taylor Goetz
Shepherd/Mentor notes:
Re: April board report for Mynewt
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> 1. Do a first Apache release 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.
As we already have made releases perhaps change to “Make further releases” ?
> 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
> 1. Mailing list activity since last report in January:
> @dev 500+ messages exchanged, 26 new subscribers (46 total)
> @commits 400+ messages, 3 new committers (19 total)
IMO just replace with “Healthy active mailing list with increasing subscribers”?
> 2. Repo is being cloned and looked at by external parties including 5+ device/chip vendors, student community, and researchers.
Perhaps reword? Continual outside interest by 3rd parties? What are we doing to attract them to be involved here?
> 3. Active participation on the @dev mailing list covered a range of topics including feature implementation approaches (e.g. Hardware Abstraction Layer, Newt build tool options, logs and stats amongst several others), code size concerns and mitigations of those concerns, coding practices, documentation fixes and enhancements. Feedback from beta testers received and discussed.
Probably cut the above as may not be much interest to the board.
> 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
>
Also probably not of interest to the board is:
> 2. Feature support: several new OS, BLE features and new board support added
> When were the last committers or PMC members elected?
>
> At the start.
We have added committers right? "3 new committers” are mentioned above. (That why I like a VOTE for committers it easy to find in the archives and clear who and when was invited,)
Thanks,
Justin