►
From YouTube: Learning Sync: 2021-01-19
Description
Meeting notes: https://bit.ly/38pal2Z
A
A
Guide
yeah,
I
haven't
actually
looked
at
what
or
how
that
is
presented
on
the
website.
Just
quite
yet
so
should
probably
do
that.
C
C
Looking
into
additionally
to
actually
publishing
the
samples
built
backs
on
the
registry,
there
was
a
discussion
about
that
in
the
distribution
channel,
I'm
just
trying
to
figure
out
what
to
do
and
for
versioning
things
of
the
sort.
A
C
Not
really
sure
it's
nice
not
having
to
worry
about
actually
explicitly
versioning
the
sample
build
packs,
which
makes
it
a
bit
annoying.
We
could
you
know
just
keeping
like
be
conscious
of
what
we
actually
release,
or
maybe
we
don't
actually
publish
I'm
not
I've
been
have
to
think
bit
more
deeply.
That
was
just
something
that
came
to
mind
that
I
wanted
to
discuss
and
think
out
a
bit
more.
If
anybody
has
any
other
suggestions.
D
Yeah
I
mean
I
definitely
lean
towards
not
publishing
them,
but
I
also
don't
feel
super
strongly
about
that.
With
regard
to
versioning,
is
it
possible
to
do
zero,
zero,
zero
and
then
like
dash
beta
or
something
like
that?
Never
actually
have
any
numbers
and
I'm
guessing
nobody
knows
off
top
of
their
head,
but
that's
one
possibility,
I
would
say
the
hill
that
I
would
die
on
is
less
than
1.0.
C
The
the
reason,
the
the
thing
that
drove
me
to
this
is
or
that
that
made
me
think
about
it-
is
because
there's
an
issue
in
samples
from
I
think
cora
from
vmware
about
having
some
published,
or
you
know,
packaged
version
of
the
build
that
sampled,
the
buildback,
so
she
could
use
it
in
demos.
C
So
once
that
was
the
case,
you
know
she
had.
She
suggested
just
having
a
zip
file
that
we
can.
You
know
she
can
download.
I
was
like,
instead
of
doing
that,
it'd
be
better
to
at
least
demonstrate.
Oh,
we
have
this
registry.
D
I'm
curious,
I'm
curious
what
she's
doing,
though,
because
like
what's
wrong
with
the
real
build
pack
in
the
registry
or
is
it
like?
Is
she
trying
to
shortcut
some
part
of
the
the
demo
process?
It's
just
like
that.
I
mean
I
definitely
get
doing
things
for
like
is
she
a
dev
advocate
is
that
is
that
what
her
role
is
yeah.
D
That
doing
things
like
even
special
pac
commands
like
like,
like
the
create
build
pack-
that's
not
exactly!
I
don't
have
pr
for
like
creating
build
pack,
scaffolding,
it's
not
exactly
the
same
thing,
but
I'm
definitely
in
favor
of
doing
things
that
make
education
and
stuff
like
that
easier.
D
B
C
C
A
We
could
do
something
very
similar
to
that
with
if
we
use
send
versioning,
semver
versioning
and
then
use
metadata
right
that
should
be
allowed
by
the
registry
right.
B
A
So
sever
versioning
would
have
like
0.0.0
plus
you
know,
and
then
you
could
do
like,
oh
that,
okay,
so
the
part
after
the.
A
A
D
D
D
The
real
yeah,
the
real
problem
is
that
we're
not
in
the
business
of
making
build
packs
right.
It's
like
hey,
like
here's.
How
you
should
go,
learn,
build
packs.
We
don't
have
any
like
because
we
want
to
be
neutral,
but
it
definitely
comes
up
again
and
again,
but
I
also
don't
want
to
get
in
the
business
of
cmb
build
cmb
of
official
build
packs
unless
it's
something
really
truly
ubiquitous,
like
potentially
like
an
app
to
build
pack
or
something.
A
A
Okay,
moving
on
user
research,
do
we
have
an
update
here.
B
I
don't
think
much
changed
from
last
week.
Sam
is
conducting
the
first,
I
think,
four
to
five
interviews,
and
I
know
he
got
feedback
on
some
of
the
questions
and
wording
in
the
working
group
on
thursday.
So
I
think
once
those
first
few
interviews
are
completed,
there
will
be
kind
of
like
a
regroup
and
maybe
either
reach
out
to
more
people
or
choose
like
specific
people,
to
try
out
features
of
build
packs
and
give
their
feedback
on
like
a
very
narrow
set
of
capabilities.
A
Cool
and
yeah
from
what
I
saw,
I
think
he
shared
some
pieces
of
information
in
the
user
research
channel.
So,
if
you're
interested
in
looking
at
some
of
that,
that's
where
it
resides.
A
Okay,
moving
on
unlabeled
issues,
just
looking
at
those
real
quick,
we
have
four
so
great
seems
like
we've
been
adding
stuff
to
this
the
operator.
How
do
we
control
location
of
layers?
Isn't
that
an
implementation
concern.
B
B
A
Is
this
implementations
as
well?
I
guess
it
could
be
platform.
C
A
D
Done
there
I
was
going
to
say
I
feel
like
the
spec
is
also
unclear.
It's
not
clear
enough
and
that's
what
we're
working
through
with
stack
stackpacks
right
now
is
the
a
lot
like
the
first
phase
of
of
it
is
just
mixing
stuff
in
the
spec,
which
is
also
yeah,
which
is
in
part,
moving
mix
and
validation
to
the
lifecycle,
so
yeah
cool.
C
C
Oh
that
I
that
I
put
for
both
implementation
and
platform,
because
probably
both
of
them
should
have
some
troubleshooting
things.
A
Oh
yeah,
like
that,
would
depend
really
based
on
the
the
page
right.
B
A
D
Yeah,
I
just
wanted
to
share
this
doc.
No,
I
don't
think
there's
much
to
do
for
us.
I
do
have
a
pr
open
for
publishing
to
the
registry
other
than
that.
I
you
know
that
there's
blogs
that
are
gonna
be
a
part
of
the
the
announcement.
D
I
think
travis
will
probably
write
those,
but
you
know
we
own
the
blog,
so
I
think
there's
a
bit
of
a
chicken
and
egg
problem
in
that,
like
you
want
to
have
the
docks
out
there
when
you
do
the
launch,
but
when
you
put
the
docks
out
there,
it's
sort
of
like
a
launch,
so
I
think,
like
it's
easy
enough
to
do
something
like
the
publish
which
is
a
separate
page.
D
Initially,
I
was
planning
on
having
like
a
page
that
was
here's
how
you
consume
from
the
registry,
but
I
think
it's
more
that
it
more
should
be
just
pervasive
through
the
docs
yeah
like
it
should
just
kind
of
be
the
way
it
works,
sort
of
yeah
like
if
we
have
a
here's,
how
you
use
the
registry
page
like
we're
doing
something
wrong
like
it.
D
Should
just
work
or
you
shouldn't
really
have
to
think
about
it,
so
I
think
the
specifying
build
packs
page,
which
talks
about
the
urls
and
that
was
recently
updated
to
include
the
registry
is
sufficient,
but
yeah.
So
if
you
haven't,
if
you
think,
there's
anything
else
that
belongs
in
the
dock
feel
free
to
add
it,
I
think
you
all
have
edit
access
from
that
link.
A
So
I
guess,
how
are
we
working
through
this
document?
Is
it
something
that
you
and
travis
are
owning?
Is
it
something
that
we
need
further
collaboration
and
coordination.
D
You
know
I
kind
of
see
it
as
like
distribution
team
owns
this
since
distribution
team
is
sort
of
responsible
for
the
launch,
like
I
said,
travis
is
gonna.
Do
the
blogs
I'm
doing
the
docs,
so
it's
more
awareness
that
I'm
bringing
it
up.
If
you
want
to
contribute
to
it's
absolutely
fine
but
yeah,
it's
really
distribution
team's
responsibility.
The
way
I
see
it.
B
D
Yeah,
we
could
do
it
that
way.
I
guess
what
I
was
thinking
was
like
just
more
incrementally
roll
things
out
like
add
this
page,
like
the
specifying
urls
or
specifying
build
packs
with
the
url
uri
stuff
is
kind
of
like
that,
the
purpose
of
it
being
like
to
slowly
get
people
trying
it
and
using
it
like
we're,
starting
to
move
over
to
it
completely
on
the
heroku
side.
D
Just
to
you
know
very
verify
that
everything
works.
So
you
mean
you
mean
like
a
release.
Branch
on
the
docs
repo.
Is
that
what
you
were
saying.
A
Was
to
have
like
just
one
big
event
right
versus
incremental.
That
would
be
a
challenge.
I
don't
feel.
D
Strongly
about
the
incremental
thing,
maybe
how
about?
Let's
do
this?
Take
take
a
look
at
the
the
pr
that
I've
linked
there
for
publishing
to
the
registry.
Just
when
you
get
a
chance,
it's
not!
It's
not
urgent
and
see
what
you
think
about
that
going
in
before
the
like
launch,
where
I
see
the
the
ga
launch,
as
being
you
have
a
tweet,
you
do
a
blog
post,
I'll,
probably
just
reach
out
to
like
dev
advocates,
I
know
and
be
like
hey.
D
You
should
start
using
this
in
your
demos
and
maybe
we'll
get
some
content
on
dev2
or
whatever
that
kind
of
thing,
but
before
that
it
would
be
just
like.
Oh
yeah
there's
a
doc
there,
and
then,
when
somebody
asks
a
question
you
link
to
it.
D
A
B
C
Cool
yeah,
I
don't
know
if
you
saw,
but
I
I
opened
up
an
issue
on
on
samples
to
add
some
of
those
to
samples
as
well
or
oh.
That
was
something
different
that
was
about
the
metadata
and
pack
never
mind.