►
From YouTube: Jupyter Community Call - August 30, 2022
Description
Recording from the Jupyter Community Call in August 2022.
The notes from this call can be found here: https://github.com/jupyter/jupyter/issues/662
Read more about these calls on Discourse: https://discourse.jupyter.org/t/jupyter-community-calls/668/
A
A
It's
just
if
you
change
your
view,
I've
noticed
it
records
whatever.
Okay.
Thank
you.
Thank
you.
Well,
in
that
case,
welcome.
This
is
the
August
2022
Jupiter
Community
call
I'm
Isabella
I'm
going
to
be
your
host
today
and
I'm
super
excited,
because
we
have
a
bunch
of
things
on
the
agenda
to
run
through.
A
If
you
haven't
been
here
before,
this
call
is
meant
to
celebrate,
what's
happening
in
the
Jupiter
Community
help
us
kind
of
build
Bridges
across
our
sub
communities
and
just
give
us
a
chance
to
all
talk
with
each
other
without
needing
to
maybe
fix
things
or
talk.
Development
just
be
excited
about
everything
that
people
do
it's
kind
of
a
show
and
tell
style.
A
So
what
we're
going
to
do
is
follow
the
agenda
that
I've
linked
I
think
everyone
has
been
here
since
I
last
linked,
but
I
will
do
that
again
in
a
moment,
and
that
means
we're
just
going
to
kind
of
go
through
bit
by
bit.
We
do
have
things
on
the
agenda
today.
We
might
have
a
little
time
for
something
if
you
are
so
excited
by
what
we
have
shared,
that
you
want
to
do
that.
If
not,
I
am
happy
to
link
the
agenda
for
the
next
call,
and
you
can
always
show
up
for
that.
A
So
with
no
further
Ado,
we
will
get
started
on
the
agenda.
Yay
I.
The
first
thing
is
actually
are,
like
short
reports,
celebrations
kind
of
short
things
that
don't
need
discussion,
I,
don't
see
anything
on
the
list
there
right
now,
but
I
will
be
quiet
for
a
couple
seconds
to
give
y'all
a
chance.
This
could
be
a
great
time
to
announce
like
releases.
We
have
this
event
coming
up.
This
exciting
thing
happened.
This
may
be
not
exciting,
but
very
important
infrastructure
thing
you
might
not
have
noticed,
happened
those
kind
of
things
foreign.
A
Okay,
no
announcements,
I
think
that's
rare,
usually
it's
the
other
way
around,
but
I'm.
Okay,
with
that
I
bet
you
we're
gonna
get
kind
of
announcements
anyway.
So
great
I
will
say,
though
quickly.
Thank
you
all
for
being
here.
It's
really
awesome
to
see
a
different
group
of
people,
so
shout
out
to
all
of
you
who
this
may
be
not
like
a
community
call
that
you
go
to
normally
shout
out
for
being
here.
Thank
you
and
then
I'm
going
to
move
to
the
agenda
items.
A
B
B
We
discovered
Jupiter
one
when
we
were
actually
doing
Financial
reports,
business
reports
for
for
different
companies,
and
we
start
we
were
stuck
with
Excel
DBA,
so
we
were
like
really
stuck
into
whatever
we
were
doing
so
we
got
started
with
Jupiter
at
that
point,
and
it
was
like
a
magical
moment
for
us
really
to
discover
the
the
interface
the
way
to
play
out
the
python
and
it
was.
It
was
really
game
changing
for
the
way
we
can
build
reports
interactively
with
the
clear
auditing.
You
know
document
where
you
can
share
your
thoughts
and
everything.
B
So
this
was
made
by
by
like
investigating
into
a
Paper
Mill
the
component
that
Netflix
is
using,
so
we
have
been
using
Peppermill
to
to
build
this
layer.
We
have
another
layer
called
the
drivers
which
are
like
a
python
library
to
abstract
connection
to
different
tools.
So
the
templates,
which
is
the
third
layer,
look
very
simple
and
neat,
so
basically,
Nas
is
Jupiter,
plus
three
layers,
automation,
layer,
connector
layer
and
template
layer
and
and
right
now
we
are
like
we
are
on
the.
B
We
have
been
like
helped
by
AWS
to
deploy
this
in
the
cloud.
So
we
have
a
cloud
offering
and
an
open
source
pure
open
source
project
as
well,
and
we
have
around
three
thousand
people
that
signed
up
last
year,
50
contributors
that
I've
already
contributed
to
the
to
the
template
repository.
We
have
a
few
Southern
stars
on
on
GitHub
and
it's
really
really
great
to
be
able
to
share
what
we've
been
building
with
you
guys
today.
So
thank
you
for
welcoming
us
here.
C
B
B
So
yeah,
our
our
vision
is
to
to
use
Jupiter
as
a
null
in
one
data
platform.
Basically,
when
you,
when
you
get
into
data
science,
you
just
want
to
stay
in
Jupiter,
because
it's
it's
it's
like
a
comfortable
place
to
be.
You
want
to
be
able
to
run
your
script.
Deploy,
do
everything
basically
from
The
Notebook
interface,
so
this
is.
This
was
our
first
intention
and
this.
A
B
D
B
A
B
Okay,
okay,
so
yeah,
then,
as
you
were
asking,
so
there
is
three
three
repository
that
are
key
to
to
Nas
the
first
one
is
the
nice
repo
on
this
one
you
will
have
so
you
will
have
all
the
all
the
scheduling,
the
API
features.
The
asset
feature,
everything
that
you
need
to
actually
run
microservices
on
top
of
the
Jupiter
environment
and
transform
your
notebooks
into
Bots.
B
Basically,
in
this
repository
driver,
you
will
have
all
the
different
tools
that
we
have
been
abstracting
to
to
as
a
small
python
files,
and
you
will
see
that
in
templates
you
basically
have
all
those
list
of
tools
you
can
use.
So,
for
example,
we
can
take
something
like
this
yeah
Finance
one
and
let's
say
you
want
to
use
Jupiter.
B
B
You
want
to
go
into
this
notebook
and
then
we
have
this
little
button
where
you
can
directly
open
the
notebook
in
into
the
cloud
infrastructure
and
there
is
the
template
so
I'm
just
going
to
click
on
it
and
go
through
the
whole
like
experience,
so
people
find
us
through
the
templates.
We
do
a
lot
of
content
in
social
media.
B
We
try
to
push
a
lot
of
like
contributors
to
create
and
add
their
own
templates
to
the
to
the
repository,
and
we
offer
the
opportunity
to
get
this
template
like
run
into
the
cloud
infrastructure
that
we
provide.
And
if
you
look
at
this
template,
it's
always
the
same
thing.
It's
always
the
same
pattern.
We
have
structured
it
this
way,
so
you
have
the
input
section,
the
model
section
and
the
output
section.
So
in
the
input
section
you
will
import
your
different
libraries.
B
Let's
say
you
want
to
follow
the
price
of
this
love
for
the
last
hundred
days.
You
want
to
predict
20
data
points
in
the
future.
You
want
to
send
yourself
an
email,
so
you
will
replace
this
email
and
basically,
once
you
have
the
setup
done
you,
you
will
be
able
to
also
expose
assets,
create
Excel,
outputs,
image,
outputs
that
will
be
shareable
and
also
schedule.
The
The
Notebook,
with
this
little
formula,
so
Nas
dot
scheduler.add,
would
be
the
formula
that
creates
a
copy
of
your
notebook
and
then
the
nas
features.
B
Will
the
feature
layer
will
take
this
notebook
and
schedule
it
at
the
right
time
so
directly
from
this
ecosystem.
You
can
have
like
something
running
on
on
schedule.
So,
if
you
like
run
this
basically,
this
will
activate
all
the
all
the
cells,
of
course,
but
you
will
you
can
see
also
that
there
is
some
level
of
abstraction
that
is
done
at
the
connector
level.
B
So
the
the
driver
repository
that
I
was
talking
to
you
about
is
about
creating
very
simple
one-line
formula
to
access
to
different
tools
and
so
for,
for
instance,
we
have
this
Yahoo
finance
one
where
you
only
pass
the
ticker
so
Tesla
date
from
day
two,
and
then
you
have
your
data
frame.
You
have
this
other
one,
which
is
the
the
prediction
column.
The
prediction
column
are
added
through
this
driver.
B
You
pass
the
data
set,
you
add
the
column
date
and
then
you
have
your
arima,
linear,
regression
and
so
on,
and
if
you
want
to
have
your
chart,
we
also
have
a
driver
on
on
ploty,
where
you
pass
only
a
few
parameters,
and
you
have
your
nice
job
popping
up
like
this.
So
the
whole
result
of
this
is
you
want
to
share
basically
a
an
email
that
will
look
like
this
hello
world,
like
any
analyst,
would
send
an
email
to
to
like
management,
team
or
colleagues.
B
B
You
have
also
the
ability
to
send
the
email
again
to
send
this
this
again
and
to
trigger
The
Notebook
through
the
webbook
feature.
So,
basically,
in
this
example,
you
can
see-
and
you
can
also
send
the
notification
through
your
emails
like
this
by
just
like,
with
with
this
only
little
formula,
you
pass
the
email
to
the
subject.
You
pass
the
the
whole
object
that
you
want
to
send,
and
and
that's
it
you-
you
will
get
this
in
your
mailbox.
B
A
B
We
want
this,
we
have
like
gathered
quite
a
lot
of
issues,
so
the
idea
is
to
really
go
and
build
a
big
catalog
of
templates.
That's
that's.
I
think.
The
main
thing
that
we
want
to
bring
to
the
Jupiter
Community
is
to
like
motivate
other
people
that
are
really
like
domain
Focus
or
expertise.
Focus
oriented
to
create
this
big
catalog
of
templates
that
can
be
used
for
anything
from
exploratory
to
building
blocks
of
something
which
is
much
close
to
a
software
foreign.
A
A
You're
seeing
people
use
them,
is
this
the
all
those
templates?
Here
you
mean
no
I
mean
all
the
issues
that
are
requesting
for
templates
like
how
are
you
are
you
running
into
those
somewhere
else
and
realizing?
Oh,
we
should
have
that.
Are
these
use
cases
that
you
need
I,
think
those
are
really
interesting
to
see
because
they're
so.
B
Specific
yeah,
it's
it's
very
specific
on
some
tools,
and
so
basically
we,
what
we
did
last
year
is,
as
we
launched,
This
Cloud,
Jupiter
plus
automation,
feature
on
top
and
templates.
We
saw
that
many
people
came
to
us
like
hey
I,
want
to
automate
this
with
this
I'm,
currently
using
something
like
zapier
or
yeah
or
make
I.
B
Don't
know
if
you
know
those
tools,
those
automation,
no
code,
automation
tools
and
they
said
like
hey,
basically
I'm
stuck
and
I'm
confined
to
the
UI,
so
I'm
I'm
really
down
to
have
a
notebook
to
actually
be
able
to
write
my
own
business
rule
into
those
templates
and
to
use
the
scheduling
feature.
The
asset
feature
that
Nas
provides
to
creative
a
more
like
Advanced
automation.
So
this
this
list
of
issue
comes
basically
from
the
most
important
tools
and
actions
that
we
have
identified
to
really
create
a
great
and
useful
library
of
templates.
A
B
These
no
it's
really
open,
it's
really
really
open,
so
it's
really
open
to
anyone
to
get
and
come
with.
Basically,
the
the
thing
is:
everybody
has
a
few
notebooks
running
for
some
tools
that
have
already
been
done
in
the
past
and
they
have
it
on
their
local
computer
and
their
name
or
you
know
not
not
structured
in
a
in
a
certain
way.
B
E
E
Is
a
little
bit
of
a
loaded
question,
because
I
still
think
that
we
lack
search
approaches
with
notebooks,
but
man
how
am
I
supposed
to
find
the
notebook?
That's
meant
for
me
in
this
repository
and
like
this
kind
of
I
mean
this
is
not
a
thing
about
Nas.
This
is
almost
in
general
right
when
I
find
people
who
prolific
at
notebooks,
there's
a
notebook
in
here
that
I
should
be
reading
right.
How
do
I
find
that
and
I?
Don't
think
that
there's
a
particularly
good
answer
to
it.
B
I
I
totally
get
you
so
right
now
we
have
400
plus
450
something
that
book.
So
it's
starting
to
become
a
problem
before
it
was
okay,
because
you
can
just
go
through
the
list
of
tools
like
hey
I
want
to
intimate,
I
want
to
go
and
use
hugging
phase
and
I
want
to
like
okay,
I
have
a
few
templates
here.
I
can
probably
add
one
or
you
know,
but
we
definitely
have
this
search
experience
question
right
now.
B
How
do
we
discover
these
notebooks
and
we
are
about
to
launch
actually
a
project
this
week
with
our
open
source,
community
and
and-
and
we
are
like-
we
are
happy
to
like-
like
have
everyone
jump
in
because
the
the
idea
is
to
is
to
create
some
kind
of
of
an
experience
like
this,
where
you
would
be
able
to
like
get
into
asking
questions
or
putting
keywords
and
get
some
suggestions
of
notebooks
that
already
exist
in
the
repository.
So
basically,
this
this
little
search
will
go
into
the
Json.
B
That
is
right
here,
which
is
the
the
the
collection
of
all
the
templates,
and
it
will
read
the
keywords
here.
Read
the
hashtags
read
the
and
take
the
the
link
which
will
automatically
lead
you
to
open
this
notebook
into
your
environment.
So
that's
that's
what
we
we
are
working
on
right
now,
because
we
have
this.
This
search
experience
also
problem
that
is
raised
right
now
through
this
list
of
templates.
B
E
B
C
I
had
a
question
that
is
about
the
different
repo
cells.
Looking
at
the
the
collection
of
notebooks
and
I
noticed,
your
license
is
BSD
for
the
notebooks
and
that
for
the
software
your
license
is
agpl
and
I
was
curious.
What
your
thought
process
was
around
licensing
of
the
software
that
you're
releasing.
B
B
D
If
I
can
like
just
step
in
I,
think
like
we,
we
didn't
like
spend
too
much
time
online
sensing
yet
because
first,
we
don't
really
have
any
experts
in
our
team
or
any
contributors
that
ask
us
this
kind
of
question
and
saying
hey.
We
should
take
a
look
at
licensing
between
the
different
projects,
so
it's
definitely
something
we.
We
need
to
consider,
consider
updating
in
the
in
the
near
future.
Definitely
now
nothing
is
fixed
for
now.
B
The
basic
reasoning
behind
this
is
we
have
this.
We
want
to
keep
this
thing
open
source
as
much
as
possible,
but
there
is
something
that
we
need
to
deploy
in
the
cloud
and
that
these
things
are
actually
a
bit
more
tricky.
It's
about
kubernetes.
It's
about.
You
know
Docker
eyes,
like
machines
that
can
provide,
so
that's,
probably
where
there
is
a
a
line
to
to
put
so
that's
that's.
That's
the
the
basic
reasoning.
B
Yeah
yeah,
that's
that's
pretty
much
it's,
and
so
the
idea
in
the
in
the
in
the
future
is
to
go
from
just
having
this
list
of
templates
to
actually
use
those
templates
to
create
like
products,
and
so
this
is
why
I
wanted
to
also
introduce
you
to
okay.
We
have
this
this
product
template
here,
so
once
you're
inside
the
the
ecosystem.
Let's
say
you
want
to
just
pick
and
choose
different
templates
and
Bender
them
together
to
create
my
automation.
B
So
we
we
have
this
data
templates
and
the
the
structure
is
I,
don't
know
if
you
guys
are
familiar
with
DBT
or
this
kind
of
transformation
tool,
but
they
also
have
a
certain
structure
to
their
tools
to
their
project.
So
this
is
what
we
want
to
do.
We
want
to
have
a
setting
kind
of
notebook
where
you
will
set
up
your
different
credentials
and
things
you
want
to
configure.
B
Then
you
will
have
your
model
section
and
you
in
your
model
section,
you
can
have
all
the
templates
that
you're
using
that
are
like
triggered
using
the
the
percentage
run
function
inside
Jupiter.
So
this
way
you
can
use
this
templates
to
do
this
action,
this
templates
to
do
another
action
and
so
on
and
create
your
your
your
products
in
in
really
less
time
that
it
would
have
take
you
if
you
would
have
done
it
from
scratch.
B
So
if
you
have
any
thoughts
on
this,
it's
it's
a
work
in
progress.
We
are
just
starting
with
this,
so
we
are
really
happy
to
to
like
get
any
feedback
on
this
and
because
I
know
that
there
is
also
other
approach
to
like
productionized
notebook
and
and
push
not
use
notebooks
in
production.
This
is
definitely
the
the
vein
in
which
we
are
trying
to
find
our
way.
A
B
B
A
A
B
Yeah
well,
the
idea
is
to
be
completely
agnostic
of
the
output.
It
can
be
a
thing
on
on
notion
or
anywhere
in
in
the
open
source.
World
we're
also
building
stuff
with
Dash,
so
yeah,
it's
basically
really
open
and
we
are
just
iterating
and
trying
to
learn
how
we
can
improve
this
and
and
create
some
kind
of
an
interesting
offering
for
both
small
and
middle-sized
companies
that
just
wants
to
get
things
done
with
the
notebooks
I.
Think.
That's!
That's
the
idea
now
once
now
that
we
have
this
base
and
this
Foundation.
D
E
D
D
A
A
A
G
G
G
G
So
things
like
this,
of
course,
if
the
file
is
not
supported,
it
doesn't
work,
but
just
to
show
you
what's
the
id
here.
So
that's
one
of
the
things
the
students
have
done.
That
was
a
tricky
one.
Another
one
that
is
very
nice
is
like.
Now
we
have
a
graph
for
showing
what's
going
on
on
the
branch
history.
So
let's
make
it
a
bit
this.
G
You
can
see
a
bit
more
what's
going
on
and
that's
also
what
the
changes
for
in
the
past
to
when
you
are
committing
in
kids.
With
the
story,
you
can
other
additional
summary
and
no,
they
have
changed
that.
So,
if
you,
if
you
click
on
a
note,
you
will
also
get
the
description
in
addition
to
the
summary.
So
that's
that's
a
nice
addition
and
a
small
addition
that
can
be
very
nice,
too,
is
that
noise.
You
can
see
the
the
branch
you
are
in
next
to
the
git
logo
on
the
status
bar.
G
Oh,
probably
it's
gonna
work,
okay,
and
then
you
can
see
that
the
the
branch
name
has
been
updated
and
what
else?
What
else?
Oh
yeah,
the
last
thing
that
they
have
improved
is
the
the
ability
to
manage
multiple
remotes.
So
now
you
can.
There
is
a
new
dialog
in
which
you
can
see
all
the
the
remotes
you
have
for
a
repository.
G
You
can
add
some
or
remove
it,
and
so
with
it
also,
you
can
decide
when
you
are
pushing,
you
can
go
for
a
advanced
push
and
you
can
pick
up
the
the
distant
repository
you
want
to
push
for
so
yeah.
That
was
the
demo
in
three
minutes
so
feel
free
to
test
super
important
and
just
like
anything,
but
it's
useful
to
improve
the
extension.
B
I
think
it's
super
cool
and
that
he
would
probably
implement
it
into
our
instance
at
last.
That
would
be
great
to
to
have
it's
actually
something
that
we've
been
I've
been
looking
up
to,
because
enforcing
it
is
in
in
the
Jupiter
development
process
is
something
that
we
we
felt
even
with
our
contributors.
It
was
hard
to
to
get
some.
You
know
strong
connection
to
git,
so
this
is
definitely
a
good
add-on.
A
Yeah
and
I
know
it's
a
longer
conversation,
but
I'm
also
just
really
interested
in
having
three.
You
know
terms
of
right
students
working
with
you.
Are
there
any
takeaways
that
you
would
want
to
share
with
that?
Maybe
that's
a
little
tangential
and
you
don't
want
to
share
that
now
and
that's
fine,
but
I
know
sometimes
contribution
workflows
even
to
an
extension
like
that
can
be
complicated.
Is
there
anything
you've
learned
what
it's
like
to
kind
of
bring
people
in
every
couple
of
months,
foreign.
G
G
Ahead,
though
so
yeah
the
the
real
trick
is
to
be
there,
at
least
at
the
beginning,
to
be
able
to
answer
most
of
their
questions,
especially
because,
like
the
git
extension
is
a
already
a
tough
one,
because
there
is
a
site
on
the
server
side
and
there's
a
side
on
the
front-end
side.
And
so
there
is
already
quite
a
lot
of
thing
to
understand
in
the
way
the
software
is
working.
G
So
what
we
are
doing
every
time
is
First
also
to
list
a
couple
of
small
issue
that
they
can
use
as
a
entry
points
to
start
to
dig
into
the
code,
because
that's
easier
to
to
go
inside
a
code
when
you
have
something
to
do
than
just
trying
to
look
at
the
various
file
and
I
I
mean
like
after
two
or
three
months,
they
can
definitely
start
to
be
very
independent
and
trying
to
solve
the
trouble
so
or
either
I
got
lucky,
but
I,
don't
think
so.
I
think
it's
achievable.
E
You
know
we're
always
trying
to
onboard
people
right
and
do
the
best
we
can
but
like
when
I
say
we
I'm
talking
like
me
and
isabella-ish
right,
but
we're
we're
not
slinging
Cloud.
The
way
you
are
so
I
think
sometimes
when
we're
onboarding
people
and
trying
to
help
them
understand
such
a
large
codes
code
base.
G
A
Yeah,
thank
you
for
answering
that
I
I'm
gonna
give
people
a
few
more
seconds
with
questions
here.
Any
other
thoughts
on
this
extension
I
know
it's
a
pretty
popular
one
and
there's
been
a
lot
of
changes
over
these
last
three
terms,
or
at
least
that's
what
I'm.
Seeing
from
the
demos,
it's
super
cool.
A
F
G
Thanks
you
little
so,
if
I,
if
you
want
a
bit
more
details,
it's
like
there's
private
companies
that
say
we
are
interested
supporting
that
that
open
source,
the
library
or
stuff
like
that,
and
so
there
are
rule,
is
to
contact
the
maintainer
of
the
project
and
try
to
figure
out
if
the
guys
can
help
or
not.
So
that
will
depend
on
which
kind
of
support
they
will
need
to
provide
to
the
student,
and
then
they
put
everybody
together,
meaning
like
the
student,
the
client
and
the
maintainer,
and
then
you
get
basically
as
a
maintainer.
A
C
I
would
like
to
talk
about
two
totally
unrelated
things.
The
first
one
is
about
lumino,
the
library
and
the
toolkit
underlying
Jupiter
lab
and
notebook
7.,
and
we
are
releasing
a
major
version
of
lumino,
the
second
major
version
It's,
a
slow-moving
Library.
It's
meant
to
not
change
very
much
and
we've
had
things
in
it
for
a
few
years
now
that
have
been
deprecated
but
kept
because
it's
meant
to
not
be
that
disruptive,
but
now
is
a
good
opportunity
to
change
them.
C
So
there
are
two
groups
of
users
who
will
notice
the
benefits
from
this.
One
is
people
who
work
on
either
core
or
third-party
extensions,
and
the
changes
you
will
notice
are.
There
are
more
native
Concepts
that
you
probably
already
know
that
are
now
part
of
lumino,
whereas
before
there
were
kind
of
our
version,
because
lumino
came
out
at
a
time
before
all
the
browsers
we
wanted
to
support,
add
native
iterators.
C
So
there
was
a
whole
set
of
data
structures
and
utility
functions
that
gave
you
the
the
same
sort
of
footprint
that
native
JavaScript
iterators
do,
but
now
we
use
just
the
Native
ones,
but,
more
importantly,
there's
some
nice
new
apis,
so
Fred,
who
was
just
talking,
has
been
working
on
a
the
ability
to
dynamically
deactivate.
Plugins,
normally
well,
not
normal
up
until
now
in
Jupiter
lab,
if
you
uninstall
an
extension
or
disable
it,
it
requires
at
the
barest
minimum,
a
page
refresh
but
more
frequently
a
server
restart.
C
But
now
we
have
the
basis
for
deactivating
plugins
without
having
to
refresh
your
page.
This
hasn't
landed
in
lab
yet,
but
this
is
the
underlying
set
of
tools
you
need
to
have
something
like
live
extension,
plugging
and
unplugging,
and
it's
pretty
cool
I,
also
linked
to
the
pr
that
updates
Jupiter
lab
from
luminol
one
to
lumino2.
So
you
get
a
sense
of
what
kind
of
code
changes
might
percolate
down
to
your
extension.
C
If
you
maintain
an
extension
for
the
most
part,
it's
just
updating
your
library
versions
and
if
you
were
using
custom,
lumino
iterators
switching
to
Native,
but
it
should
be
fairly
lightweight.
Jupiter
lab
is
a
very
large
code
base
and
you
can
see
that
the
amount
of
changes
that
actually
touch
code
are
pretty
minimal.
C
C
Cool
so
I
mentioned
this
last
call,
but
now
some
things
have
moved
in
the
next
three
months.
Jupiter
is
changing
its
governance
structure
from
having
a
benevolent
dictator
for
Life,
a
pdfl
plus
a
Jupiter
steering
Council
to
a
model
that
is
different
councils
at
different
tiers
of
the
project.
So
each
sub-project
has
its
own
group
of
decision
makers
who
are
named
and
then
there's
a
group
of
delegates
from
each
of
those
sub
projects
called
the
software
steering
Council
where
they
make
decisions
on
Jupiter
enhancement,
proposals
and
cross
project.
C
It
doesn't
really
have
that
big,
a
practical
effect
on
most
people's
day-to-day
other
than
you
kind
of
now
have
an
easier
way
to
discover
who
to
talk
to.
If
you
have
a
question
or
how
to
get
a
decision
made.
If
you
want
to
advocate
for
something,
as
opposed
to
kind
of
knowing
the
right
people
or
that
sort
of
that
sort
of
dynamic,
that
can
happen
in
a
smaller
project
and
yeah
I
think
it'll
be
good.
I
think
there
will
be
more
conversation
around
this
as
we
continue.
A
And
I
actually
really
appreciate
it
being
raised
again
on
a
recorded
call.
I
guess:
we've
had
that
with
the
Jupiter
lab
calls
now,
but
sometimes
when
people
ask
me
things
it's
great
to
have
a
place
to
point
them.
So
thank
you
for
the
continued
updates,
I'm
sure
you're
a
little
like
man,
I
get
to
say
this
over
and
over,
but
I
appreciate
it.
A
B
C
Yeah,
so
Jupiter
has
grown
organically
for
a
long
time
right.
It
started
as
I
python
almost
20
years
ago,
and
then
it
changed
to
Jupiter
in
like
2014
and
for
the
longest
time
it
was.
Basically
if
you
participate
in
the
project
and
you
become
a
contributor
who's
been
around
for
a
couple
years,
then
we
would
ask
you
if
you
want
to
join
the
Jupiter
steering
Council
and
the
steering
Council
was
a
decision-making
body
where,
if
it
couldn't
reach
consensus,
it
would
have
the
backstop
of
going
to
Fernando
the
founder
of
the
project
to
say
Hey.
C
You
know
help
us
sort
this
out,
but
that
model
is
probably
more
appropriate
for
a
smaller
project
and
the
steering
Council
grew
to
be
17
people
and
then
stopped
there,
because
17
is
already
too
large.
But
you
know
contributors
kept
coming
and
there's
a
lot
of
people
who,
at
that
point
we
didn't
have
this
way
of
acknowledging
their
participation.
So
part
of
the
new
governance
was
creating
this
concept
of
the
Jupiter
distinguished
contributor,
which
is
an
award
and
a
recognition.
You
get
your
picture
on
the
web
page.
C
C
An
informal
governance
often
leads
to
who
do
you
know
and
who's
popular
and
it's
you
know,
there's
this
foundational
essay
that
a
lot
of
us
found
really
influential
that
you
can
look
up
called
The
Tyranny
of
structurelessness
and
it's
about
what
happens
when
you
don't
actually
know
where
accountability
truly
is,
and
it
creates
these
sort
of
structures
that
are
difficult
to
navigate
and
not
always
fair
right,
and
so
instead,
we
just
thought
all
right.
Well,
how
does
this
project
actually
run?
C
How
can
we
best
represent
the
way
it
actually
is
functioning,
and
how
do
we
make
sure
that
the
bottlenecks
that
we
found
in
the
past,
like
getting
17
people
to
decide
anything
is
hard?
How
do
we
make
sure
those
bottlenecks
go
away
and
we've
been
working
on
rewriting
the
governance
for
a
couple
years
now
covet
didn't
help
right
if
we'd
been
meeting
in
person
that
probably
would
have
gone
a
bit
faster,
but
actually
not
that
much
faster,
probably
because
it's
it's
hard
to
get
buy-in
and
consensus
from
a
project.
C
C
I,
don't
want
to
overstate
how
the
tutorial
the
last
system
was
because
it
really
was
almost
always
the
case
that
the
Jupiter
steering
Council
made
the
decisions.
It
was
more
that
if
the
steering
Council
ever
found
itself
in
a
deadlock
that
was
the
backstop
and
the
moral
Authority
always
came
from
well
I
founded
the
project
and
everyone
respects
me
and
that
sort
of
dynamic.
C
But
you
know
if
you,
if
you
compare
it
to
other
organizations,
whether
they
are
businesses
or
governments
or
local
or
whatever
like
after
some
time,
you
need
to
have
representation
at
many
different
levels
right.
So
you
have
your
homeowners
association,
which
in
America
is
a
terrible
thing,
but
in
other
countries
actually
might
work
right,
and
then
you
have
local
councils
and
school
boards.
And
then
you
have.
You
know
city,
government
and
state
government,
and
you
know
so.
C
The
these
sorts
of
tiers,
I
think
the
larger
the
group
of
people
working
on
this
project
is
the
more
we
need
to
figure
out.
How
do
we
make
sure
that
when
the
Jupiter
server
team
meets
and
they
want
to
bring
in
a
new
sub
project,
a
new
sorry,
a
new
project
that
you
know
isn't
part
of
Jupiter
into
the
Jupiter
server
sub
project?
How
do
they
do
it
right?
Is
it
just
one
person
flips
a
switch
or
is
it
like?
C
There's
a
group
of
people
who
can
talk
about
it
and
make
a
decision
and
that
happening
in
a
formal
way
is
at
fundamentally
just
more
fair
and
and
at
least
then
you
can
say,
hey
look.
Eight
people
voted
against
us
and
that's
why
we're
not
doing
it?
It's
not
just
because
I,
don't
like
you
that
kind
of
thing.
A
What
do
you
think
to
vote
on
this
thing
that
you
know
nothing
about
because
you're
not
following
that
project
has
been
like
a
perhaps
not
intended
benefit,
but
usually
like
I'm
close
enough
to
things
that
I'm
being
asked
about
now
too,
which
I
really
like.
So
maybe
that's
a
weird,
but
yes,
we
are
running
into
the
security
call.
So
sorry,
you
can
continue
conversations
later.
I
don't
want
to
wrap
up,
but
Darian
did
you
have
anything
you
wanted
to
finalize
there?
No.