►
From YouTube: Octant Community Meeting - October 14th, 2020
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
B
C
All
right
well
I'll,
kick
it
off
since
we're
right
at
time,
and
we
do
a
stream
now
and
there's
people
waiting
so
welcome
everybody
to
the
octant
october
14th
community
meeting
today
we're
going
to
be
covering
a
handful
of
topics
and
hello,
sam
and
we'll
just
jump
right
into
them
and
then
we'll
open
it
up
for
any
questions
that
people
might
have.
So
with
that
said,
let's
see.
C
So
get
the
agenda
up
there.
It
is
all
right,
so
we
released
odot
16.1,
which
we
we're
going
to
do
on
the
7th,
but
we
did
it
on
the
8th
there
was.
There
was
just
a
couple
of
small
things
that
that
we
wanted
to
get
in
there
before
we,
we
cut
the
release,
so
this
is
up
now
it's
in
all
the
package
managers.
So
if
you
haven't
updated,
recommend
you
do
that
it
it's
a
good,
a
lot
of
good
bug,
fixes
we
talked
about
them.
C
We
talked
about
all
of
them
last
week,
so
feel
free
to
look
at
the
changelogs
and
and
send
send
sam
a
thank
you
for
all
of
the
the
bug
fixes
that
he
got
in
there
and
also
thanks
to
to
scott
andrews
and
josh
rosso,
who
contributed
a
couple
fixes
to
that
release
as
well.
Definitely
up
the
update.
That's
all
I
gotta
say
about
it.
If
you
haven't
updated,
do
it,
it
was
a
good
release,
a
lot
of
good
fixes,
any
anyone
got
anything
to
add
there.
C
All
right
so
moving
on
to
the
odot
17
as
an
electron
release,
so
this
is
something
we've
been
talking
about
hinting
at
and
then
talking
about
and
hinting
at
and
talking
about
more-
and
this
is
the
this
next
upcoming
release.
C
We
will
be
releasing
this
as
a
electron
application,
we'll
probably
still
package
the
old
binaries
that
you're
familiar
with
for
a
a
release
or
two
just
probably
two-fold
just
so
that
people
get
used
to
the
fact
that
there's
this
new
binary,
but
also
there's,
maybe
a
precautionary
in
case
the
electron
one-
isn't
functioning
on
across
all
these
various
platforms.
C
We
are
putting
a
lot
of
extra
effort
into
quality
assurance
and
and
controls
and
making
sure
that
what
we
end
up
releasing
for
the
electron
application
is
is
very
solid.
Sam
brought
up
a
good
point
in
a
conversation
we
had
the
other
day
about,
like
you
know,
if
we
release
this
thing
under
as
an
electron
app
and
then
it
kind
of
falls
on
itself,
then
everyone's
going
to
be
like
why'd,
you
even
waste
the
time
doing
that,
so
we
want
to
show
the
value
there
and
we
want
to
get
people.
C
You
know
using
it
and
get
feedback
on
it,
so
we're
gonna
make
sure
that
it's
rock
solid
when
it
goes
out.
That
is
also
part
of
the
reason
it's
been
so
long
waiting
for
it
to
get
released.
C
We've
been
putting
in
a
lot
of
things
in
place
like
new
navigation
and
building
out
the
breadcrumbs
system
and
and
making
sure
that
those
things
are
showing
up
where
they
should
and
to
allow
for,
like
a
good
navigation
experience
when
you're
no
longer
in
a
browser,
and
so
there's
a
lot
of
pieces
that
that
were
kind
of
being
developed
that
allow
us
to
now
package
this
up
as
a
as
as
an
application
as
we
intend
some
of
our
hopes
and
dreams.
C
There
are
things
like
being
able
to
have
you
know,
being
able
to
turn
on
and
off
system
level
notifications,
so
you
can
get
like
notifications
right
in
in
your
native
events,
on
your
operating
system
being
able
to
have
octane.
You
know
down
running
in
the
background
whether
that's
you
know
pinned
in
in
a
in
a
taskbar
or
down
in.
Like
a
you
know,
some
other
area
native
menus
and
navigating
through
octane.
C
In
a
more
native
field,
these
are
just
some
of
the
things
that
we
want
to
be
able
to
take
advantage
of,
and
then
then
we
can
once
that's
there.
We
can
start
to
get
into
things
like
a
really
good,
install
plug-in
flow
where
we
can
actually
like.
Take
you
to
the
folder.
Allow
you
to
install
them.
Allow
you
to
remove
them,
give
you
buttons
that
make
it
easy
to
restart
octant
after
you've
loaded
a
new
go
plug-in.
C
You
know,
show
where
those
assets
are
within
the
file
system
and
be
able
to
easily
go
get
to
them
things
that
are
just
really
really
difficult
now,
through
a
browser
interface,
which
has
got
us
this
far,
but
now
we
want
to
take
it
to
that
to
that
next
level.
So
that's
just
some
of
the
some
of
what
to
expect
with
an
upcoming
as
we
move
toward
to
being
on
this.
Like
electron
platform,
I
don't
know
if
I
sort
of
think
I
missed
there.
Milan.
A
Sam
yeah,
we
can
add
it
back
to
the
issue
later.
I
think
we
have
a
old
tracking
issue
550,
which
lists
kind
of
what
every
like
what
we
would
expect
to
have
to
happen
before
an
electron
release
goes
out,
namely
there
are
just
some
things
that
you
might
not
think
about
like,
for
example,
zooming
in
and
out.
You
know,
for
some
reason,
electron
doesn't
come
with
that
automatically
and
you
can
do
it
for
free
on
a
browser,
but
we'd
have
to
implement
something
like
that
and
things
like
auto
updating.
A
I
think
that's
also
something
that
we'd
like
to
have
at
least
some
validation
that
it's
working
and
in
place
before
we
ship
that
out.
So
it's
not
just
octan,
and
then
we
plop
it
into
electron.
There
are
things
that
other
things
that
need
to
be.
That
needs
to
happen
before
this
ships
out.
C
C
Excellent
all
right.
Well,
we
will
move
on
to
the
this
topic
I
added,
which
is
around
plug-in
api.
I
just
wanted.
There
was
a
couple
issues
that
were
opened
in
the
last
release
cycle
that
we
didn't
get
into
odot
16,
but
that
I
took
note
of
that.
I
think,
are
really
interesting
that
we
want
to
get
in
there.
C
Actually,
I
think
the
dataless
one
was
opened,
maybe
even
before
that,
but
currently
on
the
summary
page,
a
plugin
can
only
add
a
single
tab,
there's
just
a
tab
handler
and
it
spits
out
a
response,
and
that
response
is
the
content
of
your
tab
and
I
believe
the
the
aqua
security
folks
were
working
on
a
plug-in
and
had
a
desire
to
be
able
to
split
out
some
of
the
information
they
wanted
to
display
for
a
given
workload.
C
You
know
in
this
in
the
summary
view,
for
it
into
multiple
tabs,
because
the
basically
the
context
for
each
set
of
data
is
different,
and
that
made
a
lot
of
sense
to
me
that
I
think
that's
a
very
reasonable
thing
that
we
want
to
be
supporting
within
our
plugins.
So
that's
something
that
I
want
to
get
in
there
sooner
rather
than
later,
so
people
can
start
playing
with
it
might
do
that,
as
as
a
as
a
point
release
to
the
0.16
release.
C
If
people
are
blocked
by
it
or
we
get
more
like
hey,
we
could
really
use
this
now,
since
it's
adding
to
the
api,
I'm
comfortable,
putting
it
into
a
minor
release,
since
it's
not
deprecating
it
in
any
way,
but
it
also
depends
on
how
our
tab
handler
works
now
like
as
long
as
as
long
as
they
can
call
like
recompile
and
call
the
same
tab
handler
with
a
single
tab,
and
it
works
the
same
way
with
multiple
tabs,
then
we'll
be
fine.
C
If
we
have
to
change
the
api,
then
it's
going
to
have
to
wait
till
about
17.
and
we
might
have
to
I
don't
know.
I
have
to
look
at
it
more
and
the
other
thing
I
wanted
to
call
out
was
a
datalist
component,
and
now
I'm
saying
dateless,
because
that's
what
clarity
calls
them,
but
that
is
just
essentially
a
drop
down.
That's
pop!
C
That's
fed
with
with
data
and
and
some
of
the
items
can
be
turned
on
or
off,
and
it
can
enable
things
like
like
multi-select
within
the
data
list
and
right
now,
there's
no
good
way
for
plug-in
authors
to
expose
this,
like
especially
like
in
breadcrumbs
or
things
like
that,
where
they
might
want
to
do
sub-navigation
type
things.
C
C
So,
like
click
on
this
and
take
me
to
that
url
which
will
allow,
for,
I
know
the
the
jenkins
x
folks,
they
wrote
a
plug-in
and
the
the
desires
in
their
breadcrumbs
to
be
able
to
just
have
this
dataless
component
with
a
drop
down
with
all
of
like
the
sub
elements
that
you
might
want
to
reference
that
aren't
necessarily
qualified
to
be
like
full-on
tabs,
but
they're
just
links
or
call-outs
to
other
areas
within
the
system.
C
It's
a
ui
like
a
ux
pattern
that
they
desired.
So
that's
also
something
that
we
want
to
get
in
there
and
there's
a
couple.
Others
I
just
forgot
them
and
I
had
didn't,
have
a
chance
to
go.
C
Look
them
up,
but
we're
gonna
be
adding
some
some
new
components
and
features
to
the
to
the
plug-in
api
to
to
make
things
a
little
easier
and
since
we're
talking
about
plugin
api
before
we
started
the
the
meeting,
scott
andrews
was
asking
about
forms
forms
within
modals
and
other
form
things,
and
I
was
answering.
C
I
was
saying
that
our
introduction
of
custom
forms
and
being
able
to
render
out
your
forms
through
your
plugin
and
have
custom
actions
and
handle
validation
is
all
very
new
and
we
just
released
it
in
the
last
0.16,
and
it
is
likely
that
that
api
needs
some
use
to
determine
what
it's
missing
and
determine
like
how
we
can
better
improve
it.
C
So
to
answer
scott's
question
which
he
asked
in
the
select
channel,
I
don't
know
of
any
examples
of
using
a
form
in
a
modal
right
now
that
we
have
live
anywhere,
but
that's
something
I
think
we
can
come
up
with.
Was
there
any
more
questions
you
had
on
that
scott.
C
A
Yeah
there
was
one
more
I
think
I
forgot
the
commander
name,
the
not
the
graph,
but
the
the
little
the
little
charts.
What
do
we
call
them?
Oh.
A
The
donut,
yes,
someone
wanted
right
now
we
only
have
three
donut
colors,
green
orange
or
red,
and
I
think
the
best
way
to
go
about
it
is
just
to
I
don't
know
I
can
enable
like.
Actually
I
haven't
thought
about
it
too
much
what
that
should
look
like,
but
I
think
it'd
be
helpful
to
either
enable
wider
range
of
colors
or
just
let
them
add
the
css
for
whatever
color
they
wanted
through
some
sort
of
go
interface
or
javascript,
whichever
one,
but
it
seems
yeah.
C
Yeah,
I
think
that
one
also
came
from
the
aqua
security
plug-in.
B
Yeah,
I
remember
looking
into
that
briefly.
I
think
what
we
need
to
add
is
for
each
entry.
We
need
to
basically
clear
the
color
and
the
tooltip
description,
so
I
don't
think
it
should
be
that
hard
to
do
that,
but
I
I
briefly
looked
into
it
so
yeah.
I
think
it
would
be
good
improvement
because
there's
a
lot
of
cases
that
are
outside
of
the
you
know,
plain
donut
usage
that
we
currently
have.
C
Yeah-
and
I-
and
I
also
I
I
wonder
about
like
long-term-
and
this
is
something
that
I
think
brian
has
mentioned
before-
and
we've
talked
about
briefly
but
figuring
out-
some
way
to
enable
you
know
web
like
custom,
web
components
or
custom
angular
component
or
some
type
of
custom
component
within
the
plugin
in
a
nice
way,
whether
that
is
a
web
component
or
it
is
just
making
the
api
around
iframes
better
or
whatever.
C
It
looks
like
the
allowing
people
to
get
some
of
these
more
complex
data
visualizations
into
octane,
without
us
having
to
build
out
an
entirely
new
set
of
components
to
support
data
visualization
like
I
don't.
I
don't
think,
that's
something
that
we
want
to
do
like,
but
we
want
to
enable
you
know
we
want
to
enable
people
to
to
show
these
embedded
data
views
within
octan.
So
that's
something
we're
thinking
about
trying
to
figure
out
the
best
way
to
do
that.
C
A
C
C
B
A
C
C
Hey
pablo
thanks
for
joining
us
yeah,
so
the
documentation
we
currently
have
some
of
it's
out
of
date,
some
of
it
in
different
places,
there's
some
of
it's
markdown
files
and
the
github
repo
and
I've
said
all
this
before.
It's
just
not
a
good
experience
overall,
like
there's
some
good
content
in
there,
but
like
getting
to
it
and
like
finding
it
is,
is
not
great
like
the
way
we
navigate
you
to
it
is
is
just
it's.
C
It
could
be
better,
so
we're
currently
working
on
an
effort
to
take
our
existing
documentation
that
we
have
spread
through
various
spots
in
the
repo
and
through
the
octet
dot
dev
site
and
get
it
consolidated
under
a
docs
folder
in
our
our
storybook
and
we
I
started
that
process.
So
so,
if
you
go
up
onto
our
storybook,
let's
see
it's.
What
is
it.
C
I
think
do
we
even
link
to
it
from
from
the
octan.dev
website
at
all
anywhere,
okay
yeah,
so
it's
can't
type
reference.
C
I'm
doing
using
the
other
machine
for
the
screen
share
since
it's
a
little
bit
easier,
so
we
started
to
consolidate
this
under.
Oh
look
at
that.
Look
at
that
little
failing
on
their
pre-checks.
We
we
started
to
consolidate
everything
under
this
docs
heading
and
all
that's
here.
Right
now
is
just
like
kind
of
like
a
y
and
an
installation.
C
The
installation
guide,
styles
are
messed
up
and
that's
that's
my
fault.
I
didn't
they
were
working
fine
locally
and
then,
when
it
got
compiled
up
it,
it's
using
an
override
preview.
So
anyway,
milan
showed
me
how
to
fix
this,
but
the
idea
is
we're
going
to
take
all
of
our
existing
documentation
and
get
it
compiled
underneath
this
docs
section
and
then
off
of
the
main
octan.dev
site,
we're
going
to
re-link
to
this
and
provide
a
like
you'll
land
there.
C
When
you
click
on
on
docs
and
it'll,
just
say:
hey
go
to
our
storybook
for
comprehensive
documentation,
and
so
this
all
of
this
content
here
some
of
it
might
get
removed
completely
if
it's,
if
it's
misleading
or
out
of
date,
but
it'll
just
get
migrated
over
to
be
nested
under
that
dock.
C
Section
and
then
we'll
create
a
contributing
guide
for
how
to
contribute
to
our
docs
since
they'll,
be
in
one
location,
they'll
have
structure
and
they'll
be
areas
defined,
and
then
once
we
have
that
in
place,
which
will
be
sometime
this
week,
we'll
start
to
define,
outlines
as
github
issues
for
the
actual
documentation
that
we
want
to
build
out,
and
I
know
one
of
those
was
already
created.
Someone
was
asking
for,
like
an
architecture,
outline
and
overview
of
octant,
so
that'll
be
a
piece
of
this
someone
was.
C
We
also
want
to
create
a
a
contributor's
guide
for
how
to
add
a
new
component
to
octant.
That
was
something
that
I
think
sam
mentioned
would
be
helpful
or,
I
think
actually
it
came
from
outsi
announced
someone
requested
it
from
outside,
and
then
sam
mentioned,
it
was
like
yeah.
C
That
would
be
really
really
helpful
and
and
then
probably
specific
guides
like
here's,
how
you
create,
like
here's,
a
tutorial
for
creating
a
go
plugin,
here's
a
tutorial
for
creating
a
typestrip
plug-in
and
just
have
like
a
a
specific
walk-through
for
each
of
those,
so
expect
some
better
documentation
coming.
This
is
this
is
an
area
that
I'm
going
to
be
focusing
on
quite
a
bit
over
the
next
like
week
or
two
as
we
get
our
infrastructure
in
place
for
building
out
the
electron
application.
C
I
want
to
make
sure
that
our
documentation
is
there,
alongside
of
that
too,
so
that
it
feels
like
a
really
good
overall
experience
when
you
come
into
octane.
So
with
that
that
was.
That
was
the
main
things
I
wanted
to
cover
today.
C
Is
there
anything
else
any
questions
from
people
watching
watch
the
chat
there
a
little
bit
or
any
thing
people
wanted
to
add
that
I.