►
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
All
right,
it
looks
like
we
are
live
so
thanks
everyone
for
joining
another
episode
of
the
cross
project
councils.
A
The
openjs
foundation's
cross
project
council
meeting
drop
the
link
into
the
dock
here,
today's
the
5th
of
july
2022
and
we've
got
a
full
schedule,
but
we
hope
to
since
we
have
a
small
group
here,
we'll
try
to
just
kind
of
run
through
it
quickly,
I'm
going
to
bounce
off
of
the
github
stuff.
Here
I
guess
I
should
follow
process
here.
Do
we
have
any
announcements.
B
I
actually
don't
think
we
have
many
announcements.
I
think
we've
come
off
of
a
couple
of
events.
I
think
a
lot
of
folks
I
know
and
on
our
team
are
on
vacation
from
the
fourth,
so
hopefully
everyone's
planning
some
nice
vacation
time
this
summer.
B
A
He
declined,
try
one
more
time
you
keep
declining.
I
will.
I
will
move
on
I'll
move
on
anyway.
Okay,
so
no
announcements-
and
I
assume
nothing
from
the
board
correct
me
if
I'm
wrong,
excuse
me
so
with
that
we
can
just
jump
into
the
agenda
and
jordan
has
declined
again.
So
you
know
you
can
just
hang
out
if
you
want
jordan
or
chat
if
you
want
something
from
us,
we'll
keep
on
so
where's
my
thing
here.
A
The
first
item
on
the
agenda
is
collab
summit
retrospective
walid.
You
open
this
issue
and
and
drop
some
notes
in
here
as
well.
Do
you
expect
to
do
a
formal
like
meeting
around
a
retrospective,
or
are
we
just
taking
these
notes
or
how
do
you
want
to
proceed
on
this
issue?.
D
So
I
yeah,
I
don't
think
we
so
we
did
discuss
some
of
the
points.
I
think
it's
it's
good
enough,
but
maybe
if
I
was
thinking
if
I
could
do
just
a
short
saying
with
cdr
joey,
so
just
let
them
know,
but
I've
sent
them
in
the
slack,
so
I
think
they
they
can
just.
They
can
just
review
the
few
of
the
points
we
have
highlighted
for
so
it's
just
to
bring
them
attention
for
them
to
it.
Other
than
that,
I
don't
have
anything.
D
B
Our
whole
team
had
I
thought
she
was
pulling
those
I
do
know
she
was
busy.
She
started
maternity
leave
again
july
1st.
So
while
later
our
kahila-
and
I
can
hold
those
for
you,
okay,.
D
Sure,
okay,
that
would
be
nice
so
that
we
can
close
close
those
issues,
and
maybe
someone
is
already
waiting
for
the
recording
okay
yeah
other
than
that.
There's
nothing.
I
know
we.
We
talked
about
having
a
retro
for
the
for
the
event
for
the
conference.
Also,
we
didn't
do
it.
B
Yeah,
I
think
an
agenda
item
would
be
great.
You
know
we
had
a
smaller
group
for
our
working
session
last
week.
Oh
hey
jordan,
so
we
thought
we
would
use
that
part
of
a
cpc
meeting.
D
Okay,
so,
okay
for
for
the
then
for
the
conference,
I'll
I'll
in
the
maybe
in
the
cpc
europa
I'll,
put
an
agenda
item
for
the
retrospective
of
the
conference
and
the
the
cpc
the
conference
team.
The
the
committee
team
can
also
join
I'll
bring
them
so
if,
if
they
also
want
so,
maybe
probably
in
the
next
cpc
session,
we
can.
We
can
talk
about.
A
Cool
moving
on
the
next
issue-
oh
great
thanks
for
fleshing
that
out,
wally
looks
like
you've
got
the
links
and
everything
here
on
the
dock.
Excellent.
So
next
item
on
the
agenda
is
the
secondary,
cpc
director
seat
issue.
We
talked
about
this
two
weeks
ago.
The
plan
was
to
open
up
nominations
immediately,
but
to
have
them
run
for
four
weeks
and
then
run
a
two-week
election
cycle
so
that
we
can
announce
the
person
on
the
cpc
meeting
on
august,
2nd,
which
is
oh.
D
Wait.
Sorry,
sorry,
joe,
I
think
I
copied
the
wrong
the
agenda
from
the
previous
meeting.
Sorry
yeah.
D
A
B
We
have
three
nominations
in.
If
you
know
we
can
probably
throw
another
note
up
on
slack
need
be.
I
think
we
have
some
other
reminders
for
cpc.
So
maybe
I
just
do
a
little
quick
reminder:
mail
today
or
tomorrow
with
some
other
deadlines.
Okay,.
A
That
sounds
good.
I
think
if,
if
you're
going
to
send
out
an
email,
maybe
these
other
elections
and
selections.
F
A
Those
make
sense
to
you
that
would
be
great,
I'm
looking
to
see
what
the
requirements
are
on
the.
A
The
seats
which
I
assume
that
the
folks
who
have
already
nominated
are
aware,
but
I
thought
for
the
sake
of
this
issue,
I
should
put
a
link
to
what
the
requirements
are
for
for
this
role.
C
You
put
a
lot
of
info
and
issue
already.
A
Cool
just
popping
that
in
there
so
that
you
know
if
somebody.
A
Want
to
submit
they
don't
realize
that
you
know
you
need
to
be
an
active
participant
and
things
like
that
right.
Let
me
just
double
check
this
eligibility
must
be
an
active,
open,
js
collaborator
and
cpc
voting
members
will
vote
on
candidates.
Okay,
cool
just
want
to
make
that
clear,
great
anything
else.
We
want
to
do
on
this
issue
for
today.
A
A
Yep
wow,
as
as
laid
out
in
that
issue,.
D
A
Where
is
it
here
discussion?
Today's
meeting
was
to
open
nominations
now
and
close
them
on
july,
19th
having
that
nomination
period,
be
open
for
four
weeks
and
then
run
a
two-week
election
cycle
with
the
ability
to
announce
the
new
person
on
the
cpc
meeting
on
august
august,
2nd.
A
Cool,
oh
I
see
rich,
is
here
too.
Let
me
let
rich
in.
A
A
So,
okay,
all
good
on
this
issue,
it
seems
hey
rich.
A
B
Yeah
we
had
our
program
committee
last
week.
I
believe
I
believe
our
proposal
we
wanted
to
get
feedback
from
this
group.
We'll
get
feedback
from
the
board
feedback
from
the
program
committee.
Is
that
still
with
covet?
You
know
bringing
uncertain
times
that
2023
we
co-locate
with
open
source
summit
on
north
america.
B
B
B
But
I
think
the
proposal
is
that
we
could
use
our
learnings
from
our
virtual
event
and
do
a
virtual
event
as
well
and
increase
the
number
of
sessions
that
we
had
just
like.
We
did
in
2020
2021.
B
If
you
look
back
when
we
had
just
the
entire
venue,
for
example
montreal,
I
believe
we
had
about
40
sessions,
and
that
is
pretty
much
the
number
we
kept
when
we
went
virtual
when
we
shared
the
space
co-located
with
the
cd
foundation,
we
did
22
in
person
and
about
22
virtual,
so
our
proposal,
so
we
would
bring
down
the
number
which
is
hard
right
when
you
have
40
projects,
it's
just
the
financial
risk
has
been
pretty
significant
with
covid
and
we
did
end
up
losing
you
know
money
this
year,
so
I
think
sponsors
are
still
uncertain.
B
There's
still
some
big
companies
who
didn't
send
their
employees
to
travel
this
year,
which
meant
they
didn't
sponsor
this
year.
So
it
was
just
sort
of
that
rolling
uncertainty
with
attendance
and
sponsorship.
B
On
the
flip
side,
the
idea
is
partnering
more
with
other
regional
events.
So,
for
example,
I
met
with
carter
robasta
from
cascadia.js
he's,
given
our
folks
discount
codes,
we're
helping
him
promote
his
their
event.
B
We
have
some
of
our
community
folks
who
are
speaking
and
then
the
idea
is
to
take
the
budget
that
we
would
normally
spend
on
openjs
world,
which
is
significant
and
then
invest
that
in
regional
events.
B
So
a
regional
event
like
like
cascadia,
actually
has
no
budget
impact
on
us,
so
it
does
give
us
the
ability
to
invest
more
in
collab
summits
and
partnering
with
regional
entities.
So
I
think
that
would
be
the
direction
I
think
until
we
see
global
travel
resume
and
sponsors
not
feeling
so
overwhelmed
or
taking
a
pass
that
that's.
You
know
that
would
be
my
recommendation
from
a
fiscally
responsible
price
per
person
for
attendee.
A
A
I
think
it's
a
very
interesting
approach.
I
I
I
like
it
from
the
perspective
of
like,
I
think
we
we
need
to
put
a
really
positive
spin
on
it.
Like
you
know,
yes,
the
pandemic
is
still
raging
and-
and
we're
still
impacted
by
that,
so
we're
going
to
take
a
new
creative
approach
by
diversifying
our
event
activity
and
supporting
more
local.
You
know
organizations
and
such
I
think
you
just.
I
think
we
just
need
to
be
careful
about
how
we
position
it
and
make
sure
yeah.
B
Yeah
and
I'd
like
to
talk
more
with
our
members
as
well.
These
events
only
happen
when
you
have
some
of
these
bigger
companies
sponsor
and
provide
sort
of
that.
You
know
that
foundation
for
you
to
to
host
and
convene
an
event,
so
we're
a
member
driven
organization.
Ticket
sales-
don't
you
know
just
won't
cover
the
cost
of
a
venue
like
that
yeah
yep
so
but
yeah.
Thank
you.
Ibm.
B
A
And
pretty
reliable,
okay
cool?
Well,
I
look
forward
to
hearing
how
this
develops
and
other
ways
we
can
partner
and
you
know
collapse,
summit
stuff
and
you
know
maybe
europe
and
other
places
outside
the
us
sounds
great
yeah.
B
We've
reached
out
to
some
other
js
com,
organizers,
so
yeah,
sort
of
the
invitations
out.
We
could
provide
a
number
of
resources
speakers,
you
know
funding
for
part.
You
know
part
of
the
venues
and
things
like
that,
but
I
think
getting
one
like
one
venue
for
one
global
event:
just
doesn't
pencil
out.
I
think
at
least
it
did
not
this
year.
So.
A
A
Did?
Oh
here's
khalil
anybody
reach
out
to
the
folks
down
in
columbia,
they're
very
active
down
there
yeah.
B
Yeah
yeah
yeah,
not
on
the
conference
planning
but
of
course
spent
a
lot
of
time
with
them
in
austin.
I
reached
out
to
the
nordic
js
folks
I'll,
be
doing
a
call
with
those
folks.
So
I
reached
out
to
malta
to
check
in
on
plans
for
js
comp
europe
to
see
if
that
will
come
back
so
yep
open
to
any
and
all
ideas.
A
B
We
would
still
have
a
unique
branding
if
we
co-locate
we'd
have
a
party.
You
know
we
could
have
collab
summits
for
the
projects
independently,
so
all
of
that
would
still
work.
Okay,.
A
All
right
great,
if
anybody
can
help
with
the
notes
too,
that
would
be
fantastic.
I
will
move
on
to
the
next
issue,
which
is
number
906
cpc,
non-impact
voting
member
election.
A
Okay,
so
this,
I
guess,
is
technically
open,
based
on
our
last
meeting,
doing
a
similar
thing
as
the
secondary
board
seat,
where
we
have
nominations
open
for
a
full
month,
and
I
should
maybe
make
this
clearer
in
this
issue
and
then
a
two
week
election
period
with
results
announced
on
august
2nd
at
the
cpc
meeting.
A
Anything
we
should
do
here.
I
mean
I
just
wonder
robin
if
we
should
socialize
this
as
well.
B
C
A
A
That
the
details
here.
A
All
right
cool,
if
there's
nothing
else
on
this
one
I'll
I'll,
keep
moving
along.
Where
are
my
notes?
So
that's
and
that's
a
similar
issue
is
the
905
the
cpc
impact
voting
member
selection,
which
we
should
work
on
as
well.
A
G
A
Sounds
good
all
right
cool
and
I
see
your
comment
here
rich.
We
can
probably
save
a
few
minutes
of
time
at
the
end
to
have
a
discussion
cool
all
right
so
robin
I
guess
this
is
another
thing
that
we
should
socialize.
Although
I
guess
it's
only
impact
member
projects,
so
it
may
be
a
different
email,
I'm
not
sure.
A
Moving
on
the
next
item
is
900.
This
is
the
public
slides
for
the
june
board
meeting.
We
were
going
to
look
at
this
last
meeting
two
weeks
ago,
but
michael
didn't
have
the
slides
handy
and
then
he
also
wasn't
sure
if
they
were
fully
approved
for
public
sharing
on
like
a
public
meeting
or
if
we,
if
that's
something,
we
should
be
doing
in
a
private
session
or
one.
So
since
we
don't
have
any
board
members
here
today
either.
I
guess
we
skipped
this
one,
but
we
should
maybe
clarify.
B
Our
board
meetings,
we
have
a
public
session
and
a
private
session.
I
think
the
idea
is
for
cpc
members.
We
would
share
the
private
session
notes,
perhaps
a
couple
of
things
redacted
for
any
particular
reason,
but
it
would
go
to
cpc
members,
so
we
could
definitely
review
that
in
a
private
session.
I
know
sarah
and
michael
both
work
on
that
version
to
share
with
the
cpc
so
I'll
check
back.
I
thought
that
was
done
in
june,
but.
A
Okay,
yeah,
and
maybe
we
should
have
a
process
for
that
on
a
monthly
rolling
basis
like
if
it
goes
out.
Redacted
goes
out
to
the
cpc
mailing
list,
but
also
yeah
an
agenda
item
for
us
to
discuss
in
a
private
session,
yeah
yeah,
okay,
great
all
right,
I
will
move
along
then
the
grace
hopper
one
is
next
here.
This
is
issue
898,
sorry
to
lean
on
you
again
robin,
but
any
any
news
on
this
one
or
caillou.
B
We
have
our
submission
in
for
open
source
day.
I
I
reached
out
to
all
of
the
projects
and
the
node.js
project
came
together
to
submit
a
proposal
for
a
hackathon
on
open
source
day,
which
is
the
friday
before
grace,
hopper
thanks
to
hill
and
rich
rich
as
well.
Yes
and
danielle,
and
branson
francie
lots
of
great
folks
on
the
planning
committee.
We
should
hear
by
july
8th,
which
is
in
a
few
days,
if
not
earlier.
B
If
we
have
that,
so
that
would
be
pretty
cool,
the
invitation
would
go
out
to
30
000
attendees.
They
expect
about
a
thousand
attendees
for
open
source
day
hackathon
for
and
about
100
per
project.
So
a
nice
way,
for
you
know,
for
the
project
to
have
some
diverse
folks
participating
in
a
hackathon,
and
I
think,
pulling
from
the
old
code
and
learns
is
something
that
the
team
is
looking
at.
If
you
remember
those
from
the
node.js
days.
B
Yeah
and
then
our
sponsorship
will
be
the
20th
through
the
23rd,
it's
in
orlando
half
virtual
half
in
person,
so
15
000
in
person
event.
So
that's
all
locked
and
we're
working
on
building
on
a
booth,
it'll
be
a
linux
foundation
umbrella.
But
our
team
is
running
point
so
more
to
come.
That's
when
you
sort
that
out
cool.
A
All
right,
that's
exciting,
good,
good,
good
where's,
my
window
again
here
great
so
moving
along.
This
is
issue.
885
ip
policy
license
exemption
request
for
loopback.
B
Yup
I
can
give
a
quick
update.
I
haven't
read
the
issue
closely
in
a
while,
but
there's
some
documentation
repos
with
luke
back
that
are
under
an
artistic
license.
They
were
the
idea
was
asking
for
an
exempt
exemption.
B
We
met
with
joanna
lee
our
our
council
on
this
and
ibm
with
todd
moore
because
they're
the
project
who
the
company
that
donated
those
trademarks,
the
advice
and
council
that's
going
back
to
the
board-
is
that
we
deny
that
exemption
request
and
re-license
those
over
to
mit
with
the
rest
of
the
project,
so
we'll
take
on
that
as
our
openjs
service
staff
team
and
working
with
all
of
those
copyright
holders
and
doing
that
read
license
that
could
take
some
time
to
track
everyone
down.
B
I
think
I
can't
remember
how
many
there
are,
but
you
know
some
of
these
repos
have
up
to
24
people,
so
we'll
have
to
contact
everybody
and
get
their
permission
to
do
that
so,
okay
and
who.
B
A
Great,
let
me
know
if
I
can
help
I'd
love
to
lean
on
diana
to
kind
of
make
it
happen.
But
please
keep
me
posted
todd,
we'll.
B
A
Cool
okay,
great
we'll
leave
this
on
the
agenda
for
now,
just
like
check
on
it,
I
guess:
does
that
make
sense.
B
A
A
Okay,
sounds
good.
Next
item
is
issue
874.
This
is
cpc
board
c
term
limits.
You
know
I
I
never
remember
where
we
kind
of
landed
with
this
toby.
I
don't
know
if
you
have
a
feeling.
I
thought.
A
F
C
A
Yeah-
and
I
see
your
comment
on
may
26th,
maybe
if
you
wouldn't
mind
just
kind
of
re-commenting
and
saying
you
know,
we
think
we're
going
to
try
these
steps
and
you
know
if
we
don't
feel
like
it's
working
out
as
well.
In
a
few
months
or,
however
long
then
we'll
re-open
an
issue
like
this
and
approach.
It
then
does
that
seem.
C
A
F
A
Okay,
great
excellent,
thank
you
toby,
let's
see
so
now
we
get
into
the
contributor
covenant
pull
request
here.
I
I
love
this
one.
This
is
my
favorite.
This
is
another
one
that
I
feel
like
we
keep
talking
about
and
have
plans
to
move
forward,
but
don't.
A
Yeah
yeah-
and
I
see
that,
what's
his
name
responded,
I
forget
his
actual
role
and
I
can't
really
ben
thank
you,
god
github,
I'm
thinking,
github,
okay,
great,
so
it's
available
for
maintainers
to
edit
this
to
get
it
to
the
place
where
we
want
to
land
it
and
then
so,
for
the
last
call
updated,
toby's
block
being
removed
as
well
and
manage
changes
via
patch
process.
A
C
You
know
on
this.
One
I
think
what's
blocking
is
an
understanding
of
there's.
This
really
weird
thing
with
the
contributor
covenant
where
they
have
two
versions
of
2.0
has
two
different
versions,
and
I
I
think
that's
what's
causing
so
much.
Mayhem
really
is
because
we
can't
agree
on
what's
the
real,
the
one
we
should,
we
should
agree
as
being
2.0
and
so
whether
changes
that
we're
making
are
changes
to
2.4
or
they're,
actually
just
relying
on
the
older
version
of
2.0.
So
I
think
that's
kind
of
what's
causing
all
the
problems.
C
I
think
we
had
maybe
yes,
I
think
that
was
what
we
had
decided,
but
we
do.
You
know
2
2.1,
but
like
from
an
unclear
2.0,
that's
what
the
problem
is.
A
We've
had
some
work
sessions
around
things
sort
of
like
this.
The
last
one
was
more
of
like
an
overall
strategy
session,
but
yeah.
We
talked
about
this
and
I
thought
the
the
agreement
was
that
we
would
use
2.1
the
latest
version
and
we
would
peg
it
to
a
commit
so
that
we
knew
the
specific
version
that
we
were
using
and
then
any
changes
we
wanted
to
make
to
it.
C
So
so
this
is
not
my
understanding
of
what
had
been
decided.
Not
in
that
meeting,
though,
so
I
don't
know
so,
yeah
it's
fun
time.
I
I
think
what
needs
to
happen
is
someone
to
actually
propose
a
pull
request.
Was
the
right
changes
in
the
right
order
and
a
process
for
patching
stuff,
because
when
we
talk
about
patching
we
don't
have
a
process
for
it,
so
you
know
yeah
I
mean
I
don't.
C
I
literally
don't
know
what
folks
actually
mean
technically
by
this,
and
I
think
until
we
have
clarity
around
this,
it's
going
to
be
hard
to
move
forward.
E
Is
there
I
mean
the
other
alternative
would
be
instead
of
a
sha.
You
actually
include
the
entire
text
that
you're
copying
from,
but
that
seems
un
like
not,
it
doesn't
seem
like
it
adds
value.
It
just
adds.
Some
you
know
means
that
you
can
review
it
directly
but,
like
I
don't
know
that
it
seems
like
one
of
those.
Two
choices
would
be
pretty
uncontroversial.
E
An
established
way
to
do
this,
it's
just
like,
I
think
it's
a
relatively
trivial
tool:
script
to
write
using
git,
because
git
can
like
you,
would
fetch
the
the
con
the
file
from
the
sha
with
git,
and
then
you
would
apply
the
patch
file
with
git
and
then
you'd
commit
the
result.
So
it's
like
three
git
commands
or
something
but
like
you
did,
someone
would
have
to
write
that
script.
Yeah
for
sure,
okay,.
A
A
So
I
don't
know
I'm
thinking
like.
Should
we
have
an
issue
that
kind
of
lays
out
what
our
path
forward
is
here
and-
and
you
know
asking
for
a
new
pull
request
and
get
rid
of
this.
You
know
old
one
once
we
do
and
and
and
outline
the
process
at
least
conceptually
like
you're,
describing
jordan,
and
you
kind
of
work
off
of
that.
Instead
of
opening
up
this
pr,
every
time
and
saying
what
are
we
doing
here,
it's
driving
me
crazy.
A
E
C
Sounds
great
jordan,
you
have
a
pointer
by
any
chance
and
how
this
is
typically
done.
E
E
Done
I'm
just
guessing
out
loud
on
how
it
could
be
done,
so
I
I
would
be
happy
to
if
someone
files
the
issue
I'll,
be
happy
to
clarify
any
like
the
conceptual
steps.
As
you
know,
and
if
I'm
ambitious
enough
I'll
throw
in
some
potential
git
commands,
we
can
go
from
there.
A
E
A
Great
all
right,
I'm
going
to
move
on
for
the
sake
of
time,
I'm
not
sure
why
I
even
opened
this
but
issue
826
focus
on
javascript
security
at
openjs.
A
This
is
kind
of
stalled
on
me
and
I
honestly
don't
know
if
I'll
get
to
it
over
the
next
well
in
two
weeks
I
might
have
some
time
to
work
on
this,
but
because
I'll
be
homeless.
At
that
point,
so
I
should
have
planned.
B
A
Yes,
we
do,
and
that's
my
last
comment
too
from
two
weeks
ago-
is
that
you
know
we
need
to
make
a
repo,
but
we
basically
don't
want
to
empty
repo.
I
guess
one
thing
we
did
talk
about
was
alternating
a
security
meeting
opposite
the
standards
meeting,
so
one
week
would
be
standards
in
that
same
same
time,
slot
we
would
do
a
security
meeting.
A
Excuse
me
so
maybe
I'll
drop
that
in
this
issue
as
a
proposal.
But
again
I.
B
No,
that's.
Okay.
I
think
summer
is
probably
hard
for
a
lot
of
folks.
I
did.
There
are
a
couple
of
folks
who
I
met
at
open
source
summit
who
are
interested
in
participating.
So
once
we
get
organized
and
have
some
time
to
dig
in
you
know,
then
we
can
reach
out
to
those
folks,
and
but
I
do
like
the
idea,
do
you
want
to
start
in?
Do
you
want
to
start
in
august
or
yeah.
A
Or
I'm
looking
at
the
calendar,
the
19th
is,
you
know,
would
be
the
next
open
slot.
If
we're
talking
about
the
alternating
with
the
standards,
meaning
and-
and
I
might
be
able
to
do
something
by
then,
but
I
suppose
it
would
to
be
to
have
it
kick
off
well,
it
might
be
good
to
just
do
it
on
august,
2nd,
that's
what
I
I
suggest
we
start
on
august
2nd.
A
Does
that
seem
good
cool
all
right?
Where
is
that
issue
once
you
jump
away,
then
you
can't
find
it
again
here
it
is.
So
let
me
just
make
a
note
really
quickly
we're
just
meeting
on
august
2nd,
and
I
will
come
back
and
finish
that,
after
the
meeting
great
so
moving
on
the
next
one
is
license
check.
Support
tooling,
I
presume
there's
nothing
new
here.
A
Understandable,
I
know,
there's
been
a
lot
a
lot
going
on
there
and
then
another
one
of
the
favorites
clarify
requirements
around
coc
violation.
This
is
issue
786.
I
don't
think
there's
anything
new
here.
I
know
it's
something.
We've
been
wanting
to
further
flesh
out,
so
I
feel
like
we
should
probably
use
a
working
session
on
this
soon.
However,
I
I
probably
won't
have.
B
A
Okay-
okay,
great
that's
the
agent
under
the
agenda.
We
typically
decide
what
we
want
to
do
next
working
session
and
then
we
can
call
it
a
wrap
and
jump
into
a
quick
private
session.
A
I
won't
be
here
for
the
working
sessions,
so
I
don't
know
what
you
all
want
to
do.
A
Not
that
we
don't
have
lots
to
do,
but
we
can
skip
too.
A
And
I'm
that
sounds
like
a
skip.
We
can
mention
it
in
the
slack
channel
if
we
want
to
see
if
anybody
else
is
wanting
to
do
something,
but
otherwise.
A
We'll
maybe
pass
next
week
all
right.
B
So
yeah
we
probably
need
a
short
private
session
should
we
say
farewell
on
youtube
and
and
just
let's
do
it.