►
From YouTube: Ceph Docubetter Meeting 2020-09-05
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).
A
So
it's
just
you
and
me
it
looks
like
so.
I
will
run
through
this
as
quickly
as
I
can
so.
The
first
thing
that
I've
done
the
thing
that
is
occupied
most
of
my
time
this
week
is
ingesting
hacking.rst
into
the
developer
guide.
A
A
For
some
reason,
which
sebastian
and
I
spent
like
four
days
chasing
down,
I'm
getting
a
weird
some
there's
been
some
commit
that
has
happened
that
prevents
the
docs
from
building.
So
in
order
to
get
it
cleanly
to
build,
I
check
out
this
particular.
A
I
check
out
a
a
particular
commit
which
allows
me
to
build
cleanly
and
then
I
push
and
it's
fine
and
like
it's
really
it's
really
weird
and
sebastian,
and
I
spent
like
three
hours
earlier
tonight-
figuring
it
out.
I
mean,
like
he's
not
sitting
there
at
all
three
hours.
A
That
they're,
definitely
failing
for
me
from
master
like
anything
that
is
branched
directly
off
of
master,
is
failing
for
me
unless
I
pull
4ea
54664,
which,
if
you
like,
when
we
meet
on
on
my
friday
morning
or
thursday
evening,
I
can
I
I'll,
have
a
lot
more
information
about
it
and
we
can
go
through
it
in
greater
detail.
If
you
like,
like
the
we
can
still
get
doc
builds
done.
It's
fine.
A
A
B
A
Right,
yeah
doesn't
have
anything
to
do
with
with
like
making
progress
and
stuff,
but
I
sort
of
enjoy
it
because
it
makes
my
get
understanding
better.
So
hacking.rst
is
in
it's
a
huge
addition
to
the
developer
guide
so
for
posterity.
A
This
was
the
week
that
the
dashboard
developer's
guide
got
ingested
into
the
developer
guide
and
lens
has
sent
back
just
in
the
last
couple
of
hours.
Lens
sent
me
a
couple
of
of
requests
to
tweak
the
pr,
and
so
that
should
be
in.
A
I
hope
to
do
that
before
I
go
to
bed
and
which
is
gonna
be
within
the
next
two
hours.
So
that's
the
first
thing
dashboard
developer's
guide
is
in
so
the
next
thing
is
kfu
has
added
some
some
prs,
where
we're
guided
to
use
prompts,
where
appropriate,
like
the
prompt
directive
in
rst-
and
this
is
another
thing-
that'll
have
to
be
discussed
like
in
a
in
another
meeting,
because
it's
like
immediately
to
the
tall
weeds
for
some
reason.
A
I
cannot
get
those
to
build
right
and
I
see
that
sebastian
has
at
least
one
pr
for
a
little
typo
that
includes
this.
It's
also
not
building.
So,
like
that's
developing
I've
just
seen
that
in
the
last
day-
and
we
will
deal
with
that
more-
you
know
in
a
less
formal
meeting,
okay.
So
that
brings
me
to
the
getting
started,
guide,
deployment
guide,
the
deployment
guide
and
the
getting
started
guide.
A
The
getting
started
guide
is
the
step-by-step
by
step-by-step
thing,
that
has
all
of
a
step-by-step
by
step-by-step
procedure
that
has
all
of
the
terminal
output
in
it
that
I
wrote
between
april
and
june,
and
I
was
just
ironclad
convinced
that
that
thing
was
necessary
and
that
the
the
the
deployment
guide
as
it
existed
at
the
time
did
not
give
you
fine-grained
enough
guidance.
A
Nonetheless,
I'm
still
going
to
push
forward
with
with
putting
the
getting
started
guide
up
just
four
noobs,
but
the
hacking.rst
dominated
my
time
this
week,
so
we're
still
like
maybe
I'll
get
lucky
and
it'll
get
done
this
weekend.
So
that's
where
we
are
with
that.
So.
B
Maybe
you
should
maybe
you
should
send
an
email
about
this
hacking,
I'm
just
looking
at
it
right
now
and
for
folks
who
are
interested
in
contributing
to
the
dashboard
might
be
a
useful
piece
of
information
might
be
worth
sending
an
email
about
it
once
on
the
list.
A
Do
what
dev
that
stuff
debit
sapphire.
B
A
Yeah
sure
it's
it's
a
great
piece
of
work.
It's
it's
really
really
very
good
looking.
So
then
there
are
these
three
things
that
are
all
together
that
I
will
always
discuss
together
until
we
have
until
we've
gotten
them
incorporated
into
the
documentation.
A
There's
the
landing
page
update
with
what
I
want.
I
want
the
three
buttons
on
there
for
the
tracker,
the
dev
guide
and
the
install
guide,
but
the
matter
is
now
confused
because
initially
I
was
thinking
like
I'll
go
with
the
step-by-step
install
guide.
Now,
I'm
thinking
just
the
deployment
guide
with,
like
maybe
a
link
in
the
deployment
guide
to
the
to
the
getting
started
guide,
but
that's
like
that's
developing
for
me
as
I
go
from
innocence
to
experience.
So
I'm
not
like
I'm.
A
A
A
But
sebastian
was
like
sebastian
didn't
like
the
size,
the
buttons
he
thought
they
were
too
big,
and
I
don't
know
if
I
agree
or
not,
but
I've.
I
I've
thought
about
it
for
so
long
that
I've
kind
of
come
around
his
his
side
on
it
like
it.
So
the
buttons
need
to
be
made
smaller,
that's
one
thing,
and
that
that
was
the
main
reason
for,
for
that
pr
stalling
was
that
sebastian
thought
that
it
looked
ridiculous.
A
A
No,
it's
it's
not
because
it's
not
just
the
one
thing
like
it's!
It's
that
plus
the
deployment
guide,
plus
the
getting
started
guide
all
together.
In
one
thing,
it's
too
many
things
in
one
place.
It
needs
to
be
broken
apart
into
more
than
one
pull
request,
and
that's
why
I
got
stalled
because,
like
like,
I
we're
trying
to
pass
too
much
stuff
at
once.
It's
it's
like
a.
A
It
was
the
wrong
approach.
It
seemed
like
the
right
approach
from
a
naive
perspective,
but
with
more
experience,
it
was
wrong.
I'll
I'll
get
you
the
the
pull
requests
have
after
this.
I
guess
so.
I
met
with
brad
hubbard
a
couple
of
weeks
ago.
I
don't
remember
if
you
and
I
have
met.
A
I
know
this
is
irrelevant
for
the
purposes
of
the
the
the
record
but
brad
hubbard,
and
I
met
a
couple
of
weeks
ago
and
had
a
long
long
talk,
but
about
a
using
get,
and
I
wanted
to
work
out
with
him
a
good,
durable
procedure
for
pulling
a
remote
branch
locally
and
then
altering
it
and
then
pushing
it
to
one's
origin
and
then
sending
a
message
to
the
person
who
had
the
the
original
remote
saying
I've
taken
the
change
from
your
branch
and
formatted
it
properly.
A
This
is
for
when
somebody
has
a
good
idea,
that's
badly
formatted
and
like
it,
it
breaks
the
build
or
something
or
maybe
it's
just
like
become
stalled,
because
somebody
made
a
suggestion
and
then
it
got
they
got
kicked
back
and
then
they
decided
like
this
is
too
much
work.
You
get
the
idea.
B
A
Right,
yeah,
and
so
I
have
in
the
in
the
other
minutes
for
this
meet
an
example
of
one
of
these
that
worked
sebastian
had
had
pushed
a
change
and
there
were
some
backticks
that
were
pushed
up
against
another
another
word
that
was
causing
the
docs
to
fail
to
build.
So
I
did
exactly
what
I
just
said.
I
pulled
his
remote
built,
it
pushed
it
back.
It
works
great,
that's
like
that
was
in
my
opinion.
A
I
know
it's
it's
sort
of
a
small
thing
from
like
the
perspective
of
a
software
developer,
but
I
was
very
gratified
to
get
this
done
because
that
means
like
if
we
have
a
docs
person
like
me,
who
knows
how
to
do
that?
Then
that
means
that
people
can
just
make
badly
formed,
but
good
badly
formed
suggestions
are
good
ideas
and
they
can
still
get
carried
across
the
goal
line.
So
I
was
very
pleased
with
that.
A
A
A
I
have
an
instructional
film,
mock-up
available
of
in
this
case
it's
just
how
to
install
a
little
typo,
pouncer
called
sl,
but
I
have
ceph
branding
at
the
beginning
and
end
of
it
and
when
we
have
when
we
have
our
I
get.
I
this
makes
me
think
now,
I'm
sort
of
speculating
out
loud
rather
than
giving
a
report.
A
This
makes
me
think.
Maybe
we
really
should
have
the
getting
started
guide
step
by
step
and
then
have
a
video
of
it
for
people
who,
like
want
to
see
it
installed
like
want
to
see
like
they?
Maybe
they
don't
know
how
to
do
it,
or
maybe
it's
sort
of
a
pre-sales
thing,
and
so
that
actually
makes
me
think
yeah
the
getting
started
guide
should
go
on
the
page
it
should
should.
A
It
should
be
included
in
the
docs,
but
anyway
that's
that's,
for
we
can
brainstorm
about
that
some
other
time,
and
that
is
there's
a
number
of
little
typos
and
I've
raised
a
bunch
of
little
bugs
from
the
the
report.
A
bug
page
and
those
continue
there's
nothing.
In
particular,
that's
like
nothing
stands
out
there,
just
like
various
incremental
improvements,
the
docs
and
that's
it.
It's
it's
15
minutes,
16
minutes
not
not
terrible.
Do
you
have
anything.
B
For
dashboard
contributors,
or
even
people
who
want
to
learn
how
to
contribute
to
dashboards,
so
that
is
good.
We
can
talk
about
the
video
idea
that
you
have
a
little
bit.
I
mean
I'm,
I'm
of
the
opinion
that
videos
are
useful,
but
you
need
to.
A
B
Really
really
make
them
to
the
point
you
you
cannot
be
like
you
know,
making
a
video
of
30
minutes
nobody's
going
to
look
at
it
so
but
yeah
that
that
we
can
discuss
offline
but
yeah.
A
A
I
am,
I
am
right
there
with
you,
I
I
I
worked
on
the
branding
at
the
beginning.
In
the
end,
the
branding
is
the
word
ceph
and
a
chime
that
plays
cef
and
that
lasts
one
and
a
half
seconds,
and
then
there
is
the
video
which
is
45
seconds
and
there
is
a
one
second
black
screen
with
the
word
ceph
on
it
and
that's
it.
I
have.
I
hold
no
brief
for
for
long
introductions
or
theme,
songs
or
anything
like
that.
I
am.
I
am
100
with
you.
B
A
A
Okay,
great
thanks
for
coming
to
my
meeting
neha
you're,
my
best
friend.
A
Oh
yes,
I'll
see
you
two
days
from
now
or
two
days
whatever
tomorrow.