►
From YouTube: 20211006 SIG Arch Conformance
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
This
meeting
is
being
recorded
through
the
cloud
and
you
can
watch
it
later
on
youtube
and
I'm
your
host
around
finance
and
we
adhere
to
the
kubernetes
code
of
conduct,
which
means
being
your
excellent,
the
most
excellent
self
towards
everybody
in
the
meeting
and
we
have
a
fairly
thin
attendance
but
as
an
agenda.
So,
let's
start
with
the
first
point
on
the
agenda:
api
service
status,
life
cycle
test.
A
B
Jordans
pointed
out
because
the
test
is
using
some
rpac
as
part
of
the
initial
setup
that
and
as
now
our
back
is
no
longer
available
for
conformance
that
we
need
to
address
it
so
pretty
much.
The
current
attack
is
that
I'll
strip,
the
setup
so
that
it
doesn't
have
any
rbac
components
and
hopefully
we'll
be
able
to
see
whether
or
not
we
can
still
have
the
same
results
for
changing
the
service
status
in
points.
B
Yeah,
it's
remove,
hey
steve
yeah,
the
yeah.
The
current
are
back
components
in
the
setup,
just
need
to
be
stripped
out
and
then
we'll
see
if
the
test
is
able
to
be
a
little
bit
more
simpler,
as
jordan
has
requested.
A
C
D
A
C
Just
even
as
well
on
the
neat
agreement
on
the
way
forward
or
ld
approval,
where
we've
just
noted.
Yes,
we
noted
it.
But
do
we
need
to
get
some
lgtm
or
approve
on
this
forward
or
go
ahead
and
just
do
the
removal
and
then.
C
B
B
Oh
there's
three
dots
on
the
right.
I'm
happy.
C
C
A
B
Yeah,
so
if
we
switch
across
to
the
files
changed,
so
the
key
here
was
to
create
a
separate
function
that
will
encapsulate
the
redirect
component
from
the
original
upgrade
aware,
go
file.
So
we
can
now.
B
If
we,
if
we
go
down
a
little
bit,
there
is
the
remote
I
got
removed
and
then
we've
I've
added
in
a
a
check
so
that
we'll
do
a
return.
B
If
proxy
redirect
is
becomes
true
and
I've
gone
through
and
done
a
test
with
kind
and
api,
snoop
and
everything's
good,
and
the
unit
test
here
is
going
through
and
checking
on,
get
head
put
and
delete
and
for
the
heading
head
and
get
it
does
come
back
with.
A
301
is
what's
expected
so
in
so
those
are
the
expected
results
so
further
down
and
the
actual
code.
B
Oh
sorry,
sorry
a
little
bit
further
up
yeah.
So
once
we
set
up
the
new
request
based
on
the
test
method
and
pass
we'll
be
able
to
then
look
at
doing
a
check
to
see
whether
a
redirect
is
is
going
to
go
through,
and
then
we
check
the
response
back
from
the
headers
on
11
17.
B
so
and
then
we'll
be
able
to
get
the
status
code
and
also
check
the
headers
below
that
as
well.
If
we've
got
a
301,
if
it's
a
200,
there's
no
headers
that
have
been
written,
so
there's
no
way
to
check
the
the
path
at
this
stage
in
this
part
of
the
code
blog
that
we're
testing
but
yeah
back
in
the
conversation
at
the
top,
I
still
gotta,
just
it's
close
to
the
very
bottom
there
is.
B
There
is
some
manual
tests
that
I
did
a
little
bit
further
up,
but
further
up
yeah
a
little
bit
further
up
so
yeah,
sorry
yeah.
So
these
manual
curl
tests
that
I
did
historically
I've
already
gone
through
those
manually
and
they're
all
exactly
producing
the
same
sort
of
results
that
I'd
expect.
B
So
probably
the
only
issue
here
is
doing
a
follow-up
with
jordan
to
see,
if
he's
all
happy
with
that.
C
C
B
Bit
is
for
doing
the
seven
points
for
the
pod
endpoints
and
then
there'll
be
another
seven
that
will
be
for
service
as
well,
so
that
gets
the
14
in
total.
A
Sorry
for
that,
that
is
really
nice,
as
we
don't
have
jordan
in
the
meeting,
and
he
was
our
key
advocate
and
supporter
for
this.
Maybe
I
think
if
we
reach
out
and
slack
after
the
meeting
and
say,
can
you
we
please
have.
A
And
this
would
help
us
sorry,
clayton
nathan,
jordan,.
A
C
C
Also,
I
think
there
was
there
were
push
changes,
and
maybe
there
was
an
issue
with
the
bot,
not
removing
the
prior.
B
C
Regarding
this
pr
having
changes
pushed
and
the
approve
approve
not
being
removed
I'll
I'll,
this
will
leave
that
on
steven.
B
A
A
Beautiful
work
thanks
then
individual
endpoints
yaml
has
been
updated.
We
added
the
rbac
endpoint
in
that
pr
there
that
take
us
down
to
less
than
75
endpoints
of
conformance
testing
to
be
done.
Okay,
it
merged
23
days,
yep
it
it's
merged
in
and
it
is
off
the
list
all
right.
I'm
excited
to
see
that
so
yeah.
That's
that
moved
things
forward
and
less
than
75.
D
Yeah,
I
just
wanted
to
bring
some
awareness
and
ask
some
feedback
since
you
have
a
lot
of
experiences
conformance
tests
and
it
may
be
useful
for
node
conformance
as
well
yeah.
So
this
is
a
document
we
have.
I
mean
sig
note
tests,
I
mean
there
are
a
lot
of
tests
and
signals
and
there
is
like
cluster
tests
and
there
is
a
like
a
node
test
as
well.
D
So
there
is
a
little
bit
of
difference
how
we
run
things
and
in
the
past
I
I
don't
know
the
history
exactly,
but
I
know
in
the
past
somebody
created
them
new
tags
for
node
tests
and
the
task
tags
were
not
feature
and
not
conformance.
D
I
believe
the
long-term
goal
was
to
roll
out
node
conformance
into
some
form
of
conformance
tests,
mostly
to
conform,
not
distress
of
kubernetes,
but
rather
around
times
that
kubernetes
run
against,
so
to
make
sure
that
if
you
supply
a
node
and
configure
a
node,
it's
not
as
conformant
with
all
the
behaviors
that
we
promised
to
our
customers.
So,
let's
say,
runtime
can,
I
know,
can
properly
set
up
all
the
like
storage
or
like
runtime
can
like
give
you
all
the
proper
metrics
that
required
by
kubernetes.
D
D
We
may
need
to
rename
it
to
something
else,
but
this
is
not
a
point
of
what
I
wanted
to
bring
up
today,
so
I
wanted
to
so
I
wanted
to
clarify
how
we
use
that
conformance
today,
and
I
I
think
we
need
to
document
it
in
test
infra,
so
node
conformance
today
will
like,
without
this
proposal,
will
indicate
that
the
functionalities
that
is
covered
by
the
test
supposed
to
be
working
on
all
distress
of
kubernetes
and
all
run
times.
D
And
not
conformance
like,
and
if
it
doesn't
work
on
all
distress
or
it
doesn't
work
on
all
run
times,
then
we
will
use
a
flag
feature
that
will
indicate
that
this
is
subset
of
functionality
that
doesn't
work
everywhere
and
if
it's
work
for
you,
you
can
test
this
feature
for
your
environment
or
for
your
not
like
for
your
distribution
and
such
so
yeah.
So
it's
kind
of
too,
like
test
can
either
be
conform,
not
conformance
or
it
can
be
marked
as
feature.
D
D
D
When
feature
gate
is
in,
alpha
is
disabled,
but
when
it
go
to
beta,
it
started
being
enabled
so
practically
what
we
see
that
all
the
kubernetes
installations
have
all
the
beta
feature
enabled.
This
is
typical
pattern
and
let's
say
we
have
a
feature
that
recently
were
added.
That
iv
writes
termination
grace
period
for
probes,
so
with
this
feature,
it's
still
in
beta,
but
it's
enabled
almost
everywhere,
like
virtually
everywhere
with
a
new
version
of
kubernetes,
and
we
don't
want
to
mark
this
feature
because
we
wanted
this
feature
to
be
actively
tested.
D
So
we
want
to
mark
there's
not
conformance,
so
the
proposal
is
that
even
for
beta
feature
gates
for
beta
functionality,
we
still
will
apply,
not
conformance
stack,
and
I
was
wondering
like
how
how
like
I
know
conformance,
is
not
the
same
way
conformance
only
applicable
when
features
in
ga
right.
So
I
was
wondering
if
this
was
ever
a
question
like
was
it
ever
discussed
like
how.
C
Areas
right-
and
I
think
for
the
and
the
conformance
program
itself
for
providers
we're
trying
to
make
sure
that
the
surface
area
available
to
to
orchestrate
basically
the
kubernetes
api
server
and
everything
behind
it
is
the
surface
area
of
concern
and
that
creates
its
own
ecosystem
of
don't
say
that
it's
a
it's
kubernetes,
really
not
conformant
kubernetes,
without
going
through
those
procedures
and
submitting
something
with
I'm.
If
I
were
to
simplify
this
for
the
the
c,
the
cri
for
the
container
runtime
interface,
which
is
a
little
it's,
this
is
more
than
that
right.
C
C
Plus
the
cri
and
and
having
that
because
again
with
conformance
what
we're
trying
to
do
in
the
other
area,
is
that
you
could
completely
rewrite
it
in
rust
and
that's
that's
from
another,
a
different
surface
area,
and
so
you
in
thinking
of
what
it
looks
like
to
have
a
conformant,
kublet
api
interface.
C
That's
standardized,
regardless
of
the
underlying
cri
implementation
or
plumbing,
or
all
the
things
like.
It's
it's
being
really
really
clear
about
what
we're
trying
to
make
conform
it
and
in
determining
the
amount
of
surface
area
that's
available
to
change
and
ensure
that
the
behaviors
are
consistent.
C
D
Yeah-
and
there
is
no
definition
whatsoever
and
that's
why
not
conformance
is
not
the
best
name.
It's
not
the
c.
I
mean
it's
same
by
intention.
The
intention
is
to
say
no
even
by
intentions
are
the
same
intention
is
to
say
that,
like
every
installation
will
behave
this
way
and
will
implement
this
kind
of
functionality,
this
set
of
functionalities
yeah.
We
don't
intend
to
like
replace
runtime
or
anything
like
that.
We're
just
saying
that
all
run
times
needs
to
work
this
way
and
we
will
work
this
way
with
runtimes.
C
How
much
of
that
is
cri
and
how
much
of
that
is,
is
kublet
and
is
there
a
way
to
specifically
look
at,
for
example,
the
swagger
open
api
spec
for
the
kublet
interface
to
have
a
surface
area
to
look
at
including
all
of
the
methods
and
objects
behind
those
methods
in
the
same
way
of
looking
at
something
for
the
cri
runtime
and
looking
at
those
surface
areas.
So
where
do
the
current
set
of
in
this
case,
I'm
guessing
they're
in
the
kubernetes
tests,
ede
folder.
C
Okay,
so
the
thing
is,
as
you
get
to
the
what's:
globally
depended
on:
initially
there
was
only
nine
percent
of
the
kubernetes
api
that
had
any
sort
of
tests
and
all
of
a
sudden
we've
got
all
these
people
in
the
world
depending
on
this
functioning
in
this
way-
and
so
we
said
well,
maybe
we
should
have
a
formal
definition
of
what
this
expectations
can
be
met
and
shared,
and
so
that's
when
actually
since
we're
since
we're
on
storytelling
mode
for
a
moment,
if
you
go
over
to
ii
and
zed,
there's
a
fun
story
over
back
on,
because
this
is
all
very
relevant
to
the
journey.
C
I
think
it's
under
blog
yeah
back
in
the
dan
con
sedan.
C
It's
a
great
story
here
around
the
relationships
and
and
and
the
definition,
but
it's
in
2017
we
were
in
germany
and
and
ken
omichi
was
looking
in
the
logs
and
said:
there's
not
so
many
tests
and
and
dan
said.
Well,
we
got
to
define
what
this
is
real
good,
so
we
he
shared
his
screen
on
what
was
on
his
desk.
C
This
is
dan's
disc,
for
what
storage
and
it's
just
the
visualization
of
that
and
that's
where
we
came
up
with
what
would
be
api,
snoop
and
zach
did
some
things
and
some
test
writing
which
this
is
steven
here,
and
we
got
through
to
have
this
this
initial
definition
by
115
and
you'll
notice.
It's
always
focused
on
the
green,
because
at
that
point
it's
not
only
enabled
by
default
and
has
been
able
enabled
by
default.
It
is
an
absolute
expectation
to
be
generally
available,
which
is
why
we
call
it
ga
versus
something
else.
C
Beta
means
it
can
be
turned
off
and
is
not
expected
to
be
everywhere.
So
if
you
go
to
api
snoop,
the
the
first
page
of
that
is
actually
showing
alpha
beta
and
stable,
so
you
could
click
on
those
to
see
what's
there
and
I
think
for
for
us
what
it
allows
us
to
do
is
start.
Having
those
conversations
hey
welcome
to
the
api
you're
going
to
be
alpha
for
a
bit,
you
might
change.
C
We
may
never
see
you
again
and
that's
fine
we're
not
going
to
depend
on
you,
but
we're
going
to
make
sure
we
know
what
the
surface
area
looks
like
and
there
will
there
there's
not
conformance
tests
that
that
hit
those
hit,
those
things,
because
if
we
limit
to
only
show
conformance
eligible,
then
it's
always
going
to
be
just
stable.
That
big
check
box
right.
There
is
what
you're
kind
of
asking
like
do.
C
We
do
beta
no
and
okay,
but
I
think
it's
important
to
understand
like
because
of
the
feature
and
what
you're
expecting
from
your
audience
in
this
case
is
from
your
runtimes.
Do
you
kind
of
want
them
to
be
figured
out
a
little
earlier
than
beta
and
we
actually
had
a?
I
forget:
was
it
a
couple
of
years
ago
rhian
where
we
in
the
conformance
group
were
trying
to
figure
out?
How
do
we?
Because
we
have
the
information
to
collect
if
we
could
go
ahead
as
part
of
the
conformance
program?
C
Have
people
run
a
bunch
of
tests
to
see
for
those
beta
apis
enabled
they
wouldn't
be
part
of
conformance
you'd,
still
get
your
shiny
badge
and
say
absolutely
for
the
generally
available
things
for
the
whole
world
you
pass.
But
how
did
you
do
for
these
things
that
are
in
beta
and
having
that
report
able
to
make
informed
decisions?
One
about
the
number
of
adoption,
because
it
is
optional?
C
How
many
companies
turn
that
particular
beta
thing
off,
because
that
may
mean
that
either
it
was
it
conflicted
with?
I
think
it's
a
bit
and
it's
it's
a
obviously
a
forced,
an
encouraged
submission
from
in
this
case
you're
talking
about
the
cri
runtime.
C
B
C
General
ci
system
for
ci
signal
to
go:
hey
we've
noticed
that
these
various
runtimes
are
in
and
with
the
beta,
because
then
it
actually
gets
into
it's
nests,
important
about
what
you
call
conformance
and
more
about
who
you're
informing
that
there's
been
variation
and
that's
getting
involved
with
sig
release
and
and
you're
the
sig
in
charge
of
that
api,
in
this
case
sig,
sig,
node
and
having
those-
and
I
think,
that's
where
I'm
trying
to
get
some
clarity
on
your
beta
like
I
need
to
go
through
and
read
this
so
I
haven't.
C
D
It's
exactly
the
thinking
that
we
had
regarding
beta,
that
we
need
to
get
ready,
that
beta
will
be
available
everywhere
and
we
want
to
make
sure
that
it's
being
tested.
So,
if
you
as
a
company
as
a
platform
provider,
run
your
own
set
of
tests,
please
run
this
test
as
well,
because
it's
important
to
be
to
be
working,
you
can
disable
it
still.
D
If
you
disable
this
feature
gate,
but
if
you
have,
it
enabled,
please
make
sure
it's
working.
Otherwise
we
will.
Our
customers
will
have
some
troubles.
C
Sarah,
I
think
it
would
be
important.
I
definitely
want
to
go
through
this
asynchronously
a
little
more
deeply,
but
I
think
your
your
audience
for
this
is
well.
It
does
have
a
lot
of
conformance
information.
I
think
sig
architecture
is
probably
the
right
audience
to
help
you
with
this
call,
because
this
isn't
kind
of
a
sig
sig
release
in
helping
the
defense,
but
defining
what
we're
supposed
to
release
in
that
process
is
actually.
D
Was
it
ever
an
issue,
because
today,
like
we
have
some
tests
that
supposed
to
be
working,
but
they
only
work
if
you
pre-install
something
on
environment
like
runtime
class,
if
you
install
this
runtime
class
configured
and
run
in
cri,
then
it
will
be
working
like
tests
will
pass.
But
if
you
haven't
configured
that
and
functionality
is
not-
I
mean
there
is
nothing
to
test,
because
you
you
can
only
test
the
functionality
of
this
thing
present
on
the
environment.
C
Those
things
if,
if
they're,
optional,
they're,
not
required
and
conformance,
is
for
all
non-optional
generally
available
every
because
this
is
part
of
if
you
were
to
have
an
rfc
things
in
conformance
are,
must
you
cannot
be
called
kubernetes
without
this
and
what
you're
talking
about
at
that
point
is
may
or
should,
as
always
like
go
check.
The
rfc
definition
then
find
I'd
almost
write
it
in
that
verbage
of
should,
and
then
you
can
have
these
extra
things
on
the
side
that
say
well,
it
is.
C
It
is
conformant
to
what
is
absolutely
required
in
ga
and
at
beta,
it's
kind
of
like
it
could,
because
it
could.
Anything
in
beta
is
always
going
to
be
good
and
and
should
is
encouraged
and
and
it's
definitely
on
by
default
and
something
like
our
back.
For
example,
our
back
is
not
part
of
conformance,
and
we
actually,
you
saw
earlier
in
the
call
today
where
it's
taken
this
many
years
to
go
yeah.
No,
it's
not.
C
It's
actually
not
part
of
the
definition,
but
I
would
be
hard-pressed
to
find
a
kubernetes
deployment
anywhere
that
doesn't
use
rbac
and
then
the
same
thing
for
ingress
right.
In
order
for
ingress
to
work,
it's
going
to
be
some
stuff
in
order
for
storage,
to
work,
it's
going
to
be
some
stuff
and
it's
up
to
sig,
storage
and-
and
I
want
to
sig
networking.
B
C
Ingress
to
kind
of
ensure
that
those
shoulds
work,
but
as
far
as
the
the
global
definition
of
ga
kubernetes,
because
they're
optional
they're
not
part
of
a
requirement,
so
things
like
s,
what's
it
called
k3s
k3
k3s
can
do
its
thing
in
a
way.
That's
not
it's
conformant
right,
but
it
doesn't
do
all
of
the
things
that
you
already.
You
know
it's.
D
Yeah,
I
don't
know
like,
I
feel
it's
also
different
with
note
conformance
and
another
reason
to
not
call
it
conformance,
because
what
we
want
to
express
is,
if
swap,
is
enabled
on
a
node,
then
you
absolutely
have
to
perform
this
way
and
respect
this
like
this
way.
If
it's
not
present
on
a
node,
then
you
still
have
defined
behavior
but
like
it
doesn't
involve
any
small
features.
C
Because
of
the
overloaded
wordness
of
conformance,
I
think
it
might
be
wise
to
choose
something
similar
like
behaviors
or
or
node
behaviors
or
or
I
I
just
node
behaviors
would
be
good
because
it
is
there's
multiple
behaviors,
it's
okay,
to
not
have
these
behaviors
and
conf
in
a
conformant
kubernetes
distribution,
but
it
is
required
if
you
turn
on
these
features
and
that
feature
flag.
Conversation
of
is
this
feature
enabled
or
not
around
the
normal
flow
of
of
sig
release,
and
all
of
that.
C
How
that's
also
loaded
is
almost
it's
similar,
but
not
the
same
conversation
because
you're
it's
while
the
features
might
be
enabled
it's
not
about
the
flow
of
that.
It's
about
the
testing
of
the.
If
it's
the
node
possesses
this,
because
sometimes
that's
not
a
feature
of
kubernetes,
it's
a
feature
of
the
node
and
see
which
of
the
nodes,
so
the
ability
of
a
node,
and
so
there
won't
be
a
feature
flag
necessarily
for
let's
use
gpu.
C
Just
because
that's
something
fun,
that's
hardware
related,
but
we
probably
should-
and
we
shouldn't
require
that,
in
conformance
the
definition
for
the
global,
everybody
should
have
gpus,
but
we
definitely
want
to
have
a
thing
somewhere
within
signone.
That
says:
if
there
is
a
gpu,
then
let's
do
the
gpu
thing
and
ensure
globally,
that
on
across
all
the
runtimes
that
that
piece
of
hardware
is
available
to
the
cluster.
C
We
want
that
part
of
the
release
cycle,
so
it
needs
to
be
release
and
forming.
So
I
think,
if
you
look
through
all
of
the
sig
release
flow
and
the
and
sig
testing's
infrastructure
underneath
to
help
create
for
ci
signal
and
definitely
those
ci
signal
things
for
sig
node
are
probably
already
in
place.
But
it's
when
you
get
to
the
release
in
forming
that's
important,
so
you
can
actually
release
and
form
on
those
beta
things
that
are
a
requirement
for
that
release
like
so
I'm
just
throwing
gpus
up
there.
C
But
for
that
and
having
that
conversation
with
cigarette
sig
architecture
and
creating
those
ci
jobs
that
are
released
and
forming
that
do
block
us
moving
forward.
So
they're
important
but
they're,
not
part
of
everybody,
defining
what
kubernetes
is
globally
they're,
just
ensuring
that
our
artifacts
that
we
produce
as
a
community
do
what
they
say.
They're
going
to
do.
D
Yeah-
and
I
think
many
things
already
done
right
in
kubernetes-
I
I
mean
it's-
we
already
have
release
blocking
tests
there
and
like
it's
just
some
cleanup
and
documentation
needed,
because
we
see
more
and
more
confusion
as
people
implement
new
functionalities.
I
I'm
even
afraid
to
call
it
feature
because
feature
is
also
such
an
overloaded
term.
D
Yeah,
thank
you
for
feedback
and
absolutely.
C
Yeah,
thank
you.
It's
a
pretty
lonely.
We
we,
we
often
think
of
what
the
conformance
team
and
iii
do
is
washing
the
dishes
in
the
kubernetes
community.
You
all
got
to
get
done,
but
sometimes
you
just
got
to
have
some
staff
on
call
keep
the
kitchen
clean,
keep
stuff
flowing
and
we're
absolutely
happy
to
serve
and
and
support
in
any
way
we
can.
D
C
C
If
you
look
at
this,
this
fun
chart
like
that's
the
chart,
but
if
you
go
to
actually
api
snoop
and
you
look
at
there's
a
big
drop
down
for
which
releases
to
look
at
and
they're
all
in
order
here
and
I'm
super
proud
to
see
like
look
at
this
thing,
it's
all
all
filled
in
particularly
for
it
let's
go
and
just
show
conformance
right
so
that
that's
really
really
really
filled
in
there's,
not
that
much
to
go.
Oh
my
gosh
for
80,
81
percent
yeah.
That's
awesome!.
A
A
Well,
that's
no
loading,
so
did
you
know
sick
arch
meeting
is
tomorrow
at
I
think
7
a.m
or
8
00
pacific.
So
if
you.
C
Thank
you
at
119
over
here.
You
can
see
that
we
had
166
endpoints
that
were
there's
no
test
at
all
and
then
there's
a
new
endpoints
promoted.
So
they
added
all
this
extra
debt
extra
debt
extra.
We
finally
got
a
hold
on
added
extra
debt
somewhere
around
115,
a
couple
of
ones,
one
one
would
slip
through
now
and
then,
but
not
too
bad
oops.
Who
is
this?
Let's
get
these
who's?
This
delete
core
everyone,
namespace
service,.
B
That
relates
to
time
did
some
clean
up.
C
It's
something
that
we'll
have
to
swing
back
swing
around
too
later
in
the
release,
but
we're
down
to
freaking
74
in
points
left
after
because
it
got
up
to
this
highest
point
was
226
for
the
releases
and
if
we
look
at
the
coverage
over
there,
we're
slowly
going
back
in
time
and
getting
rid
of
all
the
debt
like
we're
still
working
on
111
and
okay
can't
click
on
these,
because
we
know
about
what
what
those
apis
are
by.
C
Looking
at
that
at
that
front
page,
we
should
get
open
a
ticket
with
zach
and
and
don't
let
him
do
it,
but
pair
with
him
on
figuring.
Why
these
older
things
aren't
there
because
part
of
a
good
story-
and
I
think
I
have.
A
C
Let
us
know
how
we
can
be
your
advocate
for
the
cigarch
meeting
tomorrow.
I
will
be
sure
and
read
through
this
today
and
so
that
I
have
actually.
B
C
D
C
Yep
drop,
I
would
to
get
more
feedback,
send
an
email
to
the
cigar
mailing
list
asking
for
this
to
be
on
the
agenda
and
then
add
it
to
the
agenda
and
then
drop
it
into
the
cigar
slack.
I'm
just
the
way
to
amplify
your
voice
is
to
make
sure
that
it's
in
all
of
the
channels
of
cigarettes,
mailing
lists
cigarette
thing
and
on
the
meeting
and
since
you're
about
24
hours
before
the
meeting,
it's
excellent
time
to
do
that.
D
Okay,
I
will
do
it
after
this
mission,
thanks
for
otherwise
yep.