►
From YouTube: OpenFeature - Project Meeting, March 31st, 2023
Description
Meeting Notes: https://docs.google.com/document/d/1pp6t2giTcdEdVAri_2B1Z6Mv8mHhvtZT1AmkPV9K7xQ/edit?usp=sharing
OpenFeature website: https://open-feature.github.io/
C
A
A
B
A
B
E
B
B
D
D
So
it'd
be
great.
If,
if
kind
of
representatives
from
each
of
those
vendors
vendors
would
take
a
quick
look
at
some
other
providers
in
there,
that
are
that
are
implemented
using
the
the
experimental
web
SDK,
because
it'll
help
us
continue
to
to
vet
out
how
we
want
that
SDK
to
look
and
the
SDK
that's
published
right
now
is
basically
in
sync,
with
the
latest
draft
spec
PR,
which
you
can
find
in
the
spec
repo
yeah.
So
take
a
look.
D
Take
a
look
at
that
and
let
me
know
what
you
think:
I'll
send
out
links
after
the
meeting
or
maybe
just
put
them
in
the
in
the
dock
or
a
message
in
slack
or
something
like
that.
Actually,
maybe
that's
what
I'll
do
is
I'll
just
I'll
kind
of
ping,
with
direct
links
to
the
providers
and
slack
in
the
in
the
cncf
open
feature,
Channel
I!
Think
that's
really
all
I
wanted
to
talk
about
so
I
won't
demo
it
or
anything.
D
It
looks
exactly
like
the
old,
like
the
old
playground,
except
it's
implemented
with
client-side
feature
Flags
instead
of
everything
being
evaluated
on
the
server
I.
Think
that's
it
for
my
update.
Does
anybody
have
any
questions
about
that
cool,
okay,
yeah?
So
my
one
follow-up
is
I'll,
put
a
big
message
in
the
in
the
slack
Channel
and
and
ping
some
reps
from
vendors
with
specific
lines
of
code
they
might
want
to
look
at
the
providers
are
really
basic,
but
it
will
I
think,
like
I
said
help
us
vet
the
web
SDK
thanks.
B
B
So
you
will
potentially
see
some.
You
know
potential
mentees
pop
into
the
slack
Channel
or
on
GitHub.
Asking
various
questions
so
definitely
ask
you
know,
for
everyone
to
you
know
be
welcoming,
of
course,
like
you
would
any
any
new
person,
but
especially
for
for
these
students,
because
they're
they're
just
breaking
into
open
source.
B
So
just
keep
that
in
mind
as
we
get
you
know
some
people
to
join
and
ask
questions
and
I
know
of
at
least
two
potential
mentees
that
are
working
on
the
proposal
and
and
likely
more
because
I've
seen
quite
a
bit
of
interest
on
the
issue
itself.
So
then
also
related
to
that.
If
there's
anything
that
you
would
like
to
see
on
that,
like
ofep
or
enhancement
proposal
process,
that
you
know,
we
could
improve
either.
B
Add
it
to
that
issue
that
we
have
in
the
ofaps,
OR
or
just
let
me
know,
and
we
can
go
ahead
and
try
to
add
that
to
the
to
the
requirements
for
the
project,
so
at
a
high
level.
Basically,
the
idea
is
to
automate
parts
of
that
process
to
make
sure
that
any
of
these
proposals
are
are
pushed
through
it.
B
B
Any
questions
on
either
of
those
topics
before
I
move
on
no
all
right.
Next
one,
this
one
was
was
kind
of
a
big
one.
We,
we
did
set
up
some
user
permission
automation
a
couple
days
ago,
so
you
may
have
seen
like
a
lot
of
removal
from
a
group
added
to
a
group.
Things
like
that.
The
idea
was
to
basically
kind
of
make
up,
for
you
know
a
year
of
manually,
configuring
stuff
across
like
35
repos
or
40
repos
or
something
so.
B
This
now
is
all
controlled
from
a
single
Community
repo.
You
can
look
in
there
and
see
basically
like
user
permissions
and
who
has
access
to
what
repos
and
that
is
run
automatically
when
you
merge
a
pull
request
with
a
change
in
there
and
it's
also
running
out
of
schedule.
So
if,
if
certain
things
are
manually
modified,
it
will
actually
revert
it.
If
it's
not
version
controlled
there,
so
just
kind
of
an
FYI
there.
B
It
should
make
it
a
little
bit
easier
to
get
the
the
permissions
that
you
need
and
also
make
it
a
bit
more
transparent
on
like
who
has
what
access
and
if
you
did
like
end
up
like
losing
permissions.
For
some
reason
it
wasn't
the
intention.
So
definitely
let
us
know-
and
we
can
correct
that,
and
then
we
did
break
out
the
parabola
or
pre
Blues
like
code,
essentially
to
a
separate
repo.
B
You
can
find
that
under
the
Community
tooling
repo
now
and
that
just
publishes
a
a
Docker
image
that
we're
using
as
part
of
the
the
community
like
release
process,
so
I
I
think
it
works
pretty
nicely,
but
it
was
fairly
destructive
when
we
ran
it.
So
apologies
for
the
kind
of
the
notification
spam
but
I
think
we're
in
a
pretty
good
spot
now
to
to
centralize
some
of
these
configurations.
B
Well,
next,
one
is
kubecon.
I
move
this
one
down,
so
it
was
kind
of
in
line
with
what
David
had
here.
We
do
have
a
slack
channel,
so
the
open
feature
Dash
cubecon
channel.
So
if
you're
gonna
attend
definitely
join
that
channel
I've,
already
posted
a
few
like
events
and
stuff
that
I've
found
out
about
that
could
be
kind
of
interesting
to
you
know,
get
people
there
and
we
can.
You
know,
hang
out
after
the
event
for
a
bit
and
yeah
chat.
We
also
have
a
one
hour
time
slot
Reserve.
B
B
So
we
can
either
like
if
there
is
a
topic
that
we'd
like
to
discuss.
You
know,
let
it
let
me
know,
let
us
know
we
can
try
to
make
that
happen.
Otherwise
it
may
just
be
a
good
time
to
kind
of
socialize
and
meet
each
other,
because
a
lot
of
us
have
only
met
virtually.
So
we
do
have
that
available
to
us
and
there's
no
yeah,
immediate
schedule,
I
guess
defined
for
topics
we
want
to
discuss.
B
B
A
B
E
E
So
the
fact
is,
we
have
a
room
that
can
hold
a
maximum
of
20
people,
so
we
haven't
been
pushing
it
as
a
like.
Hey
come
to
our
project
meeting
for
the
simple
fact
that
you
know
if
the
space
is
that
limited
and
I
think
they're
already
I
think
at
least
10
15
people,
probably
from
the
project
that
will
be
there.
So
we
can
we
can,
then
you
know,
push
it
and
share
it.
E
If
everyone
agrees
to
that,
that's
that's
also
fine
yeah
and
then
for
the
kiosk
I
added
in
the
kubecon
channel,
a
small
poll
to
see
like
who
would
be
possibly
available
to
be
at
the
to
be
there
I
added
like
rough
times.
It
doesn't
mean
you
have
to
be
there
the
whole
time.
It's
just
to
kind
of
have
some
changeover
to
talk
about
the
project,
especially
on
the
the
Wednesday
I
think
yeah
the
one
day,
because
it's
it's
quite
a
long
day,
there's
also
the
cube
crawl.
E
E
E
Yeah
and
then
we'll
we'll
do
our
best
to
try
and
keep
some
and
maybe
get
them
out
to
those
that
can't
be
there
and
actually
seeing
as
I'm
not
sure.
If
anyone
here
is
an
ambassador
or
made
it
into
the
cncf
Ambassador.
So
maybe
we
could
have
more
than
just
water
and
coffee
at
our
project
meeting
and
use
that
the
ncf
budget.
E
Or
something
we
get,
we
get
150
Euros
a
month
for
meetups
and
and
and
anything
that's,
let's
say
one
donut
yeah
for
anything
around
the
cloud
native.
We
can
kind
of
use
that
budget
an
expenses,
so
maybe
we
can
have
pizza
now,
just
kidding
yeah.
That's
that's
all
on
my
side,
if
you
have
any
questions
for
other
stuff
around
kubecon,
just
let
me
know
or
if
you
haven't
joined
the
kubecon
channel
yet
I
think
have
grabbed
the
chance
to
do
so.
B
B
There
was
a
a
proposal
by
Justin
actually
for
for
basically
supporting
multiple
providers,
that's
something
that
I
think
it's
worth
exploring,
but
from
my
perspective
at
least
I'm
not
going
to
have
a
ton
of
Cycles
for
it
until
probably
after
kubecon,
but
I
really
do
think
it's
an
interesting
area
and
something
that
we
may
want
to
to
keep
trying
to
get
feedback.
And
then
maybe
it's
something
we
could
tackle
like
immediately.
You
know
post
keep
on
if
it's
something
that
we
you
know
agree
to,
but
I
don't
know
Justin.
A
G
G
Especially
useful
in
context
where
you
want
to
have
like
at
eBay,
we
have
this
config
system
and,
as
we
begin
to
migrate
people
from
the
config
system
to
an
open
feature
backed
by
some
eBay
internal
service,
like
we
basically
want
to
take
over
that
config
system
access
and
say
no,
no,
you
use
openfeature
for
that.
Yeah
slowly
migrate,
your
stuff
for
you
over.
D
A
F
B
F
B
You
know
if
we
can
link
that
one
yeah
definitely
take
a
look.
It's
my
only
real
concern
probably
is
more
around
like
the
developer
experience,
because
I
think
conceptually
like
it
makes
tons
of
sense,
and
it
should
even
be
relatively
easy
to
implement
it's
just.
How
does
it
like
feel
to
use
if
it
you
know,
is
it
confusing?
Is
it
a
breaking
change
if
it
is
like
how
do
we?
How
do
we
deal
with
that?
B
F
When
we
talked
about
when
we
were
talking
about
the
the
client-side
SDK,
there
was
a
kind
of
conversation
about,
but
I
had
a
few
conversations
with
Todd
I
know
about
like
the
whole
Singleton
thing
and
wherever
you
could
like
what
like
what
was
in
a
what
state
lived
in
a
client
versus
in
a
in
the
kind
of
the
global
term
did
whatever
happened
with
that?
Did
we
decide
to
kind
of
like
punt
on
that
aspect
of
you
know,
changing
things.
G
A
G
Are
going
to
be
generating
these
clients
previews
in
their
like
code,
and
so
we
don't
want
them
to
be
responsible,
for
instance,
for
which
provider
gets
used
yeah
and
so
then
creating
a
named
client
that
is
then
configured
by
the
application.
Author
is
kind
of
the
direction.
I
was
pushing,
at
least
so.
D
Gotta
yeah
I
think
that
makes
sense,
I
I
think
the
the
ergonomics
of
that
are
pretty
clear.
The
only
confusion
that
has
come
up
a
couple
times
is
is
like
kind
of
like
I
mentioned
before,
just
to
make
sure
that
people,
because
both
me
and
and
and
the
the
other
contributor
I
was
mentioning,
got
confused
for
a
second
that
they
were
creating
kind
of
like
a
provider
registry,
but
it's
actually
a
named
a
named
client.
D
Really
that
can
be
associated
with
a
particular
provider
is
probably
a
better
way
to
put
it,
which
I
think
those
ergonomics
make
sense.
We
just
need
to
make
sure
there's
no
confusion
around
that.
So
I
honestly
think
it's
just
mostly
in
how
we
how
we
name
the
methods
and
parameters
I
think
that's
really
the
only
the
biggest
way
to
help
there.
D
As
far
as
the
Singleton
stuff
Pete
yeah,
like
the
the
there
is
definitely
more
Global
State
on
the
client
I
think
that's
less
of
an
issue
on
the
client
for
a
couple
reasons.
It's
a
single
user
context
really,
and
it
is
fairly
consistent
with
a
lot
of
the
vendor.
Sdks
yeah,
which
is
kind
of
also
why
we
we
kind
of
get
got
funneled
into
that
situation,
because
we
have
to
support
those
vendor
sdks,
but
but
I
I
think
this
would
also
be
doable
in
the
client
without
an
issue.
D
The
kind
of
the
thing
that
Justin
is
proposing
so
I
don't
see
it
as
a
as
an
issue
there,
but
yeah
there
is.
There
is
more
Global
State
on
the
client
and
Global
state
is
more
of
a
more
the
implications
of
goal.
State
and
you're,
interacting
with
global
state,
is
definitely
something
that
happens
more.
If
you're
dealing
with
the
the
client
SDK
the
at
least
the
experimental
one
that
exists
right
now,.
F
F
D
B
B
Okay,
I'll
take
a
just
a
note
here
that
you'll
try
to
take
a
look
at
it,
but
I
think
that
would
be
valuable
to
take.
You
know
spend
some
time
thinking
about
the
testing
partial
portion
of
it,
because
it's
obviously
like
an
important
part
of
software
now
and
if
it
needs
to
be
pretty
simple
to
write
tests,
if
possible,
yeah
I
know
a
lot
of
vendors
do
like
cover
that
in
their
documentation.