►
From YouTube: 2019-08-28:: Ceph DocUBetter Meeting
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
Okay,
so
this
the
aim
here
is
that
we
are
going
to
be
using
this
talk
about
our
meeting,
which
is
there
on
the
community
calendar
at
least
today,
and
maybe
in
the
following,
a
couple
of
meetings
to
discuss
gaps
in
realistic
human
tation
and
see
how
we
can
address
those
gaps
and
structure
the
documentation
in
a
better
manner,
so
that
people
can
just
easily
go
look
at
stuff.
That
makes
sense
for
different
level
of
users
like
what
should
be
starting
page
for
beginners
or
advanced,
and
all
that
kind
of
stuff
and
I.
B
Think
I
have
the
perfect
people
on
the
call
with
me,
because
you
guys
have
a
lot
of
experience
dealing
with
trade-offs.
What
are
the
most
amount
of
questions
or
gaps?
You
hear
about
a
Raiders
document
in
the
documentation
in
general
Raiders
documentation,
and
then
we
can
try
to
find
out.
What's
the
best
way
to
address
this
I.
C
Okay,
I
can
start
Josh.
You
know
I
created
a
couple
of
trackers
or
discussed,
creating
a
couple
of
trackers
now
I'm
sorry,
Josh,
created
a
couple
of
track
is
a
long
time
ago
that
we
recently
discussed
because
somebody
brought
up
in
the
in
the
I
in
IRC
in
safety,
well
that
the
Barbie
day
and
lib
rathaus,
C++
api's,
were
poorly
documented
and
I.
Don't
think,
there's
any
argument
that
they
are
not
so
I
volunteered
to
document
at
least
liberate
us
the
C++
API,
and
that
tracker
is
one
eight
one.
Seven.
B
C
B
B
B
We,
how
do
we
suggest
we
cover
blue
store
since
it's
become
huge
now,
it's
not
not
that
much
like
adding
everything
to
one
doc
might
not
make
sense.
So
maybe
adding
now
the
stuff
about
our
blue,
FS
and
blue
store
work
in
general
and
the
how
the
alligator
stuff
works
could
just
go
into
this
existing
document
and
even
configuring
blue
store
I
think
we
still
have
some
documentation
about
OST
memory,
Target
and
other
stuff,
but
there
are
a
lot
of
other
options
that
could
get
covered
in
general.
Do
you
guys
think.
D
Yeah
I
think
that's
like
a
good
example.
Another
major
area
is,
however,
recommendations
for
boost
or
inheritance
by
the
devices
up
we
came
up
with
then
have
rough
kaileena,
four
percent
at
one
point,
and
then
we've
had
some
more
details
of
that.
Thank
is
also
some
really
older.
Much
older
pages,
like
this
hardware,
recommendations,
page
and
earth
introduction,
which
is
just
almost
all
out
of
date,
especially
with
boost
or
I,
think
it's
a
similar
one
about,
like
which
kernels
people
to
run
and
that's
like
we
had
a
to
I,
can
find
that.
A
E
E
So
I
was
that
was
secondary.
What
I'm
suggesting
is
that,
if
we
invite
like
a
user,
particularly
one
who
does
a
lot
of
backwards,
but
doesn't
do
a
lot
of
normal,
they
might
have
a
CRISPR
idea
of
what
obviously
is
missing.
They
won't
know
how
to
fix
it
or
where
to
get
the
information,
but
that's
fine.
We
do
soliciting
a
viewpoint
like
that,
like
or
I
like
Kyle
Bader
who'd
be
good
for
performance
stuff
in
blue
store
just
for
pointing
out
what
isn't
present
and
what
topics
need
to
be
covered.
B
What
should
be
our
approach
if
we
want
to
just
look
at
one
page,
which
has
several
paragraphs
or
like
several
bullets
about
like?
If
this
is
what
you
should
know
about
the
OST
and
then
you
can
go
and
visit
each
of
these
Doc's?
We
already
have
that
we
think,
or
should
we
create
something
or
should
we
add
for
some
existing
there.
E
B
E
D
E
D
E
E
E
B
E
B
C
E
C
A
E
B
D
C
B
E
C
B
D
B
A
A
So
you
don't
have
to
actually
have
like
I
was
thinking
there'd,
be
like
a
process
like
you'd
we'd,
add
something
where
there's
comment
lines
that
will
become
doc
lines
and
then
something
just
processes
it
straight
down.
So
where,
let's
say,
there's
like
the
scrub
section,
so
there's
a
comment
that
basically
a
code
comment
that
becomes
a
doc
like
the
heading
for
scrub
and
then
the
scrubber
entries
are
below
that.
So
I
was
thinking
like
now.
We
could
tag
it
and
but
then
you'd
have
to
have
like
somewhere,
where
you
put
here
the
headings
the.
A
Or
maybe
there's
like
a
doc
file?
That's
like
a
pre
doc
file
that
has
the
headings
and
then
says
this
is
the
tag
to
consolidate
this
group
configs,
even
no
matter
what
order
they're
in
and
this
in
the
source
file,
I
I
hate
to
have
rearranged.
The
you
know
have
that
file
get
all
rearranged
on
the
one
hand,
on
the
other
hand,
I
kind
of
like
it
to
be
in
order,
as
opposed
to
having
something
that
creates
the
order,
but
that
could
be
debated.
D
B
E
A
C
A
C
D
C
B
D
C
E
D
D
B
B
E
C
C
B
A
B
C
C
B
B
Yes,
I
think
we
kind
of
have
a
bunch
of
things
here
and
we
also
know
what's
the
highest
priority
things,
so,
let's
just
try
to
get
some
of
these
at
rest.
If
we
feel
that
we
want
to
meet
again
after
two
weeks
or
whenever
we
want,
we
can
do
that.
Oh
and
also
we
can
talk
offline.
If
that
helps
does.
B
It's
the
sister
project
really
need
a
creator,
but
currently
the
structure
is
that
we
have
like
mimic
Nautilus
Master's
bugs
that
get
created,
but
this
hasn't
been
used
or
utilized.
Well,
so
maybe
we
can
figure
out
a
way
to
structure
this
human,
but
we
can
just
have
like
graders
bugs
and
we
can
decide
what
we
want
to
bat
for
and
whatnot.
B
E
I'm
gonna
wing
this
this
pad
into
project.
B
B
B
C
That's
good
I'm,
currently
I'm,
currently
asking
Nathan,
but
the
tracker,
if
I
can
take
over
the
the
documentation
bugs
for
me,
Brad
I'll,
C++,
API,
Emily,
Bobby,
D,
C++,
API
and
I
think
I'm
trying
dedicate
either
a
day
or
half
a
day
a
week
to
it
until
I
get
it
done.
So
who
does
anyone
know
who
John
Wilkins
is.