►
Description
Michael Beemer, Todd and Oleg discuss how we could build a new full-fledged roadmap for OpenFeature and what features GitHub Projects offer for that. Also we discussed GitHub automation through .github and with help of GitHub Actions like Release Drafter
OpenFeature website: https://open-feature.github.io/
A
All
right
and
I
can
share
my
screen
real
quick.
So
basically
we
had
you
had
created
the
the
project
section
of
the
open
feature
or
for
the
open
feature.
Org.
A
Good,
my
question
is
like
these
are
all
extremely
high
level.
That's
totally
fine,
but
I
need
to
start
breaking
it
down
into
more.
I
guess
granular
sections
looking
at
the
current
state
of
github
projects
like
doing
like
kind
of
nested
high
level
or
topics
in
here
is
not
currently
possible,
maybe
not
even
recommended
so
would
you
recommend
me
like
basically
adding
some
kind
of
like
you
know?
You
know,
column
and
label
here,
so
we
could
filter
like
main
initiatives.
B
Interesting
I'll
close
this
slug
so
that
it's
not
disturbing
okay
and
this
might
create
yeah.
So
this
is
my
screen.
Yep.
B
Okay,
so,
basically,
when
you
work
with
github
projects,
there
are
multiple
ways
to
adjust
the
dashboard.
Actually,
there
are
multiple
visualizations
available
only
in
projects
beta.
A
A
B
A
B
So,
for
example,
for
python
is
the
key
or
we
can
say
whatever
one
two
zero
really.
B
A
To
that
but
okay,
so
we'd
want
to
be
like
that
verbose
too.
We
wouldn't
want
to
say
just
like
alpha
right.
B
We
create
a
milestone
and
this
milestone
actually
exists
only
within
this
repository.
Okay.
So
what
you
can
do
is
you
can
group
them
but
yeah.
This
is
a
difference
between
labels
and
milestones
because
labels,
you
can
operate
them
across
multiple
repositories
in
github
projects
and
milestones
are
not
implemented
like
that.
B
So,
for
example,
this
is
alpha
release.
Do
you
have
any
topics
you
would
like
to
really
introduce
in
this
milestone.
A
A
But
yeah
nothing
necessarily,
although
we
could
probably
move
some
of
these.
Like
I
don't
know
the
hook
specification
and
stuff
like
that
could
be
added
to
the
alpha
one.
B
Yeah
anyway,
we
can
later
adjust
it
if
needed,.
A
B
Okay,
it
shouldn't
be
a
problem
here,
so
I
will
just
assign
it
to
the
milestone
open
future
spec
alpha.
So
you
can.
You
can
see
it
here.
You
can
also
see
issue
list
right
here
right
now
and
what
we
can
do
else
that
if
we
go
to
our
project
now
we
can
configure
the
visualization
because
by
default
you
cannot
see
that,
but
you
can
actually
adjust
the
layout.
So,
for
example,
you
can
set
up
milestone.
Labels
repositories
probably
doesn't
make
sense.
I
didn't
pull
requests,
so
it's
one
of
possible
visualizations.
B
B
A
B
This
is
what
we
can
do
right
now,
because
yeah,
for
example.
So
this
is
not
a
good
example,
but,
for
example,
captain
roadmap,
how
it
looks
like
we
have
slices
of
this
roadmap
for
particular
topics
like
functionality,
core
function
integrations
community
documentation,
and
we
can
do
it
like
that
here.
So,
for
example,
if
you
want
specification
so
here,
for
example,.
B
A
A
Cool
and
then
I
could
have
something
yeah
in
here
that
makes
sense.
Okay,.
A
So
when
it
comes
to
main
initiative
should
should
would
you
recommend
this
being
just
kind
of
a
dump
of
everything,
or
should
I
somehow
keep
it
like
at
like
extremely
high
level
topics
here,
because
this
is
kind
of
like
the
main
landing
page.
B
A
A
B
Yep,
so
what
we
can
do
so
if
you
see,
I
think
that
the
item
is
already
completed
so,
for
example,
github
organization
bootstrap.
So
that's
not
really
case
by
now
so
bootstrap
governance
process.
We
can
see
that
it's
done
because
I
believe
it's
done
by
now
yeah,
so
we
can
dump
it
if
needed,
but
yeah
establish
regular
project
meetings.
Again,
nobody
cares
by
now
yeah
it's
just
unboxing
project
application
in
progress,
define.
A
B
A
See
actually,
if
you
select
that
define
initial
scope,
if
you
just
like
open
it
right
there
so,
like
I
dumped
a
bunch
of
stuff
in
here
as
placeholders,
basically
I'm
going
to
port
this
to
basically
initiatives
more
or
less
and
then
hopefully
apply
filters
based
on
some
of
the
stuff.
You
see
here
to
like
kind
of
reference
all.
B
B
A
Yeah
we
can
do
the
announce
project
at
kubecon.
That's
done.
A
Honestly,
most
of
these
could
probably
go
away
when
I,
after
I've
gone
through
and
done
the
rest,
because
I
think
you
can
accomplish
most
of
the
stuff
with
you
know.
Different
labels
and
filters
and
whatnot
like
the
the
road
to
general
availability,
should
probably
be
done
with
milestones.
Based
on
what
we're
seeing
here,.
B
A
And
I
have
that
kind
of
done.
I
think
now,
so
I
can
I'll
start
plugging
away
on
that
and
I
think
when
that's
done
I'll
archive
all
the
stuff
you
have
currently.
B
A
I
think
I
guess
the
question
is
like
what
would
be
a
compelling
main
landing
page
like
what
would
be
something
that
you
could
say
like
what
is
the
current
state
of
the
project
or
doesn't
it
matter?
Could
we
like
look
at
because,
like
I
almost
need
something?
That's
like
the
spec
is
in
progress.
The
whatever
is.
B
A
What
I'm
wondering
maybe
just
have
incredibly
high
level
topics
like
whatever
define
or
like
alpha
release
or
something
like
that
for
the
spec
or
something
so
yeah.
A
B
B
Oh
okay,
so
yeah,
I
guess
some
filters
are
not
exactly
as
we
one
would
expect,
but
yeah
okay.
A
So
I
mean
maybe
it's
no
big
deal
I
mean
maybe
like
at
the
moment
people
care
more
about
the
specs.
So
maybe,
if
I
could
put
the
spec
as
like
the
main
landing
page
basically
and
show
like
the
different
topics
that
we're
working
on
where
we
are
things
like
that,
may
be
really
really
nice
and
then
obviously
the
sdks
are
next
and
then
some
of
the
other
stuff
kind
of
like
downstream
there.
So
maybe,
instead
of
doing
some
of
the
other
pieces,
I
would
just
focus
more
on
on
the
spec.
A
Yeah,
basically,
like
all
topics
or
something
you
know
basically,
and
then
that
would
probably
be
at
the
end
of
the
list.
You
know
what
I
mean
it's
like.
If
you
want
to
see
everything
we're
working
on,
you
would
go
to
the
last
tab,
but
if
you're
going
directly
to
the
modem
roadmap
with
no
view
selected
you'd
land
on
the
specification,
so
I
think
this
is
stuff
that
I
can
kind
of
handle.
I
was
kind
of
just
talking
through
or
trying
to
think
through
it
at
like.
A
You
know
what
would
make
the
most
sense
to
you,
that's
kind
of
where
I
really
wanted
the
feedback.
I.
A
I
can
do
pretty
easily
seeing
like
the
filtering
and
you
can
create
custom
columns.
You
can
add
in,
like
you
know,
whatever
statuses
you
need
like,
that
stuff
seems
pretty
straightforward.
It.
B
A
Just
I
was
kind
of
just
trying
to
figure
out
how
we
went
from
the
stuff
you
had,
which
I
think
was
solid
and
breaking
it
down.
You
know
because
they
didn't
really
have
those
layers
of
abstraction,
although
I
actually,
maybe
you
can
help
with
this
one.
I
saw
something
in
a
video
yesterday
that,
if
like
say,
if
you
select
test,
for
example,
so
number
nine.
B
B
A
B
B
Yeah,
so
you
can
see
that
there
is
project,
so
I
basically
have
all
of
feature
flux
enabled
I
mean
once
which
are
public,
so
that
is
set
by
now
that
yeah.
So
basically,
this
is
what
we
were
trying.
A
B
So
if
you
need
to
create
something
specific
so,
for
example,
python
sdk
and
whatever
you
use
2000
tasks
there,
maybe
you
want
to
have
a
separate
project,
but
for
roadmap
you
still
have
something
top
level
like
python,
sdk
version,
1.0
python,
sdk
version,
2.0,
etc.
With
scope.
A
B
A
B
A
B
This
case
well,
so
some
issues
are
quite
detailed.
So,
for
example,
captain
enhancement
proposals
they're,
basically
pieces
of
specification,
so
they
have
specification,
they
have
a
bunch
of
statuses.
They
have
linked
tickets
if
needed.
So
this
edition
some
other
items
like
captain
community
and
cubecon
valencia.
Well,
there
is
some
text
there.
B
B
B
B
B
So,
for
example,
here,
if
you
create
an
issue
in
captain,
it
will
show
you
dialogue
where
you
can
select
a
type
of
the
issue,
then
here,
for
example
new
integration,
and
it
actually
opens
this
one
but
copies
all
the
context
instead.
So
something
is
definitely
broken
in
this
repository,
I'm
not
sure
what
but
yeah
I'll
figure
it
out
later,
but
generally
for
each
type.
You
can
stop
your
own
template
either
as
form
or
all
style
like
this
one,
and
then
you
automatically
get
labels
assigned,
etc.
So
users
don't
have
to
care
about
it.
B
Sure,
because
bonus
points
that
you
can
have
additional
metadata.
So,
for
example,
we
send
people
to
slack
that
is
also
security,
metadata
new
integration,
and
you
can
see
that
it
actually
redirects
to
other
things,
because
we
use
standard
github
metadata
to
adjust
it.
So
it's
not
an
issue
template,
but
it
points
people
on
the
same
list.
B
So
security
is
basically
standard
functionality,
so
for
security
we
have
captain.github.
So
it's
global
configuration
repository
and
here,
for
example,
we
have
secured
tmd
file
and
if
it's
configured
in
this
repository
it
applies
to
the
entire
organization
by
default.
B
A
A
Do
nothing
and
do
create
repo,
at
least
it
wasn't
for
me
creating
or
porting
of
the
license
and
other
stuff
see.
Okay,.
B
So
contributing
file.
It
also
comes
from
this
repository,
so
here
so
when
you
create
a
new
issue,
for
example,
it
should
show
you
your
comments.
B
B
A
Yeah,
okay,
okay,
cool,
so
everything's
working,
it's
license
was
the
only
one
that
was
a
little
tricky
because
I
thought
that
that
would
like
be
added
right
to
the
repository,
but
no
cool.
A
B
B
A
Okay,
anything
else
that
you're
noticing
that
needs
like
immediate
attention.
B
B
A
B
For
the
rest,
yeah
most
of
metadata
could
be
stored
in
github
these
days.
A
B
A
That,
in
a
good
spot,
it's
going
to
make
people
feel
a
lot
better.
I'm
also
going
to
make
the
sdk
repos
public
with
that
disclaimer
I'll
probably
also
update
this
back
and
try
to
like.
I
don't
know-
I
probably
won't
get
to
it
today,
but
I'm
gonna
start
updating
that
readme
a
little
bit
as
well.
B
It
still
requires
some
liquid
work
to
stop
everything.
I
actually
wanted
to
stop
it
in
captain
and
then
move
it
over
then
keep
going.
A
A
B
A
Concern
about
this-
and
I
think
we've
already
talked
briefly,
but
it's
like
the
reason
I
was
reluctant
to
do
it
at
first
was
to
some
extent
it
feels
like
we're
sort
of
mandating
the
direction
now.
But,
of
course
someone
needs
to
kind
of
take
some
kind
of
initiative,
so
I'm
not
sure
how
to
balance.
You
know,
initiative
versus
community
well,.
B
Is
an
input
strap
stage,
so
basically
we
go.
We
tried
something
we
learned.
We
are
just
for
me.
It's
perfectly
fine
that
you
create
a
template
roadmap.
I
mean
put
everything
there.
It
still
comes
on
with
a
disclaimer,
then
basically
review
it
with
the
team
at
the
meeting,
and
then
you
agree
what
goes
there?
What's
not?
B
Okay!
I
wouldn't
be
too
concerned
about
doing
some
experiments
right
now,
because
everything
is
under
the
disclaimer
of
experiment.
A
Oh
yeah
yeah
that
all
makes
sense.
Okay,
I
guess
last
question
because
it
just
came
in
like
25
seconds
ago,
someone
just
opened
up
an
issue
on
our
spec
talking
about
hook,
context
and
stuff,
like
that.
This
is
a
good
question
but
like
if
we
were
talking
about
from
a
project
planning
standpoint.
If
I
had
like
hooks
as
a
item
on
our
spec,
you
know
project
board.
Would
it
make
sense
to
like
reference
something
like
this
inside
that
ticket
effectively?
B
B
Yes,
so
here,
for
example,
we
could
do
like.
I
usually
do
so
something
like
scope
here,
you
can
use
this
metadata,
which
is
a
checklist
and
here,
for
example,
yeah
we
around
hooks
whatever
else
we
have
so,
for
example,
or
recorder
rank
and
state.
Finally,
who
cares.
A
B
I
think
so,
for
example,
let's
try
to
do
it,
so
I
put
it
here
then
I
put
it
on
the
road.
B
So
on
the
project
right
now
we
don't
have
automation
sets,
so
it
just
goes
to
non-status,
because
if
you
set
up
automation
you
can
actually
set
up
automatically
states
based
on
statuses,
etc.
So.
B
Yeah,
you
can
easily
set
up
automation
so
a
bit
of
workflow
and
here,
for
example,
when
item
added
to
the
project
status
backlog
set,
enable
just
enable
yeah.
So
there
is
a
bunch
of
default
workflows,
so
they
actually
publish
this
interface
quite
a
lot
but
yeah
right
now.
It
should
be
by
default.
B
B
A
Yeah:
okay,
that's
what
I
want
to
do
here,
because
I
think,
having
all
of
those
listed
out,
you
know
fairly
well
and
then
it's
starting
to
link
to
other
issues
and
discussions
about
that
makes
it
pretty
nice
and.
A
Track,
that's
what
I
was
looking
for.
You
see
that
tracked
in
you
know
42
at
the
top.
That's
pretty
cool.
B
So
basically
github,
it's
all
references
automatically
yeah
here,
I'm
just
hitting
milestone,
so
you
can
easily
do
it
in
other
interface
or
maybe
you
can
just
maybe
at
some
point.
You
want
to
create
a
label
for
hooks
and
you
don't
know
so
it's
up
to
you
how
you
define
it.
A
Can
hooks
be
repo
specific.
B
B
Topics
so,
for
example,
for
topics
we
can
say
that
by
default
we.
B
B
B
Yeah
there
is
view
all
button:
okay
yeah,
but
basically
this
is
a
promote
application.
So
basically
promote
means
that
it's
standard
configuration
framework
and
you
can
define
this
github
settings
yaml
in
the
dot
github
repository
and
once
you
do
that,
every
repository
which
is
connected,
it
will
get
saved.
A
Cool
yeah
so
like,
and
I'm
assuming,
if
we
leave
things
out,
they're
just
left
undefined,
but
studying
things
like
home,
page
and
topics
and
stuff
would
be
great
to
automate
yep
cool
yeah.
I
know
that's
a
great
tip.
Can
you
send
me
that
one
too?
Actually
it's
just
app
settings.
I
can
find
that
actually.
B
B
This
is
actually
a
main
difference
between
github
and
github
and
other
systems,
because
they
invest
a
bunch
of
time
in
this
ecosystem,
so
both
ups
and
actions
and
thanks
to
that,
actually
there
is
a
lot
of
features
available.
So
I've.
A
Not
even
looked
at
this,
but
that's
to
get
tipped
yeah
I'll,
take
a
look
into
it.
B
Well,
I
hate
this
board,
but
it's
a
separate
story,
but
yeah
you
can
actually
find
a
lot
of
good
stuff
here
or,
for
example,
I
personally
make
fun
of
release
drafter,
which
often
automates
really
is
change.
Locks
based
on
pull
requests.
So
it's
not
a
git
change,
lock,
it's
more
high
level
based
on
pull
requests.
A
B
So
we
use
it
in
jenkins,
we're
quite
successful
again.
I
have
no
idea
what
my
marketplace
search
doesn't
work,
but
I'm
able
to
find
all
these
boss
etc.
Right
now,
so
we
use
it
in
jenkins
and,
for
example,
most
of
jenkins
change
logs
for
plugins
account
he
built
on
this
app.
So,
for
example,
let's
take
something
useful,
like
configuration
split
plug-in
so
here.
Currently
we
have
continuous
delivery.
So
sometimes
versions
are
not
that
informative.
B
A
A
B
Yeah,
so
basically,
currently,
this
draft
is
maintained
by
a
few
people
from
the
junkies
community
because
we
are
adopted
mostly
everywhere.
So
here,
for
example,
we
just
use
double
github,
so
you
can
see
that
even
for
the
jenkins
core,
we
have
unified
configuration
and
here
so,
for
example,
it
hub.
If
you
go
here,
it's
here
release
drafter,
so
here
you
can
see
basically
how
it
works
for
us.
So
by
default
we
use
two-digit
versioning,
not
somewhere,
but
you
can
configure
somewhere
as
well.
B
Here
we
have
priority
so
based
on
label
like
breaking
removed,
major
features
etc.
So
we
generated
this
layout,
then
we
also
have
some
excluded
labels
so
that
we
don't
include
everything
and
then
we
also
replace
some
text.
So,
for
example,
here
we
automatically
capture
issue
ids
from
jira
and
replace
it
by
jitter
hyperlinks.
A
B
Well,
it
doesn't
really
matter
the
stage
so
for
issue
templates.
I
would
recommend
to
start
them,
build
building
them
in
the
main
in
dot
github
right
away,
because
otherwise
it's
difficult
to
drag
them
for
github
releases,
etc.
You
can
actually
start
using
don't
github
as
well,
because
the
tricky
point,
even
if
so
here
I
just
use
source
repository,
but
you
can
actually
have
multiple
configuration
files.
A
B
Complete
templates,
if
I
recall
correctly
so
the
problem
for
that,
is
that
I'm
not
sure
this
repository
was
updated
to
a
new
version,
but
here
we
can
just
check
so,
for
example,
issue
template.
So
you
can
see
that
these
are
rather
old
versions.
A
B
A
B
A
A
Okay,
cool
yeah,
I
think-
and
I
think
I'm
gonna
sync
up
like
david
periodically,
but
just
doing
some
kind
of
regular
touch
points,
because,
like
this,
this
like
I
knew
I
was
kind
of
lacking
in
some
areas,
but
like
going
through
it
with
you,
like,
there's
stuff
that
like
looks
incredibly
useful
and
I
had
no
idea
existed
so
like
doing
these
at
some
semi-regular
sink.
I
know
you're
super
busy,
but
any
anything
where
we
could
kind
of
just
go
over.
B
A
B
And
yeah,
I
still
have
another
meeting
soon.
Oh
my
gosh,
I
spent
almost
all
the
morning
trying
to
get
the
passport
and
they
totally
failed.
So
that's
a
bummer.