►
From YouTube: OpenFeature - Project meeting, October 27th, 2022
Description
meeting notes: https://docs.google.com/document/d/1pp6t2giTcdEdVAri_2B1Z6Mv8mHhvtZT1AmkPV9K7xQ/
OpenFeature website: https://open-feature.github.io/
B
Yeah
yeah
I
mean
I,
think
we're
just
waiting
for
Mike
and
Todd
they're
gonna
connect
from
somewhere
but
yeah.
We
should
have
quite
a
few
people.
B
Yeah,
so
the
I
think
the
the
booth
area
hasn't
opened
yeah.
It
only
opens
in
half
an
hour.
That's
why
it's
still
nice
and
quiet.
B
D
D
A
D
D
Just
kind
of
an
update
of
what's
happened
so
far
and
keep
going
on
kind
of
what
we
did
in
preparation
for
it
as
well.
So
let
me
see
here:
do
we
have
a
scribe
this
time?
Is
there
any
volunteers?
I'll
subscribe,
perfect.
C
D
Perfect,
if
you
don't
mind
that
would
be
that'd,
be
great,
yep
cool,
all
right
and
then
the
meeting
notes
are
already
linked
in
the
chat.
If
anyone
has
any
items,
please
feel
free
to
add
them.
I'm
gonna
go
ahead
and
get
started
right
and
if
there's
new
coming,
let's
see
there
are
a
couple,
if
you
don't
mind
introducing
yourself
real
quick,
that
would
be
great.
F
Yeah,
hey,
my
name
is
Mark
Phelps,
the
founder
of
flipped,
which
is
an
open
source,
self-hosted
feature
flag
solution
and
I
actually
went
I've
been
to
a
meeting
before,
but
it
was
a
long
time
ago.
It
was
like
one
of
the
first
meetings
you
guys
did
and
I'm
looking
into
creating
a
provider
for
for
flipped,
and
this
is
my
colleague,
George
I'll
pass
the
mic
too.
G
Oh
yes,
my
name
is
George
I
work
with
Mark
I've
just
started
to
join
Mark.
The
building
flip
now
for
many
years,
but
he's
just
he's,
got
the
capacity
to
bring
more
people
on
board
so
I'm.
The
first
first.
B
D
Cool
all
right,
let's
check
the
schedule
yeah,
it
looks
like
it
rolls
for
the
next
meeting.
So
if
there's
any
any
volunteers
for
that,
we
can
go
ahead
and
knock
that
out
real
quick,
it's
mainly
scribe
Duty.
So
if
you
can
be
here
in
two
weeks-
and
you
don't
mind
taking
notes
for
an
hour-
please
let
us
know
Justin
Justin
will
do
it.
Thank
you
very
much
all
right
and
then
first
up
it
looks
like
Eloise.
A
Yeah
I
had
some
hacked
points
edit.
Let
me
just
quickly
check
out,
because
I
had
two
which
ones
I
wanted.
A
With
yes
up
level
of
the
community
repositories,
so
some
of
you
might
have
already
seen
it
I
started
to
do
some
commits.
Basically
what
I'm
doing
is
I'm
restructuring
a
lot
of
the
community
repository
right
now
to
get
all
the
world
open,
telemet
with
us.
So
this
is
really
not
about
Reinventing
things,
but
restructuring
I.
Think
open
television
does
a
great
job
in
doing
it
like
also
outlining
what
maintainers
are
what
the
roles
are,
how
to
reach
out
to
the
individual
SDK
implementation
groups.
A
It
is
still
in
an
early
stage,
but
I'll
reach
out
to
several
of
you
help
me,
especially
in
the
sdks.
What
we
haven't
maintained
is
through
the
technical
committee.
Sponsors
are
so
I.
I
would
like
to
get
this
up
to
a
level
where
I
think
for
new
people
joining
in
putting
like
super
simple,
and
we
have
the
rough
version.
A
Also
on
the
community
side,
it's
about
like
the
governance
board.
I
want
to
get
some
of
the
documents
which
we
had
for
quite
a
while
into
a
more
stable
State
like
they
were
proportions
on
the
charter,
but
they
were
never
agreed
upon
Believe
by
the
maintenance.
In
an
early
bath
stage,
I
was
about
to
get
all
of
these
things
moving
right
now,
so
they
adjusted
everyone's
aware.
A
So
this
is
going
to
happen
over
the
next
couple
of
weeks,
especially
if
you're
responsible
for
one
of
the
sdks
I
would
appreciate
it.
We
can
support
some
of
the
information
alerted
to
the
dogs
where
to
find
augmentation
used
to
maintain
around
it
and
observance
is
supporting
it.
A
Next
Step
that
will
be
to
get
community,
especially
the
governance
board,
into
working
mode,
but
obviously
the
connectivity
is
the
entire
governance
board.
What
does
working
mode
mean
getting
into
regular
meetings,
and
also
we
need
to
get
into
an
official
voting
cycle
and
ensure
that
everybody
who
wants
to
be
represented
is
going
to
be
represented,
are
very
much
like
the
approach
that
open
Telemetry
has
taken
that
you.
A
They
launched
their
bootstrap
governing
boards,
which
stayed
in
place
for
two
years,
and
then
they
brought
on
new
people,
and
then
the
people
are
rotating
out.
The
idea
was
that
they
don't
immediately
roadside
out
every
one
to
have
some
continuity
and
the
new
people
are
coming
in,
so
it
was
expected.
Er
will
I.
Will
propose
a
similar
approach
that
to
toward
open
Telemetry
has
used
as
well
yeah
and
if
you
I,
think,
depending
on
today's
time,
I
can
show
you
the
more
details,
but
just
to
be
aware,
we
are
moving
in
that
direction.
A
Getting
the
charges
set
up
and
everything,
so
the
things
are
working
out.
Also
I
can
briefly
mentioned
that
Kevin
from
kids
left
the
governance
board
right
now
and
Alex
is
going
to
challenge,
which
we
are
very
delighted
about
that
Alexander
board
and
obviously
we
also
want
to
achieve
a
fair
balance
of
everybody
participating,
especially
in
the
bootstrap
governing
governance
board.
A
So
if
there
are
the
way
we
are
handling
it
for
the
time
being,
as
there
is
no
official
process
yet
is
that
you
can
submit
the
pr
that
you
want
to
join
and
then
we
had
a
governance
board
member
as
simply
approving
the
fcr.
For
the
time
being,
we
want
to
kept
it
at
some
point,
also
Mike
and
I
talk.
We
are
very
of
the
fact
that,
right
now
there
are
two
dynasties
employees,
part
of
the
governance
board,
also
yeah
your
concerns.
A
If
you
think
that
you
have
any
issues,
this
is
that
Mike
and
I
will
consolidate
on
governance
board
profits.
Just
let
us
development,
it's
just
that
this
happens
historically,
but
if
you
don't
feel
comfortable,
just
feel
free
to
speak
up
or
it
doesn't
give
any
problems.
C
Which,
which
repo
is
a.
A
That
built
their
roads,
like
literally
underneath
at
a
conference
school
here
just
a
second.
A
And
as
we're
here,
I'm
also
using
the
Community,
if
you
want
to
share
how
they
actually
handle
the
voting
process
on
the
Covenant
Sports.
A
Okay,
let
me
put
this
here
so
the
way
you
open,
sometimes
we
did
this
and
I
think
that
might
be
pretty
viable
for
us
as
well.
So
initially
you
had
like
five
people
on
the
bootstrapping
governance
board
and
they
have
these
two
election
cohorts,
so
they
were
voting
for
two
people
with
a
two-year
time
and
two
people
with
a
one-year
term
what
happened
the
next
year?
Obviously
that
two-year
term
people
stayed
on
the
board.
A
The
two
people
was
the
one
year
term,
rotate
it
out,
and
then
the
year
after
the
initial
governance
board,
the
bootstrap
governance
board
rotated
out
entirely.
Obviously
they
were
up
for
re-election.
This
actually
means
that
initially,
the
number
of
total
governance
board
members
will
be
going
up
slightly,
but
I
think
that
should
be
fine,
especially
if
more
companies
are
joining
here
and
I.
Think
I
would
just
use
exactly
the
same
approach
there.
Unless
anybody
has
any
concerns
it
works
for
opens
alignment
to
be
well,
I
think
it
can
work
for
us.
A
Pretty
much
the
same
way,
so
I'll
throw
this
into
a
PR
rather
sooner
than
later
and
donate.
If
you
have
any
comments
right
now,
please
also
please
share
them
right
here.
A
F
E
I
have
a
I
have
a
point
or
a
question
on
that
topic.
I
was
just
speaking
to
one
of
the
open
Telemetry
community
members
last
night
and
they
were
saying
they're
making
changes
to
the
way
they
elect
their
technical
steering
committee
I'm
thinking
it
might
be
worth
our
time
right
now,
if
you're
already
going
to
make
these
changes
to
kind
of
also
draw
also
lay
out
how
we're
going
to
do
the
TSC
nominations
or
elections.
E
The
way
that
it
sounds
like
hotel
is
going,
which
I
think
could
expedite
things
and
make
things
simpler,
is
that
the
governing
the
governing
board
just
nominates
the
TSC
or
they
vote
for
them
within
the
governing
board.
So
I'm
not
sure
if
that
could
be
a
way
to
simplify
things,
I
think
they
have
like
a
limited
term,
but
maybe
that
would
be
easier
because
it
would
reduce
the
amount
of
voting
that
we
have
to
do
just
a
proposal.
A
D
Okay
cool
looks
like
the
next
item
was
open
picture
incubation
I'm,
not
sure
who
added
that,
but
if
they
don't
mind
collaborating
please
yeah.
A
A
I
know
it's
like
a
very,
very
lengthy
process,
and
if
we
want
to
achieve
this
by
kubecon
Europe
next
year
with
I
think
we
should
I
would
kick
off
the
process
pretty
much
right
away
so
having
the
application.
We
are
almost
there
the
only
criteria
which
we're
not
fulfilling
right
now,
as
we
implementations
in
production
I,
think
we
can
reach
this
world.
Actually
the
application
process
will
be
filled.
Obviously
we
have
Justin
here
with
eBay
and
with
some
of
the
others
who
are
actively
adopting
it.
A
I
think
it's
fine,
but
this
process
for
other
projects
that
I
was
working
on
took
about
a
year
and
there's
usually
also
lockdown
periods
before
Cube
counts
for
the
TUC.
That's
what
I
think
right
now
I
would
actually
go
for
incubation
by
the
way
I'm
also
trying
to
meet
with
Chris,
because
technically,
if
you
get
the
governance
and
everything
right
and
given
the
number
of
contributors
we
have,
we
could,
in
theory,
move
directly
to
graduation
as
well,
which
would
be
kind
of
uncommon,
but
I
at
least
want
to
get
the
incubation
started.
A
A
Yeah
but
but
we
might
also
want
to
do
along
the
way,
which
also
helped
with
sandbox,
which
was
some
unofficial
advice,
would
do
a
PR,
together
with
the
1.0
release
amongst
this
group,
that
we're
also
now
applying
for
incubation
I.
E
Know
there's
a
lot
of
people
who've
contributed
to
the
project,
thus
far
with
the
intent
of
putting
aspects
of
it
in
production
at
their
at
their
companies.
So
I
think
you
know
Ben.
That
was
one
of
the
reasons
he
was
working
on:
the.net,
SDK
and
contributing
I
I.
Think
there's
a
few
other
cases
like
that
too.
E
So
I
I
think
I
wonder
if
we
need
to
kind
of
reach
out
to
these
people
or
mention
it
in
the
slack
channel
that
this
is
going
to
be
important
for
this,
the
next
cncf
stage
and
just
be
like
hey
if
you're
willing
to
kind
of
go
public
with
your
adoption,
please
let
us
know,
because
I
think
it
would
be
good
to
track
that
for
a
lot
of
reasons.
A
B
So
I'm
I'm
also
happy
to
help
out
there.
One
more
thing
is:
one
of
these
adoptions
will
have
to
then
be
included
in
the
specification,
so
I
I
think
actually
only
one
has
to
be
entirely
public.
I
think
that's
something
that
also
needs
to
be
cleared
up,
but.
A
Yeah
I
think
you
don't
need
I,
think
we
don't
need
this,
because
it
would
be
for
a
specification
only,
but
given
that
we
want
to
have
obviously
the
full
integration,
including
select
B,
so
I
think
that
would
easily
be
doable.
I
think
we
can
get
it
for
one
implementation
of
this
specification
easily
because,
like
the
instant
implementation,
then
we
have
others
with
like
go
feature
slacks
and
others
I
think
we
just
need
to
frame
it
properly.
A
That
there's
like
a
number
of
implementations
being
available,
I'm
also
planning
to
meet
tomorrow
with
dims
and
also
get
the
TSC
prepared
for
moving
in
that
that
we're
moving
in
that
direction.
C
A
C
A
Situation,
I
think
we
have
opposite
either
using
it.
If
you
have
others,
if
you
have
other
projects
that
actually
have
providers
for
it,
where
we
have
a
lot
of
them,
so
I
think
we
have
to
frame
it
properly
and.
E
A
Then
we
should
be
totally
good,
so
I
don't
see
any
issues
coming
up
there.
I
just
want
to
get
some
of
those
questions
out
of
the
way
talking
like
being
here
in
cubic
on
getting
a
chance
to
talk
to
the
TC
chairs
directly.
C
A
D
All
right
is
anything
else
on
that
topic.
D
Perfect
looks
like
Justin
you're
up
yep.
H
Perfect
so
there's
a
few
things
on
my
mental
list
of
things
that
are
on
the
roadmap,
both
to
keep
it
on.
One
is
I've
had
chats
with
people
in
Mobile
and
they.
F
H
Unique
needs
that
are
different
than
backend's
needs
and
so
thinking
through
what?
What,
if
anything,
needs
to
change
in
the
spec
or
be
added
to
the
spec
in
order
to
support
mobile
clients,
I
don't
have
as
close
of
a
relationship
with
the
web
people
at
eBay,
but
I'll
chat
with
them
also
for
for
client-side
flagging.
We
do
a
lot
of
server-side
rendering
and
so
I'm,
not
sure
that
we're,
even
in
naturally
in
them
right
spot
to
have
that
expertise.
H
I
think
a
natural
follow-on
to
feature
flagging
is
like
experimentation
thinking
through
how
we
operate
within
the
context
of
an
experimentation
platform.
Ebay
has
its
own
view.
Given
that
we
do
experimentation,
that's
con,
that's
planning
to
be
entirely
done
via
open
feature,
and
so
that
might
just
be
writing
from
us
to
say
like
what
we're
doing
and
why.
But
we
should
have
some
sort
of
opinion
on
how
experimentation
fits
or
doesn't
fit.
I
know.
H
Todd
yesterday
mentioned
that
tracking
events
may
be
something
that
we
need
to
take
a
position
on,
or
at
least
allude
to.
So
that's
something
in
that
list,
and
then
the
last
one
that
I've
not
written
here.
Yet
is
config
when
I
think
through
how
we
get
adoption
in
other
open
source
projects.
H
That
may
be
difficult
from
a
spec
perspective,
as
in
the
context
of
multi-module
giant
Java
projects.
C
H
H
H
Like
specifically
in
the
context
of
eBay.
We
have
a
giant
config
system
and
then
we
have
a
giant
future
flagging
system.
That's
new
and
people
are
asking
the
question:
how
do
I
choose?
What's
config
and
what's
not
yeah?
My
and
the
answer
I
want
to
give
them.
Is
it's
the
same?
Api
don't
worry
about
it.
C
Oh
sorry,
could
we
use
our
feature
flagging
API
like
open
feature
like
evaluation
API
as
a
way
of
accessing
config
right
and
those
are
kind
of
like
overlapping,
but
they're,
actually
kind
of
like
almost
like
the
inverse
of
each
other
right,
yeah,
so
I
think
I,
I
I
definitely
think
we
should
think
about
this
at
some
point
just
because
from
what
it's
worth
whenever
I'm,
like
Consulting
with
people
about
future
Flags,
this
always
comes
up
particularly
at
like
a
bigger
place
like
eBay,
where
it's
like.
C
We
already
have
like
three
or
four
different
config
systems.
Do
we
want
to
add
a
fifth?
Can
we
use
this
to
expose
that?
Can
we
like,
like
hook
it
into
things
so
I
I,
agree
that
it's
worth
thinking
about
I'm?
Also,
just
my
language,
it's
just
my
two
cents
right
like
I,
it's
a
it's,
a
pretty
big
can
of
worms
to
to
open,
particularly
because
I
think
where
you
see
where
you
see
people
wanting
to
do.
C
This
more
is
like
a
really
big
engineering
orgs,
where
things
get
really
complicated
in
a
very,
very
and
like
tend
to
be
like
very
specific
for
a
specific
organization.
D
A
D
D
Answer
the
question
like:
is
it
configuration
remote
configuration
management
if
we're
hard
against
it?
We
maybe
want
to
have
a
compelling
reason
why
and
if,
if
we're
for
it,
maybe
we
want
to
give
some
like
reasons
to
to
avoid
it
if
it's
going
to
introduce
unnecessary
complexity
or
something
like
that,
so
it's.
D
H
I'm
I'm,
not
I,
don't
feel
like
the
project
needs
to
make
a
declaration
of
what
people
should
do,
but
making
it
possible
seems
useful,
in
particular
like
there's
some
mismatches
between
the
way
that
eBay
handles
its
config
and
the
Global
Singleton
client
divide,
where
like
we
would
actually.
Rather
the
provider
live
on
the
client
rather
than
the
API,
and
so
I've
not
thought
all
the
way
through
it,
and
so
I
need
to
spend
more
time.
But
there's
some
tension
there.
That
needs
to
get
resolved.
E
A
I
just
made
the
proposal.
Can
we
try
to
put
this
into
an
open
feature,
enhancement
proposal,
but
we
would
have
some
of
the
discussions
there.
I
think
we
don't
necess,
all
of
them
documented
yet,
but
I
think
it
would
be
a
good
starting
point
to
also
give
others
the
opportunity
to
comment
on
it.
Yeah.
A
Quite
a
support
we
talked
about
it,
but
we
never
formalized
it
because
eventually,
this
should
then
be
used
also
for
roadmap
planning,
which
enhancement
proposals
we
move
into
the
roadmap
and
also
for
transparency,
I
think
it's
it's
helpful
to
have
them
over
there
and
discussions.
D
Okay,
it
looks
like
Tom
had
a
quick
question
about
multi-provider
support,
so
right
now,
I
have
actually
a
pull
request
for
the
Javas
or
JavaScript
SDK
to
to
kind
of
experiment
with
a
multi-provider
provider.
So
like
a
super
provider
or
whatever
we
want
to
call
it
and
it
basically
Works,
based
on
the
order
that
you
register
the
providers
and
it'll
check
their
first
one
and
move
to
the
second
one.
D
There
could
be
more
elegant
ways
to
do
it
and-
and
you
know
like
Justin's
saying,
maybe
you
want
to
have
a
provider
registered
for
a
client.
That's
that's
out
of
scope
for
what
I've
done
so
far,
but
to
do
the
basics
of
having
multiple
providers
you
know
registered
is
pretty
straightforward.
Actually,
so
you
can
look
at
my
my
pull
request
right
now
and
if
you
have
any
questions,
let
me
know
I
have
to
go
over
it
again.
C
D
The
only
challenge
I
ran
into
was
basically,
we
have
those
provider
Hooks,
and
so
there
was
no
clean
way
to
call
the
provider
hook
or
just
the
provider
that
was
going
to
run
so
I,
just
basically
bubbled
them
up
to
the
super
provider
and
run
through
all
of
them.
So
that
was
the
only
like
caveat
everything
else
just
works.
You
know
pretty
easily
as
like
a
a
combination
provider
or
something
so
yeah.
A
The
multi-provider
one
I
think
we
have
added
like
to
be
in
1.4
orders.
What
are
we
doing
as
multiple
providers
provide
value
for
the
same
feature?
Flag?
Well,.
C
I
mean
I,
think
it's
I
think
it
you
know.
Maybe
it
would
be
worth
providing
like
a
like
a
not
like
a
formal
kind
of,
like
definition
of
like
how
the
secret
sequencing
an
order,
would
vote,
but
maybe
just
like
documenting
like
like
here's,
how
here's,
how
we've
like
it's
been
done
in
this
reference,
implementation
of
it
just
just
so.
D
That
yeah
exactly
I
was
actually
I
was
thinking
about
writing
like
a
little
blog
post
for
how
to
once
it's
merged
in
and
just
show
like
you
know,
you
can
register
multiple
ones.
It
goes
in
this
order
and
why
you
may
want
to
use
it
like
if
you're
you
know
going
from
like
basically
like
hard-coded
feature
Flags
to
like
a
other
solution,
then
you
could
basically
use
that
as
a
way
to
transition.
D
C
D
A
D
Of
got
off
from
that
does
that
answer
your
question:
perfect
cool!
D
I
E
Thanks,
okay,
so
yeah,
the
the
only
thing
I
really
wanted
to
talk
about
on
this
point
was
we
have
a
blog
post
that
talks
about
I
wrote
a
blog
post
that
talks
about
the
release
of
our
1.0
SDK,
so
that
includes
java.net,
typescript
JavaScript
and
go
so
those
have
all
moved
into
1.0,
which
was
a
goal
we
had
for
kubecon.
We
made
it
and
kind
of
just
under
the
wire,
so
thanks
everybody
who
helped
with
that
and
feel
free
to
promote
that
blog
post
link
to
it.
E
If
anybody
sees
any
edits,
they
want
to
make
it's
not
too
late.
We
can
still
update,
update
the
text
or
whatever,
but
it
is
public,
so
I
put
in
the
link
there
and
that's
been
good
to
have,
because
people
have
specifically
asked
about
that
at
kubecon.
A
lot
of
people
have
kind
of
heard
of
us
had
a
trend
traveling
into
the
next
topic
now,
but
a
lot
of
people
heard
of
us
at
Valencia.
E
They
heard
about
the
project
between
Valencia
and
now
and
The
Impressions,
we're
like
oh
I'm,
really
interested
in
this,
but
clearly
it's
very
very
early.
So
having
1.0
sdks
is
something
that
is
really
appealing.
They're,
also
really
interested
to
see
the
amount
of
providers
we
have
documented.
That's
been
really
exciting
too.
So.
We've
had
a
lot
of
good
feedback
at
the
booth,
a
lot
of
interest.
E
A
lot
of
people
like
I
said
who
are
familiar
with
the
project
and
really
happy
to
see
how
far
it's
come
in
six
months
and
frankly,
a
little
bit
surprised
to
see
how
far
it's
come
in
six
months.
So
it's
been
a
very
positive
positive
thing,
so
promote
right
now.
What
we're
trying
to
do
is,
you
know,
grow
adoption.
That
was
something
that
we
talked
about
earlier
in
the
meeting
so
remote
internally
promote
externally.
E
You
know
like
share
subscribe,
that
kind
of
stuff,
I
I,
think
that's
all
I
wanted
to
say
on
those
topics,
short
and
sweet.
Anybody
have
any
questions.
C
When
people
were
surprised,
I
think
there's
two
like
directions
of
the
growth
right.
There's.
Well,
maybe
there's
three
but
there's
two
that
I'm
thinking
of
there's
like
the
number
of
providers
and
then
there's
the
number
of
like
languages
like
sdks.
Do
you
have
a
sense
of
like
which
which
people
were
more
excited
about
or
interested
in,
or
is
it.
E
Well,
my
my
the
way
I
characterize
it
is
everybody
is,
is
just
relieved
to
hear
their
languages
supported
and
most
of
the
people
I
happen
to
talk
to
were
relieved
to
see
that
their
language
was
supported
and
I
think
we
made
some
pretty
intelligent
choices
on
where
we
focused
effort
and-
and
it's
probably
also
not
an
accident
right.
We
there's
a
lot
of
people
here
who
are
coming
from
Enterprise
backgrounds
and
they
use
this
kind
of
big
Enterprise
languages
that
are
popular
right
now.
E
So
people
are
just
relieved
to
know
that
their
language
of
interest
is
supported
and
then
with
providers
it's
providers.
People
are
excited
to
see
a
lot
of
the
vendors
that
are
available.
We
specifically
had
people
say:
oh
I
was
I
wanted
to
purchase
such
and
such
a
vendor.
My
my
team
kind
of
approved
it,
but
the
engineering
team
told
me
that
I
have
to
wrap
their
SDK
before
they'll
use
it
in
production,
and
we
were
just
able
to
say
hey.
We
did
that
for
you,
so
that
was
very
exciting.
E
Yeah
I
I
think
it's
there's
just
a
lot
of
excitement
to
see
that
either
your
language
or
or
the
vendor
of
choice
is
is
supported,
but
that
goes
for
cases
even
when
people
haven't
haven't,
purchased
a
vendor
or
started
any
feature.
Flagging
adoption
in
production.
C
That's
cool
yeah
I'm,
just
asking
because
I'm
just
thinking
from
like
a
marketing
perspective
like
what
is
it
that
gets
people
that
gets
people
excited
about
it.
Is
it
the
you
know
that
their
vendor
is
supported
or
is
it
like?
I
mean
it
sounds
like
part
of
it?
Is
this
vendor
agnostic
thing
of
like
being
able
to
say
we're,
not
locked
into
launched,
Darkly
or
split
or
whatever.
E
D
All
right
anything
else
on
that
yeah
we'll
try
to
send
some
pictures
from
the
booth.
It's
pretty
cool.
We
have
our.
You
know,
logo
up
there.
They
gave
us
a
little
section.
We
have
the
morning
shift.
So
it's
about
you
know
four
hour.
You
know
morning
shift
yeah,
it
seemed
we
didn't
have
a
ton
of
traffic
but
study
traffic
and
the
people
we
did
talk
to
seem
very
interested
in
it
or
had
already
heard
about
it.
We
just
you
know,
talked
through
a
lot
of
different
scenarios,
gave
a
few
demos.
D
We
happen
to
be
right
across
from
the
Argo
Booth,
which
is
also
cool,
because
you
know
they
get
a
lot
of
traffic
over
there
too.
So
we've
been
kind
of
chatting
it
up
and
hopefully
there's
opportunities,
maybe
to
work
with
them
and
the
hotel
team
and
a
few
other.
You
know,
cncf
projects
see
where
those
Integrations
can
really
make
sense,
but
yeah
all
good
here,
we'll
see
how
today
goes.
D
We
also
have
a
session
tomorrow
and
then
Alex
has
a
a
presentation
on
Friday
is
and
so
do
I,
so
hopefully
he'll.
Unfortunately,
it's
at
the
end
of
the
the
week,
so
no
one
will
have
an
opportunity
to
go,
see
the
booth
after
that,
but
you
know
they'll
be
recorded.
Hopefully
we
can,
you
know,
get
some
gain
some
interest
off
of
those
as
well.
D
D
B
F
F
E
D
E
D
And
we'll
Photoshop
EMP,
don't
worry,
okay,
all
right
and
it
looks
like
John
joined
a
little
bit
a
little
bit
after
we
did
the
intros.
If
you
don't
mind
John,
would
you
mind
introducing
yourself
quickly.
I
Yeah,
can
you
guys
hear
me?
Yep
sounds
great
yeah,
so
I
guess
my
name
is
John
Rowley
I've
been
working
in
software
for
like
10
years
now
and
I
love,
I
love
like
metric
observability
things
and
also
trying
to
progressively
or
or
more
iteratively
roll
out
functionality
and
kind
of
heard
about
you
guys
like
last
month
and
then
saw
you
here
at
kubecon
yesterday
stopped
by
and
talked
for
a
bit
and
I
guess
kind
of
kind
of
really
excited
for
this
project
and
the
direction
it's.
A
Gone,
how
did
you
hear
about
us.
I
I
I
was
just
I
was
looking
for
so
right
now
we
have
like
a
really
Half
Baked,
like
internal
like
for
for
my
team.
Only
kind
of
we
rolled
our
own
solution
for
some
feature.
Flags
and
I'm,
always
like
trolling
cncf
for
like
okay.
Is
this
something
that
we
can
replace
some
stuff
that
we
home
rolled
with
a
open
standard?
That's
proven!
That's
that's
out
there
and
or
or
maybe
not
necessarily
proven,
but
it's
on
the
trajectory
for
this.