►
From YouTube: Cartographer Community Meeting - Dec. 15th, 2021
Description
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
B
A
A
C
A
A
A
A
C
C
We
believe
the
security
stand
should
be
that
a
developer
cannot
change
or
interfere
with
the
outcome
of
a
supply
chain,
but
they
should
be
able
to
see
the
objects
that
were
stamped
so
that
they
can
debug
and
understand
what
actually
happened
to
their
code.
So
just
yeah
I'm
going
to
get
around
to
it
in
the
new
year.
I
suspect.
A
I've
been
talking
to
other
oss
projects.
Tech
leads
regarding
release,
numbering
opinions,
it's
just
that
opinions
like
everyone
has
or
gives
a
different
response.
So
kind
of
the
common
pattern
I
found
on
the
responses
I
received
was
that
the
first
step
was
trying
to
define
what
is
considered
the
public
api
code
base
and
then
any
breaking
change.
Any
outstanding
issue
that
it's
that
will
cause
a
breaking
change
to
the
public
api
is
what's
considered
one
point.
No,
and
that's
it,
that's
the
summary
of
the
conversations
I
have
on
this
topic.
C
What
versioning
are
we
going
to
use?
I
think
that
was,
I
think
we
were
suggesting
before
we
decide
that
we're
generally
available,
it
might
be
worth
treating
the
point
releases
like
for
I,
I
can't
remember
the
names
of
them
the
instead
of
the
one
dot,
the
o
minus.
Thank
you
yeah.
Instead
of
the
majors,
we
use
the
miners
as
breaking
change
indicators.
Until
we
get
there.
C
C
C
A
C
C
C
A
Okay
for
the
for
the
open,
my
discussion-
I
I
have
one
we
have
had
the
improvements
in
the
docs
and
many
more
to
come,
so
I
wanted
to
capture
user
feedback.
Wait
well,
I
considered
using
github
discussions,
but
the
fact
that
I
need
to
ask
admin
permissions
not
only
to
enable
it
but
probably
later
on
to
moderate
discussions.
Again,
I
will
need
to
ask
temporary
admin.
Permissions
doesn't
make
it
really
scalable.
So
I
use
an
issue.
A
The
call
for
the
community-
and
I
will
send
this
through
the
mailing
list
dislike
channel
etc
is
the
goal
of
this
issue
is
to
remain
open,
just
capturing
feedback
in
the
form
of
comments
and
anything
that
users
contributors
maintainers,
would
like
to
point
out
on
improvements.
Opportunities
for
docs
should
be
here,
so
we
can
crack
it
and
probably
turn
it
into
action
right.
So
your
feedback
is
much
appreciated.
A
C
A
C
B
C
C
I
think
that's
right
yeah
and
it's
those
sorts
of
things
that
I
think
are
better
if
we
keep
scoping
out
our
docks
to
include
large,
tutorials,
etc.
There's
a
lot
to
maintain
a
lot
of
surface
area
to
cover
as
things
change,
whereas
people
understand
that,
like
blog
posts
will
age
out
and
that
they
can
be
and
the
people
can
contribute
and
that's
the
space
for
contributions
there
are.
We've
got
places
for
our
own
blog
posts.
C
People
can
make
their
own
personal
blog
posts
and
let
us
know
about
them
and
we'll
you
know
happily
mention
them
like.
Maybe
we
could
maybe
there's
a
way
to
put
good
hyperlinks
to
other
people's
blog
posts
if
we
like
them
some
sort
of
aggregator
on
our
blog
post
page,
but
that
I
think
all
of
that
contributing
behavior.
Maybe
we
need
to
talk
about
that
in
lieu
of
this
story
too,
because
people
are
going
to
say
a
lot
of
things
like.
I
don't
know
how
to
install
all
of
these
things
and
it's
like
well.
C
We
have
to
have
a
guideline
that
says:
we're
not
going
to
walk
you
through
learning
how
to
use
kubernetes
right,
but
at
the
same
time
it
would
be
maybe
nice
to
like,
maybe
ask
the
community.
Does
someone
want
to
write
a
blog
post
on
this
to
help
people
that
sort
of
thing
so
that
we
can
focus
on
core
contributions.
A
Yeah,
that's
the
that's.
The
one
of
the
goals
of
this
idea
is
to
again.
If,
if
we
find
a
common
pattern
of,
you
know
frequently
asked
questions
or
or
common
pitfalls
in
users
that
will
probably
turn
into
yeah
something
where
the
community
can
actually
contribute
in
a
blog
post
or
something
you
know
it,
he
always
no.
No
will
it
won't
result
always
and
expanding
the
docs.
That's
not
the
goal.
A
B
I
guess
rash
in
the
what
you
were
talking
about
makes
sense
to
me
some
of
the
stuff
that
we
have
saying
some
of
the
stuff
that
we
currently
have
written
up,
let's
cleave
it
out
and
turn
it
into
a
blog
post,
and
I
I
talked
with
you
and
emily
when
you
were
looking
at
the
stuff
about
installing
in
an
air
gapped
environment
and
like
that,
I
would
be
a
total
thumbs
up
yeah.
Let's
take
that,
let's
make
that
something
we
don't
maintain,
make
it
a
blog
post.
B
C
Yeah,
I
think
I
actually
think
that
we
should
try
and
ratify
some
guidelines
on
how
what
decisions
we
make
for
exclusion
right,
so
how
we
keep,
how
we
keep
the
docs
focused
right.
So
I
recommend
that
we
have
a
story
for
that
and
that
we
write
that
into
contributing
all
right
and
then
beyond
that.
I
think
the
thing
that's
great
about
like
saying
then,
and
then
please
use
community
submissions
for
things
that
are
going
to
be
helpful
and
interesting.
C
Is
that
is
it
there's
only
one
thing:
is
that
you're
empowered
everyone's
empowered,
because
everyone's
allowed
to
write
about
this
thing
right
everyone's
about
allowed
to
say
what
they
want
to
say?
I
feel
like
if
we
think
that
our
blog
post
is
valuable
enough,
we
have
direct
access
to
the
docs,
so
we
can
put
blog
posts
directly
in
hours
all
right
or
you
can
do
your
own
personal
blog.