►
From YouTube: Learning Sync: 2021-01-05
Description
Meeting notes: https://bit.ly/38pal2Z
A
B
As
we
get
somewhat
of
a
status
update,
which
is
that
pack
is,
you
know
considering
our
planning
on
a
release
soon,
which
will
bring
with
it
a
number
of
a
number
of
changes
in
terms
of
the
ux
for
how
people
interact
with
commands,
we
should
probably
coordinate
at
least
a
blog
post,
if
not
also
some
more
explicit
documentation
like
we'll.
Have
that
we'll
have
the
command
documentation
automatically
generated.
We
should
try
to
make
sure
that
we
have
something
that
goes
along
with
it
to
be,
like
oh
yeah,.
A
B
Was
thinking
well,
if
we're
able
to
get
the
the
cached
image
thing
through
then
we
should
definitely
have
something
specifically
about
that.
I
think
it's
also
important
especially
we're
talking
about
like
we
there's
this
big
push
for
the
sub
commands.
We
should
have
some
clarification
on
why
we
did
that
and
how
we
envision
people
using
it
in
the
future,
and
you
know
a
request
for
comment.
If
you
know,
if
they're
like
oh
yeah,
we
hate
this
terrible,
then
let
us
know.
A
Okay,
do
you
I,
I
basically
added
dan
to
cache
images
since
he's
the
one
that's
implementing
that
feature
probably
has
the
better.
You
know
understanding
of
how
to
portray
that.
Does
that
sound,
accurate
yeah.
A
A
Cool
is
there
any?
I
know
we
briefly
touched
on
basically
specifically
for
pac
having
release
branches
for
changes
to
the
overall
docs
for
things
that
aren't
like
tutorials
and
guides
and
stuff.
Is
that
something
that
you're
that's
happening
essentially.
B
B
Yeah
someone
someone
did
that
because
we
have
all
these
deprecated
commands
right.
That
probably
should
also
that
that
can
be
done.
It
doesn't
necessarily
have
to
be
done
because
none
of
the
commands
are
breaking
at
this
point,
but
at
the
same
point
same
time
we
should
make
sure
that
the
commands
you
know
it's
better
to
have
the
official
commands
there.
A
Cool
and
then
cache
image,
yeah
there's
definitely
is
there.
No,
unless
we
create
a
guide
for
cache
image
right,
which
that
would
be
optional,
and
I
think
we
would
leave
that
up
to
the
platform
team
to
determine
that
sorry,
I'm
kind
of
like
in
my
head
right
now.
What
I
was
trying
to
say
is:
we
should
probably
have
a
guide
for
cash
image
right,
but.
B
A
Cool-
and
this
has
the
proper
milestone-
do
we
have
that.
C
A
And
sorry,
what
was
this?
This
is
documentation
for
the
supported
apis
yeah
and
is
it
the
migration
guides
as
well
or
yeah,.
C
A
A
Yeah,
I
don't
know
if
I
talked
about
this
last
time-
maybe
I
was
absent
during
this,
but
on
our
side,
the
learning
side
of
things,
the
website,
we
migrated
the
calendar
to
be
managed
via
team
up
and
right
now.
I
believe
it's
myself
and
joe
that
have
access
to
modify
that
calendar.
A
So
the
hope
there
is
that,
instead
of
individuals,
owning
invites
is
people
could
just
subscribe
to
this
calendar
via
whatever
their
calendar.
App
is
the
only
thing
that
I
found
is
that,
even
though
calendars
have
been,
you
know
around
for
a
really
long
time.
A
The
way
to
add
them
to
your
application,
especially
on
microsoft,
is
like
really
difficult.
So
there's
that,
but
nonetheless
I
think
this
would
be
beneficial
and
you
know
we
have
it
on
our
website
now.
So
that's
something
better
than
what
we
had
before,
which
was
nothing.
C
I
think
there's
an
rfc
number
126
that
has
been
up,
I
think,
before
the
break,
and
there
are
some
comments
there.
So
we
should
endeavor
to
go
review
that
and
leave
feedback.
A
So
I
have
a
query
here
for
things
that
don't
have
a
team
associated
to
it
and
including
the
the
learning
team
at
some
point,
and
we
could
review
some
of
the
things
that
are
there,
but
I
was
wondering
if
we
could
either
assign
or
just
either
make
it
the
request.
I
guess
I
should
say
for
people
to
come
in
here
and
label
stuff
or
if
we
want
to
do
it
here,
interactively
if
there's
anything
that
we
feel
like
might
not
be
as.
A
Sorry
so
we
decided
that
we
were
gonna,
have
a
team
label
associated
with
each
issue
so
that
way
that
each
team
knows
kind
of
what
more
or
less
we're
kind
of
holding
them
responsible
for
right.
It's
so
that
we
know
who's
going
to
pick
it
up,
or
at
least
from
what
team
people
should
be
picking
up
from
for
documentation
purposes.
A
So
maybe
they
ask
here
would
be
for
somebody
from
each
team
go
in
here
and
label
the
stuff
for
their
particular
team.
A
So
I
could
take
the
learning
one
and
maybe
david
you
could
take
the
platform
stuff
natalie
the
implementation
side.
A
A
B
That
works.
That's
nice
probably
only
works
for
people
in
our
in
our
g
suite.
Oh
that
sucks,
although
we
may
be
able
to
create
create
for
people,
because
I
could
see
my
personal
one
as
well.