Yes to both. 2015-11-19 17:54 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>:
> > > On 19.11.2015 16:50, Emmanuel Baccelli wrote: > > OK, I could go ahead and modify the wiki with some tentative text for > that, which we could refine later on. > In practice: > > - would Kaspar agree he was the shepherd of the timers task force? > > - would Martine & Hauke agree they were the shepherds of the nasty task > force? > > yes > > > - would Martine & Hauke agree they are the shepherds of the documentation > task force? > > and yes > > Cheers, > Hauke > > > > - who would take on the shepherding for the OTA task force? If no-one > speaks up, we could classify this TF as dormant the time being. > > > > On Thu, Nov 19, 2015 at 4:04 PM, Oleg Hahm <oliver.h...@inria.fr> wrote: > >> Hi! >> >> Sounds like a sensible proposal to me. >> >> Cheers, >> Oleg >> >> Am Thu, Nov 19, 2015 at 03:51:36PM +0100 schrieb Emmanuel Baccelli: >> > +1 here too. >> > I think it is also important to describe to malloc and free :) >> > I mean how to: >> > >> > 1 - create a new task force (hopefully we have a lot more to come!) >> > 2 - join/ping/revive an existing task force (e.g. OTA is somewhat >> dormant) >> > 3 - dissolve an existing task force >> > >> > For creating: how about, simply stating something like: >> > "If you wish to launch a new task force, go ahead, create your wikipage, >> > and report your progress or summarize the latest stand of your >> discussions >> > on devel@riot-os.org" >> > There's the slight possibility that duplicate work may happen down the >> > line, if a lot of task forces are active at the same time. >> > But this is not dangerous right now. If we want to cover this case, >> maybe >> > we can add: "RIOT maintainers will contact you if duplicate or very >> > closely-related work has been detected elsewhere, and if joining forces >> > might make sense." >> > >> > For ping/join/revive how about naming one or two shepherds per task >> force, >> > that could be pinged? >> > >> > For dissolving: how about "either (i) the shepherd(s) declares the TF is >> > done, or gives up, or (ii) the shepherds are unreachable, the TF has >> been >> > dormant for a long time and RIOT maintainers declare the TF dissolved" >> > >> > >> > >> > >> > On Thu, Nov 19, 2015 at 3:34 PM, Kaspar Schleiser <kas...@schleiser.de> >> > wrote: >> > >> > > Hey, >> > > On 11/19/15 14:48, Oleg Hahm wrote: >> > > > As an effort to "formalize" this idea of task forces a little bit >> more, >> > > I just >> > > > created a small page in the Wiki: >> > > > >> > > > What do you think? >> > > >> > > +1 >> > > >> > > I've updated the xtimer page. >> > > >> > > Kaspar >> > > _______________________________________________ >> > > devel mailing list >> > > devel@riot-os.org >> > > https://lists.riot-os.org/mailman/listinfo/devel >> > > >> >> > _______________________________________________ >> > devel mailing list >> > devel@riot-os.org >> > https://lists.riot-os.org/mailman/listinfo/devel >> >> >> -- >> /* Thanks to Rob `CmdrTaco' Malda for not influencing this code in any >> * way. >> */ >> linux-2.4.3/net/core/netfilter.c >> >> _______________________________________________ >> devel mailing list >> devel@riot-os.org >> https://lists.riot-os.org/mailman/listinfo/devel >> >> > > > _______________________________________________ > devel mailing > listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel > > > > _______________________________________________ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel > >
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
