►
From YouTube: Octant Community Meeting - June 2nd, 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
So
this
is
not
today.
A
Cool
all
right
now,
we're
now
here,
so
all
right.
Well,
we're
just
gonna
get
started
and
go
down
the
agenda
here
so
june,
2nd
2021,
hello,
everyone
welcome!
This
is
going
to
be
the
first
october
meeting
in
june.
Half
the
year
is
almost
over,
so
I
guess
the
first
item
on
the
agenda
that
we
want
to
talk
about
is
to
welcome
kara.
She
is
the
new
manager
of
the
acting
team
and
she
would
like
to
have
a
few
words
to
introduce
yourself.
That'd,
be
awesome.
B
I'm
sure
I'm
super
excited
to
be
here.
My
name
is
kara.
I
just
joined
yesterday,
so
I'm
very
much
in
listen
and
learn
phase
yeah,
that's
about
it.
I've
been
with
vmware
for
nine
years,
so
I've
just
transitioned
and
and
super
excited,
so
just
taking
in
all
the
information
as
quickly
as
I
can.
A
Awesome,
thank
you,
and
this
is
pretty
cool,
because
vmware
is
investing
more
resources
in
open
source
and
specifically
often
and
we've
seen
the
team
grow,
and
so
hopefully
over
time
can
make
auckland
a
more
robust
tool
and
also
just
be
able
to
have
more
people
to
branch
out
into
different
areas
of
focus,
so
super
exciting
stuff,
all
right
cool.
The
next
item
on
the
agenda
I
want
to
talk
about
today
is
something
that
came
out
of
an
issue
or
a
bug.
A
That's
been
in
often
for
two
releases
now
this
is
two
four
nine
eight
fixed
bug
where
actions
are
not
passed
to
components
right.
So
the
idea
here
is
that,
oh
is
chrome,
frozen
chrome
might
be
frozen,
come
on.
Oh
no,.
A
I
think
the
modern
pattern,
or
not
modern,
but
the
pattern
that
we
tend
to
prefer
now
is
to
attach
actions
to
things
that
users
interact
with
like
buttons
and
any
type
of
toggles
forms
and
such
and
so
given
that
consideration,
I
want
to
start
the
discussion
here
in
public
to
ask
if
we
want
to
keep
this
as
part
of
a
component
api
moving
forwards
to
1.0.
A
There
are
a
few
things
to
consider
here.
The
first
one
is
that
it
will
require
a
refactor
to
the
card
components
to
use
the
newer
pattern
where
we
manually
create
a
card
with
a
divider
and
a
new
button,
and
we
can
have
the
actions
work
this
way,
but
also
just
to
figure
out.
If
we
even
need
this
at
all.
A
So
we
can
certainly
refactor
this
out
and
over
and
it'll
certainly
simplify
the
code
base
by
saying
there
is
only
one
way
to
attach
an
action
to
a
component,
and
it
is
only
through
these
components
which
allow
actions
yeah
so
general
call
out.
Does
anyone
have
any
strong
opinions
about
this?
If
we
were
to
remove
this
prior
to
1.0.
C
C
You
know,
add
buttons
attach
the
buttons
attach
the
actions
to
the
buttons
type
thing
just
so,
instead
of
instead
of
completely
removing
the
feature,
just
kind
of
replacing
it
with
the
modern
equivalent
of
what
it
should
be.
As
you
were
saying,
like
attaching
actions
to
things
that
users
interact
with,
because
I
was
as
I
thought
about
this
more
and
I
went
back
and
looked
at
some
of
the
demos
we've
done
and
just
general
usage.
C
I
actually
have
used
this
not
recently,
but
I
like
in
the
past.
I
would
use
it
quite
a
bit
and
I
think
anyone
watching
some
of
the
demos
or
anyone
looking
to
quickly
like
tweak
knobs
on
a
deployment
or
some
other
resource,
that
we
expose
these
quick
edits
on
the
they're
likely
going
to
want
to
like
they're
gonna,
they're
gonna,
see
that
used
and
then
be
like
where'd
that
go.
So
this
is
kind
of
where
I'm
at
with
it
now.
A
Cool
yeah-
and
I
certainly
agree
with
that-
we've
definitely
used
we
yeah
when
we
first
implemented
this.
The
yama
editor
wasn't
a
thing
and
now,
given
that
it's
still
thing
there
is
value
in
keeping
these
knobs
over
time.
I
don't
know
if
there's
one
that's
preferred
within
the
more
recent
releases,
but
I
think
just
for
the
sake
of
making
sure
that
our
old
videos
are
valid.
I
think
that
is
a
reasonable
thing
to
keep
in
there
and
it's
not
too
difficult
to
transition
to
the
equipment.
A
I
think
I
think,
as
leah
mentioned
as
well,
this
does
affect
the
sample
plug-in.
So
there
there's
going
to
be
a
few
places,
federal
obamacare
changes,
but
nothing
too
complex.
A
All
right
cool!
Well,
if
there
is
nothing
else,
I
think
we've
already
made
up
our
minds
here,
so
we
can
move
on
to
the
last
bullet
point
before
open
q
a-
and
this
is
4.21.
So,
let's
see
we
can
go
to
our
projects
board
here
and
figure
out
what
work
is
stopping
us
from
0.21.
So
just
a
quick
reminder
for
anyone
watching
this.
We
are
technically
targeting
the
release.
A
Yeah,
so
for
anyone
watching
this,
we
are
technically
targeting
the
release.
For
yesterday
today,
I
think
it's
possible
I'd,
say
unlikely,
we're
probably
looking
to
land
two,
three,
seven,
six,
the
horizontal
stacking
of
fields.
We
want
to
land
this,
so
we've
got
some
ambitious
things
going
and
I
think
these
are
in
reviews.
A
We
don't
really
have
code
freezes
or
anything
like
that,
but
there
are
certainly
and
probably
give
it
two
five
two
zero
as
well
and
yeah
like
if
these
are
pretty
cheap
to
review
and
move
forward.
I
think
that's
fine
and
then
yeah
so
we've
got.
We've
got
quite
a
few
pr's
remaining
to
land.
That's
said
for
any
remaining
worker,
no,
not
to
one.
I
think
we
can
pretty
much
the
existing
in
progress
work,
that's
not
being
reviewed.
I
think
we
can
move
the
rest
over
to.
C
There's
some
housekeeping
on
it.
That
needs
to
be
done.
I
can,
I
can
take
care
of
that.
Just
like
I
know
the
horizontal
stacking
is
in
review.
The
resource
viewer
wait.
Milan
is
the
expand
collapse?
No
that's
in
progress
right
that
didn't
that's
it.
That's
still
in
progress,
but
yeah.
C
To
22.,
okay
cool
yeah,
so
I
think
yeah.
I
think
everything
else
is
pretty
accurate.
Now
I
moved,
I
moved
one
over
yeah
looks
pretty
good.
Now.
A
Not
widows
there
you
go
cool
all
right,
so
yeah
we
can
clean
this
up.
We're
cert,
I
think
reasonable
target
like
realistically
speaking.
I
probably
see
this
more
towards
friday
honestly
and
we
can
certainly
adjust
the
cycle
of
these
states
to
match
up
with
what
our
normal
length
of
the
sprint
would
be.
So
we'll
do
some
housekeeping
with
the
boards.
We
don't
have
to
do
it
right
now,
but
we're
gonna
gear
up
towards
like
finalizing
four
to
one
pretty
much
now.
C
D
I'll
have
a
small
pr
for
21
there's
a
issue
with
the
with
the
file
upload
new
file,
update
upload
button.
Then,
when
used
inside
the
tabs
view-
and
I
discovered
that
yesterday
and
now
it's
a
very
small
fix-
I'm
just
doing
final
testing
on
that,
so
hopefully
to
help.
A
A
So
we'll
throw
this
as
a
new
target,
so
hopefully
yeah
it's
not
all
and
with
we
typically
have
a
lot
of
releases
delayed,
but
I
think
it's
I
think
we
this
one
is
particularly
ambitious.
I
think
it's
all
right
that.
C
Yeah
I
mean
there
was
there
were
some
larger
items
in
this
one
that
I
think
are
kind
of
important
to
it.
The
the
other
thing
which
we've
talked
about
in
past
community
meetings
of
just
getting
into
the
habit
of
picking
a
day
releasing
what's
landed
and
then
releasing
again
sooner
right,
instead
of
like
forcing
it
and
saying
like
we're,
delaying
21
we're
at
least
21.,
we'll
release
22
sooner,
but
every
time
I
think
about
doing
that.
C
I'm
like
well
issues
like
if
we
had
if
issue
60
number
65,
which
is
the
auto
update
client,
was
like.
If
we
had
a
good
solution
for
that,
then
I
would
be
on
board
with
just
cutting
when
we
cut,
but
without
auto
updating.
I
don't
want
to
put
that
that
extra
burden
on
the
user
to
go
and
redeploy
every
four
days.
A
A
All
right
and
we're
moving
on
to
open
q
a
so
anyone
have
questions
also
answered
at
youtube
on
this
alternate
laptop
here.
It
doesn't
look
like
there's
much
traffic
at
the
moment.
C
Yeah,
I
don't
think
I
have
anything
today.
C
Oh,
this
is
actually.
This
is
a
related,
so
liam
was
working
on
some
plug-in
the
typescript
plug-in
fixes
and
was
generating
a
new
version
there,
and
I
think
there
are
some
component
changes
in
upstream
that
are
going
to
land
with
the
tab
with
the
horizontal
stacking
of
fields
in
the
tab,
tab
component
nesting
or
tab.
C
It's
nested,
because
we
already
use
tabs,
but
it's
just
making
the
tab
component
a
component.
So
I
think
I
guess
my
question
there
is
we'll
probably
want
to
hold
off
on.
Is
that
a
question?
No,
that's!
Not
how
questions
start
we
statement.
We
want
to
hold
off
on
on
the
two
pr's
from
liam,
because
I
think
the
specifically
the
one
that's
regenerating,
the
set
of
components
is
probably
going
to
need
to
get
regenerated
after
tab
components
and
the
horizontal
stacking
of
fields.
Lance.
E
Yeah,
if
I
could
just
so,
I
think
that's
definitely
a
good
idea
for
the
the
octant
plug-in
for
typescript
the
current
pr
that
sam
is
looking
at.
That's
just
renaming
a
variable,
so
I
don't
think
that's
going
to
be
impacted,
yeah
by
any
other
new
components
being
added
or
modified
cool.
F
Yeah,
my
bad,
that
is,
the
wrong
repo
yeah,
the
yeah,
the
ts.
What
what
is
the.
C
Plugin
library
for
octant
yeah,
so
yeah
there's
a
pr
there
yeah,
that's
we'll,
since
we're
since
we're
doing
a
oh,
you
know
what
this
brought
up
a
thing.
I
was
thinking
about
this
as
I
was
looking
at
this
pr.
Do
we
want
to
just
go
ahead
and
jump
the
the
pr
num
the
version
numbers
on
our
plugin
library
for
octane
and
make
it
match
our
octant
release
numbers?
C
That
would
be
awesome.
I
think
yeah
like
like
there's
no
reason
not
to
people
just
install
the
latest
from
npm
anyway,
but
that
would
really
help.
I
think
that
would
help
us
like
when
someone's
posting
an
error,
and
they
say:
oh,
it's,
it's
0.22
is
where
the
error
is,
then
we
know
and
they're
using
octano.25,
but
hey
you're.
You
know,
go
update
your
your
library
instead
of
now
we're
like
what
what
version
of
octane
did.
We
use
to
generate
0.3.
E
C
Would
be
great
so,
let's
yeah,
let's
sam's,
linking
those
in
perfect
and
then
all
yeah
that
yeah
excellent.
That's
all
I
had.
A
Great
yeah,
I
think
version
numbers
are
arbitrary
things.
If,
if
it's
helpful
then
change
it
yep.
C
That'll
also
make
it
really
convenient
when
we
start
to
generate
this
plug-in
library
for
octet
from
a
github
action,
because
then
as
we're
landing
them,
when
we
push
a
tag
up
to
octant
repo,
that
tag
will
be
used
to
generate
the
library
and
that
that
same
tag
will
be
used
to
version.
It.
A
Yeah
definitely-
and
that's
also
gonna-
be
a
fun
automation,
project
and
hang
on.
Whoever
wants
to
take
it
up
because
you'll
get
to
write
a
custom,
github
action
and
publish
it
to
the
marketplace.
Presumably,.
A
Go
once
all
right.
Well,
I
think
that
wraps
it
up
for
today,
all
right
and
well.
If
there's
no
one
has
anything
else.
Thank
you
for
coming
and
see
all
next.