►
From YouTube: CDS Infernalis (Day 1) -- Community && Governance
Description
Videos from Ceph Developer Summit: Infernalis (Day 1)
03 March 2015
https://wiki.ceph.com/Planning/CDS/Infernalis_(Mar_2015)
A
All
right
welcome
to
the
very
first
session
of
CDs
infernalis.
This
one
has
mashed
together
a
couple
of
blueprints:
it's
our
governance
discussion,
so
this
will
be
both
the
governance
as
well
as
there
was
some
update
to
our
SEF
user
committee,
which
was
originally
started
by
Loic.
Eric
is
now
in
charge
of
the
in
charge
of
the
user
committee.
I,
don't
believe,
he's
been
able
to
make
it
unless
he's
on
one
of
the
the
dial
ends.
Eric
are
you
here?
A
Can
you
give
a
shout
or
in
IRC
all
right,
I'm,
not
seeing
him
so
yeah
eric?
Is
the
current
reigning
chair
of
our
SEF
user
committee?
The
user
committee
was
originally
started
as
kind
of
the
the
first
baby
steps
towards
governance.
It
was
to
give
the
users
actual
purchase
over
some
of
the
SEF
community.
They
tend
to
run
things
like
our
our
user,
the
the
release,
notes
and
things
like
that.
They
they
look
at
who
committed
what
kind
of
put
that
together.
They
also
have
a
very
strong
presence
in
organizing
our
meetups
and
facilitating
those.
A
If
you
have
meetups
go
ahead
and
check
out
our
mailing
list
page
and
send
them
a
list
note
to
the
SEF
user
committee
mailing
list,
there
are
resources
available
to
them
that
they
can
help
your
your
meetup,
be
bigger,
better,
faster,
stronger,
so
go
ahead
and
take
a
look
at
that.
If
you
want
for
now,
I
was
going
to
run
us
through
some
of
the
SEF
governance,
which
has
been
a
long
long
long
time
in
coming.
A
It's
gone
through
many
iterations,
as
many
of
you
know
before
the
acquisition
by
Red
Hat,
we
had
looked
at
moving
the
SEF
IP
into
a
third-party
foundation
set
up
the
front-runner
when
we
were
looking
at
that
was
the
Linux
Foundation.
We
were
going
to
run
SEF
as
a
collaborative
project
similar
to
what
Zen
then
others
have
done.
A
There
are
three
docs
there's
the
Charter
at
that's
more
or
less
just
an
overview
of
kind
of
our
goals,
principles
a
bit
of
the
who,
what
where
then
there's
the
governance
doc,
which
is
all
the
meaty
details
of
how
we
are
looking
at
running,
our
the
SEF
governance,
as
well
as
a
trademark
doc
and
I
figure
we'd
just
kind
of
leaf
through
these
a
bit.
Take
a
look,
I,
welcome,
comment,
any
feedback
questions
just
go
ahead
and
shout
them
out
via
voice
or
text.
A
I
absolutely
want
the
community
to
be
involved
in
building
this
governance.
I
don't
want
this
to
be
something
that
red
hat
hands
down
from
on
high
and
says
this
is
the
way
of
the
world.
That's
never
been
the
way
we
do
things
in
the
SEF
project
and
I.
Don't
want
to
start
now.
So
definitely
this
is
your
opportunity
to
speak
up
and
let
me
know
what
you
think
about
the
governance
so
I'll
start
with
the
SEF
charter,
obviously
just
a
little
bit
about
what
we're
going
for.
A
You
know
kind
of
the
whole
change
the
world
with
open
source
vision
that
sage
started
on
so
long
long
ago.
You
know
obviously
we're
trying
to
figure
out
ways
to
do
to
proprietary
storage
vendors,
what
linux
did
two
things
like
unix
and
all
tricks,
and
things
like
that,
so
that's
kind
of
what's
colored,
all
of
our
thinking
and
how
we're
approaching
SEF
and
how
we're
approaching
this
governance
stuff.
So
we
want
it
to
be
very
open
and
very
participatory
and
led
by
the
leaders
in
our
community,
both
corporate
and
none.
A
Obviously,
the
the
biggest
thing
that
you
can
take
away
from
this
charter
beyond
the
fact
that
we're
you
know,
open-source
diehards
is
that
transparency
is
a
big
part
of
what
we
want
this.
This
governance
to
be
for
us,
the
the
transparency
in
everything
that
we
do.
We
want
to
make
sure
that
you
know
everything
from
engineering
decisions,
the
minutiae
of
implementation,
all
the
way
up
to
broad
sweeping
kind
of
strategic
initiatives,
all
the
things
that
we
do.
We
want
to
make
sure
that
those
are
done
in
public
and
recorded
for
later
scrutiny.
A
We
don't
want
any
water
cooler
discussions,
we
don't
want
kind
of
people
doing
things
in
secret
and
then
suddenly
having
the
the
world
change
around
those
who
are
helping
us
build
it.
The
next
portion
here
IP
management.
This
is
a
big
portion
of
what
we
want
the
SEF
board
to
help
us
do.
The
governance
structure
should
allow
those
participating
in
it.
You
make
sure
that
the
SEF
copyright,
the
SEF
brand
on
all
of
the
moving
pieces
there
and
are
being
treated
appropriately
by
the
community
and
all
of
those
participating.
A
You
know.
Obviously,
we
want
the
SEF
board
to
drive
other
things
like
adoption
and
whatnot,
but
we
also
want
to
make
sure
that
they're
kind
of
taking
over
as
the
Shepherd's
there's
one
point
in
here
that
will
probably
differ
from
a
foundational
setup.
Is
that
if
there
is
any
enforcement,
we
have
to
go
after
anybody
for
building
something
awful
and
calling
its
F
and
whatever
Red
Hat
will
do
that
and
and
likes
to
make
sure
that
they're,
the
ones
that
have
to
play
the
bad
guy?
That
way,
our
community
can
always
be
the
good
guys.
A
So
that's
the
only
difference
from
kind
of
a
foundational
set
up
in
terms
of
IP
management
roles.
I
didn't
want
to
outline
a
ton
of
roles
and
responsibilities,
and
everything
in
this
I
just
wanted
to
give
people
an
idea
of
who's
who's
out
there
right
the
project
lead.
You
know,
sage
has
long
been
our
benevolent
dictator
for
life.
You
know.
A
Sometimes,
life
takes
you
in
a
different
direction,
though
so
I
wanted
to
make
sure
that
the
project
lead
was
was
outlined
in
such
a
way
that
if
sage
ever
decided
that
he
needed
break
or
wanted
to
retire
or
something
he
would
be
able
to
sit
step
down
and
the
component
technical
leads,
his
lieutenants
would
be
able
to
find
somebody
to
replace
him,
but
for
now
for
the
foreseeable
future,
and
hopefully
for
the
long
term,
sage
will
continue
to
carry
this
F
banner.
In
all
things
that
takes
me,
the
component
technical
leads.
A
Obviously,
we've
identified
these
people
in
a
number
of
different
places.
This
is
like
Gregory
for
calamari
and
Josh
for
rbd
and
how
am
I
force
FS,
and
you
know
these
are
the
folks
that
are
leading
the
charge
for
the
individual
component
stuff
within
the
SEF
platform.
You
know
these
are
also
the
folks
that
will
probably
be
doing
the
majority
of
the
SEF
Tech
Talks.
If
you
haven't
seen
those
those
are
up
and
running,
you
know,
Sam
just
did
his
ratos
Tech
Talk
and
he's
the
guy
leading
the
charge
on
raid
0.
A
So
the
the
idea
here
with
this
governance
is
to
surface
more
of
this
kind
of
command
and
control
infrastructure.
The
folks
who
know
what's
going
on.
We
want
to
make
sure
that
those
are
very
visible.
Just
as
people
like
Andrew
Morton
are
very
visible
in
the
linux
kernel
community,
you
know
not.
Everyone
can
go
and
talk
to
Lena
seeeeee.
You
know,
11
human
bag
of
meat
does
not
scale,
so
we
need
to
make
sure
that
we
have
many
bags
of
meat
in
the
Ceph
community.
A
A
You
know
who
our
top
contributors
are,
where
they're
from
who's
working
on.
What
and
those
sorts
of
statistics
also
a
good
snapshot
of
that
is
available
from
the
metrics
f,
comma
dashboard,
but
definitely
would
like
to
recognize
our
committers
we're
very
appreciative
of
our
community
and
they
do
a
lot
for
us.
So
if
you
can
think
of
other
good
ways,
please
don't
hesitate
to.
Let
me
know
and
then
a
little
bit
about
the
the
governance
structure.
A
Don't
want
this
to
be
too
heavy-handed,
definitely
want
to
kind
of
keep
it
light
weight
as
much
as
possible
as
much
as
you
can,
when
you
get
giant
behemoth
the
organizations
involved,
but
we're
looking
at
kind
of
three
three
main
bodies
with
maybe
a
couple
of
little
groups
that
will
splinter
off
and
do
things
on
their
own,
but
but
the
main
main
workload
will
be
done
by
the
SEF
board,
which
is
very
much
outlined
in
the
next
doc.
Will
look
at
there's
the
technical
committee?
These
are
the
component
technical
leads.
A
This
is
where
all
of
the
implementation
where
the
metal
meets
the
meet.
This
is
where
the
things
get
done.
This
is
developers
only.
It
will
not
be
under
the
purview
or
control
of
the
board.
It
will
be
kind
of
separate
to
make
sure
that
engineering
decisions
are
being
made
by
engineers
and
correctly
and
not
guided
by
folks
who
have
perhaps
other
interests,
and
then
the
user
committee
obviously
has
already
been
going
strong.
We
would
like
to
allow
the
user
committee
to
grow
and
perhaps
take
on
some
new
roles.
A
A
Looking
at
the
development
process,
you
can
take
a
look
at
this.
It's
just
trying
to
outline
a
bit
of
the
minutiae
for
people
that
are
new
coming
in
obviously,
most
of
the
people
on
this
call
already
know.
What's
going
on
the
normal
get
branching
model
code
review,
how
blueprints
work
all
of
the
pieces
that
you've
all
been
intimately
aware
of
for
for
a
long
time
now,
there's
a
little
bit
about
conflict
resolution
in
here.
A
This
will
probably
get
fleshed
out
a
little
bit
more,
but
mostly,
we
just
want
to
make
sure
that
there's
safety
release
valves
so
that
we
don't
have
giant
conflicts
between
folk
and
there's
a
way
to
resolve
conflict
in
a
amicable
fashion.
But
so
far
we
haven't
seen
a
lot
of
need
for
that.
You
all
have
been
very
easy
going
and
and
accepting,
especially
when
bumbling
community
managers
break
things
like
the
wiki,
so
I
appreciate
that
are
there
any
questions,
I'm
just
kind
of
the
general
charter
the
who?
A
A
Barring
any
questions,
we
keep
going
seff
governance
details,
so
the
idea
here
is
to
kind
of
create
a
group
of
prominent
representatives
for
the
seffy
Co
system,
so
whoever
those
folks
may
be.
The
idea
is,
is
too
it's
less
about
taking
individual
users
and
making
them
decision-makers,
I
figure.
Individual
users
will
participate
within
the
user
community
and
the
user
committee,
and
that
user
committee
chair
will
have
a
seat
on
the
board
and
represent
those
users
interests.
A
A
No,
yes,
there
you
are,
and
now
we
can
hear
you
they
I.
B
We
do
not
notice
that
someone,
someone
from
the
outside
does
not
have
access,
so
we
we
actually
care
about
that,
and
since
I'm
not
always
connected
to
the
VPN,
I
tend
to
notice
more
than
most
so
that's
an
area
where
we
are
currently
working
on
to
make
sure
that
the
community
has
all
permissions
to
participate
in
the
past
when
it
was
in
tank.
That
didn't
happen
so
much,
but
because
of
the
internal
reorganization,
that's
something
that
we
have
to
tackle.
That
is
kind
of
new,
and
hopefully
it
will
disappear
in
a
few
month.
Yeah.
A
And
actually,
as
a
side
note
to
that,
most
of
the
VPN
resources
are
in
our
testing
lab
the
cpu
lab.
There
will
also
be
a
publicly
available
community
test
lab
that
has
just
come
along,
so
I
just
got
done:
spending
about
a
half
a
million
dollars,
red-hats
money
to
build
a
community
test
lab.
There
have
been
some
ops
hurdles
in
terms
of
getting
that
deployed
and
accessible,
but
bear
in
mind
that
that
will
be
coming.
Probably
within
the
next
few
months.
As
we
migrate
away
from
the
stuff.
A
That's
still
sitting
in
dreamhouse
tracks,
there
will
be
a
public
test
cluster
available
in
addition
to
the
internal
VPN
resources.
That
Loic
was
just
talking
about
so
there
that
will
be
nice.
That's
where
a
lot
of
our
donated
hardware,
from
some
of
the
hardware
vendors
that
we've
been
partnering
with
the
dells
and
the
Intel's
and
the
hgs
tease
of
the
world.
A
lot
of
that
hardware
will
be
going
into
the
community
test
lab
where
anyone
and
everyone
will
be
able
to
run
their
tests
against
real
hardware
with
real
SEF
cluster.
A
A
A
Okay,
so
the
next
one
there
is
the
SEF
governance
doc.
This
is
a
little
bit
more
of
the
meaty
details
of
how
how
the
the
SEF
governance
structure
is
supposed
to
work.
Some
of
this
is
a
little
rough
I
wanted
to
kind
of
get
it
out
there
before
I
really
took
some
time
to
polish.
It
I
want
to
make
sure
that
there's
nothing
completely
out
of
whack
that
our
community
had
a
chance
to
chew
on
it
for
a
bit
and
give
me
feedback.
A
So,
as
I
mentioned,
the
idea
here
is
to
have
three
main
groups:
the
board,
the
technical
midi
in
the
user
committee
and
as
I
was
just
saying
saying
a
minute
ago.
The
idea
is
for
prominent
representatives
of
the
SEF
kind
of
ecosystem
to
be
represented
rather
than
individual
users.
My
thinking
is,
the
SEF
board
will
probably
be
larger
groups
of
folk
that
are
committing
just
to
kind
of
give
each
of
those
larger
groups
of
folk,
a
lightning
rod
into
the
SEF
community.
A
Just
like
the
user
committee
chair
will
take
all
of
the
generic
user
comments,
feedback,
etc
needs
desires
into
the
board.
I
figured
that
larger
organizations
like
Susa
and
canonical
and
and
a
few
other
folks
have
also
expressed
interest,
but
those
two
folks,
I've
already
talked
to
and
I
know
their
interest
in
participating.
You
know
all
of
these
people
have
groups
of
engineers
that
are
dedicated
to
SEF
and
I
wanted
to
make
sure
that
those
voices
were
in
terms
of
direction
and
approach,
and
just
general
community
growth,
adoption
and
management.
A
All
right
so
the
expectations.
Obviously
the
board
will
have
a
number
of
functions,
but
obviously
the
the
biggest
one
for
the
board
is
going
to
be
helping
with
community
outreach
and
evangelism.
The
adoption
play
how
we're
telling
people,
what
we're
doing
all
of
the
various
resources
that
are
available,
welcoming
new
people
in
and
and
making
sure
that
the
SEF
project
is
Shepard
along
in
a
healthy
and
productive
manner.
A
A
Maybe
enforce
is
too
strong
of
a
word,
but
definitely
oversee
and
and
gently
police
they
will
maintain
and
they
will
advise
so
promoting.
Obviously,
there
was
a
lot
of
project
messaging
things
that
are
going
on
driving
activities
around
events
like
Seth
days,
maybe
conferences
or
events
like
that-
maybe
content
generation
I
would
love
to
see
some
collaboration
on
performance
profiling,
maybe
some
white
papers
or
other
articles
that
can
get
written
that
aren't
necessarily
pushed
through
by
by
Red
Hat
associated
folk.
A
That
would
be
nice
to
do
that
then,
obviously
just
general
marketing
and
PR
AR
type
relations
as
a
side.
Note,
I'm
also
looking
at
a
arp
our
initiative
with
the
SEF
community.
That
would
be
handed
to
the
board
as
a
resource
right
now,
most
of
the
SEF
notices
that
go
out
to
the
press
or
analysts
relations
when
they
have
questions
about.
What's
going
on
in
the
world
of
SEF,
all
that's
handled
through
Red
Hat
and
as
a
community
guy
who's
very
focused
on
open
source
that
fuels.
That
feels
wrong
to
me
that
feels
awkward.
A
You
know
there's
times
when
do
sir
canonical
or
Intel
or
somebody's
going
to
do
something
really
interesting
with
SEF
that
doesn't
make
sense
for
red
hat.
To
talk
about
it,
I
mean,
maybe
we
could
say
at
a
boy
way
to
go,
but
it
to
me
it
feels
like
maybe
red
hat
would
would
some
people
be
perceived
as
trying
to
take
credit
as
others
work
and
I?
Definitely
don't
want
that
to
happen.
So
one
thing
we're
going
to
be
looking
at
in
the
near
future
is
having
staff
the
project.
Have
its
own
kind
of
press
agency?
A
Have
its
own
agency
to
represent
things
that
are
going
on
upstream
in
the
project
as
well
as
being
able
to
agnostic
alee
represent
all
things
that
people
are
doing
with
regards
to
SEF.
You
know
there
was
a
push
a
while
ago,
where
Suzy
launched
their
their
cloud
that
had
def
backed
portions
I
would
have
loved
to
make
a
lot
more
noise
about
that
and
really
helped
generate
some
buzz
similar
to
some
of
the
cool
stuff
that
canonical
Canyon
tin
use
to
do
with
juju
force.
F.
A
There's
a
lot
of
really
awesome
stuff
going
on
in
the
safe
community
that
we
can't
really
make
noise
about
as
red
hat
and
I
want
to
make
sure
that
those
things
are
being
surfaced
and
represented
appropriately
to
the
world
at
large,
and
this
would
be
something
that
the
ARP
our
initiative
will
will
come
a
little
bit
behind
some
of
this
other
governance
stuff,
but
eventually
it
will
be
handed
over
to
the
board,
do
manage
and
govern
and
oversee,
though
definitely
some
cool
stuff.
Coming
there.
A
A
They
would
make
sure
that
the
community
itself
continues
to
be
supported,
maybe
financially,
if
there
are
avenues
to
do
that,
but
obviously
reducing
barriers
to
enter
people
that
want
to
participate
and
make
sure
that
that
everyone
that
is
participating
within
the
community
has
what
they
need
and
is
able
to
get
what
they
need
done
and
then
advising
like
I
said
all
of
these
disparate
groups
that
would
have
representatives
on
the
board.
This
would
function
as
a
way
for
those
groups
to
bring
their
concerns
or
provide
feedbacks
and
recommendation
on
technical
direction
of
the
project.
A
A
Obviously,
if
other
people
feel
like
that's
not
a
good
a
good
fit,
let
me
know
I'm,
obviously
not
tied
to
being
king
of
the
castle
here.
I
just
figured
that
I'm
got
all
of
the
moving
pieces
in
my
hand,
currently
so
I.
I
would
start
it
off,
but
most
of
the
heavy
lifting
would
be
done
by
the
members.
There
will
be
three
seats
that
we're
looking
at
that
are
kind
of
permanently
assigned
to
groups,
so
the
user
committee
chair,
we've
already
talked
about,
would
be
representing
user
goals,
interests
and
needs.
The
project
lead.
A
Sage,
obviously,
would
have
a
voting
seat
on
the
board
as
representative
of
all
of
the
engineers
that
are
making
things
happen,
and
then
we
also
wanted
to
do
something
called
an
academic
liaison.
There
are
a
number
of
places
where
SEF
is
being
used
in
academia
or
academic
related
places,
and
sometimes
those
those
types
of
folks
or
organizations
have
very
different
goals
and
needs
out
of
SEF
I'm.
Looking
at
places
like
cern
that
has
some
different
approaches.
Some
of
the
national
laboratories
in
the
US
have
some
different
needs
and
goals
in
terms
of
what
they
use.
A
First,
that
for
and
I
figure
academically.
It
would
be
good
to
find
someone
who
could
wreck
represent
academic
interests
on
the
board
and
make
sure
that
those
voices
aren't
getting
drowned
out
by
those
with
commercial
interests
or
other
things.
So
this
would
be
someone
who
probably
would
be
from
one
of
the
one
of
the
National
Laboratories
or
someone
with
a
very
strong
academic
focus.
Maybe
you
would
be
a
professor
at
a
university
I,
don't
know,
but
I
want
to
make
sure
that
that
type
of
voice
doesn't
get
lost
in
the
cacophony
of
SEF
discussions.
A
Membership
is
probably
the
you
know:
membership
in
the
board
specifically,
is
probably
the
least
well
defined,
and
this
is
where
I
would
like
to
hear
thoughts
from
folks
on
what
does
it
mean
to
you
to
have
someone
sitting
on
the
ceph
board?
My
thought
is
that
they
should
bring
something
to
the
table
beyond
just
a
human
presence.
Obviously
they're
going
to
have
to
represent
a
group
of
some
sort
of
people,
whether
that's
representing
the
users
at
large,
whether
it's
voted
in
openstack
style,
whether
it's
you
know,
I
belong
to
a
large
company.
A
We
have
17
engineers
and
we
want
to
make
sure
we
have
a
voice
whatever
it
is,
I
feel
like
they
should
bring
more
to
the
more
to
the
table.
I,
don't
know
if
it's.
If
it's
you
know
a
monetary
contribution,
whether
its
personnel,
whether
it's
a
past
record
of
excellence,
I,
would
love
to
hear
thoughts.
Anyone
have
ideas
on
what
they
would
like
to
see
from
a
board
member.
What
does
it
mean
to
become
a
board?
Member
right?
Are
they?
A
Are
they
are
they
elected?
Are
they?
Are
they
chosen
because
they're
bringing
you
know,
hey
you
know?
Maybe
we
have
an
election
process
where
each
person
that
wants
to
be
a
part
of
the
board
lists
off
the
things
they
bring
to
the
project.
Like
I
have
a
budget
of
twenty
thousand
dollars
that
I'd
like
to
donate
to
the
project.
I
have
17
engineers
working
on
it.
A
I
personally
have
committed
18
patches
and
am
currently
maintaining
this
portion
of
the
dock,
like
that,
would
be
your
resume
to
get
elected
to
the
board
or
something
I
don't
have
anything
that
is
really
hammered
out.
I
wanted
to
leave
this
somewhat
nebulous
and
collect,
collect
feedback,
anyone,
ideas,
feedback,
complaints.
A
A
C
C
A
No
that's
fair
yeah
the
blueprint
this
was
one
of
the
late
coming
blueprints.
I
had
not
posted
this
during
the
blueprint
submission
process,
I
didn't
know
whether
we
were
going
to
have
space
for
it.
So
I
didn't
I,
didn't
push
it
up
until
later,
so
yeah
definitely
take
time
to
review
it.
That's
why
I
figured
I
was
walking
through
this
now
a
little
bit
to
give
people
a
taste,
give
the
the
flavor
in
the
context
around
the
the
words
now
you
know,
none
of
this
is
set
in
stone.
A
They're,
obviously,
will
be
portions
that
have
not
been
considered.
You
know,
but
the
that's
the
one
major
piece
that
I
would
love
feedback
on
more
than
more
than
any
of
the
rest
of
it.
I
want
to
know
what
it
means
that
to
have
a
board
member
right.
I
want
to
keep
this
board
artificially.
Small
I
don't
want
more
than
maybe
8
10
12
people
I
don't
want
a
2030
person
board.
You
know
those
when
it
gets
big
like
that
it
becomes
unwieldy
and
it's
hard
to
get
anything
done,
but.
C
A
Sorry,
my
idea
was
to
drop
this
all
in
the
SEF
etherpad,
so
auto-tuned
yep.
I
will
actually
make
three
separate
eat
with
ether
pads,
because
these
are
pretty
long,
extensive
documents
so
yeah
as
soon
as
we're
done
with
with
this
session
and
the
calamari
session
starts.
I
will
go
in
and
edit
the
infernal
asst
page
and
I'll
make
a
charter,
governance
and
Trademark
policy
ether
pads
so
that
people
can
poke
at
it
make
notes
whatnot
Brianna.
It's
a
good
idea,
see
going
through
this.
I
wanna
make
sure
there's
nothing
else
in
here.
A
That's
terribly
informative,
all
right!
So
no,
that's
that's
the
bulk
of
the
governance
details
and,
obviously
the
one
major
piece
that
I
want.
The
only
other
one
that
was
remaining
was
the
the
trademark
policy
and
if
you
look
at
the
trademark
doc,
there's
a
short
segment.
Well
short
is
a
relative
term,
in
this
case
I
guess
at
the
top.
That
is
it's
mostly
the
centos
trademark
policy,
mostly
just
a
rip
and
replace
with
with
SEF
for
centos
very
simple.
A
It's
not
very
explicit,
does
a
good
job
of
taking
the
major
yeast
cases
and
and
kind
of
says.
If
there's
anything
else,
ask
us
I
think
this
is
the
one
I'm
going
to
go
with
it's
much
more
lightweight
and
it's
not
terribly
difficult
for
someone
to
read
through
briefly
and
rock
below
it.
You
will
see
it
a
sections
marked
deprecated.
This
was
the
much
longer
version
that
we
started
with
it's
very
much
more
akin
to
the
Fedora
trademark
guidelines
and
it's
very
very
long.
It's
like
12
10,
12
pages,
long,
very
explicit.
A
A
lot
of
you
know
non-commercial
versus
business
versus
promotional
and
publications,
things
that
require
information,
rushes,
those
that
don't
unapproved
uses.
You
know
OEM
preloads
and
all
kinds
of
crazy
like
that.
This
one,
this
one
was
much
more
explicit,
but
I
think
it
takes
a
lot
longer
for
a
human
individual
to
go
through
and
actually
get
their
questions
answered.
So
I'd
rather
kind
of
go
lightweight,
but
obviously
I
welcome
feedback
in
either
direction.
C
A
That
was
deliberately
left
a
little
bit
vague,
because
there's
a
number
of
bit
for
bit
ways
that
you
can
distribute
SEF,
whether
it's
part
of
a
package
or
whether
they
did
for
a
bit
nĂ¥got
from
github
I.
Think
it's
more
just
if
this
is
the
same
thing
as
upstream
uses,
that's
kind
of
what
that
means.
Thank
you.
A
Eric
definitely
I
agree.
That
was
the
the
purpose
of
the
board
was
to
make
sure
that
you
didn't
have
three
people
from
Red
Hat.
That's
why
I
made
my
own
seat
a
non-voting
seat,
and
so
sage
would
be
pretty
much
the
only
Red
Hat
representative
on
the
board
for
governance,
his
input.
There
was
saying
that
make
sure
that
no
one
organization
has
a
monopoly
yeah.
A
Definitely-
and
that's
that's
why
I
was
thinking
that
board
members
would
be
more
representative
of
groups,
but
there'd
be
one
person
who
had
come
from
Susa
or
one
from
canonical
are
one
from
intel
or
hgst
or
or
whoever
any
other
group.
We
would
just
make
sure
that
they
represented
not
only
their
own
commercial
interests,
but
that
perhaps
we
started
aggregating
groups
within
but
yeah
yeah.
That's
the
thinking!
B
Have
a
question
in
the
meantime,
so
this
is
like
such
groups
like
that:
the
either
care
for
their
members
or
for
the
general
public.
That
is
when
the
goal
the
ultimate
goal
of
SEF
is
to
change.
The
way
we
use
storage
is
the
future
of
storage.
So
there
is
something
that
goes
beyond
the
technical
stuff,
more
philosophical,
so
the
arm
it
could
be
that
in
the
Charter
the
goal
is
to
make
sure
the
needs
of
everyone.
B
Governments,
civil
society,
I
I,
don't
know
if
we
say
that
in
English,
but
and
companies
of
course
are
being
taken
care
of
and
that
it's
not
just
an
organization,
a
group
that
takes
care
of
the
well-being
of
its
members.
It
goes
beyond
that
they
have.
They
feel
that
that
people
coming
to
the
self-organization
would
would
be
willing
to
consider
the
well-being
of
all
mankind.
But
it's
a
big
crown,
jewels
I.
Guess
to
save
like
that,
you
get
the
idea
yeah.
A
About
I'm,
sorry,
yeah
I
suppose
there
probably
are
multiple
people
with
Eric
I
was
seeing
if
Eric
Mariah
had
joined
us.
Yet
I
was
hoping
that
he
would
get
away.
Our
user
committee
chair.
A
But
clearly
not
Louie
would
it
be
helpful.
Maybe
you
could
talk
a
little
bit
about
the
origins
of
the
ceph
user
committee
so
that
it's
not
just
me
continuing
to
ramble
on
where
you
started
it,
where
it
has
come
since
under
eric's
guidance
and
and
a
bit
about
the
folks
involved
and
and
where
we
might
take
it
from
here.
I
didn't
want
to
dominate
this
with
my
governance.
Stuff
I
also
wanted
to
talk
about
what
was
existing
and
perhaps
surface
the
user
committee
of
it.
B
Yeah
so
originally
the
secular
community
was
born
because
there
was
calamari
being
proper
ettore.
That
was
the
turning
point
so
as
we
felt
the
need
we
users
of
seldom
to
organize
to
make
sure
we
can
have
free
software
to
do
what
we
need,
because
when
proprietary
software
shows
up
it
means
it
will
only
care
for
the
needs
of
selected
group
of
people.
So
it's
a
we,
that
is
the
number
of
filing
members
of
the
safe
user
committee,
wanted
to
have
a
solution
that
is
long-term
not
uncovered
by
things
like.
B
You
cannot
do
that
with
the
wassef.
You
cannot
expand,
you
cannot
modify
it,
so
that
was
the
the
origin
of
the
surf
user
committee.
Now
a
lot
has
happened
since
then,
and
when
a
committee,
when
a
group
is
created,
it's
mostly
useless
to
just
state
that
we
don't
want
that
or
that
we
want
that
we
want
it
to
actually
do
something,
and
so
we
started
to
organize
meetups.
B
That
is
just
go
over
all
the
Comets
and
see
who
is
actually
doing
some
work
and
listing
them,
and
it
was
also
interesting
because
then
organizations
showed
up
that
you
wouldn't
expect,
like
our
universities
or
nonprofit
organizations
such
as
the
Debian
project.
Some
people
contributed
on
behalf
of
nonprofit
organizations
and
also
governmental
organizations,
so
you
turned
out
to
be
something
we
we
could
do.
We
could
use
to
help
identify
where
we
belong
since
I've
been
acquired
by
Red
Hat.
That's
a
joke
because
I
have
been
hired.
Not
acquired.
B
I
should
refrain
from
doing
jokes
because
I'm
French,
so
that
does
not
work
so
well.
I
stopped
being
involved
in
the
sectional
committee,
because
I
was
no
longer
objective.
B
Of
course,
I
could
claim
that
I
could
still
be
objectives
and
we
present
the
safe
user
committee,
but
that's
not
really
true
when
you
get
paid
by
your
employer
as
time
passes,
you
care
more
for
the
needs
of
your
employer
and
less
for
the
needs
of
everyone.
So
that's
when
Eric
started
to
be
involved
and
well.
B
The
latest
I
things
he
needed
was
to
organize
in
this
southwest
of
France
a
meetup
where
surprisingly
high
number
of
people
meet
to
discuss
self
and
develop
new
software,
so
they
have
a
calamari
equivalent
that
kind
of
thing
and
we're
going
to
surf
user
committee.
That's
pretty
much!
All
there
is
at
the
moment,
which
is
not
ideal.
It
could
be
a
lot
more
because,
if
I
so
much
potential
for
everyone
but
I,
guess
it's
yet
to
to
be
done.
And
maybe
the
organization
that
you
later
Patrick
will
help
that
yeah.
A
Definitely
so
we
are
actually
running
way
over
and
my
alarm
didn't
go
off
for
the
the
session.
That's
the
hard
part
of
running
session
and
running
your
your
mouth,
so
I
do
want
to
stop
this
and
move
it
over
to
calamari.
But
hopefully
this
gives
you
enough
of
an
introduction
into
the
world
of
self-governance,
the
user
committee,
the
board
and
other
things
please
chew
on
this,
digest
it
and
give
me
feedback.