►
From YouTube: SunPy Developer Discussion
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).
B
E
A
So
oh
yeah
Andy,
where
are
we
for
me?
0.6
therefore
take
well.
A
Is
it
by
bettany
Brittany.
B
A
A
B
F
A
So
I
have
a
question
for
you
about
that
Stewart.
So
so,
yeah
I
saw
your
comment
about
not
removing
the
carrots
three
carrots
which
I
hate
well,.
F
Now
you
know
in
the
other
documentation
on
Africa
for
a
trip,
I
docks
or
actually
in
the
Python
docks
themselves.
There's
a
you:
can
click
a
button
to
get
rid
of
them,
yeah
able
to
rid
to
the
output
I'm
trying
to
pull
that
over
I'll
get
around
to
doing
that
at
some
point,
yeah
may
or
may
not
happen
before
nor
point
six,
but.
F
F
A
A
A
Okay,
well,
so
we
need
somebody
to
kind
of
go
through
a
lot
of
well,
not
one
person
necessarily,
but
we
need
to
go
through
all
the
docs.
A
I'm
doing
the
minimum
possible
such
that
I
can
put
in
the
plot
directive
everywhere,
so
some
places
it's
a
little
bit
weird
because
it
says
like
Oh
from
the
last
cent.
If
we
make
this
one
change,
then
it
generates
this
other
different
plot
and
so
I
make
sure
to
like
change
the
wording
a
little
bit
so
that
you
know
it's
a
little
bit
more
clear.
A
C
E
A
F
F
A
But
I
don't
want
this
to
be
like
another
month
of
delay.
40
point
six,
it's
true!
It's
true!
Neither
you
can
either.
F
A
F
F
C
A
D
C
F
F
F
F
I
had
I
did
a
bit
of
read
the
docs
fixing
a
couple
of
weeks
ago,
like
I,
had
to
put
in
some
hacks
in
the
setup
I
file
specifically
for
read
the
dogs,
because
we
didn't
have
read
permission
right:
permissions
on
whatever
assets,
the
home
directory,
so
the
config
file
was
no
longer
writable,
which
mail
import.
Some
pie
was
failing,
which
means
all
the
documentation
bills
were
fighting.
So
there's
now
like
a
hack
inside
both
kogda
pie
and
set
up
a
pie
that
moves
the
home
directory
on,
read
the
doc
still
business.
It
was
horrific.
A
I
mean
the
other
thing
I'm
concerned
about
I
mean
going
about
messing
with
the
docs,
is
sort
of
like
opening
a
can
of
worms.
I
found
a
few
bugs,
while
going
through
the
docs
and
I.
Imagine
that
we
will
find
more
of
those
which
will
then
turn
in
which,
which
is
not
to
say
that
this
shouldn't
be
done,
but
it
will
turn
that
particular
thing
into
a
much
larger
piece
of
work.
Well,
we
already
knew
this.
We
said
this
wedding.
Do
me
that
the
docs
need
a
renovating.
F
A
A
A
A
No,
no
but
I
guess
my
preference
would
be
that
we
do
as
much
in
the
docks
as
we
can
given
given
a
limit
in
time.
So
we
say:
okay
in
two
weeks,
you
know
what
in
one
week,
whatever
we
do
as
much
as
we
can
and
then
we
push
everything
all
those
bug
fixes
and
doc
fix
is
to
a
point
release
later
on.
If
we
can't
finish
the.
F
Gonna
be
finished,
we're
shuttle
this
is.
We
should
at
least
at
least
any
known
bugs
should
be
faked
before
release.
If
we
find
a
bug
I'm
not
releasing
until
it's
fixed,
that's
just
stupid
the
type
bug,
yes,
I'm
sure
all
right,
I,
don't
know
like
I,
don't
mean
like
something
absurd
like
rewrite
the
entirety
of
the
map
class,
because
something
shown
slightly
wonky
I
mean
like
functionality
that
currently
exists.
That
is
not
what,
as
documented.
A
Yeah
I
mean
it
I
think
that
does
I
mean
I
agree
with
you,
the
some
level,
though
it
does
go
to
go
counter
to
what
we
had
discussed
previously,
was
just
that
we
were
going
to
have
faster
release
cycles.
So
that
means
that
does
essentially
assume
having
slyly
buggy
releases
that
we
continuously
effects,
as
opposed
to
having
massive
I
mean.
F
Like
which
is
what
we're
doing
now,
my
point
is
that
we
should
look
the
doc
we've
done
a
massive
amount
of
changes,
insights
on
fire
for
this
release
yeah,
but
those
changes
have
been
ducked
right.
It's
fine
as
long
as
those
changes
have
been
docked
and
we
fixed
all
the
bugs
that
we
know
about
in
the
code.
That's
fine!
Okay,
but
if
we
find
to
show
fix-
and
the
other
thing
is,
we
should
go
and
I
mean
I
know
who
talks
a
lot
of
the
changes,
but
I
still
think
we.
A
B
A
C
When
you
find
the
WCS
/
great
so,
and
the
documentation
that
you're
saying
today
so
I
mean
you're,
claiming
some
pie
can
do
this
and
you
find
out
that
it
doesn't
so
there's
either
two
things:
either
remove
it
from
the
docks.
When
you
fix
the
bug,
yeah.
C
E
F
F
F
F
In
the
uber,
what
two
of
the
two
of
the
examples
are
running?
Okay,
all
right
now,
that's
failing
cause
trying
to
save
out
an
applet
live
animation
and
that's
failing
because
the
printing
order
of
databases
or
not
a
printing
order
of
databases,
not
a
deterministic.
Apparently,
we've
got
two
fails
in
map
where
it's
trying
to
save
out
an
animation
to
a
file
and
then
ffmpeg
is
installed
on
Travis
and
we've
got
10
files
in
database
where
the
ordering
of
the
database
results
is
wrong,
not
wrong.
Just
different.
F
But
I
don't
see
any
reason
why
we
can't
merge
this
bill
because
currently
Travis
is
set.
The
dot
skip
first,
the
doc
test
to
allow
fail,
so
we
can
keep
an
eye
on
it
a
bit
and
we
can
fix
it
more
if
we
go
along
I
just
think
those
changes
to
documentation,
including
all
because
that
PR
contains
a
lot
of
fixes
to
the
examples
in
the
documentation.
So
therefore
it's
there,
we
should
merge
it.
We
weren't
running
doc
tests
at
all
before
so
now
that
12
of
them
are
failing
is
an
improvement.
F
F
F
C
D
F
D
Jesse,
it's
close
enough
people
to
do
this
kind
of
pass
through
the
dock,
to
make
sure
that
we
aren't
saying
something
bigger
because
the
other
day.
But
aside
from
that
and
whatever
issues
crop
up
yeah,
we
can
prioritize
of
bugs
exciting
new
pics
and
will
prefer
anything
that
fixed
it's
going
to
take
more
than
a
couple
of.
D
Let's
think
we
have
a
target
that
we
need
to
have
people
do
a
doc
pass
within
the
next
week.
If
people
can
do
within
the
next
week
or
we
watch
the
two
weeks.
C
F
D
Wcs
axis
fix
rabbit,
that's
not
going
to
change
the
documentation
side
right,
so
people
inside
from
use
to
ur
to
go
ahead,
who
pass
through
documentation,
including
me
who
pass
through
documentation.
Let's
make
sure
that
there
aren't
something
obvious.
That's
wrong!
Cease
work!
Getting
this
plot.
The
right
facade,
I
just
want
to
make
sure
the
text
and
they're
reasonably
represents
within
0.6
and
yeah
any
bugs
be
fine
grow
into
the
issue.
Tracker.
Okay,.
B
F
A
F
F
F
B
C
A
B
D
A
A
A
F
D
C
E
A
C
E
E
E
It
doesn't
allow
on
the
schools,
because
it's
let
me
get,
but
it
hates
me.
D
A
Okay,
so
what
is
left.
A
B
B
F
F
I
depends
how
that
plays
out
when
we're
ready
to
go
well.
If
we
well
we're
basing
it
looking
like
work
and
we
do
the
actual
nor
point
six
reduces
the
feel
like
it's
going
to
be
dependent
on
a
WCS
ex
he's,
not
point
5
for
this
as
well.
So.
D
C
A
A
C
A
A
B
D
E
A
A
F
D
E
B
E
B
A
F
F
It's
fine!
If
you
only
want
to
plot
images,
you
know
that
actually,
but
they
obey
the
standard
document
and
I'm
only
gonna
chastise
EIT
for
not
obeying
it
a
little
bit
because
it
was
actually,
you
know,
created
before
the
standard
document.
But
someone
threw
a
rock
and
alex
young
me
suddenly
sees
me.
He
promised
he
was
going
to
reprocess.
All
the
AIT
day
to
an
archive
is
somewhere
for
me
like
good.