►
Description
This is a recording of the GitLab Virtual meetup from 2020/05/29 featuring Abubukar Siddiq Ango and Emily Chin.
Title: How to get selected to speak at GitLab Commit (first-time speakers welcome)
Description: GitLab Commit brings together the GitLab community to connect, learn, and inspire. The call for proposals (CFP) for GitLab Commit is now open. We are looking for great speakers (no experience necessary) to share their stories with our community. In the recording, members of our Commit team share information about the events, talk about what we're looking for in a proposal, and break down a winning submission.
Submit a talk via https://forms.gle/sGWL9nrQSuXup7wD7
A
Yeah,
thank
you
very
much.
Everyone
for
joining,
like
John,
introduced,
I'm,
hungry
technical
evangelism
program
manager
at
github
and
also
part
of
the
committee
for
organizing
committee
and
basically
I'll,
be
talking
about
getting
a
CFP,
has
accepted
for
the
c'mere,
but
you
keep
up
community
event
now.
Three
things
that
will
be
sharing
for
everyone
to
take
note
of
is
first
CFP
guidelines.
A
Most
times
when
submitting
for
talks,
most
people
either
miss
some
critical
part
of
the
guidelines
or
very
important
details
in
the
guidelines
that
might
lead
to
getting
accepted
more
like
it
might
be
what
we
are
looking
for,
or
some
specific
details
that
are
required
for
submitting
for
some
tracks.
So
the
safety
guidelines
is
one
of
the
key
things
that
one
needs
to
really
pay
attention
to
read
very
well
understand
before
you
paying
a
thought
and
Amy
do
we'll
be
sharing
more
about
that
now.
A
Also
it's
one
of
the
things
you
have
to
first
identify
from
okay,
I
will
from
the
CFP
guidelines
and
thankfully
part
of
what
Emma
will
be
showing
is
you
know,
you'll
be
sharing.
It
get
lap
stories
your
post,
Maya
post-mortem
after
some
things,
went
wrong
your
war
stories
or
maybe
some
successes
that
you've
had
when
you
are
one
is
in
gitlab
or
probably
some
tough
leadership
stories.
Maybe
you've
been
able
to
identify
some
case
studies,
use
cases
awesome,
but
are
innovative
ways
of
using
gitlab
or
using
git
like
to
do
things.
A
This
can
be
something
you
share
also
now
also
a
live
demos
at
most
times
leads
to
more
credibility,
and
most
presentations
always
was
to
see
live
demos.
We're
able
to
showcase
is
not
just
you
telling
people
okay
this,
and
this
is
what
we've
done,
but
you
are
able
to
demonstrate
it,
and
it
goes
a
long
way
in
a
CFP
getting
accepted
now
at
develop
in
detective
Angeles,
a
market
lab
one
of
the
model
that
we
use
most
times
when
we
are
writing
the
CFP
Stu
meet
all
looking
at
CF.
A
This
is
the
SC
q,
a
model
which
stands
for
situation,
complication,
question
and
answer.
The
first
thing
is
a
situation.
Okay.
What
exactly
do
you
want
to
talk
about?
What's
the
situation
around
it?
Why
is
it
something
that's
important
now?
What
complication
is
there
that
you
are
trying
to
make
people
understand
and
provide
a
solution
for
then?
Why
is
that
complication?
Something
we
should
worry
about?
That
is
where
the
question
comes
in
okay,
so
the
Saltine
is
happening,
but
yeah
it's
happening.
How?
A
What
exactly
is
the
reason
why
I
should
care
about
it
or
why
is
it
a
problem
for
me,
then
you
will
now
provide
an
answer.
Okay,
since
this
is
the
problem-
and
this
is
why
it's
important
for
you
to
know
that
it's
a
problem,
then
this
is
how
you
will
solve
it.
So
and
most
this
will
give
the
person
reading
your
CFP
and
idea
of
okay,
exactly
we
are
talking
about
it
from
here
trying
to
solve
and
the
solution
you
are
providing
now
I
will
be
showing
it.
A
This
isn't
like
the
best
CSP,
but
this
is
just
an
example
of
CSP
that
uses
the
NCQA
model
first,
here
I'm
talking
about
hush-hush,
acog
votes,
basically
and
how
to
use
it
with
people
of
CI.
So
for
my
tattoo
yeah,
sometimes
tattoos
are
one
of
the
ways
you
can
like
get
on.
Video
CSP
suits
being
creative
and
how
do
I
put
it?
Let
me
just
being
creative
with
your
tattoos,
can
definitely
gets
some
eyeballs
on
your
CF
piece
at
first
now,
first
I
introduced
exactly
were
talking
about
the
situation.
It's
hard
to
keep
secrets.
A
If
you
are
having
a
problem,
you
identify
the
problem
communities
and
you
were
able
to
find
a
way
around
it.
Going
straight
to
the
solution,
sometimes
isn't
really
exciting.
But
if
you
want
to
see
hooky,
how
did
things
go
wrong?
What
are
the
steps
you
used
to
identify
how
to
go
wrong
and
at
the
end
of
the
day,
how
did
you
solve
it?
What
are
the
results
that
you
achieved
from
solving
it?
Maybe
some
increase
in
performance
or
some
maybe
some
includes
in
sna
and
so
on.
A
So
production
results
are
a
very
good
way
to
show
that
okie
units,
a
career-tech,
Nevada
you've,
had
the
experience
with
what
you
are
talking
about,
then
scoop
most
people
when
they
are
presently
a
CFP,
so
presenting
talked
about
is
that
are
too
broad
so,
but
it
is
very
important
to
scope
to
one
specific
part
of
a
topic.
If
oil
we
won't
talk
about
is
too
broad,
you
pick
a
section
you
scope
into
that.
Then
you
go
as
comprehensive
as
possible
on
a
particular
parts
of
a
topic
that
you've
chosen.
Maybe
you
want
to
talk
about.
A
Also,
when
you
are
submitting
a
CSV
stay
as
much
as
possible
to
gauge
what
kind
of
audience
are
going
to
be
speaking
to
and
what's
their
technical
capacity
so
that
you
know
end
up
submitting
it
CFP
to
people
who
have
an
idea
or
where
I
did
know
we're
talking
about
meaning
obvious.
So
it's
better
to
already
identify
who
exactly
your
audiences.
They
are
technical
know-how.
You
think
what
they
are
expecting
most
times.
Dc
has
become
b2
already
detail
within
the
safety
guidelines.
A
Okay,
this
is
the
kind
of
audience
and
the
kind
of
content
we
think
the
audience
was
that
way.
You
can
add
to
collective
knowledge
instead
of
just
teaching
the
obvious
test
that
before
you
know,
and
the
whole
thing
becomes
boring
at
the
end
of
video
now
real
technical
details,
especially
when
your
audience
will
understand
the
details
of
issues
and
challenges.
Even
contact
not
just
to
Tom
beats
down
into.
A
Maybe
it
comes
down
to
adding
new
your
audience.
If
it's
the
people
in
your
audience,
our
CIOs,
you
know.
Definitely
you
don't
necessarily
have
to
go
down
deep
into
technical
details,
but
we
are
submitting
to
maybe
cognitive
enthusiast
at
intermediate
or
advanced
level.
They
won't
get
bored
with
technicalities
so
part
of
identifying
your
audience
applaud.
If
you
want
identify
your
audience,
the
technicalities
and
challenges
on
everything,
the
petty
details
of
how
this
way
we're
done
always
be
exciting
to
the
CFP
committee
and
also
the
audience
now
one
very
great
accounting.
A
When
you
are
some,
it's
ESP
sees
to
identify
a
new
small
nd,
CFP
committee.
How
do
you
think
in
a
wooden,
especially
like
the
committee
events?
Everyone
is
sick,
it
lava,
so
we
will
think
in
terms
of
things
around
remotes
cloud
native
gitlab
and
so
on
so
identifying.
What's
the
committee
cares
about
and
what's
the
exactly,
they
are
looking
for.
It's
extremely
important
now
yeah,
like
I
mentioned
previously.
Titles,
are
very
important.
Some
titles
don't
make
it
easy
for
one
to
understand
exactly.
A
What's
the
person
wants
to
talk
about,
except
you
go
into
the
details
of
the
CFP,
so
trans
much
as
possible
to
make
it
title
very
glaring,
very
concise
and
should
have
the
necessary
keywords
that
at
first
Lu
one
understands
exactly
what
you
want
to
talk
about.
So
these
are
the
few
things
I
want
to
share
yeah.
If
you
have
any
questions,
I'll
gladly
pick
them
we're
doing
it.
Your
initiation,
so
over
to
you,
John.
B
B
C
You
John
and
I'm
dropping
the
link
to
the
CFP
in
the
chat,
channel
and
I
will
share
my
screen
to
chat
about
the
Coffman
proposal
itself
and
what
the
team
is
looking
for.
So
if
you
haven't
already
seen
it
our
culture
proposals
link
is
a
Google
Form
and
we're
constantly
iterating,
based
on
the
feedback
that
we're
getting.
So
thank
you
to
everyone.
Who's
provided
some
feedback
if
you've
already
submitted.
Thank
you.
We
are
still
pulling
great
content,
so
we
want
to
make
sure
that
we
are
as
inclusive
as
possible.
So
a
few
key
details.
C
Our
call
for
proposal
closes
next
Friday,
which
is
June
5th.
The
goal
is
we're
getting
pretty
close
to
our
our
cap
for
proposals,
but
we
want
to
make
sure
everyone
has
a
chance
to
get
their
ideas
in
and
we
have
four
different
types
of
sessions
that
you
could
submit
for.
We
have
a
kind
of
our
lightening
sessions
at
15
minutes,
a
30
minute
talk,
45
minutes
and
a
panel
discussion.
So
for
anything
besides
the
panel,
we
have
a
max
of
two
speakers
per
submission.
C
We
have
seven
tracks
listed,
get
lab
how
to's
tips
and
tricks
leading
transformation,
leading
transformation
in
the
public
sector
cloud
native,
devops,
dev
suck-ups.
Everyone
can
contribute
and
remote,
but
always
connected.
So
I
won't.
I
won't
read
the
descriptions
to
you,
but
as
john
and
abu
bakar
I've
mentioned,
the
CFP
review
committees
will
be
very
specific
to
each
of
these
tracks.
Each
track
will
have
its
own
team,
selecting
reviewing
and
defining
the
agendas
for
their
track.
So,
for
example,
John
is
the
the
track
manager
for
everyone
can
contribute
and
so
think
about
his
expertise.
C
His
his
you
know
deep
connection
with
the
community,
so
as
you're
writing
proposal,
if
you're
submitting
for
the
everyone
can
contribute
track.
You
know
be
sure
to
think
about
laying
it
out
in
that
s
cqa
format.
What
is
the
situation
set?
The
stage?
What
is
the
complication?
Why
is
there
a
need
for
the
solution
that
you
are
presenting
and
then
and
then
being
able
to
share
kind
of
the
the
challenges
that
you
had
to
overcome?
The
the
problem
that
was
presented
will
really
help
to
level
set
and
help
your
audience,
not
just
the
the
review.
C
The
review
committee,
but
also
the
people
who
are
listening
to
your
talk,
have
a
connection
with
the
content
right.
We
want
people
to
get
the
best
content
possible
and
really
understand
some
actionable
takeaways
and
we're
happy
to
chat
through
any
proposal.
Questions
that
you
have
commit
at
gitlab
come
straight
to
me.
So
if
you
want
to
chat
through
ideas,
if
you
want
to,
you
know,
get
some
feedback
on
what
track
might
be
the
best
fit
I'm
happy
to
help
there.
Oh
I
didn't
even
know
how
to
do
this.
C
Drawing
thing
John,
so
cool
and-
and
this
recording
element
is
key
because
commit
is
going
to
be
virtual.
We're
actually
going
to
be
pre
recording
with
all
of
our
speakers,
so
that
way,
we'll
have
lots
of
time
to
practice
to
help
our
speakers
feel
really
prepared
and
to
get
all
that
content
as
evergreen
content.
C
So
here
you
can
slide
right
on
through
the
full
CFP.
We
want
to
make
sure
you
see
all
the
questions
that
you
need
to
prepare
ahead
of
time,
so
I
will
just
scroll
on
through.
You
can
see
the
selections
that
you
need
to
make
in
terms
of
writing
your
abstract
again,
keep
in
mind
that
seq
a
format
it'll
be
really
helpful
in
terms
of
helping
the
selection
committee
to
understand
why
you
know
the,
why
the
how
and
they
who
your
you're
talking
really
connect.
C
With
last
time
we
had
this
meetup
someone
asked
about
how
long
the
app
chuck
should
be
well,
there's
no
minimum.
There
is
a
character,
maximum,
that's
900
characters,
and
that's
just
so.
We
want
to
encourage
you
to
be
as
concise
as
possible
while
answering
those
questions
here,
you'll
select,
which
track
or
tracks
you
want
to
apply
to.
C
C
C
Our
our
track
management
teams
will
be
getting
together
next
week
to
start
planning
their
review
process
before
they
jump
into
the
review
process
and
the
goal
is
we're
gonna
start
announcing
some
speakers
in
mid
to
late
July,
so
with
that
I
will
scroll
back
to
the
top
and
I'd
love
to
see.
If
anyone
has
any
questions,
any
ideas
that
you
want
to
chat
about,
or
any
feedback
about,
the
CFP
forum
itself.