►
From YouTube: Learning Sync: 2021-01-26
Description
Meeting notes: https://bit.ly/38pal2Z
B
B
B
Yeah,
a
lot
of
github
came
out
of
the
ruby
community
and
terence,
and
I
both
came
out
of
the
ruby
community
like
in
the
very
early
days,
but
then
also
there's
a
lot
of
ex
hirokai
over
there.
Yeah
yeah
connections
help,
but
it
was
yeah.
It
was
a
little
unfortunate.
I'm
surprised
that
happened
I
get
with.
I
get
what
they
were
trying
to
do,
but
it's
like
yeah.
If
I
have
a
page
with
a
path
to
docs.
That's
just
not
gonna
work
like
that
can't
be.
A
B
B
B
Yeah,
I
think,
there's
still
a
bunch
that
can
be
inferred
like
the
the
stuff
about
bash
and
docker
file.
I
think
confirms
that
our
bash
based
examples
are
appropriate
for,
like
the
getting
started
stuff
yeah.
B
I
do
think
like
this
is
less
of
a
learning
thing,
but
terence-
and
I
have
been
talking
about
like
a
lib
buildpack.sh
kind
of
thing
which,
after
this
user
feedback,
feels
like
a
worthwhile
investment
like
we
were
talking
about
something
that
would-
and
I
bring
this
up,
because
I
think
we
would
probably
want
to
use
it
in
the
docs
to
remove
like
the
boilerplate
and
stuff
like
that.
You
could
basically
just
source
this
thing,
and
then
you
wouldn't
have
to
have
a
bunch
of
the
complicated
thing
like
struck
like
control
flow.
B
Yeah,
like
one
of
the
things
we
were
talking
about
was
you
could
take
some
of
the
tamil
files
and
sort
of
like
deserialize
them
onto
the
file
system,
like
in
the
way
that
we
have
the
m
files
so
like.
If
you
have
build
dot,
build
packs,
slash
id
dot
id
or
whatever
you
could
actually
have
a
directory
called
build
packs
a
directory
under
that
called
or
a
directory
called
build.
The
directory
called
build
packs,
a
directory
called
id,
or
maybe
a
file
called
id
with
a
string
in
it.
B
That
is
the
id,
and
then
you
don't
need,
like
jq
or
yj
to
parse
the
tamil.
It
might
be
easier
for
bash
programmers
dash
programmers.
A
It's
still
fun
basketballs
interesting,
that's
interesting!
Just
because
I
mean
for
the
project,
for
I
mean
there's,
always
a
struggle
of
being
too
opinionated
or
not
opinionated
enough.
I
you
know,
like
the
project
lib
build
pack
isn't
really
used.
I
mean
certainly
on
the
potato
side:
it's
not
really
used.
I
don't
know
whether
it's
used
in
heroku.
B
B
B
B
B
B
B
Yeah,
I
see
the
sample
one
I'll
sign
that
to
me
too
I'll
get
those
done
this
week,
yeah,
so
that
kind
of
dovetails
into
the
registry
launch,
which
I
want
to
talk
about
so
dave-
and
I
were
talking
about
this
week,
potentially
well,
potentially
this
week
or
next
week
doing
a
pack
launch
with
the
moving
the
registry
commands
out
of
experimental
and
then
travis
and
I
have
been
talking
about
like
we're,
gonna
ship,
pretty
soon
a
detail
page
for
registry.buildpacks.io,
which
I
don't
actually,
if
you
haven't
seen
it.
B
A
B
B
Right
I've
started
a
conversation
with
them,
I'll,
probably
nudge
them
next
week.
If
I
haven't
heard
anything
yeah,
I
wanted,
I
think,
what
they're
they're,
trying
to
figure
out
if
they
want
to
put
in
one
big,
build
pack
that,
like
represents
that's
sort
of
like
analogous
to
their
builder
or
if
they
want
to
split
them
all
out
or
if
they
want
to
do
both.
B
I
told
them
any
of
those
is
fine,
like
I
told
them,
the
one
big
build
pack
is
kind
of
less
preferable,
but
if
they
were
to
do
one
big,
build
pack
and
publish
the
individual
build
packs,
they
were
worried
about
the
interactions
they
were.
They
felt
that
their
individual
build
packs,
wouldn't
work
well
in
isolation
or
wouldn't
compose
well,
which
is
like,
I
think,
on
the
vmware
side
and
heroku
side.
We're
like
yep,
been
there
we've
sort
of
taken
measures
from
our
own
experiences
to
make
sure
that
they
work
well
together.
B
But
even
if,
even
if
that's
true,
I
think,
publishing
them
individually
would
help
them
evolve
into
the
you
know:
individual
build
packs
that
could
be
used
composed
whatever
so
but
yeah
anyways.
So
the
things
that
need
to
happen
for
learning.
I
have
a
pull
request
out
for
the
documentation
to
publish
to
the
registry,
including
how
to
automate
it
with
github
actions,
and
we
also
also
at
some
point,
have
a
pr
that
just
links
to
the
registry.
B
Do
you
think
we
should
have
like
just
a
link
at
the
top
on
the
home
page?
That's
like
docs
search
for
build
packs
or
something
like
that,
or
should
it
be
more
buried
in
the
docs
sort
of
and
just
sort
of
sit
alongside
other
things.
A
I
think
we
could
have
a
banner
for
it.
I
think
it
probably
makes
sense
to
like
have
a
banner
on
the
website
anyways
for,
like
oh,
the
new
funk,
like
you
know,
when
we're
releasing
a
new
thing
just
because
I
don't
think
everybody
as
much
as
we
we.
You
know.
We
hope
that
people
are
like
eagerly
looking
at
every
single
change
to
our
docs.
I
don't
think
that's
you
know
actually
what's
happening.
B
Yeah,
the
alternative
would
be
a
change
log
where
we
could
just
have
a
stream
of
new
things,
regardless
of
whether
it's
pack
or
implementation
or
whatever,
like
that's,
that's
a,
I
think,
a
useful
pattern,
but
I'm
not
sure
we
have
enough
to
make
that
something
people
would
check
regularly
and
then
just
if
they
don't
check
it
regularly.
It
just
wouldn't
be
very
useful.
B
A
One,
I
guess
this
is
more
of
a
random
question,
but
where
should
when
people
ask
and
slack
let's
say,
questions
about
heroical
build
packs,
or
I
guess
should.
Is
it
like
best
for
me
to
just
tag?
I
guess
you
know
danielle
or
joe.
A
B
No,
and-
and
it's
really
hard
to
discern
like
a
lot
of
time-
I
think
the
rogue
buildbacks
get
a
lot
of
use
off
of
heroku
and
in
those
cases
I
really
wouldn't
want
to
direct
them
to
like
heroku
support
channels,
because
it
just
kind
of
muddies
our
like.
Oh
you're,
not
actually
doing
this
on
heroku.
Well,
I
should
that
would
have
been
nice
to
know
so
it's
best,
I
think,
to
keep
that
in
those
kinds
of
questions
in
the
cmv
slack.