►
From YouTube: Community Meeting, August 10, 2023
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
Okay
with
that
being
said,
let
me
pull
up
the
agenda
meet
the
agenda
issue
for
today.
A
I
am
still
working
on
the
Google
Docs
agenda
topic
and
that,
unfortunately,
is
not
resolved
yet
and
I
know
that
the
past
community
meeting
is
also
not
uploaded
to
YouTube,
yet
I
also
still
have,
as
also
have
that
still
on
my
list
of
things
to
clarify
with
that
being
said,
let's
take
a
look
at
the
agenda
for
today.
A
I
don't
know
I,
don't
do
not
believe
that
Tim
is
joining
us
today.
He
brought
up
a
topic
on
the
last
community
meeting
notes,
but
we
canceled
that
but
I
guess
he
did
not
have
the
chance
to
join
us.
So
maybe
he
will
bring
it
up
again
for
future
meetings,
because
I'm
also
not
quite
sure
what
his
concerns
or
what
his
questions
were.
A
Just
a
very
brief
update
on
the
kcp
io
website
work.
I
did
some
work
on
that
I
just
wanted
to
check
in
with
everyone,
just
give
a
brief
update
on
it.
The
blog
section
now
has
this
theme,
so
blog
posts
are
now
available
in
when
you
run
the
pr
locally.
It's
not
quite
done
yet,
but
I
want
to
make
the
pr
ready
for
review,
hopefully
within
the
next
two
weeks
and
then
maybe
after
some
more
reviews.
I
can
also
share
some
images
there.
A
B
A
B
C
And
also
the
the
API
groups
of
the
various
apis.
Yes,.
B
B
Yeah
so,
and
that's
what
basically,
what
I'm
suggesting
is
basically
to
do
this
one
potentially
and
at
this
point,
there's
still
few
a
few
open
issues,
but
I
didn't
have
time
to
work
on
those
basically
and
I.
Think
the
long-term
plan
is
still
to
have
the
it
has
a
plug-in.
Not
it
is
the
extension
just
basically
wanted
to
give
an
update
small
one.
So
if
people
are
interested
and
want
to
try
it
in
a
current
state,
you
can
now
Point
them
to
that.
Repository.
B
C
I
have
a
meeting
with
with
Yasin
who
was
asking
some
some
question
technical
questions
about
about
how
TMC
works,
and
especially
you
know,
status,
aggregation
and
the
Sinker
and
the
virtual
workspace.
So
we
had
a
discussion
about
that
sort
of.
C
You
know
knowledge
transfer,
if
you
can
say
so,
that
might
be
interesting
and
to
to
look
back
so
I
saw
you
create
a
new
project,
kcp
no
TMC
contrib,
where
mainly
there
are
some
issues
about
the
things
that
don't
work
anymore
after
the
migration,
but
also
in
the
existing
kcp
project,
so
that
that
was
used.
C
Previously
there
are
a
number
of
epics
of
Unfinished
work
in
in
the
the
TMC
that
might
be
worth
looking
into
because
there,
unfortunately
not
all
the
issues
are
documented,
as
they
should
have
been,
but
at
least
there
is
sort
of
you
know
the
skeleton
of
the
upcoming
design
here
in
terms
of
Concepts,
like
coordination,
controllers
and
and
so
on
and
so
yeah.
D
You
know
two
questions
so
I
just
saw
that
so
DMC
is
contract
TMC
at
the
moment
towards
the
Repository
called
trip.
Dash
TMC.
Should
we
so
coming
back
to
the
previous
topic?
Should
we
maybe
at
country
kcpio
as
a
domain,
something
like
that.
A
B
D
So
the
second
question
I'm
not
sure
David
you
mentioned
that
sharding
likes
a
question
about.
There
wasn't
PR
right,
you
had
in
the
yes.
C
Exactly
so
mainly,
this
was
nearly
down,
at
least
in
the
Sinker,
and
the
only
remaining
work
was
changing
all
the
end-to-end
tests
on
the
GMC.
You
know
side
so
that
all
the
tests
are
also
made,
but
in
the
Sinker
itself
at
least,
and
the
virtual
workspace
things
were
working,
it
seems
that
there
was
something
blocking
when
sorry,
if
I
don't
pronounce
correctly
migrating
the
the
whole
with
I
think
informers.
Something
like
that,
but.
C
One,
no
that
was
merged
I
mean
the
main
mirror
was
much
as
far
as
I
know,
but
then
some
some
parts
of
it
had
to
be.
You
know
disabled
during
the
migration,
if
I
understand
correctly.
B
C
Be
available
to
you
know
just
take
part
in
a
troubleshooking
session
or
something
like
that.
Yeah.
B
I
think
we
might
want
to
share
somebody
that
basically,
it
was
a
client
setting
up
Shenanigans,
because
we
can't
really
usefully
the
clients
and
identities
from
kcp
when
extending
yeah
I
just
got
lost
in
the
sea
of
the
informers.
So.
C
Yes
and
I
assume
it
it's.
Yes,
it's
related
to
clients
and
to
the
fact
that,
according
to
the
client
identity,
you
cannot
access
from
a
I
mean
from
outside
or
from
a
given
chart.
Yeah
I
mean
we
have
just
to
to
to
precisely
understand
exactly
the
structure
it
has
to
to
have
now,
but
I'm
I'm,
quite
optimistic
on
this
one
that
you
know
structurally
I,
don't
see
why
it
should
not
be
possible.
G
F
B
D
Yeah
just
saying
it's
an
application
topic.
We
have
to
externalize
that,
but
it's
a
library,
so
you
can
probably
use
that
and
run
your
own
application
controller
and
we
have
to
talk
about
it.
C
Yes,
on
the
other
hand,
now
everything
has
to
I
mean
for
now.
The
only
thing
that
that
could
replicated
were
all
the
objects,
which
are
you
know,
Common
to
the
main
workload
and
and
TMC
apis.
So
the
Sim
targets
the
stuff
like
that.
But
then
you,
you
mainly
you
are
thinking
from
a
given
workspace
so
from
a
given
chart
or
possibly
a
number
of
of
limited
charts
to
a
physical
cluster.
So
you
don't
expect
all
the
other
of
the
audio
objects
that
should
be
synced
could
be
Shady.
C
Yes,
it's
it's
about
location,
sync
targets
and
and
all
these
objects,
but
these
were
already
replicated.
F
Yeah
yeah,
but
if
we
externalize
TMC,
is
not
bad
for
the
core.
C
I
completely
agree
and
that's
a
wider
topic,
because
then
you
have
also
the
accesses
to
some
API
exports,
the
fact
of
listing
API
exports.
You
have
a
number
of
other.
You
know
challenges
as
soon
as
we
want
to.
You
know,
have
a
plugin
on
top
of
of
kcp
and
not
a
dedicated
binary.
C
I
saw
another
parent
in
the
about
the
TNC
about
how
to
say
that
maybe
I
should
find
like
the
the
issue,
the
fact
that
it
doesn't
sink
on
on
user
workspaces,
but
only
on
the
location
workspace.
Something
like
that
am
I
right.
F
Yeah
I
think
MJ
can
talk
a
bit
more
about
that.
We,
when
we
we
moved
at
something.
B
I
think
there
was
a
bug,
you
know
a
kcp
code
which
basically
was
obfuscated,
but
basically
index
server
is
built
a
bit
differently.
It's
always
was
defaulting
to
the
shards
indexer,
which
result
it
back
to
itself
and
got
the
result
because
we
removed
A
Shard
index
there.
It
goes
the
local
one
which
basically
is
wrong.
So.
C
Okay,
so
anyway,
yeah
just
just
feel
free
to
reach
out
directly
to
me
for,
for
you
know
those
issues
that
might,
if
I
might
help
to
enrich
the
statues
where
I.
B
Live
yeah
the
one
thing
which
I
tried
to
move
it
already
to
the
outside
being
on
the
part
of
the
both
extension.
Basically
not
privileged
and
I,
ran
the
biggest
issue
which
I
ran
into
is
the
usage
of
dynamic
clients
for
the
Sinker
in
a
virtual
workspace
context,
and
that
basically
got.
This
is
why
I
stopped
basically
moving.
That
I
think
might
be
issue
for
The
Wider
TCP
too,
because
currently
API
exports
are
very
like
permissions
and
API
exports
are
typed
like
very
strict
type
where
it
comes
for
for
skin
care.
A
E
H
Yes,
it's
about
shorting,
also
in
Cube
stuller.
We
are
also
using
yeah.
We
have
our
own
Sinker
and
it
also
uses
generic.
So
you
know
the
points
being
discussed.
We
just
discussed
are
probably
relevant,
but
I
have
to
admit
I'm
basically
lost,
there's
as
far
as
I
know,
no
actual
documentation
of
how
sharding
works
or
what
it
means,
or
anything
like
that
right.
H
H
H
You
know
that
that
other
people
using
this
code
can
use
to
understand
what
it
does
and
what
it's,
how
it's
intended
to
be
used.
What's
intended
to
accomplish
I
I,
don't
know
what
sharding
is.
D
Yeah
I,
don't
disagree.
I
just
wanted
to
check
whether
we
have
something
in
in
the
docs
folder
I
didn't
find
it
quickly,
so
I
think
I
and
lukash.
We
have
to
sit
down
and
just
brain
dump
everything
yeah
cash
server
is
one
one
part.
Oh
this!
That's
actually
a
document.
Okay,
but
I
think
this
is
very
low
level
right.
If
I
remember
right.
B
Yeah,
that's
that's
like
the
main
question
which
I
got
from
all
this
was
as
a
layer
building
on
top
of
kcp.
How
should
they
build
my
stuff
to
be
short
compatible,
basically
to
be
cash?
Server,
compatible
yeah
means
like,
if
I
put
all
my
stuff
into
one
virtual
workspace
and
spread
it
via
API
bindings.
C
H
D
Had
some
some
document-
Google
Docs,
maybe
or
Google
figure
Graphics
whatever
the
name
is
but
I-
think
I
lost
access,
so
so
I'm
not
there
anymore
anyway.
So
let's
ride
stock
Mike.
If
you
want
to
create
an
issue
for
that,
assign
it
to
me
I'll
do
that
ping
me
and
Lucas
in
the
in
the
channel.
So
we
don't
forget
would
be
helpful.
C
Maybe
if,
if
I
can
again
0.22
a
question,
there
is
also
an
an
issue
or
pending
issue
about
TMC
ISO
was
about
the
tuner
which,
if
I
understand
correctly,
doesn't
work
anymore
as
well
and
I
assume
that
here
it
it
is
something
we
had
discussed
already
in
the
past
about.
C
G
B
A
G
Lack
of
time
there
were
things
that
I
I
had
to
decide
and
I
didn't
know
how
to
decide
like
how
to
patch
kubernetes
specifically
like
where
to
introduce
what
changes
and
what?
What
were
our
goals
with
this
Fork
like?
Do
they
do?
We
want
to
keep
the
diff
as
small
as
possible,
or
do
we
want
to
make
changes
that
maybe
make
more
sense
and
I
didn't
want
to
annoy
Stefan
all
the
time
with
tons
of
questions?
H
Yeah,
it
sounds
like
you're
raising
a
question
for
the
community
if
you're
talking
about
what
are
the
goals
of
the
rebase.
D
The
main
goal
is,
of
course,
to
make
maintenance
of
the
three
base
as
easy
as
possible.
So
having
the
next
one
in
mind
is
always
a
good
idea,
and
there
are
practices
which
we
used
in
I
mean
in
openshift.
We
did
that
for
for
many
years,
and
things
which
we
learned
and
try
to
apply
in
kcp
as
well,
and
it's
not
always
just
merging
everything.
Sometimes
you
have
to
strategically
keep
things
apart,
separate
in
a
way,
it's
hard
to
say.
G
D
Yeah,
it
is
difficult,
and
sometimes
you
just
try
one
approach
and
you
realize
it
yeah
at
eighty
percent,
it's
ugly
and
then
you
do
another
one
and
then
it
works.
So
you
can
ask
me
or
any
or
maybe
David.
G
D
A
Okay,
that
would
be
awesome.
Okay,
so,
regarding
the
rebates,
I
think
it
makes
sense
to
check
in
with
the
VMware
folks
and
see
where
things
are
at
and
if
they
are
willing
to
continue
in
it
or
if
we
should
yeah.
If
someone
else
should
pick
up
the
the
the
missing
pieces,
so
we
can
complete
the
1.27
rebase.
D
H
So
I'm
curious
about
the
status
and
commitment
and
Ambitions
for
the
helm,
chart
yeah
I'm
in
Coop's
dollar
we're
also
working
on
a
health
chart
and
I
would
love
it.
If
I
could
use
a
Helm
chart
maintained
by
this
project
kcp,
so
maybe
some
yeah
I've
I
started
trying
to
use
it
in
openshift
cluster
and
it
didn't
work
for
me.
So
maybe
someone
could
just
tell
me
what
is
the
current?
You
know
status
and
Ambitions
and
commitment
for
it.
A
Well,
MJ
can
also
add
this
piece,
but
from
from
our
perspective
the
hand
chart
is
we
want
to
use
the
hand
chart
for
deploying
kcp
and
I've,
provided
some
fixes
that
I
discovered
while
trying
to
install
it
myself
so
from
outside
it?
The
commitment,
I
think,
is
there
to
to
maintain
it
and
to
improve
it
and
I
think
I.
A
From
my
perspective,
there
are
some
pretty
substantial,
potentially
breaking
changes
we
might
want
to
do
to
bring
it
up
to
like
the
quality
of
a
flicker
production,
ready
and
charts.
A
B
A
Okay,
yeah
so
I
think
the
question
is
the
the
answer
or
trying
to
formulate
an
answer
to
the
question
is
the
handshot
is
at
the
stage
as
kcp
itself,
things
can
break
and
there
is
room
for
improvement,
but
it
definitely,
from
my
perspective
at
least,
should
be
all
right.
It
should
be
the
way
to
to
install
kcp
on
kubernetes,
so
yeah
and
I
want
to
keep
supporting
that.
H
A
Do
we
have
someone
with
openshift
experience
who
would
be
able
to
help
out
because
I
have
been
developing
it
against
vanilla,
kubernetes?
The
M
chart
changes
so.
H
H
There's
a
thought
specifically
there's
a
file
I
I
posted
you
know
in
the
the
kcp
dev
slide
Channel
you
can
look
and
see,
but
my
problem
is
the
symptom
is
something
is
failing
with
a
file
access
failure
at
runtime.
B
H
So
this
is
important.
Do
we
have
anybody
who
is,
you
know,
maintaining
or
interested
in
maintaining
the
helm,
charts
that
has
open
shift
expertise,
I
mean
if
we
don't.
That
sounds
like
a
problem.
B
H
All
right,
thank
you,
then.
My
other
issue
is
or
a
question
or
comment
at
least
for
coup.
Stellar
we
like
to
have
a
you
know:
developer
friendly
deployment,
something
that
a
developer
can
deploy
on
their
laptop
and
try
things
out.
So
it's
by
no
means
production
grade,
but
it
delivers
the
functionality.
H
A
H
D
Yeah,
my
suggestion
is:
if
we
go
I
mean
if
we
want
to
implement
charting
this
I
mean
one
headshots
would
be
one
shot.
You
shouldn't
go
beyond
that,
but
of
course
joining
in
those
things
are
important
right,
so
you
have
to
set
certain
links
up.
H
Okay,
so
Ambitions,
then
in
terms
of
Ambitions
the
end
status.
So
the
answer
is
today:
the
home
chart
supports
only
single
short
operation,
ambition
to
support
multi-shard
operation,
perhaps
in
the
way
that
the
font
suggested.
So
in
order
in
terms
of
minimizing,
then
the
resource
requirements
I
think
for
a
single
shark
deployment.
We
don't
need
the
front
proxy,
for
example,
right
because
there's
a
front
proxy
built
into
the
server
and
we
can
use
the
server
without
the
front
proxy.
That
would
be
an
additional
minimization
that
we
could
have
right.
D
B
I
think
it's
a
desirable,
but
I
would
like
to
avoid
that,
because
this
leads
to
the
bugs
where,
where
we
don't
spot
informers
being
done
wrong
because
that
front
box
front
proxy
and
the
kcp,
basically
they
act
a
bit
different
on
their
paths
and
names
like
that,
the
name,
the
resolution-
it's
like
I
I,
don't
see
running
two
containers
as
a
big
penalty
in
a
performance
over
the
valley
delivers,
meaning
it
being
more
consistent
environment.
Where
production,
if
you're
developing
something
you
you
will
get
the
result
all.
D
Right,
MJ
I,
like
your
point,
I,
don't
think
it's
correct
that
there
are
actually
two
proxies:
there's
one
embedded
always
embedded
and
there
is
a
phone
proxy
and
if
everything
is
one
on
one
chart,
this
is
embedded
for
proxy
will
have
all
information,
so
it
just
acts
the
same
way,
I
think
as
a
fun
proxy.
You
will
notice
any
difference.
It's
just
an
additional
processing
font.
Logically,
it's
not
different.
D
B
That's
that
sort
of
thing
it's
like
I'm,
like
I
personally,
always
a
bit
against
over
optimizations
or
like
we're
not
talking
about
20
containers
versus
one
container,
we're
talking
one
or
two,
and
this
like
most
of
our
letters,
already
have
more
more
RAM
like
than
and
moon
mission
long
time
ago.
So
it's
like
I
I,
don't
see
this.
It.
H
B
Say
like
that,
if
somebody's
invested
in
times
and
optimizes
that
I
think
Community
will
agree
and
manage
that,
but
I
personally
would
better
spend
my
time
fixing
more
DMC
issues
than
something
like
that
at
this
point
in
time.
So,
like
I,
think
there
is
appetite
for
that.
The
question
is:
will
the
community
have
time
to
to
solve
that?
So
if
you
find
the
solution
on
Stellar
site,
how
to
do
that
like
just
feel
free
to
send
it
our
way
and
we
can
incorporate
it.
A
Okay,
yep
I
believe
that
takes
us
to
the
NFL
agenda.
Let
me
just
refresh
to
be
sure-
and
we
already
talked
about
Stefan's
point
where
they
won
the
28
rebase.
A
Okay,
does
anyone
have
topics
that
are
not
on
the
agenda.
D
Yeah
it
happened.
There
were
a
couple
of
questions.
It
was
not
something
like
a
technical
board
or
something
I
mean
where,
where
they
were
judging
over
kcp,
it
was
more
like
a
junior,
a
general
audience.
Some
interested
in
the
topic.
Yeah
was
not
a
very
meeting
in
general,
so.
A
Great.
Thank
you
for
that
update
any
other
topic.
A
Okay,
if
that's
not
the
case,
Ben
I
think
we
can
go
to
looking
at
incoming
issues.
I,
don't
think
we
had
a
lot
of
new
issues,
but
the
last
time
I
believe
we
did
not
finish
categorizing
what
was
already
there
so
I
think
we
can
hopefully
maybe
finish
that
today
there
was
also
talks
about
the
about
the
TMC
issue.
Still
in
the
co-repository
I.
A
E
C
Maybe
just
just
a
point
about
I:
don't
know
if
it's
possible
to
also
migrate
the
project
elements
or
possibly
also
move
them
by
hand.
I
don't
know
about
the
GMC,
epics
and
and
you're
having
the
TMC
epics
in
a
number
of
bones
here,
related
to
TMC.
A
C
Here
I
mean
by
the
way
the
the
projects
I
mean
boards
are
related
to
epics,
which
are
real
epics.
You
know
simple
GitHub
issues
as
a
piece,
so
at
least
you
would,
if
you
still
also
move
the
epics,
you
would
still
get
the
descriptions
of
the
Uproar.
C
A
Okay,
that
makes
sense
cool
okay,
then,
let's
I
think,
let's
move
on.
Let's
take
a
look
at
the
11
issues
that
are
not
that
are
still
marked
as
incoming
clear
object.
Status
were
not
synced
anymore,
I
suppose
this
is
already
marked
as
TMC.
E
I
haven't
really
expressed
how
it
should
be
done
so
once
again
I'm
available.
If
someone
has
some
question
about
detail.
A
C
C
A
C
Maybe
even
this
the
the
the
the
the
Upstream
Pierre
has
been
matched
possibly
so
maybe
this
can
be
closer.
I
lost
the
the
history
here.
A
Okay,
do
we
want
to
close
it
and
reopen
it
if
it
comes
up
again
as
a
topic.
C
Or
maybe
pink
polynomial
I
mean
which
is
Syracuse.
Even
if
he's
not.
You
know
actively
working
on
that.
Maybe
he
has
an
idea
about,
or
he
reminds
remembers
what
was
the
end
of
this.
A
A
C
E
C
E
I,
don't
remember
if
we
had
already
commented
on
this
one.
It
was
quite
it
arrived
quite
late
just
before
I
I
leave.
C
F
B
E
A
Close
that
okay,
loading.
B
A
B
A
I
I
think
their
issue
here
was
that
you
can
see
from
the
output
from
from
the
Epic
response
that
the
user
identity
is
something
different
than
that
what
they
have
given
in
the
world
binding,
so
yeah
closings.
There
has.
A
C
Yeah
that
mainly
that's,
you
know,
a
request
that
happens
sometimes
where
people
want
to
use
TMC
to
synchronize
objects.
That
first
exist
on
the
physical
cluster
to
the
workspace,
so
the
other
way
around
though
it
can
be,
it
can
make
sense
in
very
specific
cases.
You
know
like
PVS,
that
are
by
default,
created
on
the
physical
cluster
when
Auto
provisioned,
and
this
should
stay.
The
really
the
exception.
I
mean
usually
answering.
A
Now
I
I
see
the
point
here,
but
yeah
I
I
know
what
you
mean
so
do
we
want
to
add
this
to
the
backlog
as
a
feature
request,
or
do
we
want
to
close
it.
B
C
We
already
had
in
the
past
quite
requiring
requests
about
app
thinking,
especially
before
cubesteller
came
to
life
when,
when
the
corresponding
project
was
still
trying
to
use
the
TMC
Sinker,
and
we
just
realized
that
you
know
the
more
time
went
the
more
they
they
needed,
some
sort
of
specific
upthinking
and
that
didn't
fit
so
now.
Finally,
Cube
Stellaris
is
using
their
own
Sinker,
and
that
makes
sense,
because
you
know
the
the
use
case
is
not
the
same.
C
Yeah
upsyncing
to
be
fair,
is
already
implemented,
but
is,
is,
by
purpose,
limited
to
very
specific.
You
know
low
level,
Cube
objects
like
PVS,
no.
A
Okay,
I
think
same
author,
when
you
couldn't.
C
Yes,
I
mean
namespaces
are
managed.
Obviously,
in
a
special
way,
I
mean
you
cannot
sync
namespaces
as
you.
You
would
sing
something
else,
because
a
namespace
is
mainly
just
to
continue
for
the
corresponding
objects,
so
namespaces
are
removed
when
there
is
no
more
objects
that
have
to
be
synced
to
this
namespace
in
the
physical
cluster,
but
they
are
not
synced
Percy.
They
are
just
created
on
the
fly
or
removed
after
some.
You
know
delay
when
no
more
object
is
synced
in
in
this
namespace.
A
Yeah
that
makes
sense
I'm,
just
gonna
write,
I'm
gonna
type,
that
out
after
the
meeting
real
quick
as
an
answer.
Let
me
open
this
so
I,
don't
forget
it
yeah,
okay,
cool,
then
I'll
I
guess
I
will
close
it
afterwards.
So
it
will.
It
will
go
right
here.
A
B
B
A
Okay,
specific
Hardware
is
for
sure
okay
yeah
I
see.
B
Oh
well,
I
suspect
it
might
be
the
architecture
and
race
condition
somewhere
in
a
code
where,
like
thinkers
like
caches,
are
synced
or
not,
because
I
had
the
similar
cases
on
my
MQM
MD
in
different
places,
but
it's
a
very
complicated
piece
of
bug
which
I'm
not
sure
we
can
debug
it
without
powder,
giving
us
more
details.
A
Okay,
since
this
is
GMC
MJ,
do
you
want
me
to
go
ahead
and
just
close
it
and
see
if
the
author
come
back,
comes
back
or
just.
A
C
Possibly
here
just
the
common
lines
that
exist
should
be
mentioned.
You
know
you
have
the
API
I
mean
I,
don't
remember
how
it's
called,
but
you
have
three
comments
to
export
shamas
from
crd's.
You
have
the
crd
puller
first
and
then
you
have
some
comments
from
to
to
create
API
resource.
A
That's
and
then
back
locked,
okay,
we
have
two
more
issues.
However,
we
are
running
out
of
time
and
so
far
I
think
the
experience
has
been
that
between
meetings
we
have
a
relatively
low
volume
of
incoming
tickets,
so
I
would
propose.
We
wrap
up
the
meeting
in
time
to
be
mindful
of
everyone's
calendar
and
continue
in
the
next
community
meeting.