►
Description
A
No,
hello,
welcome
to
the
new
Jesus
technical
steering
committee
meeting
for
Liz.
It's
November,
the
8th,
2017
I
am
Jerry
simple
and
I
am
cheering
for
a
couple
weeks
instead
of
Michael
Dawson,
so
yeah
on
the
agenda.
Today
we
have
a
bunch
of
stuff,
so
I
guess
we
should.
Since
we've
been
doing
this
recently,
I'm
do
a
call
for
any
announcements.
Anyone
has
to
make.
C
C
D
E
E
F
I
mean
I
think,
and
the
discussion
was
around
whether
that
was
too
late.
So
I
I
mean
I
haven't
looked
recently,
but
it
was
definitely
one
of
the
initial
suggestions.
There
was
some
comments
about
whether
there
was
anything
we
could
do
earlier,
but
I
don't
know
if
it's
progressed
since
then,
but
that's
probably
the
place
near
the
discussion
right,
I
think.
E
B
Let's
cut
into
the
issue
which
has
been
pasted
into
the
chat,
didn't
the
summit
repo.
There
is
the
issue
that
the
summit-
repo
may
not
be
the
most
visible
place,
but
I
guess
between
stat
mention
field
and
that's
a
conversation
for
another
day.
But
that's
see,
that's
that's
one
thing
I
want
to
make
sure
it
got
got,
got
aired,
I
want
to
make
sure
they
didn't
get
forgotten.
So
there
you
go.
Okay,.
A
E
A
F
Yeah
I
think
we
started
the
discussion
on
that
last
week.
The
real
I
think
the
the
point
for
discussion
still
is
what
the
scope
of
things
that
we
include
in
those
strategic
initiatives
would
be.
There's
some
concern
that,
like
you
know,
if
we
have
too
big
a
set,
then
we
won't
have
enough
focus
so
I
think
that's
where
the
the
ongoing
input
and
discussion
needs
to
go
is
like
the
list
that
we
have
there
is
that
the
right
size
list
are
those
things
we
should
take
off.
F
That
list
to
be
more
focused,
and
you
know,
I
think
it's
still
on
my
TS
the
agenda
cuz,
it's
something
we
want
to
close
on
fairly
soon,
at
least
in
my
opinion.
We
want
to
have
a
section
in
the
agenda
where
we
go
over
those,
and
so
even
if
we
have
the
wrong
list,
you
know
I
might
suggest
that
you
know
we
don't
wait
two
months
trying
to
figure
out
the
right
list,
we
put
it
on
the
agenda
and
start
discussing
them
in
you
know
we
find
it.
F
F
So
my
suggestion
might
be
like
what
I
would
say
is
is
get
in
there
make
those
colors
to
say.
Let's
just
go
ahead,
if
it
doesn't
happen
before
I
get
back
like
I'm
away
next
week,
but
if
it
doesn't
get
doesn't
happen,
you
know
somebody
could
do
it.
We
could
add
it
to
the
agenda
that
doesn't
happen.
We
come
back.
I
will
add
it
to
the
agenda.
We
have.
B
F
B
F
It's
perfectly
with
me:
I
just
wasn't
speaking
up
because
since
I'm
not
gonna
be
at
the
next
meeting,
I
I
didn't
want
to
volunteer
to
have
something
happen
or
not
happen,
but
yeah
I
I'd
be
quite
happy.
If
you
know
we
leave
it
till
then,
when
I
get
back
I'll
land,
it
it'll
be
on
the
agenda
and
well
you
know
I'll
figure
out
who
I
can
try
and
ask
to
talk
to
those
are
how
we,
how
we
kick
it
off
and
you
know
I'll
be
there
to
lead
that
that
would
work
well.
For
me.
A
B
A
G
Because
I
know
that
a
bunch
of
people
filled
that
out
last
week,
but
a
date
hasn't
been
decided
yet
and
I
know,
at
least
for
myself
my
times
that
I
filled
out
on
they're
slowly
becoming
no
longer
relevant.
So
I'd
like
to
I'd
like
to
push
that
we
picked
some
dates
there
as
soon
as
possible
and
if
that's
not
able
to
be
done,
I'm
more
than
happy
to
pick
that
up
and
move
it
forward.
E
B
G
F
F
If
there's
consensus,
I'm
moving
it
I
would
tend
to
prefer
the
code
of
conduct
to
remain
in
a
kissy
repose,
because
there
needs
to
be
a
perception
of
htsb
owning
that
process
in
terms
of
owning
a
responsibility
to
make
sure
the
deduction
for
I.
Think
it's
too
easy
for
us
to
just
say
that
somebody
else's
problem,
if
it's
over
in
another
view
now
there
were
somewhere
else
again.
It's
a
lot
of
hard
objection,
but
I
just
think
that
we
need
to
be
border.
It's
about
it!
F
G
For
me,
it
was
mostly
if
we
have
the
moderation
guidelines
and
all
the
other
stuff
living
in
the
admin
area.
Oh
and
everyone
is
using
the
same
code
of
conduct,
it
just
doesn't
make
a
lot
of
sense
for
me
for
it
to
live
in
the
technical
steering
committee-
repo,
as
opposed
to
the
in
Manresa
and
having
it
live
in
two
places,
creates
the
possibility
of
a
delta
being
created
between
the
documents,
which
is
already
threaded
to
happen
in
the
moderation
repo,
so
I
personally
like
to
see
it
live
in
one
place.
F
I
mean
I,
decided
I
think
we
wanted
a
demon
repo,
we
want
to
become
with
Kham
Kham,
but
if
we
need
to
add
some
words
to
where
we
reference
it
that
make
it
clear,
it's
our
responsibility
to
enforce
it.
That
might
help
because
agreed
it's
not
an
attempt
or
should
not
water
down
our
responsibility
in
any
way.
F
B
F
What
I
will
say
is
that
I
am
NOT
gonna
object,
moving
it
I.
You
know,
I
mainly
want
to
make
sure
that
the
concern
is
the
stress.
So
if
there
is
some,
if
there
is
some
language
in
there,
then
great,
but
it's
more
of
a
we
as
a
body
have
to
confirm
that.
Yes,
we're
not
giving
up
that
responsibility
right.
So
it's
it's
more
of
an
expectations
thing
on
us
than
anything
that
is
has
to
do
a
specific
language,
make
sense,
yep
I'm,
certainly
on
the
same
wavelength
as
you.
F
G
A
Okay,
so
I
know
the
last
issue.
That's
currently
on
the
agenda.
Awesome
admin,
repo
issue;
no,
this
is
not
in
the
admin
repo
okay,
this
isn't
the
no
geo
summit,
repo
issue
56,
which
is
a
node.js
collaborator
summit
in
Berlin
before
after
J's
company,
you
just
an
extension
of
the
discussion
in
the
from
in
the
announcements.
I,
don't.
B
A
So
I
well
I
have
a
comment
from
live
chat
which,
with
a
concern
that
I
also
share
so
journey,
says
I'm
worried
about
being
able
to
get
a
ticket
for
Jays
company
you,
since
they
go
fast,
I'd
like
to
attend,
but
I'm,
not
sure
if
they'd
be
able
to
get
a
ticket
and
the
brief
way.
No,
they
are
available.
A
A
E
A
F
Okay,
James
go
for
it,
so
you
know
just
reiterating
a
point
and
said
earlier
yeah,
it's
you
know
whatever
the
makeup
of
the
TSA
is
by
that
time
we
need
to
make
sure
we're
putting
a
priority
on
it.
Members
there.
So
you
know
as
much
as
possible
or
if
we
need
to
making
sure
that
they're
a
solid
remote
options
or
for
that
I
think
you
know
as
we're
going
through
the
planning
on
this.
That's
something
we
definitely
need
to
make.
You
know
we
need
to
include
I.
B
B
B
A
A
A
And
also
on
tomorrow,
the
NA
API
team
is
meeting
half
an
hour
after
the
community
ends,
which
would
be
10:30
Pacific
time,
I'm,
not
sure.
If
that
is
in
you
can
see,
and
then
into
next
week
on
Tuesday
1
p.m.
Pacific
time
the
build
working
group
is
meeting
and
on
Wednesday
next
week
we
have
moderation,
team
meeting
at
11:00
p.m.
Pacific.
The
Diagnostics
working
group
is
meeting
at
1:00
p.m.
Pacific,
and
our
next
node
is
TC
meeting
will
be
at
2
p.m.
SEC,
which
is
what
five
hours
later
than
this
meeting
slot
is
I.