►
Description
To learn more about critical open source JavaScript projects like Appium, Dojo, jQuery, Node.js, and webpack, and 27 more checkout The OpenJS Foundation: https://openjsf.org/
A
There
we
go
great,
all
right
looks
like
we
are
live
thanks,
everyone
for
joining
another
episode
of
the
open,
JS
foundation's
cross
project
council
meeting
today's
the
last
day
of
January
in
the
year,
2023
I
will
say
hi
on
the
Stream
and
we'll
get
things
started.
Do
we
have
any
announcements.
B
A
B
Want
to
I
know,
I,
know
they're
rolling
in
and
we've
got
a
great
program
committee,
so
great
in
fact
that
they
created
their
own
video
to
promote
the
event.
So
if
you've
not
seen
it
check
it
out
on
our
Twitter
handle,
it's
amazing
there's
some
cameos
Joseppi's
cameo
Kylie's
in
there
and
Abby
so
yeah.
So
it's
pretty
fun
cool.
A
Yeah
this
this
year
is
flying
by
already
cool,
that's
exciting,
any
any
other
announcements.
A
No
okay,
good
anything,
the
the
anything
on
the
board
meeting
or
anything
like
that
was
that
recently,
is
that
last
week,.
A
Yeah
all
right
cool
well
with
that
we'll
just
kind
of
jump
into
the
the
agenda.
The
first
one
on
on
the
list
here
is
issue
982
and
for
folks
I
think
everybody's
got
the
link,
but
I'll
drop
the
the
minutes
here
in
the
chat.
This
first
issue
is
determine
you
know
a
review
process.
We've
talked
about
this
a
little
bit.
Luke
started
a
doc.
A
We've
got
some
questions
in
here
and
and
some
comments
so
I
think
that's.
This
is
moving
forward.
A
I,
don't
know
if
we
want
to
talk
about
this
at
all
or
just
keep
it
in
the
dock,
but
I
think
the
expectation
is
we'll
flush,
something
out
here
and
then
hopefully
send
something
out.
In
a
few
weeks.
A
Cool
all
right
good!
Well,
we
will
keep
that
going,
but
for
everyone
wants
to
participate,
take
a
look
at
the
issue
and
help
us
flesh
that
out.
C
Actually,
if
I
may
Sean,
since
you
would
be
on
the
receiving
end
of
something
like
this,
like
your
input
would
be
great
to
hear.
C
The
idea
was
to
do
a
survey
of
the
different
projects
and
and
the
foundation
and
sort
of
like
send
questions
to
the
maintainers
to
better
assess
sort
of
like
how
the
foundation
can
can
can
well
but
understand
what
kind
of
relationship
we
want
to
build.
Essentially
and
so
you're
muted.
C
A
And
I
I
have,
if
I
pasted
them
in
the
chat,
if
that's
easier
to
you
and.
A
C
It's
great
to
have,
you
know,
broader
inputs
and
when
you,
when
you
start
asking
questions,
it's
good
to
ask
the
questions
a
number
of
times,
so
you
can
sort
of
like
refine
the
questions
as
you
go.
Yes,.
C
That
we
sort
of,
like
you
know,
do
this
within
a
smaller
circle
of
people.
I
just
jumped
on
the
occasion
to
put
you
on
the
spot.
That's.
D
D
How
heavy
are
you
with
the
services
you
receive
from
the
foundation?
I?
Think
that's
a
good
question.
I
think
most
people
might
be
like
well,
I,
guess
it
depends
on
the
project
right.
Some
might
be
like
what
services
are
you
talking
about
and
that'll
be
helpful
for
us
if
they
say
that
how
responsive
do
you
find
the
foundation
to
the
concerns
of
your
project?
D
I
think
maybe
one
question
that
isn't
here
is
like.
Do
you
know
like
how
to
reach
us
like
do
you
know
the
right
communication
channels,
yeah
I?
Think
probably,
if
you
ask
all
the
projects
that
they
might
not
know,
that
answer,
especially
if
like
maintainers,
are
cycling
in
and
out.
So
maybe
that's
one
question
you
should
add
like
do
you
know
how
to
reach
us?
Are
you
aware
there
are
communication
channels
that,
like
you'll,
get
a
fast
response
from.
A
Yeah
and
Luke's,
thank
you
Luke
for
for
capturing
some
of
these.
D
Give
a
good
understanding
the
resources
provided
by
the
foundation,
yeah
I!
Think
that's
good.
Do
you
know
how
to
access
the
resources
provided?
How
likely
are
you
I
mean
I
think
these
are
great
like
these
are
good
like
we
would
call
this
at
Microsoft
good
nsat
questions
right
for,
like
you
know,
typical
satisfaction,
so
I
think
this
is.
This
is
cool.
D
C
A
D
D
D
C
A
Yes,
now
we
want
to
know
we
want
to
know
cool
all
right
great.
Well,
that's
helpful,
oh
excellent.
So
the
next
item
on
the
list
here
is
issue
957.
What
are
these
repos
I
actually
closed
this
a
little
bit
earlier
today,
because
we
had
talked
about
it
last
time.
I
left
it
open
to
put
a
note
in
there
and
I
did
I.
Think
that's
fair.
Now
the
repos
are
a
little
bit
better.
We
archive
some.
We
have
better
descriptions
and
so
I
think
this
issue
is
pretty
good.
A
The
next
one
on
the
list
is
funds
for
project
driven
initiatives
and
I
think
that
Claudio
opened
a
PR
for
this
one,
which
is
nope.
That's
the
commit
I
thought
I.
Had
it
open
here
somewhere.
C
A
C
A
Perfect,
thank
you.
So
there
is
some
copy
there
already.
If
folks
want
to
take
a
look
at
it
and
we
can
kind
of
move
this
forward.
I
know
that
in
this
PR
there
have
been
a
bunch
of
comments
already
Toby
and
and
Mateo.
C
A
C
Think
it's
moving
forward
well,
like
I,
think
the
only
yeah
I
think,
like
sort
of
the
only
thing
that's
really
left
to
do
is
kind
of
format.
The
thing
a
little
bit
more
to
have
like
more
body
and
less
of
an
FAQ
yeah.
You
know
just
and
I
think
then
we
pretty
pretty
much
good
to
to
ship.
This.
A
Yeah
I
don't
know
because
I
think
I
think
it's
meant
to
be
not
super
detailed
in
the
body
right,
we're
kind
of
leaving
it
a
little
bit
open.
C
Oh
yeah,
yeah
no
I
mean
that
was
just
yeah.
Let's,
let's
not
have
like
a
discussion
about
likes.
You
know
the
finding.
My
point
was
this
is
like
this
has
moved
forward.
Quite
a
bit,
I
think
it's
it's
towards
good
enough.
Yeah.
A
Well,
I
am
gonna,
put
my
thumb
on
it.
Awesome
so,
and
does
this
yep
closes
9
53,
so
once
we
get
that
going,
that'll
be
great
and
then
you
know
we
can
work
on
that
further.
If
we
decide
to
later
on
cool
where's.
My
agenda
great
so
next
up
is
add
patching
scripts
for
the
COC
modifications,
and
this
is
the
thing
that
I
dropped
into
the
slack
earlier.
A
A
This
is
972.
yagiza's
done
a
ton
of
great
work
on
this.
There's
been
you
know,
commentary
and
and
comments
addressed,
I
believe
so
I.
You
know
oh
and
some
there's
some
stuff
from
not
that
long
ago
too,
can.
C
E
Yeah,
so
so,
if
you've
merged
to
comment
of
the
first
initial
part
of
it,
and
then
this
pull
request
just
adds
the
GitHub
workflow
Runners
that
That's
the
basis
of
the
patching
script.
The
only
thing
that
I
did
manually
was
that,
in
order
to
make
sure
that
we
have
the
current
version
of
the
code
of
conduct,
I
created
a
patch
file
from
the
old
one
and
the
red
ones
that
you
see
in
the
patch
file,
in
my
pull
request
is
the
actual.
E
A
And
for
more
context
for
Sean
and
others
who
maybe
don't
have
it,
you
know
the
idea
was
to
make
this
updating
the
code
of
conduct
easier,
even
though
it's
been
a
bit
of
a
hurdle
to
get
this
going.
But,
like
you
know,
when
we
update
to
a
patch
or
whatnot,
we
have
a
bit
of
templating
kind
of
around
it.
That's
open.js
specific,
and
so
we
want
it
to
be
sort
of
automatic.
We
can
update
it
and
then
this
hatch
runs
and
and
the
action
runs
and
it
works
out.
A
I
see
some
comments
from
Jordan's.
Does
it
look
like?
We've
got
a
little
bit
more
work
to
do
and
then.
E
Yeah,
so
there
was
a
miscommunication
I
guess
so.
I
did
I
I
didn't
over
engineer,
but
I
I
implemented
something
that's
much
more
complex
at
what
you
want.
He
asked
and
yeah
I
need
to
roll
back
a
couple
of
comments
and
release
any
version
of
the
GitHub
workflow
and
can
be
done
in
like
a
half
an
hour.
A
Okay,
great
great
awesome,
so
maybe
we'll
ping,
the
slack
Channel
again
when,
when
it's
ready
to
move
forward
and
we'll
kind
of
keep
this
this
progress
going,
we
have
another
open.
Pr,
that's
been
around
for
a
really
long
time
that
will
be
closed
once
we
get
this
stuff
in
place
and
that'll
be
great.
A
If
not,
the
next
item
on
the
list
is
the
pr
that
I'm
talking
about
that's
851.
That's
let
me
just
open
it
to
make
sure
I'm
correct
here,
the
one
that
Ben
had
opened
up
yeah
about
the
COC
back
in
March
of
last
year,
so
it'll
be
great
once
we
get
this
all
in
place
and
can
close
this
one
too
excellence
cool.
So
the
last
couple
on
the
list,
then
here
license
check,
support
and
tooling
I.
Imagine
this
is
still
kind
of
in
a
holding
pattern.
A
I
checked
this
morning
that
IBM
license
scanner
has
been
donated
to
oasp
it's
in
the
Cyclone
DX
org,
but
it
remains
private
at
the
moment.
I
think
they're
kind
of
updating
a
couple
of
files
or
something
before
they
make
it
public.
So.
A
Sometimes
I'm
slow,
so
cool
that'll
that'll
be
hopefully
available
soon
and
then
we'll
kind
of
coordinate
with
LF
and
and
see
what
we
need
to
do
to
move
stuff
like
this
forward
cool
and
then
last
one
is
issue
786
and
clarify
requirements
around
COC
violation,
Toby
I,
know,
you've
got
this
list
here.
A
I
think
the
expectation
is
that
once
we
get
some
of
the
other
code
of
conduct
stuff
in
place
and
some
of
the
other
stuff
updated
that
we
did
recently
that
we
would
kind
of
look
back
at
this
list
and
see
if
we
got
everything
done
and
what
else
maybe
has
come
up
since
then.
C
A
I
think
you
know
this,
this
does
kind
of,
and
this
is
the
last
issue
in
the
agenda,
but
it
does
sort
of
lead
into
you
know
the
conversations
that
we've
been
having
around
the
the
moderation
panel
and
and
how
many
people
are
on
it
and
voting
and
all.
A
Yeah
so
I
mean
I,
guess
that's
something
we
haven't
talked
about,
but
the
last
working
session,
which
I
think
we
primarily
worked
on
the
first
chunk
of
work
that
yagis
had
been
working
on
in
terms
of
getting
the
the
template
in
place
for
the
code
of
conduct
and
and
pro,
and
we
had
to
do
that
work
before
we
got
the
patching
work
done
so
I
think
we
primarily
worked
on
that
yeah
yeah.
A
A
I'll
share
this.
C
I
mean
what
sort
of
happened
if
I
remember
correctly
in
that
PR,
as
it
turned
into
like
an
issue
where
we
started
discussing
sort
of
things
that
should
have
been
discussed
in
an
issue,
and
we
probably
should
sort
of
bring
that
back
and
have
a
conversation
about
it,
and
it
probably
should
be
in
in
sort
of
like
our
weekly
things.
Maybe
we
should
talk
about
it
now.
Actually,.
A
Have
about
20
minutes
until
Sarah
gets
back
and
we'll
go
to
a
private
session
for
the
board.
Slides
I
think
that
what
we're
trying
and
correct
me
if
I'm
wrong
anyone
here
on
the
call
I
think
that
we're
trying
what
we're
trying
to
balance
is
having
a
code
of
conducts
moderation
panel
for
openjs
and
the
cross
project
Council.
A
That
will
largely
be
for
escalations,
I
believe
and
we
we're
trying
to
not
have
it
be
too
big,
because
we've
had
an
issue
in
the
past,
where
we
had
too
many
people
and
we
had
an
urgent
issue
and
it
was
very
difficult
to
get
like
any
consensus
and
get
a
meeting
and
it
was
really
challenging
versus
having
a
smaller
panel
and
I.
Think
the
issue
with
the
smaller
panel
is
that
if
you
limit
it,
then
you
might
end
up
voting
and
we
are
trying
to
avoid
voting.
A
You
know
so
I
think
the
ideal
number
that
we
had
talked
about
in
some
of
the
previous
conversations
was
like
executive
director,
someone
from
like
a
marketing
committee
or
marketing
team.
Because
of
the
events.
Things
often
happen
at
events
and
then
three
other
people
from
the
CPC
or
Community
related
folks.
A
A
All
that
you
put
down
in
there
about
creating
a
diverse
panel
and
I
think
that's
a
fantastic
goal
that
we
should
keep
in
mind,
but
I
I
I'm,
trying
to
figure
out
the
other
two
things
that
how
we
you
know,
remedy
that,
and
somebody
else
commented
too
about
having
people
on
the
escalation
team.
This
panel,
that
are
not
part
of
the
projects
that
that
would
be
an
issue
and
and
some
regard,
there's
a
lot
of
comments
here.
C
Yeah,
we
should
probably
do
some
kind
of
I
mean
come
through
this
pull
request
and
figure
out
like
what
are
the
different
things
that
we
need
to
make
decisions
about,
because,
for
example,
on
on
the
size
of
and
there's
also
another
open
issue
where
some
people
have
like
raised
their
hands
to
sort
of
volunteer
for
this
yeah
and
like
on
the
size,
for
example,
I
think
some
folks
that
have
a
lot
of
experience
in
dealing
with
this
kind
of
stuff
actually
had
like
things
to
say
about
stuff
what
size
the
panel
like
that
should
have
and
I
have
like
little
to
no
experience
in
that
field
and
I.
B
And
we
have
someone
at
the
Linux
Foundation,
whose
role
it
is
to
sort
of
help
facilitate
some
of
these
code
of
conduct
panels
and
I
thought
it
might
be
nice
to
have
her
come
to
as
a
guest
for
a
working
session.
We
actually
as
a
foundation.
Don't
have
a
lot
of
experience
because
we
don't
have
a
lot
of
code
of
conduct
violations.
It's
been,
you
know
very
rare
So
hearing
from
others.
You
know
it's
probably
be
a
wise
thing
to
do.
B
A
F
A
To
do
that,
so
that's
maybe
something
to
shoot
for
which
would
be
next
next
Tuesday
at
2
p.m,
eastern
time
and
then.
Secondly,
if
we
want
to
take,
you
know
the
next
19
minutes
and
talk
about
that
one
particular
challenge
or
do
we
think
we
need
to
wait
and
speak
with
someone
who
has
more
experience
and
when
I
say
one
particular
challenge
I'm
talking
about
the
size
of
the
group
and
how
we
manage
filling
that
or
if
it
exceeds
the
limit
or
what
we
do.
A
A
Oh
you're,
you're,
muted
attorney.
F
I
totally
disagree
with
that
there's
like
very
little
day-to-day
moderation.
A
lot
of
the
a
lot
of
the
actions
that
happen
are
actually
just
a
moderator,
doing
something
unlocking
it,
but
that
that
is
separate
from
like
COC
process,
yeah
and
so
like
when
a
COC
violation
or
something
in
that
vein
right
like
dispute
or
something
like
that
comes
up.
F
F
You
just
delete
it
right,
like
everyone
is
empowered
to
just
take
that
action
and
I.
Think
specifically
how
node
codifies
that
is
like.
If
this
is
a
person,
that's
not
a
member
and
then
like
you,
go
and
do
reasonable,
reasonable
search
like
you
go
through
their
GitHub
profile,
many
times
where
we
went
through
someone's
profile.
F
It's
like
they've
been
making
the
same
comment
on
15
different
major
repos
like
this
is
very
clearly
spam,
or
it's
just
like
a
nonsense
comment
with
a
default
like
Avatar
like
that
that
stuff
is
day
to
day,
but
the
the
actual
like
hard
work
was.
Maybe
I
mean
early
on.
It
was
once
every
three
months
and
it
got
to
the
point.
It
was
like
once
a
year,
yeah.
F
So
I
just
wanted
to
differentiate
that
yeah.
The
little
moderation
stuff
haven't
constantly
known
as
it
does
I
assume
in
like
every
big
project,
but
the
bigger
like
dispute
stuff
happens
much
less,
and
so
that's
where
that
model
comes
in
of
like.
A
Yeah
yeah
yeah,
and
so
how
does
the
node
project
handle
that
if
there's
a
sizable
number
of
folks
I
mean
I,
think
there's
what
seven
to
ten
or
something?
If
there
is
a
code
of
conduct
report,
you
know
that
they
want
to
act
on
quickly.
Do
they
have
to
have
everybody
in
or.
F
Is
it
no
usually
with
that
stuff,
usually
like
not
one
person
but
like
getting
like
three
four,
because
there
was
like
time
since
we
had
someone
in
Tokyo,
we
had
seven
I
think
we
had
two
people
in
Tokyo
we
had
someone
like
middle
middle
of
Europe
right
and
so
there's
like
times
on
overlap
and
when
something's
there's
there's
like
three
types
of
violations.
F
Right,
there's
the
very
obvious
ones
right
where,
like
I,
don't
know,
your
thing
gets
posted
a
fortune
and
it's
a
bunch
of
eggplant
emojis
right
like
that's,
that's
one,
there's
four
types,
that's
one!
That's
one!
There's
like
a
very
obvious,
egregious
you
know,
violation,
that's
like
cool.
We
can
act
on
this.
The
hard
one
is
the
middle
ground
where
it's
like.
F
This
is
like.
We
need
to
like
talk
about
this
and
figure
out
like.
Is
this
actually
a
violation?
Basically
you're
like
legislating
it
and
like
you're,
you're,
doing
policy
policy
building
in
that
moment,
and
then
the
the
other
one
is
like
someone
reported
this.
F
It's
not,
but
this
isn't
really
a
thing
like
this
is
just
someone
interacting:
it's
not
actually
like
either
it's
a
bad
faith
report
or
it's
like
not
it's
someone
misunderstanding
and
so
that
that
that
third
one
there
is
the
hard
one
and
that's
the
one
where
it'll
be
like
challenging
and
you
you'll
want
to
involve
more
people
but,
like
the
the
scale
of
those
is
like
you
know,
the
4chan
stuff
is
obviously
like
you
turn
on
org
security,
and
you
lock
it
down
you
the
the
second
one,
which
is
like
an
obvious
violation.
F
One
person
can
generally
handle
that,
but
like
take
an
action,
quick
and
that's
when
it's
easy
to
take
an
action
and
then
the
second
one
or
the
third
one,
sorry
where
it's
like
a
gray
area
or
harder
is
that's
when
you
kind
of
have
to
involve
multiple
people
and
like
maybe
for
the
the
one
prior
to
that
where
it's
like.
You
know
obvious,
you
involve
two
people
right
like
there's
some
some
level
of
checking
with
other
people
who
are
online
or
something
like
that.
Yeah.
C
Yeah
I
mean
essentially
so
what
you're
saying
turning
you
mean.
You
said
many
things,
but
one
of
the
things
that
starts
here,
no,
no
I'm,
not
that
was
not
that
was
so
cool.
That
was
a
good
thing.
C
That
was
not
a
bad
thing,
but
one
of
the
things
that
strikes
me
is
you
can
I
mean
the
fact
that
you
can
be
like
12
people
in
the
group
is
unrelated
to
how
many
people
can
be
empowered
to
make
a
decision
right,
and
so
you
want
as
many
as
many
people
as
needed
to
sort
of
like
cover
the
time
zones
I'm,
assuming
it's
what
you're
suggesting.
C
F
We
did,
we
didn't,
have
perfect
time
zone
coverage
and
honestly,
like
I'm
up
till
5am
most
days
so
like
I
ended
up
covering
stuff
at
1am.
Sometimes
right,
it's
just
like
time.
Zone
coverage
is,
is
weird
and
hard.
I
I
would
say
like
20
people
is
probably
too
many.
15
is
probably
a
good
like
very
healthy
amount
and
12
7
to
12
is
like
you're
you're,
green,
you're,
perfect
and
then,
like
you
need
more
than
five
I
think
it
is
my
you
need
at
least
mine
like
five
is
the
mid.
F
That
one
I
I
mean
the
thing
I
am
always
cautious
about
with
this
is
this
is
like
effectively
corporate
open
source
to
some
extent
right,
whether
whether
or
not
it's
under
a
company
like
the
members
who
are
participating
are
all
corporate
to
some
extent
and
they're
disambiguating
from
like
corporate
Allegiance
right
and
like
that
can
show
up
accidentally
or
in
some
ways
right,
like
I
still
like
I,
still
have
a
lot
of
friends
at
Microsoft,
right
and
so
like
being
able
to
like
have
other
people
particip
like
have
their
opinions
or
the
opposite
of
like
well.
F
This
group
is
the
same
same
Dynamics
in
like
the
CPC
and
TSC
right.
It's
like
you
need
to
remove
that
political
structure
and
like
bad
blood
that
can
happen
there
and
so
I.
Think
three
three
is
scary.
That's
that
and
also
like
cool.
What,
if
you
know,
two
of
them
are
at
the
same
conference
right,
because
there's
a
very
high
likelihood
that
they're
going
to
do
that.
The
third
person
has
nothing
to
do
they.
They
can't
actually
go
reach
out
to
someone
right.
So
I
like
having
the
you
know
extra
buffering
there
quite.
A
A
bit
one
and
what
we're
looking
at
too
is
three
plus
two.
You
know
so
five
at
a
minimum,
which
I
think
is,
is
good.
Oh.
F
G
So,
like
you
know,
if
we're
talking
three
or
four
here
I,
do
like
the
comment
from
I.
Think
it's
Benjamin
in
that,
like
the
the
self
moderate
moderate,
you
know
the
moderate
self-notomy
there's
there
needs
to
be
no
objections
because
it's
a
very
high
bar
and
then
it's
re-certified
once
a
year.
That
approach
has
worked
pretty
well,
I.
G
Think
for
the
the
node
project,
like
I,
said:
we've
never
had
like
100
people
nominate,
so
it's
been
a
reasonable
number
and,
along
with
you,
know,
Tierney's
point
that
it's
not
a
decision
by
that
whole
group,
it's
usually
a
decision
by
some
subset
who's
available
right.
So
if
you
factor
that
in
then
I
you
know
until
we
have
too
many
volunteers
and
even
that
would
probably
be
a
good
problem.
I
don't
know
if
it's
worth
like
artificially
limiting
it
and
having
to
vote
to
someone
to
Toby's
point
right.
A
Yeah
well,
I
think
I
think
having
something
in
place
that
that
makes
it
clear
that
while
we
may
have
eight
members
on
the
team
or
whatever
that
you
know,
the
minimum
number
is
X
and
when
something
happens,
there's
immediately
an
email
that
goes
out.
People
need
to
raise
their
hand
that
they
are
going
to
make
time
and
be
available
to
work
on
this,
and
then
we
can
work
with
a
smaller
group
which
I
think
I.
F
I
would
also
recommend
do
not
do
email,
email
is
like
too
slow
and
it's
too
easy
to
miss
I
I
would
recommend
having
a
slack
channel
for
it.
Like
we
already
have
a
slack.
That's
how
the
node
moderation
team
has
there
on
slack
org.
They
don't
even
have
a
team.
They
have
like
an
order
that
got
paid
for
by
slack
and
that
that
was
super
vital
in
like
there
there
were.
F
There
were
a
number
of
channels,
I
mean
there's
the
main
Channel
and
then
there's
like
a
logging
Channel,
just
where,
like
everyone,
when
they
did
something
right
like
when
random
person,
went
and
deleted
a
comment
right.
You
just
put
that
in
there
and
like
that
serves
as
a
log
I
would
not
recommend
maybe
reporting
as
much
as
the
moderation
team
did,
just
because
it's
it's
a
it's
a
long
drone
to
sit
there
and
listen
to
someone
list
that
they
deleted.
15
Bots
bought
comments
in
a
meeting
like
there's.
F
F
F
Yeah
I
would
definitely
recommend
having
a
logging
Channel,
that's
like
separate
just
for
logging
in
private,
of
course,
and
also
a
general
chat
for
them
to
to
talk
in
because,
like
sometimes
you
have
to
have
discussions
about
stuff.
Also,
sometimes
you
need
to
like
schedule
stuff
right,
and
so
it's
like
yeah.
It
was
useful.
Also.
We
did
originally
have
meetings
monthly.
F
Realistically,
those
we
kind
of
ended
up
not
needing
those
they
they
weren't
helpful
like
there
wasn't
anything
to
do
in
them,
so
they
it
like
happened
occasionally
when
we
had
something
to
talk
about,
but
that
was
like
once
every
six
months,
so,
okay.
A
Yeah
all
right,
that's
all
very
helpful
and
I
I
kind
of
like
this.
You
know
Direction,
because
then
we
can
think
about
Toby
what
you
had
suggested
and
trying
to
build
a
diverse
panel
and
stuff
Robin.
Do
you
have
any
thoughts
or
concerns
about
some
of
these
thoughts.
B
No
I
like
it
also,
you
know
if
you've
worked
on
a
you
know,
one
of
the
harder
code
of
conduct
challenges.
It's
also
very
time
consuming
too
so
I
think
it
helps
folks
sort
of
share
the
burden
a
little
bit
yeah.
A
100.,
okay,
so,
theoretically
we
have
about
eight
minutes
until
Sarah
gets
back.
What
do
we
want
to
do
for
next
working
session?
Is
that
something
we
want
to
hack
on
this
some
more
and
and
shape
some
language,
or
does
somebody
want
to
take
a
stab
at
that
asynchronously
or
I?
Guess
that's
sort
of
two
questions:
what
do
we
want
to
do
with
the
next
working
session?
A
And
what
do
we
want
to
do
about
these
thoughts?
We've
been
talking
about
getting
them
formalized
Toby.
C
My
understanding
was,
you
had
suggested
that
we
would
do
something
if
Robin
was
able
to
get
the
person
in
the
foundation.
That's
working
on
that
stuff
in
the
next
session.
A
Thank
you
for
reminding
me
God
I
forgot
from
five
minutes
ago.
Yeah.
Do
we
want
to
do
we
want
to
do
that?
I
mean
there's,
certainly
more
that
we
could
talk
about
in
terms
of
just
general
code
of
conduct
and
moderation,
and
things
like
that.
What
do
you
think
Robin.
B
A
Let's
see
if
they're
available,
we
can
also
you
know.
Geez
has
been
doing
this
great
work
on
some
of
the
patching
stuff,
which
we
can
also
I.
Consider
a
part
of
that.
We
can
look
at
these
other.
You
know
the
the
checklist
that
Toby
has
from
that
other
issue.
We
can
so
generally
work
on
code
of
conducts
and
have
these
few
things
that
we
can
have
on
the
agenda.
C
Yeah
and
there's
like
a
last-
oh
sorry,
Robin
I
didn't
mean
to
to
you're
good
yeah.
There's
the
last
thing
that
I
think
we
sort
of
discussed
and
talked
about
a
few
times.
I,
don't
think
we
have
like
super
Clarity
around
it
around
the
code
of
conduct.
Stuff
is
the
the
panel
is
supposed
to
be
for
escalation,
but
it's
also
supposed
to
be
for
handling
the
project
for
a
number
of
other
projects
to
to
handle
those
right.
C
And
so
then
we
don't
have.
What
does
that
mean
if,
like
those
need
to
be
escalated
like
we
have
to
have
some
kind
of
like
clarity
as
to
whether
there
is
no
escalation
path,
but
for
those
that
don't
have
their
own
thing
or
whether,
like
there's
a
two-step
process?
And
if
so,
what
does
that
look
like?
C
Because
that's
also
something
while
we
don't
want
like
I
mean
we
want
Clarity
around
this,
so
we
don't
have
to
discuss
it
now,
but
I
think
it's
sort
of
like
a
pending
issue.
That
is
not
clearly
documented
anywhere
Michael.
G
C
Yeah
no
I
only
need
one
I
mean
like
clearly
I,
don't
want
to
be
handling
like
I
mean
I.
You
know,
I
haven't
put
my
hand
up
to
to
do
a
panel.
A
coat
of
panel
monitoring,
so
I
don't
want
everyone.
That's
in
the
CPC,
that's
sort
of
like
fall
in
the
category
of
like
you
know,
and
now
we're
handling
this
for
all
these
projects.
Right
so
I
mean
you
know
sure.
C
If,
like
you
know,
we
need
people
and
like
there
are
new
people
like
you
know,
I'd
consider
whether
I
could
like
actually
do
that
work,
but
like
I,
I'm,
absolutely
I
think
that
these
should
be
the
same
group
I'm
just
saying
if
they
are
in
the
same
group,
then
like
it's
no
longer
escalate
like
we
have.
We
need
to
clarify
whether
they're
escalation
or
not
so
yeah
I'm
I'm
not
trying
to
roll
back
what
I
suggested
I'm
trying
to
say
now
that
we
agree
that
this
is
what
we
have
to
do.
G
A
Is
going
great,
so
I'm
I'm
gonna,
maybe
just
try
to
take
a
couple
of
quick
notes
on
what
we've
been
talking
about
in
prep
for
next
week's
working
session
and
we'll
share,
maybe
in
slack
or
something
to
see
if
I
missed
anything,
but
we
can
switch
to
the
board
slides
now,
if
we'd
like
I,
mean
objection
to
that
folks.