►
From YouTube: How to get selected to speak at GitLab Commit 2021
Description
John Coghlan, a member of GitLab's Developer Evangelism team and the Commit planning team, lead a workshop to help folks, particularly first-timers, prepare their submissions for the 2021 GitLab Commit CFP. This includes information about the event, what we're looking for in a proposal, and a break down of a winning submission.
The call for proposals (CFP) for GitLab Commit is open through Friday April 30, 2021. We are looking for great speakers (no experience necessary) to share their stories with our community.
Submit your proposal here: https://forms.gle/YU2sENCjcFBSv8VF7
A
All
right,
hi
everyone,
I'm
john
coglin,
I'm
on
the
community
relations
team
at
get
lab.
I
work
on
the
developer.
Evangelism
team
within
community
relations,
michael
and
jamie
from
my
team-
are
here:
hi,
michael
and
jamie
yeah,
and
one
of
the
things
that
we
work
on
as
a
team
are
speaking
at
events
and
also
helping
with
the
get
lab
commit
event,
and
so
I
think
I
can
bring
a
pretty
good
perspective
to
the
topic
that
we'll
be
discussing
today,
which
is
how
to
get
selected
to
speak
at
get
lab
commit
before
we
get
going.
A
A
The
code
of
conduct
is
linked
to
from
the
meetup
group
description.
I'm
also
dropping
a
link
in
the
chat.
I'd
ask
everybody
to
review
that
and
abide
by
it,
and
if
you
need
to
report
a
violation,
you
can
send
me
a
dm
in
the
zoom
chat
or
email
conduct,
gitlab.com
and
we'll
work
with
you
to
address
the
issue
with
that
said
thanks
everyone
for
joining
us
and
yeah,
I'm
really
excited
to
see
some
familiar
faces,
but
also
some
new
faces.
A
So
there's
in
gitlab,
there's
10
devops
stages
for
manage
and
plan
to
monitor
and
protect.
We
have
thousands
of
features
and
we
release
a
new
version
of
git
lab
every
month.
On
the
22nd,
so
we
just
released
our
13.11
release
yesterday
and
yeah,
we're
always
adding
cool
new
things,
and
I
think
you'd
be
amazed
at
like
the
breadth
of
what
gitlab
can
do.
You
know
we're
just
getting
started.
A
I
think
you
know
our
roadmap
is
really
ambitious
and
we
have
a
great
team
and
because
we
release
every
month,
there's
always
going
to
be
cool
new
things
for
you
to
kind
of
play
with
and
learn.
So
I'd
encourage
you
to
take
a
deeper
dive
if
you're,
if
you're
new
to
the
gitlab
community,
one
of
the
things
that's
interesting
about
gitlab
is
we're
an
open
core
company
and
what
that
means
is
that
you
know
we're
open
source.
A
Everyone
can
contribute
through
merge
requests
and
that
could
be
code
contributions.
Translations
improvements
to
our
documentation,
lots
of
different
ways
to
contribute
to
gitlab,
even
submitting
a
talk
to
participate
in
our
conference
is
a
great
way
to
contribute
to
the
community,
and
we
have
some
really
cool
community
programs.
Jamie
who's
on
the
call
runs
our
meetups
program
and
the
get
lab
heroes
program.
Mario
has
a
get
lab
hero.
So
if
you
have
questions
about
that,
we
can
put
mario
on
the
spot
later,
but
yeah.
A
A
Other
things
about
gitlab
that
you
might
not
know
we're
the
largest
all-remote
company
in
the
world.
We
still
say
that,
even
though
a
lot
of
companies
have
been
forced
into
remote
because
of
coven,
but
you
know,
I
think,
we're
like
we've.
Never,
you
know
really
had
an
office
and
none
of
our
team
works
in
offices,
and
so
I
think
we've
truly
lived
that
all
remote
kind
of
culture
and
have
created
a
ton
of
resources
to
help
people.
A
So
if
you're
kind
of
new
to
working
remotely
I'd,
encourage
you
to
check
out
our
all
remote
guides
and
the
other
cool
thing
I
like
to
mention
about
git
lab
is:
we
have
great
values,
our
values
are
credit
and
you
can
google
to
find
out
what
that
means.
But
the
one
I
like
to
talk
about
the
most
is
our
transparency
value,
and
if
you
want
to
see
how
transparent
you
are,
we
are
check
out
our
company
handbook.
A
So
there's
lots
of
really
interesting
stuff
in
there.
You
can
check
out
our
public
issue
tracker
to
see
what
we're
working
on
you
can
see
what
issues
are
assigned
to
me
and
the
other
people
on
the
team
to
see
what
we're
working
on
as
individuals
and
if
you
don't
get
enough,
zoom
fatigue
from
work
and
virtual
events.
You
can
also
watch
our
a
lot
of
our
meetings
on
our
gitlab
unfiltered
channel,
but
some
of
that
stuff
may
not
be
interesting
to
everyone,
but
it's
cool
that
we're
so
transparent
yeah.
A
So
before
we
get
started
with
the
workshop,
I
just
want
to
kind
of
reiterate
my
remark
earlier
that
this
is
being
recorded,
and
so,
if
you
don't
want
to
be
recorded,
please
keep
your
camera
off,
but
I'd
love
to
see
lots
of
faces.
As
I
go
through
the
presentation
today,
please
stay
muted.
Unless
you're,
you
know
asking
a
question:
the
noise
can
be
distracting
to
folks
I'd
love
to
see
where
folks
are
joining
from.
So
if
you
want
to
share
your
location
in
the
zoom
chat,
that
would
be
really
cool.
A
So
with
that,
I'm
going
to
share
a
presentation
that
I
put
together
that
has
some
slides
and
then
this
should
take
like
15
to
20
minutes.
I
would
say,
and
then
I'd
love
for
us
to
have
like
time
to
do
q
a
so.
We
can
answer
questions
about
specific
things
that
I
didn't
address,
things
that
I
did
address,
but
weren't
totally
clear
or
maybe
topics
or
kind
of
things
that
you
have
in
mind
that
you
want
to
get
feedback
on.
A
B
A
So
I
think,
there's
a
few
things
that
are
going
to
be
helpful
to
you
as
you
get
started,
kind
of
preparing
or
thinking
about
submitting
for
the
cfp.
You
know
the
theme
for
this
year's
conference
is
innovate
together,
and
this
theme
really
speaks
to
our
approach,
to
kind
of
how
we
build
our
product,
how
we
build
our
community.
A
You
know,
as
I
mentioned
earlier,
we
have
you
know
an
open
source
kind
of
project
that
everyone
can
contribute
to,
and
some
really
great
programs
that
you
know
encourage
all
types
of
contributions,
not
just
code,
and
I
think
this
is
something
that's
really
special
and
kind
of
unique
to
gitlab
and
something
that
creates
a
lot
of
value
for
our
customers
and
users.
People
don't
have
to
wait
until
you
know
a
bug
or
something
gets
prioritized
in
our
backlog.
A
They
can
go
in
and
you
know
create
the
changes
that
they
want
to
see
on
their
own
and
get
them
merged
in
the
next.
You
know
release
in
the
in
a
few
weeks
time,
and
so
I
think
that
that's
something
that's
pretty
cool
and
I
think
you
know
we're
trying
to
kind
of
get
that
message
out
there
more.
You
know
this
collaboration
with
our
community
and
that's
part
of
the
reason
we're
emphasizing
it
in
this
year's
theme
commits
an
annual
conference.
A
So
it's
actually
kind
of
a
little
bit
more
frequent
than
annual
the
first
year.
We
did
three
different
commit
conferences
in
three
different
locations:
new
york,
london
and
san
francisco,
and
then
this
is
going
to
be
the
second
time
we're
doing
commit
as
a
global
virtual
event.
So
it's
the
fifth
commit
in
the
last
three
years,
and
you
know
I've
worked
on
all
of
them.
This
is
the
third
time
where
I'll
be
reviewing
reviewing
proposals.
Second
time
I'll
be
leading
a
track,
and
so
I've
got.
A
I
think
I've
got
some
good
perspective
on
kind
of
what
we're
looking
for
and
I'd
love
to
answer
your
questions
later.
If
you
have
specific
ideas
in
mind,
as
I
mentioned,
the
event
is
going
to
be
virtual
and
you
know
I
think,
that's
great
for
lots
of
reasons.
You
know
it
allows
kind
of
everyone
in
our
global
community
to
get
together
participate
together,
consume
the
same
content
at
the
same
time.
A
But
if,
I'm
being
totally
honest,
I'm
really
excited
to
get
getting
back
to
in-person
events
sometime
soon,
so
we
can
all
hang
out
together
and
I
can
see
my
teammates
who
are
with
me
on
the
call
today
but
yeah
this
one's
going
to
be
virtual,
and
I
think
you
know
that's
great
from
a
speaker
perspective,
because
you
know
anybody
can
participate
and
you
don't
need
to
take
time
off
or
travel
or
do
anything
to
do
that.
You'll
be
able
to
record
your
talk
from
home.
A
So
I
think
you
know
if
you're
a
first-time
speaker
or
someone
who's
kind
of
new
to
speaking
at
conferences.
I
think
virtual
events
are
great
because
it's
a
lot
smaller
of
an
investment
to
get
started
and
yeah.
The
event
dates
are
in
august,
those
are
for
western
time
zones,
so
they
may
be
slightly
different
if
you're
in
apac
but
yeah,
I
think
for
the
most
part,
the
event
will
start
on
the
third
and
end
on
the
fourth
for
the
vast
majority
of
our
community
and
I'm
just
gonna
drop
oops.
A
A
So
just
some
more
housekeeping
stuff,
the
speaker
timeline
on
the
page.
The
cfp
kind
of
submission
page
you'll,
see
that
there's
three
different
session
links,
15,
30
or
45
minutes
we're
really
trying
to
kind
of
keep
talks
boxed
into
these
like
15
minute
increments,
because
it
helps
with
schedule
building.
So
just
keep
that
in
mind
as
you're
preparing
your
talk.
The
cfp
is
going
to
be
closing
a
week
from
today
on
friday
april
30th.
A
So
you
have
one
week
to
get
your
submission
in
and
if
you
haven't
submitted
yet
don't
worry
about
it
you're
in
good
company.
Normally
we
see
about
50
of
our
submissions
come
in
in
the
last
week,
so
lots
of
folks
are
are
still
working
on
theirs,
so
you're,
not
alone.
After
the
you
know,
cfp
closes
we'll,
have
a
committee
review
those
submissions
and
then
we'll
follow
up
with
folks
in
may,
and
then
the
talks
will
be
recorded
at
least
three
weeks
before
the
event
date,
so
the
recording
window
will
be.
A
You
know,
kind
of
end
of
june
into
the
beginning.
First,
two
weeks
of
july
and
as
I
mentioned
earlier,
the
event
dates
are
august.
Third
and
fourth,
we
have
a
long
list
of
topics
here
and
I
just
want
to
be
clear
like
for
folks
not
to
confuse
topics
with
stages
or
tracks.
You
know,
as
you
would
see,
in
a
traditional
conference,
these
are
not
necessarily
all
going
to
be
tracks
at
the
event.
A
So
you
can
kind
of
take
these
topics
and
and
take
them
in
lots
of
different
directions,
and
I
encourage
you
to
be
kind
of
flexible
with
how
you're
thinking
about
things
and
because
we
don't
really
have
a
set
expectation
for
how
you
approach
these
different
topics
that
are
listed
here
before
I
move
on.
Does
anybody
have
any
questions
about
these
topics
that
they
want
to.
A
You
can
absolutely
represent
yourself,
so
I
think
some
of
the
folks
that
will
be
presenting
you
know
will
be
there
and
kind
of
talking
about
what
they're
doing
in
their
professional
lives.
But
if
you
have
a
talk
that
you
want
to
do
about
things
that
you're
using
gitlab
for
on
a
personal
level-
or
you
know
separate
from
your
company,
that's
totally
fine
too.
A
No,
you
can.
You
can
have
a
talk
that
spans
multiple
topics.
I
think
one
thing
that
we
often
find
when
we're
reviewing
submissions
is
that
the
kind
of
we
call
them
architects,
so
these
stage
architectures
kind
of
putting
the
tracks
the
talks
together
for
their
particular
stage.
Multiple
people
will
want
the
same
talk,
and
so
then
there's
a
bit
of
discussion
internally
around
where
that
talk
will
fit
best
but
yeah.
If
you're.
If
your
talk
is
spanning
multiple
topics,
that's
fine
and
then
the
you
know.
A
A
There's
developers,
operations,
folks,
project
managers,
product
managers,
community
people,
like
myself,
you
know
business
operations,
folks
marketing
professionals,
sales
professionals
and
so
all
of
those
you
know
at
least
at
a
company
like
get
lab
where
we're
really
passionate
about
kind
of
using
our
own
product
and
drinking
our
own
champagne.
You
know-
and
so
I
would
encourage
you
to
think
about.
You
know
that
audience
when
you're
thinking
about
this
list
of
kind
of
target
audiences
as
listed
on
the
cfp,
is
like
it's
not
just
developers
and
engineers.
It
can
really
be
anybody.
A
A
A
All
right
cool
yeah,
so
what
we're
looking
for?
You
know
kind
of
in
a
proposal,
and
I
would
I
would
think
of
these
as
like
the
elements
of
a
great
proposal.
You
know
the
abstract
is
the
most
important
thing.
So
you
know
if
in
reviewing
these,
you
know.
Typically,
there
will
be.
You
know
more
than
100
submissions
for
an
event
like
gitlab
commit
and
someone
like
me,
you
know
to
get
through.
A
I
think
the
first
kind
of
thing
that
I'm
going
to
look
at
is
the
abstract
and,
as
I
read
through
these
abstracts,
the
one
that
cats
might
catch,
my
attention
we'll
note
that
and
then
we'll
take
a
deeper
dive
and
look
at
okay.
Where
does
this
fit
into
the
event
overall,
but
I
would
say
you
know
that
is
the
first
box
you
need
to
check
is
having
your
abstract
in
great
shape.
A
So
I
think
like
trying
to
think
about
which
topic
it
fits
into
or
what's
the
right
audience
and
all
of
those
things
you
know
are
kind
of,
maybe
five
percent,
I
would
say,
maybe
spend
five
percent
of
your
time
on
that
and
95
of
your
time
on
the
abstract
and
making
sure
that
your
abstract
is
really
strong.
Which
brings
me
to
my
next
point
like
the
elements
of
a
good
abstract.
I
think
they
need
to
be
well
written,
easy
to
comprehend
and
well
formatted.
A
This
can
be
tricky.
You
know,
because
of
the
nature
of
how
we
collect
submissions,
which
is
a
google
form.
So
I
would
encourage
you
to
have
a
document
separate
where
you
write
your
abstract
and
once
you
kind
of
have
you
know
your
edits,
complete
copy
and
paste
from
that
into
the
google
form.
I
think
you
can
run
into
formatting
issues
or
potentially
lose
your
work
or
or
other
things.
A
If
you
try
to
just
do
everything
in
the
form,
so
I'd
really
encourage
folks
to
use
a
separate
document,
and
you
know
avoiding
things
like
spelling
errors
and
other
things
that
may
you
know
when
you're
going
through
100
submissions
quickly.
If
you
see
you
know,
spelling
errors
or
you
know
formatting
errors
or
things,
it
may
just
give
a
negative
impression
of
the
talk.
Despite
how
interesting
the
topic
might
be
so
yeah.
A
You
know
what
the
talk
is
about
in
it
and
it
can
be
done
efficiently
within
the
confines
of
a
short
abstract.
So
I
recommend
that
structure
for
folks
who,
who
might
be
looking,
you
know
doing
this
for
the
first
time
or
kind
of
looking
for
some
guidance.
You
know
that's
a
great
approach
and,
and
then
lastly,
you
know
at
gitlab-
I've
mentioned
this
a
few
times,
but
we're
really
passionate
about
our
values
so
talks
that
align
with
our
values.
A
A
A
A
A
So
just
kind
of
you
know
thinking
about
how
you
how
folks
are
using
gitlab
to
you
know,
build
more
inclusion
in
their
teams.
How
are
you
using
gitlab
to
drive
your
business
forward?
Is
there
kind
of
cool
outcomes
that
your
business
is
experiencing
from
using
gitlab
or
your
team
is
experiencing
from
using
gitlab?
We
know
those
stories
are
out
there
and
we
want
to
share
them
so
that
other
folks
can
experience
those
same
benefits.
A
There's
some
construction
going
on
outside,
so
regulated
industries
are
an
area
where
we
know
a
lot
of
people
are
using
gitlab.
We
know
those
industries,
it
can
sometimes
be
hard
to
tell
stories,
but
if
you're
in
that
space,
we'd
love
to
hear
from
you
and
then
laughs.
Lastly,
like
these
shift
left
security
and
operation
stories,
you
know
are
things
I
think
our
team
is
keen
to
hear
about.
A
So
I'm
gonna
break
down
a
winning
submission.
I
should
have
chosen
one
of
mario
since
he's
here,
but
I
didn't
know
that
mario's
gonna
be
here
so
I
went
with
this
submission
from
sharon.
Alvarez
sharon
was
actually
had
two
submissions
that
she
submitted
for
our
last
virtual
event
and
both
of
them
got
selected.
So
I
felt
like
she
must
be
doing
something
right
and
so
I
elected
to
choose
her
talk.
This
one
was
actually
selected
for
our
main
stage.
So
sharon
submitted
the
cfp
cold.
A
Like
we,
you
know
she
wasn't
a
person
that
we
were
really
you
know
in
touch
with
or
reached
out
to
or
anything
like
that.
She
submitted
the
cmp
and
it
jumped
out
to
us
and
we
moved
her
up
to
the
main
stage,
because
it
was
such
a
well
well-written
proposal.
She
did
a
great
job
with
her
talk,
so
it
wound
up
being
like
a
win-win,
but
I
think
there
are
some
elements
to
this
proposal
that
made
it
really
stand
out,
and
I
was
one
of
the
people
that
you
know
this
caught.
A
First
caught
my
attention
and
championed
getting
her,
you
know
elevated
to
that
main
stage,
and
so
I
just
want
to
share
like
what
it
was
about
that
proposal
that
really
stood
out
to
me.
So
just
right
off
the
bat
you
can
see,
you
know
sharon's
doing
two
things
by
citing
you
know
gartner
and
other
research.
I
think
you
know
she's
establishing
that
she
has
some
subject
matter,
expertise
and
understands
her
domain
because
she's,
you
know
going
basically
saying
you
know.
A
I
know
what's
going
on
in
the
space
based
on
this
data,
and
you
know
so
that
really
catched
caught
my
attention
right
off
the
bat,
and
so
you
know
having
that
kind
of
some
kind
of
way
to
establish
yourself
as
a
domain
expert
in
your
abstract,
I
think,
will
go
a
long
way.
As
I
mentioned
earlier.
You
know
the
bios
are
kind
of
secondary,
and
so
even
though
folks
can
use
those
to
establish
their,
you
know
domain
expertise.
A
I
think
if
you
can
include
it
in
your
abstract,
that's
even
better,
because
if
your
abstract
doesn't
mention
that
we
may
not,
you
know,
be
able
to
read
the
bios
as
well.
I
think
the
other
thing
is,
you
know
this
kind
of
segment
shows
that
she's
taking
a
data
driven
approach,
and
you
know
I'd
highly
recommend
when
you
can
to
include
data
in
your
proposals.
A
So
if
you
know
you're
writing
a
proposal
around
how
git
lab
improved
your
team
efficiency,
if
you
can
say
we
made
our
teams
20,
you
know
times
more
efficient,
that's
going
to
speak
or
be
more
compelling
to
the
cf
cfp
committee
than
a
proposal
that
just
says
we
made
our
teams
more
efficient.
So
having
that
kind
of
you
know,
those
metrics
in
your
abstract
is
a
great
way
to
get
folks
attention
and
then
kind
of
going
back
to
my
point
earlier
around
problem
and
solution
after
she
establishes
that
domain
expertise
and
data-driven
approach.
A
She
jumps
in
and
explains
clearly
what
the
problem
is
that
she's
going
to
address.
So
the
problem
here
is
that
you
know
organizations
are
trying
to
do
these
devops
transformations
but
they're
failing
and
the
and
then
she
goes
on
to
you
know
kind
of
what
the
problems
are
that
are
causing
them
to
fail
and
so
right
away.
You
know
we're
not
even
done
with
the
first
sentence
and
sharon's
established
herself
as
a
domain
expert
and
clearly
states
what
the
problem
that
she's
going
to
be
talking
about
is,
and
so
we're.
A
It's
got
the
data
driven
and
domain
expertise,
the
problem
and
solution
structure
that
works
really
well,
and
I
think
you
know
it's
easy
for
the
cfp
committee
to
kind
of
understand
the
message-
and
you
know
what's
the
problem
and
what's
the
solution
and
and
we're
out
of
there.
You
know
within
a
few
minutes
and
yeah.
A
So
that's
the
end
of
that
presentation
and
there's
a
link
for
the
cfp
which
I'll
drop
in
the
chat
here
but
yeah
I
wanted
to
you
know,
I'm
sorry
that
took
a
little
bit
maybe
longer
than
I
was
expecting,
but
I
wanted
to
spend
the
rest
of
the
time
just
kind
of
talking
through
things.
If
folks
have
questions
around
how
to
structure
their
proposals,
topics
that
they
want
to
bounce
off
of
us,
you
know,
I
see
a
few
other
gitlab
folks,
michael
and
brendan
are
here
and
jamie.
A
A
D
I
have
I
have
a
question
about
the
time
submittal.
Actually,
if
you
submit
a
proposal
for
15
minutes,
or
would
you
consider
it
to
be,
maybe
if
you,
if
you
like
that
on
the
you
know
the
the
the
topic,
would
you
consider
it
for
30
minutes
or
if
you
propose
something
for
30
minutes,
if
you
think
it's
not
appropriate
for
30
minutes,
if
you
consider
it
for
15
minutes,
does
that
matter
at
all.
A
A
A
A
A
C
No
questions
really,
we
were
considering
submitting
two
different
talks,
one
the
one
for
the
ieee
one
would
probably
be
the
role
diversity
and
how
we're
you
know
doing
a
bunch
of
different
adoptable
stuff
there.
Would
it
be
okay
with
the
fact
that
we're
not
just
using
gitlab
but
we're
actually
doing
a
lot
of
integrations
to
help
with
the
world
diversity
aspects?
A
Yeah,
absolutely,
I
think,
we're
because
it's
git
lab,
we
talk
a
lot
about
git
lab,
but
really
we
want
to
you
know,
be
inclusive
of
other
kind
of
platforms
and
and
other
partners,
you
know
integrations,
are
an
important
part
of
workflows
for
probably
every
organization,
that's
using
git
lab,
and
so
I
think
that
would
be
something
people
would
be
interested
in.
So
definitely
welcome
that.
A
Yeah,
I
think
you
know,
as
I
mentioned
like
stuff,
around
regulated
industries
can
be
really.
Those
can
be
hard
stories
for
people
to
tell,
and
so
you
know,
if
you're
kind
of
in
a
unique
position
where
you
can
have
you
know,
clearance
or
whatever
you
need
to
tell
those
we'd
love
to
be
able
to
share
those
stories.
A
A
But
there
are
a
lot
of
folks,
you
know
in
those
types
of
industries
using
gitlab
because
of
like
the
strength
of
our
self-hosted
product,
and
so
I
think,
there's
a
lot
of
people
out
there
that
are
curious
to
hear
about
how
other
folks
are
using
it,
but
can't
talk
about
it
themselves.
And
so,
if
you
have
that
perspective,
that
would
be
great.
A
All
right
cool!
Well,
as
I
mentioned,
the
cfp
closes
next
friday.
If
anybody
wants
to
you
know
reach
out,
I'm
going
to
put
my
email
address
in
the
chat
box.
I'd
be
happy
to
do
like
one-on-one,
chats
with
folks
about
their
ideas
or
just
go
back
and
forth
over
email
to
help.
You
refine
your
idea.
If
you
want
to
send
me
your
abstract,
for
a
review
before
you
submit,
so
I
can
give
you
feedback,
I'm
happy
to
do
all
that
so
yeah.