►
Description
Becca Zandstein, Product Management, GitHub
Learn how the whole team—from engineers, both experienced folks and newcomers, to those in other departments— can collaborate effectively. Tune into this session to learn how to collaborate on GitHub and ensure transparency in the decision-making process throughout your community.
GitHub Satellite: A community connected by code
On May 6th, we threw a free virtual event featuring developers working together on the world’s software, announcements from the GitHub team, and inspiring performances by artists who code.
More information: https://githubsatellite.com
Schedule: https://githubsatellite.com/schedule/
A
But
before
we
get
into
the
next
fake
up,
I'd
like
to
do
a
big
shout
out
and
thank
you
to
all
our
mazing
sponsors
now,
as
we
said
before,
this
is
a
first
figure
of
the
first
ever
live
virtual
only
event.
So
thank
you
to
all.
Our
sponsors
have
been
absolutely
amazing,
providing
help
and
resources
to
get
this
off
the
ground
so
but
century
circle,
CI
insta
bug
Pony
code,
Microsoft
Azure,
a
new
current.
A
B
Not
coming
to
me
Steph,
it's
not
going
to
you!
It's
not
going
in
that.
It's
not
going
to
Satya.
Every
single
dollar
goes
towards
the
kovat
19
relief
effort,
but
there's
more
for
every
dollar
that's
been
contributed
by
our
sponsors.
Github
is
matching
that
so
I
mean
it's
I'm.
Pretty
proud
of
I've
always
been
proud
to
work
for
github,
but
the
fact
that
all
of
the
money
is
going
towards
helping
the
cove
in
19
relief
effort,
I
mean
it's
it's
a
very
proud
day
for
me,
I'm
feeling
pretty
excited
to
work
here.
A
Just
I
love
they
ever
wire
for
company
that
not
only
cares
about
its
employees
like
we
got
lots
of
what
we
get,
which
is
nice,
but
they
care
about
the
communities.
They're
part
of
right
and
I
think
is
yes.
It
is
so
amazing
to
work
for
a
company
like
that
and
I
just
feel
so
incredibly
proud
to
work
them
and
I.
Thank
them
so
much
for,
like
all
the
sponsors,
as
well
as
github,
for
providing
all
that
money
to
go
to
the
Kogan
19
relief.
A
B
A
A
B
You
so
very
much.
This
is
one
of
my
favorite
people,
so
she
is
a
world
traveler
traveler
and
also
focuses
on
helping
developers.
Collaborate
as
a
community
on
github
she's,
a
senior
product
manager
here
at
github,
and
the
name
of
her
talk
is
taking
collaboration
beyond
the
code
and
get
up.
Please
help
me
welcome
the
wonderful
Becca's,
an
stained.
C
C
It's
called
discussions
by
the
way
I'm
super
excited
to
be
working
on
a
product
that
helps
communities,
connect
and
grow
while
working
with
communities
on
this
feature,
the
entire
time
I've
learned
so
much
about
how
unique
these
communities
truly
are
and
I'm
excited
to
really
be
bringing
a
lot
of
those
learnings
back
to
you
tonight,
all
right.
So
how
about
we
get
this
started
and
talk
about
community
and
collaboration,
which
is
really
what
us.
C
Github
is
an
interconnected
community
of
developers,
specifically
yura
does
at
its
core
and
what
I'd
like
to
do
for
the
next
few
minutes
here
is
to
take
you
into
the
future
of
what
another
similar
interconnected
community
looks
like.
So
we
can
apply
some
of
those
learnings
back
into
how
we
can
build
communities
on
github.
C
C
Well,
we
have
more
than
humanoids
there
with
great
abilities,
and
while
it's
true
that
the
folks
in
Star
Trek
are
doing
amazing
feats
with
code
I'm,
not
entirely
convinced
that
they
make
it
as
accessible
as
the
maintainer
is
on
github.
The
barrier
to
entry
on
Star
Trek
is
a
bit
high.
I
mean
they
do
have
to
go
to
school,
for
it
after
all,
and
maintainer
is
on
github.
C
Do
a
phenomenal
job
making
sure
to
lower
that
barrier
where
possible,
thanks
to
the
help
of
bots
automation
and
even
actions,
it's
possible
to
extend
the
growth
in
your
community,
whether
that's
on
github
or
on
the
Star
Trek
Enterprise
I
can
say
for
sure
that
BOTS
and
some
level
of
automation
alleviates
a
lot
of
the
manual
work
that
people
would
rather
not
be
doing.
And
when
you
have
so
many
humans
in
a
community.
C
Collaborating
I
have
to
say
that,
with
the
upcoming
release
of
code
spaces
alone,
we
have
a
lot
more
in
common
with
Star
Trek
and
the
ways
that
we
can
easily
interface
with
code.
Just
like
Star
Trek
were
in
a
remote
first
culture
right
now
and
that's
at
the
core
of
what
github
is
and
what
github
enables.
But
Star
Trek
might
have
been
leaving
the
path
here
and
from
code
scanning
depend
about
security,
advisories
and
so
much
more
I.
C
Think
it's
fair
to
say
that
our
suite
of
security
products
stack
up
to
the
strength
and
coverage
from
the
security
team
on
the
US
on
USS
Enterprise
vessel,
namely
Worf,
and
how
could
I
not
talk
about
data
both
github
and
Star?
Trek
are
great
examples
of
communities
that
have
built
amazing
features
with
the
troves
of
data
that
one
can
access
and
build
on
top
of
securely,
so,
whether
it's
50
million
developers
or
an
interstellar
collection
of
more
than
a
hundred
and
fifty
planets
both
have
one
thing
in
common
at
its
core.
It's
an
interconnected
community.
C
C
Ok,
so
now
that
we've
created
a
little
bit
of
a
more
detailed
framing
around
what
communities
and
collaboration
could
look
like
both
on
github
and
in
some
alternate
reality
of
science
fiction,
that
I
really
need
to
let
go
of
I
know
I
get
it.
Let's
talk
about
what
it
really
means
to
start
grow
and
sustain
communities
on
github
as
well
as
some
really
really
awesome
examples
that
so
many
communities
are
using
right
now
to
help
them
meet
their
community's
needs.
C
So,
to
start
a
community
there's
a
lot
that
you
need
to
do
and
to
be
aware
of,
but
thankfully
there's
tons
of
great
examples
and
documentation
for
how
you
could
get
started.
There's
two
things
that
are
worth
noting,
though,
before
we
get
started
on
this
on
this
phase
number
one.
No
assumptions
are
safe,
so
you
need
to
spell
things
out
clearly,
even
if
you
think
that
it's
super
obvious
to
you
and
number
two
just
don't
get
attached
to
whatever
you
start,
because
it's
bound
to
change
as
your
community
will
over
time
as
well.
C
C
But
welcoming
newcomers
is
such
a
seemingly
small
task
and
it's
a
meaningful
part
of
starting
a
community.
Let's
take
electrons,
for
example,
they
use
a
bot
to
welcome
newcomers
when
their
first
issue
is
opened.
This
allows
them
to
welcome
the
newcomer,
allow
them
to
remind
them
of
exactly
what
the
guidelines
are
and
tell
them
how
to
contribute
into
the
community.
C
Electron
also
has
an
example
of
an
onboarding
guide,
and
so
this
repository
allows
all
newcomers
to
have
a
really
easy
place
to
go
and
get
learning
resources
for
getting
more
familiar
with
the
electron
codebase
and
its
dependencies.
Great
examples
of
how
you
might
want
to
consider
welcoming
newcomers
into
your
community.
C
Another
way
to
make
sure
that
you
can
set
up
your
community
for
success
on
github
is
to
make
sure
that
your
community
always
knows
where
to
go
for
support.
No
js'
does
this
by
having
a
really
clear
list
of
table
of
contents
in
there
me
so
folks
can
quickly
dive
into
sections
that
they
need
more
information
on
specifically
where
to
go
if
they
need
help.
No
js'
also
has
a
collection
of
resources
on
their
website,
so
that
people
who
want
to
get
involved
beyond
the
code
can
do
that.
C
The
processing
foundation,
which
powers
the
p5.js
project,
for
example,
is
one
of
my
most
favorite
examples
for
a
community
that
is
specifically
built
to
welcome
newcomers
and
be
more
accessible
and
inclusive,
as
well
as
inspiring
creativity
with
coding.
The
p5.js
project
has
a
section
in
their
readme
dedicated
exclusively
to
learning
resources,
which
includes
an
absolutely
magical
trove
of
tutorials
from
dan
Schiffman
called
the
coding
train
they're
great,
and
you
should
definitely
definitely
check
it
out
after
this.
C
If
you,
if
you
have
the
time
for
newcomers,
specifically
looking
to
contribute
to
your
project,
good
first
issues
is
a
really
great
way
to
enabling
newcomers
to
easily
find
issues
that
you
have
deemed
suitable
for
a
first-time
contributor
on
a
project
and
by
using
the
good
first
issue
label
you're,
not
only
welcoming
newcomers
into
your
project,
but
you're
opening
the
door
for
so
many
more
and
we're
gonna
go
through
a
few
examples
of
how
that's
the
case.
So,
first
of
all,
there's
a
contribute
view
that
a
lot
of
people
don't
know
about
and
I
know.
C
This
exact
example
was
shared
earlier
today
on
twitter
by
the
nodejs
community
too.
So
I'm
super
excited
that
a
lot
of
people
are
finding
out
about
it.
But
this
contribute
view
is
something
that
you
all
you're
able
to
see
here
are
good,
first
issues
and
it's
right
next
to
the
contributing
guidelines
which
is
really
great
and
welcoming
for
newcomers.
Second,
when
you
use
the
good
first
issue
label,
you
make
it
easy
for
others
who
are
not
yet
familiar
with
your
project
to
find
those
issues
when
they're
browsing
the
topics
associated
with
your
repository.
C
So,
if
you're
also
not
using
topics
associated
with
your
repository,
I'd
highly
recommend
going
to
do
that
last,
but
certainly,
not
least,
for
those
who
use
github
comm,
slash
Explorer.
They
will
now
see
recommendations
for
good,
first
issues,
soap,
so
consider
using
it,
because
more
people
who
use
that
feed
will
have
those
personalized
recommendations
on
github.com,
slash
explore
moving
forward.
C
Something
else
that
the
nodejs
community
does
to
welcome
newcomers
and
set
them
up
for
success
is
providing
a
mentor
for
select
issues.
These
issues
are
not
as
common
but
when
they
are
opened,
there's
a
mentor
available
like
Anna
here
who
helps
the
potential
assignee
walk
through
their
approach
and
reviews,
open,
pull,
requests
this
process
for
allowing
a
mentor
to
be
available
allows
Anna
and
the
node
community
to
onboard
the
contributor
into
the
community
firsthand.
C
Now
we're
ready
to
go
through
the
growth
stage
and
what
that
might
look
like
for
your
community
as
it
continues
to
expand
and
change
over
time.
Each
of
these
steps.
In
the
process
is
super
critical,
both
the
start
growing,
which
is
where
we're
at
right
now
and
sustaining
but
I'll,
admit
I'm,
particularly
jazzed
about
this.
Since
we'll
cover
a
few
examples
of
discussions,
as
mentioned
in
the
keynote
earlier,
discussions
is
a
new
space
for
your
community
to
connect.
C
Newcomers
need
a
safe
space
to
ask
questions
and
community
members
also
want
a
way
to
share
their
work
and
recognize
what
others
have
done
to
help
them
out.
Maintainer
x'
also
need
a
way
to
announce,
changes,
receive
feedback
and
discuss
upcoming
releases.
All
of
this
and
more
will
be
possible
to
do
in
the
discussion
space
as
we've
been
iterating
on
discussions
the
past
few
months.
C
These
two
examples
are
for
BOTS
called
trap
and
roller
which
help
the
contributors
be
more
efficient
with
their
tasks
specifically
for
back
porting
and
updating
dependencies,
so
a
ruler,
for
example,
automates
the
process
of
updating
the
dependencies,
an
electron,
namely
chromium
in
node,
while
trap,
helps
automate
the
process
of
back
porting
features
and
bug
fixes
and
to
sustain
a
community
growth.
All
of
the
contributions
within
the
community
need
to
be
recognized.
So
thanks
to
the
all
contributors
bot,
it's
possible
to
create
a
way
to
publicly
recognize
and
reward
contributions
that
go
beyond
code.
C
The
p5.js
project
has
done
this
to
recognize
the
work
that
all
contributors
do
outside
of
issues
and
pull
requests,
because
there
really
is
so
much
work
that
community
members
are
doing
to
get
all
of
that
work
done
on
github
today
within
a
project
and
discussions
are
just
the
start
of
extending
the
contribution
graph
in
a
way.
That's
more
representative
lowers
the
barrier
to
entry
for
newcomers
and
elevates
the
value
of
work
for
so
many
folks
and
communities
that
they're
doing
right
now
that
we
need
to
be
recognizing
more
publicly.
C
That's
something
that
you
feel
your
community
could
utilize,
instead
of
giving
them
just
a
good
first
issue
and
with
the
use
of
discussions
growing
your
community
and
what
they
can
more
easily
access
and
be
a
part
of
as
possible.
So
again,
if
you're
curious
about
discussions,
let
me
know-
and
we're
also
excited
to
be
showing
you
that
later
this
summer,
for
your
open
source
communities
and,
last
but
not
least,
to
sustain
community
growth,
consider
using
automation,
that's
already
available
to
you.
So
many
communities
have
made
these
available
and
you
should
consider
checking
them
out
here.
C
All
of
those
projects
were
listed
on
the
right
hand,
side
so
yeah
for
all
the
communities
that
I've
referenced.
In
today's
talk,
they
can
be
visited
on
github
to
see
how
they
have
personally
grown
their
communities
on
github
to
date,
and
with
that
I'd
like
to
invite
you
to
ask
us
any
questions
that
you
might
have
in
our
discussion.
We're
super
excited
to
have
more
updates
coming
this
summer
on
discussions,
the
product
and
with
that
I'd
like
to
hear
what
questions
you
might
have
thanks
for
coming
tonight,.
A
B
B
B
A
B
C
Question,
yes,
we
have
been
getting
feedback
for
a
few
months
now,
since
we
first
launched
as
a
limited
beta
with
next
day
s
and
ever
since
then,
we've
been
onboarding
communities.
We're
currently
up
to
around
60
I,
believe
I
announced
in
the
keynote
today,
and
the
feedback
has
been
super
positive
and
super
honest.
So
we've
definitely
made
a
lot
of
changes.
C
B
A
B
So
the
next
one
is
so
obviously
right
now,
a
lot
of
conversations
and
discussions
have
been
happening
on
issues
for
four
years
on
github.
So
what
if
people
want
to
take
like
how
do
look
for
those
issues
that
are
already
created
like
what's
the
process
to
get
them
into
discussions?
How
do
people
do
that?
That's.
C
Such
a
great
question
Jared,
so
there's
two
ways
right
now:
one
if
you
only
have
a
few
or
someone
just
keeps
bypassing
say
your
templates
and
creating
an
issue
where
you
don't
want
it
on
the
right-hand
sidebar
as
an
admin
or
a
maintainer.
You
can
convert
that
issue
directly
into
a
discussion,
but
the
really
really
cool
part
is
that
you
can
convert
in
bulk
all
of
your
issues
into
a
discussion.
If
it
has
a
certain
label,
so
say
you
have
all
of
your
issues
with
a
labeled
questions.
C
C
Think
that's
a
personal,
a
personal
option
if
you
want
to,
if,
if
that's
your
preference
for
your
community
and
it
works
for
you
you're
more
than
welcome
to
do
that.
But
to
be
honest,
every
community
uses
tooling
in
a
different
way,
so
I'm
sure
one
communities,
usage
of
slack
is
quite
different
than
another.
Wouldn't
be
fair
of
me
to
say
that
anything
is
going
to
replace
another
tool
completely.
A
B
B
B
C
Interesting
drama
I'm,
not
sure
of
the
integration
there
with
code
spaces,
but
yes
to
github.com,
slash
explorer
already
being
available
to
all
of
our
users
on
github,
calm
and
what
it
is
is
more
of
like
a
personalized
feed.
So
you
can
look
based
on
topics
collections
or
even
just
your
own
personal
feed
and
so
based
on
the
types
of
contributions
that
you're
making.
We
can
give
you
different
suggestions
for
what
you
might
want
to
consider
looking
at.
C
B
C
So
I
think
what
they're
asking
is,
whether
or
not
they
can
see
all
of
their
contributions,
which
will
go
from
issues
PRS
as
well
as
discussions,
and
so
that
is
not
yet
available
and
we
are
looking
at
providing
API
endpoints
for
discussions,
and
so
we
definitely
would
have
to
think
on
that
one
a
little
bit
more
and
understand
what
you're
looking
to
do
with
it,
so
that
we
can
build
it
the
right
way.
So
if
you
can
provide
more
details
and
what
you're
hoping
to
do
with
it,
definitely
let
us
back
for.
B
A
C
It's
a
great
question,
so
github
discussions
is
right
where
you
exist
right
now
with
your
code,
which
is
at
the
repository
level,
the
team
discussions
feature
is
not
at
the
repository
level,
it's
based
on
the
team
structure.
So
it's
a
little
bit
it's
in
a
different
location
completely,
so
it
only
teams
can
access
that
if
you're
using
teams
on
github.
A
C
B
Will
there
be
there's
too
many?
Will
there
be?
It
is
for
people
that
are
open
for
different
types
of
projects
in
general,
rather
just
rather
than
just
issues
of
a
given
project,
their
beginning,
okay,
I
see
what
they're
asking.
Let
me
repeat
that
will
there
be
any
type
of
discussion
space
for
people
that
are
open
for
different
types
of
projects
in
general,
rather
just
rather
than
issues
of
agat
of
a
given
project
just
like
Scott,
that's
what
they're
going.
C
Yes,
so
if,
if
I'm
interpreting
the
question
correctly
and
again,
give
me
feedback
in
the
discussion
I'll
be
in
there
shortly
if
I'm
getting
this
wrong,
it's
going
to
be
up
to
you
how
you
use
discussions,
so
the
examples
that
I
showed
you
of
the
categories
is
something
that
we're
hearing
a
lot
of
communities
wanting
to
use
and
already
using.
But
we
don't
expect
that
every
single
community
will
have
discussions
that
necessarily
fit
into
those
categories,
so
some
are
going
to
use
it
just
for
QA.
C
Others
are
going
to
use
it
just
for
things
and
some
prefer
RFC's,
while
others
would
never
use
a
discussion
for
an
RFC
prefer
a
PR.
So
it's
really
going
to
be
up
to
you
how
to
configure
your
community
discussion
space,
and
we
want
to
make
sure
that
we
give
you
the
tools
to
to
do
that
at
the
end
of
the
day.
A
Definitely
well,
discussions
is
a
new
thing.
There's
a
lots
of
questions
coming
through
becca
is
gonna,
be
available
on
discussions,
but
next
half
an
hour
to
answer
all
those
questions
and
discussions.
So
we'll
stay
over
that.
Thank
you
again
so
much
backup
for
all
your
crazy
Star,
Trek
references
and
Topher
knows
all
about
discussions
in
community.
Thank
you.