Org mailing list

[Grégoire <gregoire AT fripost.org>]

Hi,

Thanks for that report. I was actually going to ask about some of those
things. I have a few questions though.

On Wed, 2013-10-16 at 03:11 +0200, Stian Rødven Eide wrote:
> * We will film all talks, but probably not the Serengeti workshops as
> there might be children participating.
Do you have a plan the post-processing of the footages? I can participate but 
it's too much work to do it all myself.

Here is a quick draft of a plan I have been thinking about and something
I can commit to:
  1. taking care of encoding the videos. This is mostly automatic and is
a pain to set-up so we might as well centralize it.
  2. dumping it all in a ftp server, like fosdem[1] does
  3. curating a few talks (I'm thinking the keynotes and some selected
talks) that we upload to youtube&ci for promotion
  4. Each track manager is then responsible for curating videos for
his/her own track if he/she wants to

Note that 2. requires a ftp server with enough space and good bandwidth.
One possibility would be that fscons buy a NAS so that at least the
storage is independent from any external organisation and it could
double as backup storage for our webserver/wiki/...

> * We will commence poster printing now and let you know as soon as they
> are ready.
Great!

> * We decided to get printed t-shirts this year.
With which design? In 2011 we made a "year-less" t-shirt design in the idea 
that it could last many years, and there is still some (not a lot) t-shirts 
from the last batch:
https://wiki.fscons.org/Inventory

> * We decided to change the official FSCONS-colors to the ones used in
> this year's poster and banners.
This means that a lot of things will need to be updated (booklet layout,
web layout, t-shirt...), is that really the smart move at less than a
month of the conference?

Additional question:

What is the rational for putting track names in the 'room name' field in
the schedule?

Is there anyone assigned to the booklet layout? Otherwise I'm
volunteering for it. I'd like to avoid last year last minute panic and I
have some improvement in mind that I couldn't make last year due to time
constraints.

/ǵ

Attachment: signature.asc
Description: This is a digitally signed message part