►
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
Well,
thanks
everyone
for
joining
another
episode
of
the
cross
project
council
meeting
at
the
openjs
foundation.
A
B
Well,
chronologically,
I
know
we
have
a
security
working
group
meeting
joe.
You
may
want
to
talk
more
about
that
in
a
sec,
but
september
is
heating
up
to
be
busy
in
early
october.
Let's
see
starting
next
week
next
thursday
I'll
be
on
a
panel
women
in
tech
panel
at
the
wix
developer
conference.
B
So
if
you
like,
wix
and
you're
a
developer
in
that
community
I'll
be
there
in
new
york
friday
september
16th,
we
are
having
a
node.js
hackathon
as
part
of
the
open
source
day
at
grace
hopper.
B
So
if
you're,
a
registered
attendee
virtual
or
in
person
check
us
out
it's
on
the
open
source
day
website,
node.js
is
a
featured
project.
So
that's
pretty
cool.
So
thanks,
danielle
adams,
franzi
and
rich
on
the
node
project.
Rich
trot
a
lot
of
cool
stuff
happening
there
and
then
sarah
and
I
and
paula
paul
and
others
from
the
foundation
will
be
in
orlando.
B
For
the
grace
hopper
conference
the
week
of
september,
20th
we'll
have
a
booth
under
the
linux
foundation
banner,
so
that'll
be
fun
and
that
same
week,
september,
22nd
and
23rd.
There
is
a
collaborator
summit
for
the
open,
visualization
collab
space.
So
if
you
love
openvis,
we
actually
have
a
slack
channel
open
visualization.
B
It
was
formerly
the
urban
computing
foundation,
so
some
of
those
mapping
projects
that
you
may
know
and
love
so
check
it
out.
We'll
have
the
eventbrite
space
up,
probably
today
for
tomorrow
and
last
but
not
least,
we
have
another
collab
summit
october,
first
and
second
adjacent
to
node.com,
which
is
a
very
popular
beloved
event
in
ireland,
and
so
that
is
october,
1st
and
2nd.
B
We
also
have
a
collab
summit
planning
channel
in
slack,
if
that's
something
you're
interested
in
and
a
and
a
github
repo
as
well
did
I
miss
anything,
there's
a
lot
going
on
a
lot
of
fun
stuff.
A
Excellence
yeah,
and
you
mentioned
the
security
collapse
space,
which
is
happening
immediately
after
this
meeting.
We
have
an
issue
on
that
that
we
can
touch
on
the
agenda,
so
we
can
talk
more
about
that,
but
just
to
reiterate
folks
want
to
check
that
out.
That'd
be
great
happy
to
have
you
anything
else
in
terms
of
announcements
or
perhaps
board
updates
would
be
another
thing
we
can
do
here.
I
mean,
I
guess
one
thing
to
say
is
the
recent
board
meeting
was
the
first
one
for
mateo?
B
We
had
four
new
faces,
which
is
pretty
fun
and
we
got
to
honor
michael
dawson,
who
has
been
such
a
steady
board
member
and
got
to
recognize
his
leadership
so
yay.
Thank
you,
michael,
but
yeah.
We
have
four
new
board
members.
We
have
mateo
who's
our
community,
one
of
our
community
reps.
We
have
two
new
silver
reps.
B
Now
paula
paul
and
abby
kabunick,
I'm
gonna
mispronounce,
your
last
name,
paula,
is
from
near
form
and
abby
is
from
github
and
yeah,
and
then
we
sonal,
who
is
our
google
rep,
is
passing
the
torch
she's
very
busy
at
work
and
with
life.
So
she
passed
her
board
seat
torch
to
sarah
jane
whitfield
at
google,
in
the
open
source
programs
office.
So
pretty
soon
we'll
maybe
have
even
we
have
two
sarahs.
B
Maybe
we'll
have
three
eventually,
but
we're
yeah
got
a
great
a
lot
of
enthusiasm
on
the
board,
so
pretty
exciting.
A
D
E
No
we're
still
working
on
the
process
of
getting
the
slides
in
front
of
the
cpc.
There's
been
that's
on
me.
What
I'm
going
to
do
is
get
a
version
this
week
before
the
next
cpc
meeting
in
front
of
folks
to
get
approved,
and
then
I'm
just
going
to
add
it
as
an
issue.
E
A
Great,
thank
you,
sarah
and
all
right
so
jumping
into
things.
Then
I'll
start
clicking
through
on
the
agenda
here.
The
first
issue
is
923
clarify
voting
processes.
I
don't
know
if
anybody
has
any
updates
on
this.
I
know
we
were
going
to
try
to
do
a
working
session,
but
that,
I
think,
has
you
know
not
not
happened.
A
B
Working
session
was
canceled
the
last
time
because
of
summer
holidays,
but
it
will
be
next
on
the
agenda.
B
That
edit,
so
if
you
all
recall,
we
have
a
pinned
agenda
essentially
on
our
cross
project
council
issue
that
has
the
topics.
A
And
I
will
also
add
it
to
the
notes
here
at
the
bottom
of
the
page.
There
is
a
section
that
says
next
week's
work
working
session
voting
process.
B
I
am
editing
816
the
cpc
meeting
schedule,
that's
pinned.
A
A
Cool-
and
I
will
say
in
the
notes
here
we'll
work
on
in
the
next
working
session-
great
all
right.
A
Every
week,
maybe
every
other
week
moving
on,
then
the
next
issue
is
9
11..
This
is
the
openjs
world
retrospective.
I
know
we've
talked
about
this
a
few
times.
I
don't
know
if
this
is
something
that
needs
to
remain
open,
or
we
should
have
some
more
notes
in
here
or
links
to
notes.
B
I
I
have
all
of
the
data
from
the
event
it's
all
organized
in
graphs
from
the
event
team.
It's
a
pdf.
I
think
I
could
just
share
it
in
the
issue
or
I'll
share
it
in
slack,
but
we
have
all
of
that
data
now
complete.
E
A
I
think
that
we
did
at
least
once
on
on
both
retrospective
and
planning,
and
we
have
started
the
program
committee
as
well.
So
I
don't
know,
maybe
that's
something
to
take
over
there,
but
I
think
posting
stuff
to
that
issue
would
be
great.
You
know
for
okay.
A
Should
well
I'll,
maybe
we
can
close
the
issue
once
we
capture
some
some
numbers
there
and
again,
I'm
not
sure
I
feel
like
wally
took
some
notes.
I
don't
know
if
those
should
also
be
added
here
too.
A
A
But
if
I'm
going
to
move
along
without
objection,
the
next
issue
is
910.
This
is
the
patching
script
for
code
of
conduct,
modifications
to
the
upstream.
This
is
something
that
I
was
going
to
work
on
and
now
that
I
have
a
place
to
live.
I
can
consider
that,
but
of
course,
if
anybody
else
wanted
to
jump
in,
I
would
not
object
as
well.
A
I
think
tyranny
even
pinged
me
something
that
he
thought
would
be
an
easy
way
to
manage
this.
So
it's
on
my
list.
I
will
try
to
get
to
this
soon.
A
Somebody
beats
me
to
it
so
not
much
more.
There
we've
got
another
open,
js
world
issue
here.
This
is
908
js
world
2023
planning.
Similarly,
I
don't
know
if
we
should
add
some
things
here
and
then
move
the
discussion
over
to
the
program
committee
or
what
people
think.
B
Yeah
we
had
a
really
well
attended
program
committee
meeting
last
week.
I
think
that
the
general
consensus
talking
with
the
board
on
budget
talking
with
program
committee
and
some
of
the
kind
of
post-mortem
conversations
we've
had
with
this
group
is
that
we
won't
do
a
big
stand-alone
event
next
year
in
2023,
but
rather
we
will
co-locate
and
do
adjacent
side
events
or
and
with
the
linux
foundation
and
other
partners,
so
be
that
node,
compu
or
half
stack
or
other
of
your
favorite
third-party
events
or
non-linux
foundation.
B
Events
we'll
be
working
on
putting
together
a
plan
prioritizing
that
budget
and
then
think
about
how
we
can
take
some
of
our
some
of
our
folks
and
take
put
them
on
the
road
as
well
and
plugging
them
into
places.
B
Yeah-
and
I
think
a
lot
of
the
planning
will
happen
in
the
program
committee
so
again,
if
that's
something
you're
interested
in,
I
would
really
encourage
you
to
participate.
That's
on
the
public
calendar,
so
I'll
I'll
put
some
information
in
there.
So.
B
We're
getting
numbers
to
be
clear:
we
did
lose
money
at
open,
js,
world
2023
sponsors
just
you
know,
weren't
there.
So
we
you
know
we
do
have
some
buffer.
So
so
that's
okay,
this
year,
but
it's
not
a
long-term
sustainable
model
for
sure.
A
A
Moving
on,
then,
I
think
this
next
issue
is
issue
906.
This
is
the
cpc
at
large
voting
member
election.
D
B
F
B
Only
had
soul
nominees,
we
have
emily
and
michael
and
toby
as
our
at
large
and
community
reps.
So
we
had
soul
nominees
in
those
categories.
B
And
our
website
update
is
in
the
works,
it
was
something
we
thought
we
could
be
managing
ourselves
and
there
were
some
changes
on
the
lf
wordpress
site,
but
we
are
fixing
those.
So
we
can
more
easily
manage
our
own
updates,
cool.
A
Well,
congratulations!
Everyone
kahil!
Maybe
if
you
get
a
moment,
can
you
update
that
issue
and
then
we'll
call
that
one
around
yeah.
A
That
would
be
great,
and
then
I
don't
know
accordingly,
you
know
there's
a
little
bit
of
conversation
in
slack
about
members
and
teams
in
github.
If
you
wouldn't
mind
taking
a
look
at
that.
D
Yeah,
but
I
mean
thanks
for
liking,
that
one.
A
These
updates,
as
well,
would
be
great
if
everything
was
online,
that'd
be
cool,
and
if
you
need
help
just
let
me
know
cool
so
then,
once
we
get
that
updated,
we
can
close.
That
issue
that'd
be
great.
Is
that
the
same
thing
for
the
cpc
impact
voting
member
selection,
I
mean,
I
guess
this
is
selection,
not
election,
jquery
node
electron.
B
Had
most
of
them,
appium
gave
me
their
updates.
Tierney
gave
us
the
electron
updates.
Shelley
is
swapping
out
with
eric
zao
and
electron.
We
are
not
electron
appium,
we
lost,
they
had
two
anyhow,
let's
see
but
yeah
folks
have
been
sort
of
sending
us,
and
this
is
where
it's
interesting,
because
it
our
governance
model,
said
that
the
cpc
would
ratify
the
the
impact
project
reps,
which
is
a
little
fuzzy.
B
A
So
yeah,
if
you
have
any
more
info
you
can
put
in
that
issue,
and
we
can
close
that
that
would
be
great.
I
also
would
imagine
that,
even
though
this
is
a
selection
rather
than
an
election,
this
ratification
question
is
something
that
perhaps
we
could
address
in
the
voting
process.
B
F
I
think
you
know
my
understanding
is
that
it's,
you
know
the
it's
not
an
election,
but
the
the
cpc
you
know
basically
has
a
has
the
ability
to
look
at
the
group
and
say
yeah
that
the
people
have
been
nominated
fit
in
with
the
expectations
that
we
have,
for
you
know,
voting
members,
and
so
it's
it's,
maybe
largely
a
rubber
stamp.
F
But
if
there
was
a
case
where
somebody
was
was
nominated
and
they
really
didn't
fit
with
the
values
or
you
know
that
the
cpc
could
could
choose
not
to
so,
I
think
like
in
terms
of
the
the
governance.
All
that
really
needs
to
happen
is
like
you
know,
maybe
that's
just
an
email
to
the
cpc
voting
member
saying
here's
the
list.
A
Yeah
I
mean
it
could
even
be
through.
You
know
some
sort
of
pull
request
as
well.
You
know
yeah
whatever's,.
F
D
G
If
I
may
just
quickly,
this
feels
like
some
of
what
galileo
was
talking
about
in
terms
of
having
some
internal
process
on
the
on
the
fa.
On
the
foundation's
side,
like
there's
a
number
of
things
that
we
have
clear
understanding
of
like
the
high
level
of
what
we
have
to
do,
and
then
it
was
like
the
actual
process
of
doing
it,
and
that
feels
like
it's
like
it
falls
in
that
category.
So
I
don't
know
where
it
should
land
but
like.
It
feels
like
the
same
kind
of
problem.
B
A
Yeah,
maybe
there
should
even
be
like
an
operations
dock
that
might
we
can
drop
these
things
in
because
there
is
some
operations
like
guidance
for
onboarding,
regular
members.
A
B
B
It's
we
have
a
lot
of
informations
in
the
governance,
but
what
I
found
is
my
eyes
were
starting
to
cross,
as
I
was
like
trying
to
read
and
interpret
and
cross-reference
in
a
variety
of
places.
So
just
what
maybe
one
sort
of
really
simple
sort
of
source
of
truth
right
on
on
that
which
we
can
clarify
in
that
working
session.
A
Yeah:
okay,
I'm
adding
that
comments
as
well
like
just
operations
and
procedures,
and
things
like
that.
B
Even
the
voting
tool
we've
pretty
much
standardized
on
that
with
opa
vote
and
and
where's.
F
A
Cool,
I
dropped
a
couple
comments
in
that
voting
process
stuff
issue
so
that
we
can
be
sure
to
touch
on
them
right
on
if
there
is
nothing
else
on
that
one
I
will
continue
on.
I
think
this
is
another
voting
election
issue
that
we
can
probably
close.
A
This
is
the
secondary
cpc
director.
So
again,
thank
you,
everyone
for
running
and
thank
you.
Congratulations,
mateo!
For,
for
being
our
new
rep.
D
A
A
B
I'll
put
all
the
all
the
registration
information
in.
I
know
the
virtual.
The
in-person
event
is
sold
out
with
the
virtual,
which
allows
you
to
participate
in
the
note
hackathon.
It's
still
open.
B
We
are
limiting
the
number
of
folks
who
participate
in
the
hackathon
just
because
it
is
very
sort
of
hands-on.
So
we're
going
to
cap
that
at
75.,
okay,.
A
Great,
so
should
we
update
that
with
any
links
or
updates.
A
Okay,
great,
so,
if
I
am
to
move
along,
I
am
on
one
of
our
favorite
pull
requests
here.
This
is
851..
This
is
to
update
the
contributor
covenant
code
of
conduct
to
version
2.1.
A
I
had
this
also
on
my
list
to
simply
updates
you
know,
so
it's
able
to
be
merged
and
then
merge
it
and
then
have
the
tool.
You
know
open
up
a.
I
don't
know
exactly
how
the
process
will
be,
but
basically
document
the
changes
that
we
want
to
make
to
the
upstream
and
then
implement
that
tool
to
to
track
those
kinds
of
changes.
G
Toby
yeah,
we
have
this
conversation
like
every
other
week
at
this
point
and
every
other
week
we
sort
of
like
slightly
change
what
it
is
that
we
want
to
do
with
that
thing.
Last
time
we
had
this
conversation.
G
The
agreement
was
that
we
would
not
merge
this
until
we
had
the
tool
ready
for
the
other
thing,
which
is,
I
think,
the
first
issue
that
you
talked
about
today
and
like
I
actually
personally,
really
don't
care,
but
I
think
we
should
like
do
a
thing
and
stick
to
it
and
not
have
it
like,
like
not
have
a
conversation
about
it
every
other
week.
A
A
I
was
kind
of
thinking
as
I
was
talking,
so
it
didn't
maybe
come
out
perfectly
but
yeah
the
tool.
I
need
to
figure
out
how
to
do
the
patching
and
then
once
I
have
that
ready
can
kind
of
step
through
this,
but
I
agree
I
am
very
much
looking
forward
to
not
having
this
issue
on
the
agenda.
A
So,
however,
we
can
get
that.
I
mean
I
have
the
plan
to
figure
out
the
patching
and
then
we'll
try
to
move
it
forward
and
now
that
I
am
living
somewhere
I
can.
I
can
focus
on
that.
So
hopefully.
G
A
Yeah
yeah
we'll
get
to
that
issue
in
one
minute,
so
I'm
gonna
move
on
because
I
don't
want
to
talk
about
that
one
anymore,
but
I
will
work
on
it
soon.
The
next
one
is
issue
826.
This
is
a
focus
on
javascript
security
open.js.
A
We
talked
about
it
earlier.
The
first
meeting
is
in
26
minutes.
25
minutes
roughly,
have
we
created
a
repo
for
this?
Yet
I
don't
know
if
we
have,
but
that's
kind
of
one
of
the
first
things
I
don't
think
I
wanted
to
do
until
we
started
the
process.
A
So
in
the
next
meeting
we
will
start
to
head
down
that
road.
I
will
admit
that
I
don't
have
a
lot
prepared.
I
have
a
couple
of
things
that
I
think
would
be
great
to
to
to
be
the
first
things
that
we
start
to
work
on,
but
yeah.
A
A
So
I
hope
folks
will
join
me
in
20
some
odd
minutes
and
we'll
talk
about
security
in
the
open
jazz
space
which
I'm
looking
forward
to.
B
B
We've
been
blogging
with
the
progress
report
and,
of
course,
is
a
robust,
more
robust
details
on
that
from
rafael
on
github
at
near
form.
Thank
you
raphael
and
thanks
all
of
you
who
have
been
sort
of
working
with
him,
so
one
of
the
things
from
near
form
and
from
trail
of
bits
who
are
working
on
that
is
everything
that
we're
learning
and
doing.
I
know
they're
thinking
about
how
does
this
apply
to
other
javascript
projects
or
other
open
source
projects
generally.
B
So
it's
probably
a
good
a
good
starting
point.
I
know
that
they're
tracking,
I
see
them
in
the
open,
ssf
slack
channel,
that's
a
good
place
to
join
as
well.
If
you
haven't,
there
is
a
best
practices
channel.
There's
a
project
alpha
omega
channel,
all
of
those
places
where
we're
sort
of
living
right
now.
A
Yeah-
and
there
are
lots
of
meetings
too,
on
the
open,
ssf
side,
you
know
securing
open
source
projects
and
best
practices,
and
there
are
a
lot
of
meetings
on
the
open,
ssf
site,
so
cool.
I
look
forward
to
kicking
that
off
and
we'll
continue
there.
A
So
if
I
am
to
move
along
the
next,
one
is
toby's
favorite
or
no.
This
one
is
the
license
check
one
this.
This
one
is
we're
still
kind
of
just
waiting
on
the
foundation.
I
think
on
this
one
right:
yeah.
B
E
A
All
right
moving
along
this
is
issue
786
clarify
requirements
around
could
have
cometh
violation.
This
is
another
thing
that
we've
had
open
for
over
a
year
august,
3rd
2021.
So
this
one
I
think,
yeah.
This
is
the
one
one
of
the
ones
that
you
have
toby
on
on
your
list.
A
So
we'll
keep
that
one,
as
is
no
update
and
issue.
761
is
build
stronger
ties
between
at
large
maintainers
and
their
cpc.
Rep.
G
I
had
a
plan
for
this,
but
I
no
longer
have
a
plan
for
this.
G
Well,
I
have
to
rethink
this
now.
I
think
it
would
be
good
for
emily,
matteo
sarah
and
I
to
try
to
figure
something
out
here.
It
might
be
if
you'll
output.
E
G
The
one
after
I
mean
it's,
it's
like
it's.
This
been
an
issue
open
for
a
fairly
long
time
that
we
sort
of
like
try
to
figure
a
way
around,
and
I
don't
think
there's
like
a
huge
amount
of
urgency
like
two
weeks
and
not
gonna
change
like
this.
So
if,
if
it's
easier
sort
of
like
mid-october,
whenever
the
next
one
is
that
the
4th
of
october.
C
B
I
just
updated
on
october
18th
is
that
work.
A
So
yes
good
question:
I
can
tell
you
just
look
at
the
two.
C
D
C
B
A
A
A
Is
that
right,
so
that
would
be.
G
C
G
B
Yeah,
I
do
appreciate
your
patience.
We
do
have
a
new
team
and
we
actually
have
an
an
open,
half
open
head
count.
So
if
you
know
great
people
but.
G
Oh,
I
I
was
throwing
the
stone
at
snowed
at
the
staff
just
to
be
clear.
A
A
G
No,
we
haven't
we've
tried,
but
since
I'm
the
only
one
that
actually
cares
about
this,
I
have
a
thing
on
my
to-do
list,
and
I
said
I
I
just
re-tap
them
every
whenever,
like
a
quarter
actually
happens.
A
G
That
was
sort
of
like
the
suggestion.
At
some
point
I
mean
there
were
things
that
felt
like
it
was
a
pain
to
have
them
on
a
weekly
basis,
but
it
was
useful
to
have
them
from
time
to
time.
That
was
one
of
them,
and
so
I
looked
at
it
like
a
couple
weeks
ago,
I'm
like
oh
I'm,
going
to
put
this
back
on
the
agenda
because
it's
been
like
a
while.
We
haven't
talked
about
it.
So,
yes,
I
think
it
would
be
useful,
but
you
know.
A
Yeah,
there
is
even
mention
in
the
dates
and
reminders
thing
to
check
the
issues.
Labeled
cpc
quarterly
review
at
the
end
of
every
quarter,
so
we
should
maybe
just
think
about
that.
I
guess.
A
If
we
don't
have
anything,
we
need
to
review
then,
okay,
but
if
we
do
we
should
we
should
either
label
it
or
drop
it
into
that
dock
dates
and
reminders.com.
A
All
right
that
was
the
last
issue,
the
last
agenda
item,
so
we
got
15
minutes
what
else
we
want
to
tackle.
B
There's
just
a
couple
of
pr's
open,
I
believe,
if
you
all,
could
kind
of
check
in
travel
fund,
we
still
have
budget
and
our
travel
fund.
We
have
two
collab
summits
coming
up
one
in
dublin,
one
in
madrid.
So
if
you
are
an
active
collaborator
and
need
support,
please
do
ask.
A
Yeah,
I
think
I
think
eric's
request
has
enough.
D
Are
we
expecting
anything
to
happen
there?
That's
on
so
so
that
one
define
a
proving
process
for
changes
to
the
code
of
conduct
and
it
was
started
by
christian
broman.
I
think,
is
blocked
effectively
by
me.
A
G
I
mean
it
would
be
kind
of
cool
to
run
through
the
issues
in
the
issue
tracker
and
close
stuff
at
some
point
and
dealing
with
a
bunch
of
open
things
that
we
are
not
ever
gonna
do
and
just
look
out,
I
don't
know,
could
that
be
part
of
something
of
that
nature.
At
some
point.
C
D
I'm
not
a
fan
of
those
sailbots.
Personally,
I
think
yeah,
it's
a
big
middle
finger.
If
an
issue
I
care
about
or
filed,
is
closed
by
a
machine.
C
D
D
So
we've
got
67
open
issues
at
this
time
of
which
22
look
like
they're
automatically
generated
meetings
for
different
council
meetings
can.
C
A
We've
been
working
on
a
better
solution
in
the
pkgjs
org,
but
it's
just
been
stalled,
for
I
don't
know
a
year
or
more.
I
I've
made
a
little
bit
of
headway
on
it.
That
would
use
hackmd
instead
of
google,
and
you
know,
would
have
a
more
automated
process,
but
it
just
hasn't
gotten
anywhere.
G
I
mean
there's
a
whole
bunch
of
like
sort
of
infrastructure
stuff
that
we
sort
of
do
that
with
right.
We're
like
it
would
be
good
if
and
then
it
sort
of
like
it
becomes
an
issue
that
we
talked
about
like
either
quarterly
or
every
other
week.
It's
like
that
would
be
nice
if
we
had
like
this
automated
that
of
this
automated
thing,
and
so
I
don't
know
like
it,
feels.
G
It
feels
like
we
should
find
solutions
that
actually
work
now,
instead
of
like
hoping
for
solutions
that
you
know
get
implemented
in
like
three
years.
F
D
G
No,
but
it's
not
that
hard
to
do
after
the
meeting
I
mean
look
joe.
I
have
a
similar
list
and,
like
other
things
where
I
have
you
know
similar
roles
that
you
have
in
here,
like
I'm
not
trying
to
like
I'm
not
trying
to
you
know
again,
blame
you
for
this
like
it's
just
like
this
stuff
is
actually
like
annoying
to
do
and
a
lot
of
people
are
not
like.
I'm
not
very
good
at
actually
like
keeping
up
to
date
was
like
really
annoying
tasks
like
this
one.
G
I
I'm
terrible
at
this
right
like
and,
like
you
know,
maybe
like
this
feels
like
a
problem.
Lots
of
people
have
and
like
maybe
we
could
find
other
options.
That
would
be
easy
to
do
so.
I
mean
like
one
of
the
things
I'm
looking
at
is
like.
Can
we
actually
do
this
using
like
zapier,
for
example
like?
Does
that,
for
example,
does
the
foundation
have
a
zapier
account
and
is
that
something
that
could
set
us
set
up?
It's
just
a
question.
I
don't
know.
B
Yeah,
okay,
let's
post
something
in
the,
maybe
in
your
in
the
pm
slack,
do
you
have
a
pm
slack
channel
yeah.
G
Awesome
because,
like
I'm
pretty
sure
you
can
do
something
that
is
like
80
of
this
using
zapier,
and
I,
like
I,
that
tool
has,
I
mean
you
know,
there's
lots
of
issues
relying
on
tools
like
this
for
stuff,
like
this
for
a
whole
bunch
of
like
very
good
reasons,
but
at
the
same
time
like
actually
not
having
to
think
about
this
and
having
this
stuff
archived
in
a
proper
place
would
be
really
cool.
A
B
Oh,
yes,
she's,
wonderful
and
well
shine
and
she's
still
participating
in
our
standards.
Working
group,
of
course,
but
that
do
does
mean
that
we
have
an
open
fit
count.
We
shared
jewelry
with
the
open
ssf,
so
we
are
looking,
but
the
linux
foundation
does
have
several
open
roles.
B
Back
from
maternity
leave
august
5th
and
she
was
out
through
august
5th
and
then
she's
sort
of
back
into
her
new
role,
helping
a
little
bit
because
someone
else
just
had
a
baby
on
open
ssf.
So
it's
just
a
little
juggling
there
as
well,
but
yeah,
but
we're
getting
some
where
we
need
it.
We've
been
getting
help
from
others
at
the
lf
or
we
have
questions.
Since
you
know
we
have
some
gaps
as
well
and
actually
thank
you.
Brian
warner.