Hi, I would also like to attend. I'm also of the opinion that Hack'n'Ack should be a separated event from this taskforce meeting. However, maybe 1,5 days could be enough for the workshop, and this would mean that 27th +28th until Hack'n'Ack starts could still fit? Cheers, Emmanuel
On Mon, Jan 19, 2015 at 8:35 AM, Peter Kietzmann < peter.kietzm...@haw-hamburg.de> wrote: > Hi, > > I would like to attend. I also prefer separate days for Hack'n'ACK and > this date. > > Best, > Peter > > > Am 16.01.2015 um 19:08 schrieb Hauke Petersen: > > Dear RIOTers, >> >> we recently came up with the idea to create task forces around special >> topics in RIOT to concentrate and speed up the development of key parts. >> The idea is to bring all people that are interested in this topic and are >> prepared to spend some on it together in a (virtual) room and start out by >> a 2-3 day workshop style event. This first period should be used to discuss >> the topic in detail to bring everyone involved on the same page, to come up >> with a clear architecture, and define interfaces and sub-modules. The hope >> is, that we can go into a very productive implementing phase afterward and >> speed up the overall development. >> >> The first key topic we want to try out this concept is the ongoing >> re-structuring of the network stack. I propose the following plan for this: >> - we use next week to coordinate (who wants to join, what is the current >> state, what are the most pressing open questions) >> - we block 2 days in the last week of January for a (virtual) white-board >> centered workshop >> >> For the workshop I propose January 27-28, but its just a proposal... >> >> >> Regarding technical aspects that are currently under (heavy) construction >> or need to be clarified (@Martine: please hit me if I have it completely >> wrong here...): >> - optimizations to the netdev interface >> - optimizations to the netapi interface >> - analysis of possible data loss using netapi in its current state >> - how to pass data/headers/packets around the stack >> - possible generalization and/or quotas in the packet buffer >> - concepts of global protocol/module list and global protocol handler >> registry >> - API definition for the neighbor table >> - API definition for the forwarding table >> - possible join for neighbor and forwarding table >> - hooks for various routing protocols >> - ??? >> >> This is just a initial list of topics to be further discussed - I hope we >> can detail it out over the next week to have a good idea about the >> questions that need time for discussion! >> >> >> So concluding: >> - who is interested (and/or) wiling to joing this effort? >> - are there any ideas on the concrete organization of such a task-force? >> - are there technical aspects I forgot? >> >> Looking forward to your feedback! >> >> Cheers, >> Hauke >> >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> http://lists.riot-os.org/mailman/listinfo/devel >> > > -- > Peter Kietzmann > > Hamburg University of Applied Sciences > Dept. Informatik, Internet Technologies Group > Berliner Tor 7, 20099 Hamburg, Germany > Fon: +49-40-42875-8426 > Web: http://www.haw-hamburg.de/inet > > > _______________________________________________ > devel mailing list > devel@riot-os.org > http://lists.riot-os.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
