►
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
A
B
Morning,
everybody,
hello,
Mike,
welcome,
Jonathan
and
moonwalk
from
the.
C
D
C
B
Just
setting
up
the.
C
D
E
C
B
D
B
Cool
Let's
see
we
could
do
project
updates
or
we
could
just
be
open
discussion,
whatever
I
I
would
I
I
would
love
to
know.
I
looked
at
an
update
on
the
virtual
maintainer
Summit.
E
Well,
I
can
tell
you
Michael,
we
are
this,
this
Friday,
it's
our
internal
deadline
to
get
all
the
contact
information
for
the
our
list
of
attendees,
okay,
and
with
that
we
are
going
to
send
it
to
events,
so
they
are
going
to
use
a
very
similar
template
that
we
have
for
the
panelists,
so
they
can
submit
their
own
attend
these
candidates
to
attend
the
the
event.
So
we
received
some
feedback
about
the
name,
so
we
decided
to
add
mini
Summit
in
front
of
it,
because
it's
a
small
trial
version
one
day
yeah.
E
So
that's
that's
where
we
are.
We
and
the
other
thing
that
we
are
working,
but
we
have
a
little
bit
more
time.
Is
the
questionnaire
like
the
survey
that
we
want
to
send
to
the
attendees
and
well,
the
entity
is
a
candidate
there.
We
want
get
us
as
many
feedback
as
possible,
so
we
are
defining
the
questions
with
the
proposed
answers
or
the
type
of
answers,
keeping
in
mind
that
this
should
be
filled
out
in
15
to
25
minutes,
so
yeah
I
think
we're
in
good
shape.
E
Now
on
part
of
the
organization.
We
are
four
people.
It
is
Emily,
Emily
has
been
extremely
supportive.
I
cannot
stress
that
the
other
person
is
Lori.
Lorusso
she's,
also
very,
very
active
on
the
open
source.
Community
Mona
were
Alex
and,
and
me
were
five
yeah,
so
I
I
think
we're
in
Excel
in
shape.
We
already
have
feedback
from
from
other
people,
David
wheeler
about
several
things
like
in
our
slide
deck.
D
F
So
right,
Michelle,
sir
sorry,
you
wanna
go
ahead.
First.
F
So
there
are
three
critical
groups
of
people,
so
what
there
is
the
group
of
panelists
there's
the
group
of
moderators
and
then
there's
a
group
of
participants
who
will
be
in
those
moderated
sessions.
So
far
we
have
gotten
a
core
list
of
panelists
we
are
connecting
with
them.
We
should
be
good
with
that.
We
have
confirmed
with
the
moderators
most
many
of
them
are
people
within
the
like
open
ssf,
so
that
we
are
good
with
that
as
well.
F
We
have
just
started
like
like
collecting
or
collating
a
list
of
potential
contacts
of
of
the
actual
participants,
and
it's
it's
only
like
about
six
weeks
away
and
that
actually
makes
all
of
us
a
little
bit
nervous.
So
that's
why
we're
internal
deadline
this
week,
but
like
there
was.
F
There
is
a
list
that
we
have
created
where
we
have
listed
the
open
source
projects,
but
we
don't
necessarily
have
contacts
of
the
maintainers
of
those
projects
like
any
emails,
any
direct
emails
or
contacts
and
like
how
do
so
I
mean
the
list
of
Open
Source
projects
is
easy
because
we
can
just
look
into
the
top
open
source
problems
that
have
been
created
by
other
groups.
F
We
have
just
listed
them,
but
how
do
we
so,
for
example,
go
was
listed
and
I've
been
trying
to
connect
with
the
good
team
and,
like
so
far
like
I've,
so
now,
I've
been
able
to
get
reach,
get
hold
of
the
security
people
who
are
involved
in
go
and
then
help
then
ask
for
their
help
to
get
or
nominee
get
some
nomination.
So
that's
one
case.
We
have
to
do
this
case
by
case
and
we
probably
need
about
12
to
15
projects
each
nominating
about
two
to
three
people
for
that.
F
So
that's
the
hardest
part
where
we
would
appreciate
help
is
perhaps
like,
if
you
know,
top
open
source
projects
and
also
the
maintainers,
through
your
Alpha
contacts
that,
like
direct
connections
made
to
us
and
because
that
would
Fast
Track
the
way
of
confirming
that
okay,
we
have
a
core
group
of
30
35
participants.
Already
it.
B
E
I
have
just
shared
the
document
that
we
have
for
the
list
of
attendees
on
the
chat.
So,
as
you
can
see,
what
we
did.
It's
also
contacted
by,
or
at
least
is
that
person
is
in
charge
of
getting
a
name
that
it's
important
into
the
said
project
or
the
organization,
so
I'm
doing
I'm
I'm
doing
a
little
bit
of
progress
on
the
ones
that
we
defined.
So
yes,
but
if,
if
somebody
has
more
information,
this
is
this
is
the
moment
what
we
needed
more
perfect.
F
And
I'm
going
to
add
new
projects
to
this
and
and
put
process,
so
it
doesn't
have
to
be
these
Pro
people
from
these
projects.
There
can
be
other
projects
right
that
can
be
added
with
with
people
I
mean.
The
idea
is
to
probably
go
like
go
through
our
personal
contacts
at
this
particular
point
so
that
you
can
Fast
Track
the
currency.
E
I
mean
this
list.
That
is
right
now
there
it's
taken
directly
from
the
critical
projects
from
the
working
group
from
the
top
critical
projects
from
that
working
group.
That
is
the
official
list
that
they
have
listed
in
the
GitHub
page,
but
I
mean
if
you
have
an
author
project,
that
we
should
send
this
invitation
like
nominate
three
candidates
for
attending
the
summit.
This
is
the
moment
to
do
that.
Like.
F
For
example,
here
we
don't
have
any
anything
from
JavaScript
site,
but
I
mean
you
guys,
obviously
have
very
good
connection
with
the
npm
people
yeah,
because
of
the
and
so
use
that
or
leverage
upon
that
to
get
like
five
projects
like
jQuery
or
yeah,
I
mean
the
big
or
prototype
or
I
mean
the
big
JavaScript
projects
have
like
one
or
two
maintenance
from
each
each
one
of
them
yeah.
So
we
have
three
or
four
of
that
and
we
have
like
about
10
people
already.
B
E
B
No
node
I'll
do
Michael
Dawson
I.
B
E
And
and
as
I
said,
the
objective
is
to
provide
this
list
to
events
as
soon
as
possible,
so
they
handcraft
the
email
like
what
not
handcraft
they.
We
already
provided
the
template
and
they
send
it
the
information
and
have
the
the
form
to
enter
the
candidates
perfect
and,
of
course,
we
are
asking
them
to
nominate
themselves
if
they
wish
so.
F
Yeah,
so
basically
the
burden
between
now
and
the
actual
event
date,
which
is
January
25,
is
that
we
need
to
contact
with
people
that
person
may
actually
nominate
himself
or
herself
that's
great
or,
if
not,
then,
for
the
larger
projects
like,
for
example,
Eclipse.
They
would
actually
find
out
three
say:
random,
Pro
or
sample
sample
projects
or
representative
projects
and
and
nominate
some
people
there.
F
Then
we
have
to
get
their
confirmation
that
they
have
to
be
available
in
that
date
and
before
January
25
we
are
also
requesting
them
to
fill
up
a
survey.
So
these
are
the
burdens
that
each
of
the
participants
have
to
go
through
or
stuff
that
they
have
to
go
through
before
doing
it
and
and
yeah
six
weeks
is
yeah
and
it
will
come
and
go
pretty
quickly.
Yeah.
B
Let's,
let's
do
it
I'm
filling
in
so
for
everybody
else.
B
Please
click
on
the
link
and,
if
you
can,
if
you,
if
you
recognize
any
of
these
projects
or
can
dig
out
of
contact,
let's
do
that
for
the
next
like
15
minutes
and
see
if
we
can
get
this
sheet
filled
out
and
that
way
and
what
I'll
do
is,
let's
leave
column
e
empty,
which
means
that
we
haven't
actually
contacted
these
people
so
and
that
way,
because
I,
don't
wanna
I,
don't
fill
out
the
row
and
make
it
unclear
whether
or
not
these
people
need
to
be
contacted
or
not
right.
E
D
F
Came
up
so
I
was
connecting
with
some
people
kind
of
priming
them
up
for
like
and
making
them
aware
of
the
event
and
then
basically
like
again
priming
them
up
for
the
invitation.
That's
gonna
come
that's
gonna
be
sent
to
them
by
next
week
or
something
like
that.
But
then
everybody
was
asking
like
about
more
information.
We
don't
have
a
website
planned
or
or
anything,
so
that's
something
that
we
probably
need
to
also.
F
For
example,
the
format
when
is
that
like
we're
a
winner
so
specifically
and
and
the
goals
in
general,
like
we
just
talk
about
what
all
of
us
know
what
the
the
mini,
Summit
or
open
source
maintainers
is
but
like
what
are
the
goals?
What
do
we
want
to
achieve,
and
so
on?
So
it's
just
like
a
one-pager
thing
that
we
I
think
it's
it's
very
critical,
yeah.
B
I
I
I
can
make
this
one
really
easy.
Just
throw
put
a
pull
request
into
the
working
group,
repo
create
a
folder
wherever
you
think
it
makes
sense.
We'll.
B
And
then
you
can
control
that
content
and
if
we
can
create
like
a
bitly
link
or
or
something
like
that,
and
then
have
that
just
just
point
there
that
might
be
easier
if
you
want
to
do
it
through,
like
the
marketing
open
ssf.org
operations
at
opennessep.org
can
help
set
that
up.
But
there's
there's
more,
you
know
you.
Can
you
can't
make
updates
yourself?
E
Okay,
then,
let's
I
I
can
create
one
hour
a
document
and
we
can
do
the
pull
request
then
bye
soon,
yes,
perfect,
okay,
I
will
do
that.
Thank
you
and
the
information
that's
going
to
like
it's
the
first
slides
of
our
internal
deck
slide.
Yeah.
E
D
B
Go
I
found
me
gnu
people.
B
B
Homebrew,
didn't
we
have,
we
know
somebody.
Homework
has
come
up
a
lot
randomly.
Do
you
know
the
Homebrew
folks,
yes,
could
I'm,
sorry,
I'm,
sorry,
I'm
drawing
a
bike.
Is
that
you
or
do
you
know
the
people?
No,
that's
me
it
is.
Oh
also.
Could
we
add
you
to
the
to
list
here
sure
awesome.
D
D
E
B
Cool
okay,
so
I'm
gonna,
let's
switch
so.
E
If,
if
you
think
about
somebody
else,
remember
we
are
our
internal
deadline.
Is
this
Friday,
but
it
will
land
in
events
next
week,
perfect.
B
Cool,
let's
see
if
there
anyone
would
like
to
give
other
updates
on
things
that
are
going
on.
A
Yeah
I
can
give
a
quick
one
on
the
risk
Matrix
on
the
risk,
Matrix
dashboard
yeah.
You
know,
we've
had
a
couple
of
great
meetings
over
the
last
a
couple
of
weeks
resulting
and
now
we're
working
on
a
good
mock-up.
A
We
ran
through
some
of
the
different
requirements,
both
the
physical,
both
a
business
and
functional
requirements
of
it,
we're
able
to
go
back
now
to
the
to
the
LFX
folks
and
and
they're
able
to
put
together.
So
we
we
haven't
settled
yet
on
what
we
were
going
to
use.
A
You
know
as
a
as
a
as
a
platform
and
all
that,
but
what
we
did
focus
on
now
were
the
requirements
of
what
what
all
needed
to
be
on
the
dashboard,
and
we
did
it
enough
to
go
and
get
a
good
mock-up
done
so
that
we
could
take
a
look
and
see
what's
missing,
identify
any
gaps,
they're
in
and
and
all
that
kind
of
stuff.
A
So
we've
made
some
really
really
good
Headway
over
the
last
couple
weeks
that
that's
actually
pretty
exciting
too,
because
you
know
a
lot
a
lot
of
the
information
that
a
little
beyond
that
they
could
benefit
everyone.
And
then
we
also
were
trying
to
figure
out
look
at
this,
not
on
the
God
I.
A
Don't
even
have
the
I
was
trying
to
find
get
to
get
the
page
up
to
actually
be
a
little
bit
more
detailed
on
on
on
what
was
on
what
we
covered,
but
I
guess:
I'll,
keep
it
very
high
level
I,
don't
I
think
we
have
another
meeting
this
week
and
I
think
we'll
adjourn
after
that
for
the
year,
but
I
think
after
this
week
we
should
be
able
to
bring
something
back
and
I.
Think
I,
think
I.
A
Think
they'll
kill
me
for
saying
this
I
think
I
think
we'll
be
able
to
bring
something
back
to
this
group
come
early
next
year,
just
to
just
just
to
bring
it
back
to
the
working
group
and
say
hey.
This
is
where
we're
at
now
and
to
give
a
look
at
that
mock-up
and
all
that
come
the
beginning
of
the
year.
A
So
that's
actually
really
exciting,
because
we
are
a
lot
further
along
I
want
to
say
that
I
thought
we
would
be,
but
but
we
seem
to
be
gelling
together
enough,
where,
where
we're
gonna
produce
something,
that's
pretty
exciting.
That.
B
Is
awesome,
I
posted
a
link
because
I
saw
neurod
posted
a
mock-up
in
slack
it
just
posted
a
link
to
that
to
the
slack
channel
in
the
mock-up.
So
yeah
that
looks
that
looks
awesome,
Randall.
B
F
C
B
Totally,
would
you
mind
adding
them
to
the
yeah
I'll
talk.
I'll,
add
a
note
and
I'll
talk
to
that
group
of
people.
That'd
be
awesome,
thank
you
and
I'm.
Sorry,
I'm.
Sorry,
I
I,
probably
shouldn't
be
the
one
saying.
Yes,
that's,
okay!
So
sorry,
if
the
folks
that
are
running
the
project,
don't
think
it's
okay,
please
say
no.
A
G
No
I
think
you
kind
of
got
it
right.
We
got
like
a
mock-ups
and
then
that
did
a
really
good
job
and
kind
of
like
the
first
proof
of
concept.
So
they
got
started.
Were
they
gonna,
stop
building
it
right
now
and
then
kind
of
like
make
it
available
early
next
year
that
product
I
can't
quite
remember,
yeah.
A
I
know:
I
know
that
that
we
had
we
had
what
we
had
before
the
meeting
last
week,
and
then
we
had
a
couple
of
additional
things,
so
he
was
going
to
put
those
things
to
put
those
things
in
for
for
the
next
one.
But
if
you
put
it
all
up
already
I'll
take
a
look
at
that,
but
I
think
that's
where
we
landed
on
I'm,
not
sure
about
an
initial
build.
A
But
if
we
did
that,
that
would
be
great
too
right,
just
just
as
just
as
an
initial
build
I
think
we
still
need
to
discuss
or
figure
out
what
the
right,
what
the
right
platform
is
for
it,
but
hell.
If
we
get
an
initial
build
out.
That
would
be
great
for
the
working
group
yep
you
see
as
well.
G
And
I
believe
the
next
meeting
I,
don't
think
it's
this
week.
It
might
be.
The
next
week
could
be
wrong.
The
following
week
might
be
take
a
look
yeah
just
in
case
others
wanted
to
attend
foreign.
B
B
F
B
Know
that
we're
targeting
next
week
but
I
think
it'll
probably
be
the
week
after,
but
I
appreciate,
appreciate
all
of
your
help
with
that
Randall
as.
B
I
don't
have
too
much
else
to
to
talk
about.
Today,
we've
been
making
progress
on
the
Assurance
assertions,
I
know
that's
being
driven
out
of
Alpha
Omega,
but
the
the
same
links
that
we
talked
about
last
time,
the
mvsr
deck
I'll
post
it
again,
but
that
one's
I
think
that's
a
couple
updates.
We
did
get
the
code
in
though
so
it's
it's
now
live
on.
The
I
mean
AO.
D
B
Cool,
if
there's
nothing
else,
I'll
give
a
little
bit
of
time
back,
but
if
there
is,
we
can
still
we
can
stay
in
chat,
Last
Chance,
three,
two
one!
Thank
you
all
very
much
have
a
great
holiday.
So,
as
I
mentioned
earlier,
we're
canceling
the
21st,
so
I
will
see
everyone
on
the
whatever
that
is
like
the
third
of
January
and
looking
forward
to
everything.
If
you
need
me,
ping
me
on
slack,
I'll
be
around
for
the
for
the
hard
not
like
going
anywhere,
but
thanks
everybody.