►
From YouTube: CPC Meeting
Description
The OpenJS Foundation is a member-supported non-profit organization that provides a neutral home for some of the most important project in the JavaScript ecosystem.
Learn more and join us at https://openjsf.org
B
Excellence.
Thank
you
for
that
welcome
everyone.
It
is
another
episode
of
the
cross
project
council's
open,
js
foundation,
cross
project
council
meeting
today
is
the
5th
of
may
the
505,
the
cinco
de
mayo.
Thank
you
all
for
joining
today
is
going
to
be
another.
B
Code
of
conduct
working
session,
working
on
processes
and
documentation
and
all
that
good
stuff
before
we
get
into
things,
are
there
any
announcements.
A
Yes,
we've
got
some
things
to
share
lots
of
things
happening
today
for
those
interested
in
getting
involved
immediately.
Following
this
meeting,
we
have
the
collab
planning
meeting,
and
so
that's
it.
At
1pm
eastern
we
have
a
lot
of
stuff
to
work
on.
We
have
summit
registrations
are
live,
there's
110
people
already
registered
for
the
collab
summit,
and
so
we're
really
excited
to
be
putting
together
that
the
the
program-
and
you
know
so,
come
please
and
chip
in
if
you
like.
We
also
have
our
standards
working
group
meeting
today.
A
That
is
immediately
following
the
summit
planning
meeting,
and
so
that's
at
2
p.m.
Eastern,
I
am
not
sure
if
that's
a
very
full
agenda,
so
maybe
short
but
hey
it's
a
good
group
of
people
to
hang
out
with
so
come
come,
say
hello
and
and
participate.
If
you
like,
then
on
wednesday,
we
have
wednesday
morning
and
pacific
and
afternoon
eastern
is
the
node
red
ama
and
with
nick
o'leary
and
cj
and
dave.
I
believe
so.
A
If
you
have
anything
you
ever
wanted
to
know
about
node
red,
you
can
ask
us
now
via
a
form
or
you
can
ask
us
on
youtube
or
twitter,
and
you
can
hang
out
and
chat
with
those
folks
on
wednesday
morning,
and
we
also
have
some
blog
posts
coming
up,
that
are
exciting
project
announcements,
but
I'm
not
going
to
link
any
of
those
details
other
than
stay
tuned
on
the
blog.
And
what
else
am
I
missing?.
B
C
B
Okay,
great
thank
you
jory
anything
else
before
we
get
into
things.
E
I
would
just
add
hey:
this
is
robin
if
you
all
could
also
register
for
the
conference
as
well.
I
know
sort
of
folks
are
wondering
and
we
did
reduce
the
pii
that
was
collected
on
that,
but
we
really
would
love
to
have
you
register.
It
helps
us
sell
sponsorships
and
just
so
all
of
our
presenters
know
how
many
folks
will
be
tuning
in.
B
E
B
Cool
all
right,
so
we
can
get
into
business
here,
as
I
had
shared
in
the
issue
and
now
in
the
google
doc
we're
thinking.
Maybe
we
do
five
minutes
on
a
voting
regular
member
updates,
as
we
were
a
little
stalled
there
in
terms
of
just
landing
on
a
tool,
letting
folks
make
sure
they
had
any
sort
of
candidate
statements
if
they
wanted
and
such
but
I'll.
Let
jori
jump
in
here
and
give
us
an
update.
A
Yeah
so,
as
you
all
know,
we
need
to
elect
two
voting
members
from
the
regular
membership
pool
and
we've
collected
three
nominees
at
this.
I
believe
three
nominees
at
this
exact
moment
in
time
where
we're
saying
that
the
nomination
and
period
should
close
end
of
day
today,
so
that
we
can
kick
off
that
that
actual
election
process.
A
I
would
love
for
us
to
move
forward
using
the
tool
oppa
vote,
which
I
can
administer
as
soon
you
know,
as
soon
as
the
nomination
period
is
closed,
so
first
thing
tomorrow
morning,
we
can
open
that
up.
I
would
love
y'alls
like
plus
one
on
that
approach
or
a
suggested,
any
suggestions
to
change
that
process,
but
yeah.
That's
the
tldr.
B
Great,
I
am
plus
one,
I
don't
know
if
anybody
has
any
objections
to
that
process.
G
Likewise,
I
I
do
have
a
question,
though
go
ahead,
toby,
oh,
what
voting
strategy
are
we
actually
settling
on?
G
Because
there
are
plenty,
even
an
open
vote,
and
so
I
think
it's
also
important
to
be
clear
about
that,
because
the
data
will
look
different
and
the
outcome
will
look
different,
depending
on
which
one
we
choose
and
it's
way
better
to
have
that
conversation
before
than
after.
H
A
I'm
going
to
go
pull
that
up
really
quick,
so
I
can
share
okay.
Here
we
go
and
with
some
oh
maybe
I
need
to
do
this
because
there's
an
attendee
that
needs
to
be
there.
We
go.
G
Frankly,
I
mean
having
done
that
in
the
past,
like
actually
reading
the
doc
and
figuring
out
which
one
we
should
pick
takes
a
bit
of
time.
I
don't
think
now
is
the
right
time
to
do
that
very
honestly,
and
I
don't
have
a
good
answer
or
would
suggest
it,
and
so
I
suggest
someone
takes
the
responsibility
of
like
reading
that
up
and
making
a
recommendation
to
the
group.
B
E
B
Yeah,
I'm
not
a
voting
process
expert,
so
I
hesitate
to
volunteer.
I
know
dory's
pretty
busy
as
well.
I'm
looking
at
the
issue
here.
B
A
G
F
G
A
Yes,
I
I
still
would
love
for
us
to
do
like
the
the
post-mortem
on
on
just
our
election
process.
You
know
and
how
to
make
this
I
mean.
Obviously
it's
our
first
one
that
we
really
we
did
so
we
can
sure
give
you
know
to
take
all
that.
A
You
know,
but
it'd
be
great
to
just
do
the
to
to
to
move
quickly
on
this.
So
we're
not
like
blocking
the
vote
on
like
a
a
presentation,
or
we
said
maybe.
B
All
right,
great
excellence-
and
that's
you
know
we
try
to
keep
that
short,
but
I'm
glad
that
we've
got
a
process
to
move
forward.
B
So
so
nominations
will
end
today
and
we'll
start
the
process
tomorrow.
Right,
that's
correct,
excellent,
all
right
cool
and
then
we
were
suggesting
a
15-minute
time
box
on
charter
language
as
the
next
agenda
item
and
then
the
remaining
time
on
focusing
on
the
issues
that
are
related
to
code
of
conduct
that
are
blocking
onboarding
thinking
that
that
is
kind
of
the
thing
that
we
should
focus
on
first
and
then
we
can
work
through
the
other
things
we
need
to
work
through
beyond
that.
B
That's
a
google
doc
there
that
has
the
a
place
to
start
fleshing
out
the
charter,
the
code
of
conduct
working
group
that
then
we
can
pr
into
the
cross
project
council.
B
I
think
that's
correct
me
if
I'm
wrong
michael,
but
I
think
that
you
kind
of
threw
some
stuff
in
here
is
the
top
part,
and
then
this
morning
I
tried
to
go
through
the
ideas
there
and
propose
an
alternate
or
something
that
we
can
refund
yeah,
as
we
were
talking
through.
F
B
Great
so
I'll
just
read
the
the
kind
of
short
paragraph,
and
then
there
are
the
bullet
points
of
responsibilities.
We
can
focus
on
the
paragraph
first.
The
purpose
of
the
code
of
conduct
working
group
is
to
let
me
update
it
is,
is
to
define
and
maintain
a
set
of
resources,
slash
processes
that
will
be
used
by
the
foundation
and
its
team
groups
and
can
be
reused
by
projects
when
implementing
their
code
of
conduct,
processes
and
enforcement.
B
We
want
to
say
more
or
less
or
what
do
people
think
about
that?
I
know
miles
you've
written
a
couple
of
these
before.
Do
you
have
any
thoughts.
B
So
this
paragraph
is
what
I
was
referring
to.
The
people
think
there
should
be
more
or
less
here.
This
is
merely
the
the
chartering
and
the
for
reference
folks.
This
is
the
working
group
stock
in
the
cross
project
council,
and
we
would
be
pr
language
into
this
establishing
a
code
of
conduct
working
group.
This
is
the
standards
working
groups
code
of
conduct,
I
mean
sorry
charter
and
I
was
sort
of
using
that
as
an
example
to
flesh
out
this
here.
D
Just
what
says
maintain
a
set
of
resources,
slash
processes
that
will
be
used
by
the
foundation
and
its
team's
groups.
I
would
that
that
sentence
is
just
like
a
bit
of
a
like,
seems
like
it's
running
on
a
bit
because
I'd
be
I'd,
maybe
say,
maintain,
maintain
a
set
of
resources
and
processes
that
will
be
used
by
the
foundation.
D
F
D
So
so
I
guess
kind
of
like
an
additional
thing
to
consider
with
this
like-
and
I
know
it's
something-
we've
gone
back
and
forth
on
is
like
the
code
of
conduct
is
one
of
those
things
that
we
will
be
setting
as
like
an
expectation
to
a
project.
So
I
think
that
it's
important
the
language
here
is
explicit
because
can
serve
as
a
basis.
E
A
Okay,
if
I
may
yeah,
so
I
think
that's
one
of
the
the
key
issues
right
now
that
are
is
actually
you
know
relating
to
the
things
we're
going
to
discuss
here
in
a
minute.
That's
that's
tripping
us
up
and
onboarding.
So
you
know,
we've
said
you
have
to
adopt
the
the
foundation
code
of
conduct
and
projects
are
like
okay.
How?
A
How
would
you
like
us
to
consume
this?
How
would
you
like
us
to
you
know,
point
back
to
it,
etc
and
to
that
end
there
they
need
more
detail.
They
need
that
explicit
implementation
guidance
and
this
group
should
theoretically
be
the
body
that
provides
it.
So
I
think
there
are
some
resources
that
will
very
clearly.
A
Be
optional
for
the
project
coc
teams
to
to
use
as
at
their
discretion,
but
then
there's
going
to
be
some
other
things
that
that
I
think
this
group
will
oversee
that
that
we
do
need.
You
know.
F
J
J
And
from
my
point
of
view,
it
looks
a
little
bit
too
much
be
honest.
I
would
try
to
like.
If,
for
smaller
projects,
these
might
be
problematic
for
biggest
project
is
kind
of
fine.
We
can
have
complex
processes
in
place
and
so
on,
but
for
a
project
which
has
of
one
or
two
individuals
contributing
it's,
and
we
have
a
fuel
like
that,
like
three,
five,
whatever
it's
not
feasible,
to
have
complex
processes
like
it
becomes
insurmountable
to
some
extent.
I
D
Think
this
is
an
interesting
challenge,
though
mateo,
because
my
understanding
is
that
the
foundation
wants
to
create
a
team,
joe
you're,
showing
messages
as
a
heads
up.
Oh
sorry,
thank
you.
D
The
like
the
the
intent
here
mateo,
I
think,
and
people
can
interrupt
me
from
wrong-
is
that
the
foundations
like
code
of
conduct,
panel
or
larger
body,
that's
foundation
wide
would
be
able
to
be.
You
know
the
people
facilitating
that
for
the
smaller
projects.
D
I
don't
know
if
this
working
group
would
be
the
people
who
are
who
are
responsible
for
that,
but
I
think
that's
important
to
keep
in
mind
while
we're
drafting
that,
or
at
least
be
honest.
A
I'm
not
sure
that
I
mean,
I
think
I
think
I
think
what
you're
pointing
out
matteo
is
that
there
are
a
lot
of
different
points
of
view
and
preferences
and
that
those
also
vary
by
the
size
of
the
of
the
project.
A
Yeah
and-
and
I
think
one
of
the
responsibilities
of
this
group
is
going
to
be
to
take
those
considerations,
you
know
very
seriously.
You
know
to
to
make
sure
that
new
policy,
as
it
pertains
to
the
code
of
conduct,
has
as
much
input
from
the
smaller
projects
as
it
does
from
larger
ones
and
and
sort
of,
like
that's
my
hashtag
two
cents.
D
F
Right
and
I
think
what
miles
just
said-
and
you
know
processor,
like
requirements
like
so
to
define
the
minimal
requirements
and
provide
resources
to
projects
to
help
them
implement
those
that
sounds
like
this.
You
know
we
haven't
just
agreed
where
the
line
is,
but
this
team
will
have
the
responsibility
to
define
that.
A
K
Guys
can
I
have
a
question:
please:
is
it
necessary
to
have
everything
inside
the
code
of
conduct?
I'm
asking
this
because
from
my
perspective
code
of
code,
it's
more
like
a
human
bases
relationship
how
to
to
deal
with
each
other
in
a
community
as
a
group,
but
not
necessary
as
a
process
on
how
to
do
the
work
itself.
K
So
is
it
necessary
to
have
everything
in
the
code
of
conduct
and
should
show
that
we
have
splitted
splitted
documents
for
that,
because
when
we
are
talking
about
human
relationship
and
those
kind
of
things
like
respect
and
each
other,
this
should
be
the
base
foundation
or
code
of
conduct.
But
each
product
each
project
has
their
own
process
and
I
believe
the
single
code
of
conduct
will
not
work
for
everyone.
A
So
sal,
I
think
you
know
thank
you
for
sharing
your
your
perspective.
I
think
it's
important
to
to
point
out
that
that
that
that
question
of
whether
there
will
be
a
single
code
of
conduct
or
not
for
all
projects
is
has
been
settled
for
quite
some
time,
and
I
would
not
recommend
that
we
revisit
slash
reopen
that
that
question
at
this
point,
because
there
are.
F
A
Yeah
no,
no,
I
I
just.
I
appreciate
your
your
input,
though,
and,
and
I
wanted
to
to
thank
you
for
it.
B
Yeah
just
to
be
clear,
too
we're
just
trying
to
establish
some
language
here
that
would
charter
the
working
group.
So
we
don't.
B
Yeah,
we
don't.
We
don't
need
to
have
all
of
the
things
listed
out
here,
but
just
some
guiding
principles
and
the
responsibilities
that
we
expect
here
of
the
group
itself,
not
of
the
code
of
conduct.
F
I
I
almost
wonder
if
we
can
just
drop
that
second
line
like
leave
it
as
the
first
leave
it
as
the
first
line,
and
then
you
know
you
had
fairly
good
coverage
for
what
we've
been
talking
about
already.
I
just
added
one
line
which
is
like
to
define
the
minimum
requirements
and
provide
you
know,
guidance
resources
to
help
them
implement
those,
because
that's
specifically
what
jory
was
calling
out,
we
have
said
you
know
we
should
use.
We
have
a
common
code
of
conduct,
but
the
projects
are
like
okay.
A
Was
just
gonna
say
that
that
that
captures
whatever
very
well
what
I
was
thinking,
michael.
Thank
you.
That's
all.
D
D
That
first
line
just
says
will
be
used
by
them.
It
doesn't
say
how
or
what
the
expectations
are
matteo.
I
don't
know
how
we
can
make
it
less
any
less
than
that
would
be
saying
that
we
don't
expect
projects
to
actually
maintain
a
code
of
conduct.
J
J
J
I
am
not,
I
just
think
it's
essentially
if
this
working
group
decides
to
all
projects
should
be.
J
F
But
it
it
I
I
do.
I
do
take
matteo's
point
that
you
can
read
if
you
just
read
the
first
line,
you
can
take
it
as
that.
If
you
look
at
the
second
bullet
point
and
the
responsibilities
when
it
says,
define
minimum
code
of
conduct
requirements
that
at
least
tries
to
say
you
know
this,
the
whole
thing
that
the
process
we're
defining
for
the
foundation
and
what
and
what
will
be
done
at
the
cpc
level
is
not
the
same
as
what's
going
to
be
required
of
the
projects
that
could
be
substantially.
D
Smaller
so
the
flip
side,
if
we
don't
define
the
projects
in
that
first
line,
then
it
somewhat
implies
that
the
code
of
conduct
committee
will
be
making
things
without
thinking
about
the
project's
needs
and
thinking
solely
about
the
teams
of
the
top
level
foundation
like
to
me.
I
see
I
see
this
as
like
a
commitment
to
adhering
to
the
needs
of
the
projects
not
taking
control
from
them.
G
Yeah,
I
I
like
the
correction
that
just
like
anonymous
dingo
made
right
now
for
use
by
the
foundation.
Instead
of
that
will
be
used,
I
think,
does
does
that
sort
of
elevate
your.
J
Yeah
it
does,
it
does
yeah,
it's
essentially
it's
it's
not.
My
overall
concern
is
not
like.
Projects
should
be
as
autonomous
as
possible
and
if
I
just
don't
want
to
some
extent
to
to
create,
to
reduce
this
autonomy
in
any
form,
yeah
no.
D
J
J
J
B
Yeah,
I
appreciate
your
concern.
I
hear
you
holy
mateo
and
I
and
it's
funny
that
that
small
change
of
language
does
help
with
that.
Yeah.
J
It
just
yeah
totally
so
they
just
wanted
to
clarify
this,
the
the
the
bit
because
it's
for
me,
it's
significant
the
difference
between
one
versus
versus
the
other
great.
B
D
D
B
B
For
the
sake
of
time,
I
I
would
suggest
that
we
I
mean
we
can
spend
a
moment
on
these
responsibilities,
but
maybe
it
would
be
best
to
just
pr
what
we
have
here
in
and
we
can
work
on
it
further
in
the
pull
request.
What
do
people
think.
B
And
I'm
happy
to
let
folks
finish
their
thoughts
here
we
can.
What
I'm
suggesting
is.
Maybe
we
move
on
to
the
next
time
box
things
on
the
agenda
here,
which
was
focus
on
unblocking
onboarding
or
specifically
related
to
code
of
conduct
issues?
Any
objection
to
moving
on
to
that
I'll.
Let
folks
finish
their
thoughts
in
the
doc
and
then
I
can
pr
that
into
the
working
group
file.
B
Jory,
can
you
do
that
for
me?
Oh.
A
Yeah,
sorry,
I
think
I
lost
the
view
from
yeah
because
we
were
sharing
sorry
chris.
B
Cool,
so
I
can
stop
sharing
and
jory.
I
would,
I
would
ask,
maybe,
since
you
are
probably
most
familiar
with
what
is
blocking
onboarding,
would
you
mind
going
through
some
of
those
sure
yeah.
A
So
also
thanks,
everyone
for,
for
that
conversation
now
just
now
on
the
the
charter.
A
I
think
that
really
is
quite
helpful,
so
one
of
the
reasons
we're
we're
focusing
on
this
obviously,
is
that
we
have
a
bunch
of
projects,
some
of
which
and
haven't
completed
their
onboarding
projects,
some
incubating
projects
who
are
just
getting
into
to
this
step
and
are
looking
for
guidance
and
the
critical
questions
that
we
really
haven't
answered
definitively
for
them
relate
to
how
they
consume
our
code
of
conduct
and
and
where,
where
our
canonical
you
know,
coc
like
is
now,
I
think
at
this
point
most
of
us
understand
we
we
do
have
even
a
url
for
that
at
code
dash
of
dashconduct.openjsf.org
and
but
I
think
that
there's
still
some
question
within
the
community
about
whether
that
is
in
fact
canonical.
A
So
how
do
we
ask
them
to
to
consume
that
canonical
and
then
the
the
the
next
bit
of
blockage
is
related
to
how
projects
escalate
to
us?
A
So
what
does
that
system
look
like,
and
I
think
and
and
I'd
be
very
keen
to
hear
from
toby
and
mateo
and
others
on
the
call
who
have
projects
that
they're
they're
bringing
in
through
and
jordan,
bringing
it
through
incubation
that
that
would
at
least
unblock
the
immediate
problems
areas.
But
if
there
are
other
points,
I'd
love
to
to
hear
that
too.
G
I'm
happy
to
speak
from
the
perspective
of
amp.
I
think
where
we're
at
here
is
that
I
don't
think
it
changes
very
much
for
the
amp
kind
of
conduct
working
group
as
to
where
that
documentation
is
stored
and
how
that
process
works.
As
long
as
the
underlying.
G
Flow,
if
you
will
is
well
accepted
and
understood-
and
I
think
there's
agreement
as
to
what
the
underlying
flow
is,
which
is
project,
handle
this
at
their
stage
and
there's
an
escalation
path.
So
where
exactly
it
happens,
I
don't
think
the
the
coc
group
actually
really
cares.
I
would
just
like
to
have
clarity
so
that
we
can
actually
resolve
that
issue
and
move
forward.
G
Whether
the
code
of
conduct
for
the
whole
foundation
has
ways
to
have
emails
for
the
different
projects,
like
that
part
of
sort
of,
like
that
implementation
of
the
process
to
be
more
specific,
doesn't
really
matter
to
us,
like
the
only
thing
that
you
know
the
the
amp
project
cares
about
here
is
to
have
something
to
work
with
and
just
implement
that
and
and
and
be
done
with
it.
G
I,
I
don't
think
it's
gonna
effectively
change
a
lot
of
things
was
the
caveat
that
something
has
been
brought
up.
Multiple
times
is
in
a
situation
of
crisis
that
involves,
you
know,
bringing
up
a
court
of
chronic
violation.
You
want
the
process
to
be
simple
and
clear
from
the
perspective
of
the
reporter
of
the.
A
So
I
think
that
perhaps
a
comment
that
I
added
on
number
515
and
I'm
just
gonna-
go
grab
it
and
pop
it
into
the
chat
so
y'all
can
see.
It
may
illustrate
this
a
bit
which
is
you
know
this.
This
is
a
pull
request.
That's
open
about
adding
the
and
reporting
emails
to
the
code
of
conduct
itself
so
that
if
an
individual
hits
our
code
of
conduct
they
and
can
quickly
find
the
reporting
email
associated
with
whatever
project
they
are
they're
they're.
A
Looking
up
at
the
bottom,
I
added
some
a
comment
for
additional
context
and
that
kind
of
points
to
how
this
is
being
handled
in
a
variety
this.
A
This
path
that
toby's
describing
is
kind
of
being
handled
in
a
variety
of
different
ways,
and
one
of
the
questions
I
would
have
is
like
you
know:
are
there
a
couple
of
different
ways
that
we
want
to
support
so,
for
example,
in
the
js
foundation
and
it
used
for
former
the
the
artist
formerly
known
as
the
js
foundation,
we
had
a
a
code
of
conduct
file
in
every
project.
A
This
project
adheres
to
the
js
foundation
code
of
conduct
with
a
link
to
that
document,
and
then
it
also
included
the
reporting
email
address
in
in
that
file
and
that
so
it's
a
very
simple
two-line
file
and
that's
my
comment.
That's
that's
number
three
here
then
we
have
their
other
variability
beyond
that,
for
example,
they
may
have
consumed
the
coc
file
that
we
require,
but
not
report
not
not
put
anywhere
within
their
their
documentation.
The
reporting
email
address.
So
you
know
the
the
question
becomes.
A
Is
there
a
specific
pattern
that
we
want
all
projects
to
follow
here,
just
for
simplicity
or
do
we
want
to.
G
Well,
just
to
clarify
this
I
mean
the
referencing,
for
example,
at
the
organization
level
of
amp
already
happens
right,
there's
only
one
code
of
conduct
for
the
whole
organization
of.
J
G
And
currently
that
one
is
hosted
in
a
meta
representation
on
the
amp
organization,
from
the
perspective
of
amp
like
whether
that
is
there
or
like
at
the
foundation
level,
doesn't
I
don't
think
it
changes
a
lot,
except
if
there's
like
too
much
back
and
forth,
I
think
that
was
the
the
thing
that
nana
brought
up,
which
is,
if
you
have
someone,
that's
in
the
you
know,
main
amp
representative
has
their
witnesses
or
like
it
wants
to
report
a
code
of
chronic
violation
goes
into
the
code
of
conduct
of
the
main
amp
repository
is
pointed
to.
G
G
So,
as
I
think,
I'm
sorry,
I
think
both
options
where
that
is
locally
or
at
the
foundation
level
work
from
the
perspective
of
that
particular
use
case.
That
particular
scenario.
D
I
think,
speaking
to
like
the
request
that
mateo
had
before
as
well,
I
think
it's
reasonable
to
allow
projects
to
make
a
decision
here
about
what
works
best
for
their
project.
As
as
far
as
like,
vendoring
or
pointing
is
concerned,
every
project
is
going
to
have
different
needs.
D
It
seems
to
me
reasonable
to
allow
projects
to
to
have
their
own
with
more
or
less
the
expectation
that
they
keep
it
up
to
date,
and
I
think
that
this
is
something
that,
if
we
wanted
to-
and
maybe
this
is
like
something-
the
code
of
conduct
working
group
could
work
on-
we
should
be
able
to
create,
for
example,
like
a
github
action
that,
on
a
regular
basis,
can
check
to
see
if
the
upstream
code
of
conduct
has
changed
and
automate
the
process
of
sending
a
pull
request
to
update
it,
for
example.
D
F
F
You
know
you
just
need
to
include
the
reporting,
the
escalation
section
as
as
part
of
that.
A
Personally,
I
think
that
there's
a
number
of
of
at
large
at
large
projects
that
would
just
be
happy
to
you
know,
do
like
the
short
and
sweet
two-line
option,
but-
and
you
know
respecting
the
agency
here-
of
projects
that
have
really
robust
moderation
and
coc
groups
to
you
know,
be
able
to
maintain
their
documentation
and
just
add
an
escalation
path
like
that
seems
very
considerate.
So
you
know,
I
think,
like
that's
great.
D
If
that
makes
sense
yeah,
I
guess
like
the
one
thing
that
we
may
want
to
confirm
here
would
be
you
know
what
level
of
modification
is
acceptable
for
the
downstream
code
of
conduct.
It
seems
like
we.
We
have
consensus
that
folks
like
need
to
be
able
to
change
the
reporting
address.
D
Perhaps
it
would
be
reasonable
for
us
to
be
explicit
if
that's
kind
of
the
only
moderate,
if
that's
the
only
modification
that
projects
should
be
allowed
to
make.
B
F
D
D
The
other
thing
that
we
could
point
out
to-
and
this
could
just
be
like
a
resource-
not
an
official
documentation-
is
we
could
potentially
keep
a
reference
to
extensions
that
projects
have
so.
D
The
node.js
project,
for
example,
has
like
our
membership
expectations,
which
is
not
part
of
the
code
of
conduct,
but
is,
like
you
know,
obviously
related
to
to
it,
and
I
think
that
showing
some
of
these
practices
can
can
also
be
a
great
way
to
point
out
to
projects
like
here's,
how
you
can
do
some
things
that
go
above
and
beyond,
without
having
to
modify
the
baseline
code
of
conduct
that
we
all
share.
A
So
I
think
we,
it
sounds
like
we've,
we've
kind
of
come
pretty
close
to
agreement
on
one
of
the
the
key
issues,
which
is
what
are
the
acceptable
options
for
consumption
of
our
coc,
and
so
I
think
something
we
need
to
do
as
a
next
step
is
open,
a
pr
somewhere
that
describes
these
options
and
get
some
thumbs
up
on
it
and
included
with
that.
I
think,
is
a
a
paragraph
or
a
sentence,
or
you
know
some
some
bit
that
describes
the
escalation
piece.
A
Where
so,
you
know
to
to.
A
We'll
see
that
and-
and
this
is
actually
a
a
this
section
and
is
something
that
I
think
some
projects
have
reported
being
uncomfortable
with
so
like
this
in
exceptional
cases,
where
a
reporter
wishes
to
challenge
the
response
from
the
project's
coc
team
or
from
the
cpc,
like
that's
that
speech.
That
piece
specifically,
is
something
that
at
least
one
project
has
said.
I'm
we're
not
comfortable
with
that
being
permitted,
because
it
kind
of
feels
like
a
you
absorption
of
the
project's
authority.
B
A
Yeah,
I
think
it's
I
think
it's
just
about
going
beyond
like
the
the
project's
economy,
so
the
concern
is
well.
You
know,
we
said
you
know
we
gave
we.
We
applied
some
intervention
here
and
then
the
person
is
appealing
it
through
the
coc
process,
the
coc
escalation
email
at
their
own
behest,
and
what?
If
the
coc
escalation
group
reaches
a
different
conclusion
like.
F
Right,
like
there's,
no
there's
no
required
escalation
path,
which
was
one
of
the
in
that
that's
in
there
because
there
have
been
past
complaints
of
you
know.
Hey
we
made
reports
to
a
particular
group,
the
people
who
were
in
that
group.
You
know
weren't,
impartial
or
whatever
we
had
no
way
to
escalate.
B
A
Yeah-
and
I
don't
think
they're
this,
this
project's
particular
concern
was
like
you
know,
for
the
for
the
individual
using
this
email
because
they
may
be
having
difficulties
with
with
the
people
on
the
coc
group
themselves
like
like
that
it
wasn't
that
use
case.
It
was
the
it
was
the
you
know,
we've
made
a
decision,
and
now
this
now,
this
person
wants
to
appeal
that
decision
to
an
ostensibly
higher
authority,
where
the
project
clearly
wants
to
be
the
highest
authority
on
their
coc.
F
A
I
I
I
don't
know
I
mean
this
isn't
I'll,
be
completely
frank.
This
is
not
my
point
of
view.
I'm
just
trying
to
you
know.
F
This
does
come
back
to
the
like
the
minimum
requirements
for
being
part
of
the
foundation.
You
know
the
it's
do
you
have
it
and
where
you
draw
the
line
right,
the
way
that
this
this
was
written
before
was
the
minimum
was
that
you
know
you
agreed
to
have
the
common
code
of
conduct
and
that
you
agreed
that
this
was
an
escalation
path.
A
Yeah
I
mean,
I
think
it's
it's.
I
think
this
does.
This
question
does
point
out,
though
you
know
that
there
are
different
interpretations
of
escalation
and
that
there's
also
in
some
cases,
variability
even
in
among
members
of
of
the
same
project
right.
So
so,
there's
just
a
lot
more
conversation
that
we
need
to
help
and
support
projects
to
have
within
their
own
coc
groups.
A
You
know
to
kind
of
be
able
to
bring
those
to
the
to
the
broader
cpc,
so
we
can
actually
help
resolve
them.
B
But
I
think
this
was
a
productive
meeting.
I
appreciate
everyone
being
involved.
We
should
determine
what
we
want
to
do
next
week.
I've
got
the
pr
already
open
for
the
charter
for
the
code
of
conduct
working
group.
You
know
we
can
continue
to
use
this
meeting
time
or
we
can
spin
off
a
separate
meeting.
B
A
A
My
gut
would
be
that
that
is
something
since
that
would
be
sort
of,
like
some
guidance
for
how
to
do.
This
would
be
that
it
could
go
on
the
either
the
coc
repo
or
even
on
the
onboarding
repo.
Does
anybody
have
a
strong
feeling
about
where
documentation
like
that
should
live.
I
I
Because
you
know
and
just
say:
do
you
care,
or
are
you
just
going
to
follow
whatever
the
foundation
tells
you
do
you
have
a
strong
opinion
just
to
sort
of
get
some
feedback
on
that
from
the
leads,
because
I
know
like
for
dojo
and
intern
we're
just
going
to
be
like
whatever
the
foundation
says,
is
fine
for
us
we're
happy
to
follow
it
because
that's
like
the
path
of
least
resistance
and
we're
cool
with
that,
and
I
have
a
feeling
a
lot
of
the
projects
are
going
to
feel
that
way
as
well.
A
Yeah,
I
definitely
think
that,
like
as
part
of
this,
just
can
check
again
with
the
projects
all
of
them.
You
know,
maybe
even
especially
those
who
aren't
regular
participants
here.
It's
good.
C
B
Great
all
right:
well,
we'll
call
it
a
wrap
thanks.
Everyone
appreciate
you
and
your
time
and
we'll
talk
more
soon.