MCH2022 wiki - User contributions [en]

User:Teirdes

2022-06-21T09:09:01Z

Teirdes:

{{UserInfo
|NickName=Teirdes
|Village=Village:The Quarantine Arms
|Arrival=2022-07-22
|Departure=2022-07-27
|Twitter=teirdes
|Languages=English, Swedish, (Dutch), (Romanian), (French), (Spanish)
|HackerSpace=hsbxl, forsken (if indeed any)
}}
Teirdes is Amelia Andersdotter.

It was her dream to understand

why on Team:Content not all team members were displayed

but it turned out

it had everything to do with the user form

which can be accessed

through the Special pages link on the left if you are logged in

her friends said her dreams were

not so ambitious but not all dreams

need to be large or unattainable

some can also pass

in but a few minutes

in fact most

2020-09-12-Content-meeting

2020-08-29T13:58:03Z

Teirdes:

= [[Team:Content|Team Content]] Meeting =

Online 2020-09-12 17:00 - 18:00

[https://pad.riseup.net/p/MCH2021-Content-Minutes-2020-09-12 Pad during the meeting, result in the minutes]

[[2020-09-12-Content-meeting-minutes|Minutes]]

== Agenda ==

As decided in the [[2020-08-29-Content-meeting-minutes|2020-08-29 meeting]]:

The action points from the last meeting are shown at the topics they belong to below.

== Administrivia ==

* Notes?
* Chair?
* Any other topics?

== Recap on action points ==
=== Walter to talk to C3VOC about remote participation ===
=== Claudia check in with team info/communication on opportunities to publish blogposts ===
=== Claudia draft a special topic blog on important of climate crisis in technical discussions ===
=== Aschwin ask Jeroen to write up an initial draft proposal on review process to be discussed this meeting ===
=== Robin draft proposal on review process ===
=== Coco reach out to the people dealing with FAQ on accessibility and wheelchair ramps for stages ===
== Status of submissions ==
== Reconciliation of envisaged draft review processes ==

== Topics for next meeting ==
== Next meeting time ==

Team:Content

2020-08-29T13:56:14Z

Teirdes: /* Meetings */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|team_is_essential_to_event=Yes
|team_has_contact_info=Yes
|team_has_info_on_wiki=Yes
|team_has_planned_meetings=Yes
|team_has_enough_people=Yes
|team_has_drafted_budget=No
|team_has_informed_volunteer_team=No
|Projectleiding=User:Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:Kirils}}
{{TeamMemberEntry|User:Coco}}
{{TeamMemberEntry|User:Jeroenh}}
== Vacancies ==
Currently no vacancies.

== Current deliverables: ==

