►
From YouTube: All Are Welcome Here: Creating an Inclusive Hyperledger Community - Swetha Repakula & Tracy Kuhrt
Description
All Are Welcome Here: Creating an Inclusive Hyperledger Community - Swetha Repakula, IBM & Tracy Kuhrt, Accenture
The phrase “All Are Welcome Here” is a common message heard around Hyperledger events, meetings, and other community interactions. However, how does the community ensure and fulfill that promise?Hyperledger’s community is not a single entity and is comprised of many smaller groups that form around WGs, SIGs, and projects. With so many groups, meetings, mailing lists how can community leaders effectively create an inclusive and civil environment to cultivate a diverse community? This session will go through the best practices for conducting meetings, writing code reviews and enabling asynchronous collaboration to create an inclusive environment. Though focused on Hyperledger tools, these skills can apply broadly to any open source project.
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerGlobalForum2020 #Blockchain
A
We
Tracy
and
I
are
part
of
the
newly
formed
I
guess
not
as
newly
formed,
but
the
diversity
civility
and
inclusion
group
we've
been
talking
a
lot
about
what
it
means
to
create
that
environment
in
that
community
and
out
of
it,
we
kind
of
wanted
to
share
our
thoughts
on
this
and
also
kind
of
get
some
feedback
from
you
guys,
because
you're
all
here
and
in
the
room
and
hand
it
off
to
Tracy.
Oh
wait,
no
I'm!
A
First
sorry,
oh,
my
name
is
swetha
I'm
an
open
source
contributor
for
IBM
I
am
lucky
to
say
that
my
entire
career
still
in
the
short
end
right
now,
but
has
been
an
open
source,
so
I
used
to
work
on
Cloud
Foundry.
If
you're
familiar
with
that
Linux
Foundation
project
and
about
the
last
two
and
a
half
years,
I've
been
working
on
hyper
ledger
fabric.
You've
probably
seen
me
in
some
of
the
Boro
fabric.
A
Integration
kind
of
conversations
the
last
six
months
been
working
on
fabric
private
chain
code,
which
they
have
a
couple
sessions
after
this,
so
go
check.
Those
out
I'm.
Currently,
a
TSC
member
worked
as
or
been
a
hyper
ledger
ambassador
for
the
last
couple
years,
yeah
so
I'm
involved.
You
see
me
around
in
the
community
I'll
hand
it
over
to
that.
Alright.
B
Thank
you,
sir
alright.
So
my
name
is
Tracy
Kurt
and
I've
been
working
with
hyper
ledger
since
2015
when
I
worked
at
PayPal,
so
I
have
basically
been
an
individual
contributor
engineer
architect,
whatever
you
want
to
call
me
all
my
life,
so
I
have
a
background
in
compilers
and
assemblers.
That's
kind
of
I
think
the
first
thing.
That's
on
that
my
career
list
there
of
microchip
technology's
I
worked
for
PayPal
for
10
years.
B
That's
where
I
got
interested
in
the
blockchain
space
and
then
I
moved
to
hyper
ledger,
because
I
really
was
very
interested
in
being
part
of
the
blockchain
technology
space,
and
so
I
worked
for
the
Linux
Foundation
as
a
community
architect
for
Hyper
Ledger.
Just
over
a
year
ago,
now
I
moved
to
Accenture,
where
I'm
working
hands-on
as
a
senior
technical
architect
doing
blockchain
projects.
I
am
a
hyper
ledger,
lab
Stewart.
So
if
you're
interested
in
submitting
a
lab-
or
you
have
already
submitted
a
lab-
thank
you
for
that.
B
But
if
you're
interested
in
submitting
and
have
some
questions,
please
let
me
know
and
I
like
sweet
that
I'm
a
technical
steering
committee
member.
If
you
need
to
contact
me
on
Rocket
chat,
I
still
do
hang
out
there.
So
I
have
a
window
open
all
the
time
you
can
always
contact
me
at
T,
Kirk,
alright,
so
back
in
December
of
2018
Dan
brought
to
us.
This
idea
of
all
are
welcome
in
the
hyper
ledger
committee.
B
It
was
something
that
started
in
a
minute
Minneapolis
at
a
bike,
store,
I,
guess
we're
in
a
coffee
shop
right
where
you
guys
actually
spent
a
lot
of
time
getting
coffee
working
on
Sawtooth
and
those
sorts
of
things
and
really
bought
it
brought
it
into
hyper
ledger.
So
this
idea
of
all
of
you
can
come
in
and
contribute
to
any
of
the
hyper
ledger
projects
in
the
hyper
ledger
labs
and
be
part
of
this
larger
community.
B
B
So
what
does
this
talk
about?
This
talk
is
about
inclusion
right,
and
so
we
use
these
words,
diversity
civility
inclusion.
What
does
this
really
mean?
So
I
thought
I'd
go,
look
these
up
in
the
dictionary
and
see
what
it
actually
had
to
say
for
us.
So
the
first
thing
I
looked
up
was
inclusive,
and
so
this
means
including
everyone.
Well,
it
seems
a
bit
circular
right
because
it
has
the
include
in
it
like
okay.
What
does
it
mean
to
include
so
it
means
to
take
in
or
comprise
as
part
of
the
whole
group
all
right.
B
So
this
is
including
everyone
taking
in
and
including
all
of
you
as
this
larger
hyper
ledger
community,
and
so
that's.
What
we're
here
to
talk
about
today
is
how
did
we
go
about
creating
this?
How
can
we
continue
to
create
an
inclusive
environment
within
hyper
ledger?
The
reason
it's
so
important
is
because
people
do
not
stay
in
the
community
unless
they
feel
empowered,
engaged
and
included
right.
B
So
the
very
first
thing
that
we're
going
to
do
is
we're
gonna.
Have
you
take
a
survey
for
us
what
it
was
the
very
first
interaction
that
you
had
with
the
community?
So
if
you
wouldn't
mind
pulling
out
your
phones
or
your
devices
like
I'll,
ask
you
to
put
them
away
afterwards,
but
just
for
a
moment,
if
you
wouldn't
mind
humoring
me
and
taking
this
survey.
B
B
C
B
Just
do
all
right,
so
I
can't
read
this
because
again,
it's
very
small
but
I
like
the
fact
that
most
of
us
were
encouraged
to
get
more
involved
in
the
community.
I'm.
Very
sad
that
there
are
a
few
entries
here
that
are
discouraged
me
from
wanting
to
continue
to
stay
involved
and
with
you
out
there
here,
but
I'll
have
to
say
maybe
one
of
my
first
interactions
wasn't
so
great
either
and
I'm
still
here.
B
So
if
you
have
a
challenge
that
you
need
to
talk
to
swetha
and
I
about
afterwards
we're
more
than
happy
to
hear
about
what
happened
now,
I
have
to
try
and
figure
out
how
to
get
back
to
the
presentation
which
I'm,
assuming
is
second
pen,
all
right,
all
right.
So
the
first
tip
that
we
have
is
documentation
so
as
developers
we
all
hate
to
write
documentation.
It's
the
very
last
thing
that
we
want
to
do.
B
The
problem
is
the
documentation
happens
to
be
the
point
at
which
many
people
actually
start
to
get
involved
with
your
projects.
It's
the
one
place
that
they
go
where
they
can
ask
a
question.
Hopefully
did
it
answer
without
actually
having
to
talk
to
anybody
else,
all
right
as
developers
I
would
prefer
to
talk
to
my
computer,
then
I
would
prefer
to
talk
to
it
individual.
Now.
That's
not
true
I'm
here.
Obviously,
but
you
know
this
is
this
is
an
important
aspect.
B
So
obviously
we
need
to
make
sure
that
we're
answering
those
questions,
because
the
more
questions
you
can
answer
through
your
documentation,
the
more
time
you
actually
have
to
spend
on
the
sorts
of
things
that
you
want
to
spend
time
on,
be
that
writing
code
or
whatever
the
thing
is
that
most
interests
you
right
so
make
sure
that
you're
keeping
the
documentation
up
to
date.
It
doesn't
do
anybody
any
good
to
come
into
a
document
attempt
to
do
something
and
it
doesn't
work.
B
That's
the
easiest
way
for
somebody
to
go.
Maybe
I'll
find
another
project
to
work
on,
make
sure
that
you're
updating
your
documentation,
based
on
the
sorts
of
questions
that
you
received
the
most
right
and
if
you
think,
hey
I,
get
this
question
all
the
time
and
it's
already
in
my
documentation.
Maybe
you
need
to
figure
out
what's
wrong
with
your
documentation
that
it's
not
answering
the
question:
is
there
not
a
good
search,
that's
available?
Is
there
now
good
pointers
to
that
sort
of
information?
B
You
know
creating
an
FAQ
is
very
useful
because
you
can
point
them
directly
to
where
those
questions
are
answered
in
your
documents,
creating
tutorials
right.
So
the
very
first
thing
that
people
want
to
do
me,
including
it
right
when
I,
want
to
learn
something
new
as
I
go
I
said:
let's
write
some
code
and
try
this
out.
B
If
I
don't
have
a
tutorial
that
makes
it
a
bit
more
difficult
right,
so
creating
tutorials
that
will
walk
people
through
the
process
of
installing
right
the
process
of
actually
getting
something
up
and
running.
That's
very
important,
and
then
one
thing
I
noticed
is
that
we
do
have
some
links
in
our
documents,
but
don't
actually
work,
click
on
a
link,
and
it
says
a
404
I,
don't
know
what
the
heck
you're
asking
me
to
do.
B
I
can't
find
that
that's
a
problem
because
I
obviously
clicked
on
that
link,
because
I
thought
it
would
give
me
the
answer.
I
was
looking
for
whoop
I
think
we
jumped
really
far
there
alright.
So
as
people
like
we
saw,
29%
of
the
people
went
out
to
chat
as
their
very
first
interaction
for
me
personally
and
for
a
lot
of
people.
I
know
that
it's
very,
very
difficult
to
put
yourself
out
there
and
chat.
Ask
that
question.
Alright.
B
If
you
put
yourself
out
there
on
chat,
you
ask
a
question
and
you
hear
crickets
well:
okay,
maybe
I'll
go
find
some
other
project
that
I
want
to
work
on
right.
If
you
are
that
person
who's.
Writing
that
question
make
sure
that
you're
providing
as
much
details
school
right
I,
saw
a
question
on
chat.
The
other
day
that
was
the
performance,
was
not
what
I
expected.
B
B
It
was
Wednesday
I,
don't
know
right
that
that
doesn't
give
the
person,
on
the
other
end
enough
information
to
answer.
Why?
What
did
you
do?
What
does
your
setup
look
like
provide
as
much
detail
as
you
possibly
can,
because
without
that
detail
that
person,
on
the
other
end,
who
you're
expecting
to
answer
that
question
not
gonna,
be
able
to
answer
it?
B
Some
other
things
that
you
can
do
as
maintainer
zuv
your
project
as
contributors
of
your
project
right
designate,
somebody
who
can
monitor
the
chats
in
the
mailing
list
and
answer
questions
that
people
have,
if
you
do
it
on
a
weekly
rotation
basis
right
this
week.
That's
why
that
is
responsible
for
answering
questions
next
week
marks
responsible
for
answering
questions
right
that
way.
It's
not
always
swetha
who
has
to
go
out
and
answer
these
questions,
and
then
we
do
have
a
chat
bot
within
Rocket
chat
that
we
use
you
and
that
is
open
source.
B
B
Alright,
so
there's
different
sorts
of
audiences
that
we
have
for
our
projects
right,
you
have
the
people
who
might
just
want
to
understand
what
the
project
is.
What
does
it
do?
This
is
a
person
who's
coming
in
a
very
high
level
right,
which
is
why
I
associated
that
with
the
hot-air
balloon
right.
Somebody
coming
in
at
a
very
high
level
just
wants
to
know
what
is
this
project?
Is
it
gonna
meet
my
needs
and
do
what
I
want.
B
B
B
Their
user
journey
is
very,
very
different
and
so
making
sure
that
you're,
taking
into
account
each
of
these
different
types
of
people,
I'm
giving
them
a
path
for
moving
from
that
person
who
just
wanted
to
know
what
the
project
is
just
somebody
who
wants
to
actually
provide
a
new
feature
and
any
way
that
they
come
into
that
journey
if
they
are
in
the
right
spot,
providing
them
ways
to
get
to
the
right
spot.
That's
very
important,
all
right,
so
how
many
people
have
participated
in
any
of
our
community
meetings
in
either
working
groups?
B
Not
so
the
very
first
working
group
I
joined
was
a
working
group
that
I
was
very,
very
interested
in
it
very
much
met
who
I
thought.
I
was
as
an
individual
and
the
very
first
time
I
joined
that
I
did
not
feel
welcome.
I
did
not
feel
like
my
opinions
worth
listening
to.
I
did
not
feel,
like
my
opinions,
mattered,
going
back
to
those
people
who
were
down
at
the
bottom,
who
were
discouraged
by
theirs.
First,
interaction,
right,
I'm,
one
of
those
people.
B
The
only
reason
I
stayed
involved
was
because
one
I
was
working
for
the
Linux
Foundation
I
thought.
I
really
should
stay
involved
in
this
working
group.
But
more
to
the
point,
I
was
very
passionate
about
the
subject.
Right
I
now
have
very
close
relationships
with
people
in
that
working
group,
I,
hope,
I'm
respected
by
people
in
those
working
groups.
I
assume
I
am,
but
you
know,
maybe
I'm
not,
but
it's
very
important
to
recognize
that
people
are
coming
to
working
group
meetings
because
they
care
about
the
topic.
B
People
matter
I've
also
been
in
a
working
group
where
every
time
I
join
that
working
group-
hey
Tracy,
how's
it
going
hey,
Joe
how's
it
going
hey,
wait
there
how's
it
going
right.
Very
first
thing
that
comes
up
with
this
working
group,
given
those
two
different
working
groups,
I
feel
a
lot
more
welcome
in
this
second
working
group,
I
feel
like
they
actually
care.
B
They've
used.
My
name
they've
actually
said
you
know
what
Tracy
it
is.
Okay
for
your
voice
to
be
heard
in
this
working
group
very
important.
The
way
that
you
treat
people-
even
if
you
don't
think
you're,
not
doing
anything
specific
to
that
person
by
ignoring
that
person
and
the
effort
that
they
put
in
to
coming
to
that
working
group,
you've
discouraged
them
from
wanting
to
stay
involved.
B
There's
a
couple
other
ideas
here,
but
I
think
hopefully
that
really
hit
the
point
on
how
important
working
groups
are,
but
other
things
you
can
do
obviously
providing
the
agendas
making
those
agendas
open
so
that
people
know
why
they're
going
to
that
meeting,
they
know,
what's
going
to
be
discussed
same
as
any
meeting
that
you
would
have
in
any
sort
of
business
environment
right
without
an
agenda.
What
are
you
covering
make
sure
that
you
give
the
opportunity
for
those
new
people
to
have
a
voice
and
to
talk
and
then
provide
context?
B
I
can't
make
it
to
every
single
working
group
meeting,
because
I
have
conflicts.
So
if
I
come
back
to
a
working
group,
that
I've
been
involved
in
before
I
may
have
lost
some
context,
so
make
sure
you
provide
kind
of
the
background
of
what's
happened.
Why
did
we
get
here?
How
did
we
get
here?
Why
are
we
even
talking
about
this
all
right?
B
So
my
last
tip
before
we
get
to
swetha
tips,
is
that
we
do
have
these
tools
and
these
tools
have
ways
in
which
you
can
point
people
to
certain
information,
so
in
rocket
chat
at
the
very
top
of
every
rocket
chat
channel.
Usually
what
we
have
is
something
that
I
probably
put
in
there,
which
is
what
is
the
topic
of
this
particular
chat.
A
So
I
think
Tracy
covered
a
lot
of
the
things
that
made
me
feel
very
welcomed
into
this
community.
My
first
interaction
into
hyper
Ledger
was
one
of
the
hack
fests
in
Amsterdam
and
I
came
in
I
had
been
working
on
hyper
Ledger
for
two
weeks.
At
that
point
and
I
remember
telling
if
you
guys
have
met
Chris
Faris
I
was
telling
Chris
another
member
or
another
colleague
Jay
who
works
out
of
China.
He's
part
of
the
China
working
group,
I
told
both
of
them.
A
I
said:
I,
don't
know
why
I'm
going
to
this
I,
don't
know
anyone
I,
don't
know
the
technology.
What's
the
point
I
went
to
that
hackfest
and
do
I
see
him
just
before.
Ok,
if
you
guys
haven't
met
Silas
I
recommend
meeting
him.
He
works
on
the
burro
project.
He
does
not
work
on
fabric,
which
is
what
I
was
there
to
kind
of
discuss
I.
He
made
me
feel
at
so
much
ease,
I.
Think
I,
ask
stupid
questions.
A
I
told
him
I,
don't
understand
why
this
isn't
running
and
he
took
the
time
to
help
me
and
I,
probably
haven't
directly
contributed
to
burro
we've
had
discussions.
We
share
bugs
amongst
each
other,
but
that
kind
of
collaboration
was
there
because
he
was
open
to
investing
some
time
in
me
and
in
the
same
way,
he
was
also
open
to
contributions
in
many
different
ways
and
that
I
think
is
kind
of
the
theme
that
I
want
to
talk
about.
How
can
we
actually
be
open?
How
do
we
make
our
projects
open
for
contributions?
A
So
the
first
we
have
one
last
survey
question
on
the
spot
kind
of
question
which
which
of
the
projects.
So
when
you
get
on
the
list
there
should
be
a
list
of
projects.
What
have
you
contributed
to
and
participated
in
and
I
believe
it's
a
select
all
or
multiple,
so
go
ahead,
just
to
kind
of
see
how
much
involvement
you
guys
have
been
able
to
have
with
the
community
in
the
projects.
A
A
The
one
thing
is
those
collaboration
tools
is
kind
of
where
we're
want
people
to
kind
of
work
together,
collaborate
talk
to
each
other,
and
hopefully
some
of
the
things
I
discuss
will
help.
So
that
way.
Yes,
we
do
want
our
code.
We
all
are
very
interested
I
mean
even
for
me,
I,
like
writing
code
over
answering
questions
or
writing
documentation,
but
we
in
the
end
to
achieve
better
projects,
better
code,
more
ideas.
We
need
to
make
sure
we
can
start
using
the
rest
of
the
kind
of
options.
C
A
So
I'm
gonna
talk
about
documentation,
we've
already
mentioned
it
once,
but
I
think
documentation
is
important
enough
that
it's
worth
mentioning
again.
So
we
talked
to
kind
of
about
answering
questions
and
making
sure
people.
This
is
your
first
step
in
to
the
project
or
into
the
you
know
the
working
group,
whatever
piece
of
the
community,
that
you're
kind
of
running
in
terms
of
projects
and
contributions.
This
is
a
good
place
to
have
your
contribution
guide.
That
could
be.
You
know
the
type
of
stylistic
things
that
you're
expecting
you
can
mention
there.
A
These
are
the
types
of
tests
that
we
look
for.
This
is
the
process
and
Tracy
also
kind
of
mentioned
that
they're
different
kinds
of
people
who
are
interested
in
contributing.
So
that
means
people
who
are
looking
for
bug
fixes
or
want
to
help
you
fixing
bugs
they
probably
have
a
different
process.
They
have
to
go
through
to
get
their
bug,
fix
and
versus
somebody
who
has
a
new
feature
that
they
want
to
do,
and
all
of
those
different
processes
should
be
documented
in
a
very
clear
and
easy
way
to
understand.
A
One
of
the
really
big
ones
is
becoming
maintainer,
I'll,
be
honest,
I,
don't
know
how
many
of
our
projects
really
clearly
say
right
up
there
on
that
readme
and
said
this
is
the
this:
is
the
process
to
become
a
maintainer
on
this
project?
These
are
things
to
show,
because
when
you
have
new
people
who
come
in,
they
want
to
know
that
there
is
a
path
for
them
to
achieve
their
goals
and
I.
Think
documentation
is
the
best
way
to
do
it.
A
Otherwise,
you're
going
to
be
answering
the
question
many
many
times,
yeah,
the
other
thing
is
think
about
it.
As
from
a
developer
standpoint,
when
I
kind
of
join
a
project,
the
first
thing
I
want
to
do
is
download
the
repository.
I
want
to
start
it
up
and
I
want
to
be
able
to
run
the
code.
I
want
to
do
a
tutorial
so
having
those
startup
tutorials
is
really
helpful.
The
other
thing
that
I've
noticed,
though,
is
every
developer.
Environment
is
different.
I.
A
If
I
close
this
and
bring
up
my
terminal,
you
will
see
I
have
a
tons
of
shortcuts
and
different
kind
of
aliases.
That
I
have
that
make
my
job
easier,
but
at
the
same
time,
if,
for
example,
Tracy
pulls
up
her
terminal,
it's
not
going
to
look
anything
like
mine,
so
it's
mine,
you
have
to
be
mindful
of
those
differences.
What
are
your
dependencies?
What
are
the
absolute
requirements?
You
need
to
run
your
project.
One
helpful
thing
that
I've
noticed
is
provide
some
developer,
docker
environments.
A
A
Similarly,
you
know
some
of
those
development
scripts
that
we
maintain
on
our
own
push.
Those
up.
If
they're
helpful
to
you
they're,
probably
helpful
to
someone
else
and
then
the
last
thing
that
I
have
here
is
use,
make
files
or
different
targets,
whether
that's
to
make
building
easy
testing
easy
running,
basic
checks
and
again
back
to
the
documentation.
Point
talk
about
that.
These
are
the
things
they're.
These
are
the
tools
they're.
A
It
makes
it
easier
for
someone
who's
trying
to
make
a
PR
because
they
know
how
to
go
through
the
process,
this
one
architect,
design
and
developed
transparently.
This
is
one
that
I
feel
very
very
strongly
about.
I
have
seen
in
different
open
source
projects.
They
approach
this
very
differently,
so
I'm
going
to
talk
a
little
bit
about
my
experience
on
Cloud
Foundry
here,
so
it's
not
directly
related,
but
I.
Think
it'll
give
you
why
I
feel
really
strongly
about
this
Cloud
Foundry
is
a
very
in
person
kind
of
a
development
project.
A
It's
not
that
they
are
not
open
to
contributions,
but
they
expect
you
to
go
in
at
certain
hours
every
day
and
work
on
teams
like
actual
teams.
It's
not
very
easy
to
move
from
one
team
to
another
and
it's
a
totally
different
process,
but
what
it
does
is
it
makes
it
really
hard
for
someone
who
is
not
in
that
team's
time
zone
to
participate.
A
So
there
was,
you
know
my
time.
My
flexibility
was
dictated
purely
by
based
on
that
team.
The
other
thing
I
noticed
is
because
a
lot
of
the
development
was
done
in
person.
We
didn't
put
anything
online
and
it's
an
oversight.
It's
not
intentional,
but
if
you
don't
put
your
decisions
online,
that
means
anybody
who
wasn't
in
the
room
in
that
on
that
day
no
longer
has
the
context
that
those
people
had
and
they
can't
really
participate
so
kind
of
moving
to
hyper
ledger.
I.
Think
hyper.
A
Ledger
is
a
lot
more
globally
cognizant
of
the
situation,
so
I
do
think
we
do
try.
We
try
to
keep
phone
calls
I'm
from
the
West
Coast,
so
these
phone
calls
are
usually
very
early
for
me
and
it
makes
it
hard
for
me
to
participate
sometimes.
But
I
do
appreciate
that
you
know
we
have
recordings
so
I
suggest
for
people
who
run
these
meetings
record
the
meetings
that
you
have
put
them
up
on
the
wiki
page.
We
have
them
there
for
a
reason.
A
Put
your
agendas
up.
There
put
your
notes
up
there.
So
people
can
have
references,
they
know
what
recordings
they
want
to,
listen
to
because
just
having
them
out
there.
It
doesn't
help
if
I
have
to
listen
to
everything,
to
find
out
the
five
minute
that
I'm
actually
interested
in
the
other
thing
is,
as
I
mentioned,
some
of
the
time
zones
we
have
people
who
are
operating
from
the
different
sides
of
the
world
and
making
decisions
on
phone
calls
isn't
always
the
best
policy,
mostly
because
not
everyone
could
have
joined.
A
So
it's
a
great
place
to
kind
of
force.
Discussion
maybe
talk
through
a
lot
of
details,
but
what
would
be
really
helpful
is
if
there
is
a
decision
or
you're
leaning
towards
a
destination,
make
that
something
that
is
asynchronous
people
can
vote
and
put
their
opinions
on
that
on
the
wiki
page
or
the
mailing
list.
These
are
really
good
places
to
have
discussions.
A
phone
call
every
week
so
be
cognizant
of
that,
and
the
last
thing,
I
would
say
is
a
lot
of
us
are
not
the
only
ones
from
our
companies
who
are
working
at
these
projects.
It's
very
tempting
to
just
walk
next
door
or
two
to
the
person.
Next
to
you
and
have
discussions,
it's
ok
to
have
those
discussions,
but
put
it
back
online.
I
can't
stress
that
enough,
the
so
what
this
is,
the
last
kind
of
bigger
spiel
I
have
and
the
rest
of
them
are
a
little
simpler
but
being
inclusive
maintainer.
A
So
I
was
talking
about
my
experience
into
hyper
ledger
and
how
Sylas
someone
as
I
said,
was
not
working
on
fabric.
Does
not
work
for
IBM
made
me
feel
included
in
this
because
he
took
time
to
invest
in
me.
So,
similarly
to
the
maintainer
is
out
there.
The
leaders
out
there
think
about
those
new
contributors
who
are
come
and
take
time
to
invest
in
them.
They
might
ask
you
some
questions
that
you
think
are
very
simple
or
obvious,
but
take
time
to
understand
and
teach
them,
because
in
the
long
run
you
want
more
contributors.
A
You
want
the
workload
that
you're
doing
to
reduce,
and
to
do
that,
you
need
to
trust
your
new
contributors.
You
need
to
have
trust
that
they
have
the
skills
and
the
best
way
to
do
that
is
to
help
them
gain
it.
If
they
don't
have
it
I
think
if
you
go
online,
we
do
have
this
slide
deck
up.
There
are.
There
are
links
at
the
very
end
that
you
can
click.
A
One
of
them
is
a
link
to
linus
torvalds,
one
of
his
interviews,
and
he
kind
of
talks
about
this
process
and
I
think
it's
very
indicative.
It's
not
specific
to
being
inclusive
or
creating
a
community,
but
I
think
what
he
says
is
kind
of
what
all
of
us
should
hope,
as
maintainer
Zoar
leaders,
what
we
want
for
our
community,
a
couple
of
more
concrete
things
to
say
as
maintainer
when
you're
doing
reviews
be
clear
and
polite.
A
If
you
don't
want
to
accept
the
pull
request,
just
say
that
I
think
trying
to
beat
around
the
bush
waste
both
people's
time.
And
you
know
if
it's
not
in
your
roadmap.
It's
not
in
your
roadmap.
You
are
the
maintainer.
That
is
your
kind
of
decision
point
that
you're
allowed
to
make
and
I.
Think
please
and
thank
yous
also
go
a
long
way
saying.
A
Thank
you
for
your
contribution
when
I
see
that
it
makes
me
feel
good
and
regardless
of
whether
they
tore
up
my
PR
or
not
at
least
I
know
they
appreciate
the
time
I
spent
on
it,
saying
that
provides
some
timely
reviews
and
merge
on
time.
I
would
say
this
is
a
fault
of
mine
as
well
I
get
distracted
by
the
code
I'm
working
on,
and
maybe
not
as
good
about
providing
reviews,
but
try
to
reduce
the
time.
A
It's
kind
of
a
similar
thing
of
reducing
the
time
between
a
question
going
unanswered,
simple
things
that
you
could
do
if
you
don't
have.
The
time
is
mentioned
that
say:
I
don't
have
the
time
to
look
into
this
now.
I
am
interested.
I
am
NOT
interested
or
give
some
quick
kind
of
thing.
So
whoever
contributed
has
an
idea.
A
So
I
think
communication
is
key
here
and
try
to
just
be
quick
reduced
in
different
amount
of
time
between
each
of
these
conversations
that
need
to
happen,
and
then
it
should
be
the
last
one.
There
is
both
this
new
and
I
really
like
this,
both
github
and
JIRA.
We
have
labels,
that's
a
good
first
issue
so
for
your
projects,
there's
usually
a
lot
of
simple
tasks
that
are
maybe
a
lower
priority,
but
good
starting
issues.
You
might
have
tasks.
A
That
kind
of
you
think
would
teach
you
about
the
project
and
things
like
that:
labeled
them
github
I,
think
all
of
our
projects
are
now
on
github
too.
So,
if
you
have
your
issue
tracker
on
github,
the
nice
thing
is
github
itself
has
like
a
list
of
things
that
you
can
just
click
on
that
label
and
it
looks
through
everything
not
just
hyper
ledger,
so
I'm
just
talking
about
open
source
in
general
here,
but
I
think
this
is
a
really
great
tip.
A
Usually
this
is
how
I
direct
anyone
who
comes
in
I
say
pick
a
component
pick
a
project
that
you
like
and
look
for
this.
So
I
think
this
is
a
great
thing
and
now
I
kind
of
want
to
turn
it
over
to
the
audience.
I
guess
we
can
kind
of
do
this
in
two
ways:
it'd
be
great
if
there
are
any
tips
that
you
guys
would
like
to
share
we'd
like
to
take
those
and
then
also
any
questions.
E
A
A
B
Right,
let
go
so.
The
point
was
for
those
of
you
who
didn't
hear
it
right
open
an
issue,
even
if
you
think
that
you
want
to
contribute
a
PR
open
the
issue
first,
because
somebody
else
may
already
be
looking
at
this,
and
you
don't
want
to
waste
your
time
right
and
you
would.
It
would
be
better
to
collaborate
with
that
person
than
to
spend
a
bunch
of
time
when
somebody
else
is
already
spending
their
time
on
it,
and
you
guys
end
up
going
in
two
different
directions.
B
D
E
A
C
E
A
A
So
definitely
this
is
our
chat,
our
mailing
list.
This
is
our
wiki
page
I
realize
if
you
go
to
that
wiki
page.
Most
of
all
of
our
links
and
resources
are
right
there,
including
when
we
meet
how
we
try
to
meet.
One
thing
we
have
been
trying
to
do
is
virtual
meetings.
I
won't
say
that
they
have
been
100%
successful,
but
we're
working
towards
that.
So
definitely
come
contact
us
talk
to
us.
We
want
to
hear
how
we
can
help
essentially.
A
Okay,
yeah
I
will
say
we
did
create
a
survey
with
the
goal
being
to
collect
some
data
to
understand
the
community.
The
response
rate
has
not
been
great,
so
I
asked
that
all
of
you,
since
you
are
here,
you
have
definitely
participated
in
a
hyper
ledger
event.
Please
take
the
survey,
give
us
your
opinions.
There
is
also
an
open-ended
textbox
for
you.
If
you
have
specific
events,
things
that
you
want
to
talk
about,
we
also
have
all
are
welcome
here,
pins.
There
is
a
slight
caveat
to
getting
one
of
these
pins.
A
A
Ethnicity,
that's
not
what
I'm
asking,
but
you
could
take
one
of
the
tips
that
we've
mentioned
and
you
can
say
I'm
going
to
work
on
that
I'm,
going
to
give
timely
reviews,
I'm
going
to
make
sure
I
say
hi
to
everyone
on
the
phone
call
in
the
mornings
or
whenever
it's
whenever
the
phone
call
is
small
tips
like
that,
and
then
we'll
give
you
a
pin-
and
this
is
our
hope
we
can
make
people
start
thinking
about
how
we
make
our
community
inclusive
and
I.
Think
that's
it.
Thank
you.