►
From YouTube: CNB Sub-Team Sync: Learning: 2021-12-10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
C
All
right
without
further
ado,
let's
go
ahead
and
get
started.
I
went
ahead.
The
stream
should
be
going
now,
yes,
okay
and
then
next
we
have
status
updates.
From
my
side,
I
don't
feel
like
I've
been
doing
a
lot
on
the
learning
team
side
of
things.
C
I
do
have
an
update
for
the
lfx
mentorship,
but
I'll.
I
added
that
to
the
agenda
any
other
status
updates.
B
A
C
See
yeah
I
mean
I
did
add
that
to
the
agenda
or
catacota
in
general
to
maybe
get
a
high
level
understanding
of
how
it
now
works.
Now
that
I
think
we
have
that
sort
of
what
is
it
migration
or
sinking
strategy
going
but
yeah,
maybe
we
could
get
a
little
bit
of
a
overview
of
that.
If
you
don't
mind
later
today,.
A
B
C
All
right
moving
over
to
stealth
prs.
This
is
an
interesting
one,
sam,
because
I
feel
like
we're
at
the
end
of
the
year
and
this
pr
didn't
actually
get
merged
and
which
one
is
it.
A
You're
not
sharing
your
screen.
Sorry
I'll
share
my
screen
real.
C
C
So
for
some
context
right
we
had
a
quarterly
review
on
the
leadership
side
of
things,
on
aligning
our
roadmap
to
more
or
less
the
things
that
are
we're
actually
working
on
and
kind
of
you
know
some
priorities
might
have
shifted
throughout
the
year
and
we
did
that
you
know
successfully
to
some
extent,
but
I
think
the
part
where
it
fell
apart
was,
I
was
to
take
and
essentially
update
our
roadmap
document
in
our
community
repo
to
reflect
some
of
those
decisions.
C
C
This
is
what
this
means
right
like
there
wasn't
a
lot
of
depth
to
a
lot
of
the
decisions
that
were
made,
and
so
that's,
where
I
kind
of
deferred
to
other
individuals
like
steven,
I
think
terence,
was
on
here
and
it
just
never
went
anywhere
right
like
enough
pinging
happened
that
that
I
felt
like
I
was
annoying
people
too
much
for
something
that
might
not
have
as
much
focus
so
I'm
not
sure
how
to
fix
it
in
the
future.
C
But
I
don't
know
if
this
is,
you
know
applicable
at
this
point
in
time.
B
So,
what's
the
impact,
if
we
just
close
this
pr.
C
At
you
know,
like
I
said,
because
it's
so
late,
I
guess
to
go
out
there
really
wouldn't
be
an
impact
per
se.
I
think
what
I'm
maybe
more
conscious
of
is
how
to
make
this
process
better
for
the
next
quarterly
review
right.
So
yeah,
that's
I
I
think
that's
where
I'm
at
right
now,
and
I
think
that
this
is
gonna,
be
gonna,
be
one
of
those
things
I
bring
up
during
those
quarterly
reviews
about
actually
following
through
with
updating
the
roadmap
and
not
just
having
discussions
about
it.
C
B
B
C
C
C
C
All
right,
okay,
next
topic,
holidays.
C
A
I
think
I'll,
I'm
I'm
off
from
work,
might
still
be
around
for
open
source
stuff,
I
don't
know,
depends.
C
C
So
if
we
look
at
this
calendar,
we're
saying
you
said,
14
15.
C
Oh
20th,
okay,
so
the
20th
yeah.
I
think
a
lot
of
people
are
going
to
be
on
that
same
boat,
so
that
would
mean
that
at
least
this
meeting
would
be
impacted
and
probably
cancelled.
So
I
think
we
might
want
to
do
that.
C
And
I
guess
we'll
let
other
people
deal
with
working
group
and
whatnot,
but
just
I
guess
for
everybody
here
vmware
will
be
out.
I
think
the
all
of
the
27th,
but
obviously
I
wouldn't
be
surprised
as
well
on
the
20th.
B
C
All
right,
the
next
topic
I
added
to
the
agenda
it
has
to
do
with
the
lfx
mentorship.
If
you
weren't
aware
we
did
have
a
mentee,
her
name
was
harshita
and
she
was
helping
us
with
giving
a
facelift
or
making
some
improvements
to
our
feature
screen,
and
so
that's
this
screen
right
here.
C
C
As
far
as
that
went,
we
do
have
a
branch
where
she
was
able
to
make
a
sizable
amount
of
changes
to
it
and
I
think
we'll
be
able
to
take
that
and
push
it
out
right
now.
Some
of
the
changes
that
are
missing
have
to
do
with
a
section
that
she
wanted
to
add
regarding
blog
posts.
C
Or
articles,
let
me
see
if
I
can
pick
that
up
yeah,
so
there's
a
blog
section
underneath
it
and
basically
that
becomes
the
1v1
kind
of
like
in-depth
article
or
blog
post
and
we
could
obviously
add
additional
articles
and
blog
posts
from
the
community
from
other.
C
You
know,
individuals
or
organizations,
and
this
part
right
here
is
blocked
because
we're
waiting
on
joe
to
approve
and
publish
some
of
the
blog
posts
that
she's
created
so
she's
still
working
on
that,
but
as
far
as
the
official
mentorship
that
has
concluded
and
so
we'll
kind
of
have
to
take
it
from
there.
C
All
right
awesome,
moving
on,
let's
see
catacota.
C
A
So
I
can
talk
a
bit
about
how
I
model
this
to
be
happening,
so
there
are
ways
to
embed
carthage
in
the
website,
so
it
will,
it
will
sort
of
show
up,
as
they
will
just
embed
the
whole
thing
as
an
iframe.
A
A
A
They
have
a
really
complicated,
build
system
to
get
this
all
working.
So
I
I
don't
know
how
that
works.
Our
solution,
meanwhile,
is
that
I,
the
main
problem
with
the
kafka
talks
right
now,
is
that
it
was
separate
repository
which
was
essentially
a
clone
of
our
dogs,
with
some
minor
changes
to
make
it
work
on
cathode
and
each
time
someone
changed
the
dogs,
they
would
have
to
go
and
change
caterpillar,
otherwise
they
would
diverge.
A
So
what
I
wanted
to
do
was
to
just
auto,
generate
the
carthage
stuff
and
keep
it
in
the
docs
repository
so
that,
like
there's
a
single
source
of
trucks,
everything
else
is
auto
generated
and
you
can
all
still
test
it
using
google.
A
So
that's
the
other
thing
with
carthage
like
testing.
There
is
a
way
to
test
out
the
code
up.
It
involves
using
selenium
in
javascript
and
they
have
their
own,
like
library,
for
doing
something
very
similar
to
what
google
does
like
setting
up
the
base
environment,
but
it
all
runs
on
catholic
stuff.
A
So
that
was
the
other
alternative.
What
I
ended
up
basically
doing
was
writing
a
really
small
go:
go
application
that
parses
some
input
files
and
it
uses
html
comment
comment
tags
as
delimiters
instead
of
the
normal
curly
braces.
A
So
when
hugo
passes
it,
it
just
sees
those
as
html
common
tags
ignores
them
entirely
when
our
parser
parses
it
we
use
them
as
as
as
delimiters
for
templating
like
the
normal
go
templating
language,
those
normal
rules
apply
it's
just
that,
instead
of
curly
braces,
you
have
those.
C
Okay,
could
you
could
you
either
share
a
screen
to
a
sample
of
of
what
that
syntax
looks
like
or
the
usage
of
that
or
yep?
Let
me.
A
So
here
here
here,
I
have
I'll
try
to
explain
the
structure
I'll
try
to
also
create
a
pull
request
explaining
how
this
works
in
the
readme
here,
but
the
the
crux
of
it
is
this:
main.go
file
doesn't
have
any
dependencies
apart
from
the
standard
library.
What
it
does
is
the
following:
first
strips
out
the
front.
A
Replaces
that
with
nothing,
then
normalizes
any
links
that
we
have
so
like?
We
use
relative
links
in
in
our
documentation,
just
normalizes
that
to
use
buildbacks
io
and
then
just
uses
template
the
like
the
templating
language,
with
the
html
common
tag,
delimiters
with
the
plus
sign
added,
so
that
we
can
differentiate
normal
common
tags
from
the
templating
tags.
So
this
is
a
normal
html
comment:
delimiter,
it's
just
a
plus
added,
so
that
you
can
differentiate.
A
So
that's
how
we
define
the
template.
We
just
go
through
the
list
of
files
and
render
them
out
the
list
of
files
are
mapped
here.
This
is
the
input
file.
This
is
the
output
file,
so
that
we
can
we
we
don't
render
out
the
whole
directory
just
render
out
what
we
want
to
where
we
want
it
and
then
the
rest
of
the
carter
documentation.
A
We
we
do
keep
generated
files
here,
but
there's
also
a
ci
checker,
which
makes
sure
that
you've
kept
these
files
up
to
date.
So
if
you
make
any
changes
you
can
just
run
like
it
shows,
you
run,
make
generate
katakuri
and
it
will
automatically
generate
a
bunch
of
things,
but
it
also
runs
a
simple
git
diff
to
check
if
these
things
have
diverged
in
ci.
A
So
the
way
it
works
is
there
are
some
audio
generated
files
here,
some
manual
files
that
are
needed
as
part
of
carter
project,
also
like
things
like
index,
json,
etc,
are
like
hand
written
things
like
step.
One
dot
md
is
generated
because
it's
defined
here
in
files
text,
okay,.
C
And
then
we
have
to
check
in
the
generated
files,
because
that's
how
code
category
works
right.
A
A
So
there's
a
there's,
an
index.json
that
defines
the
scenario
and
then
there's
a
like
setup
scripts
for
the
for
like
what
to
do
so
like
this
thing
sets
up
back
and
this
this
thing
just
waits
and
for
the
background
script
to
execute
a
bunch
of
other
things
like
that,
so
I've
migrated
over
to
two
guys:
the
app
developer
and
our
journey
gates.
We
still
have
to
migrate
people
back
autograde
and
in
terms
of
what
the
actual
like
content
looks
like.
Let
me
show
you
so
going
back
here.
A
Let's
look
at
some
of
the
files
we
parsed.
So
let's
first
take
a
look
at
this
one
content,
docs
app
journey,
dot,
md,
so
content,
docs,
app
journey,
dot,
md
and
if
I
view
it
in
raw
format.
A
So
the
good
thing
about
this
is
that
karthik
order
had
a
syntax
that
would
break
markdown
parsing
because
we're
using
like
the
the
html
tags,
markdown
parsing,
still
works
as
normal
and
those
things
only
get
rendered
out
at
the
end.
So
you
see
these
tags
here
if
false
and
end
so
that's
like
normal,
a
normal
go
template
block
so
when
in
carthage
world
we
just
want
to
like
not
show
any
of
this
like.
We
don't
want
to
show
a
button
to
cut
the
code
itself
when
we're
on
katakura.
A
We
don't
want
to
show
the
download
buttons
to
back
because
it's
already
on
there
and
we
don't
want
to
show
the
button
for
installing
docker,
because
that
again
is
already
on
there.
A
So,
like
you,
can
do
a
simple
if
false
and
end
to
remove
pieces
you
want,
and
then,
if
you
want
to
add
pieces
like
here,
you
can
just
use.
Go
like
template,
like
the.
B
A
Template
strings
to
render
things
out,
so
you
can
do
a
multi-line
string
like
this
you
again,
this
is
all
normal
go
syntax.
So
this
is
a
delimiter
here,
we've
started
the
the
string
is
what
we
want
to
print
out
in
string
and
delimiter,
and
that's
it.
A
Similarly
for,
like
the
execute
stuff
gold,
templating
language.
Has
this
thing
where,
if
you
put
a
minus
in
front
of
it,
it
strips
all
the
white
space
out
right.
So
the
reason
I
couldn't
put
an
html
tag
at
the
end
of
these
three
things
here
is
that
markdown
can't
parse
it
anymore
like
it.
It
requires
this
thing
to
be
separate
from
this
one,
so
I
this
was
just
a
hack
that,
when
we
executed
in
cartagona
format,
this
goes
all
the
way
here,
but
normally
it
just
stays
like
this.
A
So
if
you
go
to
folder,
slash,
buildbacks
up
journey
start.
A
C
A
A
A
B
C
Okay,
that
makes
sense,
that's
pretty
cool.
Actually
I
really
like
it
the
the
thing
about
the
plus
that
that's
a
little
bit,
maybe
confusing
off-putting.
I
was
going
to
initially
propose
whether
the
delimiter
could
be
still
the
html.
You
know,
but
instead
of
a
plus
use
like
the
open,
curlies
and
closed
curlys
like
double
open,
just
like
templating,
but
then
I
wonder
what
that
would
look
like
when
you
also
have
internal.
A
A
Yeah
that
that's
why
I
just
went
with
something
that
could
not
clash
yeah
interesting,
but
I
I'm
not
tied
to
that.
It's
it's
fairly,
easy
to
replace
that
those
delimiters
are
just
defined
in
in
that
small
main
script
that
I
have
here.
Oh
you
can
you
can
change
this
and.
C
Yeah
yeah,
okay,
cool;
no,
that
makes
sense
it's
pretty
straightforward,
but
at
the
same
time
I
think
it
does
require
a
little
bit
of
gymnastics,
especially
like
that
execute
one
you
mentioned,
where
you're
using
the
the
trim
function.
Essentially,
to
put
it
next
to
it.
That's
interesting.
A
C
Yeah,
I
was
thinking
like,
maybe
as
an
alternative
if
there
was
a
different
special
syntax
for
kind
of
code,
a
specific
character
or
commands
right
or
syntax
whatever
you
want
to
call
it.
So
if
you
could
hypothetically
right
separate
the
ones
that
are
go
templating
and
then
the
ones
that
are
very
specific
to
catacota
syntax,
and
maybe
that
could
be
a
little
bit
more
legible.
But
that's
a
me
spitballing.
I
don't
have
anything
concrete.
A
B
I
think
you're
right
though
it
would
have
been
nice
if
they
stole
some
ideas
from
pandora
and
made
the
descriptive
block
at
the
top
of
the
the
triple
dash
more
expressive.
C
Yeah
yeah,
because
I
have
seen
that
I
don't
know
if
pandoc
is
what
I
had
in
mind.
But
essentially
when
you
specify
the
syntax
right,
you
could
add
additional
metadata
and
that
would
have
been
a
much
better
place.
Yeah.
C
B
A
B
C
Okay,
if
we're
done
with
that
topic,
I
think
we've
reached
the
end
of
the
agenda.
Anything
else
last
parting
words.