►
A
And
we
should
be
live
now.
Awesome.
Let
me
just
make
sure
it's
actually
I've
cut
off
cool
yep.
We're
live
so
everyone
and
welcome
today's
committee
meeting.
Let's
go
down
and
do
just
attendance,
real,
quick,
so
I'll
do
it
by
my
bar
people
on
zoom
I'm
too
nice
siren
I'm,
showing
up
as
the
nodejs
foundation.
I'm
co-chair
of
the
community
committee
and
I
do
general
work
and
the
new
project.
It's
specifically
around
a
community
and
evangelism
stuff,
Jam
you're
up
next.
A
A
H
H
A
Awesome
I
think
that's
everyone
yeah,
it
did
as
people
talk
it
reorders
it
which
is
confusing
okay.
So
we've
got
a
rather
lengthy
agenda
today.
The
members
just
here's
the
link
again,
no
reason.
There's
the
link.
It's
calm,
calm
issue,
two
hundred
and
so
the
first
item
on
the
agenda
is
the
strategic
initiatives
document
I
I
submitted
this.
You
know
post
discussion,
you
know,
after
the
discussion
we
had
in
the
last
meeting
around
this
there's
been
a
significant
amount
of
conversation
on
it.
A
I
went
through
and
tried
to
do
all
the
updates
I
could
today
you
know
the
remaining
updates
that
needed
to
be
taken.
Care
of
they
were
actionable.
It
seems
like
most
of
the
things
are
either
non-blocking
or
don't
have
anything
that
actually
that
can
be
taken
released,
have
been
discussed
to
not
have
action
to
be
taken.
A
G
So
absolutely
that
I'd
like
to
point
out
as
a
point
of
process
and
something
that
we
might
want
to
add
to
our
agenda
that
relates
to
the
strategic
initiatives.
So
we've
typically
had
the
check-in
of
the
calm,
calm
initiatives
before
agenda
items,
and
we
may
just
want
to
put
the
strategic
initiatives
that
we
want
to
have
check-ins
before
them.
Yeah.
A
So
you're
actually
right
totally
yeah.
So
that's
actually
probably
a
good
thing.
I
think
all
of
the
strategic
initiatives
should
people
that
have
a
check-in
I,
don't
think,
that's
necessarily
something
they
should
like,
and
no
none
should
be
prioritized
over
others.
At
least
that's
that's
my
feeling
on
that.
G
I
think
we
should
keep
the
the
topic
that
you
kicked
off
rather
than
coming
back
that
but
I
wanted.
You
know
only
we
need
to
come
back
to
theirs,
and
you
know
to
that
point.
You
know
that's
one
of
the
barometers
that
I've
been
using
as
we
you
know
introduced
it's.
This
concept
of
of
strategic
initiatives
in
the
calm
calm
is
like.
Should
we
be
hearing
about
this
initiative?
G
G
You
know,
can
we
consider
the
GG
Commission
and
you
know
I
had
the
you
know
the
question
I
believe
it
was
around
office
hours
that
we
discussed
that
we
discuss
in
the
thread
that
I
thought
was
a
good
example
of
you
know
a
strategic
initiative
on
the
edge
of
you
know
an
acceptable
level
of
you
know:
engagement
in
the
calm,
calm,
yeah!
No,
not
that
it
shouldn't
be.
You
know
not.
That
is
important,
not
security,
preparedness.
The
long
term.
A
Which
is
just
you
know
non
this
every
meeting
has
to
have
a
plus
one
or
minus
one,
but
I
think
that
we
should
probably
the
discussion
in
the
issue
rather
than
in
the
meeting.
Just
I
think
that's
something
we
could
go
on
about
for
a
while.
Does
anyone
else?
Would
anyone
like
to
disagree
on
that
or
is
there
anything
any
specific
points
around
that
that
people
would
like
to
bring
up
well.
G
Trying
to
unraised
my
hand
and
unmute
all
the
same
time.
Sorry
right
so
you
know,
in
terms
of
you
know,
having
strategic
initiatives.
I
think
you
know
we
have
to
consider
not
only
what
we're
doing,
but
this
is.
You
know
key
wayfinding
for
folks
that
are,
you
know,
getting
to
know
the
community
committee
so
having
a
lot
of
aspirational
strategic
initiatives.
G
I
think
it's
going
to
you
know
actually
do
folks
a
disservice,
because
you
know
a
lot
of
folks
are
are
going
to
come
first
and
learn
and
listen
and
before
they
they
kickoff
actual
projects.
So
yeah
I'm
super
excited
about
us
having
this
strategic
initiatives
document,
but
you
know
my
only
suggestion
is.
Is
this?
Let's
keep
it,
you
know,
keep
it
real
as
we're
you
know,
building
is
out
and
the
more
we
can
have
various
groups
that
are
participating
and
engaging
through
through
these
meetings.
F
Point
if
we're
talking
about
aspirational
versus
like
active
initiatives,
is
there
a
way
that
we're
delineating
that
so
that
people
do
know
it's
not
that
it's
just
I,
don't
want
to
say
noise,
but,
like
you
know,
we
don't
want
to
spend
a
lot
of
energy
having
to
respond
to
issues
where
people
are
trying
to
find
what's
going
on
and
the
reason
they
can't
find
what's
going
on
is
because
it
was
something
documented
as
an
initiative.
But
is
it
necessarily
active.
A
Yeah
yeah
I
agree,
and
actually
you
know
part
of
the
reason
that
I
wanted
to
push
this
document.
I
do
in
a
time
check
here,
because
we've
already
got
through
like
a
festival,
meeting
and
one
issue.
So
you
know
one
of
the
reasons
I
started
trying
to
work
on
this
and
wanted
to
work
on.
This
was
because
there's
some
things
that
we
should
do
more
heavy
check-ins
on
and
we
need
to
start
kind
of
auditing
some
of
that
stuff.
A
A
few
of
a
few
of
the
initiatives
listed,
and
so
you
know
making
sure
we
have
all
that
document
and
stuff.
It
really
does
help
us
go
through
in
and
track
each
of
those
things
so
yeah
that
was
kind
of
one
of
my
intense
around
this
was
to
have
that
direct.
That
kind
of
liner
reporting
and
that
champion
so
I'm
gonna
suggest
we
table
for
the
discussion.
If
there
is
other
things
that
people
would
like
to
add-
or
you
know
for
the
discussions
we'd
like
to
have
on
this-
please
put
them
in
the
PR.
A
G
I've
spoken
a
lot
so
I'll
try
to
be
brief.
Please
feel
free
to
cut
me
off
if
I
go
along,
so
working
group
70
goodness
this
came
out
before
strategic
initiatives
that
MD
as
part
of
a
thread
around
the
user
feedback
group,
and
we
began
to
get
into
the
discussion
of
of
Kenneth
Amy
even
chartered
under
the
community
committee.
G
So
I
you
know
set
out
to
create
this
working
groups
document
it's
based
on
the
the
TSC
document,
which
has
a
lot
of
of
legacy
cruft
into
it
well
in
well
back
into
IO
j/s,
including
how
you
template
and
create
a
subsequent
working
group.
So
you
know
today
we
have
the
one
working
group,
which
is
the
evangelism
working
group
under
the
the
community
committee.
I
think
that's
been
ratified
at
this
point,
turning
right
finalized
all
the
this
up
there.
G
So
you
know
the
evangelism
working
group
was
the
archetype
and
the
prototype
for
the
user
feedback
initiative.
So
you
know,
as
I
was
trying
to
set
up
the
user
feedback
initiative.
I
refer
back
to
the
evangelism
working
group.
So
in
you
know,
setting
up
this
document
around
working
groups,
I
tried
as
much
as
possible
to
capture
and
bring
that
context
of
understanding
of
the
events
as
a
working
group
to
that
working
group.
A
A
Kind
of
the
feedback
I
was
trying
to
share
his,
or
is
that
there's
so
much
boilerplate
and
in
context
that
doesn't
necessarily
even
apply
to
the
the
compound.
It's
really
about
technical
things
where
you
know
part
of
basically
one
of
our
tag
lines
is,
you
know.
Code
is
not
equal
to
a
contribution,
so
they
paraphrase
paraphrasing
that.
But
you
know
there's
a
lot
of
context
in
here
that
can
just
be
stripped
out
and
we
can
kind
of
once
that
stripped.
A
We
could
iterate
it
from
there,
but
there's
a
lot
of
things
that
just
don't
strictly
apply
to
the
work
community
committee,
and
so
that
was
my
main
concern
in
it.
But
honestly,
like
just
stripping
any
kind
of
boilerplate
in
context
out,
that's
not
needed
would
really
I
think
enable
us
to
go
forward
with
this
and
drive
kind
of
better
working
groups.
B
A
The
car
and
better
buy
better
I
mean
working
groups
that
are
tailored
to
the
cost
community
rather
than
tailored
to
the
TSC.
Not
necessarily
that's
working
great
so
for
the
community
committee
are
better
one
sort
of
the
PSE
but
yeah.
So
that's
that's
generally,
where
I
was
trying
to
what
I
was
trying
to
get
at.
Is
that
there's
a
lot
of
stuff?
That's
not
really.
G
Sorry
and
just
just
to
respond
to
that,
while
that's
true
Tierney,
you
know,
as
someone
who
is
you
know,
attempting
to
create
things
under
the
auspices
of
the
the
community
committee.
There's
also
precious
little
definition
that
we
have,
you
know
collectively
aligned
around.
So
there's
there's
also
an
opportunity
for
us
to
do
the
work
of
building
consensus
and
define
some
of
these
things
in
this
document
may
be.
G
That
out,
and
do
that
some
other
space
and
bring
that
back
in,
but
you
know
that
boilerplate
that
exists
to
help
you
know
create
basically
technical
working
groups
under
I,
Oh
Jess
is
really
useful
and
was
really
effective
in
establishing
the
initial
working
groups
that
we
had
and
I
have
Jess.
So
you
know
finding
the
the
forum
for
us
to
you
know
to
hammer
out
how
we
got
you
know,
define
working
groups
and
you
feel
comfortable
with
working
groups
creating
and
evolving.
I
I
think
we
we
have
to
spend
the
time
and
doing
that.
A
That's
effectively
exactly
what
I
was
trying
to
get
is
we
need
to
figure
out
how
it
works
for
us,
and
you
know,
have
that
forerunner
of
the
iOS
working
groups
and
car
know
just
working
groups
and
then
figure
out.
You
know
how
we
can
apply
that
work
based
off
what's
here
to
us,
but
we
need
to
make
sure
that
the
document
we
do
ratify
and
pull
in
is
applicable
directly
to
the
calm,
calm,
oh
yeah,
so
I
think
starting
an
issue
specifically
around
that
it
would
probably
be
a
good
way
to
have
the
discussion.
A
A
A
A
Realize
let
me
do
it
myself
as
I
switched
okay
cool,
so
our
next
agenda
item,
real
quick
here
or
not
real
quick,
is
current
expectations
turn
to
expectations,
responsibilities
from
the
enterprise
advisory
group
at
the
end.
This
is
this:
is
your
issue
again,
your
PR?
Would
you
be
able
to
I,
think
I,
know
I?
Think
the
right
thing?
Would
you
be
able
to
elaborate
on
that
I.
G
A
I
mean
I,
prefer
you
know
saying
that
its
issues,
the
comp
calm,
has
its
I,
don't
think
that's
entirely
accurate.
It's
just
something.
I
raised
something
that
I
like
to
share
just
to
make
sure
the
kumkum
is
aware
of
it,
because,
generally
it's
like
aware
of
the
enterprise
advisory
group,
because
discussions
had
been
had
elsewhere
and
not
necessarily
with
the
calm
calm.
Even
though
it's
under
the
compound
see
you
necessarily
what
it
was
getting.
A
G
So
this
is
a
an
initiative.
James
Snell
came
to
me,
my
goodness.
It
was
I
think
before
just
interactive
and
just
like
I'd
like
to
begin
forming
a
group
of
you
know,
companies
that
can
provide
feedback
if
we're
gonna
make
a
a
change
to
you
know
the
codebase.
You
know
one
of
the
one
of
the
prevailing
concerns
at
the
time
was
the
decision
around
es
modules
and
the
potential
impact
on
the
platform
of
making
that
change.
G
It
is,
you
know,
a
slightly
different
flavor
from
the
user
feedback
that
is
been
a
bit
more
broadcast,
and
you
know
things
like
the
benchmarking
group
survey,
where
you
know
going
out
and
doing
broader
feedback.
So
you
know
I
thought,
there's
a
great
opportunity
to
to
engage
community
more
directly
and
see
how
that
fit
in
the
user
feedback
initiative.
G
We
ran
an
initial
meeting
and
in
the
beginning
of
the
month
and
captured
the
notes
and
put
it
in
the
repo
and
then
I
basically
ran
out
of
time
to
go,
and
you
know
build
out
the
initial
burst
of
activity
for
setting
up
a
group
with
setting
up
the
contributing
MDE
code
of
conduct,
whatnot
fair
amount
of
work,
so
you
know
took
me
a
while
to
get
get
to
setting
up
all
of
the
infrastructure
during
that
time.
I
also
had
a
tourney
and
Michael
Dawson
much
books.
You
know
trying
to
ping
me
and
say:
hey.
F
F
I,
don't
think
that
you
I,
don't
think
you've,
ruffled
feathers,
I
think
it's
from
from
what
I've
read
through
the
issue
and
the
pull
requests.
It
just
sounds
like
people
are
confused
about
the
scope
of
the
advisory
group
versus
something
like
the
user
feedback
initiative.
Like
the
user
feedback
initiative,
we've
talked
through
and
it
generated
like
from
the
community
committee
itself
like
I,
know
that
you
and
Mike
stepped
in
and
have
been
doing
way
more
work
on
that
and
that's
awesome
and
driving
that
forward.
F
G
G
If
we,
you
know,
if
we,
you
know,
we've
already
done
a
lot
with
calm.
Calm
in
saying
you
know,
code
is
not
a
key
part
of
what
we
do.
Actually
everything
in
the
node
project,
in
terms
of
attribution
in
terms
of
you
know,
recognition
our
ability
collectively
to
recognize
action
and
and
and
attribute
on
it
is
based
on
github.
So
in
you.
G
F
Okay,
so
I
think
my
understanding
initially
was
that
the
enterprise
advisory
group
was
more
of
a
foundation
effort,
not
necessarily
executives
from
the
node
foundation,
but
like
thinking
about
what
the
foundation
encompasses,
which
is
includes
the
project.
I
just
didn't
understand,
you
were
wanting
to
start
the
enterprise
if
I,
because
it
didn't
start
there
so
you're
just
saying
that,
but
you
still
think
that,
like
its
heart
should
live
and
ownership
and
licensing
should
live
as
part
of
the
project.
F
G
G
There
are
corporate
members
within
the
you
know
the
foundation
who
happen
to
be
big
enterprises,
but
you
know
it
is
not.
You
know
the
the
presence
of
those
companies
that
are
you
know
also,
members
of
the
foundation
doesn't
preclude
and,
in
my
opinion,
should
not
preclude
their
participation
in
aspects
of
the
project,
whether
that's
in
the
calm,
calm
or
the
technical
steering
committee
sure.
F
G
G
To
my
point
you
know
about
you
know
this
being
in
github.
You
know
my
feedback
consistently.
The
the
feedback
that
has
been
given
to
me
has
consistently
been.
Basically,
you
need
to
create
an
issue
about
these
things
and
if
you
had
created
an
issue
about
these
things,
you
wouldn't
have
had
folks
expressing
so
much
concern.
My.
F
A
Of
what
I
think
Tracy
is
getting
at
is
that
even
though,
like
I,
don't
think
any
one
of
the
calm
calm
is
against
things
not
starting
at
github.
I
know
the
DOJ's
collection
didn't
get
started
in
github.
That
grew
very
naturally
from
in
person
discussions
and
then
you
know
expanded
into
github.
Much
like
the
advisor
group
seems
to
be
trying
to
do.
Part
of
that
is
III,
don't
think
anyone
outside
of
you
know
I
was
included
on
these
emails.
I
was
not
necessarily
engaged
with
them.
A
Deeply
I
think
I
might
respond
to
one
of
them,
and
there
was
a
lot
so
and
I
believe
Michael
Dawson
was
also
included.
I'm,
not
sure,
though,
so
you
know
I
think
surfacing
that
context
of
making
that
transparent
is
kind
of
what
people
are
trying
to
get
at
and
that
that
is
what
would
help
push
this
along
and
you
know
pushing
it
or
you
know,
trying
to
add
it
under
the
comm.
Come
I,
don't
think
again,
I,
don't
think
anyone
is
explicitly
opposed
to
that.
F
That's
what
Dan
is
trying
to
do
so
I
will
say
this.
So
I
was
invited
to
the
advisory
group.
Meeting
I
was
not
able
to
attend
I
I,
don't
I'm,
not
opposed
I.
Think
I
was
sorry.
I
was
just
trying
to
bring
context
to
this
pull
request
and
sort
of
I
think
why
people
are
uncomfortable
with
it,
not
that
they're
negative.
G
F
It
I
am
totally
I
think
that
it
is
an
appropriate
thing.
I
just
want
to
make
sure
that
the
people
who
are
in
the
advisory
group
know
what
they're
getting
into
it
by
it
being
a
repo
in
the
project
that
it
goes
under.
The
purview
of
the
community
committee
I
would
love
to
see
that
work
on
github
if
they
feel
comfortable
doing
so.
F
It's
more
work
if
the
majority
of
people
live
off
of
github,
just
like
user
feedback
initiative,
because
you
still
end
up
having
to
go
back
and
get
hub
and
document
that
stuff
right
update
on.
What's
going
on,
I'm
totally
fine
with
that,
I
think
that
that
stuff
needs
to
happen
in
order
for
people
to
understand
what
the
Advisory
Group
is
and
then
just
like
any
of
the
other
groups,
because
we
don't
have
a
lot
of
working
groups.
I,
don't
I!
F
F
So
I
would
just
like
to
see
that
activity
and
then
we,
you
know
point
to
it
and
say
right
that
we
that
this
should
be
a
thing.
I
think
that's
the
the
thing
that
I'm
thinking
I
just
want
to
make
sure
scope
wise
that
the
people
who
are
excited
and
active
with
the
advisory
group
are
fine
with
it
being
in
the
project,
not
that,
like
everything,
is
required
to
be
in
the
project
in
order
for
it
to
be
important
to
note
and
the
foundation.
Okay,.
F
G
You
know
part
of
what
I
expect
to
end
up
doing
with
user
feedback
is
experimenting
around
the
edges
of
dealing
with
humans
and
carrying
that
context
back
to
get
up
because
again,
I
feel
very
strongly
that,
in
order
for
us
to
collectively
align
around
things,
it
has
to
be
in
github
it's
in
some
capacity.
So
you
know
with
those
individuals
that
are
you
know,
enterprise,
organ
individuals.
G
You
know
I,
think
that
the
organizers
of
the
the
advisory
group
are
going
to
have
to
carry
data
by
proxy
back
to
github.
Are
we
comfortable
with
that
right,
yeah?
So
yeah?
We
said
that
you
know
those
individuals
may
not
be
on
github,
okay,
I'm
comfortable
with
the
fact
that
you
know
some
team
member
at
MasterCard
may
not
be
able
to
may
not
even
you
know
technically
be
able
to
log
in
to
github,
and
but
you
know,
it's
still
valuable
to
know
just
project
two
to
go
and
collaborate
with
those
individuals.
F
So
the
biggest
thing
for
me
is
scope
of
moderation
and
code
of
conduct
application
there.
So
then
it
would
be.
Logging
I
know
that
that's
probably
uncomfortable
so
because
this
is
sort
of
unprecedented.
If
we're
talking
about
actual
project
work
that,
like
just
majority
of
lis,
is
not
happening
on
feel
like
this
is
something
that
needs
to
be
discussed
in
the
admin
repo
and
not
in
community
committee,
because
this
has
ramifications
beyond
the
community
committee
would
definitely
affect
the
TSC.
F
We
would
probably
want
to
open
an
issue
out
this
to
talk
about
what
does
it
mean
when
we're
having
it's
great,
that
we
are
opening
and
I?
Think
I
I
do
worry.
A
little
bit
about
people
are
gonna
argue
that
it
just
needs
to
be
in
github,
and
that's
not
right
to
be
a
more
inclusive
project.
We
do
need
to
allow
for
people
to
communicate
in
places
that
are
just
github,
but
that
also
means
that
you
are
still
buying
into
participating
in
official
node
spaces,
where
the
code
of
conduct
and
moderation
applies.
F
If
your
existing
primarily
and
write
an
email
and
then
somebody
from
the
moderation
team,
I'm
not
saying
the
whole
moderation
team,
I,
don't
know
like
I,
don't
know
if
there
needs
to
be
some
sort
of
here's,
the
moderation
team,
if
you
need
to
access
them,
if
you're
feeling
uncomfortable
and
like
can't
talk
to
somebody
within
this
group,
I
just
don't
want
it
to
be
such
a
siloed
space.
That,
like
something
happens,
because
that
always
this
just
like
you
know,
Murphy's
Law,
and
then
they
don't
feel
like
they
have
an
outlet.
G
So
much
of
what
the
TSC
techno
steering
committee
is
working
on
is
technical,
and
thus
you
know
has
a
code
component
and
therefore
you
know
fits
neatly
into
you
know
the
github
model,
and
so,
if
we
go
looking
for
feedback
to
you
know
the
technical
steering
committee
we're
going
to
more
likely
than
not
get
it
sort
of
feedback.
Yeah.
D
One
thing
I
want
to
add
so
because
I
think
it's
important
if
this
group
it
wants
funding
for
anything,
they'll
want
to
go
to
someone,
and
so,
if
that's
not
calm
calm,
then
they
have
to
go
directly
to
the
board
right.
So
it's
something
important,
that's
kind
of
neglected
out
of
all
of
this
is
the
potential
that
they
might
want
funding
for
something-
and
maybe
that's
just
to
have
a
on
site
meeting
somewhere
something
to
that
effect
again.
So
that
would
be
a
reason
why
to
have
it
under
comm.
Come
this
group.
D
B
A
G
A
So
with
that
I'm
gonna,
we
should
table
this
and
move
on
to
the
next
few
agenda
items.
So
MPE
I
was
on
I.
It
doesn't
look
like
Diego
wasn't
able
to
get
on
the
meeting
today,
so
I'm
gonna
a
table
M
peeve
till
our
next
meeting,
because
he
was
the
champion
there
or
he's
not
not
necessarily
champion.
He
was
working
heavily
on
it,
so
I
believe
he'd
be
the
best
person
to
be
able
to
give
us
an
update,
so
item
on
our
agenda.
G
C
E
I've
got
an
update
on
that,
so
we've
got
a
couple
of
meetings
coming
up
one
on
the
second
one
of
the
nights,
there's
about
there's
about
four
people
that
are
currently
interested
in
those
meetings.
So
we're
gonna
get
instant
momentum
in
early
January.
It's
been
kind
of
hard
at
the
end
of
the
year,
but
I've
been
looking
over
the
internationalization
repo
that
was
in
the
nodejs
in
nodejs
and
kind
of
trying
to
reconcile
some
of
our
current
concerns
with
things
that
already
been
done.
E
There's
some
differences
there
between
the
previous
concerns
but
I
think
generally
I
just
want
to
get
like
an
MVP
repo
up
with
some
structural
documents
and
and
all
that
kind
of
stuff
and
pick
up
a
min
time
early
this
year,
and
hopefully
it
will
grow
into
something
that
maintains
regular
growth.
You
know,
maybe
eventually
a
working
group
or
something
awesome.
A
A
C
I
mean
I
think
this
is
definitely
like
a
very
this
is
this
has
already
been.
This
is
gonna,
be
a
very
lengthy
process
because
it
involves
just
a
lot
of
factors
because
it
is
the
official
website,
but
I
think
this
should
be
somehow
I,
don't
know
how
somehow
sort
of
persistently
connected
to
the
kumkum,
maybe
via
like
a
strategic
initiative.
I,
don't
know
also
to
the
TSC,
probably
like
I'm
assuming
they'll,
want
a
say
in
this.
Obviously
they
do
make
sense,
but
yeah
I
was
thinking
something
along
those
lines.
I
don't
really
know.
A
Update
on
what's
happened
previously
with
the
notice
redesign,
the
one
we
have
been
in
the
works
kind
of
behind
closed
doors
and
then
us
moving
forward
with
it,
and
you
know
closing
that
previous
chapter
and
kicked
off
a
new
one,
so
yeah
I
just
generally
outlined
the
things.
I
probably
probably
need
to
do,
and
that's
not
me
like
dictating
trying
to
dictate
what
we
do.
I
was
more
just
trying
to
give
an
assessment
of
the
pain
points
that
I've
had
and
that
I
also
had
those
pain
points
and
so
from
there.
A
You
know,
I
also
linked
a
blog
post
that
at
a
Miller
did
who
Miller
is
an
observer
I,
don't
think
he
was
able
to
make
it
because
holiday,
it's
a
blog
post.
Are
we
designing
nodejs,
where
you
did
a
very,
very
extensive
analysis
of
the
website
and
then
other
websites
to
do
a
lot
of
things
really
good
things
so
yeah?
He
put
a
lot
of
work
into
that.
I
wasn't
expecting
that
to
even
happen,
so
it
was
really
impressive
and
he
did
a
ton
of
really
good
work
so
yeah
generally.
A
This
is
just
something
that
you
know.
It's
gonna
as
Olivia
said:
gonna
take
a
lot
of
work.
You
know
in
terms
of
information
in
terms
of
structure
in
terms
of
actual
design
and
implementation,
and
you
know
us
landing
all
the
things
that
need
to
be
done
and
agreeing
upon
those
so
yeah.
This
probably
isn't
something.
That's
gonna
be
done.
You
know
this
week
or
next
week
or
next
month
or
even
the
month
after
that,
but
it's
gonna
be
something
that
we
are
working
toward.
A
Probably
is
a
project,
hopefully
so
yeah
definitely
want
assistance
from
anyone
who
is
willing
to
help
out
with
you
know,
content,
information,
architecture,
design
and
eventually,
implementation,
and
also
you
know,
if
there's
any
feedback
that
the
kumkum
has
on
how
we
could
do
this
appropriately
or
you
know
things
like
we
should
probably
get
together
with
ESC
to
discuss
how
this
works.
That's
something
we
should
probably
go
ahead
and
do,
and
actually
this
is
that's
continuing.
C
C
Also,
I,
don't
I,
don't
even
think
it's
like
that.
Weren't
enough
people
I
think,
was
a
lack
of
like
direction
and
like
organization,
because
they
never.
We
tried
so
many
times
to
really
just
put
something
up
there,
but
it
never
really
worked
because
we
didn't
have
a
framework
for
organizing.
It
is
I
think
the
main
blocker
slash
problem
that
we
have
at
this
point
and
we
really
should
tackle
the
first
first
yeah
I.
C
G
D
I
D
G
D
F
That
would
definitely
be
we've
got
we've
had
to
project
managers,
William
say
that
they,
like
desperately
want
to
help
with
things
within
the
project
people
by
their
profession.
So
that's
I
think
incredibly
helpful,
because
the
majority
of
us
played
project
managers
along
with
our
other
work,
but
yeah.
That's
a
good
idea,
and
also
yes,
yeah
I
mean,
as
that
especially
Olivia,
like
as
that
discussion
takes
root.
F
C
C
C
A
H
So
obviously,
like
I'm,
just
gonna
take
one
or
two
minutes
basically
dated
the
repo
I
renamed
it
to
mentorship
and
also
I
added
the
forms
and
the
styling
I
created
selling
us
stuff
like
that,
and
we
also
agreed
to
move
the
mentorship
program
to
note
or
not
agreed.
We
opened
an
issue
and
we're
waiting
like
for
some
time
for
people
to
agree
or
disagree
and
then
we're
gonna
transfer
the
ownership
to
note.
Basically,
that's
all
the
updates
awesome.
A
Great,
thank
you
very
much.
Yes,
it
actually
looks
like
since
I
looked
at
this
last
night,
there's
been
significant
movement
in
it,
which
is
great,
really
excited
to
see
people
engaging
with
this
yeah.
So,
okay,
I
think
I'm
gonna
cut
us
off
there
because
we're
almost
at
eye
so
does
anyone
else?
Have
anything
they'd
like
to
add
dan?
Can
you
give
a
you
know
a
four
or
five
minute
update
on
use
your
feedback.
You.
G
Only
feel
time,
absolutely
so
user
feedback
we
did
it
kind
of
we
completed
our
first
major
task
in
creating
a
survey
for
the
benchmarking
working
group,
so
worked
with
Greg
Wallace
to
get
the
the
benchmarking
survey
completed
that
was
completed
just
before
the
Christmas
holiday.
It
hasn't
been
fully
rolled
out.
Ira.
G
A
I
think
one
of
the
ways
you
can
do,
that
is
by
creating
an
issue
in
the
con
con
repo,
because
the
people
that
are
active
in
evangelism
that
I
know
of
do
check
into
the
even
if
it's
just
browsing
so
yeah.
That's
that's
the
way.
I
would
approach
I
a
screen
issue
in
the
calm,
calm
and
the
kumkum
members
can
go
and
support
you
and
you
know,
evangelism
embers
can
go
and
support
the
efforts
there
and
in
the
ways
that
are
most
appropriate
and
that
they
can
help
with
great.
A
Awesome,
okay,
and
with
that
I
think
we
can
close
out
the
meeting
for
today
and
we
have
a
few
agenda
items
to
carry
over
to
the
next
meeting.
I
will
go
through
and
you
the
CC
agenda
label,
to
make
sure
that
are
currently
carried
over,
but
otherwise
have
a
great
day.
Everyone-
and
we
will
see
you
later
bye
goodbye.