►
From YouTube: Learning Sync: 2021-03-30
Description
Meeting notes: https://bit.ly/38pal2Z
A
All
right,
let's
get
started
so
the
first
thing
is
status
updates.
I
could
give
you
a
simple
one
from
I
believe
last
week
in
regards
to
the
doc's
website.
A
We
added
a
search
functionality
to
the
docs
website,
based
on
a
service
provided
by
algolia.
I
believe
so
that's
been
integrated
along
with
that.
We
made
a
couple
tweaks
to
the
main
menu
and
how
that
is
presented
in
mobile.
So
hopefully
all
that
is
working
well.
We
don't
have
analytics
right
now.
I
think
that's
a
question.
That's
come
up
a
bit,
but
it
would
be
interesting
to
know
like
the
usage
for
some
of
that.
A
So
that
might
be
something
that
I
follow
up
with
leadership
about,
whether
or
not
we
could
get
some
analytics
going
through.
Just
the
standard
google
analytics
any
other
status
updates.
C
A
A
C
A
P,
all
right
added
that
okay
next
is
unlabeled
issues.
A
A
B
C
C
A
All
right
so
we'll
leave
that
there,
the
platform
team
will
go
ahead
and
groom
it.
Let's
make
sure
it
has
a
triage
and
we
could
go
from
there.
A
B
Yeah,
I
can
stick
to
it
so,
like
a
few
weeks
ago,
I
just
had
an
idea.
Maybe
we
can
create
an
intro
video
just
about
one
minute
explaining
what
buildbacks
are.
I
don't
have
like
a
real
vision
on
how
should
it
be,
but
I
think
I
mean
I
saw
many
videos
that
trying
to
explain
what
products
are
doing
and
like
it
can
be
very
helpful
to
explain
to
others
who
it
is.
B
I
mean
who
build
books
are
for
and
how
can
it
help
others
and
I'm
not
sure
how
to
continue
with
this,
and
I
would
love
to
get
some.
I
mean
javier,
and
I
had
the
discussion
yesterday
talking
about
how
to
move
forward
with
this.
But
if
anyone
has
an
idea
on
how
to
do
this,
I
would
love
to
hear.
A
Yeah,
I
I
guess
part
of
me
wonders
like
the
involvement
of
the
core
team
and
the
reason
why
I
asked
that
it
or
why
that
comes.
A
To
my
mind,
is
because
this
is
ultimately
going
to
be
a
projection
of
what
the
project
is
all
about,
and
I
know
anthony
and
I
have
been
speaking
to
like
the
complexities
of
this
project,
given
the
the
large
scope
of
its
audience
right
like
we
talked
about
the
app
developer,
we
could
talk
about
the
operator
and
we
could
even
talk
about
the
implementers
right
like
people
that
are
implementing
platforms
based
on
clarity,
build
packs.
So,
given
at
like
every
single
one
of
these
levels,
I
think
the
conversation
could
be
slightly
different.
A
I
I
would
want
to
make
sure
that
whatever
we
create
is
generic
enough
to
you
know,
speak
to
the
project
as
a
whole,
but
also
useful
enough
that
people
gather
what
it's
about
in
a
very
short
time
frame
right,
as
opposed
to
just
I
don't
know
things
that
they
could
just
look
at
within
the
rest
of
the
website.
B
I
totally
agree,
I
think
I
think
that
bill
packs,
like
our
project,
is
it's
pretty.
I
mean
it's
hard
to
explain
to
people
what
it's
doing,
because
there
are
so
many
people,
I
mean
different
people
that
can
use
it
in
a
different
way,
and
I
think
this
is
one
of
the
main
things
that
I
thought
about
when
thinking
about
this
intro
video,
I
just
to
explain
people.
If
you
are
this
kind
of
person
you
can
use
it,
but
also,
if
you're
doing
something
else,
you
can
also
use
it
in
a
different
way.
A
Yeah
yeah,
I
think
definitely
I
believe
the
app
developer
use
case
is
pretty
solid
right.
It's
like
hey,
just
pack,
build
specify
a
builder
and
your
stuff.
Your
application
magically
gets
compiled
into
an
image
right
then
there's
the
operator,
which
is
like
a
lot
of
day,
two
operations.
A
You
know
you
keep
your
stuff
up
to
date.
You
could
set
what
kind
of
blessed
artifacts
could
be
used
right
and
the
app
developers
could
only
use
within
this
builder,
right
or
stuff
like
that.
A
I
think
the
one
that
maybe
we've
been
lacking,
although
I
think
it's
been
doing
fine-
is
the
implementers,
the
platform
implementers
right
kind
of
speaking
to
the
fact
that
our
project
isn't
just
tooling
for
again
these
two
other
personas.
It's
about
a
specification
that
anybody
could
integrate
to
create
a
platform
right
or
provide
the
sort
of
functionality.
A
C
I,
like
the
I
remember,
javier
after
it
was
kubecon
he
sort
of
highlighted
one
of
the
ibm
presentations
about
kind
of.
I
remember
it
was
like
moving
left
but
like
the
idea
that
the
app
developer
worries
about
their
source
code
and
the
operator
worries
about
the
dependencies
and
that
separation
of
responsibilities
is
what
we
provide.
That's.
B
A
The
last
point
right
like
I
totally
agree
with
all
that
I
think
the
the
point
where
maybe
we've
been
lacking
and
has
created
some
uncertainty
or
you
know,
lack
of
clarity
is
the
the
fact
that
it's
a
spec
project
and
we
don't
provide
all
of
the
tooling
right
like,
for
instance,
people
will
come
to
this
project
and
say:
hey:
do
you
have
a
build
pack
that
does
static
host?
You
know
yeah
static
site
hosting
and
like
no.
We
don't
provide
any
build
packs
at
all
actually
right.
A
C
What
if
we
frame
it
as
like,
we
are
a
like,
because
I
don't
think
I
don't
think
the
average
person
necessarily
really
cares
that
that
we
don't
we
don't
author,
the
build
packs.
They
just
want
to
find
the
build
pack
right
and
the
distinction
between
the
project
and
the
vendors
is
maybe
less
important
to
them.
So
I
agree
with
you,
but
I
think
we
could
frame
it
as
like.
C
A
A
A
If
someone
had
come
up
with
a
way
that
we
could
say,
like
you
know,
build
packs,
isn't
the
I'm
gonna
use
the
term
anthony
and
I
have
been
using
the
household
name
right,
build
packs,
isn't
the
household
name
you're
not
gonna,
go
and
search
for
a
build
pack
of
whatever
right
it's
going
to
be
used,
potentially
most
likely
in
some
sort
of
back
end
right,
like
google
cloud
platform
right
like
or
git
lab
as
part
of
auto
ops
right
like
it's
in
a
lot
of
cases
like
an
underlying
technology
that
is
portable
and
can
be
used
in
a
lot
of
different
platforms.
A
Right,
I
don't
know
if,
if
office
hours
would
be,
maybe
too
too
large
of
an
audience,
but
definitely
at
least
within
this
meeting,
set
up
a
time
or
dedicated.
You
know
scheduled
event
that
we
say:
okay,
today
we're
going
to
go
in
there
and
just
literally
discuss
what
this
intro
video
would
look
like
and
set
up
a
mirror
board
right
and
just
like
start
putting
together
like
okay.
What
do
we
want
to
present?
What
don't
we
want
like?
A
C
I
think
some
of
the
the
data
points
from
the
user
interviews
might
be
also
like,
and
you
said
workshop
and
I
know
sam
wanted
to
have
a
workshop,
so
maybe
we
could
marry
them
somehow
that
might
be
nice.
A
Cool,
I
guess
yeah,
do
you
mind
at
least
driving
that
yeah
sure
I
can
bring
this.
A
B
A
Oh
cool
all
right
next
topic,
guidelines
and
build
packs.
Is
that
what
bp
stands
for
best
practices?
Sorry
best
practices?
Okay,
I
don't
know
you're
in
a
build
packs
world.
Bp
stands
for.
D
Yeah
I
I
started
with
an
initial
draft
of
that
rfc,
which
we
discussed
in
the
last
office
hours,
but
like
it's,
it's
it's
not
complete
yet,
and
I
don't
know
if
everyone
here
was
in
the
last
officers,
but
what
we
discussed
was.
There
are
a
few
things
that
are
not
captured
by
the
spec
that
that
still
makes
sense
to
go
in
some
document
where
we
say
that
over
time,
we've
noticed
that
these
are
some
guidelines
or
best
practices
for
different
personas
who
are
dealing
with
buildbacks.
D
D
You
also
want
some
guidelines
for
each
of
these
personas
who
are
using
our
tooling,
and
the
rfc
is
just
about
whether
we
should
create
a
repository
like
this
and
what
what
should
be
sort
of
like
the
overall
high
level,
content
and
structure
of
that
repository,
and
it
doesn't
actually
go
into
details
on
like
what
the
actual
guide
the
set
of
guidelines
would
be.
Just
is
an
rfc
about
like
possibly
creating
a
repository
like
this
and
what
could
go
into.
A
A
Cool,
so
I
think
you
gave
us
a
pretty
good
overview
of
what
this
is.
Personally,
I
haven't
looked
at
it,
so
I'd
like
some
time
to
do
so.
Does
anybody
have
any
questions
on
this.
D
I
mean
not,
I
mean
we
we
could
also
put
in
the
docs
website.
I
guess
in
which
case
it
might
just
be
a
subfolder
in
the
docs
point.
D
The
only
reason
why
it
could
be
a
separate
repository
is
that
if
you
want
like
a
different
process
for
reviewing
and
merging
guidelines
than
we
do
for
documentation,
that
was
the
only
concern
that,
if
you
want
something
more
formal
to
go
into
the
guidelines,
then
what
happens
with
the
documentation.
But
if
not-
and
if
the
process
is
the
same,
then
it
can
just
be
a
subfolder
in
the
docs
repository.
A
B
Hey
young
samuel,
can
I
ask
you
know
if
you
could
just
sum
up
the
motivation
from
me
just
a
little
bit
right
like
if
you
have
best
practices
in
the
code
base?
It's
because
multiple
people
are
going
to
be
collaborating
right
and
you
want
to
lessen
the
learning
curve
for
each
people
right
to
keep
consistency.
B
I'm
guessing!
You
know
if
you
could
just
sum
up
the
motivation
for
best
practices
in
in
like
spec
authoring.
I
I
bill
pack
authoring.
I
guess
platform
authoring.
D
Yeah,
so
I
have
some
of
them
in
the
rfc,
but
like
I'll,
just
read
out
the
headlines
so
like
better
consistency
and
user
experience
for
users
and
authors
across
different
ecosystems.
So,
let's
say
you're
you
you're
familiar
with
ecosystem
x
that
configures
its
build
packs
using
a
certain
way
and
now
you're
moving
to
ecosystem
y,
for
whatever
reason,
maybe
just
some
consistency
amongst
the
two.
Similarly,
like
better,
like
another
point,
is
better
portability
amongst
different
platforms.
D
So
let's
say
your
build
pack
relies
on
certain
details
of
how
back
is
implemented
as
a
platform
as
opposed
to
something
else
like
kpac,
for
example.
So
let's
say
it,
it
allows
configuration
only
through,
like
I
guess,
project
or
normal
files
which,
like
the
project
descriptor,
which,
like
back
implements
but
other
platforms,
don't
then
you
may
be
like
causing
issues.
D
Similarly,
like
as
a
buildback
author,
there
may
be
certain
pitfalls
around
like
how
you're
using
the
api,
where
you
might
discover
you
might
not
discover
issues
with
them
initially,
but
later
on.
As
like,
you
get
more
experience,
you're
you're
sort
of
like
relearning
what
others
have
already
figured
out
by
using
the
api.
D
A
A
Moving
on
dockercon
cfp
sam,
I
believe
you
put
that
on
there
as
well.
D
A
Yeah,
I
don't
think
that
we
organize
you
know
as
a
whole
community
or
project
to
speak
at
any
given
conference,
I,
with
the
exception
of
kubecon,
because
it's
you
know
part
of
the
cncf
and
they
essentially
hold
a
slot
for
us.
A
Yeah,
I
think,
maybe
at
this
point
right
like
at
least
what
I
was
doing
on
slack
was
just
bringing
up
the
opportunity
and
then
again
letting
the
individuals
decide
whether
or
not
they
wanted
to
attend.
A
A
I
just
know
like
I
mean
again
speak
personally
for
myself.
I
don't
have
the
time
to
go
and
do
a
presentation,
and
especially
when
a
lot
of
conferences
would
hope
or
expect
you
to
have
like
a
unique
presentation
right
so
like
they
wouldn't
like
you
to
essentially
reuse
the
presentation
that
you
were
previously
used.
I
think
that
that
makes
the
effort
a
little
bit
more
difficult.
D
Something
that
would
be
interesting
for
me,
maybe
for
the
implementation
team
to
discuss
later
on,
but,
like
we
have
seen
a
lot
of
talks
on
like
how
buildbacks
work
in
a
high
level
overview
and
in
none
of
the
deep
types
dives
do
we
actually
go
into
how
like,
like
the
life
cycle,
actually
works
like
we
do
describe
the
phases
and
everything,
but
I've
not
seen
a
talk
where
it
describes
how
it
works
with
and
and
creates,
lego
compatible.
You
know
this
look.
That
would
be
very
interesting
as
a
talk
again
just
a
suggestion.
B
C
Do
we
think,
because
I
I
feel
that
such
a
talk,
it
would
be
interesting
for
me
to
watch
right
and
anyone
who
contributes
to
the
life
cycle
I
feel
like
we
would
enjoy
having
such
a
talk,
but
do
we
think
that
the
general
audience
of
like
dockercon
attendees
might
who've,
like
maybe
never
even
heard,
of
build
packs
before,
would
be
interested
in
going
going
into
that
level
of?
I
think
that's.
C
Why,
honestly,
that
all
of
the
talks
that
are
out
there
are
like
this
is
how
build
packs
work
and,
by
the
time
you've
explained
that
your
25
minutes
is
up
right.
So
it's
it's
a
challenge
and
I
think
we,
I
agree
that
presenting
some
new
information
would
be
valuable.
I
just
don't
know
how
to
also
hook
in
the
more
casual
listener,
if
that
makes
sense,.
D
Yeah
so
like
the
the
talk
that
reminds
me
of
is
like
there's,
this
talk
by
this
rice,
which
is
like
containers
from
scratch
which,
like
it,
goes
into
a
lot
of
integrity,
details
on
like
how
to
create
containers
from
scratch,
but
it
also
sort
of
keeps
it
high
level,
but
like
something
similar
where
you,
you
start
from
saying
that
you
have
these
pieces
of
information.
Now
you
have.
How
do
you
assemble
them
together
in
in
in
form
of
an
output
image
that
I
guess
the
audience
would
be
niche?
D
But
it's
a
nice
way
of
like
knowing
how
the
oci
spec
is
like
flexible
enough
to
accommodate
a
use
case
like
build
packs
versus
something
that
people
are
mostly
familiar
with,
which
is
like
docker.
So
even
something
like
builder
has
like
similar
semantics,
where
you
have
run
copy
and
etc.
Instead
of
a
dockerfile,
you
have
different
commands,
but
build
packs
are
unique
because
we
we
don't
have
like
the
sort
of
manual
instructions
on
how
to
modify
the
image,
but
rather
that's
all
captured
by
detect
and
build
parts
of
the
buildbacks.
D
And
then
you
have
a
higher
level
orchestrator
that
manages
all
of
this,
so
that's
sort
of
where
I
was
getting
at
that,
even
though
life
cycle
itself
may
be
a
concept
that
may
be
new
to
them,
but
like
just
how
it
works
to
orchestrate
all
of
these
things
together
may
be
interesting
for
people
who
are
familiar
with
the
oci
spec
or
container
images
in
general,
like
weird.
A
Yeah,
I
think,
a
similar
project
that
I
think
still
does
a
pretty
good
job
of
presenting
it.
Maybe
internal
workings
is
something
like
container
d
right
like
nobody
goes
and
uses
container
d
directly,
but
you
could
certainly
find
you
know
presentations
about
container
d,
and
so
I
think
maybe
it
goes
back
to
the
idea
again
that
we
speak
to
so
many
different
audiences,
and
I
think
what
sam
is
bringing
up
is
that
we
haven't
spoken
to
the
audience
where
you
know
they're,
like
really
in
the
weeds
of
how
this.
C
C
I
I'd
be
open
to
working
on
something
like
that.
I
think
I
I
sort
of
share
a
little
bit
of
javier's
like
it's
a
lot
of
work,
but
is
that
something
that
you
know
sam,
if
you
feel
like
you'd,
be
up
for
it
and
you're?
Looking
for
a
collaborator,
I
think
we
can.
We
can
help
out.
D
I'll
go
check
the
cfp
like
how,
since
it's
closing
on
first
I'll
check
what
it
actually
requires,
if
it's
just
an
abstract
and
and
if
the
deadline
is
like
I'll
check,
what
the
deadline
for
the
actual
like
some
some
content
is.
If
there
is
a
deadline
for
the
actual
content
is-
and
I
will
let
you
notice
now,.
A
All
right,
so
it
does
seem
like
we've
gone
a
couple
minutes
over,
so
I
do
want
to
say
this
was
a
very
you
know,
insightful
conversation
in
a
lot
of
aspects,
but
we
do
have
to
cut
it
short
all
right
with
that
said
any
parting
words.