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

[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-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 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 guarantee on short notice.
>>> exactly this happens each year again. we say there will be no video at
>>> self scheduled sessions, then there is equipment and thus the expectation
>>> that there will be video… 
>>>
>>>
>>>
>>>
>>> ___
>>> Debconf-team mailing list
>>> Debconf-team@lists.debconf.org
>>> http://lists.debconf.org/mailman/listinfo/debconf-team
>>>
>>
>>
>> ___
>> Debconf-team mailing list
>> Debconf-team@lists.debconf.org
>> http://lists.debconf.org/mailman/listinfo/debconf-team
>>
>
>
> ___
> Debconf-team mailing list
> Debconf-team@lists.debconf.org
> http://lists.debconf.org/mailman/listinfo/debconf-team



signature.asc
Description: OpenPGP digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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: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 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 guarantee on short notice.
>>
>> exactly this happens each year again. we say there will be no video at
>> self scheduled sessions, then there is equipment and thus the expectation
>> that there will be video… 
>>
>>
>>
>>
>> ___
>> Debconf-team mailing list
>> Debconf-team@lists.debconf.org
>> http://lists.debconf.org/mailman/listinfo/debconf-team
>>
> 
> 
> 
> ___
> Debconf-team mailing list
> Debconf-team@lists.debconf.org
> http://lists.debconf.org/mailman/listinfo/debconf-team
> 



signature.asc
Description: OpenPGP digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 its foot down and refuse.

-- 
pollo

On 2017-07-20 10:16, 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 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 guarantee on short notice.
> 
> exactly this happens each year again. we say there will be no video at
> self scheduled sessions, then there is equipment and thus the expectation
> that there will be video… 
> 
> 
> 
> 
> ___
> Debconf-team mailing list
> Debconf-team@lists.debconf.org
> http://lists.debconf.org/mailman/listinfo/debconf-team
> 



signature.asc
Description: OpenPGP digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 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 guarantee on short notice.
> 
> exactly this happens each year again. we say there will be no video at
> self scheduled sessions, then there is equipment and thus the expectation
> that there will be video… 
> 
> 
> 
> 
> ___
> Debconf-team mailing list
> Debconf-team@lists.debconf.org
> http://lists.debconf.org/mailman/listinfo/debconf-team
> 



signature.asc
Description: OpenPGP digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 equipment, we may be able to come up with volunteers, but
> that's difficult to guarantee on short notice.

exactly this happens each year again. we say there will be no video at
self scheduled sessions, then there is equipment and thus the expectation
that there will be video… 


-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 guarantee on short notice.

-- 
Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008
 Hacklab
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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?!?
> 
> Will those self scheduled event end up in the same rooms as the
> others, filing the time tables even more, putting more load on
> attendees and video volunteers alike?
> 
> Whats the point of this, why doesnt the content team decide on those
> talks / slots too?
> 
> I'd understand if those self-scheduled events were in a dedicated
> different room (which might or might not be videoed) but I dont get
> why it's useful to have content team scheduling and self scheduling
> for the same ressource (=room).

I volunteered to put the self-scheduled talks into wafer each night in
yesterday's meeting (as I did for the last three DebConfs).

In general ad-hoc sessions are an important part of DebConf, as a lot of
stuff tends to pop-up during conversations between attendees or in the
Q of a regular talk and it is useful to have follow-up BoFs on them.

I'm sure you're aware there's more interesting things to do between
9PM-2AM at Debconf than scheduling stuff in wafer, printing out the
schedule and putting it up everywhere.  Now if we also need to have
content team meetings each night to decide on the proposed ad-hoc
sessions and their particular merits, I think that is straining our
resources (not least cause not every content team member will be
on-site).

The current plan is as follows:

1. Attendee enters their ad-hoc/self-scheduled session into wafer.

2. Attendee writes the talk title and wafer id in their preferred
timeslot for the next day (or maybe the day after next, TBD) on a
whiteboard/chalkoard/whateverboard at FD.

3. Each night, I accept the self-scheduled sessions in wafer, and
schedule them according to above FD board.

4. On a best-effort basis, I will print out next day's schedule and hang
it up next to the talk rooms / strategic locations.

5. At the morning session, the full schedule for that day will be put up
and the self-scheduled talks highlighted.

6. There will be no self-scheduling in the main auditorium, on the two
smalller ones and the two BoF rooms.

7. There will be no video-team support for any self-scheduled sessions.

I might have gotten something wrong in the above, so please correct me.
But I think that's roughly the plan.


Michael
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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?!?
>
> Will those self scheduled event end up in the same rooms as the others,
> filing the time tables even more, putting more load on attendees and
> video volunteers alike?

Dear all,

While sadly I'll not be attending the conference, from what little
exposure of conferences I have had in India, having self-scheduled
talks are cool. Many a times people do get inspired to give/share
something after hearing a talk or two. I have experienced and have
seen people overcoming their shyness and sharing whatever they know.
Sometimes, it may be boring, at times controversial and sometimes
downright useful.

In either of the scenarios, I believe and think it adds a bit of
character to the conference rather than taking it away.

FWIW, I highly enjoyed the lightning talks given on-topic and
off-topic in Debconf 16 and if memory serves right, most of them were
scheduled last-minute.

I hope this one tradition is encouraged rather than being discouraged.



>
> --
> cheers,
>   Holger
>


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 people have contacted me privately
> > complaining on why the schedule starts at 9AM. I agree, and you will
> > remember I have argued for it to start at 10AM. Please, before
> > publishing the schedule, consider _shifting_ everything by 1hr 
> 
> yes!

-1
No.  From my point of view 9:00 is fine. :-P

> > Also, several people whose talks were not accepted have asked how
> > ad-hoc or self-scheduled (pick a name!) sessions will happen. This has
> > to be discussed and decided *now*, or we will be drowned in requests.
> > 
> > Please do talk about this and decide. Ideally, the schedule and the
> > rules (and space availability, and all that) for self-scheduling
> > should be announced at the same time.
> 
> 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?!?
> 
> Will those self scheduled event end up in the same rooms as the others,
> filing the time tables even more, putting more load on attendees and
> video volunteers alike?

As far as I understood Gunnar, self-scheduled talks will not have video
coverage.

> Whats the point of this, why doesnt the content team decide on those
> talks / slots too?
> 
> I'd understand if those self-scheduled events were in a dedicated different
> room (which might or might not be videoed) but I dont get why it's useful
> to have content team scheduling and self scheduling for the same ressource 
> (=room).
 
At DebConfs where I was more active in scheduling all was scheduled by
content team and the rule was that anything that is scheduled less than
24h in advance will not get video coverage.  I have no idea why this is
changed now and how it is done technically for random attendees to
self-schedule anything.  But as far as I can see the effect would be
that the video team has less work since less talks are maintained by
content team.
 
My totally wild guess is that features of the new conference management
system permit other things than we did before and so those new rules
apply.

See you

  Andreas.

-- 
http://fam-tille.de
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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. I agree, and you will
> remember I have argued for it to start at 10AM. Please, before
> publishing the schedule, consider _shifting_ everything by 1hr 

yes!

> Also, several people whose talks were not accepted have asked how
> ad-hoc or self-scheduled (pick a name!) sessions will happen. This has
> to be discussed and decided *now*, or we will be drowned in requests.
> 
> Please do talk about this and decide. Ideally, the schedule and the
> rules (and space availability, and all that) for self-scheduling
> should be announced at the same time.

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?!?

Will those self scheduled event end up in the same rooms as the others,
filing the time tables even more, putting more load on attendees and
video volunteers alike?

Whats the point of this, why doesnt the content team decide on those
talks / slots too?

I'd understand if those self-scheduled events were in a dedicated different
room (which might or might not be videoed) but I dont get why it's useful
to have content team scheduling and self scheduling for the same ressource 
(=room).


-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team

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

[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 days again. There is ample work to do,
and I need the rest of you to help with it. 

First, as I expected, several people have contacted me privately
complaining on why the schedule starts at 9AM. I agree, and you will
remember I have argued for it to start at 10AM. Please, before
publishing the schedule, consider _shifting_ everything by 1hr - That
means, start at 10, lunch 13-15, coffee at 17:00, supper 19:30. Please
do *not* change the blocks' logic (it's 3-2-2, not 2-3-2 or some
such), as it would immensely displease me :)

Also, several people whose talks were not accepted have asked how
ad-hoc or self-scheduled (pick a name!) sessions will happen. This has
to be discussed and decided *now*, or we will be drowned in requests.

Please do talk about this and decide. Ideally, the schedule and the
rules (and space availability, and all that) for self-scheduling
should be announced at the same time.

Thanks a lot. Now, I will try to disappear again into vacation mode.


signature.asc
Description: Digital signature
___
Debconf-team mailing list
Debconf-team@lists.debconf.org
http://lists.debconf.org/mailman/listinfo/debconf-team