Re: [Debconf-team] Content team: Our current status, next steps

2017-07-21 Thread Molly de Blanc
Exactly! I don't know who would want their BoF recorded (though I know some people do). On 07/20/2017 11:40 AM, Tiago Bortoletto Vaz wrote: > Hi Molly, self-scheduled activities can be anything from talks, BoFs to > arts performance :) > > On 07/20/2017 11:15 AM, Molly de Blanc wrote: >> Are self-

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-20 Thread Tiago Bortoletto Vaz
Hi Molly, self-scheduled activities can be anything from talks, BoFs to arts performance :) On 07/20/2017 11:15 AM, Molly de Blanc wrote: > Are self-scheduled sessions exclusively talks, or is this also time for > more BoFs, planning meetings, action sessions, etc? > > -m. > > On 07/20/2017 10:1

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-20 Thread Louis-Philippe Véronneau
I agree with h0lger here. We have been very clear from the start the videoteam has limited resources and time and dealing with the requests from self-scheduled talks always add more load. I won't be playing with the cameras this year for obvious reasons, but I highly encourage the videoteam to put

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-20 Thread Molly de Blanc
Are self-scheduled sessions exclusively talks, or is this also time for more BoFs, planning meetings, action sessions, etc? -m. On 07/20/2017 10:16 AM, Holger Levsen wrote: > On Tue, Jul 18, 2017 at 12:28:59PM +0200, Wouter Verhelst wrote: >> On Tue, Jul 18, 2017 at 09:50:21AM +0200, Michael Banc

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-20 Thread Holger Levsen
On Tue, Jul 18, 2017 at 12:28:59PM +0200, Wouter Verhelst wrote: > On Tue, Jul 18, 2017 at 09:50:21AM +0200, Michael Banck wrote: > > 7. There will be no video-team support for any self-scheduled sessions. > I would make that "no guaranteed video-team support". If it is in a room > with video equip

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-18 Thread Wouter Verhelst
On Tue, Jul 18, 2017 at 09:50:21AM +0200, Michael Banck wrote: > 7. There will be no video-team support for any self-scheduled sessions. I would make that "no guaranteed video-team support". If it is in a room with video equipment, we may be able to come up with volunteers, but that's difficult to

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-18 Thread Michael Banck
Hi, On Sat, Jul 15, 2017 at 07:48:44AM +, Holger Levsen wrote: > I really don't get this. We have a talks team, which decides about > talks and workshops and all that. And then we have self-scheduling > where talks and workshops which werent accepted by the content team > get self scheduled?!?

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-15 Thread shirish शिरीष
Reply in-line :- On 15/07/2017, Holger Levsen wrote: > > I really don't get this. We have a talks team, which decides about > talks and workshops and all that. And then we have self-scheduling where > talks and workshops which werent accepted by the content team get > self scheduled?!? > > Wil

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-15 Thread Andreas Tille
On Sat, Jul 15, 2017 at 07:48:44AM +, Holger Levsen wrote: > On Fri, Jul 14, 2017 at 01:03:15PM -0500, Gunnar Wolf wrote: > > As most of you are aware by now - We finally have a (preliminary) > > schedule! \o/ > > yay! thanks to everyone involved…! +1 > > First, as I expected, several peop

Re: [Debconf-team] Content team: Our current status, next steps

2017-07-15 Thread Holger Levsen
On Fri, Jul 14, 2017 at 01:03:15PM -0500, Gunnar Wolf wrote: > As most of you are aware by now - We finally have a (preliminary) > schedule! \o/ yay! thanks to everyone involved…! > First, as I expected, several people have contacted me privately > complaining on why the schedule starts at 9AM.

[Debconf-team] Content team: Our current status, next steps

2017-07-14 Thread Gunnar Wolf
Hi, As most of you are aware by now - We finally have a (preliminary) schedule! \o/ It's not yet officially published, but I sent it by mail on an ODS to the content team, and Pollo loaded it (modulo some errors I will try to locate and fix somewhen soon) into Wafer. Now, I'm going away for some