►
From YouTube: SIG Chairs and TLs Monthly (Pt. 2) 20200120
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
And
here
we
are
alright,
so
now
intros,
just
like
a
right
any
other
regular
cat
golf
meeting
than
anybody
here
has
been
a
part
of
at
their
core
life.
We
do
intros
one
level
set,
make
sure
everybody
knows
who
everyone
is.
There
are
90
plus
of
you
within
the
project.
Obviously,
no,
not
all
90
are
here
right
now,
but
I
guarantee
you
there's
people
in
this.
Call
that
don't
know
each
other,
so
I
thought
it
would
be
nice
if
we
could
go
around
in
the
agenda.
A
There
is
like
a
little
template
if
you
are
like
hey
I,
don't
know
what
to
say:
I
put
some
musts
as
far
as
your
name,
what's
sake,
you're
representing
working
group,
you're
representing,
etc,
and
then
some
optional
fun
stuff.
No,
you
don't
have
to
say
all
of
them.
Our
last
call
was
like,
let's
just
do
all
of
them
and
then
intros
for
like
30
minutes.
A
So
if
you're
stoked
to
do
all
of
them,
please
feel
free
for
color
if
your
pets
right
next
to
you
and
you
want
to
show
at
your
cat,
feel
free.
So
I'm
just
gonna
go
around
the
heads
of
the
zoom
meeting
right
now
and
:.
All
of
you
to
do
a
quick,
intro
cool
all
right.
So
first
person
I
see
is
Steve
Wong.
Who
are
you
Steve
I'm.
B
Steve
Wang
I'm,
formerly
co-chair
of
the
VMware
sig
that
got
folded
as
a
cloud
provider,
but
I'm
co-lead
of
the
IOT
edge
working
group
and
I'm,
just
getting
a
VMware
user
group
started
so
aspiring
to
have
the
first
meaning
before
the
end
of
this
month.
I
software
engineer
for
the
M,
where
my
favorite
football
team
is
the
Green
Bay
Packers.
So
for
you,
people
in
San,
Francisco
I,
hope
you
lose
this
coming
weekend.
B
I
guess
that's
about
in
later
on,
in
the
ending
had
or
should
I
just
put
it
in
now
open
discussion
of
tips
and
things
so
I've
got
a
tip
for
people
running
these
groups,
and
that
is
be
really
careful
about
changing
the
meeting
time
of
your
cig
working
group
or
whatever,
because
changed
the
meeting
time
for
the
IOT
edge
working
group.
I
think
it
was
a
year
ago
and
people
are
still
showing
up.
B
You
see
the
zoom
notice
that
people
are
there
for
your
meeting
at
the
old
original
time,
because
that
stuff
lives
in
presentation
decks
up
on
YouTube
and
people
find
it
a
year
later.
And
it's
just
like
it's
not
a
casual
decision
to
change
the
time
of
your
meeting,
because
it's
where
it
took
a
year
before
even
half
the
people
switched
over
to
the
new
time.
So
I'll.
A
That
yep
and
there
are
some
tricks
and
tips
there-
that
we
can
share
with
you
and
that's
exactly
what
these
meetings
can
be
about
too,
because
all
of
us
that
are
knee-deep
and
that
administrivia
kind
of
has
some
quirks
and
some
tips
around
there.
So
that's
a
good
one
that
we
can
do
for
a
parking
lot.
All
right.
The
I
see
the
Google
room.
You're
next
I
see
Walter
John,
possibly
others
hiding.
D
E
C
A
G
A
H
You
yeah
it's
nice
to
see
you
all
so
I'm
Barnes
Midland
an
open
source
engineer
at
femur
and
I'm,
currently
a
culture
of
you
from
working
group
and
if
you
want
to
contact
me
I'm
available
everywhere
at
for
us
parts
Nicola,
so
it
shouldn't
be
very
hard
and
find
me
and
about
I,
have
two
cats
and
dog,
which
is
very
big.
But
it's
not
with
me
right
now.
A
I
Hi
everybody,
this
Michael,
you
can,
let
me
actually
start
Who.
I
am
so
I'm
one
of
the
chairs
for
sick
windows,
most
core
maintainer
of
harbor
and
aspiring
to
also
get
more
involved
in
this
in
CF
seek
runtime
as
well
over
the
next
couple
of
months.
Easiest
way
to
find
me
is
probably
on
slack:
m2
I
did
not
read
Kidz
hub
notifications.
It
takes
me
sometimes
weeks
or
months
to
get
to
them.
I
J
K
A
A
L
I
work
with
that
who
so
I
can
find
she's
pretty
good,
I'm
George,
castor
our
work,
it's
a
contributor
experience
and,
generally
speaking,
part
of
my
job
is
to
make
myself
available
for
said.
Co-Chairs
and
tech
leads
if
you
need
stuff
so
normally
I'm
the
person
who
fixes
your
YouTube
videos
if
they
get
messed
up
that
sort
of
thing
during
work
hours,
slack
otherwise,
email,
asynchronous
I'm,
pretty
vigilant
about
my
email,
a
lot
of.
A
M
A
N
A
N
A
A
Really
raining
onesies
right
now
we're
delete
onesies,
alright.
So
thanks
for
entertaining
me
with
all
the
intros.
This
is
good
too,
because
everybody
knows
on
the
call
on
Tuesday
can
now
listen
to
all
of
your
intros
in
like
fast-forward.
Some
short
wall
sound,
really
fun.
The
next
thing
that
I
wanted
to
do
in
this
meeting
and
all
meetings
go
forward
is
have
a
little
announcement
section.
This
is
just
for
things
that
are
applicable
to
you,
how
you
run
your
groups
and
then
open
the
floor
to
you.
A
Also,
if
you
have
announcements
for
other
people,
that
cross-cutting
SIG's
absolutely
need
to
know.
This
is
this.
This
is
that
time.
So,
first
and
foremost,
yes,
there's
a
contributors,
experience
survey.
We
actually
hit
our
goals
as
far
as
our
numbers.
So
that's
great.
However,
we
could
use
some
more
vets,
meaning
if
you
have
a
group
of
people
that
you
work
with
that
have
over
two
years
of
contributing
to
kubernetes
experience.
Please
have
them
still
take
the
survey
that
is
I
would
say
open
for
another
24
hours,
but
we're
pretty
much
good.
A
So
we'll
have
some
pretty
data
and
infographics,
and
things
like
that.
As
far
as
like
what
contributors
want
to
see
out
of
contributor
experience
priorities,
so
if
workflows
and
stuff
like
that,
so
do
me
a
favor.
You
know
just
make
sure
slack
to
your
slack
channels
and
stuff
like
that.
You
get
the
word
out
again.
A
There's
only
24
hours
left
on
that
there
is
a
new
community
meeting
and
George
is
on
the
line
to
both
answer
questions
and
also
give
up
like
a
high
level
of
what
the
heck
happened
and
where,
with
the
current
state,
is
so
George.
You
want
to
take
it
away
for
what's
up
with
the
Thursday
community
meeting
yep.
L
Which
is
in
40
minutes
I'll
actually
have
to
leave
soon
to
prep
for
it.
So
we
saw
declining
community
attendance
at
the
community
meeting
and
I
sent
out
a
little
survey
and
asked
around
ends
up
there's
just
way
too
many
meetings
in
the
community.
If
you
were
getting
tired
of
it,
so
what
we're
gonna
do
is
we
switch
that
to
a
monthly,
cadence
and
I
was
also
getting
feedback
from
Secours?
L
Who
are
like
wait
a
minute
not
to
give
a
community
meeting
status
update
and
then
give
that
community
meeting
status
update
again
a
cube
con
I
got
stuff
to
do
bla,
bla
bla,
so
moved
it
to
a
monthly
cadence.
So
that's
gonna
happen
the
third
Thursday
of
every
month.
That's
that
kind
of
change,
and
then
what
we're
gonna
do
is
I
submitted
a
PR
to
the
kubernetes
governance
to
actually
give
you
more
options
on
where
to
do
a
status
update.
L
So
we
do
have
transparency
requirements
as
saiga
supposed
to
like
tell
the
community
what's
happening
and
before
you
would
just
do
that
at
the
community
meeting.
So
if
you
look
at
the
link
in
the
nose
there's
like
a
little
tracker,
I
scheduled
everyone
when
they're
going
to
go
this
kind
of
works
out,
you
do
a
community
meeting
status,
update,
probably
about
twice
a
year
but
then
cube
con.
Your
status
updates
through
there
would
kind
of
count
as
a
transparency
requirement
as
well.
L
L
So
what
you
would
do
instead
is
fill
out
the
little
template
anyway
and
then
just
send
that
to
the
mailing
list
instead
or
if
you're,
traveling
or
something-
and
you
send
a
representative
or
worse
case,
like
you-
can
hop
on
zoom'
with
me,
we'll
record
a
little
video
and
we'll
do
your
status,
transparency
update
so
I.
You
know
on
paper.
They
should
remove
a
lot
of
work
from
you.
So
you're,
not
you
know
doing
the
same
thing
over
and
over
and
over
again,
but
I
would
like
feedback
on
that
and
also
last
thing.
L
We're
gonna
try
to
get
a
new
host
for
every
single
monthly
meeting.
They
will
be
pinging
you
way
earlier
than
usual,
so
normally
for
your
Thursday
status
would
be
on
Monday.
This
time
we're
gonna
ping
you
at
the
beginning
of
the
month,
they're
gonna
be
a
brand
new
contributor
who's,
never
who's,
looking
for
a
way
to
contribute,
so
we
want
to
get
new
people
up
there.
L
So
we
appreciate,
if
you're,
welcoming
to
them
and
that
kind
of
things,
so
they
will
I
have
a
little
status
checklist
that
they
follow
on,
went
to
remind
you,
they're,
going
to
remind
you
at
the
beginning
of
the
month.
You
know
they'll
be
available
to
help
you
through
slides
and
all
that
kind
of
stuff,
and
then
they'll
give
you
a
final
reminder
the
day
of,
and
then
the
Monday
before,
as
well
as
sending
out
emails
to
the
kubernetes
that
list
and
hopefully
that
will
work
out
better
for
you
all.
A
A
B
L
You
know
and
then
that
kind
of
satisfies
the
requirement:
okay,
good
and
also
the
template
that
I
provide
it's
in
the
notes.
That's
like
an
open
living
document,
so
it's
like,
if
that's
not
working
for
you
or
you
want
to
add
a
thing
or
remove
a
thing
or
whatever
you're
totally
free
to
do
that
or
let
me
know
if
you
want
me
to
add
more
information
or
things
like
that,
so
nothing's
really
set
in
stone.
L
A
L
A
A
B
The
scale
conference
is
a
large
open
source
conference
in
Los
Angeles
held
annually
yep.
It's
not
cube
calm,
but
it
does
get
maybe
4,000
people
and
it
has
for
a
Ford,
a
container
and
Orchestrator
track.
So
there's
lots
of
kubernetes
it's
too
late
to
talk,
although
I
think
you
still
can
submit
lightning
talks
and
a
lot
of
the
people
on
this
call
and
the
kubernetes
community
shows
up
at
it.
It's
not
a
commercial
conference,
so
you
can
get
there.
B
A
Thanks
to
you,
and
then
does
anybody
else
have
any
other
announcements
for
chairs
or
tech
leaves
as
a
chair
or
a
clean,
all
right,
yep
I,
just
kind
of
put
you
all
on
the
spot,
but
for
future
meetings.
Now
you
know
if
you
want
to
say
something
to
I'd
share
another
chair
or
tech
lead,
and
you
want
to
do
it
like
me,
a
zoom
and
set
a
chat,
and
now
you
have
that
opportunity.
A
All
right
next
is
my
favorite
part,
which
is
open.
Discussion
looks
like
we
have
a
little,
maybe
a
little
less
than
30
minutes,
which
is
nice.
Three
things
that
I
wanted
to
go
over
is
obviously
the
emetic
kickoff
question.
What
other
things
do
you
feel
could
be
valuable
to
you
from
this
meeting
and
just
to
play.
A
How
to
resolve
conflicts.
This
meeting
is
really
anything
that
you
can
think
of.
As
far
as
skill
building
is
concerned,
there's
also
the
administrivia
element,
which
is
like
okay.
How
do
we
actually
really
run
a
zoom
meeting
again
I've
been
like
you
know,
clicking
buttons,
but
how
does
this
really
work?
We
can
do
things
like
that.
A
A
This
is
sort
of
ties
in
with
mentoring
as
well,
and
then
today,
I
wanted
to
talk
a
little
bit
more
about
those
two
specific
things,
specifically
one
who
is
taking
your
place.
Have
you
thought
about
that?
And
yes,
if
you
say
the
answer
is
no
I
haven't
that's
fine
too,
and
then
the
other
one
is
getting
in
contact
with
you.
A
One
of
the
reasons
why,
during
the
intro
I
had
in
the
template,
getting
you
know
what's
the
best
contact
is
we'll
actually
have
somebody
go
through
these
videos
and
they're
gonna
check
and
they're
gonna
take
a
list
of
the
chairs
and
tech
leads,
and
what
your
best
contact
is,
because
a
lot
of
folks
have
really
hard
times
getting
a
hold
of
folks
as
far
as
getting
information
out
to
community
groups,
especially
that
has
to
do
with
release.
You
can
see
in
that
linked
issue
in
the
agenda
that
a
former
release
lead.
A
It
just
had
the
time
of
their
life,
trying
to
get
a
hold
of
people
to
ship
features
out
the
door.
I'm
sure
others
have
had
similar
experiences.
I
have
similar
experiences
like
I'm,
pretty
sure
everybody
on
the
line
has
experienced
that
as
well.
So
my
discussion
point
that
we
should
do
right
now
is:
what's
the
best
way
to
get
acknowledgments
from
40
community
groups,
especially
the
leaders
of
those
community
groups.
A
I'll,
kick
it
off
so
some
folks
on
the
Tuesday
like
I'm,
not
gonna,
slowly,
name
names
but
I
mean
even
watch
the
recordings.
Some
folks
won't
Tuesday's
call
thought
we
have
a
mailing
list.
That's
kubernetes,
cig
leads.
Why
are
we
not
using
it
slash,
utilizing
it
to
its
fullest
extent,
slash
people
not
reading
it?
Why
is
that?
Not
our
baseline
other
folks
said
no,
that's
a
terrible
way
to
get
a
hold
of
me.
You
should
definitely
direct
email
me
or
other
people
said
that
wasn't
scalable.
Should
we
use
slack.
A
So
obviously
you
can
see
there's
like
so
many
different
mediums.
You
just
heard
it
in
your
intros
as
well.
There's
so
many
different
ways
to
get
in
contact
with
you
all.
So
should
we
set
a
baseline
and
do
we
think
that
that's
acceptable,
meaning
like
if
we
come
back
and
say
the
following?
We
need
you
to
read
the
following
communications
for
the
following
things:
does
that
make
sense
in.
J
Your
world
I
do
find
it
reasonable
for
people
to
be
able
to
say
I
prefer
to
be
contacted
like
X,
where
X
is
some
reasonably
constrained
list
like
my
carrier,
Pidgeon
right,
but
if
I
want
to
be
contacted
on
slack
and
you're.
Trying
to
get
me
I,
don't
think
that
it's
unreasonable
to
expect
that
someone
would
use
the
name
I
put
in
in
the
community
in
the
community
calls
and
in
the
community
repo
to
find
me
on
slack.
J
E
I
think
that
I
mean
I
think
we
have
to
differentiate
between
I
want
to
reach
everybody
and
I
want
to
reach
an
individual
I
mean
slack
for
reaching
an
individual
makes
sense,
but
if
I've
gotta
reach
out
to
everybody
for
some,
you
know
policy
change.
That
leads
really
need
to
know
about,
like
I,
don't
want
to
ping
everybody
individually
and
I.
J
E
A
K
I
I
think
it's
indications
saying
here's
the
mailing
list:
here's
the
slack
channel
policy,
changes
and
announcements
that
everyone
needs
to
be
aware
of
will
be
sent
to
both
of
those
places
pick
the
one
that
works
for
you
and
and
then
assuming
that,
once
things
are
sent
to
those
two
places,
people
are
responsible
for
having
seen
it.
That
seems
reasonable
to
me.
Yeah.
B
A
to
meet
you
yeah
I'd
agree
for
sending
it
out
to
the
group
to
steal
it
for
both,
and
you
don't
have
to
pick,
which
is
better
for
targeting
individuals.
I'll
make
one
observation
that
I
believe
SIG's,
not
yamo,
only
records
a
github
name
and
doesn't
ask
you
for
a
slack
ID.
So
maybe
it
would
be
a
good
idea
to
add
that
is
there
isn't
a
as
far
as
I
know,
there
isn't
a
way
to
look
it
up.
Yeah.
B
A
A
If
you're
a
chair,
the
amounts
of
times
I've
had
to
guess
a
chair,
slack
handle
the
other
name,
is
nuts,
so
I
guess
something
like
that:
oh
no
did
I
freeze
on
okay,
god,
no
I
see
you
sad
moving
so
I'm
wondering
if
we
can
give
you
all
like
a
template
of
like
where
to
put
BIOS
and
like
what
like,
like
you
know,
if
you
should
put
things
in
your
slack
in
your
slack
bio
or
something
like
that,
Tilley
better,
identify
you
to
folks,
but
at
the
same
time
I
don't
want
you
to
get
plowed
over
with
foot
with
you
know,
enquiries
either
so
anyway.
A
This
is
a.
This
is
a
rolling
thing.
I'm
gonna
type
up
some
notes
from
listening
to
Tuesday
session
and
this
session,
plus
all
of
the
preferred
contacts
that
you've
all
have
already
given
and
come
up
with
sort
of
like
a
little
mini
proposal
of
a
communication
strategy
for
chairs
and
tech
leads.
Does
that
sound
pulled?
N
A
N
Like
one
thing,
I
struggle
with
a
lot
is
talking
to
other
six
or
sig
leads
on
getting
support
for
them
for
a
task
or
initiative.
That
I
think
is
important
for
my
sig,
but
I.
Don't
know
how
to
reason,
with
the
priority
of
like
what
how
busy
the
other
sig
needs
are
to
borrow
their
time
to
support
things
that
we
may
need
to
do
together
right
so
like
pretty
much
things
that
require
like
cross.
N
Sig
support
from
other
SIG's
I
feel
bad,
asking
other
leads
and
I,
and
it's
hard
to
hard
to
reason
about
priorities
by
just
going
to
other
sig
meetings.
So
I
think,
like
a
really
good
use
of
this
meeting
would
be
more
like
one-to-one
time
between
sig
leads
to
determine
like
which
items
for
certain
release
is
more
important
and
how
we
can
give
you
up
the
time
properly,
so
that
we
can
work
together
to
get
those
certain
items
done.
Is
that
does
that
make
sense,
yeah.
A
No,
it
definitely
does
I
mean
I.
From
my
facilitate
from
like
our
facilitation
standpoint,
I
mean
we
can
definitely
add,
like
a
section,
or
maybe
you
not
the
end
like
for
cross
for,
like
that
cross
collaboration,
and
then,
if
folks
want
to
drop,
you
know
where
it's
not
applicable,
they
can
drop
kind
of
thing.
Anybody
have
any
other
thoughts
to
andrew's
suggestion.
A
A
Thanks
so
much
all
right
and
then
one
of
the
last
discussion
points
and
then,
of
course,
if
you
all
have
others,
we
can
do
those
too,
but
one
of
the
last
things
that
I
wanted
to
mention,
of
course,
is
you
it's
so
important
that
we
think
about
ourselves
as
chairs
and
tech
leads
to
and
how
we
get
support
who's
going
to
take
our
places.
Are
you
going
to
do
this
forever?
Oh,
my
gosh.
That's
very
daunting!
I'm
thinking
about
that
I
actually
am
no
longer.
A
That's
fine
too!
That's
what
we're
here
for
the
Tuesday
call
was
very
similar.
I
had
a
lot
of
people
who
said
they
weren't
sure
didn't,
haven't
thought
about
it
and
honest-to-goodness
I
didn't
either
and
that's
why
I
feel
like
it's
so
important,
because
I
couldn't
I
can't
believe
that
I,
like
I,
haven't
asked
people
on
my
mailing
list
like
Here
I
am
contributor
experience
and
it's
like.
Oh
my
gosh
I've,
never
said
hey.
Does
anybody
here?
You
know
interested
in
being
chair
ever?
A
A
You
meet
not
not
you
mean
I'm,
sorry,
but
there
there
has
been
a
concept
and
I've
been
thinking
about
this
concept
of
myself
of
a
chair
tech
lead
shadow
program,
because
a
lot
of
folks
in
the
community
feel
that
the
chair
role
is
one
that
isn't
like
a
tech
lead
where
you're
making
decisions
so
to
speak
and
therefore
can
get
other
people
involved
at
a
level
that
isn't
necessarily
code
decisions
being.
A
When
that's,
why
like,
if
you
build
a
shadow
program,
folks
can
kind
of
see
what
you're
doing
so,
it's
like
more
learning
by
doing
and
then
you're
giving
them.
You
know
kind
of
like
the
release
team,
where
you
give
them
sort
of
some
tasks
occasionally,
and
then
you
build
them
up
in
that
kind
of
a
in
that
kind
of
a
role.
What
do
you
think
about
that?
I.
J
K
K
K
Think
that
is
probably
a
more
pressing
issue
and
the
things
that
I'm
involved
in
is
just
to
scale
back
the
commitments
of
the
cig
and
make
sure
that
commitments
are
actually
staffed
and
then,
once
once,
they're
staffed,
I
agree
with
David
like
once.
There's
a
pool
of
people
who
are
actually
doing
work,
then,
taking
that
pool
of
people
and
developing
leadership
and
pruning
to
leadership
positions.
There
makes
a
lot
of
sense.
I.
Think
that's
really
great.
A
D
A
E
Yeah,
what
exactly
problem
are
we
trying
to
solve
by
like?
Is
it
not
working
I
mean
I.
Yes,
I
see
that
the
succession
planning
maybe
isn't
working,
but
it
seems
like
each
individual's
sake
and
if
it's
not
working
for
an
individual's
sake,
then
maybe
you
should
bring
that
up
and
we
get
a
few
of
them.
We
can
talk
about
it
but
like
beyond
the
succession
planning.
What
problem
are
you
trying
to
solve
by
say
making
it
more
formal
like
I?
E
A
A
Guess,
what's
the
word
I'm
looking
for
looking
to
you
know,
just
I
guess
make
it
within
the
environment
right,
oh
and
I
mean
like
it's
like
I
hear
a
lot
too
from
other
current
contributors,
I
mean
that's
two-plus
years
that
they
have
tried
to
like
help
out
other
SIG's
and
like
get
involved,
but
the
processes
were
there
too
different,
or
it
was
just
like
too
much
and
they
just
like
threw
their
head.
They
threw
their
hands
up
and
said
whatever.
A
Let
them
do
their
own
thing
so
just
trying
to
solve
some
of
these
things
right
and
it's
really
hard
in
a
decentralized
environment
to
solve
some
of
the
human
things
when
everybody's
doing
different
things
right,
yeah.
E
A
And
that's
and
that's
why
we're
here,
I
mean
that's.
Why
I
set
this
meeting
up
in
hopes
that
maybe
we
could
come
together
on
a
couple
terms
or,
if
not
come
together,
then
we
all
sit
here
and
share
every
month.
What
we
do
differently
in
hopes
that,
like
that
different
thing,
could
be
good
for
your
group,
too.
Yeah.
K
Okay,
one
of
the
things
that
we
value
a
lot
of
is
decentralization
just
because
it
helps
us
scale,
and
so
the
idea
that
you're
gonna
have
perfect
consistency
across
a
decentralized
organization,
probably
isn't
very
realistic.
I
I
think
if
we
look
at
the
goals
for
the
SIG's
like
what
are
they
trying
to
accomplish
and
then
goals
for
contributors.
Those
aren't
always
the
same.
K
A
Feel
like
you'll,
see,
though,
that
I
don't
think
all
of
our
save
chairs
even
agree
on
the
baseline
of
what
a
chair
is
so
I'm
like
in
your
alley,
I'm
hearing
you
and
like
what
you
think
it
is,
but
other
chairs
would
disagree
with
that
and
I
don't
know
if
any
of
those
are
on
the
line
right
now.
So
that's
right
me.
It's
just
like
we
can't
even
get
a
baseline
of
folks
to
agree
to
do
updates,
for
instance,
of
the
community
meeting.
A
B
Just
gonna
throw
it
a
whole
bunch
of
comments
so
going
back
five
minutes
ago.
There
were
comments
about
how
much
formal
procedure
do
we
need,
and
the
fact
is,
some
of
these
SIG's
or
working
groups
or
user
groups
are
quite
different
in
what
they're
trying
to
do
or
take
on
than
others
and
I,
because
there
trying
to
do
different
things,
I
think
too
much
formalism
would
be
in
structure
would
be
bad.
You
know
a
user
group,
for
example,
isn't
like
a
sig
at
all.
B
It
doesn't
go
on
code,
so
the
moment
you
tried
to
put
in
place
things
related
to
code.
It
gets
a
little
messy
now
you
could
fork
the
instructions,
but
I,
don't
know
I,
don't
think
it's
that
dysfunctional
now
with
regard
to
you
know,
advice
on
how
you
do
things
that
would
be
useful
for
people
in
leadership,
positions
of
SIG's
working
groups,
whatever
I
think
that
just
some
lessons
and
things
like
how
to
conduct
a
face-to-face-
or
you
know,
sig
activities
like
that
would
be
valuable.
B
Maybe
it's
a
good
thing
to
leave
it
unstructured
with
no
firm
rule
on
how
you
in
you
accomplish
a
succession
because
they're
operating
differently,
but
my
advice
for
somebody
doing
it:
I'd
be
skeptical
of
somebody
coming
in
to
be
a
sig
leader
if
they've
never
been
to
a
Sigma,
a
meeting
of
that
sig
before
and
if
they've
never
been
to
any
segment
before
then.
That
seems
like
a
definite
bad
idea
right.
B
A
All
right
we
have
maybe
a
few
minutes
left
it
looks
like
folks
are
dropping
now
any
other
last-minute
discussion
points
for
anything
that
we've
talked
about
and
again
this
is
sort
of
just
our
kickoff
I
plan,
to
hopefully
like
I,
said,
have
some
more
like
how
to
use
and
demos
in
the
future
meetings.
So
this
is
loose.
A
All
right,
yeah
I
mean
it's
literally
I
want
to
stress
it's
90
plus
of
you
all
us,
huge-mongous
and
just
like
Steve
hit
on
it's
like
every
group
does
run
their
thing
differently.
So
it's
like
I
wonder
if
there
are
any
baselines
outside
of
you
know
what
we've
already
established,
like
you
know,
templates
or
checklist,
sir
I
wonder.
B
If
anybody's
ever
done
a
survey
of
members,
you
know
if
you
were
going
to
establish
a
model
of
what
SIG's
really
seem
to
be
working.
Well,
maybe
a
good
way
to
do.
It
is
to
pull
the
members
just
asking
them
you
know.
Are
them?
Are
the
meetings
of
the
cig
valuable
to
you
and
if
we
can
find
the
outliers
that
seem
really
good,
then
we
can
look
at
what
they're
doing
differently
and
try
to
reproduce.
B
On
the
other
hand,
you
know
you'll
probably
find
some
outliers
where
you
couldn't
pull
them,
because
I
I
don't
want
to
bad-mouth
anything,
but
there
have
been
some
where
I've
dropped
in
on
a
meeting
and
said
this
is
a
loser:
I'm!
Never
coming
back
here,
yeah,
you
know
it
would
seem
like.
Maybe
if
you
have
stats
on
zooms
that
people
show
up
and
never
come
back
or
show
up
and
drop
after
five
minutes,
I
don't
even
know
if
soon
gives
you
those
kind
of
stats.
B
F
B
A
Definitely
like
the
idea
I
mean
because
obviously
we
do
the
contributor
experience
survey,
but
it's
20
plus
questions
already
in
nine
minutes
and
it's
a
lot
of
high-level
stuff,
so
I'm
wondering
if
it
would
be
beneficial
to
like
pull
some
of
your,
like.
You
know,
five
questions
at
most,
not
necessarily
right
now,
because
they
just
probably
filled
out
another
survey
but
like
at
some
point
in
the
year.
Like
hey.
Do
you
think
these
meetings
are
valuable
like
what
else
could
we
do?
A
That
would
be
better
and
obviously
like
it's
anonymous,
you
don't
have
to
end
like
you
know,
it's
you're
collecting
information
about
what
other
people
might
think.
I
don't
know,
I
think
that
sounds
like
a
good
idea
and
then
you
might
learn
something
different
too
about
how
you
run
things.
I
mean,
like
we've,
been
changing
the
community
meeting
for
at
least
two
years
straight,
just
based
solely
on
survey
and
focus
group
feedback.
So
I
don't
know,
might
be
something
to
think
about.
Well,.