►
From YouTube: Learning Sync: 2021-05-25
Description
Meeting notes: https://bit.ly/38pal2Z
A
I
know
we
have
this
new
thing
about
a
scribe.
Yeah,
I
guess,
do
you
know
anything
about
that
like
what
that
is
exciting.
A
B
A
A
All
right,
so
that
makes
me
the
facilitator
right.
Yes,
all
right,
let's
go
through
status
updates.
I
can
go
through
this
one
real
quick
yesterday,
I
think
you
saw.
I
did
a
little
bit
of
reviews
on
the
docs.
The
doctor
file
or
docker
comparison
looks
really
good,
so
appreciate
that
I
did
start
doing
the
yeah,
the
git
pod
integration
stuff,
which
hopefully
it's
not
too
much
of
a
burden
into
all
our
repos.
A
I
did
get
some
feedback
or
more
or
less
a
question
about
whether
or
not
we
had
too
many
integrations
in
our
repos,
and
I
kind
of
I
I
you
know
specifically
on
gitpod.
I
pushed
back
in
the
form
that
this
isn't
like
some
of
the
other
github
action
integrations
or
bot
integrations
it's
more
like
a
configuration
for
tooling
that
people
may
or
may
not
want
to
use
personally,
I'm
using
it.
So
obviously
I
have
a
personal
desire
to
for
it
to
be
integrated
or
available
so
yeah
any
feedback.
A
There
would
be
appreciated
if
we
want
to
talk
about
that.
Other
than
that,
I
did
notice
that
in
a
community
page
our
slack
button
was
missing
because
we
no
longer
use
slack
in
so
I
went
ahead
and
created
the
quick
fix
for
that.
B
Yeah
for
me,
I
was
mostly
just
addressing
like
fixing
that
dockerfile
comparison
page
and
addressing
your
comments.
Sorry
thanks
and
think
addressed
most
of
it.
One
other
interesting
thing
that
I
think
we
may
want
to
talk
about
later
is
like
we
track
the
issues
in
docs
repository,
but
I
think
we
also
own
the
community
repository
at
least
I
get
tagged
as
a
learning
maintainer
whenever
someone
opens
up
a
request
there,
so
I
don't
know
if
you
want
to
track
the
issues
there.
B
Yeah,
I
think,
last
time
we
mentioned
a
couple
of
things
around
how
to
get
more
dog
contributors,
like
maybe
adding
like.
B
B
Recently,
I
know
just
like
we
were
reaching
out
to
people
for
like
integrations
with
cnb
or
like
where
we
want,
like
their
stuff
integrated
into
buildbacks.
I
was
thinking
about
the
reverse,
where
other
projects
are
considering
integrating
cnb,
so
we
have
the
adopters
page.
I
know
which
is
like
people
who
have
already
adopted
cnb.
I
I
wanted
to
figure
out
whether
there's
like
projects,
organizations
considering
the
adoption
and
whether
we
can
track
that
somewhere,
so
that
if
they
need
help
or
they
get
stuck
on
something,
maybe
we
can
reach
out
to
them.
A
A
Yeah
that
makes
sense
cool,
also
added
that
to
the
agenda.
Do
you
have
a
particular?
Well,
let's
go
through,
I
guess
the
other
stuff,
like
standing
item
user
research.
I
don't
think
there's
anything
here
given
that
at
least
not
here
to
get
an
update
there
and
I
don't
think
there's
going
to
be
a
lot
of
movement
there
anyway.
A
The
next
item
is
the
unlabeled
items,
so
this
is
the
kubecon
slides.
Is
this
talking
about
the
office
hours
ones.
B
A
Okay,
moving
on
so
we've
got
three
topics,
all
four
of
which
are
yours,
which
one
do
you
care
more
deeply
about
that
you
want
to
get
into
the
weeds
first.
A
B
A
Yeah,
I
guess
this
is
interesting,
so
if
you
go
to
the
community
like
the
code
tab
there,
there
is
a
quote-unquote
contributor's
guide
that
I
produced
a
while
back.
A
A
I
guess
what
may
be
missing
is
like
the
visibility
to
this
document
for
one
right
and
then
maybe
any
improvements
to
this
document
again.
This
is
a
solely
biased
because
I
wrote
it
right
so
like
I.
If
there's
a
different
approach,
I'd
be
interested
to
hear
about
it.
B
I,
for
what
it's
worth
like
last
time,
we
were
discussing
something
similar.
So,
for
example,
there
was
this
page
called.
What
can
I
do
for
mozilla,
which
is
like
their
version
of
like
contributing
sorry?
So
you
can.
You
can
tell
this
that
this
is
basically
powered
by
a
yaml
template
which
you
can
modify
and
it's
got
these
questions
and
links.
So
you
you
ask
these
questions
and
then
these
links
take
you
to
the
next
question
or
a
leaf
node,
which
is.
B
So
like,
if
you're
interested
in
writing
more
code
like
no
not
interested
user
design,
okay
and
then
like
you,
can
click
here
and
it
takes
you
to
the
exact
repository.
A
Like
this
particular
page,
right
is
difficult
to
discover
because
even
well,
I
I
feel
like
a
lot
of
documents
on
github
itself.
Right,
like
that
are
hosted
on
github,
are
hard
to
discover
and
hard
and,
like
even
maintainers,
I've
seen
them
point
to
other
resources,
like
blog
posts
or
whatever,
like.
Let's
say:
what
is
it
the
commit
signing
right
like
we
have
a
page
for
commit
signing
as
part
of
our
high-level
contributing
guide
right?
A
A
I
see
it
as
they're,
just
not
discoverable
enough
or
maybe
they're
not
up
to
par
with
what
we
really
want,
and
so
one
of
those
two
things
needs
to
be
addressed,
or
maybe
both
right,
and
so
I
do
think
that
to
solve
the
discoverability
aspect
of
it
right,
if
we
have
it
on
the
docs
page
or
sorry,
if
we
have
it
on
our
actual
website,
that
would
make
it
by
far
a
lot
more
discoverable
right
and
to
then
talk
about
the
second
point
where
it
might
not
be
up
to
par
with
what
we
need
or
want.
A
B
Yep
should
should
there
also
be
like
direct
links
here
to
both
the
repositories
and
like
a
filter
with
good
first
issues,
tagged
in
each
of
these
repositories,
so
that
okay,
I'm
new
right.
So
one
thing
that
I've
noticed
in,
like
the
only
example
I
can
think
of
is
like
the
python
bug
tracker.
B
This
may
be
a
good
starting
point
for
you
to
discover
more
components
or
to
dive
deeper
into
that
same
component.
I
don't
know
if
you
have
any
thoughts
on
like
managing
issues
in
that
way,
like
labeling
them
with
more
details.
I
guess
it.
It
also
makes
sense
when
you
have
enough
issues
to
require
that
level
of
management.
A
Yeah,
that's
I
was
going
to
get
into
the
idea
or
the
notion
that
I
think
we
could
definitely
improve
the
curating
of
issues
right.
I
think
we've
had
this
discussion
at
least
internally,
where,
as
developers
as
engineers,
we
tend
to
focus
on
getting
stuff
done
right
and
we
are,
you
know,
let's
say
that
we're
ultimately
very
productive
in
that
fashion,
but
it
doesn't
seem
like
it
scales,
really
well
right
when
we
think
about
like
okay.
So
now
we're
just
a
handful
of
developers
in
this
sort
of
silo.
A
You
know
cranking
out
issues
as
much
as
possible,
but
if
we
really
want
to
scale,
I
think
there's
a
lot
to
be
said
about
being
able
to
curate
issues
so
that
others
can
consume
them.
So
we
ended
up
with
this
like
triage
process
at
some
point.
So
if
you
click
on
the
triage
page
down
there
right
like
this
actually
goes
and
like
tells
you
like
what
a
good
first
issue
looks
like
right,
because
this
is
something
that
we
identified,
that
you
can't
put
a
good
first
issue
label
on
something
that
isn't
clearly
defined
right.
A
So,
like
you,
you
can't
go,
and
I
don't
know,
what's
a
really
good
example,
like
even
the
source
metadata
thing
right,
that
I'm
a
mentor
for
right,
like
if
it
just
says,
implement
source
metadata
as
the
issue-
and
it
just
says,
look
at
this
rfc
like
it's
super
big
right,
but
we
added
like
the
criteria
for
good
first
issues
to
have
acceptance,
criteria
right
and
so,
like
the
responsibility
of
this,
I
think
lands
on
the
maintainers
to
do
their
part,
and
I
think
just
maybe
overall
more
focus
there
and
again.
A
If
the
quote-unquote
process
needs
to
be
improved,
then
we
should
be
looking
at
that.
But
this
is
what
we
came
up
with
right.
So
I
think
at
this
point
I'm
just
kind
of
giving
you
historical
context
of
where
we've
been
and
what
is
available.
A
B
Because
I
saw
this
and
then
I
thinks
somewhere
yeah
this
one.
I
also
saw
this
which
went
into
this
rfc,
which
I
think
you
created
around
like
synchronizing
labels,
so
that
people
know
exactly
which
labels
should
be
there
in
the
repository
or
like
if
you
need
new
ones
and
what
the
description
for
each
of
them
should
say
across
different
repositories,
yeah
and
so
like,
and
I
was
just
wondering
like.
What's
do?
B
We
have
any
updates
on
these,
because
these
are
like
a
bunch
of
these
are
issues
that
were
opened
in
2020
and
hey.
I
don't
see
any
updates
on
them,
so
I
was
just
going
through
a
community
repository
and
wondering
like.
Should
we
be
actively
like
figuring
out
whether
this
is
still
needed,
if
not
close
them
or
if
it's
needed,
like
figure
out
how
to
track
them?.
A
You
know,
I
guess
one
thing
that
we
do
do
for
other
sub
team
sinks.
Like
the
platform.
We
have
a
needs,
discussion,
standing
item
and
so.
B
A
A
So
that
seems
something
tangible
right
now
to
just
add
a
needs
discussion
to
our
standing
items
as
far
as
the
other
ones
go.
I
guess
what
is
like.
I
get
that
they're
still
right
and
I
get
that
we
need
to
update
them.
Is
there
anything
specific
that
you're
proposing.
B
I
was
just
wondering
whose
responsibility
is
it
to
update
this
thing,
whether
it's
our
responsibility
or
not?
If
it
is,
then
we
should
include
this
in
our
like.
Like
the
I
don't
know
so
like
these
unlabeled
issues,
I
I
wonder
if
we
should
have
like
a
stale
issues
or
stale
br
section,
which
shows
issues
that
are
more
than
30
days
old
without
activity
yeah
so
like
at
least
we're
tracking
things
that
that
are
getting
stale.
I
I
remember
I
read
somewhere
where
it
was
like.
I
think
it
was
the
contribute.
B
I
don't
remember
somewhere
in
the
community
repository,
it
was
like
30
days
for
stale
issues
or
something
like
that
was
proposed,
like
you
should
not
leave
a
pr
open
for
seven
days
without
like
getting
asking
for
some
updates
and
issues
for
30
days
without
asking.
I
don't
know
where
I
saw
that.
A
Yeah,
oh
no.
I
I
feel,
like
we
start
getting
into
this
like
problem
that
I
guess
not
only
us
all
face
right
but,
like
I
think
the
open
source
communities
faces
where
it's
like.
If
you
go
to
like
any
major
project,
I'm
sure
you'll
find
a
lot
of
outdated
old
issues
right.
A
So
that's
like
one
option,
then
there's
the
other
option
where
you
have
like
a
very
aggressive
stale
bot
right
like
that
is
always
just
nagging
you
like:
hey,
I'm
gonna
close
this
and
you're
like
no.
No,
it's
still
important
right
and
like
we
still
care
about
it
and
you
know
kind
of
getting
caught
in
that.
I'm
not
entirely
sure
which
one
of
the
two
is
best
right
now.
A
We're
definitely
on
the
former,
where
we're
just
kind
of
letting
stuff
stack
up.
B
I
was
thinking
rather
than
like
something
active
like
a
stale
board
if
we
just
like,
have
a
link
here
which
shows
old
issues
and
we
try
to
go
through
some
of
them
manually,
maybe
in
the
most
recent
order.
So
we
have
the
most
recent
issues
on
top
yeah
or
the
most
recent
pull
request,
because
I
think
we
don't
do
it
for
pull
requests
either
and
then
some
pull
requests
end
up
sitting
there
for
a
long
time
until
someone
notices
and
like
it
doesn't
have
to
be
like
a
bot
reminding
us.
A
Yeah,
I
totally
agree,
I
think
that's
worked
fairly
well
for
us.
I'm
not
sure
how
well
it'll
scale
overall
right,
but
it
has
worked.
Okay.
I
don't
like
that.
It's
like
a
that
there's,
like
synchronicity,
necessary
like
us
having
to
go
into
this
room
to
like
discuss
them,
so
I'm
not
a
huge
fan
of
that,
but
I'm
maybe
not
trying
to
solve
that
right
now.
Right,
like
maybe
that's
something
that
we
could
solve
later.
A
Do
you
mind
if
I
add
that
as
an
action
item
for
you
to
create
just
like
that
thing,
yeah
yeah?
Thank
you.
A
A
B
B
That's
tracking
issues,
I
think
that's
pretty
much
it.
This
was
like
the
other
integration
tracker.
I
was
curating
today
about,
like
other
open
source
projects
that
are
considering
buildback
integration
and
like
it,
it
may
be
useful
for
us,
as
well
as
like
other
maintainers,
to
track
like
which
projects
like.
So
these
are
links
to
specific
issues
with
say
that
a
add
buildback
support,
and
then
I
have
like
this
quick
description
of
what
it
does,
and
I
don't
know
if
you
want
to
update
it
over
time.
B
It's
saying
like
hey,
this
was
the
blocker,
or
how
did
you
find
these?
So
I
created
a
random
github
search
which
did
a
lot
of
filtering
on
organizations
and
keywords
and
tried
to
find
open
issues
and
then
sought
through
them
in
some
some
order.
But
these
looked
interesting
to
me
like
some
of
them,
for
example,
are
like
this
backstage
one.
B
It's
a
cncf
sandbox
project,
which
is
like,
I
think
it
was
created
by
spotify
for,
like
some
sort
of
a
developer
box
that
lets
you
create
template
services
easily
or
something
like
that,
and.
A
B
Into
it,
but
they
were
discussing
like,
but
the
build
packs
would
be
a
good
way
to
like
quickly
start
creating
images
for
developers
or
things
like
that,
so
this
like,
given
that
it's
also
a
cncf
project,
I
thought,
like
maybe
it's
worth
reaching
out
to
them,
saying
that
hey
you're
here,
if
you
need
any
help.
A
B
Similarly,
like
a
bunch
of
these,
other
ones
are
like
so
this
is
a
binder
hub
is
again
like
a
pretty
famous
community
project
for
hosting
jupyter
notebooks.
So
this
is
the
tool
that
creates
those
images
that
they
use,
so
they
use
this
way
hacky
wave,
they
have
a
dock
with
templated
dockerfile.
That
creates
the
image
for
them,
like.
I
think
bunch
of
these
different
integrations
may
be
nice
to
sort
of
expand
your
community
and
also
for
us
to
figure
out
like
what's
missing,
that's
preventing
adoption.
A
Let
us
know
blah
blah
blah
right
and
then
maybe
start
a
dialogue
to
me
that,
like
that,
that
sounds
like
the
trait
of
like
outreach
right
in
in
a
way
which
I'm
not
sure
falls
under
any
particular
sub
team
right
like
is
it
a
learning
thing
I
feel
like?
We
might
be
a
little
bit
out
of
our
realm
to
some
extent,
if,
let's
say
it's
something
like
life
cycle
specific,
I
for
sure
wouldn't
touch
it
right
potentially,
but
yeah,
I'm
not
sure.
So
that's
a
very
interesting
conversation.
A
I
wonder
if
it's
worth
bringing
up
in
either
the
working
group
or
the
leadership
meeting
about
maybe
having
either
the
core
team.
Do
it,
or
you
know,
I
don't
know,
finding
a
solution
for
the
right
approach.
B
A
Did
you
see,
I
think
gitlab
has
one?
I
don't
know
if
it's
tied
to
devops
or
sorry
is
it
called
auto
ops,
auto
devops,
something
like
that
they're
they
have
a
current
integration
with
build
packs,
but
I
know
that
they
have
an
issue
open
where
they
want
to
be
able
to
contribute
like
the
test,
api
right
or
like
they're,
very
interested
in
the
test
api,
and
so
they
have
an
issue
to
track
that.
So
I
think
very
similar
there
it'd
be
interesting,
like,
as
we
start
working
through
a
test
api
to
get
their.
A
B
A
B
B
The
other
thing
we
talked
about
last
time
was
like
this
cncf
contributors
page.
I
think
natalie
was
supposed
to
create
a
service
desk
ticket
because
you're
still
listed
as
a
sandbox
project.
B
I
think
someone
was
supposed
to
do
like
go
and
edit
it,
but
I
don't
know
if
we
should.
I
think
that,
like
what
can
I
do
for
mozilla
may
be
applicable
to
what
can
I
do
for
cncf,
like
cncf,
is
broad
enough
to
warrant
something
like
this
yeah,
so
I
think
they
have
like
similar
attributes
here,
but
I
think
they
could
do
better
with
how
this
information
is
organized.
A
I
know
this
is
something
very
different,
but
another
approach
when,
when
we're
asked
about
like
how
to
get
more
docs
contributors,
one
of
the
things
I'm
really
interested
to
try
is
similar
to
google
summer
of
code.
There's
the
google
season
of
docs
right
yeah.
B
I
think
we
also
talked
about
that
last
time.
A
B
I
think
I
was
sort
of
involved
in
this
back
in
2019
with
a
separate
open
source
organization,
but
I
think
we
can
definitely
put
a
proposal
up
at
the
verity,
so
I
don't
know
if
cncf
participates
and
then
or
whether
we'll
be
participating
in
it
individually.
A
Oh,
that's
interesting.
Let's
see.
A
A
There
you
go
so
if
you
there's
the
cntf
mentoring,
github
page
and
on
there
there's
a
a
couple
more
programs
that
they
participate
in
so
season
of
docs
is
one
interesting.
B
I
think
that's
it.
Should
I
assign
this
to
you.
B
A
Good
perfect
love
it.
I
guess
I'll
assign
it
to.
A
It's
for
my
yeah
that
I
wasn't
saying
my
email
address
is
slightly
backwards.
It's
our.
B
A
All
right
cool,
so
that
makes
sense.