How do I find the daily schedule for remote participants?
The latest version of the schedule is online at https://open-security-summit.org/schedule/all/ Daily schedule: 8:30 – 9:20 Breakfast and Registration 9:20 - 10:30 Keynotes 10:30 - 12:30 Sessions 12:30 - 13:30 Lunch 13:30 – 15:00 Sessions 14:30 - 15:00 Sessions 15:00 - 15:30 Break 15:30 - 16:30 Sessions 16:30 – 17:30 Sessions 18:00 - 19:00 Dinner 19:30 – 21:00 Sessions 21:00 - 23:00 Sessions
On Monday we start with light/planning Working Sessions in the morning and do the Briefing over lunch
How can I join the sessions I’ve registered for?
Open the Google Meet URL and join the session. Meet URLS will be available from 10:00 p.m., Sunday, 3 June 2018.
How do the sessions work for remote participants?
Join the Google Meet and follow and participate in the session using Chat to ask questions or to indicate that you wish to address the session. You can request copies of slides etc., and contribute to the outcomes.
What is expected of me as a remote participant?
The expectations of remotte participants are the same as for on-site participants. Each of the Summit’s 140+ working sessions will create a published deliverable for the wider InfoSec Community to engage with. This high level of productivity does require some essential commitments from the attendees, including participation, mutual respect, and radical candour. For more information, see here.
How can I get involved?
The OSS Summit is a participant-driven event, dedicated to the collaboration of Development and Security professionals, with a strong focus on DevSecOps.
Can I invite others to join?
You can share the Google Meet URL with people who are interested in joining remotely. Meet URLS will be available from 10:00 p.m., Sunday, 3 June 2018.
If I need help who should I contact?
The team is waiting to help you! Get in touch via Slack on os-summit.slack.com workspace. We have various channels to support the topics that interest you. #oss-general This channel is for workspace-wide communication and announcements. All members are in this channel. #oss-helpdesk This helpdesk is for participants with general issues regarding the Summit. Tracks and sessions related channels We have channels for every track and session. The following legend describes the prefixes of the channels’ names for the tracks and sessions. w = working sessions u = user session p = product session t = track Example: the channel name for the working session “Agile Practices for Security Teams” is: #w-agile-prac-sec-team Send an email message
If you would like to email before or during the event please contact firstname.lastname@example.org.