incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "MynewtProposal" by Sterling Hughes
Date Thu, 01 Oct 2015 14:59:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "MynewtProposal" page has been changed by Sterling Hughes:
https://wiki.apache.org/incubator/MynewtProposal?action=diff&rev1=13&rev2=14

  
  With the momentum behind the Internet of Things, there is an increasing need for standard
open source software to help developers create connected devices.  One area where there is
a large need is an open-source, liberally licensed, community-driven RTOS (real-time operating
system.)
  
- Today, there are many RTOSes, the majority of which are provided by proprietary vendors
(e.g. Intel, ARM, TI, Blackberry), and many of which are not permissively licensed (e.g. FreeRTOS)
or controlled by a single company.  These restrictions create fragmentation, because either
not everyone can afford to purchase the operating system, or restrictions put on the OS's
use (e.g. only work on ARM or Intel platforms), means that people using other processors cannot
adopt it.  
+ Today, there are many RTOSes, the majority of which are provided by proprietary vendors
and many of which are not permissively licensed or controlled by a single company.  These
restrictions create fragmentation, because either not everyone can afford to purchase the
operating system or restrictions put on the OS's use (e.g. restricted to vendor-specific platforms),
means that people using other processors cannot adopt it.  
  
  The lack of a standardized operating system creates fragmentation around everything above
it.  Because there is not a well adopted community driven operating system, people don't have
a place to contribute back new drivers, or networking stacks.  Additionally, there is constant
work to port and maintain software across a myriad of different operating systems, all with
slightly different APIs and interfaces.
  
- In order for the industry to accelerate, and keep up with the increasing complexity in these
devices, it's important that an open-source community form and provide a RTOS effort that:

+ In order for the industry to accelerate and keep up with the increasing complexity in these
devices, it's important that an open-source community form and provide a RTOS effort that:

  
-  * Accepts community contributions, and encourages code reuse 
+  * Accepts community contributions and encourages code reuse 
   * Natively supports source package management, to allow for efficient redistribution and
reuse of software across a broad swath of use cases (from wearables to industrial equipment)
 
-  * Supports all of the "new" protocol stacks required for IoT (Bluetooth, IPv6, etc.) 
+  * Supports all of the "new" protocol stacks required for IoT (e.g. Bluetooth, IPv6, etc.)

-  * Has drivers for all new chipsets, sensors and other devices 
+  * Has drivers for all new chipsets, sensors, and other devices 
  
- The core of Mynewt has been designed to accommodate these requirements.  It contains a small
pre-emptive RTOS core, that works on native (OS X, Linux) and Cortex platforms (and is easily
portable to others), and standardized HAL and BSP interfaces.
+ The core of Mynewt has been designed to accommodate these requirements.  It contains a small,
pre-emptive RTOS core, that works on native (OS X, Linux) and Cortex platforms (and is easily
portable to others), and standardized HAL and BSP interfaces.
  
- It also provides a build and package management tool that allows developers to install,
develop, redistribute source packages.  This tool allows developers to start with the core
of the OS, and it's interfaces, and then download only the source packages they need to run
their embedded project.  This will allow the community to grow beyond just porting the core
of the Mynewt system and extend to all of the necessary protocol stacks, drivers and sensor
interfaces that a modern embedded developer will need. 
+ It also provides a build and package management tool that allows developers to install,
develop, and redistribute source packages.  This tool allows developers to start with the
core of the OS and its interfaces, and then download only the source packages that are needed
to run their embedded project.  This will allow the community to grow beyond just porting
the core of the Mynewt system and extend to all of the necessary protocol stacks, drivers
and sensor interfaces that a modern embedded developer will need. 
  
  In addition to the Mynewt core, there is active development around a set of commonly needed
functionality when developing small embedded systems, including: 
  
   * A Flash Filesystem designed for small flashes, with large block sizes (very common in
single chip designs)
-  * An Open Bluetooth stack, with native support for Nordic processors
+  * An Open Bluetooth stack with native support for prevalent modules
  
  == Initial Goals ==
  
@@ -79, +79 @@

   * Log structured flash filesystem
   * Flash circular buffer stores 
   * Drivers for Sensors and Actuators 
-   * Services to control motors, pumps and read accelerometers, heart rate sensors, etc.

+   * Services to control motors, pumps, read accelerometers, heart rate sensors, etc. 
   * Core services for location and time 
  
  == Current Status ==
@@ -114, +114 @@

  
   * The GPL (and LGPL) are profoundly impactful for physical products, as most constrained
devices are linked into a single executable, meaning any proprietary device that includes
GPL'd source code must release their software. 
    * This often contains information about proprietary hardware designs as well as software
designs. 
-  * Most projects are either not community driven and lack a clean IP trail.
+  * Most projects are either not wholly community driven and/or lack a clean IP trail.
  
  == Known Risks ==
  
@@ -135, +135 @@

  We like the Apache brand (it's a good brand!)  However, we want to enter the ASF because:

  
   * In order for an OS to be ultimately successful, it needs to be community driven 
-  * We believe strongly in a community which is a meritocracy, and think that the ASF has
a successful framework for managing such communities. 
+  * We believe strongly in a community which is a meritocracy and think that the ASF has
a proven, successful framework for managing such communities. 
   * The ASF has a strong track record in developing healthy communities that co-exist with
commercial entities. 
   
  == Documentation ==
  
  Documentation is available here: https://github.com/mynewt/docs
  
- We are actively working on documentation, and expect it to improve dramatically within the
next couple of weeks. 
+ We are actively working on documentation and expect it to improve dramatically within the
next couple of weeks. 
  
  == Initial Source ==
  All source code is currently hosted by Runtime, Inc. on Github.  
@@ -151, +151 @@

  
  https://github.com/mynewt/
  
- The tadpole repository contains the Core of the Operating System and file layout.  The larva
repository contains the Core OS and all packages developed around that core.  The newt repository
has the build and package management tool that is used to stitch together and build new OS
projects.
+ The "tadpole" repository contains the Core of the Operating System and file layout.  The
"larva" repository contains the Core OS and all packages developed around that core.  The
"newt" repository has the build and package management tool that is used to stitch together
and build new OS projects.
  
  == External Dependencies ==
  
- No external dependencies currently exist in the core OS, all code has been written by Runtime.
+ No external dependencies currently exist in the core OS; all code has been written by Runtime.
  
- The board and microcontroller specific support packages contain code from the various MCU
vendors.  This code has been ensured to be under either an Apache or BSD license. 
+ The board and microcontroller-specific support packages contain code from the various MCU
vendors.  This code has been ensured to be under either an Apache or BSD license. 
  
  == Cryptography ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message