►
From YouTube: CNCF TOC Meeting - 2018-12-04
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
B
Thank
you
so
agenda
for
today.
For
me,
the
main
topic
would
again
be
to
work
categories.
We
can,
if
we
have
time
which
I
hope
you
do
we'll
have
a
quick
gun
for,
and
duration
review
for,
quality
and
S&T.
So,
let's,
let's
crack
on
next
slide.
Please
amazingly
Zuri
cube,
can
see
well
there
next
week.
Next
slide
start
booking
2019
next
slide.
B
A
Good
a
next
slide
Taylor,
yes,
so
we
have
45
candidates
for
the
governing
board.
Selected
seats
and
5
candidates
for
the
end-user
seats
were
currently
in
the
what
is
known
as
a
qualification
period,
where
governing
board
and
voting
folks
are
able
to
reach
out
to
the
candidates
to
ask
them
any
questions
or
essentially
do
anything
they
want
to
kind
of
vet
the
set
of
candidates
after
this
two-week
qualification
period
closes.
C
A
A
Literally
kind
of
baked
in
the
Charter
for
us
to
use
contorted
IRB,
so
it
is
just
ranking
45
people
which
it
is
a
little
bit
painful,
but
the
first
time
we
did.
This
I
think
we
had
a
good,
20
or
30
set
of
set
of
folks
last
last
I
recall.
So
it
does
work
that
just
takes
more
time
on
the
person
ranking
folks,
I
I
have.
A
Board
for
the
governing
board
selected
seats
and
then
the
end-user
board
votes
on
the
end
user
seats
right
yeah,
the
other
thing
went
in
you,
don't
actually
have
to
rank
all
45.
You
could
basically,
just
you
know,
pick
your
let's
say
six
for
the
governing
board
and
then
just
leave
the
rest
ranked
last
essentially,
but
it's
up
to
you
to
up
to
you
in
terms
of
how
you
want
to
vote
and
do
it
no.
C
A
B
So
we're
in
Catherine's
brain
so
sorry,
so
thank
you
very
much
for
the
feedback
on
categories
and
SIG's.
There's
been
a
bit
of
discussions
since
in
the
last
two
weeks,
or
so
from
people
on
the
document,
which
is
the
right
place
at
the
moment
to
discuss
it.
I
particularly
want
to
thank
the
folks
around
the
same
proto
working
group,
who
have
been
helping
out
by
proposing
st.
as
a
kind
of
concrete
example
model
for
what
a
saint
should
do.
B
B
B
B
So
here
you
can
see
a
mission
statement
which
is
quite
general
essentially
asserts
that
there's
more
work
to
be
done
in
open-source
security,
especially
with
cloud
native,
and
then
has
a
kind
of
vision
down
there
near
the
bottom
of
what
quinton
is
showing
you
here,
scroll
down
a
bit,
please
Quentin
and
then
is
that
he
may
not
be
able
to
speak
as
he's
a
Barcelona.
Just
in
the
you
on
the
call
today,
just
in
comment.
B
Okay,
so
you
can
see
here,
there's
a
need
for
new
projects,
or
one
of
the
things
that
they
wanted
to
do
is
to
visit
new
projects,
and
you
can
see
responsibilities.
And
if
you
go
down
just
a
tiny
bit
more
Quintin,
you
can
see
deliverables
so
opening
it
up
to
the
floor.
Who
thinks
this
is
a
plausible
set
of
deliverables
for
AC
that
are
presented
to
the
TOC,
which
is
the
voting
body
meeting
on
these
call
and
get.
C
B
B
B
D
Hadn't
caught
up
with
the
recent
changes
in
the
document,
so
I'm
still
reading
through
the
mission
statement
and
such
okay,
the
deliverables,
you
know,
I-
think
it's
really
important
to
have
deliberate,
deliberate,
that
users
will
understand
and
that
are
broadly
applicable
to
both
users
and
to
the
projects
I.
Don't
just
reading
the
deliverables
alone,
it's
not
clear
that
they
do
so
I'm
reading
through
the
rest.
In.
C
Brian
I
see
you
made
a
comment
there
about.
The
server
lists
were
quite
paper
being
too
long,
just
some
other
feedback
there.
So
so
I
was
involved
in
the
storage
white
paper
and
we
didn't
you
know,
target
a
particular
size.
We
targeted
a
goal
of
explaining
a
particular
area
and
it
turned
out
to
be
about
the
same
size
as
the
service.
One
I
personally
found
this
on
this
one
very
useful,
well,
I
think
if
it
had
been
significantly
shorter,
it
would
have
been
significantly
less
useful,
and
the
same
was
my
experience
for
this
storage.
C
D
Think
it's
that's
one
issue
and
it
was
specifically
with
that
document.
I
haven't
read
the
storage
working
group.
Why
paper
I
did
review
and
comment
on
the
Surrealists
working
group
white
paper
I
think
it
could
easily
have
been
multiple,
separate
documents
that
were
more
focused
and
more
targeted.
It
was
really
really
broad
which
I
agree
has
value
to
some
people.
I,
don't
I
haven't
really
seen
that
much
discussion
of
it
from
people
outside
the
set
of
people
who
are
already
deeply
involved
with
CAF,
so
I,
don't
know
what
kind
of
impact
it
had
more
broadly.
B
So
one
of
the
audiences
that
we
could
state
more
clearly
is
it's
implied
in
in
all
the
stuff.
Around
education
and
I
think
that
we
don't
yet
have
a
good
joined
up
story
for
educational
material
coming
out
of
the
CN
CF,
which
I
think
is
a
mission
fail.
I.
Think
that
having
a
more
focused
attention
on
each
category
through
the
SIG's
could
help
help
with
that
and
maybe
provide
a
focus
for
CN
CF
staff
to
provide
resources
to
help
to
solve
specific
issues.
D
You
know
I
think
the
cloud
native
landscape
is
is
big
and
it
is
complex
and
if
we
can
help
users
understand
the
impact
and
help
them
understand
how
what
the
pieces
are
and
how
they
fit
together
and
how
it
will
improve
things
for
them,
but
also
what
the
risks
are
and
how
they
can
mitigate
those
risks.
You
know
it's
we're.
Gonna
need
to
be
able
to
distill
it
down
into
something
simpler,
and
this
is
you
know,
working
groups.
D
Don't
need
to
solve
this
entire
problem
independently
or
by
themselves,
but
you
know
I
think
my
other
concerns
with
working
groups
are
more.
You
know,
one
concern
is
that
they
need
to
provide
value
and
we
need
to
understand
what
that
value
is,
but
also
we
need
to
just
make
sure
that
we
organizationally
understand
how
to
run
them
in
an
effective
way
right.
So.
B
F
This
is
Matt
Farina,
real,
quick.
You
know
to
jump
in
to
take
this
from
kind
of
the
kubernetes
perspective.
What
we've
done
over
there
is
we'll
have
like
an
organizational
unit
and
then
it'll
have
well
sub
projects.
I
think
in
the
document
Quinton
might
have
brought
this
up,
and
so
in
a
sub
project
you
might
have
you
know
an
area
which
is
what
a
sig
owns
and
then
a
sub
project
is
a
concrete
thing,
so
maybe
one
sub
project
is
going
and
producing
certain
reports
around
target
audiences.
F
Another
sub
project
is
about
educating
project,
maintainer,
zhan
security
and
helping
them
audit
it
and
get
to
where
they're
going
and
you
might
have
different
sub
projects,
because
then,
if
you
need
to
know
okay
I'm
going
to
this
kind
of
thing
who
owns
that,
what
area
do
I
go?
I
talked
to
you
know:
you've
got
one
thing,
but
that
one
thing
may
have
more
than
one
area
of
responsibility
in
kubernetes
organizes
those
into
sub
projects.
Not
every
cig
has
them,
but
many
of
them
do
otherwise.
Not
you
organize
and
find
things
yeah.
C
I
think
I
do
share
your
concerns,
Camille
and
I,
and
I
think
that
the
model
that
matt
suggested
is
is
a
reasonable
way
of
dealing
with
it.
The
alternative
is
to
have
you
know
two
separate
sets
of
organizations,
the
execution
branch
and,
be
you
know,
governance
branch
if
you
like
and
and
but
then,
if
they
get
disconnected,
they
don't
work
very
well
either.
So
so
having
them
fundamentally
connected
is
a
good
idea.
I
think
and,
and
the
sub-project
model
does,
that
in.
F
Kubernetes
see
gaps.
We
actually
discussed
this
at
length
because
we
have
a
bunch
of
high-level
things,
we've
done
with
helping
facilitate
the
community
and
get
people
thinking
about
app
development
topics
in
general
and
at
the
same
time
dealing
things
like
the
workloads
API
in
kubernetes,
and
we
talked
about
separating
those
and
what
it
would
mean
fundamentally,
and
we
one
of
the
things
that
hit
us
is.
We
want
the
practitioners
talking
with
the
people.
F
Who've
got
the
problems
and
are
trying
to
solve
it,
so
everybody
can
see
where
everyone
else
is
coming
from,
and
it's
kind
of
like
that
thing
of.
If
you
separate
theory
from
execution,
where
do
those
paths
go?
Can
the
theory
and
can
the
teaching
really
solve
the
problems
if
they're
disconnected
from
the
execution
and
for
us
we
chose?
We
didn't
want
to
go
that
route
because
we
thought
it
would
lead
to
problems.
Are.
G
F
G
Well
and
I'm,
part
of
the
kubernetes
storage,
sig
and
I
know
that
I
think
it's
just
kind
of
everyone
in
there
and
we
I
wouldn't
say
we
have
a
huge
amount
of
customer
input.
Always
we
we
try
to
consider
that
is
an
angle
but
I
don't
know
how
to
get
all
equal
voices,
which
I
think
is
what
you're
proposing
and
information
to
everyone.
So
I,
don't.
F
In
fact,
over
on
helm,
one
of
the
things
we
did
was
we
said
who
are
our
audiences
and
then
we
stack
ranked
them,
and
then
we
had
information
on
them
because
we
wanted
to
say
you
know:
where
does
an
application
developer
come
differently
from
a
tooling
developer,
come
differently
from
a
package
distributor
because
we
understand
you
know
we
wanted
to
have
roles
and
then
some
details
around
profiles
around
those
roles.
We
could
talk
to
them
because
we
just
say
developers
and
end-users
really,
who
are
those
and
what
are
their
needs?
F
H
H
F
So
safe,
actually
I
think
brings
up
a
really
interesting
point
when
we
talk
about
space
and
bringing
it
up,
because
if
I
go,
look
at
the
safe
working
group
objective,
it
says
gear
access
for
everyone.
Safe
working
group
will
explore
secure
access
policy,
control
and
safety
for
operators,
administrators
developers
and
end
users
across
the
cloud
native
ecosystem.
But
if
I
look
at
security
right,
what
about
signing
your
releases
and
then
distributing
them
and
having
your
signature
be
done
differently?
F
That's
a
security
practice
right,
but
does
that
fit
in
there
safe
and
in
the
safe
document
here,
I
see
safe,
but
then
I
see.
Security
is
a
general
thing
and
I
get
that
there's
a
bunch
of
things
outside
of
that
small
objective
of
safe
and
so
I
can't.
Is
it
just
meant
to
be
a
subset
of
security
or
security
in
general
right
so.
B
B
To
do,
and
so
we
can
actually
ask
questions
like
the
one
Camille
focused
about
commingling,
of
different
granularities
at
work
and
responsibilities,
for
instance.
So
let's
not
worry
about
that
last
question
team
too
much
right
now,
I
think
you
know,
one
of
the
questions
is:
can
we
even
come
up
with
a
model?
That's
able
to
execute
useful
work
and
I?
Think
the
other
question
is:
what
is
the
dividing
line
between
what
EOC
does
as
a
voting
group
and
what
happens
in
the
sake?
B
I
I
That
that
I
have
are
you
know
in
this
space
and
I
think
it's.
The
work
example
is
great
and
we
just
need
to
not
fall
into
the
trap
of
only
looking
at
the
work
example
right
we're
trying
to
use
the
work
example
to
motivate
the
more
abstract
ideas
you
know
the,
but
the
questions
that
I
have
are:
what
are
the
established
practices
in
this
space?
That
everyone
agrees
are
kind
of
a
the
the
the
lowest
common
denominator,
and
there
may
not
be
any
I
mean
it
some
of
these
spaces
there
may
be.
I
The
approaches
are
so
radically
different
if
there
aren't
any.
What
are
the
kind
of
common
approaches?
What
are
the
emerging
things?
What
are
the
things
that
that
people
are
experimenting
with
and
there
I
would
expect
there
to
be
a
couple
of
different
approaches
and
a
couple
of
different
ideas,
I
I
think
when
we
established
the
landscape,
it
needs
to
not
be,
as
certainly
not
as
a
set
of
icons
on
an
unreadable
a
chart,
but
I
think
we
want
to
establish
the
landscape
with
a
narrative
that
establish
that
is
that
there
are
probably
different.
I
There
are
different
parallel
paths
or
different
ideas
that
people
are
experimenting
with.
There
are
things
that
are
more
emerging.
There
are
things
that
are
more
established
and
I
think
that
we
we
might
want
to
phrase
those
as
questions
that
we
want
the
cig
to
to
ruminate
on
and
I
can
try
to
be
more
specific
here
on
the
dock
I,
as
opposed
to
I.
Think
we
we
want
to
when
we
establish
the
landscape,
we
I
think
we
want
to
prevent
the
cig
from
becoming
becoming
a
true
a
kind
of
a
governing
body.
I
I
think
this
were
the
storage
said
the
storage
working
group
ran
into
trouble.
Those
were
the
swords
were
correct
me
if
you
disagree,
but
I
think
where
they
felt
like
they've,
got
to
adjudicate
a
single
path
and
we
don't
actually
want
a
single
path.
We
want
to
know
what
the
paths
are
that
are
out
there.
C
Does
that
make
sense,
I
agree
entirely
and
and
I
don't
know
if
we're
of
it,
but
we
we
kind
of
reformulated
the
storage
working
group
specifically
around
that
idea
that
that
was
the
crux
of
the
matter
and
and
I
think
the
white
paper
that
came
out
of
the
second
phase
of
that
seems
to
be
in
well
received
very
well
received,
because
it's
precisely
that
Eisley
wall.
Sorry,
it's
precisely
not
dictating
a
one.
C
B
B
Okay,
so
we've
just
come
to
some
time.
Does
anyone
else
have
a
major
thing?
They
want
to
say
right
now
about
this
document.
I
think
we
made
it
move
this
for
a
tiny
bit
today,
I
really
like
to
think
about
how
we
can
take
the
next
steps
in
refining
what
we
have
here
and
turning
it
into
something.
A
bit
more.
You
know
compactly
written
and
expressed
that
we
can
start
to.
You
know
really
start
to
kind
of
turn
the
vote
on
maybe
a
tear
apart
and
sighs.
C
I
B
So
only
men,
you
know
about
maybe
leaning
out
for
something
cool
right,
so
Chris
Taylor.
Please
pick
new
things.
The
next
topic,
which
I
believe
to
be
the
core
DNS
graduation
discussion
and
Quinton.
You
black
go
this
green
great
Taylor.
Would
you
mind
projecting
in
thank
you,
okay,
Chris.
What's
the
process
you.
I
K
So
yeah
thank
you
good
morning.
Everyone,
my
name,
is
Francois
trio
and
I
am
one
of
the
maintenance
of
the
accordion
s
project,
so
Kody
and
STI
I.
Guess
it's
a
time
of
the
annual
review
just
to
recall
that
we
we
did
the
first
applying
as
inception
project
in
March
2017
and
then
almost
one
year
later
it
was
the
first
annual
review
where
we
applied
for
incubation
February
2018.
K
So
now
is
under
review,
but
on
same
time,
application
for
a
graduated
project,
cody,
honest
I,
just
remind
a
little.
It's
is
a
like
DNS
server
in
Ingo
language.
The
main
point
is:
it
is
written
in
plugins
in
our
CTO
plugins
that
make
it
very
easy
for
any
user
to
adapt
for
whatever
you
want,
either
by
reusing
existing
plugins
either
by
writing
your
own.
So
what
we
did
during
these
years,
I
mean
since
March
2017
that
we
have.
We
have
a
bunch
of
plugins
available
and
we
tried
last
year
ready
to
start.
K
K
The
main
point
of
this
year
is
adoption
of
core
DNS,
so
here
I
show
25
to
big
position.
You
serve
I.
Guess
there
is
much
more
25
is
because
we
did
a
survey
thanks
to
CN
CF
to
know
who
is
using
core
DNS
and
then
some
people,
without
yes,
I'm,
okay,
to
to
show
up
in
your
adopted
list.
What
we
did
this
year
is
okay,
follow.
It
is
more
ensure
that
core
DNS
is
reliable,
is
perform
as
expected
and
and
has
a
right
to
nage.
K
So
it's
more
majority
of
CO
DNS
on
one
side
and
the
other
side
is
anti
great
core
DNS
as
a
component
of
Germany
T's.
That
was
already
in
the
plan
when
we
presented
for
incubation
beginning
of
this
year.
So
now
it
is
done
so
I'm
happy
to
copy
past
this
morning.
The
tweet
that
happened
yesterday
evening
that
showed
the
release
of
humanity
is
114
that
that
what
is
yesterday
and
that
Seco
DNS
is
a
default.
Dns
plugin
it.
K
K
Can
we
go
to
next
slide?
Thank
you,
Chris,
so
coordinates.
Community
I,
don't
know
how
to
sure
I
know
that
each
project
tried
to
show
here
I
to
the
numbers
we
showed
up
a
beginning
of
this
year
and
where
we
are
right
now,
after
one
a
little
less
than
one
year.
So
the
contributor,
for
example,
went
from
42
to
112.
K
The
the
more
amazing
thing
for
me
is
the
docker
pulled
the
10
million
dollar
pools
from
our
dock
accordion
s,
which
does
not
include
the
Cuban
eighties
pool
for
Korean
s,
because
in
that
case
we
we
asked
the
image
of
coordinates
in
the
GCR
at
I/o,
so
it's
only
for
the
core
dns
repository
I.
What
I
wanted
to
show
here
is
maybe,
on
the
this
graphic
on
the
on
the
bottom,
is
what
happened
for
the
adoption
by
the
developers
of
core
DNS.
K
So
you
see
these
two
lines,
so
one
is
the
stars,
but
the
second
one
that
grow
up
the
same
way
and
you
can
see
the
the
increase
from
inception.
Incubation
graduation
is
the
fog
of
the
project.
So
that
means
you
have
now
for
450
Fox
of
CO
DNS
means
people
that
try
to
understand,
try
to
maybe
make
a
little
change
or
just
to
grow.
Some
understand
what
happened
inside
and
that's
a
huge
achievement
also.
K
K
K
K
We
have
realized
I
think
last,
like
last
year,
twelve
release.
So
that
means
a
quite
often
I
rate
of
release.
The
rate
of
peer
merch
is
a
little
lower
or
little
is
STD.
I
did
not
work
because
we
focused
more
on
the
radio
bility
II
on
the
performance
than
to
I,
don't
add
and
add
features
so
one
one
thinks
of
globally.
This
peer
has
been
approved
by
Jonathan
bull,
that
is
our
sponsor
for
COC,
the
sponsor
of
Cody,
Ennis
I,
don't
know
I
guess
now.
K
C
K
C
K
J
J
K
K
K
We
took
a
lot
of
how
for
this
graduation
criteria,
we
had
to
write
down
our
governance,
and
that
was
a
kind
of
process
where
we
had
a
lot
of
talk,
the
the
X
for
the
governance.
We
want
it
to
be
open
for
maintenance.
So
that's
why
we
have
an
important
number
of
maintenance.
The
one
that
are
more
active
I
think
are
the
six
six
or
seven
first
one
in
the
list.
If
you
look
at
the
six
or
seven
first
contribute
or
in
code
units.
A
B
B
J
A
G
L
In
here,
okay,
thank
you.
Well,
hey.
My
name
is
Eduardo
Silva
I'm
part
of
a
fluentd
team.
Since
a
lot
of
years
and
the
goal
of
this,
a
graduation
presentation
is
trying
to
demonstrate
our
current
status
of
the
project.
Since
we
join
an
incubation
on
November
2016
two
years
ago.
So
I
know
one
day
soon
be
is
a
real
production,
great
luggage
solution,
and
it's
been
used
a
mostly
by
major
cloud
providers
and
may
your
distribution,
a
complexity
to
the
communities
or
also
stand-alones
solution
that
are
not
containerized
by
like
Google,
Microsoft
and
Red
Hat.
L
In
terms
of
growth,
we
have
seen
a
huge
growth
in
the
last
year's
and,
for
example,
in
the
last
ten
months
we
have
seen
around
35
million
docker
pulls
from
our
official
registry,
and
since
then-
and
this
has
been
growing
a
lot
in
not
just
say
how
many-
how
many
people
is
choosing
to
indie
with
kubernetes
and
Sano's
services,
but
also
from
a
community
and
developer
perspective.
Next
slide,
please,
okay
in
the
last
year,
so
the
first
year
after
inception
in
at
cook
on
Lex,
was
one
year
ago
in
the
US
we
released.
L
It
flew
in
d1,
dot,
o
and
since
then
we
had
don't
exceed
C
two
releases
and
the
last
release
that
we
have
available.
So
one
three
that
one
that
was
available
since
like
seven
days
ago,
and
also
we
have
seen
some
kind
of
our
nails
and
a
knowledge
on
our
github
repository.
Currently,
we
have
like
seven
thousand
github
stars
next
slide.
Please
a
when
important
things
to
understand
about
will
be
itself
that
a
it
behaves
a
bit
different
than
in
the
way
that
works
with
other
projects
with
a
with
the
developers
on
it
ecosystem.
L
So
indie
itself
is
like
a
serious
codebase,
but
most
of
the
major
futures
and
extensions
that
they
are
available
are
days
of
plugins
and
plugins
can
be
created
by
anyone
or
any
company.
When
we
join
it.
An
incubation
like
two
years
ago,
we
had
like
600
plugins
and
no
way
they
would
have
more
than
800
plugins,
which
has
been
updated
in
the
last
year.
So
we
are
quite
a
mess,
because
you
will
understand
that
we,
as
maintainer
maybe
will
focus
in
the
fluidity
core
base
and
also
on
no
more
than
20
plugins.
L
So
you
can
see
that
are
many
companies
contributing
back
in
their
own
way
and
since
women
D,
of
course,
is
like
I'm
based
on
a
group
ecosystem,
a
this
plugins
I'll
publish
it
in
the
in
the
ruby
gems
registry
and
everybody
can
get
them
and
take
advantage
of
that,
in
addition
to
the
plug-in
as
an
ecosystem,
and
we
also
provide
like
language
SDKs.
So,
for
example,
if
you're
writing
your
application
goal,
no
tears
or
any
kind
of
language,
you
can
ship.
L
Your
looks
directly
from
your
own
code
to
fluency,
so
20
can
also
behave
not
just
they
can
look
for
weather,
but
also
as
an
aggregator,
and
we
have
seen
most
of
these
in
this
model.
What
people
ship
looks
from
applications.
Windy
is
mostly
outside
of
the
communities
world,
and
we
get
a
lot
of
traction
with
that.
People
write
an
application
in
Java
by
using
that
in
Python
and
Kola
next
slide.
L
We
maintain
a
also
efficient
playing
sports
plant,
the
elasticsearch
integration
for
nodejs
application,
which
is
a
cost
something
and
also
we
did
a
better
integration
with
primitives.
So
in
general
we
have
tried
to
make
a
increase
for
the
whole
adoption
in
work
better
with
the
community
in
terms
of
create
products,
more
extensions
for
it,
and
also
we
focus
a
lot
of
how
to
integrate
better
with
the
enterprise
and
we're
quite
happy.
The
whole
fluently
has
been
growing
in
the
in
the
last
time
and
I
think
so.
C
Yeah
I
had
I
had
one
with
Quinton
here
around
or
800
plugins.
On
the
one
hand,
it
sounds
very
impressive.
From
the
other
hand,
it
maybe
makes
me
wonder
how
specific
these
are,
rather
than
being
more
general
I
was
curious.
You
know
what
does
that
landscape
of
800
plugins
look
like
as
far
as
I
understand.
There
are
producer
plug-ins
and
consumer
plugins.
Is
that
true
yeah.
L
Actually,
we
have
more
categories.
One
of
them
is,
let
me
call
it
input
what
you
say:
consumer
we
have
filter
plugins.
We
have
parser
plot
plugins,
buffering,
plugins
and
output
plugins,
so
all
about
what
you
need
plus
sometimes-
and
you
have
a
make-
the
right
plugins
to
consume
the
Bay
Area.
But
you
need
to
write
your
specific
filter
to
parse
on
so
sorry,
it's
the
secret
builder
to
apply
some
kind
of
threshold
or
I,
don't
know
obfuscate.
L
L
For
that
in
the
code
base,
we
provide
a
flexible
ecosystem
with
so
people
can
create
their
own
solution
and
the
way
to
do
it
is
using
like
the
ruby
gem
ecosystems
again
what
the
code
can
be
Ruby
or
C,
and
then
people
often
call
those
plugins
easily,
because
also
in
the
fluency
distribution,
we
provide
our
own
tooling
to
get
those
right.
A
plugins
for
the
right
version
that
fluently
is
running
okay,.
A
B
Just
get
a
couple
of
snapshots
for
the
two
projects
and
just
attach
them
to
a
post,
xxx
yep
yep,
the
dev
stats
is
really
good
Chris
good
job
is,
it
is
still
quite
it's
quite
a
kind
of
information.