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/01/06 11:02:48 UTC
Draft of January report for Mynewt
Hi all,
Sorry for the last minute review request. Thanks for your guidance and happy new year!
Please note that I plan to get a more accurate commits count tomorrow morning (instead of 150+).
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.
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 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.
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:
Re: Draft of January report for Mynewt
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Thanks for posting the report. Nice job.
I’ve signed off.
-Taylor
> On Jan 6, 2016, at 1:07 PM, aditi hilbert <ad...@runtime.io> wrote:
>
> The January report for Apache Mynewt is up.
> Mentors, please sign off.
>
> https://wiki.apache.org/incubator/January2016 <https://wiki.apache.org/incubator/January2016>
>
> thanks,
> aditi
>
>
>> On Jan 6, 2016, at 8:27 AM, aditi hilbert <ad...@runtime.io> wrote:
>>
>> Justin,
>>
>> Sure, I’ll move that. Understand that may not be a requirement in general for graduation but we do hope for a roadmap for Mynewt OS.
>>
>> aditi
>>
>>> On Jan 6, 2016, at 5:06 AM, Justin Mclean <ju...@classsoftware.com> wrote:
>>>
>>> Hi,
>>>
>>>> count tomorrow morning (instead of 150+).
>>>
>>> Rough counts are fine - the exact stats don’t matter.
>>>
>>>> 3. Develop a roadmap and release schedule for the Mynewt Operating System
>>>
>>> Not a big deal but I’d remove this one. Apache projects are volunteer based, and while some projects do have roadmaps, they don’t always end up being accurate or achievable. You release as often as is needed there no real need for a release schedule or a road map.
>>>
>>> IMO I’d replace that point with resolving the (ongoing) discussion about committership.
>>>
>>> Thanks,
>>> Justin
>>
>
Re: Draft of January report for Mynewt
Posted by aditi hilbert <ad...@runtime.io>.
The January report for Apache Mynewt is up.
Mentors, please sign off.
https://wiki.apache.org/incubator/January2016 <https://wiki.apache.org/incubator/January2016>
thanks,
aditi
> On Jan 6, 2016, at 8:27 AM, aditi hilbert <ad...@runtime.io> wrote:
>
> Justin,
>
> Sure, I’ll move that. Understand that may not be a requirement in general for graduation but we do hope for a roadmap for Mynewt OS.
>
> aditi
>
>> On Jan 6, 2016, at 5:06 AM, Justin Mclean <ju...@classsoftware.com> wrote:
>>
>> Hi,
>>
>>> count tomorrow morning (instead of 150+).
>>
>> Rough counts are fine - the exact stats don’t matter.
>>
>>> 3. Develop a roadmap and release schedule for the Mynewt Operating System
>>
>> Not a big deal but I’d remove this one. Apache projects are volunteer based, and while some projects do have roadmaps, they don’t always end up being accurate or achievable. You release as often as is needed there no real need for a release schedule or a road map.
>>
>> IMO I’d replace that point with resolving the (ongoing) discussion about committership.
>>
>> Thanks,
>> Justin
>
Re: Draft of January report for Mynewt
Posted by aditi hilbert <ad...@runtime.io>.
Justin,
Sure, I’ll move that. Understand that may not be a requirement in general for graduation but we do hope for a roadmap for Mynewt OS.
aditi
> On Jan 6, 2016, at 5:06 AM, Justin Mclean <ju...@classsoftware.com> wrote:
>
> Hi,
>
>> count tomorrow morning (instead of 150+).
>
> Rough counts are fine - the exact stats don’t matter.
>
>> 3. Develop a roadmap and release schedule for the Mynewt Operating System
>
> Not a big deal but I’d remove this one. Apache projects are volunteer based, and while some projects do have roadmaps, they don’t always end up being accurate or achievable. You release as often as is needed there no real need for a release schedule or a road map.
>
> IMO I’d replace that point with resolving the (ongoing) discussion about committership.
>
> Thanks,
> Justin
Re: Draft of January report for Mynewt
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> count tomorrow morning (instead of 150+).
Rough counts are fine - the exact stats don’t matter.
> 3. Develop a roadmap and release schedule for the Mynewt Operating System
Not a big deal but I’d remove this one. Apache projects are volunteer based, and while some projects do have roadmaps, they don’t always end up being accurate or achievable. You release as often as is needed there no real need for a release schedule or a road map.
IMO I’d replace that point with resolving the (ongoing) discussion about committership.
Thanks,
Justin