►
From YouTube: Cartographer Community Meeting - Feb. 16th, 2022
Description
00:00 Intro
00:59 The TL;DR: what's new in the project this week
06:35 Live editor updates
08:15 Open Mic: Orphans (Issue 592)
13:55 OSS health assessment results and OpenSSF badge
17:12 OpenSSF best practices badge: passing grade achieved
18:30 Good first issues
20:52 Convention Service
26:08 imgpkg management to submit Cartographer to TCE
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
A
Formatting
could
be
better
all
right.
Welcome
new
faces,
not
much
welcome,
kartik
welcome
everyone,
all
right,
the
dldr.
What's
the
end
the
project
this
week,
I
I
was
exploring
a
little
tool
that
probably
none
of
you
will
actually
use
this
kid
cracking
back
in
the
days
I
took
a
kit
training,
and
the
first
thing
that
they
asked
me
to
do
was
to
install
these
two.
A
So
I
know
it's
it's
not
perfect,
but
it
gives
me
some
visual
indications
of
activity
last
week,
the
repo,
so
I
will
say
that,
what's
in
the
project,
a
lot
of
activity
on
the
options
deliverable
right
also
spike
in
orphans-
that
it's
also
part
of
the
agenda
today,
I
also
see
activity
around
the
live
editor
from
rush.
That's
awesome
and
yeah
also
moving
rfcs
discussing
rfcs.
You
know
a
lot
of
design
work,
but
that
was
the
summary
from
my
point
of
view.
Is
that
correct?
Is
that
a
good
summary?
What's
new?
C
A
A
A
A
E
D
D
C
B
D
A
A
A
C
C
A
B
Do
you
want
to
open
up
the
issue
thanks
steven,
so
we
haven't?
This
is
a
and
currently
a
a
bug
or
an
issue.
I
don't
know
what
we've
had
it
labeled
as,
but
basically
when
a
resource
selects
a
different
template,
then
or
even
a
different
supply
chain,
I
think
than
what
it
currently
was
stamping
out.
We
leave
orphan
objects
behind
and
there's
a
couple
ideas
for
solutions.
If
you
scroll
just
a
little
bit,
I
think
it
was
talked
about
in
maybe
a
pre-ipm
serious
comment
there
about
you
know.
B
B
I
can
only
imagine,
depending
on
what
is
all
on
that
cluster,
and
so
one
idea
that
we
came
up
with
yesterday
was
storing
the
basically
the
template
or
the
cs,
storing
like
the
stamped
object,
gvk
and
the
template
gvk
and
a
configmap
in
the
namespace
and
using
that
to
get
the
information
out.
For
so
we
can
go
and
check
all
of
the
objects
that
have
the
labels
of
the
workload.
F
B
E
E
Yeah
we
talked
about,
I
mean
in
our
comment.
I
think
we
listed
that
as
one
of
the
options
or
if
we
didn't,
we
talked
about
it,
we
didn't,
but
we
talked
about
using
doing
that.
If
we're
open.
To
doing
that,
I
mean
it's
going
to
become
a
pretty
potentially
large
list,
but
a
large
list,
meaning
if
it's
any
any
object
that
the
workload
owns.
C
F
C
G
A
No
okay,
great
a
couple
of
weeks
ago,
actually
he
completely
completed
the
assessment
cartographer
against
a
set
of
oss,
let's
say,
guidelines
from
vmware
tensor.
I
just
wanted
to
provide
a
quick
summary
here.
Real
quick.
The
goal
here
is
to
you
know,
improve
a
couple
of
areas
here
or
focus
on
a
couple
of
areas.
A
A
A
That's
that's
a
multi-step
process,
as
I
always
say
it
all
starts
with
user
user
adoption,
but
yeah
so
far.
You
know
since
launch.
It
was
four
weeks.
Four
months
ago
the
active
contributors
base.
It's
kind
of
the
same.
We
have
some
external
contributions
here
and
there,
but
the
core
base,
it's
still
a
regular
theme,
and
it
will
be
like
that
for
for
for
a
while
yeah
contributions.
I
just
wanted
to
do
a
little
bit
here.
Yeah.
This
is
the
graph
to
say
the
same
thing
like
a
stable
contributor
base
here.
A
A
You
know
it's
hard
for
someone
to
actually
quickly
become
a
maintainer
for
an
open
source
project
out
there,
especially
people
from
the
outside,
and
especially
with
our
current
governance
model
and
cryptographer,
it's
impossible.
So
we
will
have
a
casual
external
contributors
and
that
will
be
the
figure
for
the
foreseeable
future
recognition
contributors,
as
I
mentioned.
This-
is
something
that
I
I've
been
pushing
to
you,
I'm
still
waiting
on
swag
providers
to
complete
their
tasks,
so
we
can
finally
make
public
the
initiative
and
kind
of
that
is
the
summary.
A
Let
me
provide
here
also
a
quick
update
on
best
practices
batch.
We
have
achieved
passing
grade.
This
is
the
baseline.
This
is
the
minimum
level
of
compliance
against
the
openness
of
best
practices
for
silver
level,
as
we
discussed.
If
I
switch
here
to
silver
level,
things
are
quite
different,
so
we
are
missing
several
requirements
that
I
will
be
tracking
and
issues.
So
we
can
establish
this
as
a
mid-term
goal.
There
are
things
passing
grade
that
are
optional.
A
A
Thank
you.
Rush
yeah
and
my
final
intubation
intervention,
good
first
issues,
yeah.
You
are
probably
aware
of
a
couple
of
pr's
that
I
use
benjamin
gottman.
He
sent
a
couple
of
pr's
here
and
the
two
of
them
are
basically
aim
to
close
the
the
two
good
first
issues
that
we
have.
We
have
labels.
Let
me
see
here
we
have,
as
far
as
I
can
say,
only
two
issues:
labeled
as
good
first
issues
and
benjamin
sent
prs
for
both
of
them.
A
This
is
good
because,
as
far
as
I
can
see
he's
not
a
vmware
employee,
so
that's
awesome.
The
thing
is
that
we
will
need
more
good
first
issues.
We
have
more
than
100
issues
right
now
and
I'm
kind
of
sure
that
there
are
at
least
a
couple
of
them
that
could
be
labeled
as
good.
First
issues,
it's
a
good
way
to
onboard
new
contributors.
A
Yeah,
the
dogs,
also
on
the
docks.
There
are
many
kinds
of
contributions.
You
know,
yeah
code
contributions
are
one
way
of
contribution.
Not
everyone
is
has
a
skill
to
do
that,
so
the
goal
is
also
to
have
yeah
I'll,
keep
adding
non-code
issues
for
potential
contributors,
like
you
know,
blog
posts
or
helping
on
some
formatting
stuff
for
for
the
site
for
the
docs
right
rush,
we
were
checking
the
styles
for
this
side
and
they
need
a
ramp
up
yeah.
They
need
some
improvements,
so
that
will
be
a
good
example
of
a
conversation.
H
Where
is
it
at
it's
been?
The
rc
has
been
around
for
a
while.
I
marked
it
approved.
I
had
encouraged
others
to
do
so
as
well.
We
had
somebody
drop
in
to
to
ask
like
hey.
How
can
I
see
a
good
example
of
a
config
path?
We've
got
this
config
template.
That's
really
just
meant
to
wrap
convention
service.
H
C
H
Yeah
like
in
terms
of
just
I
guess
there
are
a
couple
of
things
we
could
do,
one
like
scott's
proposing
this
so
he's
one
of
the
steering
I
heard
somebody
use
the
term
steering
committee.
I
like
it
he's
a
member
of
the
steering
committee,
so
he's
signed
off
on
it
right
now.
Two-Thirds
of
the
people
that
have
responded
have
approved.
C
Yeah,
can
I
ask
that
we
don't
assume
approval
from
one
of
the
steering
committee
members
who
actually
proposed
a
an
rfc.
I
would
like
to
see
stephen
approve
it.
Thank
you.
Otherwise,
that's
just
a
way
to
say
yep,
but
that's
other
than
that.
I
think
we
can
ask
stephen
to
approve
it
all
right.
I
think
that's
what
we
can.
C
H
B
B
A
D
A
D
D
Please
keep
me
honest
here
if
I
mess
up,
but
there
was
a
tce
issue.
If
you
open
that
david
that
that's
linked
there,
that
is
meant
to
not
require
upstream
projects
to
do
that,
and
rather
have
the
pce
project.
Take
the
owner
take
the
onus
to
like
copy
the
package
into
whatever
tc
depository.
That
was
my
understanding.
I
could
be
totally
wrong
about
it,
though,
so
I
just
wanted
to
like
surface
this
up
and
share
with
you
all
to
see
if
this
makes
the
overall
process
easier
on
your
side.
D
G
Our
packages
end
up
being
all
tagged
like
0.0.0
dev,
which
scott
created
an
issue
about,
and
I
don't
know,
I
think
it
makes
sense
to
separate
it's
a
different
repo.
I
remember
like
in
conquers
itself,
like
we
had
conquers
conquests
like
the
oss
big
repo,
where
the
source
code
lived,
but
then
we
had
a
reboot
for
bosch
releases
literally
before
the
helm
chart,
so
that,
like
the
efforts
of
packaging
living
in
a
place,
the
efforts
of
just
code
lives
in
a
separate
place,
and
particularly
I
don't
know.
I
think
that
makes
sense
works.