►
From YouTube: Octant Community Meeting - March 24th, 2021
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
All
right
welcome
everybody
to
the
march
24th,
often
community
meeting
today
we
are
cutting
release,
so
we're
going
to
talk
about
that
see.
If
anyone
has
any
demos
or
features
I'd
like
to
call
out,
let
me
share
the
agenda
and
we
will
get
started
so
bigger.
A
Okay,
so
yeah,
so
today
is
oh
that
18
release
it's.
It
was
it's
a
it's
a
pretty
good
release.
I
was
gonna
pull
up.
The
we
haven't
made
the
release
pr
yet,
but
that'll
probably
happen
the
next
few
hours.
We
have
a
good
set
of
lots
of
changes
in
this
one,
so
we've-
and
I
can-
I
can
actually
show
some
of
this
on-
would
be
good
to
show
some
of
it
on
our
so
documentation.
Actually,
this
is
this
is
fixed.
A
The
reference
site
is
updated
off
from
our
main
upstream
tracking
branch,
so
we
you'll
see
some
of
the
newer
stuff
in
here,
even
though
it
isn't
officially
released
yet
so
I
was
just
gonna
show
some
of
that
through
storybook
sam
added,
the
just
the
standard
accordion,
it's
very
similar
to
it's
actually
a
a
child
of
the
or
a
parent
to
the
stepper,
but
without
the
form
elements
and
the
you
know
props
to
go
to
the
next
one.
So
that's
the
clarity
actually
implements
it
in
a
like.
A
In
the
back
end,
in
the
same
way,
so
we
just
exposed
the
the
actual
raw
according
element
for
people
to
use
for
putting
data
into
their
fields.
There's
a
few
I'm
trying
to
remember
all
the
yeah,
so
you
can,
you
can
do
the
allow
multiple
expanded,
which
I
think
by
in
our
example.
We
have
set
to
false.
A
But
if
I
flip
that
to
true
this
is
config
rows.
There
yeah
allow
multiple
expanded
true.
A
So
now
I
should
see
that
they
both
expand
so
sam
thanks
for
that
one,
let's
see,
we've
also
got.
It's
got
updated,
we're
gonna!
There's,
let's
see
that
was
already
there.
That
was
already
there
was.
There
was
the
icons
so
luis
added
the
ability
for
just
a
straight
icon
component
now
currently
by
itself.
This
is
more
of
like
a
prep
for
other
features
coming
so
right.
Now
it
is
just
an
icon.
You
can't
like
it's
it's,
it
will
work
anywhere.
A
You
can
put
a
component,
but
you
can't
like
easily
embed
it
with
with
into
text
or
easily
use
it.
You
know
within
other
parts
of
octan
one
area
where
you
can
easily
use.
It
is
like,
for
example,
in
titles.
You
can
now
stick
an
icon
component
in
a
title
and
have
it
render
out
which
was
difficult.
A
You
could
do
it
before
you
had
to
use
markdown
escape
to
html,
to
do
it
so
but
yeah.
So
this
supports
it's
currently
based
on
clarity.
Four,
it's
it.
It
supports
all
of
the
standard
fields.
Status
is
like
the
the
one
that
is
has
optional
things.
Where,
when
you
change
status,
it
will
use
the
clarity
status
indicators
instead
of
the
color
you
provide.
A
So
you
can
see
now
it
went
to
yellow
because
it's
warning
so
status
will
take
precedence
over
over
color,
but
we
do
also
allow
just
free
form
explicitly
set
in
color.
All
of
the
all
of
the
other
options
are
fully
supported
and
you
can
see
as
I'm
as
I'm,
maybe
I'm
a
little
bigger.
But
as
I
change
these
things,
things
change
right.
All
of
the
icon
shapes
are
the
same
shapes
that
that
clarity
lists
and
also
arbitrary
sizing.
I
think
up
to,
like
I
don't
know.
A
If
we
put
a
cap
on
it
or
not,
maybe
we
did
it
doesn't
look
like
it
as
big
as
you
want
so
yeah.
This
is.
This
is
a
really
good
feature
that
will
be
you're
going
to
see
this
being
leveraged
a
lot
throughout
the
rest
of
octan
and
upcoming
releases.
An
example
is
like
in
our
modules
we
like
they
list
all
those
icons.
On
the
left
hand,
side.
A
Those
are
just
text
strings
right
now
that
we
convert
to
icons,
we'll
probably
ultimately
replace
that
with
you
just
pass
in
an
icon
component,
then
it's
configurable,
it
can
have
a
badge
you
can
have
you
can
you
know
change
colors
based
on
statuses
things
like
that,
so
the
badge
color,
I
think,
is
all
the
standard
like
yeah,
so
that's
green,
so
yeah,
so
that
was
from
those
from
luis.
So
thank
you
for
that.
A
I
think
one
of
the
things
I
I
forgot
to
do
for
some
of
the
newer
members
of
the
team
was
remind
everyone
to
like
have
demos
prepped
for
release.
When
we
do
the
community
meeting
and
it's
time
to
release
we
all
we
try
to
demo
the
things
that
we
worked
on.
I
didn't
do
a
good
job
of
like
prepping
people
for
that,
so
I'm
just
running
through
all
the
things
that
other
people
did.
None
of
this
is
work
I
did.
A
This
is
all
work
that
the
team
did,
so
I
just
want
to
call
that
out
as
I'm
going
through
it.
So
what.
A
So
we've
got
so
that's
the
icon,
I'm
trying
to
think
if
there
was
labels
and
selectors
to
say
list
the
list
components
the
same
step,
the
table
stuff
yeah
yeah,
so
we
sam
added
the
ability
to
expand
data
rows
on
on
tables.
So
this
is
part
of
clarity.
We
just
exposed
it
now,
so
you
can.
You
can
leverage
it
with
your
plugins,
but
as
you
see
here,
it's
it's
the
these
data
rows
below
just
take
a
component,
so
it
can
be
anything
in
this
case.
A
It's
a
a
card,
but
that
can
just
be
free
form
text.
It
could
be
markdown,
it
can
be
really
any
any
component
will
render
there
so
use
your
use,
good
judgment
when,
when
you're
nesting
things
in
there
that,
like
generally
it's
it's
it's
you
know,
I
don't
know
that
I
would
slam
another
table
in
there,
but
I
think
you
probably
could
so
yeah.
This
is
this.
Has
all
the
features
exposed
that
you
would
expect
trying
to
find
the
actual
config
entry
for
the
expand
there?
A
It
is
expandable,
so
there's
a
new.
We
have
helpers
for
all
of
this
in
the
in
the
plug-in.
Libraries,
at
least
on
the
go
side,
probably
need
a
pr
on
the
javascript
side
to
add
the
easy
ability
to
an
expandable
row,
but
it
has
so
there's
this
new
expand
field,
similar
to
how
we
do
actions
where
you
can
do
underscore
actions
and-
and
you
get
the
the
actionable
items
on
the
table.
A
If
you
haven't
seen
that
it
looks
like
this
where
so
that's
that's
from
us
underscore
actions,
or
I
think
it
is
hunting,
underscore
expand,
and
then
I
believe
this
I
don't
know
what
this.
What
does
this
flag
do?
Set
it
to
true,
oh
yeah,
so
the
the
columns
you'll
notice,
when
you
replace
so
there's
the
ability
to
expand
and
keep
the
columns
or
expand
and
just
completely
replace
the
columns
so
now
that
that
3
4
they
disappear.
A
When
you
see
the
content,
that's
that's
nice
for
when
it's
a
full
context,
switch
right
where
you're
like
hey,
expand
this.
Now.
Here's
the
details
of
this
thing.
You
don't
need
any
of
the
column
data
to
deal
with
this
contextual
thing
right
here
in
front
of
you.
It
also
just
kind
of
cleans
up
some
of
the
space
for
for
use
so
trying
to
think
what
else
is
on
this
expandable
road
config
sam
was
that
was.
Was
there
another
item?
I
feel
like
I'm
missing
something.
C
That's
pretty
much
it
like.
You
can
also
mix
and
match
a
bunch
of
the
stuff,
so
you
could
hypothetically,
have
grid
actions
with
expandable
rows
and
it'll
do
exactly
like
you'd
expect,
although
it
would
get
a
little
busy.
C
Other
things
that
are
interesting
here
that
we
might
potentially
want
was
like
maybe
someday
we'd
like
to
add
more
filtering
capabilities
like
right
now.
If
you
throw
content
inside
of
the
grip
of
the
expandable
row
there,
nothing
really
knows
what
it
is,
but
you
know
I
don't
think
that's
a
high
priority
thing,
but
it
could
be
something
that
we'd
want.
Something
else
to
potentially
call
out
is
that
this
is
used
in
the
context
of
a
well.
C
Let
me
stay
back
so,
like
clarity,
has
the
concept
of
a
data
grid
and
a
table,
and
this
is
used
in
the
context
of
a
data
grid,
so
it
has
the
pagination
on
the
bottom
right,
and
you
have
that
filtering
things
this.
As
far
as
I
remember,
this
is
not
implemented
for
plain
old
tables,
so
in
other
words,
if
you
just
want
a
regular
simplified
table
like
so,
you
don't
get
any
of
the
expanding
or
action
capability,
but
that's
an
implementation
detail
like
for
the
most
part.
A
Yep,
okay,
great
and
okay,
yeah.
Thank
you
again,
sam
for
adding
that
in
that's
very
useful.
We
also
have
now.
I
know
milan
demoed
this
at
the
at
the
last
community
meeting,
but
it's
it's
in
now
the
some
small
tweaks
to
to
style,
but
you
can
see
that
there's
a
new
new
styles
on
the
resource,
viewer,
smoother
edges,
clean
icons,
nice,
readable
font.
You
know
it's
yeah,
we're
really
pleased
with
how
it
came
out.
We
made
we
made
some
compromises,
not
compromises.
A
We
we
wanted
to
ensure
some
accessibility
and
to
do
that.
We
weren't
able
to
use
like
any
pie
in
the
sky
colors
we
wanted.
But
ultimately
I
think
we
came.
A
We
came
to
some
good,
reasonable,
color
settings,
good
saturation
levels
and
it's
very
readable
and
viewable
both
in
dark
and
light
mode,
and
it
just
it
just
kind
of
cleans
things
up
right,
like
milan,
did
add
a
feature
which
I
can't
show
in
the
storybook,
but
we
can
show
in
live
octane
where
you
can
actually
double
click
these
now
it
was
he
he
demoed
that
last
week
too,
but
so
anything,
that's
anything
that
doesn't
have
multiples
being
associated
with
it.
A
You
can
double
click
and
it
will
go
to
that
link
that
you
normally
would
have
to
expand
and
click
to
get
into,
and
then
even
even
in
views
that
are
really
busy
just
the
color
change
to
me
like
yes,
this
is
still
really
busy
and
it's
really
hard
to
like
make
heads
or
tails
of,
but
I
find
it
less
offensive
and
just
the
the
the
aesthetic
changes
are
pleasing
to
me
enough
that
I'm
like!
Oh
okay,
let
me
let
me
dig
around
in
here
and
before
it
was
just
like
here's.
A
B
No,
I
think
that's
that's
way
better
than
I
demo
it
last
week.
Thank
you.
I
I
think
it's
a
great
first
step
so
excited
to
to
see,
especially
you
know,
on
a
as
you
said,
a
busy
grass.
You
can
do
better
than
that,
and
we
talked
about
that.
So
a
lot
of
cool
stuff,
hopefully
coming
in
future
as
well
yeah.
A
Yeah
so
for
front
end
changes
I'm
trying
to.
Let
me
see.
A
Oh
yeah,
this
was
this
is
not
in
the
current
release
but
luis
removed
the
resource
age
column.
When
it's
not
necessary,
it
was
like
a
duplicate
column
that
would
show
up.
I
wonder
if
it's
in
our
our
sandbox
example.
Actually,
no,
but
you
would
get
an
age
column
twice
in
certain
cases
if
the
resource
defined
their
own,
we
would
also
pull
the
api
one
and
show
them
both
and
this
now
we
we
just
show
one.
So
that
was
a
nice
nice
cleanup
change.
A
I
don't
have
anything
prepped
for
this,
it
might
be,
might
be
hard
to
do
on
the
fly,
but
I'll
try.
So
the
anyway.
C
Yeah
this
this
might
actually
be
broken
now,
because
it's
an
api
change
to
the
validators
and
just
looking
at
the
schema
right
here
right,
that's
like
taking
in
a
required
as
an
array,
whereas
now
it's
a
mapped
value.
A
A
It's
yeah-
I
was
just
merged
in
this
morning
too,
but
yeah
we'll
get
that
story
updated.
That's
the
story
updates
get
pushed
out,
as
I
mentioned
at
the
start
of
this
story,
updates,
get
pushed
out
when
they
when
they
land,
so
that's
not
a
block
for
the
release,
but
so
I'll
just
talk
about
what
happens
now
previously
and
I
can
pull
up
the
I
can
pull
up
the
the
pr
here
as
well.
A
So
previously,
what
would
happen
is
when
you
ran
through
validators,
specifically
with
the
stepper.
You
could
only
set
a
single
validator
and
you
could
not
really
provide
it
with
with
data
in
a
useful
way
in
the
old
way
that
the
stepper
worked.
So
louise
refactored
this
so
that,
essentially
everything
all
of
these
validators,
I
believe,
except
for
composing,
compose
async-
is
that
correct
all
of
them
except
those
two.
D
Well,
all
of
them
received
a
value,
but
actually
there
are
just
like
five
of
them
that
you
can
pass
like
min
max
email.
I
know
you
may
not
mean
length
max
length
yeah,
it's
like
five
of
them
that
you
can
modify
yeah.
A
Yeah,
so
what
we
did
is
is
or
what
here
here
we
go
right
here.
So
this
is
the
list.
We
have
the
static
list
of
validators
now
that
you
can
use
and
so
min
max
required
required
to
etc.
These
can
now
be
set
as
as
multi
like
you
can.
You
can
do
a
group
of
validators
for
four
fields
which
you
could
not
do
before,
and
then
you,
you
can
also
set
their
expected
properties
or
values
to
validate
against.
A
So
I
can't
demo
it
in
storybook,
as
sam
pointed
out,
we
need
to
make
that
schema
change
there,
but
we
louise
created
this
set
of
of
constants
that
make
it
easy
to
kind
of
integrate
and
use
them
we'll
we'll
get
those
mirrored
over
on
the
typescript
plugin
side
as
well,
and
I
think
this
overall
is
just
a
it's,
a
good
enhancement
to
the
next
step
for
the
stepper,
which
would
be
per
action
or
per
step
actions.
A
So
it's
kind
of
on
that
path
of
like
okay.
How
do
we?
How
do
we
make
this
thing
deal
with
multiple
types
of
validation?
Okay,
right
now?
How
do
we
make
it
deal
with
synchronous
validation?
Where
it's
a
round
trip
to
the
server
and
back
and
that'll
be
part
of
our
forms
refactoring
as
well,
which
is
going
to
be
in
the
0.19
release.
So
this
is
kind
of
like
similar
to
the
icon
component.
A
It's
like
a
step
in
that
direction,
to
bring
us
to
more
feature-rich
capabilities
within
octan,
so
yeah
really
good
work
on
that
luis.
A
The
tooltip
size
on
labels
to
avoid
hidden
labels-
I
don't
know
if
that's
anywhere
in
storybook,
but
that
was
an
error
like
an
issue
where
the
tooltip
would
just
like
overflow,
everything
and
and
hide
labels,
and
when
you
hovered
on
it
like
it
would,
if
you
had,
if
you
had
a
tool
tip
for
your
labels
and
you
hovered,
it
would
hide
them
all
and
it
made
them
made
them
hard
to
click
the
the
ones
that
got
hidden.
So
that
updates
that
we
talked
about
the
resource
viewer.
A
A
He
extended
the
the
plug-in
api
so
that
the
the
context
that
is
used
to
make
requests
to
the
server
can
get
metadata
added
to
it,
so
that
when
you,
when
you
have
custom
implementations
of
octant
or
your
your
another
example,
be
like
you're
writing
tests,
where
you
want
to
like
test
that
a
plug-in
actually
does
go
end-to-end
with
its
data
into
octant.
You
can.
A
You
can
now
do
this,
which
couldn't
do
before
some
of
the
use
cases
for
that
are
like
custom
data
stores
where
you
want
to
put
in,
like
a
token,
like
an
auth
token,
or
something
like
that
to
allow
you
to
go
access,
a
data
store
where
maybe
you
don't
want
to
you
like
you
want
that
baked
into
the
code
in
a
way
that
is
not
hard
coded
into
octane,
so
add
action
to
timeline
step.
What
is
this?
A
Oh,
oh
yeah,
yeah
yeah,
so
the
timeline
component.
That's
a
new
one
too!
I
don't
think
we
did
we.
I
don't
know
if
we
showed
that
maybe
we
did
sam
yeah
sam
was
that
correct
added
this
one
too
yeah
sam's
been
on
a
component
terrier.
Lately
he
did
the
demos
for
how
to
add,
create
new
ones
and
then
was
just
like
that's
fresh
online,
I'm
gonna
add
a
bunch
of
components.
A
So
this
is
the
timeline
component.
It
supports
all
of
the
the
clarity
steps
and
and
like
vertical
alignment,
horizontal
alignment-
you
can
add
the
button
groups
to
it.
Those
buttons
can
have
actions
with
confirmations.
So
if
you
have
a
step
that
you
need
to
retry,
you
can
have
that
spire
in
action
back
into
octane.
Octane
can
listen
for
that
event
and
then
do
or
your
plugin
can
listen
to
that
event
and
then
do
what
it
needs
to
do
to
initiate
the
retry.
A
All
of
the
steps
have
the
standard
setup
state.
It's
like,
I
think,
fail.
No
air
aired.
No,
oh
man,
embarrassing.
Let's
see
where
is.
A
C
You
want
to
go
to
the
api
tab
on
the
top
and
there
is
going
to
be
a
bindings
for
clarity
state,
and
so
you
have
not
started
current
processing
success.
A
A
Refresh
the
page,
that's
what
it
is
always
just
always
refresh
all
right,
it's
processing,
that's
good
processing
is
good
success.
Hey,
okay!
Look
at
that
error!
Yeah!
I
don't
know,
I
don't
know
what
happened.
I'm
blaming
browsers,
so
yeah,
all
of
the
oh
yeah
back
to
what
we
were
doing
all
of
the
the
states
are
supported
current
processing,
success,
error
and
then
also
the
standard.
The
header
title
descriptions.
A
Those
are,
those
are
what
you're
seeing
here
header
I
believe
step
is
the
title
and
then
that's
the
description
and
then
there's
a
toggle
to
make
this
thing.
What's
it
called
there's
a
toggle
to
make
it
vertical.
I
believe.
A
Oh
no,
I
want,
I
want
docs,
there
we
go
vertical,
varian
should
just
guessed,
it
would
have
been
so
much
cooler.
If
I
would
have
just
guessed
and
then
everyone
would
be
like.
Oh
makes
sense.
A
Vertical
there
we
go,
and
so
now
you
see
it's
vertical
and
I
I
believe
well,
it
normally
the
the
resize
isn't
captured,
but
I
believe
that
if
the
I
believe
it,
it
just
fills
the
space
that
it's
that
it's
provided.
So
if
I,
if
I
redo
that
up
here.
A
Nope
nope
come
on
what
vertical
true,
maybe
not.
I
don't
know
why
it
does,
though,
I've
seen
it.
I've
used
it
in
in
flex,
layouts
and
it
it
fills
the
there's,
probably
just
some
box
here,
binding
it
into
that
size,
but
it
does
fill
the
space
so
that
thank
you
for
that,
sam,
that's,
a
great
great
addition.
I
think
there's
definitely
some
plugins
out
there
that
are
are
interested
in
in
taking
advantage
of
this
so
and
I
think
yeah
I
can.
A
That's
the
timeline
component
metadata,
oh
yeah,
another
one
from
from
sam,
which
is
plugins.
This
has
been.
This
is
an
outstanding
request
for
a
while,
and
this
is
plugins
can
now
add
multiple
tabs.
A
Well,
plugins
can
add
multiple
tabs.
The
way
it
works
is
is
it's
an
api?
A
It's
a
api
extension,
so
your
existing
your
existing
plugin
will
continue
to
work
and
render
a
single
tab,
but
you
can
now
register
multiple
tab
handlers
on
the
go
side
where,
as
you
see
here
in
the
example
where
sam
has
registered
these
three
tab
handlers,
those
tab
handlers
all
work
with
the
same
set
of
capabilities
that
you've
registered.
So
you
don't
get
to
divorce
the
capabilities
that
you're
plug-in
the
like
the
gbk
that
your
plug-in
handles
from
the
tabs
that
you
render,
but
you
do
get
to
say
I
handle
like.
A
I
have
multiple
tabs
that
I
can
render
and
inside
those
tabs.
If
you
wanted
to,
you
could
check,
you
know,
check
the
the
type,
that's
the
request,
type,
that's
being
given
to
you
and
then
maybe
not
do
a
thing,
but
generally
speaking,
you're
going
to
want
to
use
this
when
it
is
your
intention
that
you
want
to
render
two
tabs
for
pods
or
two
tabs
for
a
k,
native
serving
object
or
t
like
it's.
The
intention
here
is
that
you
want
to
render
multiple
tabs
for
the
type
of
object.
A
This
was
a
request
that
came
in
from
daniel
who
is
the
author
of
the
starboard
plug-in
and
had
a
use
case,
a
very
good
use
case
where
it
was
like.
We
have
this.
He
has
a
vulnerabilities
tab,
but
then
also
being
able
to
show
the
configuration
audit
tab
on
the
same,
because
it's
for
the
same
object
so
on
the
same
screen
so
being
able
to
show
both
of
those
was
was
kind
of
the
driver
there.
I
think
it
makes
a
lot
of
sense.
There's
other
there's
other
use
cases
for
warming
to
extend.
A
Have
your
plug-in
extended
object
with
multiple
tabs.
So
that's
that's
in
node.18,
and
we
enabled
that
both
in
the
plugins
the
javascript
and
go
side
so
that
that's
the
javascript
api
is
slightly
different.
It
uses
the
tab,
the
multiple
return
types
that
are
essentially
supported
by.
A
I
think
I
have
a
a
test
that
kind
of
shows
it
all
right
here,
so
this
tab
handler
it
can.
It
can
either
return
a
single
tab
response
or
multiple
tab
responses.
So
you
know
here
it
uses
the
create
tab
response
helper
to
build
out
two
tabs.
So
that's
just
taking
advantage
of
kind
of
more
typescript
patterns
that
you
would
expect
where
the
return
type
of
a
function
can
be
ored.
A
So
it's
it
returns
a
tab
response
or
a
list
of
tab
response
that
was
a
little
more
intuitive
on
the
javascript
side
than
having
to
register
multiple
tab
handler
functions,
mainly
because
the
javascript
side
doesn't
do
registration,
the
same
way,
the
go
side.
A
Does
the
javascript
side
does
a
dependency
injection
pattern
where
it
goes
in
and
actually
fetches
the
function
out
of
the
code
and
then
runs
it
instead
of
you
registering
your
function
with
the
endpoint
and
then
it
being
dispatched
to
so
that's,
ultimately,
that's
how
that
ended
up,
but
it
works
well.
A
And
I
think
go
back
and
look.
I
think
that
covers.
I
think,
that's
that's
all
of
the
features
and
updates,
oh
and
then
the
the
speed
improvements
so
there's
outstanding
pr,
which
I
think
will
land
today
and
be
in
0.18,
which
is
the
memory
caching
for
the
crd
navigation
entries.
A
I
need
to
take
another
pass
at
it,
but
it's
looking
good
and
so
that
that'll
be
in
for
0.18
as
well,
and
that
was
related
to
the
work
we
talked
about
last
week,
which
is
generally
speeding
things
up,
there's
a
few
things
that
that
won't
be
in
order
18
that
we
were
looking
at,
maybe
getting
in
the
being
able
to
to
generate
links
for
components
from
the
go
plug-in
side
similar
to
how
you
can
for
the
javascript
side.
A
I
think
we're
gonna
that
that'll
be
pushed
to
o.19
the
button
styling
and
link
options
for
the
for
the
text
and
link
or
for
the
link
components
will
be
pushed
to
0.19
and
I
think
that's
yeah.
A
We
got
most
of
the
things
in
there,
so
these
are.
These
are
what
we
we
didn't
get
to
the
form
stuff
I
mentioned
previously.
That
we'll
be
I'll,
be
focusing
on
for
that
for
the
next
release
so
and-
and
I
think
that's
yeah-
I
think
that's
it.
That's
all
I
does
anyone
want
to
add
anything.
I
missed
talk
about,
highlight
something
demo,
something
show
anything
before
I
move
on
to
talking
about
kind
of
the
the
plan
for
oda,
19
and.
C
I
think
the
only
thing
to
call
out
based
on
the
changes
that
we
just
talked
about,
is
that
the
only
breaking
api
change
is
that
I'm
aware
of
I
could
be
wrong.
I'd
have
to
go
through
the
change
logs
again,
but
it
should
be
just
the
validators
as
that
changes
the
inputs
from
just
taking
an
array
of
validators
to
a
map,
everything
else,
including
the
yeah.
Everything
else
here
looks
like
it's
not
breaking.
A
Yep,
that's
a
good
call
out
sam.
Thank
you.
I
will
we'll
be
sure
to
highlight
that
in
the
release
notes
section
I
I
don't
know
that
many
folks
are
using
the
stepper
yet
anyway.
So
I
think,
as
we
continue
to
improve
it,
more
people
will-
and
I
think
the
yeah
I
think
we
should
be
okay
for,
but
if
you
do
run
into
issues
while
you're
using
it
please
reach
out
in
the
octan
channel,
and
we
will
get
you
helped
out
migrating
to
the
new
to
the
new
format.
A
A
All
right,
so
we've
got
about
26
minutes
left
in
our
scheduled
block
of
time,
and
what
I
wanted
to
do
is
see
if
there
was
any.
Let's
see
if
there's
any
questions
online
anywhere,
nope
nope,
okay,
so.
B
What
I
want
to
show
yeah
go
ahead.
Sorry
I
put
the
question:
we
can
do
it
at
the
end
too
about
the
it's
just
the
thought.
You
know
it
seems
that
it
might
be
a
little
easier
for
us
to
make
a
plug-in
library
and
octant
in
sync.
B
If
we,
if
you
bring
them
together
and
especially
with
the
mpm
7.0,
can
have
different
workspaces,
so
I'm
thinking
might
be
a
good
idea
to
to
kind
of
merge
those
two
together
inside
like
monorepo
and
and
so
we
can
make
them
easy
and
sync
and
release
them.
At
the
same
time,.
B
A
There's
something
to
think
about.
I
don't
really
think
it'll
make
it
any
easier
right
like
like.
I
think
I
think
it's
probably
just
a
problem
now
of
like
out
of
sight
out
of
mind
versus
like,
like
all
of
the
steps
you
would
have
to
take,
to
keep
it
up
to
date.
Release
new
npm
versions,
make
sure
it
stays
in
sync.
Are
the
exact
same?
They
just
happen
in
another
repo
right
now,
right
so
yeah.
A
I
see
what
you're
saying
the
benefit
of
it
being
another
repo
is
that
it
can
also
have
its
own
set
of
owners,
which
there
are
there's
there's
like
a
they're,
slowly,
building
up
a
plug-in
library
community,
like
all
they
care
about,
is
the
typescript
plug-in
libraries
and
and
and
the
stuff
there
as
long
as
we
don't
break
the
octane
api
that
they
talk
to,
they
don't
care
about
octane
and-
and
I
think
we
could
probably
by
keeping
at
its
own
repo.
A
We
can
then
make
that
a
more
like
the
entry
point
into
that
repository
and
like
the
scope
and
and
like
what
they're
focused
on,
can
stay
really
tailored
to
that
plug-in
library.
But
I'm
I'm
willing
to
I'm
willing
to
consider
the.
I
guess.
What
I
would
say
is
it's
kind
of
just
been
neglected
a
little
bit
and
were
mainly
because
it
didn't
have
an
action
in
place
that
would
automate
the
releases
and
I
I
didn't
feel
like
cutting
releases
all
the
time,
but
now
it
has
actions.
A
So
you
can
push
a
tag
and
it
pushes
a
new
release,
which
is
a
which
is
like
a
huge
like
having
that
automated
is
in
and
of
itself
is
like
a
big
big
deal
so
just
from
a
maintenance
side.
A
So
I
think
I
would
say,
let's
see
how
it
goes
for
the
next
like
two
releases
and
if
we're
still
experiencing
a
lot
of
drift
and
a
lot
of
like
misses
on
updates,
then
I
think
bring
it
in,
so
that
it's
like
in
our
face
and
in
front
of
us
and
figure
out
how
we
still
or
maybe
yeah
yeah.
I
think
I
think
that
would
be.
That
would
be.
The
approach
I'd
want
to
take
is
like
see
how
we
do
over
the
next
couple
releases.
A
Now
that
there's
some
actions
in
place
that
automate
it
and
some
test
harnesses
in
place
to
get
some
of
the
stuff
under
test
and
then,
if
we're
still
having
a
lot
of
drift,
then
yeah,
I
I
think
bringing
it
in
would
be
good
and
then
we
can
always
always
extract
it
back
out
right
like
if
we
bring
it
in,
like
things,
are
going
good,
we're
keeping
it
up
to
date.
It's
got
its
own
cadence.
It's
got
its
own
like
community
around
it.
Then
we
fork
it
back
out.
B
A
You
know
the
other
thing.
This
is
something
that
we
could
add
to
like.
Maybe
our
our
ci
cd
as
an
idea,
is
if,
because
we
kind
of
do
this
now,
where,
like
we
scan
the
area
of
the
code,
that
that
has
been
changed
and
and
we
could
kind
of
enhance
that
a
little
bit
and
say
like
if
it's
an
air
like
if
it's
in
package
view
components
or
if
it's
in,
I
guess
yeah.
If
it's
in
package
like
package,
plugin
or
package
view
components.
A
If
there's
changes
there,
then
on
the
like
in
the
because
I
think
we
can
generate
like
checklists
like
a
comment
or
something
that
says
like
does
this
require
basically
like?
Does
this
require
plug-in
library
changes?
Does
it
like
just
have
like
a
so
then
it's
in
your
and
you
like,
you
have
to
like
check
it
off
and
say
yep.
It
does
like
no,
it
doesn't
or
yes,
it
does
as
just
a
reminder
for
changes
like
that.
A
E
I
mention
this
really
quickly,
because
I
had
a
similar
idea
on
the
same
lines,
but
not
in
terms
of
organizing
code
but
having
like
a
very
simple
kind
of
test,
which
would
exactly
actually
run
something
like
a
yeoman
generator
just
to
generate
a
plug-in
and
run
it,
and
it
could
be
as
simple
as
just
running
a
local
like
local,
locked
in
and
installing
plug-in,
because
I've
had
issues
where
everything
works,
because
everything
is
just
like
rendered
based
on
the
templates,
but
we
I've
never
actually
run
it
so
to
to
begin
like
you
could,
just
like
you
know,
just
install
a
plug-in
using
human
and
see
if
that
works
correctly
and
then
later
on.
E
E
A
Yeah
yeah,
I
mean
I
like
that
idea.
I
like,
and
I
I
know
sam-
has
brought
this
up
a
few
times
as
well,
just
general
testing
ideas
around.
How
do
we
get
our
plug-in
apis,
like
end-to-end
tested
and
under
test
and
like
even
even
to
a
degree?
How
do
we
get
octant
under
like
actually
talking
to
an
api
and
under
test,
and
one
of
the
things
that
kind
of
makes
this
easier
is
the
fact
that
we
can
now
plug
in
our
own?
A
We
can
plug
in
an
object,
store
and
plug
in
our
own
cluster
client,
which
can
just
return
fake
data
to
the
calls
which
will
allow
octan
to
start
and
a
lot
like
like
if
we
one
of
the
thoughts
I
had
was
like
just
essentially
recording
recording
the
api
calls
similar
to
like
what
you
do
for
there's,
there's
like
a
few
libraries
out
there
for
like
testing
various
cloud
providers
where
you
enable
it.
A
You
do
the
calls
you
want
it
records
the
api
calls,
and
then
you
turn
it
off
instead
of
record
mode,
it's
in
replay
mode
and
then
in
replay
mode.
It
it
it
just
is
is
exactly
that
a
replay
of
all
the
events
that
happened
while
you
were
recording
and
for
the
purposes
of
testing.
That
seems
like
perfect
for
what
we
want
right,
like
record
a
set
of
actions,
it's
very
much.
What
was
that
browser
testing
framework
where
you
would
go
and
actually
like
record
your
clicks
and
then
play
them
back.
B
A
Selenium
yeah
yeah
like
selenium
right,
like
where
you
go
through,
and
you
like.
You,
record
everything
and
then
play
it's
that
but
for
api
calls,
and
I
think
that
would
probably
be
easier
than
trying
to
like
spin
up
kind
or
run.
Maybe
it's
not
anymore,
but
I
know
originally
when
we
were
trying
to
like
stand
up
a
kind
cluster
or
a
mini
cube
cluster
and
then
have
octan
talk
to
it
and
then
assert
that
what
assert
that
the
ui
of
octet
was
doing
the
right
thing.
E
A
Yeah,
I
agree
if
you
are
excited
to
do
that
vikram.
I
would
encourage
you
to
open
an
issue
and
yeah
or
and
start
or
a
discussion
either
one
and
start
to
describe
like
how
you
might
attack
this
problem
and
we
can
iterate
there
and
then
because,
like
the
moment,
we
kind
of
have
consensus
on
how
we
want
to
attack
the
problem
like
it's
going
to
be
a
priority
for
whoever
wants
to
work
on
it
like
it's.
It's
something
we've
been
kicking
around
a
long
time,
but
just
haven't
done
yet.
E
A
Okay,
so
yeah
good
question
milan
that
generates
some
good
discussion
before
we
move
on.
But
and
I
talk
about
019-
is
there
any
other
things
for
the
open
q,
a.
A
Okay
I'll
circle
back
to
it
at
the
end
and
see
so
we're
gonna
kind
of
shorten
up
this
next
release
and
and
target
it
for
april
7th.
So
don't
expect
a
lot
of
big
features
in
it.
What
we're
mainly
doing
is
is
we're
going
to
focus
on
getting
some
of
those
last
little
bits
of
form
updating
into
the
release.
A
We
want
to
get
some
some
of
the
final
bits
of
like
the
component
updates
and
and
integrating
that
new
icon
component
into
octane,
and
then
we
also
will
take
this
time
to
address
some
of
the
issues
that
we've
been
putting
into
our
product
excellence
backlog.
A
A
Our
are
tech
debt,
essentially
like
things
that
that
are
not
easily
like
demo-able
or,
like
hey,
look
at
look
at
what
you
get
now,
because
we
did
this,
but
the
long-term
health
of
the
project
and
the
overall
experience
that
you
get
release
after
release
improves
as
we
address
these
product
excellence
things
so
and
then
any
bugs
that
do
shake
out
from
dot
net
from
0.18
will,
if
they're,
if
they
get
reported
within
the
the
next
couple
weeks,
we'll
also
get
those
those
addressed
so
a
little
bit
shorter
sprint,
not
as
much
features
more
of
just
like
a
I
wanted
to
get
out
of
the
essentially.
A
What
this
is
I
wanted
to
get
out
of
the
habit
of
being
like,
oh
no,
oh
dot.
18
is
not
ready,
we're
going
to
push
till
next
week.
Oh,
it's
not
right.
Instead,
like
we'll
cut
what
we
have
and
then
and
then
we'll
do
a
shorter
one
and
cover
what
we
have
like
like
it's
just
a
it's
a
more
iterative
process.
It
feels
a
little
better
to
actually
be
releasing
things.
A
It
gets
us
into
a
nice
cadence
and
a
nice
rhythm
and
with
the
larger
team
it'll
be
important
that
we're
doing
our
releases
on
more
on
a
you
know,
on
a
schedule
as
we
can
like.
A
It's
obviously
not
a
rigid
schedule,
but
you
know
the
amount
of
the
amount
of
work
that
we're
able
to
complete
now
in
a
shorter
period
of
time
is
enough
to
warrant
a
release,
and
you
know
honestly,
when
it
was
myself,
sam
and
milan
for
a
while,
it
would
take
us
a
while
to
get
enough
things
to
warrant
to
release
it'd
be
like
we'll
wait
a
week,
because
we
don't
really
have
enough
yet
so
with
the
team.
A
Doubling
it's
it's
as,
as
you
saw
just
from
this,
this
release
cycle
0.17
to
0.18
was
much
shorter
and
the
amount
of
features
we
got
in
much
much
higher,
and
this
is
with
you
know
many
members
of
the
team
onboarding
during
that
period
of
time
as
well
right
who
are
all
doing
excellent
by
the
way.
A
So
thank
you
to
all
the
new
members
of
the
team,
luis
vikram
felipe
doing
an
amazing
job,
and
thanks
to
milan
and
sam
for
onboarding
and
and
being
patient
and
pairing
and
and
and
helping
to
get
everyone
on
board.
It's
been.
It's
been
really
great
so
far,
so
I
really
appreciate
the
the
effort
from
everyone
so
with
we
have
13
minutes
left.
A
I
I
think
what
will
the
the
what
I'll
do
right
now,
so
the
team
is
going
to
plan
0.19,
which
is
basically
just
going
to
be
a
shift
like
some
of
the
things
we
didn't
get
in
order.
18
like
this
thing,
this
ain't
going
to
be
a
no
doubt.
19.
like
like
these
two
right
here
who
are
we
kidding
like
I'll,
just
move
those
I'll
move,
those
down
to
20
right
now,
because
it's
not
this
is
not
going
to
happen
yeah.
A
No,
so
what
we'll
do
is
I
want
to
go
through
quickly
for
the
for
the
community
kind
of
what
we're
planning
for
19
and
then
the
team
will
take
offline
and
we're
going
to
add
some
context
to
issues
probably
tomorrow,
just
so
that
each
member
of
the
team
can
easily
go
in
and
like
tackle
an
issue
and
and
solve
it.
A
We
had
kind
of
trouble
with
some
of
our
issues,
this
last
sprint,
where
they
just
didn't,
have
enough
context
and
enough
detail
to
make
them
like
you'd
start
on
them
and
then
halfway
through
you'd
realize.
Oh,
this
is
wrong
or
oh,
I
gotta
shift
directions
and
a
little
frustrating
on
some
of
them
for
the
people
who
are
working
on
them.
So
to
avoid
that
we're
gonna
we're
still
gonna
plan
our
releases
publicly
and
then
separately,
either
in
the
in
the
channel
or
or
synchronously
in
a
separate
video.
A
We're
gonna
just
add
that
context,
but
that
context
will
be
added
to
the
issues
as
comments,
so
everyone
can
see
them
we'll
also
be
doing
some
of
the
good
first
labeling
or
good
first
issue.
Labeling
in
that
process,
as
like
things
fall
out
and
we
move
them
to
different
releases
so
expect
to
see
some
some
traffic
and
activity
on
the
on
the
issue
board.
A
A
I
think
I
mean
I
honestly,
I
think
my
summary
covered
it
right
like
we're,
shortening
it
up,
focus
on
on
getting
form
updates
in
there,
product
excellence
bugs
and
and
our
product
excellence
stuff
protected
and
then
any
bugs
tomorrow
at
18..
If
there
is
an
issue,
that's
really
important
to
you
and
it's
and
and
you
go
and
you
look
at
no.19
and
you
don't
see
it
comment
on
the
issue
and
say:
hey:
is
this
something
that
you
all
can
do
for
odon19
and
and
we'll?
A
Let
you
know
in,
and
I
would
say
anything
that
anything
that
that
gets
a
comment
between
now
and
the
next
community
meeting
is
a
maybe
after
after
next
community
meeting.
If
then,
it'll,
definitely
just
it'll
have
to
wait
until
about
20..
So
get
your
get
your
feedback
in
there.
Now,
if
there's
anything,
that's
important
to
you,
we
will
we'll
try
to
see
if
we
can
get
it
into
this
shorter
cycle.
But
again
it
is
a
shorter
cycle.
So
april
7th
is
the
target
product
19.
A
A
Well,
I
again,
I
appreciate
everyone's
everyone's
hard
work
on
this
release.
Look
for
it
later
today,
folks
and
yeah,
we'll
we'll
set
up
some
time
to
plan
our
our
odot
19
and
add
context
to
the
issues
I'm
going
to
start
moving
some
things
into
there,
so
that
we
we
have
a
backlog
to
we'll
just
set
up
a
meeting
and
go
down
each
one
and
and
make
sure
that
they're
they're
ready
to
be
worked
on,
but
so
watch
out
for
that
from
me
and
that's
all
I
have.