Team:Productiehuis
Productiehuis | |
---|---|
1st line contacts: | geekabit |
Does: | Stage:
Radio:
Streaming:
|
Does not: | Stage:
Radio:
|
Is an exclusive team: | Yes |
Contact: | orga-av@lists.sha2017.org |
IRC: | #sha2017-productiehuis |
Deadlines: |
2017/02/01 - point of no return (order list finalized) |
Needed resources: | |
Comment: | Made up of voc, a/v, stage, and other teams |
Vacancies: | 0 |
Current team size / amount of ppl: | 0 |
Contact at projectleiding: | |
Backup Contact at projectleiding: | {{{Backup_Projectleiding}}} "{{{Backup_Projectleiding}}}" cannot be used as a page name in this wiki.
|
Managed Vacancies: | You can add for your team on a page by adding: {{TeamVacancies|Productiehuis}} |
Contents
About
Productiehuis is the team that makes speakers on stage heard and seen in the tent and online. The team consist of the following teams from previous events:
- avid
- voc
- broadcast
- stage
Team members
- Andi
Nickname: Andi
Team: Team:Productiehuis
HackerSpace: muCCC
Village: Village:muCCC
Dect: 2632 (AND2) - Bigred
Nickname: Bigred
Team: Team:Productiehuis
HackerSpace: TKKRlab
Dect: 2542 ? - Bix
Nickname: Bix
Team: Team:Productiehuis
HackerSpace: Hack42 (NL)
- Cooper
Nickname: Cooper
Team: Team:Productiehuis
- Cyberfox
Nickname: Cyberfox
Team: Team:Productiehuis
- Dave_o
Nickname: Dave_o
Team: Team:Productiehuis
HackerSpace: RevSpace
Dect: DAVE (3283) ? - derpeter
Nickname: derpeter
Team: Team:Productiehuis
Role: C3VOC
HackerSpace: CCC Berlin
Village: Village:VOC
Dect: 7383 - Evo--
Nickname: Evo--
Team: Team:Productiehuis
- Felixs
Nickname: Felixs
Team: Team:Productiehuis
Role: A/V Technician
HackerSpace: Selfnet
Dect: 7425 - geekabit
Nickname: geekabit
Team: Team:Productiehuis
Village: Village:deFEEST
- Mack
Nickname: Mack
Team: Team:Productiehuis
Role: Sound engineer
- meise
Nickname: meise
Team: Team:Productiehuis
HackerSpace: C4
Dect: 6462 (MIMA) - Raven
Nickname: Raven
Team: Team:Productiehuis
HackerSpace: CCCZH
Dect: 2769 - PsychiC
Nickname: PsychiC
Team: Team:Productiehuis
HackerSpace: ACKspace
Village: Village:ACKspace
- xopr
Nickname: xopr
Team: Team:Productiehuis
HackerSpace: ACKspace
Village: Village:ACKspace
- Vision
Nickname: Vision
Team: Team:Productiehuis
HackerSpace: none
- Zuntrax
Nickname: Zuntrax
Team: Team:Productiehuis
Dect: 8687
Angels
Relations to other teams
Team | Relation |
---|---|
Team:Volunteers and Buildup Mgmt |
|
Team:Volunteers | Teardown, with caution to the sensitive gear. |
Content and Team:Broadcast | To anticipate special requests Productiehuis *MUST* be kept in the loop to facilitate properly. Examples:
|
Team:Infrastructure | Productiehuis will have special power requirements for the lighting, AV, streaming and radio.
Team Productiehuis needs sufficient floorspace to setup monitoring of all camera feeds of each tent, monitor the VOC infrastructure itself and the upstream Content Delivery Network health and to support people with streaming problems. The location needs to be close to the NOC to enable VOC to directly contact NOC people when an outage occurs. |
Team:Logistics | Productiehuis gear will need to be:
Productiehuis needs access to a Gator or another motorised vehicle with sufficient power/traction to quickly drive towards a tent with technical problems of anykind. Team Productionhuis is responsible for a widely scope set of tasks and should have their own dedicated vehicle to avoid loss of production. |
Team:DECO | The stages must look pretty, besides just functional. Style is everything. We also need functional lighting in the tents. Team Productiehuis will need help with:
|
Team:Lounge | Coherent audio/DJ-gear with the lounge makes it possible to use the audio from the Lounge for broadcasting on radio, streaming or just get gear at one AV-supplier. |
Team:NOC | Team Productiehuis will need technical help:
|
Team:Sysadmin | Team Productiehuis will need:
|
Other | Team Productiehuis will need:
|
Todo
There is a wiki page with a todo list.
Stage templates
Productiehuis:Multiple stage templates
Productiehuis:Radio studio template
Actions
Begin date | End date | Action responsible | Status | Action |
---|---|---|---|---|
2016-04-22 | 2016-04-27 | Productiehuis | Decision required | Request for decision on the Deadlines (as displayed on the wiki) |
2016-04-23 | 2016-10-01 | Orga | Open | Event dimensions must be clear. |
2016-04-24 | 2016-10-01 | Productiehuis | Open | Design stage templates to prepare without knowing the event dimensions. |
2016-04-24 | 2016-10-01 | Productiehuis | Open | Match c3voc inventory with templates and create a gap-analyses/diff-list. |
Legend:
- Begin date: when did you put the action item here?
- End date: When do you expect this action item to be finished?
- Background Red: when date is overshot and Status is Open or Decision required
- Background Green: When date is in the future and Status is Open or Decision required
- Background Light Blue: When date is in the past and Status is Closed (thus finished)
- Status:
- Open (style: red background)
- Closed (style: green background)
- Decision required (style: orange background)
- Action: description of the item, short and nice. If large explanation is needed create a dedicated page to keep the action item list easy to browse.
Hints:
- sub-divide actions when there are multiple aspects/angles/things to do/achieve.
- use color coding to easily visually see where we are at. This list will become large.
Meetings
All meetings (so far) are held via mumble No meetings planned. Look at the PastMeetings page, or add a meeting here.