* A plan how to [[Team:Content-Travel-Budget-Management|manage the travel budget]]
* Draft Call for Participation
** Send approved version to main
** Considering presentation of (how, when, by whom)
* Settle on motto
* Consider integration Pretalx/ticketing system (which ticketing system?)
* Document [[Team:Content#Outline|outlines]] of processes
** What to do in event of emergency (e.g. sudden society lock-down, etc)
** How to organize with ancillary teams (Music, Academic)

== Previous deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]

== Meetings ==

[[2020-09-12-Content-meeting|2020-09-12]] | [[2020-09-12-Content-meeting-minutes|minutes]]

[[2020-08-29-Content-meeting|2020-08-29]] | [[2020-08-29-Content-meeting-minutes|minutes]]

[[2020-07-25-Content-meeting|2020-07-25]] | [[2020-07-25-Content-meeting-minutes|minutes]]

[[2020-07-04-Content-meeting|2020-07-04]] | [[2020-07-04-Content-meeting-minutes|minutes]]

[[2020-06-20-Content-meeting|2020-06-20]] | [[2020-06-20-Content-meeting-minutes|minutes]]

[[2020-06-06-Content-meeting|2020-06-06]] | [[2020-06-06-Content-meeting-minutes|minutes]]

[[2020-05-16-Content-meeting|2020-05-16]] | [[2020-05-16-Content-meeting-minutes|minutes]]

[[2020-05-02-Content-meeting|2020-05-02]] | [[2020-05-02-Content-meeting-minutes|minutes]]

[[2020-04-11-Content-meeting|2020-04-11]] | [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] | [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

2020-09-12-Content-meeting

2020-08-29T13:55:08Z

Teirdes: Created page with "= Team Content Meeting = Online 2020-09-12 17:00 - 18:00 [https://pad.riseup.net/p/MCH2021-Content-Minutes-2020-09-12 Pad during the meeting, result in the..."

= [[Team:Content|Team Content]] Meeting =

Online 2020-09-12 17:00 - 18:00

[https://pad.riseup.net/p/MCH2021-Content-Minutes-2020-09-12 Pad during the meeting, result in the minutes]

[[2020-09-12-Content-meeting-minutes|Minutes]]

== Agenda ==

As decided in the [[2020-08-29-Content-meeting-minutes|2020-08-29 meeting]]:

The action points from the last meeting are shown at the topics they belong to below.

== Recap on action points ==
=== Walter to talk to C3VOC about remote participation ===
=== Claudia check in with team info/communication on opportunitiesto publish blogposts ===
=== Claudia draft a special topic blog on important of climate crisis in technical discussions ===
=== Aschwin ask Jeroen to write up an initial draft proposal on review process to be discussed this meeting ===
=== Robin draft proposal on review process ===
=== Coco reach out to the people dealing with FAQ on accessibility and wheelchair ramps for stages ===
== Status of submissions ==
== Reconciliation of envisaged draft review processes ==

== Topics for next meeting ==
== Next meeting time ==

2020-08-29-Content-meeting-minutes

2020-08-29T13:52:07Z

Teirdes: Created page with "= Team Content Meeting Minutes = Online 2020-08-29 14:00 - 15:00 Agenda [https://pad.riseup.net/p/MCH2021-Content-Minutes-2..."

= [[Team:Content|Team Content]] Meeting Minutes =

Online 2020-08-29 14:00 - 15:00

[[2020-08-29-Content-meeting|Agenda]]

[https://pad.riseup.net/p/MCH2021-Content-Minutes-2020-08-29 Pad during the meeting, result in the minutes]

== Administrivia ==

* Amelia Andersdotter volunteers to take notes.
* Walter van Holst agrees to chair the meeting.
* Agenda review:

Claudia wants to add the feedback on the CfP from Vesna:
* Clarify remote participation
* Contemporary and critical topics?
* How will orga deal with carbon footprint?

== CfP/Feedback ==

=== Remote participation ===

Need clarification on remote presentations, how this will work with recordings of sessions, streaming, etc. We want to avoid "can you hear me?" or "does it work? does it work?" connection testing. Possibility: add requirements on remote speakers w.r.t. connection quality and conferencing tooling.

People who indicate that they prefer to give a remote presentation could be given a document with criteria for remote participation that they will have to conform to. We should also indicate some deadline (a month?) for the presenter to demonstrate compliance (video sample, aspect ratio for slides, etc.).

'''Action point (Walter)''': Will talk to C3VOC about remote participation.

=== In event of cancellation? ===

The CfP should include information that in the event of corona-no-go, the camp is cancelled rather than shifted to virtual. Could be included in an FAQ for the entire event rather than in the CfP. The CfP should also probably not include information around general orga logistics (i.e. carbon footprint). What CfP could clarify is how to do remote presentations if desired and necessary in exceptional cases.

=== Contemporary and critical topics ===

'''Action point (team):''' In response to concerns that CfP does not highlight sufficiently contemporary topics, MCH2021 website could be enriched with a series of blogposts detailing content teams' reflections on these topics of outstanding import in contemporary digital rights discussions. Each team member wishing to contribute to an orga blog should feedback with the rest of team content before requesting publication on main site.

Purpose:

- expand on the CfP
- without changing it
- help ensure continued interest in CfP

Past experience shows that highlighting CfP helps people submit more proposals.

'''Action point (Claudia):''' Check in with team info/communication on opportunities to publish blogposts.

'''Action point (Claudia):''' Write a special topic blog on important of climate crisis in technical discussions.

== CfP / Pretalx ==

=== CfP has gone live. ===

All the old (dummy) submissions are cleared out. All submissions in the systems are now new ones (except the serious submission from Bert). Claudia and Robin checked the style-sheet. All done.

=== Status of submissions ===

There are seven (7) submissions to date.

One speaker has asked for clarification on whether we want visions for the future, stories of the past or accounts of the present. Proposal to challenge speaker. Attila not yet responded on hotel.

There will be sleeping facilities on site too. They are being built. Attila may have provided budget indications for accommodation already.

== CfP review process ==

'''Action point (Aschwin):''' Ask Jeroen to write up an initial draft proposal on review process before the next meeting.

'''Action point (Robin):''' Write up an initial draft proposal on review process before next meeting.

Postponed until next meeting: reconciliation of envisaged draft review processes.

== Zammad ==

Erik presents Zammad.

Visibility of Zammad sites should be restricted to editors or agents. Setting visibility to "public" creates a link that can be accessed by individuals without a log-in. The only purpose for which this is suitable would be something like a Speaker FAQ.

Many team members have not logged in yet.

Zammad will help keep track of tickets and finances, but does not have full-blown wiki functionality.

Erik will have more time to develop features/provide support in two months after he has finished his autumnal teaching duties.

Every team member should have received an e-mail with details about logging into Zammad. There is no single-sign-on for the totality of MCH2021 services yet.

== Other actions points ==

Update from Coco:

There is still a vacancy on accessibility. This should be added to the FAQ for the entire orga whether we have wheelchair ramps. No contact with the stage builders yet, but should return to this issue.

'''Action point (Coco):''' reach out to the people dealing with FAQ on accessibility.

'''For information (Erik):''' new version of Pretalx soon. We can come back to this at a later time.

== Speakers contacting ==

Will be covered in Zammad.

== Topics for next meeting ==

* Check back on action points
** Walter to talk to C3VOC about remote participation
** Claudia check in with team info/communication on opportunitiesto publish blogposts.
** Claudia draft a special topic blog on important of climate crisis in technical discussions.
** Aschwin ask Jeroen to write up an initial draft proposal on review process to be discussed this meeting.
** Robin draft proposal on review process.
** Coco reach out to the people dealing with FAQ on accessibility and wheelchair ramps for stages.
* Status of submissions
* Reconciliation of envisaged draft review processes.

== Next meeting time ==

[[2020-09-12-Content-meeting|12 September 2020]], 17:00-18:00

User:Teirdes

2020-05-02T20:44:06Z

Teirdes:

{{UserInfo
|NickName=Teirdes
|Languages=English, Swedish, (Dutch), (Romanian)
|HackerSpace=hsbxl, whitespace, forsken (if indeed any)
}}
Teirdes is Amelia Andersdotter.

It was her dream to understand

why on Team:Content not all team members were displayed

but it turned out

it had everything to do with the user form

which can be accessed

through the Special pages link on the left if you are logged in

her friends said her dreams were

not so ambitious but not all dreams

need to be large or unattainable

some can also pass

in but a few minutes

in fact most

User:Teirdes

2020-05-02T20:40:26Z

Teirdes:

Team:Content

2020-05-02T20:39:35Z

Teirdes: /* Team Members */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}

== Current deliverables: ==

* Draft Call for Participation
** Send approved version to main
** Considering presentation of (how, when, by whom)
* Settle on motto
* Consider integration Pretalx/ticketing system (which ticketing system?)
* Document [[Team:Content#Outline|outlines]] of processes
** What to do in event of emergency (e.g. sudden society lock-down, etc)
** How to organize with ancillary teams (Music, Academic)

== Previous deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]

== Meetings ==

[[2020-05-16-Content-meeting|2020-05-16]] | [[2020-05-16-Content-meeting-minutes|minutes]]

[[2020-05-02-Content-meeting|2020-05-02]] | [[2020-05-02-Content-meeting-minutes|minutes]]

[[2020-04-11-Content-meeting|2020-04-11]] | [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] | [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

User:Teirdes

2020-05-02T20:38:25Z

Teirdes:

{{UserInfo
|NickName=Teirdes
|Languages=English, Swedish, (Dutch), (Romanian)
|HackerSpace=hsbxl, whitespace, forsken (if indeed any)
}}
Teirdes is Amelia Andersdotter.

User:Teirdes

2020-05-02T20:37:58Z

Teirdes:

{{UserInfo
|NickName=Teirdes
|Languages=English, Swedish, Dutch
|HackerSpace=hsbxl, whitespace, forsken (if indeed any)
}}
Teirdes is Amelia Andersdotter.

User:Teirdes

2020-05-02T20:37:07Z

Teirdes:

{{UserInfo
|NickName=Teirdes
|Languages=English Swedish Dutch
|HackerSpace=hsbxl (if indeed any)
}}
Teirdes is Amelia Andersdotter.

Team:Content

2020-05-02T19:55:15Z

Teirdes: /* Current deliverables: */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}
== Current deliverables: ==

* Draft Call for Participation
** Send approved version to main
** Considering presentation of (how, when, by whom)
* Settle on motto
* Consider integration Pretalx/ticketing system (which ticketing system?)
* Document [[Team:Content#Outline|outlines]] of processes
** What to do in event of emergency (e.g. sudden society lock-down, etc)
** How to organize with ancillary teams (Music, Academic)

== Previous deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]

== Meetings ==

[[2020-05-16-Content-meeting|2020-05-16]] | [[2020-05-16-Content-meeting-minutes|minutes]]

[[2020-05-02-Content-meeting|2020-05-02]] | [[2020-05-02-Content-meeting-minutes|minutes]]

[[2020-04-11-Content-meeting|2020-04-11]] | [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] | [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

Team:Content

2020-05-02T19:53:19Z

Teirdes: /* Meetings */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}
== Current deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]
* Document [[Team:Content#Outline|outlines]] of processes
* Draft Call for Participation

== Meetings ==

[[2020-05-16-Content-meeting|2020-05-16]] | [[2020-05-16-Content-meeting-minutes|minutes]]

[[2020-05-02-Content-meeting|2020-05-02]] | [[2020-05-02-Content-meeting-minutes|minutes]]

[[2020-04-11-Content-meeting|2020-04-11]] | [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] | [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

2020-05-16-Content-meeting

2020-05-02T19:52:09Z

Teirdes: Created page with "= Team Content Meeting = Online 2020-05-16 14:00 - 15:30 Minutes == Agenda == As decided in the 2020-05-02-Cont..."

= [[Team:Content|Team Content]] Meeting =

Online 2020-05-16 14:00 - 15:30

[[2020-05-16-Content-meeting-minutes|Minutes]]

== Agenda ==

As decided in the [[2020-05-02-Content-meeting-minutes|2020-05-02 meeting]]:

# Final decision on the motto.
# Erik can prepare discussions on ticketing systems, but wants to have a direct line with the administrators for such a aystem.
# Layout for the CfP once it is released to the public. Timeline for providing this support.
# How many stages, stands, workshops etc? Early prepping with ensure better functioning facilities.
# What do we do if corona-crisis prevails? Contingency/emergency plans?
# Next meeting.
# ''If enough time:'' Music project, what happens with it? What is the overlap with content? [Optional pending feedback from music project team]

2020-05-02-Content-meeting-minutes

2020-05-02T19:48:54Z

Teirdes:

These are the minutes for the [[Team:Content|Content Team]] [[2020-05-02-Content-meeting|meeting on 2nd May 2020]].

present
Claudia
Walter
Aschwin
Coco
Erik
Jos
Robin
Amelia
Bert

# Amelia volunteers for note-keeping. Walter "volunteers" to chair the meeting.
# Changes to the agenda?
## There are no changes to the agenda at this time.
# FAQ format for the call for participation:
## In previous meeting it had been agreed to cooperate on a CfP on a riseup-pad. Deadline for amendments to draft CfP passed on April 25.
## Why would we want a FAQ format?
### We are concerned that people may misunderstand the spirit of the event.
### The CfP was also getting quite long, and an FAQ is a way of pushing some information to a voluntary digest.
### It is now a pleasant read, from its structure.
### There are still some grammar mistakes but they are easily fixed.
## Will we put this to the main orga as a pad or as an e-mail?
### '''Proposal 0''': to do so as raw text in an e-mail rather than as a pad. As content team we are responsible for deciding on what the CfP will end up looking like, so we should not give the impression that anyone could come in an edit it.
### No objections to Proposal 0.
# Pretalx
## In the previous meeting, it was agreed that we would want to progress with Pretalx.
## Features discussion
### We will have to manage our finances via Pretalx which did not make the developer happy. It could be developed in some other tool. We will need a ticketing system anyway, and that system could be integrated with Pretalx and also do the finances.
### This needs to work not only in the preparation, but also on-site so that we can make assessments by the speakers' desk when people say that they have made a claim that we have previously approved.
### Everyone who works at the speakers' desk would also need to have an account in the ticketing system. But this might be appropriate since we are more likely to have sensitive personal data (such as rankings of speakers) in Pretalx, making it inappropriate for this data to be made accessible to people outside of content team.
### Having an overview of our finances was one of the requirements we had on this tool before it was selected. Before the actual conference we may need to have an overview of our finances to know what kind of commitments we can make. A ticketing system would function also for this purpose if appropriately integrated with Pretalx, through e.g. plug-in.
# (bis) Redmine or Bugzilla?
## ''Ticketing system?''
### Redmine is the least bad ticketing system, but we also want to ensure that the peo ple who are administering the ticketing system are happy with this.
### '''Proposal 1''': ticketing system can be discussed in the next meeting after more careful preparations of the discussion?
### Concern that we will have a great ticketing system feud.
### Budget requests need to be made at the time when we start selecting the first speakers.
### Proposal 1 is accepted.
# Academic conference
## Report from Erik
### Kirils is going to be away for some weeks so he's not going to be able to help until he has returned. Other people are happy with having an academic subconference since it's not necessarily that big of an organizational drain. It only needs budget for projector, tents, chairs, and can otherwise be externally funded.
### Attila will be able to respond how much the estimated cost of a village with a stage and equipment associated therewith. Renting through the main organization will give access to potential group discounts.
### Having a small academic conference in the form of a village and having academics for the mainstage require different organizational effort: village format will be less labour and cost intensive.
### ''Do we have an additional wiki-page for the academic village conference?''
### No, it is currently part of the [[Team:Content|Team:Content]] wiki-page.
### The Team Content wiki-page does not currently have a lot of relevant information which makes it a bit more challenging to help other people navigate how they can easily assist with the academic conference organization.
### Academic village organization team still needs to constitute itself and this will be delayed by a few weeks still. Previous experiences from SHA do indicate somewhat of an urgency in getting this off the ground. Before the end of this summer there should probably be an orga team dedicated to getting this off the ground.
### The musical subtrack is in a similar position. There is now a wikipage for the musical subtrack. Wikipages may help other parts of the organization visualise the relationships between different subteams and what is happening in which sub-orga group.
# Goals and expectations: motto
## Do we want a motto at all?
### A motto for the CfP risks turning into a motto for the entire conference.
### Previous motto was "resilience and convenience".
### '''Proposal 2:''' we can have a longer list of motto proposals from which we pre-select two or three that become subject of a longer discussion at the next meeting.
### Brainstorming, tentative decision. There will be an e-mail.
# Roles for teams
## Mapping exercise on roles for teams
### We have received an e-mail asking for roles from teams. It is not currently clear what we are meant to respond to this e-mail.
### Team members listed on the public Wikipage is still incomplete. This is a UI issue, since all the team members are visible for a logged in user trying to edit the wikipage.
### Martian shares the part of the Wiki that describes [[Roles#Content|the roles of the content team]].
# Topics for the next meeting?
## Final decision on the motto.
## Erik can prepare discussions on ticketing systems, but wants to have a direct line with the administrators for such a aystem.
## Music project, what happens with it? What is the overlap with content? [Optional pending feedback from music project team]
## Layout for the CfP once it is released to the public. Timeline for providing this support.
## How many stages, stands, workshops etc? Early prepping with ensure better functioning facilities.
## What do we do if corona-crisis prevails? Contingency/emergency plans?
# Next meeting time?
## Three weeks we have orga meeting.
## Then have another meeting on May 16 to be able to bring news to the main orga meeting.
## Proposal: May 16, 14-15:30. No objections to this proposal.
# Chairperson decides meeting closed.

2020-05-02-Content-meeting-minutes

2020-05-02T19:47:13Z

Teirdes:

These are the minutes for the [[2020-05-02-Content-meeting|MCH Content Team meeting on 2nd May 2020]].

present
Claudia
Walter
Aschwin
Coco
Erik
Jos
Robin
Amelia
Bert

# Amelia volunteers for note-keeping. Walter "volunteers" to chair the meeting.
# Changes to the agenda?
## There are no changes to the agenda at this time.
# FAQ format for the call for participation:
## In previous meeting it had been agreed to cooperate on a CfP on a riseup-pad. Deadline for amendments to draft CfP passed on April 25.
## Why would we want a FAQ format?
### We are concerned that people may misunderstand the spirit of the event.
### The CfP was also getting quite long, and an FAQ is a way of pushing some information to a voluntary digest.
### It is now a pleasant read, from its structure.
### There are still some grammar mistakes but they are easily fixed.
## Will we put this to the main orga as a pad or as an e-mail?
### '''Proposal 0''': to do so as raw text in an e-mail rather than as a pad. As content team we are responsible for deciding on what the CfP will end up looking like, so we should not give the impression that anyone could come in an edit it.
### No objections to Proposal 0.
# Pretalx
## In the previous meeting, it was agreed that we would want to progress with Pretalx.
## Features discussion
### We will have to manage our finances via Pretalx which did not make the developer happy. It could be developed in some other tool. We will need a ticketing system anyway, and that system could be integrated with Pretalx and also do the finances.
### This needs to work not only in the preparation, but also on-site so that we can make assessments by the speakers' desk when people say that they have made a claim that we have previously approved.
### Everyone who works at the speakers' desk would also need to have an account in the ticketing system. But this might be appropriate since we are more likely to have sensitive personal data (such as rankings of speakers) in Pretalx, making it inappropriate for this data to be made accessible to people outside of content team.
### Having an overview of our finances was one of the requirements we had on this tool before it was selected. Before the actual conference we may need to have an overview of our finances to know what kind of commitments we can make. A ticketing system would function also for this purpose if appropriately integrated with Pretalx, through e.g. plug-in.
# (bis) Redmine or Bugzilla?
## ''Ticketing system?''
### Redmine is the least bad ticketing system, but we also want to ensure that the peo ple who are administering the ticketing system are happy with this.
### '''Proposal 1''': ticketing system can be discussed in the next meeting after more careful preparations of the discussion?
### Concern that we will have a great ticketing system feud.
### Budget requests need to be made at the time when we start selecting the first speakers.
### Proposal 1 is accepted.
# Academic conference
## Report from Erik
### Kirils is going to be away for some weeks so he's not going to be able to help until he has returned. Other people are happy with having an academic subconference since it's not necessarily that big of an organizational drain. It only needs budget for projector, tents, chairs, and can otherwise be externally funded.
### Attila will be able to respond how much the estimated cost of a village with a stage and equipment associated therewith. Renting through the main organization will give access to potential group discounts.
### Having a small academic conference in the form of a village and having academics for the mainstage require different organizational effort: village format will be less labour and cost intensive.
### ''Do we have an additional wiki-page for the academic village conference?''
### No, it is currently part of the MCH Content wiki-page.
### The MCH Content wiki-page does not currently have a lot of relevant information which makes it a bit more challenging to help other people navigate how they can easily assist with the academic conference organization.
### Academic village organization team still needs to constitute itself and this will be delayed by a few weeks still. Previous experiences from SHA do indicate somewhat of an urgency in getting this off the ground. Before the end of this summer there should probably be an orga team dedicated to getting this off the ground.
### The musical subtrack is in a similar position. There is now a wikipage for the musical subtrack. Wikipages may help other parts of the organization visualise the relationships between different subteams and what is happening in which sub-orga group.
# Goals and expectations: motto
## Do we want a motto at all?
### A motto for the CfP risks turning into a motto for the entire conference.
### Previous motto was "resilience and convenience".
### '''Proposal 2:''' we can have a longer list of motto proposals from which we pre-select two or three that become subject of a longer discussion at the next meeting.
### Brainstorming, tentative decision. There will be an e-mail.
# Roles for teams
## Mapping exercise on roles for teams
### We have received an e-mail asking for roles from teams. It is not currently clear what we are meant to respond to this e-mail.
### Team members listed on the public Wikipage is still incomplete. This is a UI issue, since all the team members are visible for a logged in user trying to edit the wikipage.
### Martian shares the part of the Wiki that describes [[Roles#Content|the roles of the content team]].
# Topics for the next meeting?
## Final decision on the motto.
## Erik can prepare discussions on ticketing systems, but wants to have a direct line with the administrators for such a aystem.
## Music project, what happens with it? What is the overlap with content? [Optional pending feedback from music project team]
## Layout for the CfP once it is released to the public. Timeline for providing this support.
## How many stages, stands, workshops etc? Early prepping with ensure better functioning facilities.
## What do we do if corona-crisis prevails? Contingency/emergency plans?
# Next meeting time?
## Three weeks we have orga meeting.
## Then have another meeting on May 16 to be able to bring news to the main orga meeting.
## Proposal: May 16, 14-15:30. No objections to this proposal.
# Chairperson decides meeting closed.

2020-05-02-Content-meeting-minutes

2020-05-02T13:39:03Z

Teirdes:

present
Claudia
Walter
Aschwin
Coco
Erik
Jos
Robin
Amelia
Bert

# Amelia volunteers for note-keeping. Walter "volunteers" to chair the meeting.
# Changes to the agenda?
## There are no changes to the agenda at this time.
# FAQ format for the call for participation:
## In previous meeting it had been agreed to cooperate on a CfP on a riseup-pad. Deadline for amendments to draft CfP passed on April 25.
## Why would we want a FAQ format?
### We are concerned that people may misunderstand the spirit of the event.
### The CfP was also getting quite long, and an FAQ is a way of pushing some information to a voluntary digest.
### It is now a pleasant read, from its structure.
### There are still some grammar mistakes but they are easily fixed.
## Will we put this to the main orga as a pad or as an e-mail?
### '''Proposal 0''': to do so as raw text in an e-mail rather than as a pad. As content team we are responsible for deciding on what the CfP will end up looking like, so we should not give the impression that anyone could come in an edit it.
### No objections to Proposal 0.
# Pretalx
## In the previous meeting, it was agreed that we would want to progress with Pretalx.
## Features discussion
### We will have to manage our finances via Pretalx which did not make the developer happy. It could be developed in some other tool. We will need a ticketing system anyway, and that system could be integrated with Pretalx and also do the finances.
### This needs to work not only in the preparation, but also on-site so that we can make assessments by the speakers' desk when people say that they have made a claim that we have previously approved.
### Everyone who works at the speakers' desk would also need to have an account in the ticketing system. But this might be appropriate since we are more likely to have sensitive personal data (such as rankings of speakers) in Pretalx, making it inappropriate for this data to be made accessible to people outside of content team.
### Having an overview of our finances was one of the requirements we had on this tool before it was selected. Before the actual conference we may need to have an overview of our finances to know what kind of commitments we can make. A ticketing system would function also for this purpose if appropriately integrated with Pretalx, through e.g. plug-in.
# (bis) Redmine or Bugzilla?
## ''Ticketing system?''
### Redmine is the least bad ticketing system, but we also want to ensure that the peo ple who are administering the ticketing system are happy with this.
### '''Proposal 1''': ticketing system can be discussed in the next meeting after more careful preparations of the discussion?
### Concern that we will have a great ticketing system feud.
### Budget requests need to be made at the time when we start selecting the first speakers.
### Proposal 1 is accepted.
# Academic conference
## Report from Erik
### Kirils is going to be away for some weeks so he's not going to be able to help until he has returned. Other people are happy with having an academic subconference since it's not necessarily that big of an organizational drain. It only needs budget for projector, tents, chairs, and can otherwise be externally funded.
### Attila will be able to respond how much the estimated cost of a village with a stage and equipment associated therewith. Renting through the main organization will give access to potential group discounts.
### Having a small academic conference in the form of a village and having academics for the mainstage require different organizational effort: village format will be less labour and cost intensive.
### ''Do we have an additional wiki-page for the academic village conference?''
### No, it is currently part of the MCH Content wiki-page.
### The MCH Content wiki-page does not currently have a lot of relevant information which makes it a bit more challenging to help other people navigate how they can easily assist with the academic conference organization.
### Academic village organization team still needs to constitute itself and this will be delayed by a few weeks still. Previous experiences from SHA do indicate somewhat of an urgency in getting this off the ground. Before the end of this summer there should probably be an orga team dedicated to getting this off the ground.
### The musical subtrack is in a similar position. There is now a wikipage for the musical subtrack. Wikipages may help other parts of the organization visualise the relationships between different subteams and what is happening in which sub-orga group.
# Goals and expectations: motto
## Do we want a motto at all?
### A motto for the CfP risks turning into a motto for the entire conference.
### Previous motto was "resilience and convenience".
### '''Proposal 2:''' we can have a longer list of motto proposals from which we pre-select two or three that become subject of a longer discussion at the next meeting.
### Brainstorming, tentative decision. There will be an e-mail.
# Roles for teams
## Mapping exercise on roles for teams
### We have received an e-mail asking for roles from teams. It is not currently clear what we are meant to respond to this e-mail.
### Team members listed on the public Wikipage is still incomplete. This is a UI issue, since all the team members are visible for a logged in user trying to edit the wikipage.
### Martian shares the part of the Wiki that describes the roles of the content team: https://wiki.ifcat.org/Roles#Content
# Topics for the next meeting?
## Final decision on the motto.
## Erik can prepare discussions on ticketing systems, but wants to have a direct line with the administrators for such a aystem.
## Music project, what happens with it? What is the overlap with content? [Optional pending feedback from music project team]
## Layout for the CfP once it is released to the public. Timeline for providing this support.
## How many stages, stands, workshops etc? Early prepping with ensure better functioning facilities.
## What do we do if corona-crisis prevails? Contingency/emergency plans?
# Next meeting time?
## Three weeks we have orga meeting.
## Then have another meeting on May 16 to be able to bring news to the main orga meeting.
## Proposal: May 16, 14-15:30. No objections to this proposal.
# Chairperson decides meeting closed.

Team:Content-Tool-Evaluation

2020-03-29T11:41:37Z

Teirdes:

This subpage helps [[Team:Content|Team Content]] define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used [http://frab.github.io/frab/ frab] (Ruby-on-rails), but will now assess [https://pretalx.com/p/about/ Pretalx] (Python) as potential replacement. An early iteration of this assessment work can be found [https://resistencia.pads.ccc.de/4 here] (Etherpad).

The assessment will be discussed on [[2020-04-11-Content-meeting|Team Content's meeting 2020-04-11]].

{| class="wikitable sortable"
|-
! Property !! frab !! Pretalx
|-
| Support CfP|| Yes || Yes
|-
| Support rating of submissions || ||
|-
| Support confirmation of submissions in several stages || ||
|-
| Support mass mails to submitters/speakers || ||
|-
| Support mass mails to subsets of submitters/speakers || ||
|-
| Support feed-back from audience* || ||
|-
| Planning tool (graphical) || ||
|-
| Planning publishing || ||
|-
| Support for a ticketing system || ||
|-
| Interface to Angel system || ||
|-
| In a "common" language*** || No (Ruby-on-rails) || Yes (python)
|-
| Secure (whatever that means)** || ||
|-
| Reimbursement management || ||
|-
| Reimbursement management per speaker || ||
|-
| Manually mark speaker as arrived || ||
|-
| Delete a submission category || ||
|}

* Does this mean feedback from audience once a talk has been given, or also during the evaluation phase?

** Seems like both frab and pretalx are "secure" within some definition of secure - how stringent do we want these requirements?

*** I took the liberty of classifying ruby-on-rails as "uncommon"

Team:Content-Tool-Evaluation

2020-03-29T11:31:28Z

Teirdes:

This subpage helps [[Team:Content|Team Content]] define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used [http://frab.github.io/frab/ frab] (Ruby-on-rails), but will now assess [https://pretalx.com/p/about/ Pretalx] (Python) as potential replacement. An early iteration of this assessment work can be found [https://resistencia.pads.ccc.de/4 here] (Etherpad).

{| class="wikitable sortable"
|-
! Property !! frab !! Pretalx
|-
| Support CfP|| Yes || Yes
|-
| Support rating of submissions || ||
|-
| Support confirmation of submissions in several stages || ||
|-
| Support mass mails to submitters/speakers || ||
|-
| Support mass mails to subsets of submitters/speakers || ||
|-
| Support feed-back from audience* || ||
|-
| Planning tool (graphical) || ||
|-
| Planning publishing || ||
|-
| Support for a ticketing system || ||
|-
| Interface to Angel system || ||
|-
| In a "common" language*** || No (Ruby-on-rails) || Yes (python)
|-
| Secure (whatever that means)** || ||
|-
| Reimbursement management || ||
|-
| Reimbursement management per speaker || ||
|-
| Manually mark speaker as arrived || ||
|-
| Delete a submission category || ||
|}

* Does this mean feedback from audience once a talk has been given, or also during the evaluation phase?

** Seems like both frab and pretalx are "secure" within some definition of secure - how stringent do we want these requirements?

*** I took the liberty of classifying ruby-on-rails as "uncommon"

Team:Content

2020-03-28T21:58:21Z

Teirdes: /* Current deliverables: */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}
== Current deliverables: ==

* [[Team:Content-Tool-Evaluation|Evaluate PretalX]]
* Document [[Team:Content#Outline|outlines]] of processes
* Draft Call for Participation

== Meetings ==

[[2020-04-11-Content-meeting|2020-04-11]] [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

Team:Content-Tool-Evaluation

2020-03-28T21:57:52Z

Teirdes:

Team:Content-Tool-Evaluation

2020-03-28T21:57:15Z

Teirdes: Created page with "This subpage helps Team Content define and assess criteria for Conference Planning Tools (CPT). Up until now, Team Content has used [http://frab.github.io/fra..."

Team:Content

2020-03-28T21:52:58Z

Teirdes:

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}
== Current deliverables: ==

* Evaluate PretalX https://pretalx-dev.ifcat.org/orga/login/?next=/orga/ (Add your findings in the pad https://resistencia.pads.ccc.de/4 )
* Document outlines of processes
* Draft Call for Participation

== Meetings ==

[[2020-04-11-Content-meeting|2020-04-11]] [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] [[2020-03-28-Content-meeting-minutes|minutes]]

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

Team:Content

2020-03-28T21:50:27Z

Teirdes: /* Tasks */

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}

==Tasks==

From [[Roles]]:

'''Content'''

* Write and publish a call for papers
* Evaluate submissions for presentations and workshops, inform speakers about whether their submission is accepted or not
* Schedule presentations and workshops
* Publish the program online
* Invite specific known interesting speakers
* Determine, with PL, the policy for reimbursement of expenses
* Integrate content organized by villages

With special assistance to

'''Heralds'''
* Train the Herald volunteers
* Moderate Q&A sessions at the end of talks (if requested by speaker)
* Monitor speakers and take care of needs that arise during presentations
* Watch the room and making sure the event/talk runs smoothly
* Minimize delays in the schedule (ensure speakers start and end on time)
'''Speaker desk'''
* Have a physical presence at the event where speakers can go to
* Confirm that the speakers are present, contact them and initiate rescheduling if not
* Inform speakers about the license for the stream
* Try to deal with last-minute requests/needs from speakers

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Current tasks: ==

* Evaluate PretalX https://pretalx-dev.ifcat.org/orga/login/?next=/orga/ (Add your findings in the pad https://resistencia.pads.ccc.de/4 )
* Document outlines of processes
* Get to a milestone planning
* Draft Call for Participation
* Lessons learned from SHA2017
* Content team: how many people do we prefer to have
* First thoughts on the budget we would like to have
* [[Teams#Team_checklist|Go through the Team Checklist]]

== Meetings ==

[[2020-04-11-Content-meeting|2020-04-11]] [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] [[2020-03-28-Content-meeting-minutes|minutes]]

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk

User:Teirdes

2020-03-28T21:47:15Z

Teirdes: Created page with "Teirdes is Amelia Andersdotter."

Teirdes is Amelia Andersdotter.

Team:Content

2020-03-28T21:46:49Z

Teirdes: /* Team Members */ added Amelia

{{Team
|Lead=User:Walter,User:Claudia,User:Martian,User:Robin
|Description=Curates the programme, from managing the CfP to setting up the schedule.

This team will have separate subteams for the speaker desk and the heralds. During the event it should ideally be based at the speaker lounge.

It will not do anything infodesk, media lounge, media desk related.
|Exclusive team=No
|Contact=content@lists.ifcat.org
|Projectleiding=Coco
}}
==Team Members==

{{TeamMemberEntry|User:Claudia}}
{{TeamMemberEntry|User:Wvholst}}
{{TeamMemberEntry|User:Martian}}
{{TeamMemberEntry|User:Jos}}
{{TeamMemberEntry|User:Robin}}
{{TeamMemberEntry|User:Teirdes}}
{{TeamMemberEntry|User:Bert}}
{{TeamMemberEntry|User:ErikTews}}
{{TeamMemberEntry|User:kirils (speakerdesk liaison)}}
{{TeamMemberEntry|User:Coco (projectleiding liaison)}}

==Tasks==

The team curates the programme, and also somewhat coordinate* things outside of the lecture-halls; like workshops, village activities, etcetera. With the help of villages and other groups, we will attempt to provide a more cohesive visitor experience, content-wise; with some overlap between the stuff going on at the campgrounds and the stuff in the lecture halls*.
*Coordination in this context doesn't mean deciding what is good content and what is not. Nor does it involve a high committee telling other people what to do. It rather means to entice villagers and other volunteers to join the bigger picture, and try to (partially) merge their content with the program, or prepare their own content in an accessible way. This may, of course, involve us pushing, harassing and stalking you from time to time. It also is likely to involve your stage place to give stage space to the main programme.

We are also responsible for helping out with the Speaker Desk and Heralds, although these will have separate (partially overlapping) teams.

== Outline ==

''Every potential speaker, including big names, have to have a proposal in FRAB or any other Programming Management System software. That doesn't mean that every speaker has to put it in themselves, only that there must be one (and with the consent of the speaker(s) involved, obviously)'' For instance, at OHM, the rather famous Dutch writer Arnon Grunberg had his literary agent put in a proposal for a storytelling workshop. Which we gratefully accepted after finally convincing ourselves that we weren't being trolled. Which we weren't.

Team:Content members "adopt" several high-profile speakers and had proposals put in Frab on their behalf in former camps.

If you feel a speaker *should* be there and none in Team:Content wants to "adopt" that speaker, then you must do it yourself or convince someone else to perform that task. If neither you nor anyone else cares enough to make a simple proposal in Frab happen, then it probably is not such a terrific idea, to begin with.

===== What does the approval process look like? =====

# Every proposal gets voted on in Frab by every member of Team:Content. Proposals that get high votes, clearly have the nearly unanimous "wow-factor" and are the ones that get confirmed first and are probably a good fit for the biggest stage. Since this voting process is more or less anonymous (well, not really, but for most intents and purposes it is), it also prevents the programme from becoming someone's line-up of favourite speakers.
# At this point we will try to work with Team:Communications to start communicating publicly about these cherries on the cake. This will be on our Blog, set up for this propose. Because those are likely to attract ticket sales.
# The rest of the proposals get discussed in several meetings. We aim for quality over quantity and rather have a sparse programme with lots of long breaks but high-quality talks than a crammed programme. It is an open-air hacker festival after all and there should be plenty of other things happening in villages to have a good time. Either way, the discussions about edge cases will be settled in person and will not necessarily be by consensus but just by majority voting.
# At OHM and SHA we asked villages to be able to use their stages (not very successfully). Unless a village specifically wants to hand over stage slots to the official SHA programming, we want to encourage villages to develop their own village programmes and want to give their curators access to Frab for that purpose.
# For every proposal that gets accepted, a member of Team:Content now *must* adopt that proposal, chase the speaker for confirmation and be the PoC for that speaker. This may include activities for visa-processing, travel and lodging arrangements etc. for those speakers that simply cannot be expected to arrange that themselves.
# Covering traveling and lodging expenses is ultimately a bit of an arbitrary decision. It is more a less a function of how much we want that speaker and what can be expected from a speaker her- or himself. If someone is a starving ethical hacker from, say, Moldova or Peru, we're much more likely to consider that person worth supporting than in the case of an employee of a Silicon Valley behemoth. In some cases there will have been preliminary discussions about that already along the lines of "if your proposal gets accepted and it is as good as you have shown elsewhere so you get to be the opening/closing speaker of one of the days, we may be able to contribute to your traveling and lodging arrangements". Thanks to several people in Team:Finance and Team:Projektleiding we have secured a modest budget through a government subsidy that is earmarked for this purpose. If anyone else wants to chip in for this purpose, please have them talk to Team:Finance first, but in principle that is welcome.
# Once we have done all the confirmations/rejections/passing on to villages, there will be a few weekends of planning sessions. With lots of post-its on the wall of an undisclosed location. Which should result in a programme. And therefore a pretext for all of us to have an awesome time.

== Speaker Desk: ==
* [[User:Kirils]] / WitchDoc

== Heralds ==
* WitchDoc/Ijon/Lindworm

== Current tasks: ==

* Evaluate PretalX https://pretalx-dev.ifcat.org/orga/login/?next=/orga/ (Add your findings in the pad https://resistencia.pads.ccc.de/4 )
* Document outlines of processes
* Get to a milestone planning
* Draft Call for Participation
* Lessons learned from SHA2017
* Content team: how many people do we prefer to have
* First thoughts on the budget we would like to have
* [[Teams#Team_checklist|Go through the Team Checklist]]

== Meetings ==

[[2020-04-11-Content-meeting|2020-04-11]] [[2020-04-11-Content-meeting-minutes|minutes]]

[[2020-03-28-Content-meeting|2020-03-28]] [[2020-03-28-Content-meeting-minutes|minutes]]

== Lessons learned from SHA2017 ==

https://orga.sha2017.org/index.php?title=Team:Content

https://orga.sha2017.org/index.php?title=Team:Content/Heralds

https://orga.sha2017.org/index.php?title=Team:Content/Speakerdesk