Hi, looks like it's gonna be February 5th and 6th (a Thursday and a Friday). Martin is the only one that is not available on Thursday. Is everyone okay with that?
Cheers, Martine 2015-01-19 17:30 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>: > Hi everyone, > > sandwiching the H&A is indeed not a good idea, I agree. > > Thanks Martine for the doodle, let's wait until Thursday and decide on the > dates based on the outcome of the doodle then. > > Cheers, > Hauke > > > > On 19.01.2015 13:17, Martine Lenders wrote: > > Hi, > Since this thread has gained some traction now I would propose to use to > dudle it out. The two days adjacent to each other where most are available > would be the date: https://dudle.inf.tu-dresden.de/RIOT-NSFT1/ > > Cheers, > Martine > Am 19.01.2015 12:29 schrieb "Emmanuel Baccelli" < > emmanuel.bacce...@inria.fr>: > >> Hi Thomas, >> damn, your right, I misread the dates. So Hack'nAck would be "sandwiched" >> inside the workshop, and I guess that's not great. How about 28-29, or >> 29-30, then? >> Best >> Emmanuel >> >> On Mon, Jan 19, 2015 at 11:24 AM, Thomas Eichinger < >> thomas.eichin...@fu-berlin.de> wrote: >> >>> Hi, >>> >>> I’d also like to attend. I’d prefer a date without H&A in-between (as >>> these tend to >>> end late at night, which would make it hard to start with NSTF early >>> again) but >>> wouldn’t object if there is a majority in favour of this. >>> >>> Best, Thomas >>> >>> > On 16 Jan 2015, at 19:08, Hauke Petersen <hauke.peter...@fu-berlin.de> >>> wrote: >>> > >>> > 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 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > devel mailing > listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > 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
