forked from RIOT-OS/RIOT
-
Notifications
You must be signed in to change notification settings - Fork 1
Virtual Meeting on November 19, 2014
OlegHahm edited this page Nov 19, 2014
·
3 revisions
- Hauke Petersen (FU Berlin)
- Oleg Hahm (INRIA)
- Martin Landsmann (HAW Hamburg)
- Peter Kietzmann (HAW Hamburg)
- Phạm Hữu Đăng Nhật (Ho Chi Minh University of Technology)
- Thomas Eichinger (FU Berlin)
- Ludwig Ortmann (FU Berlin)
Joined at the very end:
- Teemu Hakala (ell-i)
- Philipp Rosenkranz (FU Berlin)
- Oleg proposed the agenda
- Agenda was approved as followed:
- Organization/Managing of distributed development procedures
- Release branch
- Dependencies of special make targets (like
make flash
)
- As a reaction to the discussion on the mailing list, initiated by Peter, participants tried to figure out how to improve development procedures for porting efforts.
- Agreement was made that the wiki page on Development Procedures should state that porting for a new board should always require to create a wiki page for this board first.
- This wiki page should then point to an issue in the tracker coordinating porting tasks.
- For maximum visibility, a pointer to this information should be put into the README and on the wiki start page.
- Peter volunteered to add this information and pointers - by a PR and/or mailing list.
- Oleg proposed to create a release branch, where we can already merge some pending PRs (particular the network refactoring ones) for early testing.
- Hauke counter-proposed to have this branch not in the RIOT repository, but in Martine's fork.
- Participants agreed on Hauke's solution - assuming that Martine will agree, too.
- Referring to #1724 and #2012 it was discussed if the
flash
target should depend onall
or not. - Consensus was made that this would be most logical.
- However, it would be nice to specify different file names for one application to make it possible to flash different versions of an application.
- Peter pointed to #2021 and asked for comments.
- Consensus was made that having this meeting every two weeks is good.
- For the upcoming Hack'n'ACK party in Berlin, we'll try to connect with a similar event in Hamburg using PlaceCam over a single video conferencing setup (mic, speakers, cam, screen) per site.
- Minutes of these meetings should go into the wiki (sic!). For the next meeting we'll have to agree on a minute taker before the meeting starts.
RIOT - The friendly Operating System for the Internet of Things
Homepage | [GitHub] (https://github.com/RIOT-OS/) | Developers Mailing List | Users Mailing List | Twitter @RIOT_OS
- Family: ARM
- Board: Airfy Beacon
- Board: Arduino Due
- Board: CC2538DK
- Board: CC2650STK
- Board: HikoB Fox
- Board: IoT LAB M3
- Board: LimiFrog-v1
- Board: mbed_lpc1768
- Board: MSB-IoT
- Board: MSBA2
- Board: Nucleo-L1
- Board: Nucleo-F334
- Board: Nucleo-F303
- Board: Nucleo-F091
- Board: Mulle
- Board: OpenMote
- Board: PCA1000x (nRF51822 Development Kit)
- Board: Phytec phyWAVE-KW22
- Board: RFduino
- Board: SAMR21-xpro
- Board: SAML21-xpro
- Board: Spark Core
- Board: STM32F0discovery
- Board: STM32F3discovery
- Board: STM32F4discovery
- Board: UDOO
- Board: yunjia-nrf51822
- Board: Zolertia remote
- Family: ATmega
- Board: Arduino Mega2560
- Family: MSP430
- Board: MSB-430H
- Board: TelosB
- Board: WSN430
- Board: Zolertia Z1
- Board: eZ430-Chronos
- Family: native
- Board: native
- Family: x86
- Board: Intel Galileo