►
From YouTube: 2019-08-14:: 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
Have
two
things
that
I
want
to
talk
about
real,
quick
just
to
follow
up
from
our
previous
discussion
about
the
signed
off
by
thing?
If
we
can
get
rid
of
it
or
what
can
we
do
to
make
it
easier?
So
looks
like
people
are
okay
with
getting
rid
of
it
for
Doc
pr's,
but
it
might
just
be
harder
to
integrate
that
kind
of
rule
or
that
kind
of
logic
into
it
have
to
just
do
that
so
now.
B
We
can
add
the
signed
off
by
in
the
merge,
commit
where
we
add
the
reviewed
by
and
all
that
stuff,
which
would
just
mean
that
it
is
in
the
next
module
omit
and
not
in
the
original
PR,
but
in
general
I
think
I
still
see
value
in
having
of
something
like
easy
steps
to
add
a
signed
off
by
in
whatever
state
a
person
is
in
from
there.
Like.
B
You
know,
starting
from
the
basic
situation
where
you
want
to
add
a
signed
out
by
or
if
you
already
created
a
PR
and
then
you
want
to
add
it
or
if
you've
used
the
web
UI,
and
you
then
want
to
add
it
so
like
these
are
the
three
scenarios
where
people
might
want
to
understand
how
to
do
that
stuff.
So
I
think
it
wouldn't
it
wouldn't
harm
us
to
just
write
a
simple
dog-
or
maybe
you
know
just
you
know,
create
a
video
of
how
that
can
be
done.
B
And
I
mean
the
only
problem
again
with
making
signed
off
by
not
a
mandatory
check
is
that
people
can
still
override
it
and
then
again
doesn't
solve
the
the
whole
purpose
of
having
a
signed
off
by
in
regular
VRS
as
well
make
which
make
four
changes
so
so
I
think
that's
kind
of
clear.
We
thought
probably
working
on
something
that
can
make
it
easier,
and
we
can
just
point
people
to
that
particular
link
and
have
it
in
the
docs
as
well
in
the
getting
started,
features
as
well.
I.
B
Thing
that
I
wanted
to
bring
up
was
about
this,
which
I've
added
to
the
ether
pad
already
but
I'm
just
pasting
it
in
the
chat
as
well.
So
we
have
this
contract
position
open
for
deaf
upstream
documentation,
and
now
we
have
it
posted
in
our
website
as
well,
so
the
requirements
and
the
deliverables
and
the
responsibilities
and
all
the
terms
and
conditions
are
already
there.
A
B
B
B
They
stood
on
the
track.
The
title
of
the
talk
is
about
of
growing
in
sustaining
open-source
software,
and
we
are
going
to
be
talking
about
the
evolution
of
the
self
development
process
and
the
idea.
The
main
idea
there
is
to
highlight
the
importance
of
documentation
and
the
stuff
that
we
are
trying
to
do
here
at
off
the
better
to
bridge
the
gaps
of
how
quickly
the
code
changes,
but
the
documentation
is
not
up
to
date
and
that's
one
of
the
biggest
challenges
for
users
and
developers.
B
So
I
am
going
to
be
talking
to
Mike
our
community
manager
later
this
week
about
what
other
stuff
are
this
relevant
with
respect
to
the
stock?
But
that's
about
it.
That's
kind
of
the
idea
is
to
first
be
able
to
narrow
down
on
what
are
the
key
aspects
that
we
should
highlight
in
the
stock
and
how
we
can
use
this
platform,
which
is
not
just
a
safe
that
form
or
a
storage
platform,
but
just
an
open
source
software
platform
to
talk
about
safe
and
talk
about
documentation
and
other
improvements.
A
B
B
So
probably
that
is
another
thing
that
Mike
can
help
us
with,
and
some
of
the
ideas
that
we
have
discussed
earlier
in
this
meeting
is
something
that
I
want
to
propose
to
him
as
well,
and
maybe
we
can
have
him
come
to
one
of
these
meetings
and
let
us
know
how
he
thinks
we
can
proceed
on
that
and
how
we
can
get
more
people.
You
involve,
even
in
the
website
aspect
of
things,
not
just
the
the
drastic
safecom
part
of
it.
I.