►
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
A
We
also
have
a
code
of
conduct.
So
please
remember
to
be
excellent
to
me
to
each
other
and
yeah.
We
don't
really
have
anything
at
the
agenda.
We
can
definitely
work
on
the
project
code,
but
I
wanted
to
bring
up
one
topic
about
learning
inactive
members
from
the
oil
we've
talked
about
this
before
and
I.
Think
Bob
you
sent
an
email
to
the
mailing
list
as
well.
B
Sorry
I
am
I,
have
a
draft
I
just
haven't
like
moved
the
PR
up
of
the
changes
to
community
membership,
MD
that
just
have
a
section
regarding
like
inactive
membership,
I
wanted
to
get
that
out
and
then
open
up
a
sure,
PR
in
K
org,
and
send
something
out
to
you,
kiddo.
That
will
probably
happen
sometime
in
the
next
two
weeks.
A
Okay
pageant
board,
so,
firstly,
this
is
the
new
github.
You
I
guess
you
haven't
seen
that
it
is
public
someone
like
someone
from
github
tweeted
about
it.
Sometimes
you
make
it's
okay
to
have
this
on
the
recording
and
yeah,
let's
go
to
the
locked
ones
first
and
then
in
progress
clean
up,
github
service
accounts.
All
of
these
are
really.
A
A
C
So
I'm
also
this.
B
A
D
A
B
The
updated
the
I
asked
for
an
update
on
the
issue.
They
said
that
they
need
to
open
one
more
PR
and
then
they
should
be
good
to
go
to
archive
that
one.
The
only
remaining
one
then
will
be
cubed
AWS
and
that's
the
one,
the
fuzzy
one.
That's
probably
gonna
wind
up
being
a
spun
out
or
you
know
something
is.
E
B
D
A
E
Not
related
to
the
issue,
but
what
do
we
do
with
triage?
Not
today.
A
E
E
C
Yeah
I
guess
that's
I!
Guess
that's
fine
for
now,
I
kind
of
like
ultimately
have
a
hope
that
it
this
run.
The
triage
party
runs
behind
HTH
proxy
instance,
which
might
drastically
reduce
its
token
usage,
but
I
don't
have
the
time
or
bandwidth
to
stand
up
gah
proxy
on
Kate's
in
front
of
clusters
right
now,
it's
somewhere
in
the
backlog.
If
you
want
to
take
a
crack
at
that,
I'd
be
awesome.
But
the
hope
is
that.
E
E
A
A
A
B
E
Ideally
like
this
is
something
that
you
think
we
should
do
or
something
that
we
should
assign
to
the
cigs
to
do.
The
one
thing
I've
noticed
is
that
someone
will
then
ask
like
hey:
can
you
update
membership
for
this
team
at
which
you
have
no
context
of
who
should
actually
be
a
member
of
the
team?
So
maybe
we
should
try
to
charge
this
out
to
the
cigs
and
said.
E
A
A
B
B
B
A
E
Yeah,
so
this
has
to
do
with
the
cloud
provider
consolidation,
so
there
are
teams
from
Lake
City
AWS
a
geyser
that
need
to
be
within
under
cloud
provider.
So
it's
spun
out
into
the
question
of.
Can
we
do
nested
configs
for
parabolas
and
I'm,
not
sure
that
we
have
an
answer
for
that?
Yet
so
I
think
this
has
been
on
hold
and
my
bell
just
rang
so
give
me
a
second.
A
E
C
If
I
remember
correctly,
it
probably
evolved
rewriting
that
command
the
merge
command,
which
I
think
is
responsible
for
taking
the
directory
structure
and
compressing
it
down
into
something
airbus
understands
gotcha.
So
it
looks
like
it's
a
relatively
small
piece
of
code
and
there's
I'm,
assuming
there's
a
bit
of
basil
that
invokes
that
somewhere
it
could.
D
A
E
C
A
E
Think
the
I
think
what
maybe
you
had
mentioned
during
in
that
issue
is
that
we
would
want
some
way
of
determining
that
the
current
members
within
a
sub
org,
like
SIG's,
are
equivalent
I,
guess
we'll
meet
the
bar
for
sponsorship
or
have
been
doing
that
work
to
also
match
kubernetes
membership.
Before
saying
that
this
can
be
policy.
C
I'm,
just
Salus
Christoph
sure
right,
I
wish
Christoph
this
year,
I
felt
like
I
was
like
anybody
added
before
this
stage,
sure
we
can
check
them.
Anybody
added
after
just
go
ahead
and
do
it
and
then
I
think
there
was
pushback,
because
we
don't
want
that.
Add
new
people
before
we
remove
stale
people
I
still
feel
like
it
would
just
simplify
the
world
if
we
just
moved
forward
with
it
as
it
is.
A
C
E
C
E
A
C
So
this
is
somebody
wanting
to
add
a
new
or
to
us
that
we
have
prior
art
or
other
random
words
like
kubernetes,
CSI
and
kubernetes.
Client
question
is:
do
we
pointed
those
two
things
and
say
sure
add
your
random.
Getting
a
board
will
support
that.
It's
not
that
painful
and
careless,
or
do
we
say
actually
we'd
like
everything
to
go
into
community
six
I
feel
like
if
we
make
the
line
of
everything
she's
going
through
in
86.
Should
we
not
do
that?
Kirk,
you
ready
CSI
and
Humanities
client.
E
Yeah
I
think
we
I
I,
think
we've
already
made
that
line
where
we
said
we
were
okay
with
adding
multiple
orgs.
Maybe
if
we
say
that
it's
a
finite
amount
of
multiple
works
like
I
would
actually
be
curious,
what's
in
the
Cosi
work
or
was
meant
to
be
in
the
cozier,
because
it's
not
explained
here
really
outside
of
the
fact
that
it's
supposed
to
be
six
storage
related,
maybe
yeah.
D
C
I
have
a
bit
of
a
problem
with
this
because
that
it's
like
well,
why
don't?
We
have
like
a
kubernetes
cluster
provider
organic?
You
brew,
nettings
cloud
provider,
one
for
all
of
the
various
repos
of
this
sub
projects
I,
like
maybe
that
makes
sense,
but
I
think
unless
we
actually
have
a
well
thought
through
policy.
D
A
E
Point
well:
here's
the
yeah,
here's
the
thing
we
should
be
and
for
the
sake
of
fairness
like
we
don't
have
a
policy
right,
so
we
can't
say
that
there's
an
exception
to
the
policy,
because
there
may
not
be
be
one
that
exists
right.
So
we
have
to
explain
that
like
we
have
to
define
like.
What's
the
we
have
to
say
like
what
is
this
for
where's
actually
four,
and
why
can't
it
live
and
one
of
the
current
works.
A
A
A
Yeah
I
guess
that's
kind
of
at
I
feel
like
we
aren't
doing
too
much
progress
and
read
stuck
in
maintenance
mode
these
days,
but
and
not
everyone
has
bandwidth
but
yeah,
I.
Guess.
If
there's
like
some
things,
you
see
that
people
should
take.
A
look
at
for
people
should
take
approach.
Please
ping,
this
on
slack.