►
From YouTube: Kubernetes Contributor Experience SIG 20190123
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
To
today's
edition
of
Cooper
no
needs
contributor
experience,
my
name
is
Paris.
I
will
lead
us
into
some
kind
of
awesome
destiny
today,
and
today
is
January.
23Rd
I
did
turn
older
a
few
weeks
ago.
If
anybody
missed
that-
and
today
we
do
have
a.
We
do,
have
a
very
packed
agenda.
I'm
not
gonna
lie,
and
if
you
do
have
something
to
discuss,
please
put
it
on
the
open
mikes
to
class
discussion
list,
and
if
we
don't
get
it
to
get
to
it
today,
we
can
either
take
it
to
a
a
mailing
list.
A
If
you
need
something
immediately
or
B,
we
can
save
it
for
next
week.
First
things:
first,
we
do
have
a
code
of
conduct
that
we
abide
by,
please
be
excellent
to
each
other,
since
we
do
have
a
large
group
on
the
phone
today.
If
you
have
something
to
say
well,
someone
else
is
saying
it.
Please
just
raise
your
hand
and
I
have
the
gallery
view
on
so
I
can
see
your
awesome
avatars
and
faces
also
just
ping
and
chat
too.
A
If
you
have
something
that
you'd
like
to
say-
and
we
can,
we
can
call
on
you
after
someone
takes
a
breath
and
that's
my
spiel
for
how
to
behave.
Maybe
not
now
there
are
some
I
think
there
are
some
new
contributors
on
the
line
right
now
that
have
never
been
on
this
call
before.
If
you
are
one
of
those
individuals
and
would
like
to
give
an
into
a
brief
introduction
of
yourself
now's
the
time,
if
not,
there's
no
pressure
in
doing
so,
but
anybody
want
to
take
a
shot
at
introducing
themselves.
I
will.
B
C
A
E
Is
Ray
yeah
I'm
located
in
New
York
City
East,
Coast
I
work
for
we
work
and
we
are
the
end
user
of
the
comm
Dallas,
actually
helping
with
sick
talks.
The
website
translation
to
Chinese
I'm
from
China
and
I
help
with
the
translation
be
happy
to
join
this
contribution.
Cuz
we
have
a
experience.
This
is
my
first
time
awesome.
A
That
is
great
translation
work,
it's
much
needed!
Thank
you!
So
much
for
all
your
help.
There
that's
awesome
and
last
call
I'm
so
exciting
if
three
on
the
phone.
Look
like
yes,
alright,
if
you
have
not
given
an
intro
previously,
you
can
do
so
at
another
one
or
feel
free
to
put
in
at
any
time.
Alright.
Now
we
are
going
to
our
main
show
just
to
give
context
for
folks
on
the
line.
Who've
never
been
on
a
call
before
we
usually
go
through
our
regular
programs.
Those
are
listed
on
the
agenda.
A
F
F
Doing
that,
while
I
was
gone,
just
the
usual
bit,
wasn't
one
of
the
one
of
the
things
I
I
want
to
fix
her
this
year
for
office
hours
is
in
the
past.
Our
diversity
has
not
been
very
awesome.
That's
like
the
same
four
or
five
people.
I
would
literally
love
to
be
in
a
spot
where
it's
like
Bob.
We
don't
need
you
this
week,
like
don't
actually
don't
show
up.
We
haven't
gotten
to
the
point
where
we
tell
people
not
to
show
up.
F
So
if
you
have
anybody
who's
doing
kubernetes,
you
know
in
production
and
has
that
kind
of
expertise
and
rotate
out.
It's
only
one
hour
a
month.
They
don't
even
have
to
do
it
every
month
they
could
I,
give
them
all
sorts
of
swag
and
stuff.
So
if
you're
looking
for
people
who
don't
know
how
to
give
back
and
just
want
to
answer
user
questions,
I'd
love
to
slaughter
men
but
other
than
that
I
feel
like
the
project's
doing
pretty
good
some
bad.
H
F
Ideally,
what
I
have
three
sessions
a
day
but
I
don't
yet
have
coverage
in
Asia
or
in
Mia
I
I
could,
given
the
volunteers
we
have
Europe
West
Coast
is
the
only
thing
we
can
cover.
I
have
everything
written
down.
All
we
need
is
two
or
three
motivated
people,
and
we
could
just
give
them
everything
that
we
have
to
pull
that
off
in
another
time
zone.
Ideally,
I
would
love
to
have
localized
ones.
If
people
want
to
do
one
in
their
own
native
language
like
we
could
do
all
those
things.
H
It's
my
concern
at
the
moment,
so
I
was
a
panelist
at
last
last
week's
office.
Our
sedation
and
I
heard,
though,
that
we
we
have
enough
questions
there
at
the
same
time
probably
way
like
if
we
don't
have
enough
volunteers
for
the
panel,
and
we
don't
have
enough
like
let's
call
it
technical
diversity.
So
people
with
the
with
the
deaf
technical
experience
who
can
answer
different
technical
question,
and
so
probably
when
my
start
was
the
single
of
his
our
session.
H
F
H
H
F
A
What's
Jen,
what's
the
general
consensus
about
that
like
from
a
meet
our
contributors
like
mentoring,
standpoint,
because
right
now,
we've
on
a
7:30
a.m.
Pacific
and
a
1
p.m.
Pacific,
because
in
the
when
the
luncheon
is
actually
the
lower
of
the
attendance
and
I?
Think
that's
because
it's
in
the
smack-dab
in
the
middle
of
the
workday
yeah.
H
Speaking
from
the
AMIA
time
zone
perspective,
I
would
say
that
meet
up
meet
our
contributors
is
healthier
than
office
hours.
So
we
we
have
the
wider
panel
and
like
enough
people
who
can
answer
questions
so
made
our
interpreters
again.
From
from
my
standpoint
from
a
person
who
attends
the
imitation
is
absolutely
fine.
A
D
Think
I
know
that
there
are
lots
of
people
from
India
who
want
to
contribute
and
who
are
interested
in
attending
the
session.
But
7:30
a.m.
Pacific
time
is
in
your
friendly
I'm,
not
really
sure
if
that's
friendly
for
other
countries
with
China
or
maybe
even
Australia
and
I
am
not
familiar
with
the
level
of
interest.
We
have
there.
Okay,.
A
I
might
play
around
with
it
next
month
on
and
I
might
switch
the
1
p.m.
to
7
p.m.
and
see
what
happens
because
I'm
just
curious
to
see
if
we
can
catch
people
on
like
an
evening
where
they
just
want
to
listen,
sort
of
like
podcast
style,
bolo,
say,
okay
and
for
meet
our
contributors.
I
definitely
still
need
more
volunteers.
We
have
at
least
two
two
slots
for
every
session
from
here
on
out
for
the
rest
of
the
year.
That's
the
same
thing
that
George
said
it's
one
hour
time
commitment.
A
I
A
E
We
have
assumed
I
I,
don't
know
whether
folks
know
we
have
transition
team
from
Korea.
I
didn't
see
Japanese
the
folks
Korean
team
has
some
contribute
to
contribute.
This
show
up,
but
also
keeping
in
mind
is
what
in
Asian
hands
own,
so
they
have
accounted
and
Catholics,
for
they
are
all
meetings.
So
even.
E
A
And
I
know
I
know
now
that
I
think
it's
either
it's
scheduling
or
instrumentation.
That
has
a
super
late
meeting
now
node
has
a
super
late
meeting
now,
there's
I
think
two
other
two
or
three
other
states.
Now
that
have
late
super
late
meetings
to
cater
today
attack
audience
all
right,
so
George
contributor
I
mean
not
contributed
community
meeting
stuff
yep.
F
So
I'm
gonna
plop
the
schedule
there
I
went
ahead
and
schedule
the
community
meeting
and
sync
updates
all
the
way
through
August
and
so
two
things
here,
I
also
penciled
in
where
I
think
the
release
this
next
release.
Retro
is
so
we
can
move
that
so
I
shared
this
with
a
cig
leads
in
their
list
and
on
their
channel.
So
basically
they
should
theoretically
know
when
they're
giving
their
cig
status
updates
on
thirty
days.
In
reality,
they
never
do
so.
F
One
thing
we're
asking
hosts
and
what
I've
been
doing
is
reminding
them
ahead
of
time
and
doing
all
this
kind
of
stuff,
but
on
column
a
should
seem
hosts.
We
are
looking
for
more
people
to
host
the
meeting,
so
it's
not
just
Paris
Josh
and
I.
So
if
you
want
to
commit
starting
with
next
week,
feel
free
to
just
add
your
line
there,
if
you're
interested
in
the
hosting
you're,
literally
just
following
the
agenda,
it's
not
it
kind
of
work.
The
meetings
almost
sort
of
runs
itself.
F
That's
my
way
of
convincing
you
that
it's
not
that
hard
to
do
and
if
you
ever
need
help
I'm
always
available
to
help.
You
out,
you
get
lost,
so
if
you
want
to
help
facilitate
the
meeting,
it's
a
lot
of
fun
I
like
to
equate
it
as
like
hosting
Saturday
Night
Live.
But
no
one
believes
me
so,
if
you're
looking
to
to
host
a
meeting
there,
it
is
I've
left
enough
slots
there
as
well,
that
are
empty.
F
A
George
all
right
now
we
will
typically
go
into
actually
no
I
did
add
something
to
our
regular
programs
list.
One
thing
that
we
have
started
to
do
is
every
week:
I
need
to
know
email
for
all
of
the
chairs
and
tech
leads.
That's
like.
Oh,
it's
over
a
hundred
people
we're
doing
this
in
hopes
to
bubble
up
communication
that
we
think
is
super
important,
and
then
they
can
disseminate
this
information
to
their
weekly
meeting
some
of
these
people
of
thousands
of
members
and
their
SIG's.
So
it's
important
that
they
water
down
the
information
as
well.
A
So
we
give
them
nuggets
every
week
of
info
like
three
to
four
nuggets
Furyk's.
For
example,
last
week's
nugget
was
hey.
The
maintainer
truck
survey
went
out
for
cube
con,
don't
forget
to
sign
up
for
an
intro
or
a
deep
dive.
Also,
please
do
your
YouTube
videos
manually,
the
automation,
broke,
etc,
etc.
So,
if
anybody
has
any
tips
that
they
think
we
need
to
convey
to
the
chairs
for
tech
leads
this
week,
please
add
them
to
the
dock.
For
instance,
I'm
going
to
tell
them
about
the
meet
our
contributors
on
February,
7th
I'm
gonna.
A
Ask
them
for
Mentors
we're
gonna
tell
them
that
they
should
create
roles
which
that's
something
that
we
should
also
talk
about
as
well,
but
things
like
project
manager,
issue,
triage
captain,
a
new
new
contributor,
ambassador
they're,
creating
new
opportunities
for
people
in
their
sake.
So
that's
what
the
that
need-to-know
email
is
about
and
why
you'll
see
that
from
now
on
on
the
regular
program
list,
and
so
again
this
is
just
a
way
for
us
to
spider
out
communications,
two
chairs
and
tech
leads.
Does
anybody
have
any
questions
about
that.
A
A
Let's
do
this
all
right,
so
our
lovely
project
board
also
I,
want
to
show
you
this
as
well
is
I
also
want
us
to
borough
of
the
culture
where
we're
Duke
we're
filing
issues
again,
if
you're
working
on
something
for
contributor
experience
right
now-
and
it's
not
reflected
on
this-
it
should
be
so
that
we
can
get
better
at
tracking
exactly
what's
going
on
within
our
crew.
So
I
just
want
to
talk
about
anything,
that's
blocked.
Does
anybody
have
anything
that
is
blocked
right
now,
that's
not
showing
on
this
list.
A
So
what
I
like
to
hear
yeah
we're
blocked
still
with
MIT,
with
one-on-one
mentoring,
process
stuff,
because
calendar
stuck
and
it's
hard
and
then
time
so
we
are
still
blocked
there
and
then
I,
don't
know.
What's
going
on
with
this
sub
project
details
in
SIG's
animal?
What
Aaron
do
you
know
yeah.
A
We're
subscribed
yeah
over
in
the
column
over
subscribed
so
and
then
our
backlog
is
super
d2
these.
This
is
just
people
that
this
is
stuff
that
has
not
been
picked
up
yet
I,
don't
know
if
we
should
go
through
here
and
decide
if
this
is
blocked
because
of
time
or
if
it's
blocked,
because
no
one
is
picking
it
up,
but
we
need
to
get
this.
Some
of
the
stuff
is
super
old.
We
need
to
figure
it
out,
like
this
release.
Rename
release
note
Aaron
what
the
heck
is
this
about
like
this
is
like,
though,
I.
A
J
A
A
K
M
A
F
I
A
Also,
we
are
trying
to
figure
out
the
zoom
stuff.
I,
don't
really
know,
I.
Think
a
tldr
here
with
the
zoom
stuff
and
for
people
that
need
context
is
that
our
chairs
are
under
administrative
burdens.
I
would
say
that
word
at
this
point,
with
a
lot
of
our
productivity
infrastructure
and
zoom
is
very
heavy
to
administer
from
our
perspective
as
a
user
right
now,
it's
like.
Oh,
my
god.
A
This
is
a
great
product,
but
from
when
you
have
70,
plus
people
that
have
keys
and
licenses
into
this
system,
and
then
you
have
to
like
tell
them
how
to
protect
their
community
and
like
oh,
you
need
to
click
this
one
button,
or
else
this
one
thing
won't
work
that
gets
very
laborious,
especially
with
engineers
who
are
like.
We
just
want
to
click
something
and
talk
to
each
other.
A
So
we've
been
trying
to
figure
out
ways
to
automate
that
process
for
them
and
it
has
been
it's
passed
with
flying
colors
at
a
very
small
level,
but
then,
when
you
get
it
to
a
very
large
level
like
a
cluster
lifecycle,
who
has
nine
projects
sub
projects,
rather
meaning
nine
meetings
a
month?
Excuse
me
a
week
that
gets
a
little
hairy
and
it
just
broke.
So
we
need
to
go
back
to
the
drawing
boards
with
productivity
stuff.
A
So
if
the
productivity
stuff
sounds
interesting
to
you,
come
on
and
talk
to
us,
but
we're
also
doing
moderation
stuff
this
week.
What's
that
mean
like?
We
need
to
increase
our
moderator
pool
by
two
times,
so
there's
a
lot
of
documentation
and
work
that
needs
to
be
done
there
before
we
can
start
recruiting
and
then
we've
got.
Let's
see
what
else
going
on.
We
still
have
a
lot
of
the
communication
stuff
going
on.
You
can.
A
Oh,
that's
great
first
issue
stuff
because
it's
just
a
lot
of
like
research
and
data
points
that
we're
collecting
about
the
communication
stuff
that
we're
doing
that's
right
here
if
you're
interested
in
that
issue
and
then
we're
working
on
still
working
on
closing
out
the
contributor
experience
survey,
but
Don
and
I
are
actually
working
on
some
of
that
data
for
the
contributor
site
strategy.
So
that's,
hopefully
gonna
be
done
here
shortly
as
well
and
a
ton
of
other
stuff.
That's
going
on.
A
Oh
yes
and
contributor
summits,
which
I
know
Quinn,
actually
has
a
question
about
during
open
mic,
but
we
met
with
C&C
f
yesterday
to
talk
about
like
budget
and
kind
of
what
their
goals
are
for
the
event.
It's
everything
that
we
thought
about.
They
said
that
they'll
kind
of
do
whatever
we
want
to
do
and
that
there
was
no
necessarily
budget
number
so,
okay.
A
Now
we
need
to
figure
out
as
a
group
what
that
means.
What
events
were
gonna
run:
the
teams
that
we
need
to
kickoff
for
these
things
and
then
also
set
up
sub
project
meetings
for
this
I.
Don't
necessarily
want
us
to
have
what
I
see
chat
going
I,
don't
necessarily
want
us
to
have
a
lot
of
conversation
about
summits
in
this
meeting,
because
we
have
so
much
else
going
on
this
year.
A
I
would
like
for
us
to
break
off
into
more
sub
project
meetings
like
a
cluster
lifecycle
has
because
this
this
meeting
every
week,
I
think
it's
inundated
and
rundown
with
all
of
the
things
that
we
do,
and
sometimes
we
can
veer
off
into
one
direction.
So
I
think
that
we
should
start
breaking
down
into
little
R
groups.
I
know
like
the
non-code
group
needs
today
and
stuff
like
that,
and
then
we
can
kind
of
report
and
bubble
that
back
up
in.
A
A
Now,
let's
go
right
into
open
mic.
The
first
thing
I
wanted
to
talk
about
today
is
the
style
guide
stuff
to
get
folks
context
when
we
were
building
the
contributor
site
and
George
and
Bob
called
neckla
phi
from
our
community
repo.
We
realized
that
oh
wow,
these
docks
are
either
stale
out-of-date
shouldn't,
probably
be
showing
on
a
contributor
site,
etc,
etc,
and
then
that's
when
we
kind
of
like
regrouped
and
decided
all
right
well,
we
need
a
style
guide
because
the
things
are
gonna
get
displayed
on
the
Internet's.
A
They
should
have
some
kind
of
the
rules
if
you
will
and
those
rules
are
the
style
guide.
So
we
are
pretty
much
forking
what
the
docs
team
has
and
thoughts
gonna
get
into
that
in
a
second,
but
so
that's
kind
of
I
just
want
to
give
some
background.
I
know
we
have
a
lot
of
new
folks
on
the
line
right
now
so
Bob.
Do
you
want
to
kick
it
off
with
what
you've
been
doing
with
the
style
guide
and
feel
free
to
share
your
screen?
Sure.
I
I
Okay,
sort
of
as
Paris
was
saying,
like
sort
of
came
up
because
the
contributor
site
and
essentially
surfaced
a
bunch,
the
issues
that
we
encountered
with
like
no
real,
consistent
formatting
through
a
bunch
of
stuff.
So
this
is
pretty
common.
You
know
when
you
have
multiple
people,
especially
working
on
the
same
document
and
things
get
yard
in
at
various
different
times,
and
you
know
this
is
John.
I
So
with
that
in
mind,
got
work
on
this
sort
are
like.
We
want
to
get
this
like
sort
of
the
door,
especially
for
all
the
work
grains
like
the
developer
guide,
and
so
we
can
have.
You
know
pretty
consistent
formatting
from
the
echo
and
the
stock
itself
is
based
off
the
docs
style
guide
for
gentleman
he's
like
criminais
style,
but
it's
a
bit
more
firm
and
about
all
the
these
other
things
in
there.
There's
and
I
did
this
with
a
little
bit
of
research
into
like
various
tech.
Writing.
I
I'm,
not
an
expert
on
this
stuff
by
any
means,
but
looked
into
tech
right
and
various
tech
writing
and
then,
like
sort
of
the
style
guides
from
will
github,
Microsoft
and
sort
of
pulled
in
like
what
seemed
relevant
along
with
some
of
the
other
work.
That's
been
like
done,
especially
around
like
you
know,
tombstones
and
the
links
will
dive
right
in
so
the
top
parvis
is
just
like
a
cheat
sheet.
I'm
gonna
actually
go
past.
All
this
and
down
to
like
actual
sort
of
rules
or
I
should
say
these
are
all
guidelines.
I
So,
first
and
foremost
will
sort
of
like
be
the
content,
design
format,
actually
yeah
and
design
for
main
language,
so
don't
use
personal
email
addresses
this
is,
you
know,
makes
sense,
use
the
like
cyclical
groups
or
you
know,
community
agrees
io.
Do
we
actually
have
a
full
list
of
all
those,
or
is
that
all
in
the
dock?
For
gathering
all
our
communication
points?
I,
don't
know.
I
Any
case
going
on
just
some
other
stuff,
like
explicitly
with
dates.
There
hasn't
been
a
lot
of
consistency
there
so
and
we
framed
it
like
text
dates,
essentially
try
and
use
this
format,
because
it's
very
readable,
that's
reason.
People
like
especially
from
the
date
same
thing
with
dates.
A
numerical
format
stick
to
ISO
8601
so
year
on
the
day.
J
J
Can
I
just
raise
an
it
on
the
UTC
thing
here?
You're
all
going
to
tell
me
deal
with
it,
but
UTC
doesn't
follow
daylight
savings
time.
There
are
a
number
of
meetings
that
also
make
the
mistake
of
specifying
their
time
in
terms
of
PST
or
EST
or
whatever,
so
they
lock
in
which,
whether
they're
forward
or
backward
into
their
time
zone
there
are
time
zones
you
can
use
that
net,
like
jump
around
with
daylight
savings
time
like
PT
and
ET,
or
the
US
at
least
perhaps
you're
a
pest
something
similar.
J
F
N
O
N
On
that,
I
was
actually
gonna
say.
You
know
this
actually
is
Europe,
because
when
we
jump
around
based
on
US
times
other
people's
time
zones
don't
jump
around
the
same
as
we
do
in
the
United
States
on
the
same
days,
and
so
there's
always
these
overlap
periods
where
our
time
zones
are
jumping
around
different
somebody's
experiencing
a
pain
point
because
of
it.
I
agree.
J
P
H
So
the
first
situation
here
is
to
use
GMT
instead
of
here
DC,
so
GMT
is
still
universal
format,
but
it
follows
that
time.
Zone
changes,
so
GMT,
plus
1
is
actuated
time.
That
right
now
is
on
green,
which
another
and
as
a
note
that,
as
Matt
mentioned
about
one
or
two
weeks,
overlap
between
United
States
time
zone
change
for
the
date,
daylight,
saving
and
European.
K
Just
to
give
you
an
idea,
everyone,
this
is
a
problem.
The
US
military
had
for
a
long
time,
and
they
just
said
nope
we're
all
now
using
UTC
time
deal
with
it.
So
this
is
not
something
people
easily
solve
right,
like
the
only
way
to
solve
this
is
to
make
the
whole
world
go
to
one
time
standard.
Do
you
not
think.
P
A
Right
I'm,
hammering
down
we're
done
with
this
conversation.
If
you
have,
if
you
have
questions
about
this,
there
is
an
open
PR
right
now.
So
let's
get
everybody
to
like
blank
shut
in
the
PR
cool.
All
right
go
ahead!
Bob!
You
got
a
thing.
I
Is
diagrams
images
and
other
assets
right
now,
there's
sort
of
no
standard
convention
of
where
the
stuff
lives?
This
is
just
sort
of
you
know.
My
call
on
and
I'm
welcome
to
other
suggestions
on
dumping
stuff
in
the
same
folder
is
where
the
primary
like
document
is.
The
other
thing
is:
whenever
you
are
doing,
a
diagram
actually
use
the
canaries
icon
set.
We
have
for
everything
I
think
actually
add
Rada
io.
Now
just
has
this
natively
in
their
thing
now,.
A
H
H
I
Next
thing
and
sorry
I'm,
just
sort
of
breezing
through
this
next
thing
is
just
sort
of
standard
document.
Layout
is
only
have
one
sort
of
single
h1
right
at
the
top
or
like.
If
you
it's
a
massive
document,
large
sections,
then
it's
appropriate
again
and
follow
the
hierarchy
of
like
you
know:
h1
h2,
h3
h4,
don't
you
know,
sort
of
jump
around
and
all
that
and
if
the
doctrine
is
pretty
large,
do
include
a
table
of
contents.
A
I
I
think
that
will
probably
be
the
links.
Okay
and
I
know.
We've
we've
talked
about
this
before
I
know.
There's
the
the
I
think
the
link
guide
of
preferring
like
reference
style
links
over
inline
style
links
a
lot
of
scenarios
just
because
it
makes
it
easier
to
read
and
update
the
doc,
especially
if
the
link
is
used
more
than
once.
So,
if
you
pop
I,
go
to
I,
keep.
I
Over
to
like
the
discuss,
that's
here,
you
can
see
like
when
actually
editing
and
working
on
the
document.
Like
that's
a
link
right
there,
that's
just
easier
to
have
inline.
It's
not
shoving
this
text
far
out
away
or
anything
like
that
and
like
there's
several
times
where
I
frank,
like
the
code
of
conduct
multiple
times
and
just
having
that
single
link
at
the
bottom
is
super
handy.
I
The
big
thing
will
be
the
the
the
preference
on
the
line
length,
and
this
is
completely
up
for
debate-
is
I.
Have
everything
here
like
at
80
characters?
Oh
boy,
yeah,
I
I
have
no
real
preference.
I
just
went
with
80
because
that's
sort
of
the
standard
for
a
lot
of
other
things.
I
know
markdown
will
wordwrap,
but
when
it
comes
to,
like
you
know,
trying
to
edit
and
work
on
a
document
like
having
your
limit
is,
you
know
pretty
helpful
if
anyone
is
curious,
github
markdown
is
120
characters
wide.
P
L
A
A
J
A
In
this
stuff,
it
really
does
have
to
do
with
things
that
were
exposing
on
the
internet,
meaning
like
domain.
That's
not
github
all
right.
So
what
action
here
is
for
people
to
respond
on
Bob's
PR?
We
will
keep
it
open
for
the
required
length
to
collect
some
feedback,
so
at
least
72
hours
and
then,
hopefully,
by
next
week
we
will
have
a
merged
style
guide.
Questions
concerns
comments
all
right.
Thank
you!
So
much
George,
oh
yeah,
George,
I'm,
sorry,
I,
didn't
see
you
you're.
A
A
F
A
Yeah,
this
is
kind
of
our
very
first
step
into
this
great
wide
world
of
getting
our
together.
So
alright
and
thank
you
Bob
if
you
want
unshare
now
we're
gonna
go
to
anita,
which
I'm
super
pumped
about
I
need.
Are
you
gonna
share
your
screen
at
all?
If
so,
you
can
just
go
ahead
and
take
it
over
if
not
go
ahead
and
mmm-hmm.
A
C
All
right,
I
have
shared
my
screen.
Can
you
sign
yep
you,
okay
should
I
send
them
go
ahead.
Oh
yeah,
all
right,
hello!
Everyone
thank
you
for
letting
me
speak
to
you.
I'm
Anita,
Sharma
I'm
at
Oregon,
State
University,
so
I'm
a
beaver
as
we
have
been
talking,
but
I
have
a
black
people
situation
at
home,
but
what
we
are
talking
about
today
is
inclusivity
and
whether
the
software
tools
and
technology
itself
that
we
use
can
impact
until
civitate.
So
let's
start
and
I
should
be
presenting
as
like
this.
C
So
what
we
want
to
do
over
here
is
so
like.
How
can
we
reduce
or
remove
biases
that
are
embedded
in
software?
How
do
we
find
those
gender
bias
bugs,
and
the
answer
is
through
a
method
that
we
call
gendermag
method?
It
stands
for
gender
inclusiveness
magnifier,
so
it's
gender
and
man,
but
really,
if
it's
easier
for
you
to
talk
to
others
and
call
it
inclusive
man,
that's
fine
too,
because
what
what
we
are
looking
at
is
it
is
a
process
to
evaluate
your
tool
tools,
inclusiveness
from
the
focus
of
problem-solving.
C
So
if
you
have
an
individual,
a
user
who's
using
an
IDE,
it's
offered
to
any
kind
of
configuration,
they
are
doing
some
kind
of
problem
solving
and
there
are
five
cognitive,
styles
or
cognitive
facets
that
tend
to
cluster
by
gender
and
I'll.
Talk
about
these
five
facets
and
what
gendermag
method
is
asking
to
do
is
if
you
take
a
use
case
or
a
scenario,
and
then
you
walk
through
your
tools
and
say:
would
your
user
have
this
goal
in
mind?
Would
they
take
this
action?
C
Would
they
know
they
have
taken
the
right
action
and
then
you
kind
of
have
a
persona
with
one
of
this
set
of
cognitive
factors
and
then
say:
would
this
person
have
a
problem?
Why
or
why
not?
And
then
you
answer
why
or
why
not
they're
trying
to
pull
in
these
cognitive
fascist
about
how
different
people
are
problem-solve
differently.
Alright,
so
here
are
the
facets,
so
the
gender
back
personas
have
are.
We
have
four
of
them?
We
have
Tim
Abby
and
two
facts.
C
Patrick
and
Patricia
are
twins,
so
they're
interchangeable,
but
Tim
and
Abby
are
at
the
two
ends
of
the
spectrum
with
very
different
cognitive
styles,
and
there
are
fives
are
facets
that
we
have
motivations,
how
information
is
processed
computer
self
confidence,
self
efficacy,
discovered
averseness
and
learning
style
the
interest
of
time
you
won't
go
through
everything,
but
you'll.
Take
one
arm
faster
blue,
take
risk
averseness
and
let's
look
at
a
particular
persona
that
we
have
here
is
a
persona
for
Abby.
You
see
this
gray
line.
On
top
of
the
gray
line.
It's
changeable.
C
You
can
change
the
background
skills.
Whatever
pictures
you
want,
you
know
put
any
pictures,
but
on
the
bottom
is
where
we
have
the
five
facets.
If
you
take
one
of
the
facets
attitude
towards
risk,
it
says
that
a
bee
has
rarely
a
bee.
Rarely
has
any
spare
time
so
she's
risk-averse
about
using
unfamiliar
technology
that
might
need
her
to
spend
extra
time.
So
it's
not
that
I
be
scared
of
technology
or
a
bee
won't
push
a
button.
C
C
Each
of
these
fascinate
have
been
backed
by
at
least
five
independent
empirical
studies,
where
we
found
statistical
differences
in
men's
and
women's
preferred
cognitive
style
here
is
the
risk
averseness.
This
was
a
self-reported
survey
of
men
in
blue
and
women
in
pink
showed
here
and
how
they
self-reported
their
risk.
Tolerance
first
thing
to
note:
is
that
there's
a
lot
of
overlap,
so
it's
not
that
all
men
are
risk
tolerant
at
all,
women
are
discovered.
C
It
is
a
lot
of
overlap,
but
if
we
look
at
the
line,
more
women
than
men
tend
to
be
risk
averse
than
the
opposite
right
and
what
happens
is
we
have
Tim?
Who
is
in
charge
of
looking
out
for
the
risk
averse,
cognitive
facet
for
all
these
people
on
the
left-hand
side?
So
we
have
42%
men
and
25%
limit.
Abi
is
on
the
other
side
and
we
have
the
patch
pads
looking
at
the
middle.
C
So
if
we
are
using
software
or
building
software,
that
is
on
the
left
of
this
black
line
right
because
most
often
we
have
in
software
development
people
of
a
certain
kind
and
most
often
they
are
the
Tim's.
But
if
we
only
work
with
Tim's
facet
and
we
are
leaving
behind
a
lot
of
other
people,
they
are
leaving
behind
about
70%
women
and
50%
men
right.
So
that's
the
thing
to
take
out
from
here.
What
we're
trying
to
get
gendermag
is
about
being
inclusive.
It
is
not
about
essentialism,
it's
not
that
all
men
are
the
same.
C
All
women
are
this
way
and
to
do
that,
we
in
the
person
of
the
pictures
that
showcase
men
and
other
genders
and
other
race
we
recognize
just
like
gender,
is
in
a
spectrum.
What
we
want
to
say
is
we
want
to
support
the
cognitive
style
of
different
people
from
one
end
of
the
spectrum
to
other
end
right.
So,
if
you
make
Abby's
life
easier
and
we
make
things
like
easier,
everyone's
life
is
better
and
easier.
C
It
is
also
dependent
on
individuals.
So
it's
not
that
one
individual
will
have
all
the
cognitive
facets.
That
Abby
has,
for
example.
Here
is
me:
I
am
very
different
than
Abby
in
information
processing
and
tinkering,
but
closer
to
Abby
in
computer
self-efficacy
and
in
attitude
towards
risk.
It
can
also
be
situational.
I
might
be
much
more
risk,
tolerant
if
I
have
just
talking
to
my
students
or
just
in
my
class,
whereas
you
know,
if
I'm,
giving
a
talk
at
a
bigger
place
or
have
a
grant
proposal
do
or
release
do.
C
So
what
does
it
mean
for
open
source
tools
and
technically
civility
in
the
tools?
We
did
a
field
study
with
five
open
source
projects
where
these
teams
looked
at
their
software
their
projects
and
ran
a
gendermag
session
to
identify
where
there
would
be
problems
very
quickly,
since
I
only
had
ten
minutes
or
12
minutes.
To
finish
my
talk
and
I
want
to
leave
there
as
far
ask
me
questions,
so
what
we
did,
we
took
all
the
use
cases.
C
We
had
them
kind
of
walk
through
each
action
and
there
they
found
out
if
there
was
a
problem
that
a
user
would
face
and
remember
we
have
to
ask
like
what
are
you
would
Abby
have
a
problem?
Yes
No,
maybe,
and
why
so
some
of
the
problems
might
be
just
hey:
the
label
is
really
small
or
the
font
size
is
really
small
and
that's
ok,
that's
a
problem,
but
if
it
is
because
of
certain
Abi's
facets
like
information
processing
style,
then
they
mark
it
with
the
facet.
C
And
then
we
collected
all
the
problems
with
those
facets,
and
that
shows
us
the
percentage
of
problems
that
the
teams
found
and
gender
biases
involved
because
they
affected
the
facets
and,
as
you
can
see
here,
you
know
it's
quite
a
bit
of
the
problems.
Had
gender
or
or
discover
a
facet
related
issues.
Here
is
an
example.
This
is
about
how
Abby
likes
to
process
information.
She
likes
to
get
comprehensive
information.
C
Processing
statue
likes
to
get
all
the
information
before
starting
on
a
task,
and
here
one
of
the
participants
says:
hey
like
the
way
the
resources
are
organized
in
this
website
is
counterproductive.
To
the
way
Abby
likes
to
learn
should
get
lost
our
rabbit
hole
of
finding
information
trying
to
get
all
gangsta.
C
Another
Casey
is
here
to
actually
find
what
the
PR
policy
is.
You
only
find
that
when
you
open
in
your
pull
request
other
than
that,
you
don't
find
this
information,
so
you
have
to
go
and
click
on
something,
and
here
is
Abby,
doesn't
like
to
tinker
she
likes
to
get
information
and
then
like
do
something
and
you're
forced
to
make
a
start,
a
pull
request
and
then
find
out
the
policy
and
like
doesn't
work
right.
A
single
problem
could
have
multiple
facets
like
here.
C
C
What
we
want
to
do
is
D
bias,
your
software
tools
and
soft,
our
technology
that
you
use
because
it
pays
off
because
having
people
being
contributors
having
people
do
any
kind
of
voluntary
work
itself
is
work,
and
if
someone
has
to
do
this
extra
cognitive
tasks,
extra
workload
just
to
get
to
use
your
software,
it's
just
it's
just
making
it
harder.
So
why
not
be
be
inclusive?
C
In
the
tools
we
create
in
your
business
in
our
classrooms
software
tools
and
therefore
make
a
more
inclusive
society-
and
this
is
the
picture
dogma
show-
is
that
you
know
they
are
not
pinks
and
blue.
Some
of
us
a
yellow,
some
of
our
green.
You
know
you're
all
different
kinds
of
people.
You
want
to
support
everyone
and
be
inclusive.
I'll
leave
this
on.
C
As
you
cast
questions,
so
the
gender
market
is
free,
you
can
download
it
we'll
be
more
than
happy
to
help
you
out
if
you
want
to
run
a
gender
Mac
session
on
your
project
on
your
documentation
or
what
have
you
so
Paris
and
I
are
talking
about
having
a
go
and
the
go
documentation
from
the
perspective
of
the
gender
map
sessions
to
find
out.
If
there
are
some
parts
of
the
documentation
that
you
know,
it
is
not
supporting
any
of
the
facets.
C
C
K
K
C
What
do
you
say
all
of
them
consistent
right,
so
ways
to
look
at
is
is
instead
of
saying:
let's
have
a
pink
documentation
for
a
B
and
something
else
from
Tim.
What
you
want
to
look
at
is
like
different
ways
that
you
can
use
UI
source
opening.
So
maybe
it's
not
that
you
have
separate
documentation,
but
the
way
you
structure
them,
maybe
accordion
style.
C
So
you
have
some
information,
and
if
Abby
wants
no
more
information,
then
she
can
click
on
it
or
have
like
pop-ups
that
she
can
say
stick
so
that
she
can
look
at
the
word,
whereas
Tim
would
just
go
in
and
start
clicking
down
there
and
do
stuff.
So
I
would
say
like
it's
not
very
just
because
it's
going
to
be
a
problem
later
on.
Do
you
have
separate
documentation
and
you
might
I
might
assume
like
it's
documentation
of
them,
and
only
so
I
don't
want
to
go
there.
Like
me,
no.
K
C
I
think
so
so
what
we
are
looking
at
is
we
are
looking
at
information
architecture,
so
we
are
doing
a
kind
of
study
right
now
based
on
this
IBM
I'm,
sorry,
but
this
open
source
data
that
we
had
and
trying
to
match.
Each
of
this
information
structuring
our
information
architecture
with
the
cost
of
accessing
and
the
cost
of
going
to
a
particular
site,
and
using
that
then
you
can,
you
can
try
to
figure
out
what
is
the
least
amount
of
cost.
A
B
or
Tim
would
bear
to
beach
the
actual
in
peace.
G
C
You
structure
the
information,
what
kind
of
cues
you
give
so
that
you
know
they
pop
up,
because
even
though
Abbey
is
comprehensive
information
processing
style
that
she
reads,
everything
she's
a
regular
human
and
she's
busy.
So
if
there's
something
information
hidden
deep
down,
she
might
not
see
it
and
I
really
like
the
way
you're
saying
whenever
you
start
a
new
topic
in
documentation
start
with
italic
site.
That
is
emphasis.
C
R
You
so
much
for
your
presentation.
It
was
really
clear
and
I
just
kind
of
sort
of
had
like
this
light
bulb
moment
of.
Oh.
There
is
a
very
logical
reason
why
some
people
are
more
risk-averse
than
others.
It
is
not
anything
innate
or
you
know
it.
It's
it's
like
literally
a
factor
of
time.
How
much
time
does
one
person
has,
and
that
is
something
that
I
had
never
really
realized
quite
like
that,
and
it
just
I
think
it's
starting
to
make
my
day
I'm
having
a
lot
of
feelings
about
this
right
now.
C
A
Thank
You
Anita.
This
was
wonderful
because
I
saw
the
extended
version
of
this
at
Mozilla,
so
this
was
wonderful.
That's
can
I
immediately
as
soon
as
I
heard.
The
last
part
I
had
walked
in
the
door
during
the
last
segment
and
she
at
the
the
segment
was
something
like.
Oh.
If
your
projects
wants
this
and
I'm
like
yeah
looking
around
no
one
else
is
so
excited.
A
A
C
A
We
did
yeah,
we
that's
the
one
open-source
comm
article
right,
yeah,
okay,
that's
in
our
notes,
so
fYI
to
everybody.
Listening,
there's
a
longer
version
of
this
in
the
notes
all
right.
Thank
you.
Everyone
thank
you.
I'd
like
to
eventually
spider
this
out
this
information
out
to
all
of
our
six
I,
don't
know
how
we
can
do
that
or
whatever
whatever
we
can
talk
about
that
at
a
separate
time.
The
meeting
is
over
for
folks
who
need
to
jump.
I
know,
there's
several
items
on
the
open
mic
discussion.
A
A
Yeah,
if
you
and
if
you
want
to
just
mailing
list,
if
anybody
else
has
anything
that
they
need
to
accomplish
this
week,
take
it
to
the
mailing
list
and
then,
if
you
want
to
hang,
if
anybody
wants
to
hang
on,
I
can
still
hang
on
for
a
few
minutes
and
anybody
else
that
wants
to
hang
on.
We
can
get
through
some
other
open-ended
items.
A
George
is
available
as
a
standalone,
video,
yes,
I,
believe
it
is
Anita.
You've
got
this
video
recorded
right
now.
Do
you
want
me
to
record?
Do
you
want
to
do?
We
can
do
like
a
separate
zoom
meeting
and,
like
you
can
do
it
all
over
again
and
I
can
record
you,
okay,
yeah
sure
I
listed
that
yeah
we
can
do
like
a
thorough
30-minute
session.
You
can
just
kind
of
talk
to
yourself,
I'll,
be
in
your
corner,
snapping,
okay,.
C
A
I
mean
and
Aaron
made
an
awesome
point
too,
that
we
get
always
linked
to
this
meeting
duh,
but
at
the
same
time
it
might
be
fruitful
for
folks
to
see
the
whole
thing
if
they
want
to
see
the
whole
thing.
I
do
a.
We
will
talk
offline,
last-minute
things
that
need
to
get
addressed
right
now,
say
or
speak
or
forever
hold
your
peace,
ed,
worse,
tend
to
hand
up
I
know,
you've
got
dub
guide,
stuff
going
on,
feel
free
to
shoot
and
then,
like.
A
A
M
S
Most
of
the
information
and
ducts
have
been
classified
by
six
and
most
of
the
information
had
to
be
really
have
been
related.
Also,
some
dogs
and
I
would
say
that
probably
between
40
and
50
documents
and
the
folder
has
been
reviewed
by
a
six
I've
been
conducting
them.
You
know
slack
emailing,
email
list
and
I
think
for
this
week
we're
gonna
have
a
really
good,
organized
and
clean
developer
guide
and.
A
You're
like
so
far,
that's
a
lot
number
one.
That's
a
lot.
You
need
a
ton
of
progress,
you
have
shepherded
things
and
none
of
us
here
have
been
able
to
shepherd
because
of
just
ambiguity
and
time
and
whatever.
So
you
have
already
made
a
great
progress
that
why
I'm
so
excited.
Thank
you
so
much
for
all
of
your
efforts.
A
So
want
to
thank
everybody.
That's
on
the
line
right
now
that
has
also
been
approving
ad
wash
stuff
and
reviewing
it.
Gwen
I
know
you
I,
see
and
of
course,
Nikita
I
see
you
both
in
there
as
well
all
the
time.
So.
Thank
you
very
much
for
that
questions.
Concerns
comments
for
Edouard,
EV,
guide,
stuff.
O
A
Q
R
Got
a
couple
Valen
volunteers
to
help,
and
but
I
don't
know
if
I
am,
if
I'm
going
to
go,
I
haven't
been
able
to
speak
to
my
manager
in
the
last
two
weeks.
It's
totally
on
my
list
for
my
next
one
on
one
but
there's
questions.
D
G
F
K
A
Q
A
Happily,
like
George,
take
tasks
and
do
things
for
you
I
just
don't
want
to
leave
that
piece.
Okay,
sorry,
I'll
leave
the
like
a
contributor
social
piece,
meaning
like
all
of
us,
can
get
together
and
have
fun.
I,
don't
know
if
they
Bowl
in
Barcelona,
but
we
can
figure
out
what
they
do.
I
A
Yeah
so
we'll
get
our
little
we'll
get
this
little
sub
project
going
and
then
we
can
spider
out
what
we
need.
So
right
now
for
Barcelona
me
George
Quinn
Jonas,
who
else
wants
to
help
out
with
Barcelona
I
mean
we'll
put
this
on
the
mailing
list
as
well,
but
everybody
f
is
God
like
Meehan
Bob's
got
a
taffy
hand,
it.
A
A
Alright,
so
right
now,
we've
got
a
Jaffa
Bob
and
a
Gwyn
who
are
unsure
if
they're
gonna
go,
but
all
of
them
will
do
the
work
leading
up
to
it
all
right,
yeah
I
mean
in
the
worst
case
scenario.
If
I
have
to
like
stand
up
there
and
deliver
it.
That's
fine
I'll
do
that,
for
you
just
do
the
damn
thing.
For
me,
all
right
last
call
for
anything
else
will
obviously
have
even
more
conversation
about
contributor
summit
stuff
in
the
upcoming
weeks.
Gwyn
and
Josh.
A
Q
A
A
All
right
watch
out
for
all
of
the
PRS
that
are
enlisted
I
know
we
didn't
get
to
go
through
all
of
them,
but
some
of
them
are
community
changing
things.
One
of
them
is
endorsement
for
Nikita,
but
it's
a
silent
endorsement.
So
if
you
have
issues
then
off
to
Erin
and
then
I
think
that's
it
it's
Christoph.
Do
you
have
anything
Nikita?
Do
you
have
anything
all
right?
All
right?
Oh
gee,
sock!
What
about
G
Scott?
What's
going
to
achieve
sock
when's
our
minds?
Our
next
deadline.
D
A
A
So
it
is
definitely
code,
I,
don't
know
like
even
a
dwarf.
You
can
think
of
things
like
from
an
automation
perspective
that
you
see,
while
you're
building
the
develop
developer
guide
that
you
know
another
intern
could
work
on
from
an
automation
perspective.
You
too,
even
so.
That's
definitely
also
very
much
an
extension
of
you
too,
but
if
there's
anything
else
that
you
see
just
poking
around
from
like
hey,
this
would
be
cool
perspective.
A
Let
us
know
cool
and
they
Christophe
you
too,
if
there's
anything
that
we
can
do,
that
would
be
awesome
and
then
get
the
word
out
to
and
your
SIG's
other
SIG's
meaning,
if
you,
for
instance,
hang
out
and
sig
networking
tell
them
about
gee
sock.
Just
give
it
as
a
reminder,
release
team,
you
might
be
able
to
use
a
ji-suk
intern
for
some
kind
of
automation
or
some
maybe
dashboard,
building
or
I,
don't
know
if
they
think
big,
I,
guess,
ATS
I,
guess
that's
sort
of
the
motto
here.