►
From YouTube: Octant Community Meeting - December 23th, 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
All
right,
hello,
everybody
and
welcome
to
the
six
minutes
late
december,
23rd,
octant
community
meeting.
Let
me
get
our
notes
pulled
up
here
and
we
will
get
started.
I
apologize
for
being
a
little
late
there
with
some
technical
difficulties,
but
based
on
the
current
number
of
viewers.
I
think
that's
okay,
so
we
will
get
these
shared.
A
A
Second,
why
is
it?
Why
is
everything
just
it's
because
I
haven't
touched,
my
computer
in
a
week
runs
mad
at
me.
Okay,
here
we
go
share.
Community
notes.
Share
there
we
go.
Okay,
folks
should
be
able
to
see
that
pretty
well,
so
yeah.
This
is
short
short
agenda
today,
make
it
a
little
bigger
so
yeah
so
on
the
agenda
today,
we've
got.
A
I
just
wanted
to
talk
about
like
what's
coming
in
the
new
year
and
that's
kind
of
it
and
then
we'll
do
open
q
a-
and
I
think
for
the
so
what's
coming
in
the
new
year,
we're
actively
working
on
the
electron
build,
which
was
mentioned
here.
I'll
pull
up
the
notes
from
last
week.
So
so
there's
an
electron,
build
branch,
electron
builder.
We
are
working
to
get
that
up
and
running
and
get
that
part
merged
into
our
main
mainline
branch.
A
So
hopefully
you
know,
then,
the
first
few
days
after
everyone's
kind
of
back
from
this
holiday
and
vacation
we'll
get
that
merged
in
and
the
goal
is
to
kind
of
push
out
that
first
electron
release
and
binary.
A
I
would
like
to
see
it
go
out
somewhere
around.
You
know
january
13th
right
in
there
sooner
if
we
can
later
if
it
needs
to
be,
but
that's
kind
of
the
the
target
date.
If
you
look
at
our
current
sprint,
which
is
here
on
0.17,
there's
a
note
in
here
that
we're
I'm
hoping
to
kind
of
get
it
for
around
the
13th.
A
So
we,
as
you
can
see,
there's
still
some
outstanding
issues
around
this.
Some
of
these
are
actually
in
flight,
but
just
like
the
this
one
is
in
progress
by
me
and
probably
by
cm
kind
of
both
because
we're
working
in
the
same
branch,
so
so
yeah
we're
chopping
away
at
it.
So
expect
that
that
that's
the
big
thing
to
expect
in
a
new
year
is
that
is
that
electron
branch
and
then
the
other
thing
is
which
we
talked
about.
A
A
We
just
talked
about
how
we're
going
to
be
organizing
our
projects
and
issues
and
stuff
moving
forward
to
kind
of
make
it
easier
to
digest
for
the
community
as
we
move
away
from
from
zen
hub,
which
was
a
bit
of
a
barrier
for
a
lot
of
folks,
including
myself.
It
just
kind
of
had
too
much
going
on
so.
A
I
think
that's
it
for
the
big
stuff
coming
in
in
right
in
the
early
new
year
and
then,
after
that,
it's
just
kind
of
executing
on
our
on
our
roadmap
expect
to
see
some
updates
to
our
roadmap.
Coming
soon
we've
we
released
some
information
about
our
kind
of
okrs
and
and
our
goals,
and
expect
some
of
that
to
to
get
into
here
and
update
some
of
the
language.
That's
in
here.
A
A
The
other
thing
that
I'm
going
to
be
looking
at
as
kind
of
an
effort
to
help
folks
get
involved
in
the
community
is
creating
a
community
markdown
file
and
with
that
file,
we're
gonna
I'll
work
with
sam
and
milan
and
and
we're
gonna
kind
of
define,
and
I
get
nisha
and
pia
as
well,
but
we're
gonna
work
to
define
what
it
means
to
be.
A
You
know
like
a
community
member,
a
contributor
and
a
like
an
approver
or
a
reviewer
right,
and
we're
gonna
actually
like
put
that
into
into
clear
terms
and
and
and
call
that
out
and
show
like
what
it
means
to
get
involved
and
how
you
can
get
involved
and
and
the
ways
you
can
become
more
like
more
of
a
part
of
our
of
our
auction
community.
A
Instead
of
just
what
we
do
now
is
kind
of
like
oh
everyone's
involved
right
and
there's
no
there's
no
good
way
for
people
to
feel
fully
engaged,
because
it's
it's
it's
very
ad
hoc
and
free
form.
A
So
I
wanna
get
some
get
some
more
concrete
definitions
around
that
stuff
publicly
out
there,
because
we
do
have
active
members
of
the
community
like
people
who,
I
would
consider
would
be
already
in
our
list
of
of
community
members,
probably
probably
even
a
person,
maybe
two
who
might
be
in
the
contributors
section.
And
then
I
don't
know
that
we
have
any
like
approvers,
who
would
be
coming
from
the
outside
community.
A
Yet
so
I
think,
having
language
and
having
a
clear
definition
of
what
all
that
means
going
forward
will
kind
of
help
people
see
you
know
what
the
steps
are
to
getting
to
that
point
and
being
more
involved
at
a
higher
level.
So
that's
something
that
I
want
to
get
out
there.
You
know
sometime
early
in
the
in
the
new
year
as
well.
A
B
Yeah,
I
have
a
fun
thought
about
outside
contributors
and
just
expanding,
who
might
potentially
be
a
maintainer
approver.
Do
you
ever
foresee
a
future
in
open
source
where
large
companies
would
trade
around
people
like
if
I
spend
x
amount
of
time
on
your
open
source
project
like
let's
say,
microsoft
and,
like
you
know,
help
review
your
open
source
project?
You
come
do
mine
and
we
get
a
little
bit
of
cross
pollination
of
ideas
between
projects
or
even
if
something
like
that
already
exists.
A
Yeah
so
I
mean
some
larger
open
source
projects
do
have
charters.
That
kind
of
outline
like
that,
the
the
board
and
like
who
makes
decisions
needs
to
be
made
up
of
a
diverse
enough
set
of
people
who
are
contributing
from
various
companies
right,
so
it
can't
be
like
80,
vmware
and
20
google,
or
something
like
that.
It
has
to
have
a
spread
before
people
are
allowed
to
like
become
part
of
the
board
that
makes
decisions.
So
that's
one
way
that
that's
handled
the
the
like
trade,
a
resource
thing.
A
I
think
that
for
most
companies,
that
probably
wouldn't
do
it
because
they'd
be
like
that's
our.
We
pay
that
person
to
do
our
stuff,
not
your
stuff,
but
I
like
the
idea,
I
think
I
think
that's
kind
of
the
the
the
the
spirit
of
of
some
of
the
like
hackathon
stuff
and,
like
you
know,
bug
bounty
things
and
things
like
that.
But
generally
I
think
it's
like.
Does
this
project
provide
us
value,
then
we're
gonna
contribute
to
it
and
get
people
dedicated
to
doing
it.
A
A
You
do
see
a
lot
of
people
who
like
used
to
work
for
the
company
right
and
then
they
left,
and
then
they
continue
to
contribute
to
the
project
and
as
part
of
moving
to
whatever
new
place
they
move
to
or
whatever
they
like.
They
call
out
in
their
new
job
like
hey,
I'm
still
going
to
be
a
member
of
this
community
and
contribute
to
that
project
actively,
and
then
you
get
some
cross-pollination
like
that.
A
But
yeah
I
haven't
seen
a
lot
of,
and
maybe
there
is
a
system
for
it,
but
I
haven't
seen
a
lot
of
like
direct
like
you
know:
moonlight
not
moonlighting.
What's
the
like
visit
wow,
you
know
what
I'm
saying
what
you're
saying
the
thing
you're
saying
whatever
the
word
for
it
is.
C
I
I
actually
did
a
project
that
is
it's
not
a
project.
It
was
a
hackathon
project,
so
I
did
a
hackathon
on
the
blockchain.
Something
like
this,
where
I
think
the
future
is
going
to
be
more
like
to
kind
of
follow.
You
train
of
thought,
sam
that
engineers
will
have
their
niche,
which
will
be
kind
of
skill,
set
it's
more
like
expertise,
domain
expertise.
C
Let's
say
I
don't
know
well,
front-end
angular
is
probably
a
little
too
wide,
but
if
we
narrow
that
to
like
10
sub
components
and
market
them
as
a
skills,
so
I
think
there's
going
to
be
something
like
that.
So
it
would
be
nice
that
you
know
you
can
do
move
along
those
ways.
So
if
your
expert
expert,
some
of
that,
you
can
kind
of
easily
move
from
one
project
to
another
in
open
source.
C
C
That
yeah
there's
going
to
be
a
few
more
things
than
17.
We
branched
that
I
don't
know,
maybe
a
couple
months
ago,
right
right,
so
there's
navigation
is
completely
new
now
and
also
the
breadth
comes
will
be
changed.
So
I'm
hoping
that
the
next
two
or
three
weeks
we
have
we're
going
to
stabilize
that
to
make
it
a
little
more
robust
that
you
need
to
make
changes.
I
I
know
I
want
to
go
back
into
navigation
and
change
few
things
in
css
level
just
to
make
it
a
little
better,
but.
A
Yeah,
I
am
I'm
looking
forward
to
once
we
have
electron,
then
it
immediately.
A
A
It
reminds
me
of
like
how
how
much
I
I
miss
just
shipping
web
apps,
because,
like
your
like
your
pipeline,
can
be
so
shortened
right
like
you.
Can
you
can
push
out
the
the
smallest
change
and
you're
not
building
a
full
binary
to
do
it
and
you're
not
like
you're,
not
having
to
get
that
binary
installed
on
a
user's
desktop
and
like
all,
and
so
like?
A
A
A
We
pay
back
some
of
our
tech
debt
and
then
once
we're
at
a
point
where,
like
we
have
we're
back
to
having
good
confidence
in
our
ci
right,
then
then
we
can
add
on
to
our
existing
pipeline
like
if
it
passes
right.
It
goes
out
right
like
if
it
so
it
has
release
notes.
It
has
api
docs
right.
We
have
checks
for
all
of
these
things
in
the
future
that
make
sure
that
any
feature
that
impacts
public
apis
or
things
like
that
that
are
non-deprecating.
Obviously
right
they
just
roll
out.
A
A
I
I
will
have
to
figure
out
a
good
way,
so
it's
not
like
super
annoying
right
like
do
you
want
to
be
on
the
dev
version
or
the
main
line
release
version
right
so
that
way,
you're
not
getting
like
the
hey,
there's
a
new
update
for
acting
every
every
18
minutes
or
whatever,
but
you
know
you
can
be
like.
I
want
to
be
on
the
main
line,
so
you
only
get
it
when
we
go
and
push
a
release,
tag
right
and
versus
here's
all
like
any
time.
A
A
A
I
I
was
thinking
that
I
would
maybe
just
just
find
some
issue
or
find
some
fun
thing
or
whatever
to
just
kind
of
hack
on
maybe
well,
if
it's
useful
the
live
code
of
plugin,
because
there's
already
examples
of
plugins
being
coded,
but
I
don't
know
I'm
thinking
I'm
trying
to
think
of
an
idea,
something
that
would
be
fun
to
do,
live
with
people
or
just
so
that
people
could
watch
it
later
when
they
came
back
in
the
new
year.
A
So
if
you
all
have
any
ideas
on
what
might
be
cool
or
fun
to
do,
let
me
know
I
honestly
just
haven't
thought
about
it.
I
just
know
that
I
want
to
do
something
so
the
moment
that
I'm
like.
A
I
think
what
I'll
do
is
just
create,
create
notes
for
the
next
meeting
right
now
and
then
we
can
add
in
ideas
which
that
would
be
the
30th
right,
not
the
20th,
the
30th.
There
we
go.
A
So
anyway,
if
you
have
ideas,
thoughts
on
that,
that
would
be
that
would
be
fun
toss
them
in
there.
B
I
have
an
idea
cool
this
one
is
something
I
think
scott
opened
an
issue
for
this.
It's
1506,
I
think,
for
the
idea
of
managed
fields,
but
the
idea
is
pretty
simple:
right,
like
you:
have
this
metadata
part
of
an
object
that
might
show
a
history
of
server-side
and
apply,
and
what
might
that
look
like
from
a
ui
perspective
or
even
not
even
from
a
ui?
B
But
how
might
we
track
previous
server-sided
changes
within
octan,
because
something
like
something
like
usage
in
the
terms
of
an
auditing
tool
right
like
auditing
history,
is
something
that
we
really
could
leverage
on
and
that
we
haven't
really
done
much
of.
Besides
events.
A
Yeah,
so
I
can
say
that
the
the
automatically
fold
managed
fields,
one
is
hard
tarp,
so
that
would
be
the
reason.
It
is
the
reason
it
is
an
issue
and
not
someone
just
did.
It
is
because
both
scott-
and
I
looked
at
this
at
one
point
and
we're
like
oh
yep-
that's
that's
that's
more
than
like
an
hour's
worth
of
work,
so
I
think
it
would
be
good
to
to
try
it'd
be
fun
right.
I'm
willing
to
willing
to
give
it
a
shot
so
yeah.
A
Yeah,
I
would,
as
you
think,
of
any
others
pop
them
in
there,
and
we
can.
We
can
decide
like
day
of
if
people
are
around
and
then,
if,
if
yeah,
we'll
just
we'll
just
pick
something
and
and
give
it
give
it
a
shot,
so
I
think
it
would
be
it'll
be
fun.
A
Great
thanks
everybody
and
for
folks
are
around
next
week.
We'll
see
you
next
week.