►
From YouTube: Community Standup: 9/3/19
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
Yeah
I
mean
I'm
ready.
We
can
dive
into
something
all.
B
E
Yet
excellent
I.
B
B
All
right,
so
I
I've
been
spending
a
lot
of
time
on
documenting
the
the
release
process,
with
particular
emphasis
on
the
curriculum
side
of
things,
but
also
try
to
take
the
opportunity
to
do
the
same
for
the
platform.
The
two
are
similar.
They
use
the
same
generally
the
same
kind
of
release
like
technical
semantics,
like
we
usually
have
a
release
branch-
and
you
know
they
use
semantic
versioning
and
all
that
kind
of
stuff,
but
there
are
differences,
especially
with
respects,
to
what
goes
in
to
them
in
terms
of
planning,
and
this
came
up.
B
I
first
thought
this
is
something
we
should
have
been
doing
a
long
time
ago,
but
in
the
in
the
last
release,
one
of
the
things
that
came
up
was
that
you
know
I
I
really
wanted
to
start
having
the
community
tests.
You
know
the
changes
to
the
release
and
I
I
I
didn't
I
didn't
get
finished
with
all
the
changes
that
I
thought
needed
to
be
made
until
I.
Don't
know
like
Thursday
of
that
week.
B
It's
left
like
two
days
prior
to
the
weekend
that
I
wanted
to
deploy
the
the
new,
the
new
curriculum,
which
had
some
time
constraints,
because
that
was
the
excuse
me.
That
was
the
less.
That
was
the
the
release
that
included
the
batch
lesson,
which
was
something
packet
pushers
was
waiting
on,
so
we're
trying
to
get
it
all
working
and
it
just
felt
rushed
so
that,
combined
with
the
fact
that
we
should
have
been
doing
this
a
long
time
ago.
B
B
What
can
we
expect
it
at
the
end
in
terms
of
testing
and
how
long
that
that
time
is
dedicated
for
all
kinds
of
stuff,
like
that
now,
the
next
version
of
the
curriculum
we're
just
gonna,
do
a
patch
release,
so
version
one
does
0.1
as
a
basically
a
way
of
doing
a
test
run
of
the
new
release
plan.
So
if
you
go
to
the
it's
go
to
the
forum,
you
can
click
that
topic
and
you
can
see
I
posted
a
forum
post
here.
B
This
is
this
is
gonna,
be
the
the
format,
the
general
format
that
you're
gonna
see
for
any
for
any
of
these
kickoffs
really,
especially
for
the
curriculum.
They're
gonna,
look
very
similar
to
this,
because
every
everyone
needs
to
have
a
platform
target.
Each
one
needs
to
have
a
project
plan,
meaning
the
things
that
you
actually
are
gonna
do
in
the
/
in
the
in
this
release
and
then
an
ideal
target
release
date.
This
is
not
strict,
but
it's
also.
It
also
should
be.
B
You
know
somewhat
firm
like
we
should
we
invested
a
lot
in
making
the
workflows
for
the
curriculum
release
really
really
lightweight,
so
there
should
be.
It
should
be
rare
that
anything
like
really
severely
pushes
target
release
dates.
Just
because
we
can
we
can
do.
We
can
do
curriculum
leases.
So
often
it
just
kind
of
doesn't
make
sense
to
hold
it
up.
Hold
a
release
up
for
anything
really
well.
I'm
sure
there'll
be
exceptions
to
that.
But
that's
generally
true,
if
you
open
a
new
tab
with
this
link,
I
would
recommend
taking
a
peek
at
that.
B
That
is
the
new
curriculum
release
process.
It's
in
the
Docs,
but
you
know
it's
again.
This
is
what
this
is
meant
to
test
the
process.
So
it's
by
no
means
finished.
If
we
feel
like
something
didn't
work
out,
we
want
to
change
something
or
add
something.
Then
we
can
do
that.
That's
totally
fine
and
as
as
the
as
part
of
the
release
process,
I
posted
this
over
the
weekend.
But
this
this
stand-up
serves
as
like
the
formal
kickoff
for
the
for
this
release.
B
So
the
release
is
version
zero
or
one
does
they're,
not
one
we're
gonna
be
targeting
version
platform
platform
version
zero,
four
zero,
which
is
the
current
release
version.
In
fact,
I
expect
even
the
next
curriculum
version
will
target
that
that
which
will,
by
the
way,
that's
that's
gonna,
be
common.
Now
that
we've
split
the
two
I
expect
that
the
curriculum
release
cycle
will
be
much
quicker
than
that
of
the
platform
just
because
of
the
nature
of
the
two.
If
you
open
this
link,
this
is
also
something
very
useful.
I
have
done.
B
This
I've
been
using
github
projects
since
the
beginning
of
the
project.
In
fact,
I've
been
using
github
projects
since
they
were
released.
It's
since
get
upgraded
them,
however,
the
the
it
hasn't
been
a
always
obvious
that
then
I've
been
doing
that,
and
even
if
that's
true,
even
if
somebody
found
these,
they
didn't
know
I
still
what
they
were
from
so
in
the
new
in
the
new
process
for
doing
for
doing
releases.
It's
like
a
first-class
citizen.
B
It
that's
part
of
the
actual
release
process,
so
in
step,
one,
which
is
what
we're
doing
right
now
we
are
yeah.
You
know
why
I
posted
a
forum
thread
and
we're
having
this
stand
up
and
we're
talking
about
open
issues
or
PRS
that
need
to
be
included
in
this
release
and
we've
decided
to
target
version
0.40.
And
finally,
we
have
this
curriculum.
We
we
have
a
project
plan,
that's
created
in
the
curriculum,
repos
project
lists,
so
you
see
we're
in
the
curriculum
repo.
We,
the
project's
tab
and
versions.
The
1.0.1
is
right
here.
B
This
is
where
the
platform
release
planning
is
a
little
different.
If
you've
noticed
me,
that's
primarily
where
I've
been
using
this
this
these
github
projects,
which
are
kind
of
like
Kanban
boards.
You
can
kind
of
think
of
them
that
way
they
actually
work
they
autumn
they're
automated
that
way,
in
fact,
so
as
you
close
issues,
they
move
from
left
to
right,
which
is
really
cool,
very
useful
and
if
you're
not
used,
one
of
these
I
should
take
a
step
back.
B
Actually,
if
he's
not
used
one
of
these
before
this
is
a
pretty
pretty
typical
tool
to
use
in
in
software
development,
especially
those
that
have
gone
in
the
agile
direction.
But,
to
be
honest,
it's
I
think
it's
grown
well
beyond
that,
and
even
even
people
who
hate
hatch
hole
will
still
use
Kanban
boards,
because
they're
very
useful
I
used
to.
In
fact,
I
got
my
first
year.
Exposure
to
these,
when
I
was
working
on
the
open
daylight
project,
they
used
them
in
the
sub
project
that
I
was
working
on.
B
It
was
Trello,
which
is
probably
something
you
guys
have
seen
before.
The
cool
thing
about
github
projects
is
they've,
got
everything
that
you
probably
wanted
to
see
from
Trello,
but
their
automated
based
on
github
hooks,
and
things
like
that.
You
don't
have
to
write
that
automation.
So
if
you
want
to
see
like
where
the
release
is
like
where,
where
how
close
are
we
to
releasing
versions,
one
does
0.1
use.
Take
a
peek
at
this
everything.
Everything
needs
to
move
generally
from
left
to
right.
So
these
are
all
the
things
that
are
not
done.
B
These
are
all
the
things
that
are
done
or
are
being
done.
They
are
in
progress
and
these
are
the
things
that
are
done
and
actually
this
is
merged.
So
I'm
not
sure
why
this
is
in
progress.
That's
done
and
that's
it.
So,
generally
speaking,
every
for
every
release
we
have
this
plan.
The
objective
is
to
get
things
from
left
to
right.
As
soon
as
everything
in
the
is
in
the
right
column,
we
are
ready
to
do
the
release
every
once
in
a
while,
and
this
this
does
happen
every
once
in
a
while.
B
I'm
not
going
to
be
crazy,
strict,
it's
just
a
guide,
the
the
purpose
of
the
release
planning
in
general,
not
to
capture
everything
that
could
possibly
need
to
get
done
in
a
release
mostly
to
capture
the
things
that
we
should
hold
a
release
up
for
you
know
basically
the
things
that
are
that
are
they're
too
important
to
keep
going
with
like
I.
We
know
that
we
need
to
fix
the
issue
in
the
stack
storm
lesson,
which
is
something
toad
and
I
have
discussed.
B
So
we
want
to
raise
that
here.
These
are
things
that
we
need
to
get
them
in
this
release,
or
rather
really
should
get
done
at
the
very
least
that
doesn't
mean
this
is
all
they
can
get
done.
In
fact,
I
think
I
say
that
in
the
docs
now
like
three
times
so
I'll
say
it
again
here,
but
that's
kind
of
the
point
so
as
soon
as
everything
is
from
left
to
right.
B
That's
that's
when
we
do
the
release,
if
you
want
to
take,
take
a
peek
at
the
platform
release
planning
by
the
way
it's
fairly
similar.
There
are
some
key
differences,
especially
with
respect
to
testing
anything.
To
get
into
the
specific
technical
details
is
gonna
be
different,
obviously,
because
it's
a
different
project
entirely.
B
You'll
also
notice
that,
instead
of
at
the
repo
level,
the
project
planning
for
the
platform
is
done
at
an
oral.
So
you
go
to
you,
go
to
the
organ
and
click
projects.
You'll
see
the
antidote
versions
up
here
and
you'll
notice.
Previously
that
I
did
ooh,
there's
a
bunch
of
post
release,
stuff
I
need
to
update,
see
I'm,
not
following
my
own
stuff.
This
is
why
we
need
to
plan.
The
next
version
is
0.4
dot,
one
which
I
did
already
create.
B
I
haven't
done
the
release
kickoff
for
this,
just
because
I
I,
don't
know
why
I
just
didn't
I'll
do
that
next,
but
yeah
the
thing
to
go
to
for
now
is
the
forum.
That's,
like
gonna,
hold
all
the
information
together.
So
if
you
go
there
and
you
click
click,
you
click
the
the
release.
Kickoff
version,
one
that
about
1
you'll,
see
everything
you
need
there.
The
thing
I
need
from
everybody,
it
looks
like
cloud
toad
has
commented
already
is
between
now
and
the
next
standup.
B
We
should
capture.
Take
a
look
at
the
project
plan,
see
what's
in
there
and
then
comment
here.
This
is
this
is
where
we
should
communicate
regarding
the
release
planning
for
this
version.
If
you
have
anything
that
you
think
needs
to
get
done
in
this
release,
that,
like
I,
said
you,
you
know
you
want
us
to
be,
you
want
us
to
be
aware
of
it
and
we
should
hold
up
the
release
we
should.
We
should
not
actually
do
the
release
until
the
thing
you
think
should
be
done
is
done.
B
B
A
B
A
B
B
C
D
D
D
I
have
so
today,
I'll
post
enough
for
army,
just
fr
our
image
to
our
s3
bucket
and
I'll
work
on
getting
the
an
example.
B
B
All
I'm
gonna
try
to
make
I'm
gonna
try
to
my
best
to
get
PTR
existing
again
this
week,
the
ideal,
and
that
way
we
can,
you
know,
always
nightly
see
like
what
the
latest
is
in
terms
of
in
terms
of
what
the
you
know,
what
the
curriculum
is
doing.
It'll
help
with
the
curriculum
release
process
to
then,
when
I,
whenever
we
do
a
quick
release
will
just
say
like
yeah.
Basically,
whatever
PTR
looks
like
that's
what
we're
gonna
release.
D
E
Sure,
sorry
and
I've
missed
one
of
the
statements
that
I've
acted.
There
was
anything
else
but
I'm,
looking
at
the
number
201
style
checks
and
enforcement
in
CI
there's
a
couple
linter
that
could
provide
support
for
this,
such
as
a
markdown
CLI.
D
E
D
D
E
D
B
Be
great
I,
don't
know
if
you've
looked
at
the
way
that
circle
CI
is
being
yearly.
There's
no
circle
see
I'm
coq
au
vin
in
the
platform,
its
coverage
tool.
It's
you
could
actually
make
certain
github
checks,
not
blocking.
So
if
they
fail,
they
don't
necessarily
result
in
you
know
they
they
don't
they
don't
prevent
the
merge
of
a
pull
request
like
we
should
probably
consider
that,
because
if
you're
gonna
get
a
lot
of
false
positives,
it
might
be
useful
just
to
have
just
to
have
a
tool
that
provides
a
report
of
like
here
here.
B
B
B
Idea,
I
think
that
I
wrote
I
created
the
issue
a
long
time
ago.
As
you
can
see,
it's
changed
hands
in
terms
of
which
release
I
wanted
to
put
it
in
several
times,
but
if
memory
serves
when
I
was
looking,
what
I
was
looking
to
do
was
basically
build,
not
just
not
just
one
tool
but
like
have
like
a
suite
of
different
tools
that
check
different
things
and
then
I
was
gonna,
wrap
them
all
underneath
one
umbrella,
okay,
I
have
I,
remember
I,
remember
starting
work
on
this
I.
Just
don't
remember
what
came
of
it.
E
B
B
Yeah,
that's
that
I
think
that's
what
I
started
working
on
I
wish
I
wish
I
remember
what
I
did
with
all
of
that,
but
I
do
remember.
Having
worked
on
that
because
I
I
was
I
was
I
was
building
my
own
dictionary
of
like
terms
that
were
fine,
as
you
can
imagine,
there
are
a
lot
of
terms
we
use
in
the
curriculum
are
really
a
networking
and
in
general
that
are
not
in
your
average
dictionary.
B
D
Nope,
okay,
then
I'm
gonna
call
time
of
death
and
I'll
get
the
I'll
actually
download
this
one
and
edit
it,
because
obviously
there
was
like
a
pretty
significant
gaps
in
time
with
silence
and
then
I'll
post.
It
immediately
for
the
notes
I'm,
just
gonna
put
in
there
that
Matt
went
over
the
product.
You
know
where
it
basically
announced.
You
know
weird
that
this
was
the
kickoff
for
the
you
know,
for
the
curriculum
release
and
I'll
put
in
some
links
to
where
he
was
pointing
to.
D
D
A
Two
different
things:
one
is
moving
the
licenses
for
the
curriculum
from
Apache
to
CC.
By
the
other
thing
is,
we
will
need
to
put
in
instructions
about
putting
in
the
the
note
and
I
can't
I.
Don't
know
why
my
brain
will
not
remember
the
term
but
anyway
they
note
that
says:
yay
verily
I'm
allowed
to
contribute
this.
Those
are
two
separate
things.
What
is
the
type
of
license?
The
other
is,
is
the
developer
certificate.
A
D
D
D
Yeah
developers,
okay,
I'll,
put
in
those
notes
and
then
and
that's
it
and
I'll
post
them
on
the
website.
So
thank
you
for
joining
everyone
and
Stephen
in
particular,
and
we'll
see
you
next
week.