►
From YouTube: Ceph Docubetter Meeting 2018-10-26
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
B
A
B
A
Was
just
letting
Gaurav
know
so
so
Gaurav
is
an
Indian
in
India
with
self
support,
I
believe.
B
A
He
has
recently
made
some
talk,
contributions
to
I,
think
RBD
and
I
was
just
telling
him
that
we
started
this
focused
effort
to
improve
Doc's
overall
in
SEF,
and
now
we
just
don't
want
to
here.
Are
people
complaining
that
our
talks
are
bad?
Nobody
is
in
which
they
can
either
go
and
fix
them
themselves,
or
at
least
come
and
report
it
to
us
of
what
exactly
is
bad
and
then
we
will
ensure
that
it
gets
fixed
and
no,
you
want
to
kick
it
off
sure.
B
A
B
B
So
right
now,
if
you
visit
the
stocks
URL
in
here,
I'm
gonna,
see,
if
you
refresh
this
page,
you're
gonna
see
one
of
three
states
and
these
three
different
states
are
there.
It's
randomly
selected
each
time
you
refresh
the
page,
and
that's
really
just
because
we
can't
it's
like
there's
like
a
you,
there's
like
a
bootstrapping
of
this
state
and
it's
only
gonna
work
when
it
actually
finally
gets
deployed
to
the
master
branch.
So
right
now
we're
just
like
simulating
what
it
would
be
like
if
you
were
viewing
this
on
other
branches,.
B
And
there's
like
a
couple
lines
of
code
that
we
just
need
to
comment
out
right
before
we
merge
and
it
all
like
starts
using
the
actual
URL,
let's
see
so,
okay.
So
here's
an
example:
the
screen
where
it's
saying
this
is
a
development
version,
so
this
would
apply
to
basically
any
version
of
the
documentation.
That's
rendered
for
an
end-of-life
or
sorry
not
an
end-of-life
am
or
for
like
a
PR
or
a
wit
branch,
or
something
like
that.
A
B
B
Okay,
so
I
refreshed
it,
and
this
is
simulating
this
would
be
like
if
you
visited
the
jewel
documentation
right.
There's
the
end-of-life.
You
know,
release
and
then
same
same
thing
goes
there.
We
can
discuss
that
later
and
then
see
so
then,
okay,
so
then,
if
you
are
on
like
mimic
or
luminous,
then
this
edit
on
github
is
gonna.
Take
you
to
the
correct
branch
over
and
get
so
it'll
be
like
a
pull
request
that
get
started
or
make,
or
for
luminous
or
whatever
version
of
the
doctor
on.
A
A
B
B
A
And
I
think
the
commute
that
I
added
is
already
showing
up
to
report
the
documentation,
bug
and
it
redirects
to
the
projects
page.
The
thing
that
is
left
to
do
is
to
actually
write
some
introduction
in
there
that
how
it
works
and
what
what
should
a
user
go
in
and
do
there
so
I
will
probably
fill
that
up
and
then
and
that's
the
pairing
thing
it
has
nothing
to
do
with
the
PR
effort.
Well
that
sound,
that's
fun
to
do
on
mind
that
I
will
finish
doing
maybe
next
week.
A
Yeah
so
kind
of
do
you
have
any
questions
so
far?
I
know
it's
a
new
way
to
do
things,
but
it
is
eventually
making
our
life
easier
to
create,
pull,
requests
and
report
bugs
you
don't
have
to
go
through
the
whole
process
of
and
then
you
could
choose
to
still
open
a
tracker
issue
for
documentation,
but
if
you
wish
to
you
can
just
go
and
fix
it
immediately
on
github.
Does
that
make
sense
to
you.
A
A
If
you
have
any
more
this
just
if
you
have
any
more
bugs
that
you've
found
while
your
you
were
investigating
RVD
or
other
parts
of
safe
I,
think
this
is
gonna
get
merged
next
week.
So,
instead
of
going
the
other
route,
you
could
just
use
this
route
to
just
make
a
a
simple
commit
to
fix
a
documentation,
bug
that
you
observed,
and
that
will
be.
That
will
be
really
good.
That
will
be
like
a
kickoff
for
this
whole
process.
B
A
I
think
so
I
think
we
should
talk
about
next
steps
because
I
see
this,
we
are
getting
much
next
week
right.
So
on
I,
honestly,
there
were
a
lot
of
ideas
that
came
in
the
email
thread
that
it
started
initially,
and
we
had
decided
at
some
point
that
we
are
only
going
to
first
tackle
the
basic
problem
that
we
were
trying
to
solve
and
then
maybe
incorporate
the
other
things.
Maybe
this
is
a
good
time
to
go
back
to
that
email
thread
and
prioritize
the
next
things
that
we
would
like
to
do
in
this
direction.
B
B
A
I
was
just
thinking
the
the
first
problem
that
you
had
pointed
out
was
like
when
we
search
for
safe
documentation.
It's
never
that
you
get
the
latest
one.
Maybe
now
that
we
are
trying
to
fix
the
right
things,
we
should
also
make
people
get
to
the
right
links
easily,
and
so
the
search
bar
or
the
I
think
the
Google
search.
Optimization.
A
B
So
I
think
that's
kind
of
we
should
do
both
of
those,
maybe
at
the
same
time.
So
it's
kind
of
like
how
do
you
get
Google
to
tell
you
the
right
link
and
then,
if
you
end
up
at
the
wrong
link
by
some
other
method
or
if
Google
doesn't
give
you
what
you
want,
then
once
you
arrive,
you'll
see
the
banner
ad.
That
says
this
is
an
old
version
and
you
jump
to
the
newer
version.
I
think.
B
A
B
I
think
it's
something
about
tagging
links
that
helps
the
search
engine
figure
out
what's
going
on,
but
then
we
can
also
blacklist
certain
URL
formats.
So
maybe
we
could
blacklist
all
the
PRS
and
and
maybe
like
development
branches
and
stuff
like
that,
and
then
you
can
use
tags
in
the
header
I
think.
Maybe
we
could
shoot
for
you
know
it's
like.
If
you
type
in
SEM
you
get
you
go
to
what
mimic
you'd
always
go
to
the
latest
stable
release
instead
of
a
master,
maybe
yeah.
A
A
B
B
A
And
if
somebody
wants
to
particularly
search
for
Luminess,
they
should
just
type
in
luminous
in
their
search
cuher
in
that
should
help
them
land
the
right
page
or
even
the
navigation
bar
is
going
to
be
useful
there
right
and
even
if
I
land
it
I
can
just
go
pick
out.
A
navigation
bar
and
I
can
just
go
to
luminous
Docs
or
the
particular
same
same
thing.
Yeah.
B
B
B
A
Since
this
meeting
is
getting
recorded,
the
other
thing,
but
we
should
put
a
process
that
anybody
who
would
like
to
get
involved
in
trying
to
make
the
docs
better
in
any
way,
because
this
is
there's
etherpad
and
then
there
is
an
email
threat.
Unsafe
devil
just
feel
free
to
come
and
contribute
and
join
this
meeting
or
not
just
contribute
that.
B
A
I
think
the
mailing
list
it
depends
on
you
know
what
what
level
they
are
using
IRC
or
whatever
email,
email,
mailing
list.
Anything
works
out.
I
think
and
I
also
think
that
once
this
PR
gets
merged.
Nor
maybe,
since
you
are
the
main
contributors
to
send
out
an
email
saying
that
this
exists
and
people
should
just
use
this
framework
just
just
to
spread
the
know-how
right
sure,
yep.