2020 team sprint

[intrigeri <intrigeri@boum.org>]

Hi,

at DebConf19, overwhelmed by "use strictures 2;" love sparkling from
the amazing team dynamics we had there, and blissfully ignoring the
other constraints my life is operating under, I foolishly committed to
bootstrap the scheduling process for our next in-person team sprint.
Oh well :)

First useful steps could be to:

1. Gather rough availability data

   Emphasis on "rough": at this point, it's probably too early to say
   things like "I can't make it on March 23". But if there are broad
   instances of DateTime::Duration that work better or worse for you,
   it could be useful to share this info.

2. Piggy-back on another event or not?

   IIRC there were pros & cons expressed on this topic in the past but
   in the end, we chose "yes" the last couple times. I lack
   time+energy to go through these past discussions and sum them
   up now.

   Expected outcome: "yes, at all costs", "yes, if possible", "no, if
   possible", "no, at all costs".

3. If we would like to piggy-back on another event: research and
   brainstorm which ones could be good candidates.

4. Discuss all the things you'd like to, that the above framework is
   to limiting for.

Cheers,
-- 
intrigeri