►
From YouTube: Learning Sync: 2021-02-09
Description
Meeting notes: https://bit.ly/38pal2Z
A
Okay:
let's
go
ahead
and
get
started.
I
started
the
recording,
so
we're
we're
off
to
a
good
start,
see
status
updates.
Does
anybody
have
any
status
status
updates
relevant
to
this
sub
team.
A
Doesn't
sound
like
it
as
a
minor
note,
I
was
looking
through
some
issues
this
morning.
There
was
an
issue
for
adding
a
search
capability
to
our
doc's
website
and
I
believe
david
had
mentioned
a
service
that
bootstrap
and
a
whole
bunch
of
other
open
source
projects
use.
A
So
I
went
ahead
and
made
the
request.
Apparently
it
might
take
them
some
time
to
get
back
to
us
whether
or
not
it's
suitable.
I
guess,
but
hopefully
that
works
out
and
we
don't
have
to
actually
implement
too
much
there.
Just
import
a
javascript
thing.
A
B
I
don't
think
there's
more
to
share
from
last
week.
I
know
sam
is
looking
to
get
some
feedback
on
the
scenarios
that
were
proposed
for
the
user
kind
of
user
test
of
some
bill
pack
capabilities,
and
I
think
in
speaking
to
him
it's
it's
been
a
little
difficult
to
identify
a
scenario.
That's
going
to
be
instructive.
You
know
useful
for
us,
but
also
compelling
for
the
person
you
know
doing
the
exercise.
B
So
I
think
at
some
point
in
one
of
the
working
groups,
he's
planning
to
circulate
and
get
feedback
on
the
various
ideas
that
have
been
proposed.
A
Okay,
cool
that
makes
sense.
That
was
going
to
be
my
follow-up
of
how
exactly
do
we
interact,
because
the
last
thing
I
saw
from
them
in
the
user
research
channel
was
some
data
based
on
some
of
the
interviews
that
happened,
yeah
cool,
so
I
guess
we'll
look
forward
to
that.
Let's
see
next
item
is
unlabeled
issues,
as
I
made
mention.
I
looked
at
these
earlier.
We
don't
have
anything
new
here,
so
we
could
consider
that
completed
and
we
had
a
future
topic
of
tagging
issues.
C
B
I
put
that
there
following
our
discussion
last
week,
danielle
and
I
were
I
guess
I
think
the
idea
was
to
tag
we
already
have
some
but
like
to
go
through
and
tag
some
of
the
issues
as
good
first
issues,
so
that
other
people
could,
you
know,
contribute
to
our
docs
more
easily,
and
I
don't
know
if
there's
anything
else,
any
other
ideas
regarding
tagging
that
we
had.
A
Yeah,
so
we're
talking
about
specifically
just
the
good
first
issues
is
that
right.
C
Yeah
we
there
was
a
couple
issues
that
just
seemed
a
little
less
less
writing
than
you
know
some
other,
so
we
figured
it
would
be
good
to
tag
them
as
good.
First
issues.
A
Interesting
yeah.
That
sounds
like
a
good
idea.
I
wonder
if
that
ties
into
the
topic
I
added
for
today,
which
is
work
for
like
mentoring
programs.
I
know
that
was
the
linux
foundation
program.
I
forgot
what
the
name
of
the
program
was,
but
basically
we
could
get
some
assistance,
some
hands
and
one
of
the
things
I
thought
of
like
especially
like
this
search
functionality.
Right.
A
I
know
that
there's
the
google
summer
of
code
and
then
there's
a
google
summer
of
docs
or
maybe
season
of
docs,
sorry
where
there's
like
tech
writers
that
also
come
in
here,
and
so
I'm
not
entirely
sure
exactly
how
this
would
happen,
but
I
am
basically
kind
of
bringing
up
the
the
question
of
maybe
we
should
formulate
some
issues,
or
at
least
maybe
get
some
somebody
to
volunteer
to
work
on
some
work
items
that
could
kind
of
be
thrown
out
to
these
pro
programs.
We
don't
necessarily
have
to
do
the
work
ourselves.
C
But
how
would
we
have
not
like
what
I
don't
it's
interesting?
It
would
be
interesting
to
see
what
requirements
they
have
for
projects
for
that.
Just
because
I
assume,
like
you,
probably
don't,
have
just
one
issue
that
they're
going
to
work
on.
A
Yeah,
so
typically,
I
think
the
programs,
the
way
they
work
is
that
there's
a
certain
amount
of
hours
right,
so
you're
trying
to
find
enough
work
for
them
to
fulfill
that
time
span.
So
you're
kind
of
doing
a
very,
like
almost
precise
estimate
on
how
long
things
should
take
and
get
done
so
yeah.
A
I
don't
think
it
would
be
one
issue,
but
it
could
be
a
set
of
issues
right,
think
of
maybe
an
epic
of
documenting
for
a
very
specific
persona
right
and
we
could
add
a
whole
bunch
of
stuff
associated
to
that,
depending
on
how
many
hours
we
expect
that
to
take.
But
yeah
like
again.
This
is
just
me
throwing
information
out
there
of
a
potential,
not
so
much
saying
that
at
least
I'm
volunteering
right.
But
if
someone
wants
to
volunteer
for
something
like
that,
I
think
it'd
be
great.
A
I
don't
know
I
mean
that
is
the
interesting
like
we
haven't
done
it.
At
least
I
haven't.
I
don't
know
if
anybody
else
has
to
know
exactly
what
the
process
there
is
right.
Is
it
like
hey,
just
throw
again
issues
together
and
be
like
here,
go
figure
it
out
right
and
then
they
just
like
ask
people
within
the
community
just
like.
I
would
assume
sam
did
right
to
some.
A
A
So
that's
the
tech
writing
thing
right
which
again,
once
these
events
start
happening,
or
at
least
deadlines
start
happening,
maybe
we'll
just
throw
them
here
or
throw
them
somewhere
so
that
we
again
try
to
take
advantage
of
them
if
we
feel
like
they're,
valuable,
the
other
ones,
the
google
summer
of
code
and
the
linux
foundation,
those
are
more
technical
right.
So
again,
if
we
wanted
to
add
functionality
to
our
website.
I
think
those
are
very
suitable
for.
A
All
right,
if
there's
nothing
else
there,
we
can
go
on
to
the
next
topic
of
documenting
fundamentals,
layers,
etc.
D
Yeah
I
put
this
on
here.
This
is
actually
something
that
was
on
my
mind
about
a
week
ago,
and
then
we
had,
I
don't
know
if
you
saw
we
had
an
article
on
buildbacks,
go
to
the
front
page
packer
news.
D
I
think
it
caught
up
to
three
or
four,
and
I
made
the
mistake
of
like
responding
to
comments
in
there
and
having
people
tell
me
that
I
don't
understand,
build
packs
or
docker
like
not
even
kidding,
but
one
of
the
things
that
stood
out
to
me,
and
it
was
already
on
my
mind,
was
that
like-
and
I
forget
people
still
fundamentally
don't
understand
anything
any
of
this
stuff
right,
like
docker
layers
and
like
they'll,
equate
updates
of
a
doc
rebuilding
a
docker
image
with
rebasing
and
and
die
on
that
hill,
and
all
that.
D
So
when
I've
tried
to
like
reply
to
those
kinds
of
thoughts
and
not
you
know,
it's
not
always
hostile
like
on
hacker
news.
Sometimes
it's
just
like.
So
how
does
buildback
create
layers?
You
know?
I
think
that
was
actually
the
question
in
slack
I
didn't
really
have
like
a
good.
I
couldn't
find
anything
to
link
to
other
than
like
here's,
the
full
spec
and
it's
in
there
right
like.
D
So
I
actually
tried
to
rework
that
page,
but
it
just
got
me
thinking
about
you
know
trying
to
have
that
like
beginner's,
mind
and
and
not
forget,
even
though
we
need
to
explain
some
really
complicated
stuff,
try
to
keep
the
people
in
mind
that
just
don't
understand
this
stuff
at
all,
so
it
was
just
something
I
wanted
to
highlight
and
I'll.
I
have
that
pr
and
I
think
it
needs
some
tests
fixed,
but
yep.
A
D
One
of
creating
a
build
pack
is
like
I
want
to
put
this
thing
in
a
layer
and
so
like
I
linked
them
to
the
build
app,
and
I
don't
know
if
I
don't
know
if
the
person
figured
it
out
or
not,
but
you
know
there
wasn't
a
good
like
anchor
link
for
creating
a
layer.
So
that's
the
like.
D
I'm
the
very
beginner
build
pack
author
now,
the
other
ones
I
saw
like
yesterday
with
the
hacker
news
thread,
was
definitely
more
like
people
evaluating
build
packs
for
their
own
use
and
even
got
like
these
are
not
all
just
like
hacker
news.
Nerds
like
I
definitely
got
some
questions
via
email
from
people
that
were
legitimately
interested
in
in
using
build
packs
and
the
so
they're
buildpack
users,
they
kind
of
think
they
get
docker
file,
but,
like
you
know,
they
kept
asking
about
docker's
limitation
of
having
the
layers
being
linear.
It's
like
no!
D
No,
that
is
a
docker
file
limitation
and
so
those
kinds
of
things
like
the
question
that
person
asked
me
was,
you
know,
can
you
can
you
point
me
to
something
that
maps
the
build
packs
concepts
to
the
docker
concepts
or
something
like
that
right,
and
so
I
sent
them.
Actually,
I
think
our
kubecon
talks
from
2019,
the
one
I
did
with
steven
and
then
the
one
I
think
terence,
did
with
emily
cover
that
pretty
well,
but
we
don't
have
like
a
blog
or
a
page
or
something
yeah
right,
yeah.
D
Yeah,
that's
right.
We
were
supposed
to
create
this
like
repo
or
whatever
of
presentation,
but
yeah.
So
I
guess
like
to
your
question
javier,
like
these
are
very,
very
beginner
entry
level
folks,
but
it's
like
because
they're
trying
to
evaluate
it,
we
kind
of
have
to
explain
these
more
complicated
things
to
to
like
demonstrate
the
benefits
beyond.
Just
I
think
I
mean
I
think
for
some
people,
it's
like
pack
build
wow
that
worked
great,
but
then
other
people
like
I
have
this
docker
file
and
it
works.
D
Why
would
I
switch
and
and
to
explain
that
you
have
to
be
like
well
what,
if
you
have
a
thousand
docker
files-
and
you
know
that
kind
of
stuff?
So
it's
just
something
you
know
that
we
don't
have
to
like
do
anything
today
to
fix
anything
it's
just
as
we're
like.
I'm
certainly
going
to
be
thinking
about
this,
as
I
write
more
blogs
and
docs
and
stuff,
but
yeah.
A
We
have
a
essentially
like
a
reference
article
where
someone
essentially
tries
to
migrate
a
doctor
file
over
to
a
build
pack
right
where,
like
the
the
concepts,
are
mapped,
I
feel
like
that
should
be
not
so
much
trivial
but,
like
the
first
experience
right,
it's
like.
Oh,
I
had
this
docker
file
and
I
wanted
to
create
a
buildpack
compatible
image
out
of
it
right,
and
so
I
did
this
instead,
if
we
don't
have
that.
A
A
really
good
yeah,
really
good
blog
article
right
to
kind
of
get
past.
That
first
mindset.
D
I
would
volunteer
to
write
that
unless
somebody
else
wants
to,
because
I
think
that's
a
great
idea,
just
here's
a
docker
file
and
even
take
one
from
like
a
legit
real
project
and
just
write
a
build
pack
from
it
just
way
to
build
back
from
it
I
mean
it
depends.
I
mean
there
are
plenty
where
it's
like
it's.
There
are
plenty
where
it's
so
trivial
that
it's
like
this
isn't
actually
a
good
example,
because
you
know
it
just
doesn't
demonstrate
it
well
or
something,
but
right
right.
D
Gender
yeah,
I
mean
yeah,
I
I'm
such
a
bad.
I
think
the
word
I
think
the
word
is
diminisher
like
by
volunteering.
Now
nobody
else
is
gonna.
Do
it
but
I'll
be
busy
with
the
registry
at
least
for
another
week.
So
if
anybody's
interested
to
you
know
have
at
it.
D
C
B
Yeah,
I
I
mean
if
anyone
has
like,
if
you
had
come
across
a
docker
file,
you're
like
this.
Actually
this
seems
like
it
would
be
perfect.
You
know
that
that
would
be
great.
A
B
The
only
so
I
mean
I
know,
I'm
kind
of
like
taking
this
there's
two
right.
There's
like
two
ways
we
can
go
with
this.
One
is
for
the
purposes
of
our
of
our
interview
and
the
others
for
our
docs,
and
so
maybe
we
do
something
different.
You
know,
depending
on
which
way
we're
going,
but
the
only
thing
that
we
kind
of
want
to
keep
in
mind
for
the
the
interview
is
that
we
don't
necessarily
know
what
background
the
person
we're
interviewing
is
gonna
have,
and
so
it
should
be,
ideally
something
that's
that's
accessible
to.
A
Yeah
I
mean,
I
think
at
least:
is
there
like
a
baseline,
where
they
have
to
at
least
have
some
container
knowledge.
B
I
think
so
I
can
go
back
and
look
at
the
the
people.
It's
like
people
from
the
first
round
who
demonstrated
enough
familiarity
with
the
technology.
A
Yeah,
so
I
just
posted
a
link
to
a
doctor
file
from
the
spring
pet
clinic.
You
could
look
at
that
and
see
whether
or
not
that
works.
A
Yeah
and
then
the
from
right,
I
think
the
way
I
think
about
that,
like
the
from
open,
jdk,
11
jre,
how
that
translates
over
to
stacks
might
be
a
good
way
to
explain
how
stacks
work
and
why
they
are
rebaseable
and
updated.
I
don't
know.