►
Description
A
A
Nobody
else
has
any
the
the
one
that
I
would
share
is
that
the
the
open,
Jas
board
meeting
is
happening
tomorrow.
I
checked
the
board,
I,
don't
see
any
issues
there
and
I.
Don't
have
any
other
issues
that
have
been
raised
by
the
the
node.js
project
at
this
point,
but
if
there
is
something
urgent,
let
me
know
and
I'll
see
what
we
can
do
in
terms
of
getting
it
on
the
agenda.
A
The
other
thing
I
did
think
I'd
mentioned
it's.
It's
good
for
TC
member
awareness,
but
also
for
other
people.
Just
in
general
is
there
is
a
good
distribution
list
for
the
open,
GS
CPC
discussions.
So
if
you're
interested
in
kind
of
keeping
up
with
what
goes
on
there,
Jory's
been
sending
out
a
nice
sort
of
summary
of
what
was
discussed
in
the
last
meeting.
So
I'd
recommend
you
know
if
you
have
any
interest
in
following
what's
going
on,
that's
a
great
way
to
sort
of
stay
up
to
date,
with,
what's
going
on
day
to
day.
C
A
A
B
A
B
D
A
B
A
Sound
good
to
everybody,
okay,
so,
let's
move
on
to
the
next
one,
which
is
under
TSE,
seven
18,
which
is
nominating
Bethenny
to
the
TSC,
been
quite
a
bit
of
discussion.
I,
don't
know!
If
we
need
to
discuss
that
in
the
meeting.
It
was
actually
tagged
for
the
agenda
for
the
final
vote,
but
because
of
the
IBM
acquisition
of
Red
Hat,
closing
we're
over
number,
so
I.
Maybe
I
should
just
take
the
tag
off
until
we
come
to
a
conclusion
and.
A
B
A
C
B
A
B
A
Okay,
yeah,
okay,
so
we've
had
some
discussion
we'll
discuss
further
later
on
the
meeting.
Let's
move
on
to
the
next
one,
which
is
tracking
you
for
updating
TC
on
board
meetings.
I,
you
know,
I
will
be
going
to
the
first
40
meeting
this
week.
So,
like
I
said
my
only
thing
now
is
to
say
you
know:
is
there
anything
that
you
want
me
to
take
there?
Otherwise,
when
I
come
back
following
week,
I'll
report
on
on
what
I
can
well
I'm
in
the
last
issue.
A
That's
tagged
is
number
423
our
strategic
initiatives
so
I'm
going
to
open
that
up.
The
one
thing
I
will
start
out
with
just
because
we've
had
a
more
recent
discussion
on
that
and
I
think
makes
sense
to
have
a
little
bit
of
visibility.
Discussion
on,
even
though
we're
not
quite
ready,
is
the
Python,
the
the
forward,
progress
on
Python
and
three
and
Jim
a
rotted
open
an
issue
in
the
repo
suggesting
that
we,
you
know,
make
sure
that
we
have
a
path
per
for
see,
Klaus
who's,
actually
doing
a
lot
of
the
work.
Moving.
A
A
Actual
progress
there
what's
been
suggested
is
that
Klaus
is
going
to
provide
a
file
which
highlights
you
know
what
he
thinks
is
important
for
us
to
know
and
we'll
review
that
as
part
of
the
strategic
initiatives
review
like
you
know
that
we're
going
through
today,
and
we
don't-
we
don't
have
that
yet
so
what
next
meeting
we
should
have
that
in
place?
Does
that
make
sense
to
everybody
I
think
the
key
thing
is,
you
know
we're
two.
A
A
D
A
Then,
let's
go
through
the
list
of
initiatives
and
starting
with
I'm
just
going
to
look
through
so
any
pie.
We
just
had
a
new
release.
Yesterday
did
have
a
note
out
on
API.
We
did
have
aggression
that
we
need
to
quickly
fix
up,
but
definitely
thanks
to
Nicola
who
jumped
on
that
and
quickly
turned
that
around.
Otherwise
we're
still
waiting
to
see
if
any
of
the
talks
got
accepted,
for
no
coffee,
you
or
no
question
or
active
list
so
Jeremiah
and
the
next
one
on
the
list
is
the
streams
initiative.
C
Yeah
so
I've
had
some
time
to
dedicate
to
this
and
so
made
a
decent
progress.
I
will
link
it
I
posted
into
their
progress,
update
and
finally,
so
there's
automated
tests
in
this
row
now
now
and
there's
a
bunch
more
helpers
that
make
every
composing
everything
nicer
and
those
are
pretty
minimal
code
wise,
but
certainly
help
the
end
and
the
user
experience.
A
A
B
B
There's
you
know
some
stuff
that
throws
that
that
creates
other
possibilities
that
that
we
can't
yet
talked
about,
but
hopefully
soon
and
I,
don't
really
have
anything
to
report
other
than
that,
like
you
know,
moving
it
very
slowly
forward,
but
it
has
not.
It
has
not
stalled,
but
I
don't
have
any
meaningful
progress
to
report
on
this
week.