Concrete Milestones for next release

• 6LoWPAN Completion (including ND)
• RPL Restructuring + new MOPs
• AODVv2
• OLSRv2
• Finish Network Stack restructuring
• TCP
• HTTP
• CBOR
• JSON
• Boarder Gateway Router

• integrate 3rd party into RIOT
• Full support (GPIO/EXTI/UART/timer/SPI/power management/[I2C]/[PWM]/[ADC] for
  • STM-F0/3/4
  • Arduino-due
  • Teensy 3.1
  • XMC2go
  • nRF51822
  • IoT-Lab
  • MSB-IoT
• Drivers for
  • nRF24l01
  • XBee

• Core API improvements?
  • ==> Allow merging PRs that do DEVELHELP checks
  • (wasn't this ==> check if standard C assertions work)?
    •  yeah, and above if not
  • compare core/lifo.c :43
• IPC refactoring
  • IPC with msgs larger than type+value
  • Inter-Node IPC
  • Decouple IPC endpoints from threads (multiple msg endpoints per thread)
  • (posix) IO API using IPC
  • epoll / IO events
• build system support for LGPLv2 compliance testing
  • s/LGPLv2 compliance testing/license indication/ (we've got BSD etc. some of which have additional requirements)
  • (I'd like to see build system support for companies that use RIOT combined with propretary code. They need to provide a way (forced by LGPLv2) to prove that RIOT was linked unchanged. We need to provide an easy way to compile RIOT, compile vendor code, spit out the vendor code as .a, then make it easy to just take the right RIOT tarball, copy in the vendor .a, recompile RIOT, link everything so that the MD5s matches. IMHO that's absolutely needed for any non-OSS RIOT adoption.)
• clarify "LGPLv2 or newer" in Copyriot boiler plate
  • need to unify to version 2.1
• Reduce number of old issues/PRs
  
  
  
  
  
  

Where Do We Go From Here?

• C++ support?
  • pull request needs review
    • https://github.com/RIOT-OS/RIOT/pull/981
    • reassigned to martin
  • compatibility chart
• POSIX?
  • compatibility chart
• Network stack? (missing pieces to connect/interoperate with "outside" e.g. CBOR, HTTP, TCP, Bluetooth)
• Wiselib support?
• Reference Hardware?
• "IoT stack"
  • "automatic" default networking
  • service discovery
  • model for describing services/APIs
  • API's for accessing RIOT nodes/networks using other systems
  • implement sample "full-stack" demos (e.g., connect supported device to WLAN / laptop, it will autoconnect to the RIOT network, then use 10 line python code to print all connected node names including "services")
• discuss: simplify riot tcb, use optional "process manager" for things like thread names, "daemon threads"
• setup codespeed (https://github.com/tobami/codespeed/ ) for bloat / performance measurements
  
  

• Martine presents framework for Jenkins use
  • Jenkins: https://ci.riot-os.org/jenkins/
  • RIOT job manager: https://github.com/RIOT-OS/riot_job_manager
    
    

• statement from Johann Fischer
• PR of the month 04 + 05 -> PR of the release?