►
From YouTube: SimPEG Governance Meeting: April 5th, 2021
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Excellent,
well
thanks
everyone
yeah
thanks
for
taking
time
to
chat
about
this
today.
I
think
it's
a
good
timing.
You
know
we
had
time
to
think
on
all
of
this
for
for
quite
a
while
earlier
conversations
for
maybe
like
a
couple
months
ago
at
this
point
yeah,
so
I
sketched
out
a
document
which
I'm
just
gonna
assume.
Has
everyone
actually
looked
at
or
do
you
want
to
go
over
briefly
together
everyone's
looked
at
it?
A
Okay,
then
we
don't
need
to
go
through
that
sort
of
step
by
step,
but
basically
wanted
to
sort
of
get
feedback
suggestions
on
kind
of
what
put
in
there.
A
So,
the
idea
being
that,
like
we
want
to
sort
of
aim
towards
and
eventually
develop
a
steering
council
and
consider
starting
a
non-profit,
but
I
think
we're
still
slightly
too
early
stages
on
both
of
those
is,
if
we
don't
have
money
coming
in
and
we
don't
have
anybody
who's
currently
like
in
in
desperate
need
of
funding,
then
there's
not
like
a
burning
need
for
a
non-profit
yeah
and
then
in
terms
of
a
steering
council.
A
I
think
that
is
a
good
idea,
but
I
think
we
do
need
to
kind
of
figure
out
like
what
sorts
of
decisions
and
like
what
sort
of
role
it
would
play
before
forming
it.
I
think
that
forming
it
before
we
know
what
it
does
could
could
end
up
being
just
a
bit
clunky
so
yeah.
So
my
suggestion
is
basically
like.
Do
we
want
to
kind
of
formalize
two
of
the
roles
we
talked
about
in
the
previous
document,
so
sort
of
like
a
managing
director,
bdfl
and
a
director
of
operations?
A
What
do
folks
think
of
that
and
then
also
I'm
sort
of
like
self-volunteering,
to
build
the
managing
director
role
and
if
anyone
has
concerns
questions
anything
like
that
thinks
it's
a
terrible
idea,
I'm
all
ears
yeah.
So
I
don't
know
who
wants
to
kick
off
with
whatever
thoughts
you've
had
a
chance
to
formulate.
C
I
like
it,
I
like
it's.
It's
short,
it's
concise,
it's
easy
to
read
and
understandable,
so
I
actually
don't
have
anything
to
criticize
or
to
change.
Yeah
I
mean
from,
I
think,
all
the
discussions
we
had
it's
now
much
shorter
and
I
think
it's
good
for
a
start
and
it
could
be
build
up
on
it
later.
C
D
Yeah,
I
think
I
think
at
this
point
it's
definitely
a
good
idea
just
to
finalize
these
roles
first
and
then
go
on
with
the
other
parts.
I
also
would
like
to
echo
dom's
comment
that
he
wrote
in
there
about
having
more
outline
goals
for
the
project
in
general,
because
it's
kind
of
open-ended
at
this
point
yeah.
It
is
like
whoever
wants
to
work
on
something
kind
of
spearheads
that
goes
forward,
so
it'd
be
really
nice
to
kind
of
come
together
and
have
the
big
goals
for
the
project
for
the
next.
You
know
few
years.
E
Yeah
and
even
I
think
in
the
short
term,
you
know
in
order
to
be
able
to
tackle
the
the
ongoing
growing
list
of
issues
is
that
it
would
be
great
if
we
start
planning
releases,
you
know,
say:
0-15
we're
going
to
attack
all
these
issues
because
they're
all
like
you
know,
do
something,
and
then
you
know
16
we're
gonna,
do
these
ones
and
so
forth,
and
so
on.
E
It
doesn't
mean
that
we
cannot
like
introduce
something
new
if
someone
is
interested
in
pushing
it
right
now,
but
I
think
he
would
give
us
more
like
a
direction
right
like
we
kind
of
missing
direction
or
like
goals,
I
guess
it's
kind
of
open-ended,
as
joel
said
so.
It'd
be
great.
I
think
if,
if
the
director
of
operations
and
the
managing
director
would
agree
on
on
set
goals,.
E
E
A
B
Very
reasonable
good
step
forward.
It.
F
No,
not
particularly,
I
think
it's
I
I
mean
like
the
way,
you've
kind
of
formatted.
This
is,
you
know,
postponing
stuff
and
then
kind
of
taking
things
on
as
need
basis
and
yeah.
So
I
I
think
it's
a
matter
yeah,
I'm
just
trying
to
kind
of
assess
what
those
next
steps
are.
At
this
point,
I
don't
have
any
you
know
particular
sage
advice
really.
G
I
know
tebow
what
was
your
yeah?
No
like
that?
Look
like
I
agree
with
it
like
it's.
The
document
was
good
and,
like
short,
and
I
agree
that
the
the
position
where
we
you
you
just
mentioned,
it's
kind
of
the
minimum
that
we're
already
working
on
it's
just
we
like
like.
We
are
officializing
that
that's
good
and
yeah,
like
like
dumb's
comment
about
having
a
mission
statement,
also
is
useful.
G
I
also
actually
added
a
small
comment
on
that
in
the
in
the
dark
of
like
if
it's
a
useful
question
of
asking
yourself
like
how
do
we
see
think
peg
in
one
years
in
two
years,
five
years
or
even
ten
years
down
the
road?
What
does
it
look
like,
and
I
think
that
answering
that
also
will
also
help
with
dumb's
point
of
like
right
now.
Think
peg
is
yeah
really
move
forward
based
on
our
academic
research,
which
has
give
it
like
a
very
good
kick
in
et
cetera
and
like
we.
G
We
have
like
very
advanced
tool
in
that,
but
we're
all
like
it's
like,
but
we
also
yeah
lacking
some
like
basic
tools
that
sometimes
like,
like
block
people
of
like
I'm,
just
wondering
I'm
just
thinking
again,
like
I'm
doing
joint
inversion
with
a
simple,
but
at
the
same
time
somebody
else
tried
to
plot
like
a
pseudo
section
of
a
dc
survey
and
the
result
is
really
not
as
satisfying
as
like
residing
and
in
their
mind,
it's
like,
oh,
if
it
cannot
plot
it,
it
cannot
invert
it
which
is
not
true
but
yeah
so
like
there
is
really
a
disbalance
in
that
and
how
we
accomplish.
G
That
of,
like
moving
away
from
the
only
academic
driven
is
like.
I
think
it's
a
question
we're
trying
to
answer
right
now
with
doug
and
with
with
my
attacks
and
myra
and
diaz.
But
it's
it's
maybe
something
that
we
will
need
more
thoughts
as
well.
A
Yeah
and
having
I
think
some
of
these,
like
I
think,
to
the
point
of
sort
of
release
plans,
but
also
like
I,
like
dom's
suggestion
of
kind
of
going
in
and
grouping
issues.
You
know
we
sort
of
have
tags
right
now,
but
they're
not
necessarily
like
we
apply
them
pretty
ad
hoc
and
so
to
have
a
bit
of
structure
around.
E
To
me,
the
you
know
the
one
year:
okay,
one
year
is,
is
very
short-term,
but
then
two
five
years
it
all
depends
who's
going
to
be
around
right.
Yeah,
and
you
know
I'm
seeing
you
guys,
you
know
joe
and
lindsey
are,
I
guess,
more
advanced
and
probably
later
down
the
road
too,
but
eventually
you
guys
are
going
to
have
grad
students
as
well
right,
and
then
these
guys
are
probably
you
know.
It
makes
sense
for
your
grad
students
to
like
take
on
issues
and
you
know,
write
more
codes
and
how
to
send
bags.
E
So
I
think
we
kind
of
need
to
align
ourselves.
That
way
is
that
you
know
I'm
gonna
line
up
a
lot
of
work.
You
know
a
backlog
of
tasks
and
then
it's
to
assume
that
at
some
point
someone
else
is
going
to
come
in
and
help
out
and
push
this
further.
As
long
as
it's
well
laid
out
it
you
know
it
would
make.
It
would
just
be
easy
to
to
give
to
someone
else.
A
F
Ask
so
are
there
any
so
thinking
of
jaja's
group
and
or
jaguars
are
trying
to
motivate
anybody
to
kind
of
contribute?
Is
there
any
kind
of
I
don't
know
special
in
incentive
or
acknowledgement
or
something
that's
a
little
bit
more
of
a
enticement
to
really
kind
of
get
people
on
boarded
and
particular
things.
A
That's
a
good
question.
I
think
what
we
should
do
is
actually
make
more
use
of
the
website.
We
have
right
now
is
to
be
able
to
list
contributors
and
so
have
folks
be
able
to
have
their
name
on
there.
A
They
can
right
now
in
the
like
simpeg
repository,
but
it
would
be
nice
if
that
was
actually
kind
of
front
and
center
on
the
simpeg
website,
and
I
think
same
thing,
with
kind
of
like
institutional
logos
and
and
groups
like
acknowledging
that
mira
and
diaz
are
contributing
to
the
project
by
allowing
folks
to
put
time
time
onto
the
project,
and
so
giving
sort
of
giving
an
acknowledgement
in
those
in
those
ways
would
be.
I
think,
an
important
step.
A
F
I
was
just
thinking
about
the
you
know,
some
kind
of
as
part
of
the
page,
like
a
set
of
items
that
you
know
had
been
done
and
contributed
by
a
certain
person,
and
you
know
just
so
that
you
know
for
this
particular
you
know
week
on
august,
the
5th
you
know
joe
did
did,
did
something,
and
here
here's
a
you
know
a
one-line
description
of
what
he
did
and
then
it
just
kind
of
keeps
cycling
through,
so
that
you
know
it's
just
another
way
of
sort
of
capturing.
D
Yeah,
I
mean
it
right
now:
it
doesn't
kind
of
happen
on
a
weekly
basis,
but
I've
been
trying
to
add
in
every
time
we
do
the
release,
notes
and
everything.
I
make
note
of
people
that
have
added
to
it
every
time
and
like
specific
pull
requests
and
things
like
that.
I
do
make
note
of
it
and
put
it
in
there.
F
Yeah,
I
was
just
kind
of
thinking
more
of
something
that
was
continuously
updated.
You
know
just
you
know
somebody.
Somebody
does
something
writes
a
one
sentence
description,
but
he
did.
You
know
this
goes
up
in
a
you
know
like
a
continual
feed,
there's
a
picture
and
there's
yeah
he
what
he
did.
If
nobody
else
does
anything
then
he's
up
front
and
center
for
a
week,
but
if
somebody
else
does
something
he's
kind
of
pushed
off,
so
there's
an
incentive
to
try
to
you
know,
keep
your
picture
up.
There.
D
Yeah,
it's
kind
of
a
you
could
you're
kind
of
described
like
it's
almost
like
a
news
feed
of
simpeg,
almost
maybe
something
on
the
like.
You
know
what
I
mean
like
it
seems
like
it's
almost
like
a
news.
Feed
like
it's
like,
oh
man,
look
at
this
one,
this
person
just
added
this
impact.
Look
at
what
this
person
just
added
to
something.
A
We
definitely
could
we
do
have
the
twitter
account,
which
we
hardly
use,
there's
also
the
this
week
channel
on
slack
that
we
could
use.
I
mean
what
we
did
do
in
the
past
and
be
happy
to
revive
this.
If
it's
of
enough
interest
is
that
folks,
just
posted
a
screenshot
of
something
and
like
three
to
five
bullet
points
of,
I
did
something
cool
with
some
peg
or
synthetic
related
this
week,
and
then
we
just
put
that
in
a
blog
post.
F
A
C
It
is
probably
but
something
we
would
have
to
be
very
clear
who's.
The
audience
yeah,
because
I
think
any
developer
would
probably
look
and
go
to
the
commit
feed
in
github
to
see
who
is
committing
and
who
is
what.
So,
then
we
will
have
to
see
how
much
is
the
effort
to
put
in
and
how
much
is
what
we
gain
from
it,
because,
as
I
see
it
as
it's
described
to
be
mostly
to
attract
new
users
or
new
developers,
because
I
don't
see
that
it
would
help.
F
Yeah,
I
think
that
would
be
a
main
part.
This
is
something
it
just.
It's
kind
of
follow
up
on
what
lindsay
had
said
with
respect
to
you
know
getting
jaja's
group
excited
and
committing
parsing
stuff
out
to
to
them,
and
whoever
else
is
just
yeah.
You
know
just
to
do
something
and
you
know
have
your
your
picture
come
up
and
a
short
description
of
what
you
did,
and
you
know
at
least
it
was
there
momentarily
and
then
next
time
you
look
you're
getting
the
list
someplace,
but.
A
Is
it's
not
hard
to
get
a
twitter
feed
on
a
website,
and
so,
if
and
and
that
could
be
a
very
easy
way
to
give
shout
outs,
is
that
when
a
new
release
is
out
with
a
contribution
from
a
new
contributor,
we
make
sure
that
that
that
their
name
is
is
mentioned
in
that
tweet.
And
then
that
just
goes
to
the
website.
And
then
we
don't
have
to
manually
maintain
first.
A
F
C
C
E
D
A
A
A
A
Okay,
so
what
I
was
thinking
is
then
to
start
making
use
of
the
simpag
community
repository
to
be
kind
of
the
place
where
we
track
these
sorts
of
decisions,
and
also
where
we
make
suggestions
about
practices
like
doug's
suggestion
of
making
sure
we
find
mechanisms
for
giving
shoutouts
to
new
contributors,
those
sorts
of
things
so
kind
of
like
a
meta
layer
on
on
simpeg
being
this
community
repository.
A
As
a
bit
of
like
I,
don't
know,
a
formal,
formal
issue,
a
document,
that's
a
bit
of
a
guide
that
if
we
can
point
folks
to
if
they're
new
to
the
community
and
want
to
know
how
decisions
are
made
and
those
sorts
of
things
have
that
there
and
then
use
that
as
a
space
to
kind
of
prioritize
things
like
drafting
a
mission
statement,
a
a
couple
year
plan
and
we
don't
necessarily
need
to
draft
them
in
like
github
issues.
But
at
least
those
issues
can
track.
Google
docs
and
things
like
that.
A
So
I
guess,
or
at
first
does
anyone
have
concerns
about
that?
Does
that
sound,
reasonable.
B
A
Okay,
so
then
I
guess
what
my
asks
will
be
in
that
sense
is
like
well,
maybe
I'll
write
this
up,
we'll
make
it
as
a
pull
request
and
then
probably
just
ask
for
like
thumbs
up
edits
from
folks.
We
can
leave
it
open
for
a
week
or
so,
and
then
it's
something
we
can
always
iterate
on,
but
you
know
leave
it,
leave
it
open.
So
there's
time
for
input
and
in
particular
joe,
your
input
to
on
your
roll
definition
would
be
would
be
very,
very
helpful,
so
we
can
get.
A
We
can
get
that
in
sort
of
as
top
priority
and
then
start
to
think
on
drafting
some
of
these
documents
and
making
some
updates
to
the
websites
and
these
sorts
of
things
and
and
prioritizing
what
we
think
needs
to
be
done
kind
of
first
and
first
order.
Second
order,
these
these
sorts
of
things.
E
Okay
and
you
it's
going
to
be
you
just
like
how
are
you
going
to
what
kind
of
document
are
you
going
to
put
up
there.
A
So
I'll
just
create,
like,
I
think,
just
a
markdown
document
and
that's
something
that
if
we
want
to
build
it
into
a
website,
that's
that's
easy.
Yeah.
B
A
A
E
D
E
G
D
G
Don't
know
yeah,
it's
not
easy.
Well,
it's
like
you
can
look
at
how
many
people
are
on
discourse
and
how
many
on
the
slack
and
how
many
overlaps
there
is,
but
it's
like,
like
the
slack,
is
getting
pretty
decent,
like
with
on
the
general
channel,
we're
like
close
to
400.
F
G
C
C
C
G
F
A
So
for
the
mission
statement,
ideas,
I'm
sure
folks
here
have
seen
the.
Why
statement
that
rowan
he's
the
one
who
led
that,
but
soggy
myself
worked
with
him
on
that
in
2015.
So
quite
a
while
ago
I
just
dropped
the
link
in
there.
It's
probably
a
bit
longer
than
what
a
mission
statement
is,
but
in
a
sense
it's
a
nice
document
to
look
back
on
as
kind
of
some
of
the
original
motivation.
C
It
reminds
me
of
the
discussion
we
had
about
the
description
of
inversion
and
I
think
it
got
stuck
right.
G
B
B
B
E
E
E
E
Yeah,
so
do
we
want
to
exclude
seismic,
or
you
know,
because
I
said,
there's,
obviously
a
ton
of
packages
with
size
mac
and
we're
like
we
don't
have
any
experience
much
enough
right
yeah.
F
Do
you
need
to
get
down
to
that
level?
I
mean
you're
operating
here
at
a
pretty
high
level
for
for
just
computational
geoscience
for
simulation
and
inversion.
I
mean
whether
you're
a
different
discipline
or
not
doesn't
at
this
level,
doesn't
make
much
difference.
I
think,
especially
if
you're
going
to
be
limited
to,
let's
say
two
sentences.
D
D
Yeah,
because
right
we've
developed
all
these
tools
that
are,
we
develop
them
all,
consistent
manner
that
you
can
pick
and
choose
what
you
want
and
combine
them
like
combine
the
modules
together
in
certain
ways
they
all
implement
similar.
Like
similar.
You
know
similar
methods,
similar
things
like
the
similar
apis.
They
all
kind
of
work
in
a
similar
manner,
and
the
point
is,
you
can
just
take.
Take
one
module
here:
okay,
plug
it
in
here
and
get
get
a
result,
take
a
different
module
plug
it
into
the
same
thing
and
get
a
result.
D
E
G
D
Like
I
don't
know
like
it's
not
like
we're
not
like
we're
claiming
to
be
able
to
simulate
any
like
everything
we're
just
trying
to
we're
claiming
I
don't
know,
I
guess
it's
a
difference
of
I
don't
know
our
goal
is
to
support
anything
versus
our
versus
our
goal
is
to
implement
everything
like
it's.
I
think
it's
subtly
different
there,
but
I
feel
like
the
first
one
is
more
of
our
our
goals
right.
Our
goal
is
to
support
anything.
A
To
me,
that
brings
back
some
of
the
language
of
like
the
idea
of
simpeg
as
a
framework
is
that
our
goal
is
that
the
framework
is
flexible,
extensible
and
supports
a
wide
number
of
methods,
but
that
doesn't
necessarily
mean
that
we
need
to
be
on
the
hook
for
writing
them
all
like.
It
would
be
great
if
we
can
plug
into
other
forward
simulators
for
seismic,
and
we
don't
necessarily
need
to
maintain
that.
But
it's
still
within
perhaps
our
like
our
mission
to
be
able
to
interface
to.
A
A
A
E
It's
yeah,
I
capture
the
the
current
state
of
you,
know
the
knowledge
in
in
a
way
you
know
the
technical
advancements
like
capture
it
and
then
standardize
it
in
a
way
so
that
we
can
build
further
it's
hard.
So
it
should
be
easier.
E
A
G
G
G
E
D
I
guess
you
could
say
we
could
say
that
it
makes
it
like
we're
trying
to
make
it
a
little
bit
easier
for
people
to
use
recent
research.
You
know
what
I
mean
like
right:
it's,
okay,
we're
trying
to
make
joint
version
more
tractable
for
different
for
anyone
kind
of
thing.
It's
like.
G
E
You
have
a
lot
of
good
words
in
there.
Just
put
some
auxiliary
words
off.
A
G
C
C
A
C
Also,
just
the
fact
that
you
can
that's
it's
another
black
box
right
yeah,
I
mean
that
that
that
could
even
be
with
a
closed
source.
When
you
can
read
the
code,
I
mean
that
that's
where
it
becomes
messy,
it
can
have
a
close
source
license,
but
the
code
can
still
be
visible,
which
would
already
be
better
than
a
black
box
where
you
cannot
see
the
code
so.
G
It
was
also
like
it's
also
what
has
been
used
a
lot
for
us
since
the
beginning,
like
it's,
been
a
crucial
support
tool
for
our
like
everybody's
research
and
that
any
benefits
from
from
it
and
yeah.
That's
what
drove
the
development
also.
E
A
Well,
do
you
folks
want
to
take
a
crack
at
just
like
putting
a
sentence
in
before
the
meeting
next
week
and
like
we
can
challenge
everyone
to
do
that?
If
we
all
add
one
we'll
have
quite
a
number
to
look
at
and
see
what
elements
we
like
and
not
yeah
for
me,
that's
something
that
I
need
to
like
sit
and
think
quietly,
but.
D
C
E
A
A
G
A
Think
you
can
make
it
public.
I
don't
have
any
concerns
with
that
anybody
else,
like
all
of
the
rest
of
our
things,.
G
A
I
think
we
could
just
bring
this
up
at
the
weekly
meeting
and
then
handle
things
on
github
for
now
and
then,
if
there's
other
stuff
that
comes
up
just
make
those
agenda
items
and
if
we
need
another
dedicated
meeting
we
can.
We
can
kick
something
off,
but
I
don't
know
unless
anyone
else
here
feels
like
we
need
another
dedicated
meeting
on
this.