►
From YouTube: Keynote: Open Open Source and Making Great Places for Col... Joe Sepi, Michael Dawson, & Beth Griggs
Description
Keynote: Open Open Source and Making Great Places for Collaboration - Joe Sepi, Open Source Engineer & Advcoate, IBM; Michael Dawson, Node.js lead for IBM and Red Hat; Beth Griggs, Senior Software Engineer, Red Hat
The Node.js project is often seen as an example for Open Source projects and we’ve learned a lot over the last 5 years about how an “Open” Open source project works. The goal is to build places where both individuals and companies can come together to make impactful technical, organizational, and community contributions. Come learn about some of the core concepts and principles behind open communities and governance and how we are applying these to help grow the OpenJS Foundation. What’s more we want your help, find out how you can get involved!
A
C
And
I'm
michael
dawson,
I'm
the
node.js
lead
for
red
hat
and
ibm.
That
means
I
get
to
spend
a
lot
of
my
time
working
in
the
community,
various
working
groups,
the
technical
steering
committee,
but
it
also
means
I
get
to
work
with
great
teams
within
red
hat
and
ibm,
and
people
like
joe
and
bethany
in
the
work
that
we
do
for
the
node.js
in
the
node.js
space.
C
A
C
Yeah,
certainly
that
transparency
and
and
the
work
that
we
do
to
make
sure
that
you
know
anybody
can
come
to
the
project
and
work
on
that
level.
Playing
field
is,
is
sort
of
a
key
component.
It's
it's
that
if
I'm
invested
in
in
node-
and
I
want
to
depend
on
it,
you
know
me
as
an
individual
and
certainly
organizations
want
to
have
confidence
that
they
can.
C
You
know,
get
involved
and
move
the
sticks
forward
in
the
areas
that
are
important
to
them,
and
you
know
that
open,
open
source
approach
allows
everybody
to
kind
of
work
on
the
different
areas
that
they
think
are
important
and
have
the
whole
project
move
forward
much
faster
than
you
know.
I
think
projects
that
are
driven
by
a
single
company,
because
there's
only
so
much
that
one
person
can
kind
of
stick
into
their
head
and
keep
on
top
of,
and
this
sort
of
distributed
approach
really
lets
us
us
move.
B
Yeah,
I
I
certainly
think
that's
probably
one
of
the
most
surprising
things
people
find
about
the
node.js
project.
Is
that
because
we
are
open,
open
source
and
everyone
comes
in
with
their
own
ideas,
we
don't
have
a
roadmap,
we
do
have
initiatives
and
ideas
and
plans
rough
plans
in
place
within
the
working
groups
about
what
we
might
like
to
do.
But
there
is
no.
C
Yeah
and
certainly
what
seems
to
come
out,
you
know
what
comes
out
in
a
release
is
what
people
have
decided
is
important
and
worked
on,
and
it's
sort
of
an
amalgamation
of
that
all
across
the
way,
and
you
mentioned
we
don't
have
you
know
a
defined
roadmap
that
doesn't
mean
we
don't
have
plans
and
goals
and
things
that
we
think
are
important.
We,
you
know
the
working
groups
and
teams
are,
are
bring
together,
people
who
are
working
on
areas
that
are
of
interest
to
them.
B
B
You
can
find
the
calendar
and
just
join
them,
and-
and
I
think
people
do
find
that
surprising-
they
need
to
know
that
the
project's
open
in
that
way
for
anyone
to
turn
up
and
join,
and
that
does
come
with
the
challenge
of
making
people
feel
comfortable
and-
and
we
have
worked
hard
to
try
and
lower
the
barrier
to
entry.
So
people
are
comfortable
in
doing
that.
C
Yeah,
I
know
I
often
get
that
question
like
well.
How
do
I
join
the
meeting
and
the
answer
is:
there's
a
zoom
link.
You
can
show
up.
You
can
participate
just
like
everybody
else,
but
sort
of
making
sure
people
are
comfortable
and
then
comfortable
to
speak
up.
You
know
is
an
ongoing
effort
within
the
the
project
and
then
similarly
sort
of
you
know
people
being
comfortable
that
they
could
lead
a
particular
area.
So
you
know
the
the
project.
C
We
have
some
really
good
experience
in
node
core,
but
it
actually
covers
a
a
very
broad
range.
So
people
can
come
to
the
project
and
have
some
domain
experience,
which
is
really
really
useful
and
in
fact
they
may
know
more
about
that
particular
area
than
anybody
in
the
project
and
making
them
feel
comfortable
enough
to
to
bring
that
experience
and
share
it.
Is
you
know
one
of
the
things
that
we
need
to
continually
sort
of
work
on
and
remind
people
that
they
can?
They
can
do
that.
B
One
of
the
things
that
worked
well
within
the
release
working
group,
which
was
one
of
the
working
groups,
I'm
particularly
active
in,
is
we
set
up
some
mentoring
sessions
and
so
in
the
calendar
we
blocked
off
an
hour
every
couple
of
weeks
where
anyone
who
had
an
interest
of
joining
the
release,
working
group
and
maybe
eventually
producing
helping
to
produce
the
releases
of
node,
could
join
and
just
shadow.
The
process
ask
questions,
learn
about
how
they
can
pick
it
up
and
pick
up
a
release,
and
we
found
that
worked
really
well.
B
I
think
we
onboarded
around
about
three
three
new
releases
from
those
sessions,
and
it's
not
it's
not
an
easy
task
to
grasp.
It's
not
something
you
can
just
like
read
a
doc
and
then
get
on
with
it,
and
so
I
think
it
was
really
valuable.
It
was
really
great
to
get
new
people
into
the
project
and
help
out.
A
C
Yeah
yeah
and
that
that's
something
where
you
know
that
helped
them
feel
comfortable
to
come
in
and
work
with
us
and
know.
They'd
have
people
who
would
talk
to
them,
and
it.
It
makes
me
think
that
you
know
we
try
and
do
everything
in
github
as
much
as
we
can
to
be
transparent
to
let
people
participate
across
the
time
zones.
But
at
least
for
me
that
that
sort
of
personal
touch
of
being
able
to
talk
to
people
sometimes
is
invaluable.
C
A
C
In
the
end
it
I'll
admit
it
can
be
quite
tiring,
and
you
know
we,
you
know
that's
one
of
our
challenges
is:
how
do
we
find
the
right
balance
here,
because
we
don't
want
people
to
be
so
exhausted
from
the
discussions
that
they
don't
want
to
contribute
anymore,
but
at
the
same
time
you
know,
I
think
we
need
to
not
rush.
Some
of
these
discussions,
because
we
we
need
to
get
everybody's
input
and
see
if
we
can
find
something
where,
where
there
is
a
consensus.
A
Yeah,
I
think
balance
is
the
key
word
there
for
sure,
and
I
think
you
know
in
terms
of
getting
people's
input.
A
good
example
is
the
the
surveys
work
that
we've
been
doing.
You
know
with
with
the
next
10
effort
and
the
unhandled
promise
rejection
work.
Those
are
really
great
ways
to
get
people's
input.
B
And
the
project's
structured
in
a
way
that
when
it
comes
to
it,
we
have
the
technical
steering
committee
that
can
vote
on
particular
issues.
Topics
pr's,
where
consensus
hasn't
been
able
to
be
met
for
for
a
significant
portion
of
time,
but
the
we
do
try
to
avoid
that.
We
hope
that
consensus
can
be
resolved
out
in
the
community
amongst
the
wider
collaborator
contributed
base,
rather
than
being
elevated,
to
seek
to
make
a
decision,
but
obviously,
in
some
cases,
if
it's
gone
on
for
a
few
months,
you
do
want
that
kind
of
escape
hatch.
A
Yeah
consensus
can
be
challenging,
but
I
think
it's
it's
it's
definitely
a
feature
and-
and
you
know,
when
we
merged
the
two
foundations
together,
the
js
foundation
and
the
nodejs
foundation
to
form
the
openjs
foundation.
We
took
a
lot
of
the
learnings
that
we
had
in
you
know:
building
this
open,
open
source
space
in
the
node.js
foundation
and
tried
to
bring
that
over
to
the
open.js
foundation,
which
I
think
you
know
has
has
been
successful.
C
Yeah,
I
think
I
think
it
you
know,
and
one
of
the
reasons
why
that
makes
so
much
sense
is
that
the
project,
the
node.js
experience
it
embodies
a
lot
of
those
things
that
are
important
for
individuals
and
companies
who
want
to
rely
on.
You
know,
packages
and
products
and
projects
in
their
production
environments.
It
has
that
you
know
sort
of
open
and
level
playing
field
where
you
know,
if
you,
if
you
come
and
you
can
contribute,
you
can
move
things
forward.
C
Your
voice
is
heard.
We
take
everybody's
views
into
into
the
consensus
versus
you
know.
If
you
have
a
project
which
is
predominantly
run
say
from
by
your
competitor,
you
may
not
be
nearly
as
comfortable
as
depending
on
that,
as
as
one
that
would
be
under
this
kind
of
model,
and
the
opengs
foundation
is
a
great
place
to
sort
of
foster
that
experience,
because
if
you,
if
you
move
from,
say
a
single
company,
you
know
supporting
the
open
source
project.
C
You
need
somebody
else,
some
other
organization
to
step
in
and
take
up
some
of
the
pieces
that
they
would
have
done.
You
know
providing
the
things
like
zoom
accounts
and
emailing
lists
and
just
sort
of
the
basic
resources
that
are
available
within
a
company
but
aren't
necessarily
freely
available
to
an
open
source
project
unless
they're
part
of
a
foundation
or
something
like
that.
A
Yeah,
I
agree
it's
like
it's
a
single
home,
for
you
know
the
js
ecosystem
to
be.
You
know
stable
and
you
know
growing
well,
you
know,
and
especially
for
companies
who
want
to
support
that
work.
But,
like
you
said
it's
it's
it's
a
place
to
grow
that
work
as
well
to
have
the
support
from
the
foundation
to
do
things
like
the
surveys,
the
package,
maintenance,
work
and
and
there's
you
know,
there's
there's
so
much
stuff
that
we
can
do
to
really
support
the
community
at
the
foundation
level.
C
Yeah
and
the
other
thing,
I'm
I'm
kind
of
excited
about
I'll
just
quickly.
Mention
is
like
the
collaboration
spaces,
so
the
foundation
you
know
from
the
beginning
has
supported
projects
and
collaboration.
Spaces
are
another
way
where
we
can
support
discussions,
initiatives
which
are
not
necessarily
a
project
but
are
also
very
important
to
the
ecosystem.
The
java
eco
ecosystem
overall.
A
Yeah
we
can.
We
can
talk
a
moment
too
about
like
why
why
people
get
involved,
and
I
think
you
know
that
that
collaboration
space
is
a
great
place
to
get
involved.
But,
like
you
know
you
in
my
experience,
working
at
companies
that
use
open
source,
you
know
you
want
to
get
involved
in
the
project
and
help
you
know
fix
bugs
keep
things
stable.
You
may
need
features.
You
know
there
are
so
many
different
reasons
why
you
would
want
to
get
involved
in
open
source.
C
A
B
C
Yeah-
and
I
guess
in
terms
of
the
risk
is
like,
I
often
see
issues
which
are
like
hey
I'm
having
this
problem
and
then
you
can
see.
People
are
getting
frustrated
in
those
issues
because
somebody
doesn't
immediately
answer
them
but,
like
the
reality,
is
you're
using
a
project
you're,
not
paying
anybody
to
support
you
for
that
project.
C
So
if
people
are
helping
you
that's
because
you
know
they're
volunteering
their
time,
they
think
it's
in
the
project's
overall
best
interest,
but
you
shouldn't
depend
on
somebody
else
necessarily
being
able
to
to
have
that
time
for
you
when
you
need
it
and
by
letting
your
employees
in
be
involved
and
help
maintain
the
things
you
depend
on.
You
can
help
yourself
and
that's
really
the
position
you
want
to
be
in
you
know
to
either
work
with
a
partner
who
will
help
you
or
to
to
be
able
to
help
yourself
in
those
projects.
C
A
Yeah,
I
think
too,
you
know
at
like
a
personal
level.
You
you
gain
amazing
skills
in
working
in
open
source
that
are
valuable
to
a
company
being
able
to
work
well
with
others
and
and
find
consensus
and-
and
you
know,
work
through
certain
issues
that
come
up
often
in
open
source.
It's
definitely
a
skill
to
to
appreciate,
and
then
also
you
know,
it's
a
great
place
to
hire
too
a
previous
company
I
worked
at.
B
C
Certainly,
the
skills
that
you
grow,
you
learn
in
an
open
source
project,
apply
to
working
in
a
larger
company,
at
least
where
you
know
you're
trying
to
get
things
done.
You
don't
can't
necessarily
tell
what
people
what
to
do
and
you
have
to
work
together
in
a
collaborative
manner.
I
mean
I
think
it
you
got
to
do
that
in
every
in
any
kind
of
company,
so
they're
really
great
skills
to
learn.
B
C
B
B
You
should
be
able
to
stream
on
youtube
going
back
to
the
open,
open
source
and
we
try
to
stream
all
of
our
meetings.
So
all
of
our
decisions
are
there
for
everyone
to
see
and
yeah.
So
everyone's
welcome
to
join
the
meetings.
Joining
events
like
him,
js
world
is
just
a
few
ways
you
can
get
involved.
C
Yeah,
I
I,
as
we
said
before,
it's
a
great
way
to
make
the
personal
connection,
those
teams
and
working
groups.
The
other
thing
I'd
recommend
is
like
try
and
you
know,
work
within
your
company
to
get
them
to
actually
support
your
work,
to
make
it
more
than
just
your
side
job,
because
you
know
we're
lucky,
you
know
ibm
and
red
hat
are
very
supportive.
It's
part
of
you
know
we
have
a
portion
of
our
time
to
work
in
the
community
and
that
actually
makes
it
a
lot
easier
to
to
to
contribute.
C
So
you
know
working
within
the
company
to
help
them
understand
that
you're
actually
reducing
their
risk
and
that
you,
you
know,
you'll,
be
there
to
help.
You
know
fix
issues,
identify
issues
in
some
of
these
key
components.
That
they're,
depending
on,
I
think
is,
is
also
a
good
component
in
terms
of
like
how
to
be
able
to
contribute
in
a
more
sustained
and
sort
of
long-term,
long-term
manner.
A
A
But
you
know
we
to
kind
of
get
back
to
the
whole,
open,
open
source
thing
and
to
just
sort
of
reiterate
what
beth
was
saying
as
well
like
there
are.
There
are
lots
of
ways
to
get
involved
again.
You
know
issues
pull
requests.
Openjsf.Org
collaborate
will
give
you
a
bunch
of
resources
in
terms
of
joining
the
slack
and
and
the
calendar
nodejs.org
calendar
is
where
all
the
node.js
calendar
lives.
A
C
I
guess
at
this
point:
that's
probably
all
the
time
that
we
have
thanks
to
for
coming
and
watching
our
keynote.
Hopefully
we've,
given
you
a
little
bit
of
insight
into
you,
know
the
the
open
open
source
approach
that
the
node.js
project
has
some
of
the
the
things
that
are
going
on
and
and
have
sort
of
inspired
you
to
get
involved.
If
you're
not
not
involved
already-
and
you
know,
we
hope
to
see
you
in
github
and
across
the
projects.