►
From YouTube: Cartographer Office Hours, August 22nd, 2022
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
Okay,
welcome
everyone
to
the
cryptographer
office
hours
weekly
meeting.
I'm
really
glad
to
see
you
all.
Let
me
share
again:
here's
the
link
to
the
agenda
and
notes
feel
free
to
add
anything.
You
would
like
to
discuss
there,
starting
by
adding
yourself
to
the
attendees
list,
bring
your
affiliation
please.
A
If
you
don't
have
an
objection,
I
can
be
a
note
taker
today,
all
right
great
well,
usually
the
first
item
in
the
agenda
here
is
to
rebuild
standing
rfcs
because
like
this,
so
I
was
wondering
if
there
is
any
one
of
these
proposals
that
you
would
like
to
discuss
here.
B
We
do
have
one
rfc
that
we're
trying
to
push
through
it's
blueprints,
but
I
guess
that
kind
of
goes
to
my
first
bullet
point
down
in
the
discussion.
B
Topics
is
that
there's
been
talk
of
dissolving
the
toc
and
that
we
need
a
new
governance
model
and
I
think
that
would
change
the
way
we
get
rfcs
approved.
So
I
don't
know
what
we
should
really
talk.
B
C
B
D
Emily
thanks,
you
said
that
there
isn't
a
tfc
all
right,
I'm
pretty
sure
we
just
named
did
we
I
need
to
like
go
back
and
double
check.
Did
we
get
around
to
specifying
by
name
the
members
of
the
tfc.
B
I
believe
that
the
I
had
heard
rumors
that
scott
was
going
to
call
a
quick
vote
before
rawlings
left
to
dissolve
the
toc,
but
I
haven't
seen
any
action
on
that.
So.
D
Yeah
in
the
meantime,
I
would
imagine
that
scott,
this
guy
supports
blueprints
and
that
would
unblock
things
because
we
don't
need
there's
no
quorum
for
the
tsp.
B
D
Yeah,
I
do
not.
D
D
You
know
blueprints
that
are
leaf
nodes
and
blueprints
that
are
not
least
nodes,
and
I
continue
to
hear
rash
say,
like
I
said,
I'm
on
the
sense
about
this,
and
I
continue
to
see
other
people,
echoing
my
my
thoughts
on
that
the
most
recent
was
a
developer
advocate
internal
to
vmware,
who
spoke
up
about
it,
and
it's
unclear
to
me
what
will
be
necessary
to
make
this
to
get
this
to
change
so
that
that
would
be.
D
D
If
you,
if
you
have
a,
if
you
have
a
blueprint
that
stamps
something
out
there
are,
there
are
fields
that
you
would
exclusively
use
and
if
you
have
a
blueprint
that
is
apparent
to
other
blueprints,
there
are
fields
that
you
would
exclusively
use
so
that
there
are
like
these
two
sets
of
exclusive
fields
in
the
in
the
resource,
and
that
seems
like
a
smell
like
this
is
not
one
thing.
This
is
two
things.
D
I
yeah,
I
don't
remember
from
a
user
standpoint
if
there
were
pieces
where
I
was
like.
Oh
you
kind
of
need
to
know
the
difference
I
know
rash.
Has
I
I've
heard
rash,
articulate
and
I
I
can
see
the
goal
that
he's
that
he
is
advocating
for
which
is.
D
If
you
have
a
catalog
of
blueprints
that
you
are
going
to
pick
and
choose
from
in
terms
of
building
a
new
blueprint,
then
you
know
it's
it's
easier
to
just
say.
Like
oh
they're
all
blueprints,
you
don't
need
to
know
if
this
is
a
leaf
blueprint
or
if
this
is
a
parent
blueprint,
they're
just
all
blueprints
and
they
do
something.
D
I
think
that's
something
that
you
would
need
like
extra
metadata.
On
top
of
for
correct
me,
if
I'm
wrong,
I
don't
think
there's
a
field
in
the
blueprints
where
you
just
say
like
this
is
what
this
blueprint
is
for.
This
is
what
it
does
it's
something
we
expect
to
be
external,
but
yeah
so
and
that
that
user
is
the
operator.
D
It's
not
the
dead,
end
user,
it's
the
it's!
The
somebody
who
wants
to
be
a
blueprint
author
and
wants
to
reuse
other
blueprints.
D
Yeah,
so
so
yeah
right
and
russia's
russia's
point
is:
if
they
are
the
same
they're
the
same
resource
they're
the
same
kind,
then
you
don't
need
to
specify.
Oh
this
is
this
happens
to
be
a
leaf,
or
this
happens
to
be
a
parent
of
other
leaves
yeah.
You
just
say
like
hey,
get
that
blueprint.
A
C
B
Super
cool:
what's
the
name
of
your
talker,
will
we
be
easily.
C
Able
to
find
it
considering
I
have
five
sessions.
This
one
is
customizing
kansu
application
platform
to
the
extreme
okay,
okay,.