►
From YouTube: Cartographer Community Meeting - Feb 2nd, 2022
Description
00:00 Intro
00:45 The TL;DR
05:17 Open mic discussion (see agenda for full details)
Community meetings happen each Wednesday at 8:00 AM PT/11:00ET
See the agenda here (https://bit.ly/2Z67z08), add any topic you may want to discuss and join us live!
A
A
Cool,
okay,
please
make
sure
to
add
yourself
to
this
list.
If
you
don't
mind
today,
it
seems
like
we
don't
have
new
faces,
but
I'm
really
glad
to
see
you
all
so
welcome
for
the
tldr.
I
don't
know
if
this
section
should
be
renamed
to
the
big
picture
or
something
like
that,
because
what's
new
in
the
project
this
week,
at
least
from
my
limited
point
of
view-
maybe
it
has
a
lot
to
do
with
rfcs
rfc
is
everywhere.
A
I
wanted
to
create
a
meme,
but
just
rfc
is
everywhere
and,
and
we
can
check
there
on
the
public
project
board,
what
team
is
actually
doing
right
now,
but
probably
for
a
user
out
there,
who's
just
getting
started
with
the
tool
or
who
doesn't
have
enough
context.
What
could
be
a
good
summary
of
all
big
picture
for
all
the
work
that
the
team
is
doing
right
now
or
what's
new
in
the
project.
B
I
think
there's
been
at
least
one
open
talk
about
cartographer
in
the
last
week
and
there
seems
to
be
an
uptick
in
in
public
discussions.
A
B
Another
thing
is
like
just
personally:
I've
taken
a
a
strong
interest
in
what
what
we
can
do
to
provide
live,
editing
and
live
visualization
of
supply,
chain
designs
and
workload,
design.
Nothing
concrete
on
that.
Yet,
but
finding
that
there
are
a
lot
of
people
interested.
A
Yeah
yeah
I've
seen
some
interest,
not
only
the
internal
session
we
had
this
week,
but
several
times
even
myself
as
a
user.
I
would
like
to
have
some
visual
editor,
some
visual
way
to
see
the
all
these
steps
in
the
supply
chain.
So
I
believe
you
already
have
an
issue
for
that
rash
is
that
I.
B
D
Milan,
this
is
just
a
good
fyi,
for
you
too,
I
don't
know
if
everyone
knows
midline,
but
he
works
on
the
ui
team
and
so
yeah.
This
might
be
cool
for
for
you
to
talk
to
rashford.
C
C
At
this
point-
and
you
know,
we
kind
of
made
a
bit
of
progress-
still
not
sure
how
that
fits,
and
that's
obviously
inside
a
little
different
framework,
and
we
can
talk
about
that
some
some
time
on
this
meeting,
but
definitely
has
something
to
maybe
synchronize
those
efforts.
A
D
Yeah,
this
is
a
small
bug
fix
we
made
last
week.
I
guess.
D
Sorry
yeah.
Basically,
if
we
ever
encountered
an
error
while
trying
to
stamp
out
a
template,
it
would
just
halt
and
then
wouldn't
proceed
through
the
rest
of
the
supply
chain.
Even
if
there
were
other
resources
that
could
be
stamped.
So
we
just
fixed
this
so
that
yeah,
if
you
run
into
a
failure,
it
doesn't
stop
propagation
of
everything
else
in
the
supply
chain.
A
That's
great:
okay,
okay,
cool!
Thank
you
great
well
from
previous
meeting.
We
had
basically
a
whole
session
for
for
rfc
discussion.
Mainly
so
we
didn't
have
any
any
follow-up
item
there.
Okay,
open
my
discussion.
This
one
was
proposed
by
raj
and,
I
believe
also
maddie,
but
maurice
is
not
available
today,
so
yeah.
A
The
idea
was
to
use
public
meeting
time
just
to
quickly
introduce
rfc
and
if
the
rfc
is
created,
but
by
someone
who
is
not
in
the
core
team
who
is
not
part
of
the
core
team
to
receive
feedback
to
get
feedback
and
try
to
keep
the
discussion
as
I
think
as
possible.
A
So
what
will
be
the
implications
of
that?
We
will.
You
know
time
box,
the
the
rfcs
just
make
it
to
a
proper
introduction
and
prioritize
them
and
just
keep
the
discussion
async.
B
I
just
wanted
to
be
just
a
little
bit
more
concise.
The
idea
I'm
proposing
is
that
not
not
a
synchronicity
like
definitely
use
that,
but
also
feel
welcome
to
ask
for,
especially
with
the
maintainers
team.
B
We
can
have
impromptu
discussions
just
as
long
as
they
get
captured
in
our
async,
which
is
basically
in
the
comments
of
an
rfc,
and
I
think,
also
we're
pretty
willing
to
support
any
open
source
contributor
who
wants
to
have
a
talk
with
us
would
definitely
make
time
to
talk
to
them
as
well,
but
that,
in
these
meetings
we
make
sure
we
get
through
the
introduction
to
rfcs,
because
the
goal
is
is
to
know
what's
on
the
board
and
what
we
need
to
consider
and
to
make
sure
that
we've
carved
out
time
to
to
see
that,
and
especially
if
it's
being
introduced
by
someone
external
to
the
maintainers
team.
B
That's
when
we
really
want
to
hear
from
people,
and
that
might
be
the
one
time
we
go
a
little
over
time
to
make
sure
that
we've
captured
whatever
it
is,
that
they're
proposing
all
right
so
that
they
feel
included.
But
the
rest
of
us
have
the
opportunity
to
talk
to
each
other
any
old
time
we
like
does
that
make
sense.
A
Thank
you,
raj.
Okay,
any
other
comment
regarding
this:
no
okay
cool
thanks,
great
yeah
we
had
last
week
at
tansu
code
live
streaming.
The
goal
was
to
walk
through
a
new
user
on
how
to
install
cryptographer
and
how
to
use
it.
A
Also
for
next
week
we
have
a
tgik
episode
coming
up
tjik
or
thanks
goodness,
it's
kubernetes.
The
original
show
that
jobita
started
back
in
next
few
days,
and
now
it
has
a
rotating
host
schema
and
I
will
be,
I
will
be
the
host
for
next
week
and
we
will
have
an
interesting
introduction
to
the
valley
proposition
of
cartographer,
the
why,
behind
the
project
and
a
demo,
so
we
hope
we,
you
can
join
also
for
the
multiple
paths:
rfc
rush
provider,
a
quick
intro
on
the
office
hour
session.
B
No,
that's
an
open
question
was
an
open
question.
If
anyone
wanted
me
to
go
any
deeper
into
it,
I've
just
I've
just
noticed
that
that
when
I
link
to
the
rsc,
it's
not
grabbing
the
latest
updates
in
the
pr.
So
I've
got
to
be
careful
about
that.
It
would
seem
so
just
know
that
there
is
actually
an
update
to
the
rsc
and
the
link
at
the
top
of
it
is
invalid.
I'm
just
going
to
delete
it,
but
yeah
I've
I'm
working
on
it.
I'm
updating
it.
B
I'd
like
to
see
that
people
actually
investigate
it
and
have
some
opinions
so
that
we
can,
I
think,
make
a
decision.
I
I
just
feel
like
we
have
roadmap
requirements
to
make
decisions
between
this
and
snippets
at
this
point,
so
I'd
really
like
to
get
feedback
as
soon
as
possible.
I
don't
know
what
we're
going
to
do
to
drum
up
and
ensure
that
we
hit
quorum
quickly,
but
I'm
free
to
talk
about
any
questions
anyone
has
about
it.
A
Okay,
cool!
Thank
you
raj,
that's
great
okay,
and
this
was
an
outstanding
question
from
myself.
We
discussed
a
couple
of
community
meetings
ago.
I
believe
the
idea,
the
suggestion
to
move
the
contents
of
issue
triage
were
kind
of
pre-ipm
meetings
to
be
open,
making
it
part
of
the
community
meetings.
Agenda.
D
B
D
B
D
A
A
Yeah,
I
believe
3
8
pm
is
on
fridays.
That's
what
I
saw
in
the
calendar,
but
yeah.
The
suggestion
from
brush
is
to
just
basically
stream
the
free
ipm
meeting
itself
right.
B
B
Advertise
that
it's
available
for
people
to
attend
probably
fly
on
the
wall.
I
haven't
really
thought
about
that,
but
the
idea
was
to
open
up
awareness
and
how
we're
doing
planning
correct.
A
If,
in
the
future,
there
are
users
contributors
who
like
to
discuss
the
priority
for
their
issues,
I
don't
know
if
that
will
be
the
correct
place
to
do
it,
but
the
anyways,
if,
if
it
happens
in
the
community
meeting
or
in
a
separate
meeting,
the
the
whole
goal
is
just
to
make
sure
that
we
are
prioritizing
user
feedback
issues
that
come
from
the
community.
A
Cool,
oh,
that's,
great!
Okay!
Well,
I
think
that's
it
so
far,
any
other
coming
suggestion
idea!
No!