►
From YouTube: Ceph DocuBetter Meeting 2020-08-12
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
Yeah
I've
I've
put
seven
or
eight
things
on
there,
so
I'll
I'll
go
through
it
really
fast.
B
Right
so
I.
B
B
That's
what
I
learned
from
doing
that.
So
that's
the
the
first
thing.
I
don't
remember
if
I
put
that
in
no
okay,
so
yeah
this
is
gonna
be
shorter,
okay,
so
the
first
thing
is
sebastian
is
on
leave
right
now
from
susa
and
we're
in
the
middle
of
a
discussion
about
the
getting
started
guide.
B
If
he's
still
on
leave
like
next
week,
I
he
had
to
leave.
Suddenly
we
don't
know
when
he'll
be
back.
If
he's
not
done
next
week,
then
I'm
gonna
go
ahead
and
get
you
and
josh
to
sort
of
like
just
approve
it,
and
then,
if
he
has
quibbles,
we
can
address
those
after
he
comes
back,
and
maybe
this
will
also
give
me
time
to
do
the
dashboard
component
of
the
getting
started
guide
because
right
now
we're
up
to
dashboard.
But
we,
I
haven't,
taken
the
screenshots
for
dashboard
stuff.
Yet
so.
A
B
Where
that
that's,
where
that
sits
right
now,
the
docsept.com
site,
reorg
sebastian
are
having
a
discussion
about
how
big
the
button
should
be.
Josh
has
also
weighed
in
with
good
suggestions
about
putting
some
padding
in
there,
so
the
buttons
aren't
right
up
against
each
other.
That's
about
it
yeah.
I
looked
at.
A
It
I
looked
at
it
briefly.
I
have
a
quick
question,
so
I
think
you
have
it
says:
octopus,
installation
guide
or
something
right.
Your.
B
A
It
needs
to
say
installation
yeah,
I
was
just
we
should
make
it
like
version
specific.
B
Yes,
I
I
think
sebastian
also
brought
up
if
not
exactly
that
point
something
like
that,
like
hey
octopus,
is
a
version.
This
needs
to
say
ceph
except
adm,
and
he
also
had
this
question
about
you
know.
Stefadium
is
not
the
only
method
of
installation
which
I
know,
but
the
whole
point
is
to
give
people
this
one
simple,
unified
tool
to
do
it
and
in
order
to
in
order
to
respond
to
him,
I
get
sort
of
my
entire
job
has
been
trying
to
trying
to
simplify
it.
B
So
there's
this
one
simple
path,
and
then
we
explain
you
can
do
it
through
rook
or,
however
else
you
want
to
do
it
and
he
he
asked
this
one
question,
which
is
a
simple
question
to
ask
and
a
hard
question
to
answer
which
is
like
do
we
want
to
have
like
four
versions
of
this
and
the
answer
is
like?
No,
no,
we
don't,
but
it
needs
to
be
more
thoughtful
than
just
that.
So
that's
like
so
I've.
I've
got
to
think
about
that
and
respond
to
him.
A
Sure,
yes,
but
I
mean
in
general
what
we
would
like
to
do.
Ideally,
is
we
want
to
back
like
backboard,
your
pr
to
octopus
so
that
it
shows
up
against
the
octopus
version
of
the
docks
as
well
right.
B
A
Should
just
probably
check
with
I
I,
as
far
as
I
know,
I
think
everything
that's
in
master
mostly
gets
backboarded
to
octopus
at
the
moment,
so
you
shouldn't
have
to
like
change
anything
it'll,
just
be
cherry.
Picking
the
same
commits
to
octopus.
That's
that's
all
I
think,
but
yeah
I
mean
my.
My
only
concern
was
that,
like
let
us
say
when
pacific
comes
out,
it
shouldn't
say:
octopus
installation
guys
or
it
shouldn't
yeah.
B
Of
course-
and
I
have
questions
about
that-
the
way
that
I
naively
think
of
dealing
with
it
is
sort
of
an
sbn
and
not
get
based
way
of
dealing
with
it,
which
is
like
I'll
just
write.
The
entire
guide
all
over
again,
which
is
probably
not
the
way
that
you
guys.
A
B
Like
conditional
docs,
yeah
yeah
that
would
that'll
be
neat
to
learn,
we
were,
we
were
always
warned
off
of
conditional
docs,
but
I'm
for
it
I'll
ask
you
on
our
our
friday
meeting
I'll.
Ask
you
more
specific
questions
about
it.
A
B
Okay,
so
last
week
I
went
back
and
forth
with
kefu
on
merge,
commit
format,
and
that
resulted
in
the
addition
of
a
proper
merge,
commit
format
section
being
added
to
the
developer
guide,
which,
if
it
was
copied
and
printed
out,
would
probably
be
about
two
pages,
and
there
is
still
some
discussion
between
just
collin
and
kevu
as
to
whether
they
want
to
use
the
the
web
exposed
api
to
find
email
strings
for
people
they're
having
a
discussion
still
right
now,
if
that's
still
going
on
next
week,
then
I
will
probably
ask
you
a
josh
to
back
me
up
and
I'll.
B
A
Yeah
I
haven't
looked
at
this
vr
closely,
but
yeah
I
can.
If
you
want
me
to.
B
Yeah,
it's
it.
There's
no
point
yet
because
they're
having
their
discussion
and
they've
also
they've
asked
rick.
I
think
who
is
a
guy?
Who
is?
Oh?
No,
I'm
sorry,
that's
a
different
discussion,
I'm
confusing
two
things
but
yeah,
but
like
don't
don't
waste
your
time
yet,
okay,
so
the
next
thing
the
release
notes
didn't
go
out
and
luca
servini
contacted
me
earlier
today.
I
made
a
pull
request
with
the
with
the
release
notes,
but
then
it
turns
out.
B
Abhishek
already
knew
about
that
and
had
done
it
so
once
I'm
once
I
have
demonstrated
that
I
can
do
this
get
thing
correctly.
B
I
think
I
want
to
learn
how
you
guys
have
the
eye
of
sauron
to
see
whenever
any
sort
of
move
is
made,
because
that
way
I
could
have
saved
myself
a
couple
of
hours
this
afternoon.
Doing
that.
A
Yeah,
I
think
that's.
I
think
these
are
a
couple
of
things
that
go
with
every
point
release
we
do
things
like
release,
notes
and
announcements.
The
other
thing
is
that
we
also
have
a
releases
table.
I'm
sure
you
must
have
noticed
it
which
has
information
about
what
is
the
latest
release
or
every
release
gets
added
into
that
table,
and
that's
also.
A
B
Yeah
one
of
the
another
thing
we'll
talk
about
on
friday
in
the
like.
I
I'm
trying
to
use
this
meeting
as
more
like
an
executive
level
summary
and
then
like
on
friday.
I'll
ask
you
specifically
because
this
thing
happened
today.
I
would
like
to
make
like
a
doc's
checklist
for
every
z
stream,
or
I
don't
know
if
it's
called
zed
stream
in
this.
B
Mean
every
point
release
whatever
it's
called
I'd
like
for
there
to
be
a
checklist
and
I'd
also
like
I
am
in
favor
of
of
merging,
getting
as
many
merge
commits
and
as
possible,
I'm
in
I'm
in
favor
of
of
getting
as
much
in
in
the
documentation
anyway,
because
it's
not
the
code
base,
it's
not
going
to
break
anything,
it's
just
going
to
be
wrong
and,
and
it
can
always
be
fixed.
I
would
like
to
have
a
because
the
docs
can
always
be
fixed
if
we
can
just
get
the
workflow
fast.
A
A
There
was
something
that
existed,
you
should
check
with
abhishek
abhishek
usually
deals
with
the
stuff
and
he
might
already
have
something,
but
it's
not
in
a
place
that
everybody
can
go
look
at,
so
it
might
just
be
a
matter
of
adding
it
to
the
dog
somewhere
or
maybe,
or
also
to
for
you
to
be
aware
of.
B
You
should
think
about,
I
will,
let's
see,
then
I
had
a
very
good
meeting
with
brad
hubbard
the
other
day.
I
was
talking
to
him
about
this.
This
idea
that
I
have
for
a
workflow,
which
I
don't
remember.
If
I
I
don't
know
if
you
were
in
the
orchestrators
meeting
the
other
day
when
I
asked
this,
but
I
will
ask
it
again
for
the
for
the
record
here:
sometimes
there
are
stale
commits,
or
there
are
like
badly
formed,
commits
by
people.
B
They've
tried
to
make
an
alteration
to
the
docs
and
it
doesn't
look
right,
but
the
the
core
idea
is
good,
so
this
is
like
I
want
to.
I
want
to
throw
out
the
bath
water
and
keep
the
baby
and
the
workflow
that
I
want
to
use
is.
I
want
to
add
the
like,
when
somebody
has
a
a
baby
and
bad
bathwater
type.
Merge
I'm
sorry
a
pull
request.
B
I
want
to
add
them
to
my
origin,
repo,
as
an
ups
or
as
a
remote,
and
then
check
out
that
branch
locally,
make
the
alteration
credit
them
as
the
primary
author
and
myself
as
a
co-author
and
then
push
it
and
then
have
it
reviewed,
and
this
is
like
we'll
have
to
work
this
out
where,
like
I
contact,
whoever
like
you
or
josh
or
somebody
who
is,
is
qualified
to
vet
the
technical
side
of
it.
And
then
we
just
get
these
things
like
that.
This
works
for
two
cases.
B
One
failed
things
like
I've
got
to
commit
from
back
in
february.
That
clearly
needs
to
be
rebased
and,
like
I'm,
not
sure
if
it's
even
still
like
it's
just
a
thing
that
I
wasn't
completely
sure
what
I
was
doing
at
the
time,
but
like
the
idea
is
good,
but
the
form
is
bad
so
for
old
stuff
like
that,
and
then
also
for
people
who
tried
to
make
a
good
a
good
commit.
But
then
like
did
not
reach
kefu's,
incredibly
exact
standards.
B
I
want
to
be
able
to
just
consume
that
stuff
and
preserve
the
credit
for
the
original
people,
and
then
so.
That's
that's
that's
my
half
of
it
and
then
our
half
working
together
is
like
we
figure
out
who
I
get
this
stuff
too,
so
that
it
can
be
approved
within,
like
12
or
24
hours
of
the
of
the
pull
requests
going
through
so
like,
and
if
we
can
get
that.
B
I
don't
know
how
long
it'll
take
to
like
to
work
that
out
where
it's
like
a
thing
that
we
just
sort
of
expect
will
happen.
But
I
want
to
check
out.
I
want
to
check
out
remote
branches
to
my
to
my
own,
my
own
origin,
and
then
I
want
to
push
them
and
then.
A
B
I
yeah
and
then
just
close
the
other
and
then
like
have
the
authority
and
the
confidence
to
close
the
other
pull
request
that
has
been
made.
You
know
with
the
with
a
link
to
the
the
one
that
supersedes
it.
That
is
newer.
B
A
Mostly
the
workflow
that
we
follow
for
code
changes
a
lot
of
times.
This
happens
that
there's
a
there
is
somebody
who
contributes
a
piece
of
code
and
are
not
able
to
follow
up
on
the
requested
changes
or,
like
you
know,
maybe
they
get
busy
or
they
get
sidetracked
in
those
cases
we
do
the
same
thing.
We
we
just
like
make
sure
that
the
original
author
gets
the
credit
for
the
change
and
we
modify
the
the
the
commit
and
we
create
pr.
A
So
I'm
I'm
like
open
to
like
documenting
this
in
a
way
that
everybody
can
do
this,
the
the.
If
you
must
have
seen
we
have
a
stale
bot
for
the
same
reason,
yeah
if
a
pr
gets.
B
A
And
so.
B
Okay,
I
I
have
a.
I
have
a
document
in
the
file
system
of
this
computer
that
I'm
looking
at
right
now,
which
has
the
get
workflow
I'll
write
some
text
around
it
and
I'll
add
it
to
the
dev
guide
somewhere
I'll
I'll
go
through
and
find
a
place.
B
A
The
developer
guide
just
how
to
deal
with
state.
What
is
the
workflow
for
stale
peers
and
just
create
a
pr,
and
then
we
can
have
a
discussion
there.
I'm
pretty
sure
a
lot
of
people
will
have
different
opinions,
but
I
think
the
main
idea
should
be
that
we
are
still
and
nobody
is
taking
accountability
for
it,
and
the
change
is
good.
Whatever
you
mentioned,
we
just
do
that.
B
Yeah
also
this
this
isn't
in
the
in
the
agenda,
but
you
you
said
this
reminded
me
of
this
when
we're
when
we
have
this
install
guide
up
and
like
the
this,
like
that
first
task,
the
getting
the
install
guide
and
the
dev
guide
link
and
the
the
tracker
bug
for
the
bug
tracker
link
on
on
the
website.
When
that's
done,
the
next
thing
is
to
go
through
the
developer
guide
and
developer
guide
has
tons
of
good
stuff
in
it.
It
was
last
or
it.
B
It
refers
to
itself
as
being
last
updated
in
march
of
2016,
which
is
definitely
not
true
anymore.
But
that
shows
that,
like
the
whole
thing
needs
to
be
gone
through,
and
so
I
want
to
use
like
the
the
old
linus
torvalds
precept
that
all
bugs
are
shallow
with
enough
eyes,
and
I
want
everybody
to
like
I
want.
I
want
to
use
you
and
anyone
at
your
level
who
has
influence
not
right
now
but
like
in
a
month
to
have
like
a
week
of
looking
at
the
dev
guy.
B
So,
like
you
look
at
the
things
that
you
know
well
and
then
you
send
me
like.
I
will
receive,
I
don't
care
if
it's
emails
or
pull
requests
or
whatever
and
then
I'll
just
go
through
and
integrate
the
whole
thing
into
a
an
updated
dev
guide
for
2020.,
because
it's
full
of
good
stuff,
but
I
don't
know
where
there's
holes
and
I
also
don't
know
enough
to
know
which
things
like
where
the
where's
the
sand
shifted.
B
So
anyway,
that's
not
on
the
agenda,
but
that's
the
next
thing.
That's
the
next
big,
like
ongoing
project
to
take
the
place
of
this
installation
guide
project
is
the
the
the
thorough
reworking
of
the
dab
guide.
So
then
I
I
removed
the
disc
prediction
section
because
dirt
wash,
I
don't
know
dirt,
watch
his
actual
name
he's
in
hamburg
in
germany
he
is
a
very
vocal
critic
of
stuff
on
on
the
irc
channel
and
he
is
also
very
helpful,
and
so
that's
useful
to
me.
B
I
like
him
because
he's
he's
loud
and
his
complaints
are
meaningful
and
so
disc
prediction
apparently
doesn't
work.
We're
waiting
on
keifu
asked
some
guy
named
rick
that
I
don't
know
if
there
is
a
substitute
for
it.
B
A
Yeah
he's
the
person
behind
our
profit
store
stuff,
so
he
he
is
the
right
person
to
ask.
If,
obviously,
if
he
doesn't
does
it
doesn't
respond
or
like
if
he
is
also
busy
with
other
things,
we
can
go
ahead
and
take
a
call,
but
it's
a
good
idea
to
check
with
him
once.
A
I'm
pretty
sure
josh
checked
too,
but
I
mean
it's
no
harm
to
check.
B
Yeah
I
I
asked
josh,
then
josh
got
back
to
me
like
at
the
end
of
that
work
day,
saying
like
no,
it's
not
and
now
like.
Now
this
is
it's
going
through
the
same
process
on
github
as
we
speak
and
the
last
thing,
which
is
it's
a
vague
idea
that
I'll
just
mention
now
when
we're
done
with
with
having
the
installation
guide.
B
I
want
to
make
a
short
video,
no,
like,
I
hope,
no
more
than
five
minutes
showing
how
to
install
stuff-
and
I
know
that
I'm
a
I
know
I
was
hired
as
a
tech
writer,
but
I
would
like
to
do
some
small
video
productions
because
they
would
be.
It
would
be
helpful
to
have
all
the
steps,
not
just
in
a
in
a
document
but
also
like
recorded,
so
that
it's
sort
of
it's
like
a
proof
of
concept.
B
This
thing
actually
works
also,
and
I
was
born
in
1979,
but
I
understand
that
people
who
are
younger
prefer
videos
to
text.
So
that's
a
plan.
I
have
another
document
which
I
will
show
you
the
next
time
we
meet
or
something
where
I
have
collected
youtube
videos
of
introductions
to
various
things
that
are
similar
to
what
I
envisioned
tours
of
the
basic
parts
of
stuff.
B
Now
a
lot
of
these
things
are
physical
ones,
on
woodworking
one's
on
nes
tetris,
but
it'll
give
you
an
idea
of
what
I
envisioned
for
it.
So
anyway,
the
the
future
looks
like
this.
B
We
get
the
install
guide
done,
then
we
go
through
dev
guide,
using
everybody's
expertise
and
then,
when
those
are
done
and
it
feels
like
the
site
is
fresher
and
easier
to
serendipitously
navigate,
then
we
start
doing
short
films
that
are
instructional,
that
present
the
work
and
and
if
we
can
do
these
short
films
quickly,
that
would
be
good
like
if
a
short
film
takes
no
more
than
like
a
week
to
produce.
That
would
be
great,
so
yeah,
so
that
anyway,
those
are
those
are
my
plans
for
the
future.
B
A
B
B
A
Is
good
I
mean
yeah,
I
think
I
think
the
last
one
I
think
I
can
see
how
it
can
be
useful
for
people
who
prefer
visual
stuff
more
than
like
just
reading.
Let's
talk
about
it
more,
let's
get
ideas
from
other
people,
I
mean
the
easiest
way
I
can
think
of
it
is
like
you
know
you
do
the
stuff
and
just
take
like
use
screencast
or
something
to
like
record
it
and
create
a
small
video
out
of
it.
B
I
read,
as
I
read
through
the
old
stuff
doc
stuff
from
before
I
was
hired.
I
see
that
it's
a
lot
of
this
stuff.
That
is
exactly
the
stuff
that
I've
confronted
like.