►
From YouTube: Spotlight on Maintainers - Universe 2022
Description
Open source runs the world, but who runs open source? Join Abigail Cabunoc Mayes live on the garden stage as she chats with open source maintainers and GitHub stars.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
A
The
humans
behind
open
source,
so
I'll
be
talking
to
a
couple
open
source
maintainers
about
what
it
means
to
be
a
maintainer
so
joining
me
today
we
have
Barbara
Forbes
Barbara
is
the
GitHub
star
in
Microsoft
Azure
MVP,
with
a
focus
on
Powershell
and
infrastructure
as
code,
and
we
have
tyranny.
Siren
is
a
principal
developer,
Advocate
at
twilio,
where
they
spend
their
time
working
with
the
product
teams,
improving
developer
experience.
A
B
So
for
open
source
I
originally
got
started
playing
video
games.
I
played
a
lot
of
video
games,
probably
when
I
shouldn't
have
been,
and
through
that
I
kind
of
found,
a
bunch
of
different
communities
and
those
communities.
They
kind
of
ended
up
leading
me
into
okay,
like
how
do
I
maintain
a
community,
how
I
manage
a
community
and
that
you
know
led
me
to
forums
so
I
used
to
open
up
a
bunch
of
free
forums,
and
then
you
know
freeform
systems
weren't
really
doing
what
I
wanted.
B
So
from
there
I.
You
know
I
moved
into
like
okay.
How
do
I
actually
set
up
my
own
forum
and
I
got
involved
in
IBB
I?
Did
that
for
I?
Think,
like
two
years
yeah,
and
from
that
you
know
their
their
release
cycle
was
a
bit
different
than
kind
of
what
I
was
wanting
from
software
from
open
source.
It
was
a
bit
slower
than
I
was
looking
for
so
I
from
there
I
started
kind
of
like
branching
out
like
okay
I,
like
JavaScript
I
like
web
development.
B
This
is
the
thing
I'm
interested
in
how
what
are
some
other
things
that
I
could
find
and
get
involved
in,
because
I,
really
like
this
code
and
open
source
stuff
from
that
I,
you
know,
was
going
through
kind
of
JavaScript
and
JavaScript
Twitter
and
found
a
blog
post
by
Michael
Rogers.
That
was
kind
of
announcing
the
the
fork
of
iojs
out
of
node,
and
you
know
doing
a
really
good
job
at
welcoming
non-technical
contributions.
There's
like
a
whole
paragraph
at
the
bottom,
just
kind
of
saying.
A
B
Performing
JavaScript
so
I,
you
know,
got
involved
in
that
showed
up
to
the
website.
Working
group
repo
started:
writing
a
bunch
of
content
and
like
trying
to
help
them
kind
of
do
better
content,
because
I
was
a
really
good.
Writer
and,
like
you
know,
talk
talk
about
technical
things,
but
I
wasn't
like
necessarily
experienced
with,
like
you
know,
performing
JavaScript
and
stuff.
B
So
from
there
I,
you
know,
did
a
bunch
of
work
in
that
repo
eventually
got
to
the
point
where
it
was
like
so
much
work
that
I
was
doing
in
that
repo
that
it
was
kind
of
drowning
out
the
other
work
that
was
happening.
So
we
split
that
off
into
the
evangelism
working
group
and
from
there
I
just
kind
of
continued
going
up
up
in
node
and
doing
more
and
more.
There
eventually
got
a
job
offer
from
that.
B
B
A
A
B
A
B
So
I
am
you
know:
I
can
write
pretty
good
JavaScript
now,
maybe
not
as
much
C
plus
I
try
to
avoid
that
as
much
as
possible,
but
yeah
you
know,
I
was
able
to
grow
because
of
that
like
non-technical
base,
yeah
and
you
know,
grow
into
my
entire
career.
You
know
now
as
a
principal
developer,
Advocate
focusing
on
JavaScript.
That's.
A
C
Yeah,
it
happened
a
little
bit
by
accident,
so
what
I
was
doing
was
just
doing
my
day-to-day
job,
working
with
Azure
working
Automation
and
really
creating
my
own
solutions
for
problems
I
encountered
in
my
own
work
and
I
started
blogging
about
these
things
thinking.
Well,
maybe
someone
else
has
the
same
problem
and
often
I
would
publish
the
code
on
GitHub.
Just
so,
I
have
someone
to
somewhere
to
store
it.
C
Yeah
yeah
and
I
write
their
blogs
about
it
and
then
suddenly
I
discovered
that
people
were
adding
stars
to
my
repository
and
they
were
creating
issues
and
stuff
like
that,
and
I
was
okay.
This
is
a
serious
thing
now.
I
need
to
start
maintaining
this
stuff
so
really
just
by
accident
like
okay.
This
is
not
something
people
can
use
yeah.
C
A
C
I
thought
yeah:
maybe
people
can
use
this
so
I'll
put
this
online
and
I
put
it
in
the
gallery
and
then
I
checked
and
it
had
like
40,
000
downloads
and
I
thought.
Oh
I
can't
just
make
some
changes
now,
like
I
can't
be
like
oh
change
this,
because,
like
five
people
are
using
it
yeah
now,
I
have
to
actually
be
careful,
so
I
need
to
check
if
a
change
is
actually
breaking
and
have
some
sort
of
process
going
on
yeah.
A
B
A
C
A
C
B
A
lot
of
the
projects
I
operate
in
are,
like
very
large
scale,
widely
used
projects
and
I
think
when
a
project
gets
big
enough.
Honestly,
just
communication
between
people
is
a
huge
huge
challenge
and,
like
some
people
are
gonna
struggle
with
that
more
right
or
some
people
are
like
you
as
an
individual,
are
going
to
communicate
differently
than
other
people
will
and
being
able
to
kind
of
manage
that
and
like
find
a
place,
a
way
where
you
can
kind
of
be
okay.
A
B
That's
a
really
big
one
for
me,
I
think
in
terms
of
smaller
projects,
personal
projects,
I
think
just
dropping
perfectionism
is
really
important.
It's
hard
to,
like
you
know,
I
can
sit
there
and
work
on
a
project.
I
mean
I've
done
this
so
many
times,
usually
when
I'm
on
an
airplane
and
I
have
so
much
free
time
to
just
sit
and
write
code,
but
yeah,
just
you
know,
being
okay
with
something
being
imperfect,
being
not
complete
and
like
just
putting
it
out
there
and
having
it
be
in
that
incomplete
State.
B
B
But
just
getting
it
out
there
and
like
even
in
barely
functional
or
non-functional
state
and
being
able
to
work
on
those
iteratively
right
in
the
way
you
would
in
a
bigger
project,
yeah
I
think
that's
a
really
a
really
big
thing.
That
I've
seen
be
helpful
and,
like
I
mean
you
know,
through
other
open
source
things
projects
that
I've
worked
on.
There
was
a
decentralized
open
source
social
protocol
that
I
used
to
be
a
part
of
called
tent.
B
A
B
A
That
makes
a
lot
of
sense,
yeah
and
that's
something
I
still
struggle
with
with
working
open
is
just
that
vulnerability
of
like
putting
something
out
there
for
others
to
see
for
the
first
time,
but
again,
if
you're
putting
something
imperfect
that
just
leaves
room
for
others
to
come
in
and
fix
it.
Yeah.
B
A
A
B
A
B
C
Exactly
and
it
can
be
scary
because
when
are
you
a
developer,
when
are
you
good
enough
at
a
language
yeah
yeah,
there
are
no
set
limits
and
the
only
way
to
find
out
is
to
put
yourself
out
there
yeah
and
just
take
that
chance.
I
recommend
always
finding
someone,
you
can
trust.
So
if
you
feel
yourself
getting
stuck
with
the
feeling,
then
you
have
someone,
you
can
trust
and
say:
hey
I'm,
not
feeling
confident
about
this.
What
do
you
think
should
I
put
it
out
there?
A
A
B
C
Always
very
open
about
it,
which
helps
me
just
have
some
people
around
say:
I
have
no
clue
if
I'm
doing
it
right,
yeah
and
I
often
even
say
I
know.
This
is
silly
probably,
but
just
check
this
for
me
and
I
can
get
let
go
of
it
because
I
feel
I'm
getting
stuck
so
I'm
really
open
about
it
with
the
people.
I
really
trust,
and
that
has
really
helped
me
to
get
out
of
feeling
stuck
yeah.
A
A
B
Or
your
involvement
in
that
project
or
their
involvement
in
that
project,
yeah,
yeah
and
so
like
being
able
to
find
that-
and
you
know,
have
have
those
few
people
that
you
can
really
rely
on
to
like
reach
back
to
I
think
is
important
and
I
think
the
way
I've
historically
done.
That
has
just
been
be
very
present,
be
very
communicative
and
that's
my
communication
style
I
know
not
everyone's
communication
style.
Is
that
way,
but,
like
I,
think
just
generally
being
present
and
there
yeah.
A
B
A
really
good
way
and
like
it's
really
easy
to
think.
Oh,
like
this
person
hates
me
or,
like
you
know,
there's
some
some
issue
there
and
just
kind
of
trying
to
step
out
of
that
that
self
self
reflection
of
like
how
your
you're
kind
of
you
know
being
perceived
by
other
people
when
you
don't
know
that
that's
a
another
big
one.
For
me,
too,
yeah.
B
A
B
B
A
B
C
C
All
humans
and
we're
only
talking
true
text
and
I,
think
we
all
know
the
feeling
when
you're
typing,
with
an
emotion
and
you're
typing
harder,
that's
by
the
way,
a
very
good
time
to
step
away
from
your
keyboard.
I
agree:
yes,
but
there
are
going
to
be
misunderstandings
and
we're
all
going
to
be
different
peoples
and
some
communities.
Maybe
there
are
people
that
aren't
that
nice
to
beginners
it
it
happens
and
it's
important
to
think
it's.
Never
personal.
A
A
A
C
A
C
Like
you,
don't
have
to
please
everyone
and
not
other,
not
everyone's
gonna
be
friendly
and
that's
okay,
yeah
and
basically
it's
their
loss
and
it's
okay
to
make
mistakes
and
I
did
that
once
I
I
made
a
module
for
Powershell
I
thought:
oh,
the
world
needs
this
module.
Yeah
and
I
published
it
and
I
made
a
blog
post
and
it
turned
out.
It
existed
already
yeah
and
it
was
huge
already.
It
was
like
how
did
I
miss
this
okay
and
I
thought?
C
C
A
B
A
B
A
B
B
Exactly
yeah
and
I
think
that's
that's
the
biggest
thing
is
it's
okay
to
mess
up
as
long
as
you
learn
something
from
it
right,
messing
up
and
not
learning
something
from
it.
Isn't:
okay
like
and
that's
like
where
you
you
should
try
to
either
like
you
know,
there's
a
bunch
of
things
to
do
in
that
situation,
but
I
think
if
you're
always
learning
from
your
mistakes.
B
That's
that's
like
the
progress
in
open
source,
yeah
and
like
even
outside
of
code
I've,
like
learned
a
lot
about
myself
and
like
been
able
to
become
a
better
Communicator
because
of
Open
Source,
and
maybe
not
everyone
will
have
that
experience.
But
you
know
that's
that
constant
self-reflection
and
like
mistakes
being.
Okay
is
a
really
big
thing
that
has
helped
me
over.
You
know
almost
a
decade
now,
yeah.
A
C
Doesn't
come
and
we
sometimes
have
to
remember
and
I'm,
conscious
of
that,
like
I
know,
we
are
direct
and
other
cultures
might
think
different
of
that
right,
and
you
know
there
are
some
cultures
who
will
like
almost
apologize
for
existing
when
they
ask
you
something
yeah,
yeah
and
stuff
like
that,
is
really
good
to
be
aware
of
some
things
being
cultural,
but
how
cool
is
that
that
we
can
collaborate
with
stuff
all
over
the
world?
Yeah
yeah
I.
A
Mean
it's
awesome
yeah.
That
was
something
I
learned
at
Mozilla.
It's
people
in
I
think
especially
India.
They
would
ask
for
permission
before
they
jumped
in
and
we
were.
We
were
ignoring
those
questions
because
they're
like
oh,
this
isn't
like
a
real
question
about
the
code.
They
can
just
jump
in,
but
they
cut
different
cultures.
You
need
to
approach
them
a
little
bit
differently.
If
you're
trying
to
collaborate,
yeah.
B
Exactly
and
that
that
actually
is
a
really
big
one
that
I
wish
I
had
learned
more
about
there's
this
kind
of
concept
of
like
ask
culture
versus
guest
culture.
Are
you
familiar
with
this
yeah
I
yeah?
That's.
That
was
a
hard
one
to
learn
about,
because
just
because,
like
I'm
a
certain
way
in
that
and
like
it's,
a
really
good
concept
that,
like
oh
people,
actually
do
like
interact
differently
than
I'm,
expecting
them
to
because
it's
how
they
don't
interact,
how
I
interact
yeah
so
yeah,
that's
another
one.
Definitely
go!
A
C
A
C
Can
create
issues
to
let
people
know
that
you
have
find
something
or
suggest
a
future
you're
already
contributing.
Then
you
can
check
the
code,
you
can
check
the
documentation,
you
can
even
check
for
typos
in
the
documentation
and
fix
those,
because
they
are
there.
Oh
yeah,
and
it
will
be
a
way
to
get
in.
Another
thing
you
can
do
is
write
blog
posts
about
a
product
or
give
talks
at
user
groups
or
organize
user
groups.