►
From YouTube: K8s SIG Docs Meeting for 20230711
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
Alrighty
folks
hi
everyone
and
big
welcome
back
after
a
little
small
time
off
of
the
regular
schedule
for
the
community
meetings
for
Sig
docs
today
is
Tuesday
the
11th
of
July
2023
for
the
bi-weekly
community
meeting
for
seek
docs
for
the
kubernetes
project,
big
thanks
to
everyone
for
joining
I
hope.
A
Everyone
is
enjoying,
if
you're
in
the
northern
hemisphere
your
summer,
if
you're
in
the
southern
hemisphere,
you're
winter
right
now,
and
what
I
wanted
to
mention
is
that,
given
that
we
are
a
special
interest
group
of
the
kubernetes
project,
this
meeting
is
governed
by
the
kubernetes
code
of
conduct.
So
we
do
want
everyone
to
be
very
respectful
to
each
other
in
terms
of
meetings
like
this,
on
slack
in
PRS
and
issues
anywhere
that
the
kubernetes
project
has
its
has
its
work,
big
thanks
again
for
everyone
joining.
A
We
do
have
a
little
bit
of
a
light
agenda
today.
So
for
folks
who
are
on
the
call
that
want
to
add
to
the
agenda
now,
you
can
definitely
do
so.
If
you
don't
have
access
to
be
able
to
edit
the
agenda,
it's
because
you'll
need
to
join
the
Sig
Docs
Google
Group,
which
will
give
you
access
to
our
calendar
and
access
to
be
able
to
edit
this
specific
agenda
as
well.
A
Okay,
for
those
who
don't
know
me,
hi,
my
name
is
Natalie
vladko,
my
pronouns.
Are
she
her
and
I'm
one
of
the
co-chairs
of
seek
docs?
A
We
have
one
of
our
other
coaches
on
The
call
here:
Ray
lahano,
who
may
not
be
as
responsive
today,
as
you
may
have
seen
in
the
chat,
but
Ray's
still
going
to
try
and
participate
and
help
out
as
much
as
possible
and
we've
also
got
one
of
our
tech
leads
Tim
bannister
on
the
call
too
hi
Tim,
so
I
wanted
to
just
kind
of
introduce
a
couple
of
folks
who
helped
make
decisions
around
here.
A
But
what
we'll
do
is
we'll
get
started
with
the
agenda.
I
I
will
link
it
here
again
in
the
chat
for
everybody.
A
I've
had
interesting
feedback
about
sharing
a
screen
specifically
for
recording
purposes,
I'm
going
to
try
today
and
for
recording
purposes
to
not
share
my
screen
and
just
see
how
that
goes
in
terms
of
what
folks
think
of
watching
the
recording
later
so,
please
click
the
link
in
the
chat
to
be
able
to
follow
along
with
the
agenda.
A
Speaking
of
the
agenda,
we
can
firstly
get
started
by
inviting
anybody
who's
new
as
a
contributor
or
a
meeting
participant
who
wanted
to
say
hello,
either
in
the
chat
or
unmute
themselves
to
say
hi
to
us.
That
now
is
the
time
to
do
so.
A
Hi
Robert,
please
tell
us,
tell
us
who
you
are
in
terms
of
other
other
credentials,
you'd
like
to
share.
Oh.
B
I,
just
you
know
like
to
hang
out
at
Linux.
Foundation
I
do
some
strategic
partnership
stuff
and
you
know
the
folks
at
the
mothership
were
like
hey.
Could
we
help
our
documentation
friends
out
with
some
generative
AI
tooling
could
could
we,
you
know,
carry
some
wall,
water
and
chop
some
wood
to
help
out,
and
the
answer
is
yes,
hi
I'm
here
so
we'll
talk
about
that
more
but
but
that's
it.
I
I
lead
strategic
Partnerships
over
at
LF.
A
Perfect
thanks
so
much
for
joining
yeah
big
thanks
that
you
could
be
here
anybody
else
who
wanted
to
say
hi
today,
yeah.
C
D
Hi
Marcelo
here
no
longer
and
you
I've
joined
as
my
b3ib.
The
third
fourth
call
I
have
news.
I've
recently
joined
the
org
thanks
to
Ray
and
Tim
have
sponsored
me
for
joining
the
the
organization.
Thank
you.
E
Hi,
my
name
is
Moab.
This
is
my
first
call
I,
think
and
I'm
looking
to
contribute
or
to
do
my
first
contribution
with
kubernetes.
A
A
We
always
need
lots
of
help.
Missions
I
definitely
welcome,
and
you
can
also
help
if
you
wish
to
by
being
able
to
if
you
want
to
provide
some
informal
reviews
and
some
things
that
you're
looking
at
in
the
kubernetes
project
as
well.
That's
always
a
helpful
thing
too.
So
thank
you
and
welcome.
A
Alrighty
I'm
going
to
take
silence
as
a
we've.
We've
done
the
room,
so
thanks
everyone,
we
miss
every
anyone.
Please
feel
free
in
the
agenda
to
add
your
name
and
any
information
you'd
like
us
to
to
know
about
you.
A
That
would
be
great
and
big
thanks
for
those
of
you
who
did
introduce
yourselves
and
say
hi,
going
on
with
the
next
part
of
the
agenda
for
those
who
are
new,
we
do
have
a
couple
of
things
that
we
go
through
as
general
reminders
and
a
general
how
I
never
want
to
use
the
term
housekeeping
but
I'm,
trying
to
think
of
a
better
term
administrative
to
Do's.
A
Let's
say
that
we
always
have
here
in
the
in
in
sick
docs,
and
one
of
those
is
a
is
a
role
that
we
have
called
the
pr
Wrangler.
That
role
is
someone
who
is
an
approver
in
the
insect
docs,
who
every
every
week
is
kind
of
on
shift
to
help
get
our
PRS
moving
through
the
approval
process,
getting
them
reviewed
by
either
the
specific
other
sigs
that
need
to
use.
A
Do
a
technical
review
helping
to
do
some
reviews
themselves
and
helping
to
get
approvals
through
so
that
we
can
keep
our
pi
numbers
at
a
at
a
manageable
level.
That
is
something
that
is
a
it's
a
it's
a
constant,
a
battle
that
we
are
that
we
are
facing.
So
that's
why
we
are
always
welcome
to
get
as
much
help
as
we
can
from
either
Community.
A
A
Looking
at
who,
the
current
PR
Wrangler
is
and
being
able
to
kind
of
Point
them
in
the
direction
of
the
review
that
you're
wanting
because
they're
the
ones
who
are
kind
of
on
shift
for
the
week
to
help
push
those
PR
reviews
through
so
for
this
week
it's
Karen
Bradshaw,
Karen's
information
there
yep
KB
hawky.
A
Thank
you
so
much
Tim
information
in
terms
of
the
pr
wrangler's
handlers
in
the
in
the
agenda
and
then
next
week
we
have
next
week
we
have
chiming
another
round,
Tech
lead
in
the
following
week.
Taylor,
who
is
another
vertic,
leads
as
well
there
for
the
pr
Wrangler
so
there
for
the
next
three
weeks.
If
you're
looking
for
reviews
trying
to
help
getting
and
getting
your
information
and
PR's
or
issues
through
the
pr
Wrangler
is
always
a
really
good
person
to
be
able
to
ping
there.
A
I
want
to
note
that,
because,
given
that
we
are
a
small
amount
of
approvers
and
reviewers
right
now,
sharing
the
workload
is
definitely
something
that
would
that
we're
trying
to
do
a
lot
more
often
here
in
zigdox,
okay
and
for
those
PR
Wranglers,
and
you
know
a
previous
who
are
on
the
call,
please
make
sure
that
you're
looking
at
your
shifts,
we
did
thanks
to
Nate,
add
in
a
third
weeks
person
just
so
that
we've
got
the
the
agenda
kind
of
lined
up
for
who's
going
to
be
on
on
shift
for
the
next
few
weeks.
A
But
if
Wranglers
can
keep
in
mind
when
they're
going
to
be
working
on
things,
that
would
be
great
for
those
who
are
interested
in
wanting
to
learn
more
about
PR
wrangling.
We
also
have
a
shadow
program
for
this.
A
It
does
take
some
time
to
become
a
PR
Wrangler,
because
you
do
need
to
become
a
reviewer
and
then
an
approver,
but
we
are
always
willing
to
help
folks
learn
about
what
we
do
if
you're
more,
if
you're
interested
in
learning
and
then
also
getting
more
involved
in
cdocs,
feel
free
to
reach
out
to
any
PR
Wrangler,
that's
on
shift
or
any
of
us
co-chairs.
A
Or
tech
leads
that
if
you
want
to
Shadow
the
pr
wrangling
process
just
reach
out
to
us-
and
we
are
happy
to
put
you
on
a
week
that
will
work
for
you
and
hopefully
the
the
Wrangler
of
your
choice.
And
then
you
can
be
able
to
learn
the
ins
and
outs.
Everyone
has
their
own
different
style
and
way
of
working.
So
there's
no
one
way
that
we
all
do
this
but
feel
free
to
jump
on
the
shadow
program
as
well.
A
If
you
wish
to
alrighty
the
next
thing
that
I
want
to
remind
folks
of
is
again
with
the
with
the
creative
conduct,
if
you
are
noticing
anything
in
the
code
of
conduct
or
in
terms
of
in
meetings
or
in
slack
or
on
PRS
or
issues
that
you
think
that
is,
might
not
be
that
good
of
behavior
and
you'd
like
to
perhaps
address
this
via
the
code
of
conduct.
You
can
reach
out
to
the
code
of
conduct
committee
and
you
can
remain
anonymous.
A
The
email
address
is
conduct
kubernetes.io
and
the
information
I've
put
there
in
the
agenda
for
you
as
well.
If
you'd
like
to
access
that
okay,
that
was
a
lot
of
talking
for
me
thanks
thanks
for
listening,
we're
going
on
into
our
agenda
now,
and
we
are
at
the
moment
up
to
release
one
two
eight
for
kubernetes
for
folks
who
are
new
in
the
kubernetes
project.
A
We
do
releases
three
times
a
year
around
about
almost
four
months
each
time
and
we
are
currently
up
to
release
one
two,
eight
and
so
I
wanted
to
check.
If
we've
got
someone
on
the
call
from
our
release,
docs
team,
who
was
going
to
give
an
update
for
today.
A
Okay,
Nate,
please
go
for
it.
A
Oh,
that's
a
great
question:
I
am
not
sure
I
can
I
think
we
might
be
able
to
get
some
information.
I
have
a
feeling.
There
we
go,
Ray
I
knew
Ray
was
going
to
typing
something
early
August,
but
the.
F
Just
because
I
want
to
make
sure
that
we
have
some
folks
available
for
netlify
and
sort.
A
Be
helpful
yeah.
Definitely
our
Doc's
lead
Richard
Dougley.
Who
is
information
in
the
in
the
agenda
there?
Oh,
thank
you.
Ray
correction
is
being
mid-august.
August
15.,
our
docs
lead
for
for
this
cycle.
Richard
is
in
a
in
a
different
time
zone
than
what
we're
used
to,
which
is
great.
A
It
does
mean
that
we
will
have
likely
some
different
folks
need
to
be
available
for
netlifine
for
for
a
lot
of
that,
as
opposed
to
let's
say
the
usual
Ray
in
yourself,
mate,
so
so
yeah
so
that'll
be
something
that
hopefully
we
can
sync
up
with,
rather
than
later,
to
figure
out
how
we
can
be
available
there
as
well
great
to
hear
you'll
be
available.
A
Ray
we'll
see
how
that
works
on
the
with
it
with
time
zones
too,
but
yeah
we
can
discuss
that
closer
to
the
date
as
well.
A
I
just
took
the
last
update
from
the
release
team
notes
into
into
today's
agenda,
which
is
that
the
doc
status
is
green
and
that
all
the
cap
owners
have
had
been
reached
out
to
once
again
for
the
next
deadline
of
of
their
of
their
doc
status.
So
with
that
being
said,
docs
are
currently
green
for
those
who
are
new,
Sig
docs
does
do
a
lot
of
work
around
releases
as
well.
A
There
is
always
a
docs
lead
as
part
of
the
release
team,
and
we
work
with
that
with
that
docs
lead
to
help
make
sure
that
not
only
everything
is
kind
of
running
smoothly,
but
also
that
the
right
permissions
are
given
so
that
the
website
can
be
updated
with
the
new
things
that
are
required
for
the
release.
So
we
give
updates
every
meeting
to
that
effect.
A
A
It
is
going
to
be
me
talking
again
because
I
know
Ray's
unavailable,
but
I
wanted
to
quickly
note
here
per
Divia,
our
other
co-chair,
who
isn't
available
at
the
meeting
at
the
moment,
but
that
we
have
a
new
role
called
the
issue.
Wrangler,
you
may
have
heard
me
talk
about
PR
wrangling,
and
so
this
same
idea,
but
specifically
for
our
issues,
is
something
that
we're
going
to
be
doing.
A
Issues
need
to
be
triaged,
we'll
need
to
be
making
sure
we
can
actually
be
able
to
label
them,
maybe
as
good
first
issues
or
label
them
appropriately
or
get
let's
say
consensus
with
other
sigs
that
are
required
to
work
on
certain
things
and
an
issue.
Wrangler
is
going
to
be
a
person
that
is
hopefully
going
to
be
doing
a
lot
of
that.
We're
going
to
be
soon
working
on
documenting
that
role
and
issue.
Ringling
is
going
to
be
something
that
may
or
may
not
require.
A
Approvers
only
could
be
something
that
is
a
bit
of
a
lower
permission
level
role.
It
could
be
really
really
great
for
folks
who
are
semi-new
in
their
contribution
Journey,
but
have
been
around
the
the
Sig
for
a
little
while
still
and
are
willing
to
help
out.
So
once
that
documentation
documenting
of
the
role
has
been
done,
we'll
share
more
here
in
the
in
the
meeting
and
get
folks
who
are
interested
to
jump
on
board
with
that.
Is
there
any
questions.
F
Thanks
with
and
a.
F
Issue
wrangling
for
a
while,
the
one
that's
what
I
have
with
with
newer
votes
coming
in
and
doing.
C
F
Group
going
to
be
sort
of
oversight
on
on
that
making
sure
that
okay,
if
something
is
mistakenly
triage,
is
there
a
way
of
gracefully.
H
A
In
my
talks
with
Divya,
we've
talked
about
how,
with
when
you're
focus
in
particular.
This
would
be
something
that
there'd
be
considerable.
Training
given
specifically
for
wrangling
as
opposed
to
a
current,
consistent
review
or
approver,
may
not
need
that
as
much
because
they've
been
around
the
project
and
in
City
docs
for
quite
a
while,
whereas
someone
who's
knew
who's
willing
to
do
that.
Kind
of
work
would
need
a
bit
of
training
at
first,
and
that
would
be
the
way
that
we'd
hopefully
resolve
some
of
that
I.
A
Don't
think
we
can
ever
completely
eliminate
the
possibility
of
let's
say
mistakes
at
the
same
time.
Mistakenly
triaging
an
issue
versus
mistakenly
approving
a
VR
is
probably.
A
F
And
it's
not
just
new
folks
who
can
make
questions
season.
Seasoned
documentarians,
also,
but
I
I
just
wanted
to
make
sure
that
that
was
a
part
of
the
right
of
the
Renaissance
understanding
how
to
to
make
Corrections
yeah.
A
For
sure
and
again
this
is
one
of
those
roles
that
a
we
just
really
need
to
see
dogs,
but
we
also
need
another
way
for
new
contributors
to
get
involved
that
maybe
isn't
as
kind
of
big
investment
Stakes,
as
is
learning
a
lot
about
kubernetes
and
thus
being
able
to
contribute
to
a
lot
of
the
docs
of
the
project
and
help
to
review
those
so
yeah.
A
So
this
is
again
one
of
those
things
where
hopefully,
the
two
birds,
one
stone
approach,
but
yeah
a
lot
of
training
to
be
involved
as
well
with
that
too
big.
A
Awesome
right
any
other
questions
about
the
issue:
Wrangler
role.
D
Yeah
so
related
question,
since
the
brand
new
role
no
previous
personnel
has
had
it,
but
regardless
I
think
the
first
issue:
Wrangler
should
be
an
experienced
contributor
that
can
then
mentor
and
then
new
ones
or
they
they
can
do,
go
through
a
similar
process
that
they're
shadowing
the
pr
Wrangler,
the
shadow,
the
the
issue
Wrangler.
But
if
it's
like
I'm
gonna,
be
the
first
issue
of
a
new
contributor,
it
would
be
a
disaster.
It
has
no
point
of
reference
or
previous
experience.
Yeah.
A
So
all
of
us
who
will
reprovers
and
have
been
in
like
sync
docs
for
a
little
while
have
done
our
own
issue,
wrangling
already,
because
no
one
else
really
does
do
any
kind
of
triaging
or
anything
on
a
lot
of
the
issues
we
kind
of
have
to
do
that
role
already
ourselves.
So
this
is
actually
a
bit
of
a
breakup
to
have
this
a
very
specific
on
its
own
as
a
role.
A
So
the
first
issue,
Wrangler
very
likely-
as
you
mentioned,
still
going
to
be
someone
experience,
but
there
are
experienced
people
already
in
this
work
that
will
be
able
to
Aid
you
a
lot
of
training
and
help
newer
folks,
but
B
be
able
to
catch,
for
example,
issues
that
might
crop
up
crop
up
as
well.
So
while
it
is
a
new
role,
it's
not
a
completely
new
stream
of
work.
A
lot
of
us
are
doing
this.
On
top
of
our
all
of
our
other
worker.
Jobs
are
really.
G
To
the
blast,
radius
is
a
is
hugely
different
if
you're
a
PR
Wrangler,
the
worst
thing
you
can
do
is
probably
break
the
kubernetes
website,
which
actually
people
will
notice.
G
If
you
are
an
issue
Wrangler,
the
worst
thing
you
can
do
is
you
know
great
greatly
upset
a
contributor
who
didn't
need
upsetting
and
failed
lived
by
our
community
values
and
we
lose
a
contributor.
Please
don't
do
that,
but
not
as
many
people
will
notice.
A
Definitely,
but
at
the
same
time,
it's
great
to
hear
that
it's
possible,
possibly
that
you're
interested
in
Marcelo
and
for
anyone
else
on
the
call
interested
it's
a
great
way
to
a
learn
about
things
that
we
want
to
be.
You
know,
fixing
and
working
on
in
in
think
docs,
but
also
a
way
to
help
to
maybe
how
to
say,
influence
possible
future
roadmap
and
things
that
cdox
is
working
on
too.
A
As
the
issue
Wrangler,
you
get
a
lot
of
kind
of
say
in
a
lot
of
those
things
and
a
lot
of
be
able
to
kind
of
move
a
lot
of
needles
forward
in
in
that
way,
so
yeah
it's
it's
a
role
that
has
been
needed
for
quite
some
time,
but
even
to
do
the
work
of
creating
this
role
is
itself
something
that
we've
been
struggling
to
do
for
a
while.
So
we're
very
excited
to
to
get
this
started.
A
A
All
right
thanks
everyone
again
when
that's
ready
to
go
we'll
post,
not
only
in
slack
but
here
for
the
meeting
as
well
and
for
folks
who
want
to
get
on
board
I
believe
it'll,
be
a
diving
myself
doing
a
lot
of
the
kind
of
training
and
the
communication
on
this.
So
yeah
watch
out
for
info
from
us
soon
to
move
on
to
the
next
agenda
item
I
want
to
call
on
Maureen
hello.
I
I
I
A
F
Thanks
for
bringing
us
up,
I
I,
like
in
in
place
link,
Checkers
and
and
on.
C
F
Other
sites
today
maintain
our
own
I've
got
something
like
them,
Checkers
out
other
than
NCD
and
I.
Think
hotel
is
also
about
a
similar
thing
set
up
so
on
on.
What's
up
on
PR,
it
does
a
check.
Does
this
I'm
glad
to
see
this
this
PR
in
place,
but
I
I?
This
is
just
my
first
time
seeing
it,
though,
does
it
actually
blog?
Would
this
like
actually
like
do
a
request
for
changes
if
there's
something
broken,
and
does
this
only
check
the
the
current
page
that
has
been?
F
F
Could
also
make
a
difference
in
terms
of
adoption
and
acceptance.
I
So
the
way
I'm
not
like
super
expert
in
link
Checker
right
here,
because
I
just
came
across
it
last
week,
but
the
way
I
understand
that
the
script
works
is
that
you
can
provide
a
glob
and
then
it's
going
to
scan
all
files
that
match
that
glob
and
the
change
I
am
introducing
is
just
a
new
flag
that
went
past
to
the
script
is
going
to
update,
that's
only
for
the
links
in
markdown
Pages
for
now,
because
that's
what
I
had
the
time
to
do
this
morning.
I
I
But
just
as
an
addendum,
there
is
no
automation
being
done
as
of
this
PR
I,
just
literally
added
the
new
flag
and
the
logic
to
make
the
In-Place
substitutions.
So
anyone
using
it
would
have
to
run
locally.
F
Right
that
that
that
makes
more
sense
to
to
me,
because
I
I,
don't
recall
us
actually
having
an
automated
on-pr
check,
I
wouldn't
necessarily
be
opposed
to
it.
Thank
you.
F
But
I
think
so
so
for
for
a
local
check,
I
like
that
it
suggests
a
a
fix.
I
think
that's
helpful,
but
I
will
I'll
add
myself
as
a
reviewer
to
this
just
so
that.
F
Be
able
to
go
through
it
and
speak
to
it,
but
I'm
happy
to
look
at
it
over
the
next
couple
of
days
here
or
maybe
even
this
afternoon.
Actually
I
can
probably
get
to
it,
but.
A
Great
thanks
Maureen
for
bringing
this
to
our
attention
and
adding
this
to
the
suggestion.
I
also
think
it's
great
I
I,
just
added
also
your
comment
Tim
about
possibly
proud
running
a
job
like
this
for
broken
links,
I
think
that
could
be
a
great
great
idea
too.
A
So
yeah
thanks
again
also
Nate
as
well,
for
adding
yourself
as
a
possible
reviewer.
Anyone
else
on
the
call
that
wants
to
review
the
link
is
in
the
agenda
for
that
PR,
thanks
again
Maureen
for
bringing
that
here,
Tim.
G
Not
many
people
in
this
sick
use
prowl,
but
if
you
are
a
sick
dogs
person
watching
a
video
listing
live,
and
you
would
like
to
use
proud
to
run
a
test
Mosey
on
over
to
the
sick
testing
slack
Channel
and
see
if
there
is
someone
there
who
is
willing
to
share
their
experience
of
using
power
a
lot
and
connect
with
you
and
and
make
it
a
joint
effort.
You
are
not
expected
to
know
you
know.
Hugo
marks
and
kubernetes
documentation,
your
localization
of
choice
and
prowl.
C
F
Would
be
interested
in
having
like
I
said
for
for
a
a
page
changed
or
a
section
changed?
Would
it
be
interesting
to
have
a
link
check
done
automatically
and
flagged
anything
broken
at
that
point?
Yes,
yes,
yes,
yes,
yes,
yes,
I!
Think,
okay,
yes,
I!
Think
I,
think
I
think
we're
checking
the
entire
site
every
time.
That's
problematic,
but
I
think
for
for
changed
sections.
I,
think
that
would
be
super
valuable.
Okay,.
A
I
mean
but
look
at
the
localization.
This
is
hugely
valuable,
yes,
yeah
yeah
for
sure
and
I
can
and-
and
that's
a
that's
a
good
point
to
note.
The
idea
of
you
know
checking
the
page
itself
rather
than
needing
to
do
the
whole
site
each
time
for
sure
but
yeah,
especially
when
bigger
changes
need
to
go
Downstream
to
the
localizations.
Something
like
this
would
be
unreal
yeah
for
sure.
A
All
right,
I'm,
going
to
jump
over
to
the
next
point
in
our
agenda,
which
is
actually
actually
in
the
just
questions
and
discussions
area.
So
before
I
do
move
on.
Does
anyone
have
any
other
issues
or
PR's
that
they
wanted
to
bring
up
before
we
moved
over
to
General
conversation.
A
Sure,
and
what
did
you
want
to,
what
did
you,
what
were
you
bringing
attention
to
with
this
PR
today.
D
I
want
to
know
my
team
made
a
comment
there
that
the
content
that
I
suggesting
the
change
I
suggest
might
be
better
placed
in
a
different
page
and
I'm
asking
there.
If
that's
the
case,
do
I
need
a
separate
PR
for
that
page
or
I
can
use
the
same
PR
to
contribute
to
that
so
I
I
posted
a
you
know
a
suggestion.
E
D
H
F
Make
if
the
if
the
change
is
related
right,
if,
if
somebody
says
okay,
this
reminds
me
of
something
unrelated
that
we
also
need
to
do,
then,
probably
that
would
be
a
new
issue
in
a
new,
a
new
PR,
but
if
the,
if
the
change
is
related
and
like
like
it's
like
it's
like,
oh
you're,
updating
this,
this
also
needs
to
be
updated
because
it's
it's
like
hitting
the
same
API
or
something
that
should
probably
be
done
in
the
same
PR.
F
So
you'd
add
a
new
commit
to
make
that
change,
even
though
it
is
on
a
separate
page,
so
I
think
of
PR's
as
conceptually
here's.
This
set
of
changes
for
this
issue,
not
here's
a
change
to
this
page,
because
then
you
get
if
you,
if
you're,
if
you're
sort
of
breaking
it
up
by
page,
then
you
wind
up
with
like
potentially
like
five
or
ten
PR's
per
issue
that
has
a
larger
update,
so
I
would
I
would
collect
that
all
into
this.
If
I'm
understanding
your
question.
D
A
Awesome.
Thank
you.
Thanks.
Marcella
thanks
Nate
One,
Last
Call
for
any
other
issues
or
PR's
to
bring
up
before
we
move
over
to
our
next
agenda
item.
A
All
right
taking
that
as
a
no,
we
are
up
to
the
last
point
of
our
agenda,
which
is
in
the
questions
and
discussions
area,
and
this
is
where
we
get
to
give
one
of
our
guests
from
the
Linux
Foundation
Robert
Reeves
the
floor.
Specifically,
if
you
missed
out
earlier
reefs
from
Linux
Foundation,
is
here
to
help
easy
to
talk
about
a
generative
AI
for
kubernetes
docs
and
how
he
and
the
team
can
possibly
help
us
so
Robert
I'd
love
to
give
you
the
floor.
B
Well,
I
have
no
ideas,
zero
and
Shadowood
Nate.
When
we
chat
last
week,
wasn't
eight.
F
B
It
was
great,
well,
look
gang,
you
know
we
were
chatting
at
LF
and
you
know.
The
goal
here
is
to
provide
our
maintainers
our
contributors
projects,
foundations
with
the
best
tooling
around
and
there's
concern
amongst
some
of
the
lft
members
that
we
might
be
kind
of
missing
an
opportunity
here
with
generative
Ai,
and
you
know
they
they.
Somebody
asked
well
Robert.
What
do
you
think
I
was.
B
I,
just
I
I,
don't
know
I
mean
outside
of
using
co-pilot
to
make
me
look
smarter
that
that's
the
extent
of
generative
AI
that
I
do,
and
so,
but
the
the
conversation
was
like
there
is
an
opportunity
here.
B
It
feels
like
there's
something
in
documentation
as
a
force
multiplier
and
so
wanted
to
start
the
conversation
with
our
documentation,
team
and
and
the
folks
that
help
out
here
are
doing
the
good
work
to
see
what
we
can
do
to
help
out
we're
frankly,
we're
not
looking
to
dictate
to
our
sigs
how
to
do
things.
We
want
to
understand
what
you
would
like,
and
we
support
that.
B
So,
if
there's
tooling,
that
you
want
to
try
out
getting
support
from
that
vendor,
bringing
them
in
providing
help,
because
what
what
vendor
doesn't
want
to
say.
Well,
we
helped
the
you
know:
cncf,
we
helped
kubernetes.
You
know
solve
this
problem
that
that's
very
much
a
feather
in
their
cat,
and
so
this
is
really
about
offering
the
team
here
help
we're
here
to
help.
We
want
to
follow
your
lead.
We
don't
want
to
tell
you
what
to
do.
We
want
to
listen
and
better
understand.
Now
that
being
said,
I
am
a
devops
person.
B
We
used
to
call
it
software
configuration
management
when
I
started
so
really
dating
myself
and
I'm
a
huge
fan
of
robust
tool
chains
that
help
people
be,
you
know,
provide
them.
Forced
multipliers
do
more
with
what
they
have
today,
Nate
and
I
chatted
about
that.
B
He
certainly
had
some
great
ideas,
but
look
gang
at
the
end
of
the
day.
I
just
want
to
be
a
resource
to
help
out
and
to
find
people
that
are
in
Sig
docs
that
say
Hey
this.
B
This
is
something
that
interests
me,
because
I
think,
if
Sig
docs
was
able
to
improve
this,
this
winds
up
being
a
template
that
other
foundations,
other
projects
can
model
I
mean
who,
who
best
but
kubernetes
documentation
to
kind
of
pave
the
way
it'll
be
painful,
it'll
be
uncomfortable,
but
who
best
to
to
you,
know
Shine
the
Light
and
carry
the
torch
and-
and
we
just
want
to
help
you
all
do
that.
A
Thanks
Robert
thanks
so
much
we've
got
some
yeah.
Let's
get
some
hands
up
to
start
some
conversation,
Marcelo
I,
say:
you've
got
your
hand
up
there.
D
A
newbie
I
think
one
of
the
greatest
concerns
with
generative
AI
is
Eddie
gathers.
It
sits
all
the
information
from
everywhere
all
the
Combs,
all
the
internet
and
comes
up
with
a
with
an
answer
to
your
your
your
promise.
D
One
thing
I
know
is
that
in
the
style
guide
you
in
the
documentation
cycle,
you
you
separate
content,
original
content
produced
by
you
and
in
the
sick
talks
versus
vendor
content.
That
should
be
explicitly
say.
Oh,
this
is
a
link
to
an
external
site.
Is
you
you,
you
have
to
to
to
make
explicit
your
sources,
the
sources
that
are
community?
D
So,
if
is
a
contributor,
rely
on
go
to
chat,
GPT
and
say,
write
me
a
an
article
on
networking
and-
and
it
will
come
up
with
that
with
a
with
a
text,
37
mixed
match
of
all
gathered
from
all
over
the
place
and
puts
that
together
it
looks
good,
looks
nice,
but
then
we
publish
it
and
then
it
comes
out.
I,
don't
know,
Amazon
comes
and
say
hey.
This
is
our
content.
Why
are
you
putting
it
there
as
yours?
E
F
Actually,
he
brought
this
up.
Yes,
yes,
very
much,
so
one
of
the
things
and
and
I
think
somebody
in
the
chat
already
sort
of.
F
F
Rather,
let
you
folks
sort
of
drive
this,
but
in
terms
of
what
a
generative
AI
is
good
for
and
what
use
cases
it
is
good
for
is
like
we
don't
have
to
have
it
sort
of
look
at
the
the
kubernetes
like
kubernetes
repo
and
and
generate
like
API
documentation
or
generate
the
actual
documentation.
F
I
think
there
are
other
use
cases
that
AI
could
be
helpful
where
we
avoid
those
types
of
pitfalls
and
and
and
Keegan
sort
of
puts
it
well,
where
we
can,
we
can
pick
and
choose
where
these
things
go
and
what
they're
doing
and
and
choose
the
type
of
help
that
they're
providing
us
and
furthermore,
we
can,
potentially,
with
with
Robert
as
students,
help
automate
some
of
the
the
training
and
whatnot.
F
If
we,
if
we
feel
like
we
need
to,
there
are
also
off-the-shelf
solutions
that
may
also
so
I'll
I'll
put
it
back
to
the
floor
for
more
conversation.
Now.
G
So
an
area
where
I
I'd
like
to
to
see
this
sort
of
thing
is
just
to
give
an
example
I
think
of
how
can
we
use
you
can
combine
generative
AI
with
automated
testing,
so
you
can
say
to
you
know.
The
large
language
model
here
is
an
example
kubernetes
manifest.
How
could
it
be
better
to
help
people
learn
this
API
and
the
large
language
model
says
hey.
G
You
know,
here's
an
example:
config
map,
here's
a
better
example
config
map
and
it
adds
a
description
or
whatever
cool
added
a
you
know,
a
description,
annotation
nice
suggestion,
but
we
can
also
run
that
through
kubernetes
and
say:
hey
kubernetes.
Is
that
manifest
valid
line?
Oh
there's,
a
warning!
Okay!
Thank
you.
Large
language
model,
your
your
change
was
lovely,
but
here's
some
feedback.
You
just
got
a
warning
from
that
and
because
it's
a
large
language
model
you
can,
then
you
can
then
kind
of
prompt
it
back
and
say
what.
G
If
that
gave
you
a
warning?
How
would
you
like
you
know,
and
you
can
combine
the
strictness
of
kubernetes
when
it's
going
to
give
you
a
warning
or
not,
and
kubernetes
will
always
know
whether
you
know
a
manifest,
gives
you
a
warning
along
with
you,
know
the
the
generative
nature
to
say?
Oh
well,
if
that
gave
me
a
warning,
maybe
I
missed
a
colon
or
whatever,
and
you
know
after
a
few
iterations,
you
might
have
an
improvement
and
that's
something
we
could
run.
You
know
every
week,
interesting
I.
B
I
think
that's
where
I
could
come
in
and
help.
So
if
y'all
say
like
look,
this
is
Robert.
This
is
what
we
want.
This
is
what
we're
thinking.
We've
got
something
a
proof
of
concept
going,
and
these
are
some
areas
where
we
need
Improvement
like,
for
example,
generative
AI
is
hooked
up
with
GitHub
actions,
it's
doing
a
thing
and
the
reviewer
for
that
PR
is
saying.
Well.
This
should
be
better
that
this
this
would
be
an
improvement
and
getting
that
change
into
the
llm
would
would
improve
it.
B
So
next
time
it
goes
through
with
GitHub
actions.
It
would,
you
know,
not
make
the
same
mistakes
working
with
that
vendor
to
see.
If,
like
okay,
can
you
add
a
feature
here
to
add
feedback
from
a
PR
comment?
Okay,
you
know-
maybe
maybe
we
could
do
that,
but
working
with
those
vendors
that
you
all
select
to
get
them
to
improve
that
that's
something
that
I
can
absolutely
do
once
you
all
decide
once
you
all
say
hey.
This
is
this
is
what
we
want
again.
A
Yeah
I
do
want
to
I,
do
want
to
question
on
GitHub
action
spot
just
because
I
think
across
the
project.
We
don't
use
them
widely,
but
but
Tim
you
might
have
another
opinion
on
that.
A
Another
area
that
could
be
worthwhile
is
as
a
way
as
another
possible
check
in
terms
of
this
is
just
kind
of
me
spitballing
here,
but
we
often
because
of
the
number
of
PR's
that
we
get
if
there
is
a
way
to
trigger
kind
of
certain
checks
when
specific
wording
is
used
in
a
PR
description
that
spell
check
of
X
or
something
of
X,
where,
like
reviews
can
actually
be
done
quite
quicker,
and
you
know
jumped
on
very
quickly
for
especially
for
newer,
reviewers
and
so
on
versus
others
like
that,
could
be
something
worthwhile,
I
think
and
we
can
use
the
the
tagging
that
already
happens
with
the
size
of
the
pr
to
help
with
that
too
yeah
Nate.
F
And
now
that
it's
been
brought
up,
I
completely
agree.
I,
think
that
one
of
one
of
one
of
the
tools-
I
use
quite
a
lot-
is
good.
F
I
would
love
to
be
able
to
connect
a
a
like
a
like
a
copy
editor
like
a
smart
copy,
editor
bot
that
also
understands
our
style
guide
and
is
able
to
say,
okay
well,
this
is
how
is
a
semicolon
and
by
the
way,
pod
should
be
capitalized,
and
things
like
that
which
which
like
like
as
a
copy
edit
pass,
would
be
I
think
a
really
interesting
use
case
to
sort
of
sort
of
even
out
some
of
the,
because
it
takes
a
lot
of
time
to
do
even
that
type
of
editing
and
I.
F
Think
that
it
is
it's
it's
it's
it's
it's
one
of
the
things
that
AI
is
good
at
that
doesn't
sort
of
lean
into
the
to
the
issue
that
or
celebrates
up
AI.
Sometimes
the
interesting
machine
yeah.
A
And
like
another
use
case
I'm
just
thinking
of
for
myself,
knowing
that
the
kubernetes
docs
is,
you
know,
uses
American
English
and
my
own
default.
Isn't
that
I
know
I?
Sometimes
you
know
have
there's
a
lot
of
extra
use
that
I
use
that
shouldn't
be
there,
for
example,
so
things
like
this
yeah
for
a
Tim.
G
So
here
here
we
are
further
down
the
line,
but
imagine
this
this
user
experience
for
a
new
contributor
and
they
open
a
pull
request
straight
away.
A
bot
throws
in
a
comment
saying
hey:
this
is
a
placeholder
we'll
put
some
feedback
here
with
some
some
details
and
then
20
minutes
later
there's
some
feedback
saying:
okay,
yeah,
we
think
you've
misspelled
config
map
here
and
this
these
are
some
style
guides.
Would
you
like
some
suggestions?
G
If
so,
do
you
know
comment
with
Auto
suggest
the
contributor
comes
along
my
new
PR,
what
it
says,
whatever
slash
Auto
suggest
and
now
the
large
language
model
sends
them
17
suggestions
that
they
can
click
accept
on.
B
Yeah,
that's
dependable
is
a
really
good
model
that
in
GitHub
actions,
it's
just
phenomenal
for
that.
You
know
where
you
can
tell
it
to
do
things.
Rebase
a
PR
other
stuff
like
that
like
inside
that
PR
telling
it
to
do
things
I
think
that's
just
a
really
good
workflow
like,
let's
not
you,
know,
I'm
I'm,
a
big
fan
of
avoiding
context,
switching
for
contributors
like
if
they're
in
looking
at
the
pr
great,
let's
stay
there.
Let's
not
move
to
another
place,
that's
just
really
inefficient.
F
F
A
Yeah
yeah
I
think
yeah
like
for
me
off
the
top
of
my
head.
A
The
workload
of
the
smaller
reviews
would
be
the
possible
like
first
thing
that
I
think
could
be
a
really
like
great
way,
for
example
across
our
style
guide,
and
so
on
could
be
a
great
use
of
of
those
kinds
of
resources,
especially
since
we
already
have
some
of
the
ability
to
you
know
take
out
or
what
are
the
excess
and
spr's
that
are
there
and
are
these
are
possible
kind
of
testing
test
test
cases
for
llm.
You
know
jumping
in
and
saying.
A
Oh,
this
is
clearly
a
spell
check
PR,
and
so
we
can
just
provide
the
feedback
this
way
or
whatever
so
I
think
that
could
be.
That
could
be
really
cool
and
would
be
as
someone
who
has
a
very
healthy
dose
of
skepticism
about.
This
would
be
a
great
way
to
prove
to
someone
like
me
that
this
is
actually
super
helpful
and
beneficial
as
well.
Hey.
B
Absolutely
winning
over
you
know,
folks
that
are
skeptical.
It
should
absolutely
be
part
of
any
proof
of
concept
showing
value
to
to
win
hearts
and
Minds.
Absolutely.
A
D
You
know
that
there
are
two
big
camps
of
generative
AI
is
the
proprietary
closed
Source
like
open,
AI,
chat,
GPT
and
then
llama
models
and
an
open
source,
I
I?
Guess
the
alignment
with
the
cncf
would
go
through
a
vendor
that
uses
open
sourced
to
AI
I.
H
Excuse
me,
yeah,
absolutely
I
I
would
hope
so
good.
B
H
B
I
would
hope
that
there
would
be
an
opportunity
for
us
to
let's
say
either
one
of
our
foundations
that
focuses
on
that,
to
bring
them
in
or
to
work
with
a
vendor
that
you
know
wants
to
maybe
create
a
new
llm.
That
is
open,
that
other
people
can
take
advantage
of.
There's
an
opportunity
for
a
new
foundation
around
this
who
knows,
but
I
I
believe
it's
safe
to
say
that
our
preference
would
be
something
that
is
open.
A
I
mean
yes
and
no
I
kind
of
want
to
put
my
hand
like
in
that
conversation,
because
we've
had
instances
in
the
past
where
that
has
been
used
to
not
great
benefit
or
effect.
And
so
we
don't
want
to
push
that
as
a
definitive
possibility.
Just
yet,
because
humans
are
still
very,
very
required
for.
A
As
a
first
step,
definitely
as
a
possibility,
but
as
a
note
we've
had
in
the
past,
people
just
only
submit
machine
translations
and
we
kind
of
have
let
that
slip.
So
we're
trying
to
kind
of
be
a
little
bit
more
strict
for
like
a
better
term
on
that
as
an
outcome
just
yet,
but
it
doesn't
mean
in
the
future
that
couldn't
be
something
when
the
when
the
technology
gets
better.
It's
just
not
there
yet
right
now,.
B
Yeah
agreed,
but
there
there's
another
part
that
he
said
there
about
a
human
being
involved.
We
absolutely
have
to
have,
because
these
are
this-
is
humans.
Reading
this,
and
we
need
to
have
somebody
reviewing
this
to
make
certain
that
it
makes
sense.
Somebody
that
is,
you
know,
knows
that
that
language
and
gets
it
you
know
certainly
translating
idioms
and
and
those
sorts
of
things
absolutely
need
to
have
a
human
there.
B
So
there
might
be
something
that
takes
a
lot
of
time
and
it
would
be
very
challenging
to
use
generative
AI
to
solve,
but
there
might
be
something
two,
three
four
five
on
that
stack
stack
rank
list
that
we
could
take
something
in
the
fives
that
we
could
solve
for,
and
that
does
have
a
big
impact
we
don't
have
to.
You
know,
have
a
moon
shot
on
our
first
attempt
here.
B
It
could
be
something
very
small
to
see
value
and
really
it's
it's
more
about
proving
or
providing
confidence
in
generative
AI
in
this
use
case.
It's
not
just
about
solving
the
problem.
It's
about
convincing
the
team
that
it's
worthwhile
to
continue
exploring.
A
I
think
also
just
capturing
some
of
that
workload
that
we
mentioned
before.
That
is,
you
know,
low
hanging
fruit
for
other
reviewers
and
contributors,
so
that
we
can
kind
of
help
with
the
workload.
If
we
know
that
this
is
a
PR,
that's
a
certain
thing
for
a
style
guide
spell
check,
Etc
like
or
link
updating,
or
things
like
this-
that
it
can
kind
of
help
us
catch
very
quickly
and
easily,
so
that
other
reviewers
can
already
kind
of
jump
in
and
do
that,
work
and
and
push
that
through.
A
So
that,
let's
say
approve,
is
actually
review,
more
blogs
or
like
do
like
larger
PRS,
and
things
like
that.
That
do
take
a
lot
of
our
time,
and
actually
this
tooling
wouldn't
be
a
good
use
for
just
a
good
good
use
for
just
yet
that
would
be.
That
would
be
my
yeah.
That
would
be
my
first
suggestion.
B
It's
entirely
possible
that
y'all
could
start
looking
at
this
and
find
out
that
there's
actually
other
areas
with
Automation
and
other
tooling.
That
is
more
impactful
than
generative
AI.
That
would
be
a
good
thing.
It's
it's
all
about
the
results,
it's
all
about
the
value
that
it
provides
to
Sig
docs.
So
if
it
turns
out
that
the
team
looks
at
this
and
says,
okay,
we
see
value
we're
just
not
really
convinced,
but
we
also
in
exploring
this
found
other
areas
that
were
more
important
to
concentrate
on
and
hey
LF.
B
Can
you
help
us
with
that
tool
chain?
Sure
that's
a
valid
answer
too:
it
doesn't
have
to
be
there.
There's
no
agenda
here.
The
the
number
one
thing
is:
how
can
LF
help
our
documentation
folks
and
create
best?
You
know,
have
Sig
docs,
create
best
practices
and
then
share
them
throughout
the
organization
throughout
all
the
foundations.
That's
really
the
goal.
We
picked
generative
AI
because
all
right
kind
of
got
a
Zeitgeist
thing
going
on,
but
if
it
turns
out
it's
something
else,
great
yay
Improvement
we
won,
so
it
just
doesn't
have
to
be.
B
A
G
So
I
agree,
please
feel
free
to
suggest
things
I'm
going
to
suggest
one
and
I
wanna
I
wanna
encourage
other
people
to
know
that,
like
there
is
a
slack
Channel,
there
are
future
meetings.
This
is
not
the
only
chance
to
come
in
I.
Think
that
hiding
the
git
experience
much
further
would
be
really
helpful
to
contributors
and
might
actually
be
something
where
you
could
one
day
bring
in
generative
AI
into
that
as
well.
G
So
I
stuck
a
link
into
the
sign
Channel
around
dcap,
CMS,
lovely
idea,
Ray
I,
I
am
plus
plus
plus
one
and
a
half
on
that.
Using
my
Tech
lead
a
half
extra
vote
that
I
don't
really
have
yeah.
We
could
do
a
GitHub
discussion,
things
to
I.
Think
all
of
the
things
that
I'm
a
favor
of
are
things
that
make
it
easier
for
new
contributors.
We
don't
need
to
make
it
easier
for
experienced
contributors.
They
already
know
how
to
do
it.
B
That's
valid,
there
was
a
speaker
at
cdcon
last
year
and
when
it
was
in
Austin-
and
she
was
talking
about
cognitive
load
for
developers,
that
was
really
her
Focus
her
area
of
specialty,
where
she
did
a
lot
of
research
and
talking
about
how,
when
new
people
come
in,
to
learn
a
language,
it
is
really
hard
and
to
that
end
she
came
up
with
something
called
Hedy
h-e-d-y,
which
was
an
easier
way
to
Learn
Python
without
knowing
exact
syntax
but
her
Focus.
B
What
really
stuck
with
me
is
like
her
Focus
was
on
the
initial
first
30
seconds.
First,
five
minutes
with
learning
something
new
I
think
focusing
on
that
with
new
contributors
is
worthwhile,
because
how
many
contributors
come
in,
look
at
it
and
say
wow!
This
is
really
hard.
I
I,
don't
want
to
help
anymore
and
and
removing
that
initial
friction
I
think
that's
a
worthwhile
cause.
A
A
And
that
could
be
something
that
once
that
started,
we
can
link
here,
send
that
to
you
Robert
and
send
it
to
a
lot
of
the
different
folks.
You
can
get
their
opinions
kind
of
in
and.
A
And
then
we,
as
leads,
will
take
on
kind
of
looking
at
those
suggestions
and
seeing
what
we
do
want
to
kind
of
push
forward
with
I
would
I
I
personally
would
want
consensus
across
the
leads
group.
That's
co-chairs
and
tech
leads
and
then
and
kind
of
going
from
there
and
we'd
be
able
to
get
back
in
touch
with
you,
regardless
of
what
a
decision
or
yeah.
A
Great
we're
trying
to
when
you're
speaking
of
vendors,
we're
trying
to
use
GitHub
generally
in
terms
of
a
lot
of
the
different
things
that
they
have
in
terms
of
options
and
tooling,
and
so
their
discussions
area
is
something
that
we've
been
able
to
concentrate
a
lot
of
like
longer
form.
Conversations
in
and
I.
Think
calling
all
of
our
days
in
that
one
place
probably
is
the
best.
A
The
best
idea,
wonderful
awesome,
so
I
guess
the
action
item
here
is
I've
I've,
kindly
asked
already
to
create
the
GitHub
discussion
and
then
we'll
link
that
and
then
for
anyone
who's
interested
in
putting
suggestions
up
we'll
we'll
share
that
across
the
slack
Channel
and
do
a
lot
of
different,
sharing
and
kind
of
reminding
of
folks
to
be
involved.
A
In
that
conversation,
I'd
say
a
few
healthy
weeks
of
that
I
think
there's
a
lot
of
people
in
and
around
who
aren't
here
right
now,
who
probably
want
to
get
involved
and
then
maybe,
in
a
couple
of
you
know
a
month
or
two
time
we
can
kind
of
get
back
to
Robert
and
see
where
we've
like
landed
with
that
convo.
A
Great,
so
thanks
thank
you,
Robert
for
coming
to
join
the
meeting
and
and
and
getting
this
discussion
started
and
thanks
everyone
for
your
helpful
suggestions
and
opinions.
There
I've
tried
to
take
as
beautiful
notes
as
I
can,
while
also
trying
to
be
involved
and
moderate
the
discussion.
So
if
you
see
anything
in
the
notes
that,
like
I've
just
incorrectly
kind
of
noted,
feel
free
to
just
change
that
no
worries
at
all.
A
All
right,
we,
we
did
a
a
longer
one
today,
so
I
want
to
thank
everyone
for
sticking
by
and
and
joining
in
the
convo
and
taking
part
we'll
be
back
here
again
in
a
couple
of
weeks.
A
If
we
do
have
a
as
an
FYI,
if
we
do
have
an
APAC
scheduled
meeting
the
same
week
as
a
bi-weekly
Sig
docs
meeting,
we
do
preference
the
APAC
meeting
folks
so
that
they
can
have
a
chance
to
discuss
things
and
be
present
with
each
other
too,
and
we'll
try
and
post
that
a
bit
earlier
than
the
day
of.
Unfortunately,
we
just
kind
of
saw
that
that
last
meeting
a
bit
later
so
we'll
try
and
get
a
couple
of
days
notice
for
everyone.
A
If
there
will
be
a
cancellation
of
this
regular
bi-weekly
meeting.
Okay,
thanks
Big
thanks
to
everyone,
I'll
be
uploading
the
meeting
soon
and
have
a
great
rest
of
your
day.