►
From YouTube: CHAOSS Weekly Community Call 7-13-21
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
Everyone
welcome
welcome
to
the
july
13th
edition
of
the
weekly
community
call
for
chaos.
I'm
elizabeth,
I'm
the
community
manager
here.
So
I'm
very
happy
to
see
you
all.
I
don't
think
we
have
anybody
new
in
the
call
looks
like
it's
mostly,
the
usual
suspect,
so
welcome
happy
to
see
everybody
thanks
for
taking
time
to
hang
out
with
us
for
this
hour
or
half
an
hour
in
some
cases,
so
yeah,
let's
get
right
into
it.
B
We
posted
the
meeting
minute
here
and
if
you
have
not
added
your
name
yet-
and
you
would
like
to
do
that,
please
feel
free
to
do
so
and
also
tell
us
one
good
thing
or
two
good
things.
However,
many
good
things
you
want
to
tell
us
about
that
are
going
on
in
your
life
recently
that'd
be
great.
We
would
love
to
see
that
we
have
a
few
things
on
our
agenda
today.
B
It
looks
like
most
of
the
things
are
from
previous
meetings
and
such
and
and
old
topics,
but
we
did
have
a
few
announcements
that
we
wanted
to
make
real
quick
for
everybody.
The
first
one
is
that
we
meant
to
put
this
in
the
newsletter.
It
was
my
bed,
I
didn't
get
it
in
there.
The
grace
hopper,
open
source
day
is
happening
this
week
and
sean
is
going
to
be
representing
chaos
with
the
auger
project
and
that's
happening
on
thursday.
B
So
thank
you
sean
for
doing
that,
and
do
you
have
anything
you
want
to
say
about
that
or
add.
I
know
we've
done
these
in
the
past,
but
there's
something
you
want
to
add.
Yeah.
C
This
is
bittergea
and
auger
both
did
it
in
the
fall,
and
I
think
we
both
encountered
some
challenges
with
the
virtual
environment,
and
so
this
is
kind
of
an
experiment
to
see
how
the
virtual
grace
hopper
goes
and
they're
actually
doing
two
of
these
open
source
days
virtually
this
year,
one
this
month
and
then
one
in
october,
so
there's
still
an
opportunity
for
other
parts
of
chaos
to
participate
in
the
fall
version.
C
D
Yeah
that
that
would
be
great
they
had
reached
out
to
some
folks
individually
about
helping
to
run
an
open
source
hackathon
at
the
october
one.
So
I
didn't
I
was
I'd,
be
curious
to
know
how
we're
engaging
as
chaos
in
terms
of
what
the
presence
actually
looks
like,
but
I
didn't
sign
up
for
that,
but
I'm
not
opposed
to
participating
in
being
grace
hopper.
I
was
actually
just
talking
about
it
today.
So
if
there's
another
way
to
to
work
in
it
that
I
don't
that's
not,
I
know.
C
Yeah,
if
you
don't
mind
if
and
if
there's
anyone
else
interested,
what
I
can
do
is
just
pass
your
contact
info
along
to
the
people
that
we've
been
working
with
to
have
them
maybe
reach
out
to
you
individually.
I
really
do
think
they're
still
figuring
out
the
virtual
part,
and
I
think
we
all
are
but
like
a
virtual
hackathon,
is
a
tricky
thing
with
when
nobody
knows
anybody
and.
D
B
C
B
Awesome:
okay.
The
second
thing
is
that
so
that's
happening
on
thursday
and
then
on
friday
we
are
going
to,
I
think,
be
migrating
our
website
to
our
new
hosting
company,
which
the
website
itself
will
look
the
same,
but
on
the
back
end,
does
where
all
of
the
improvements
and
we'll
have
a
lot
more
functionality
and
a
lot
more
control
over
what
we
can
install
the
plugins
and
and
things
like
that
so
kevin.
E
Actually
so
the
the
switch
is
actually
going
to
happen
on
wednesday,
the
linux
foundation.
Iet
support
rightfully
pointed
out
that
making
a
switch
like
that
on
a
friday
is
a
bad
idea.
Yeah.
C
That
was
a
really
good,
really
good
insight
on
their
part
yep
not
having
deployed
new
websites
in
a
really
long
time.
E
C
I
was
just
gonna
say
kevin
and
I
would
really
like
it
if
a
couple
people
could
just
click
through
chaos.info
and
see
if
you
find
anything
that
breaks
that
that
doesn't
seem
to
break
on
regular
chaos
stock
community,
I
don't
think
anything
should
break
on
either
side,
but
you
know
we've
tested
it,
but
we
are
limited
in
what
we
can
test.
So
if
anybody
else
has
a
minute,
just
go
click
around
and
identify
if
there's
anything
broken
that
we're
not
aware
of
that,
would
be
very
helpful.
F
To
take
other
pages
or
I'll
just
post
in
the
in
the
channel,
thank.
E
The
the
website
repo
issue
would
be
the
that
would
be
ideal
that
way
if
it's
a
if
it's
a
feature,
improvement
or
a
bug
that
will
be
that
can
be
addressed
after
the
migration,
I'm
I'm
starting
to
make
a
list
of
those.
So,
additionally,
we're
going
to
be
following
the
website
migration.
We
are
going
to
be
doing
a
an
accessibility
audit
on
the
website.
E
So
so,
following
the
migration,
we
will
be
looking
at
making
improvements,
so
feel
free
to
mention
improvements
or
make
feature
requests
on
the
the
site.
Additionally,
we've
reset
all
of
the
admin
and
editor
access
for
the
new
site.
So
if
you
would
like
some
sort
of
access
to
the
site,
perhaps
we
should
collect
names
for
that
admin.
Access,
editor
access,
blog
access,
I'm
not
sure
how
we
want
to
assign
permissions,
but
I'm
certainly
open
to
having
more
people
with
with
access
to
the
site.
B
I
also
wanted
to
give
a
shout
out
to
matt
g
and
matt.
Now,
I'm
sorry
matt
cantu
for
they're
also
their
work
on
this
team,
because
I
know
it's
been
a
a
group
effort.
Kevin's
lead,
kevin
and
sean
are
leading,
but
yeah.
So
thank
you
to
all
of
you
and
thank
you
to
lucas
for
volunteering
to
help
test
and
do
a
qa
pass.
B
B
E
A
github
issue
is
the
best
way.
However,
a
slack
message
I
will.
I
will
certainly
respond.
Two
and
honestly,
a
slack
message
actually
might
be
faster,
but
but
again
issue
would
be
the
the
preferred
method.
B
Let's
see,
okay,
the
next
thing
on
our
list
is
to
let
you
all
know
that
we
are
hosting
another
of
our
auger
workshops
on
saturday
july
17th.
So,
if
you're
interested
in
that,
I
should
have
posted
the
registration
link.
I
did
not
do
that,
but
I
will
do
that
if
I
can
do
more
than
one
thing
at
one
time,
which
would
be
amazing
if
I
could,
but
I
can't
so
if.
B
That
handy
wants
to
do
that.
Fine,
if
not
I'll,
do
it
after
meeting,
but
that
is
happening
on
saturday
morning
for
us
central
chicago
time
and
that
will
be
sean
again
hosting
that
so
sean
has
a
very
busy
week
this
week.
Thank
you,
sean
for
being
awesome.
C
How
are
those
going
john
in
terms
of
we
get
about
anywhere
from
two
to
five
people,
and
this
is
the
summer,
so
I'm
expecting
less
participation,
but
I
could
be
surprised.
C
C
B
B
I
will
just
also
say
that
our
gsoc
students
as
usual,
are
just
absolutely
amazing
and
we're
really
really
thankful
for
all
of
them
and
you're
all
doing
a
really
really
great
job.
It's
it's
mind-blowing
how
much
work
gets
done.
So.
Thank
you
guys.
Thank
you
all
for
doing
such
a
good
job.
If
you're
missing
the
updates,
they
usually
end
up
in
the
newsletter
or
on
slack
or
in
the
mailing
list.
So
that's
where
those
happen.
B
If
you're,
not,
if
you're
not
participating
in
any
of
those
places,
then
you
should
be
no
I'm
just
kidding.
Do
we
want
to
take
a
minute
and
let
I
see
josh
andrew
both
are
here
on
the
call
just
let
them
give
a
quick.
You
know
30
second
update
of
how
it's
going.
How
about?
Let's?
Do
that
real,
quick
josh?
Do
you
want
to
go?
First
sorry.
G
J
J
E
J
J
B
Okay,
perfect!
Thank
you.
If
you
missed
it,
the
doc
is
in
the
chat,
the
zoom
chat
for
anyone
who
is
who
missed
that
it's
right
there
that
josh
just
posted.
K
K
But,
okay,
sorry
it's!
It
was
my
microphone,
so
we
just
finished
implementing
scorecard
it
took
longer
than
I
expected.
I
thought
I'll
just
do
it
in
a
week
or
so,
but
well
bugs,
and
now
I'm
building
a
new
worker
for
libya
to
which
would
calculate
dependency
freshness.
So
it's!
It's
really
amazing,
because
you
know
having
having
getting
an
opportunity
to
build
a
worker
from
scratch
is,
is
just
amazing.
A
K
A
lot
of
projects,
so
we
have
different
versions
of
dependencies
like
flask
1.1.1
someone
would
be
using
and
it
might
have
a
vulnerability
which
would
I
basically
it's
a
vulnerability
that
extends
to
a
project.
So
it's
always
a
good
idea
to
keep
them
updated.
K
So
it
just
measures
that
you
know
gets
to
the
package.
Files
looks
at
your
dependency
versions
and
then
you
know
let
you
know
that
you
might
be
behind.
You
must
update
that's.
B
Awesome:
okay,
that
makes
sense
any
questions
for
josh
or.
B
Drove
all
right
we
will
go
on,
then
that
was
a
little
sidetrack
of
announcements,
but
it's
kind
of
announcements.
Status
updates
are
also
announcements.
I
guess
okay,
so
the
next
one
is
that
the
chaos
slack
is
now
the
free
version.
We
did
talk
about
this
a
little
bit
last
week,
actually
quite
quite
a
bit
last
week,
and
we
decided
that
the
the
free
version
of
slack
was
going
to
be
just
fine
for
our
needs
for
now,
so
that
has
now
happened.
B
So
if
anybody
sees
those
little
messages
popping
up,
we
know
about
that
and
it's
a
deliberate,
purposeful
choice.
So
so
don't
worry
about
it.
It's
okay,
it's
all
good
and
in
the
future.
If
we
find
that
it's
not
serving
our
needs
any
longer,
then
we
will
talk
about
payment
and
upgrading,
but
for
now
we're
good
last
minute.
Questions
on
that.
B
All
right
rock
on
moving
forward.
I
love
it.
So
we
had
a
few
action
items
from
previous
meetings
and
this
has
been
a
couple
of
meetings
ago.
So,
if
we
haven't
talked
about,
if
you
don't
remember
totally
fine,
we
can,
you
know
bring
it
up
again
next
week,
but
the
first
one
is
data
ethics
considerations.
B
We've
been
talking
about
adding
something
to
our
template,
our
pr
template-
and
I
know
that,
like
the
the
automation
and
the
website,
migration
kind
of
is
putting
a
little
wrench
in
that
in
that
so
and
that
may
wait.
If
I'm
not
mistaken,
I
believe
that's
what
we
were
talking
about
kevin,
but
you
can
update
us
on
that.
If,
if
that's,
okay,
yeah.
E
So
actually,
in
the,
I
believe,
it's
in
the
in
the
metrics
repo
we've
been
having
a
discussion
in
the
interview
or
in
the
in
the
issues
about
adding
both
the
a
data,
ethics,
disclaimer
and,
and
also
a
dei
disclaimer
to
the
metrics
template.
E
And
where
were
where
were
where
the
discussion
is
at
right
now,
and
it
is,
I
think,
it's
an
ongoing
conversation
but
where,
where
the
discussion
is
at
right
now
is
kind
of
leaning
towards
keeping
the
metrics
templates
simple
and
moving
moving.
Those
disclaimers
to
the
the
website
page
where
we
display
the
the
metrics
in
general.
E
So
there
already
is
a
data
ethics
disclaimer
there,
but
so
the
there's
a
talk
of
kind
of
editing
that
a
little
bit
possibly
linking
out
to
a
larger
data
ethics
document
and
also
possibly
adding
a
a
dei
disclaimer
to
the
metrics
as
well.
C
Yeah
disclaimer
is
probably
I
mean
it's
yeah
they're,
both,
I
think
more
at
the
other,
the
ei
one
is
pragmatic
application
and
I
think
the
data
one
is
a
value
statement
like
where
we,
what
we're
trying
to
accomplish
and
how
we're
working
to
respect
people's
privacy
with
the
data.
E
I
I've,
I
understood
it
as
two
separate
things.
One
is
kind
of
a
use
case
for
dei,
so
dei
can
dei
can
inform
the
use
case
for
most
of
the
metrics
that
we
have,
but
where
the
where
the
disclaimer
comes
in,
is
that
most
metrics
have
some
have
some
connection
to
dei
right.
So
it's
important
in
the
in
the
use
of
metrics
it's
important
to
consider
to
consider
dei
issues.
So
I
believe
that
does
need
to
be.
E
G
E
Those
are
two
kind
of
separate
issues
we
could.
We
can
provide
some
guidance
on
use
cases
for
the
objective
section
in
the
metrics
template,
but
but
I
do
think
we
do
need
some
sort
of
dei
disclaimer
as
well
and
but
not
on
the
metrics
template
that
would
be
more
on
the
metrics
release
page.
E
I
think
the
last
the
last
two
comments,
the
last
two
comments
in
that
issue,
or
maybe
the
last
three
comments
in
that
issue
by
myself
and
landed
in
that
in
that
area.
Okay,
so
the
it's
not
yeah,
we're
not
talking
about
the
disclaimer
anymore.
We're
now
talking
about
guidance
in
the
objective
section,
specifically
in
the
objective
section
of
the
template
to
address
dei
use
cases.
E
So,
but
I
think
we,
the
where
we
were
where
we
were
talking,
was
not
about
adding
another
header,
it's
more
about
just
providing
guidance
on
hey.
Please
consider
dei
in
your
use
cases
when
you
are
writing
the
objectives
for
this
metric
and
york
is
here,
so
he
can
either
say.
Yes,
that's
what
we
talked
about
or
no,
we
were
having
a
completely
different
discussion.
Kevin.
E
Yeah,
the
the
metrics
template,
pull
request.
E
But
so
going
back
to
the
the
issue
that
started
this,
adding
a
metrics
disclaimer
to
the
metrics
template
or
adding
an
ethics
disclaimer
to
the
template
may
just
create
a
replication
and
redundancy
that
we
don't
need
if
we're
trying
to
make
these
metrics
templates
as
simple
as
possible.
So
the
I
think
where
we're
at
right
now
is
we.
We
believe
that
the
ethics
disclaimer
is
better
served
on
the
metrics
release
page,
and
perhaps
we
can
link
out
to
a
a
larger
metrics
document
or
a
larger
ethics
document
from.
G
B
B
But
if
nobody
else
has
anything
on
this,
we
can
move
forward
if
that's
okay,
so
the
next
kind
of
piece
of
that
was
that
sophia
had
brought
her
information
from
a
talk
that
she
did
with
a
few
others
who
were
also
in
the
chaos
project
and
other
places.
She
brought
that
to
us
last
week
at
the
very
tail
end,
and
so
we
were
going
to
have
a
look
at
that
and
give
thoughts
back
to
her.
I
don't
know
if
anybody's
had
a
chance
to
do
that,
but
we
had
also
talked
about.
B
D
I
mean
I
like
that
idea
in
general.
I
think
this
is
a
big
topic,
so
just
putting
a
little
like,
oh
by
the
way,
you
should
consider
this
and
then
not
saying
too
much
after
that,
like.
I
think
we
have
a
an
opportunity
to
make
a
statement,
or
at
least
just
to
like
contribute
to
the
conversation,
because
I
think
it's
very
large
and
comprehensive.
So
I
I
am
a
fan
of
we
could
start
it
as
a
blog
post.
D
It
could
become
a
doc
as
as
kevin
mentioned
on
on
somewhere
on
the
the
releasing
page
or
guidance
around
metrics
usage.
We
can
figure
out
where
that
lives
later,
but
I
think
a
blog
is
a
great
place
to
start
or
you
could
start
it
as
a
conversation
either
way.
I
just
want
to
share
this
this
doc,
as
elizabeth
mentioned,
just
as
we've,
we
had
this
as
a
a
mosfest
discussion
last
year,
so
essentially
we
prompted
it
with
just
who
we
were.
D
It
was
myself
daniel
from
petergia
and
then
another
googler,
just
talking
about
three
different
personas
that
interact
with
this
kind
of
data
and
sort
of
the
ethical
challenges
that
we
face.
As
say,
the
community
manager
or
contributor
the
the
aggregator
or
platform,
and
then
me
as
the
the
controller
and
maintainer
of
that
amassed
data
and
what
are
the
responsibilities
to
each
individual
party
kind
of
prefacing
it
with
what
how
these
things
could
be
used
in
both
corporate
and
community
context
and
then
starting
to
pose
questions
and
considerations
for
all
those
parties.
D
Slash
acknowledging
that
they
are
more
more
people
involved
in
their
chain.
So
I
wanted
to
share
the
deck
just
as
what
we
had
started
to
outline
in
terms
of
some
of
those
divisions.
Personas
questions,
ethical
ambiguities,
because
we're
not
talking
about
owned
stuff.
I
think
once
once
you're.
This
is
a
recorded
thing,
so
I'll
be
careful
about
how
I
say
this,
but
in
terms
of
say
some
companies
like.
D
Included
when
you
amass
and
create
a
data
set,
you
can
license
it
and
license
how
it's
used
and
tools
like
kaggle
that
are
designed
to
share
data
and
resources
like
this.
But
often
this
kind
of
data
is
not
actually
classified
as
anything.
In
fact,
our
we
have
a
public
data
set,
that's
a
mass
collection
of
github
activity
data
and
it's
currently
not
licensed,
and
you
look
at
how
the
lf
is
doing
it.
D
So
I
think
again,
there's
a
lot
of
room
for
just
conversation,
especially
in
the
context
of
the
community
where
you
do
know
these
people,
and
so
you
should
they.
It
should
be
a
conversation,
not
just
a
an
assumption.
So
basically,
I'm
saying
all
of
it
to
say
that
I
love
to
help
to
craft
that
whenever
we
want
to
move
forward
with
it.
D
I
hope
that
we
could
use
some
of
the
the
concepts
and
ideas
here
as
a
way
to
start
ideas
and
ideas
of
where
we
want
to
focus,
but
danielle
we're
talking
on
a
side
channel
about
it
might
make
sense
to
start.
D
I
don't
want
to
start
yet
another
working
group,
but
maybe
some
kind
of
like
little
pilot
project
that
doesn't
necessarily
have
to
be
maintained
as
an
overall
working
group,
but
maybe
it
should
be
part
of
another
one.
So
I'd
be
curious
for
this,
for
the
team
to
think
where,
where
does
it
make
the
most
sense
for
a
work
like
this
to
be
done
in
the
project.
M
I
would
recommend
this
to
be
part
of
common
working
group
because,
like
in
common,
we
have
it.
There
is
nothing
which
is
usable
for
everyone
and
serves
the
entire
community
and
doesn't
pretend
on
any
working
group.
We
discuss
those
things
in
the,
so
I
would
propose
bringing
this
to
the
common
working
group
and
we
can
discuss
it
or
maybe
we
don't
create
a
metric,
but
it's
a
big
thing
that
is
ongoing
and
it
can
support
others
too.
So
that
is
why
I
said
yes.
H
D
I
think
it's
both
like,
I
think,
like
in
my
context,
I'm
coming
at
it
from
a
company
where
there
are
very
stringent
restrictions
and
regulations
for
how
I
use
store
and
interact
with
data,
but
in
a
community
there
isn't
any
of
that.
So
it's
more
to
help
people
understand
what
guidelines
they
should
draw
for
themselves
in
terms
of
using
the
data
responsibly
and
it's
they
have
the
opportunity
to
build
their
own
culture
and
assumption
around
how
data
around
their
own
projects
are
created.
D
D
I
don't
necessarily
think
that
whatever
we
propose
will
become
the
de
facto
standard,
it's
more
to
just
help
to
encourage
standards
here
or
at
least
standard
practices
that
say
you
as
a
community
leader,
have
some
sort
of
statement
around
how
you
plan
to
handle
data
like
this
or
just
one.
I
guess
this
is
about
why
you
should
care
more
than
how
you
should
do
it,
so
I'm
assuming
we
start
with
the
y
and
then
the
how
and
then
the
how
is
could
be.
D
We
worked
on
our
own
sort
of
data
usage
statement
and
that
could
be
an
example
of
like
well.
Chaos
has
had
felt
strongly
about
being
transparent
around
how
we
use
data
and
how
we
collect
data
and
maintain
it
and
maintain
the
integrity
of
it
and
security
of
it.
This
is
our
statement
and
that's
sort
of
beginning
the
conversation
of
like.
How
might
you
do
this.
H
So
I
I
like
this
a
lot
and
I
like
george's
suggestion
of
maybe
five
to
ten
minutes.
I
think
you're
in
the
weekly
call
gear,
because
I
think
this
certainly
covers
more
than
it
covers
all
working
groups.
I
think
and
listening
to
you
talk
sophia,
like,
I
think,
there's
questions
that
can
be
asked
about
how
you
would
use
data
that
is
otherwise.
You
know
not
data
that
you
generated,
but
also
trying
to
help
provide
guidance
for
people
who
are
looking
to
use
the
data
that
you
do
generate.
H
G
H
From
our
community
might
be
an
interesting
statement,
but
I
don't
know
like
if
that
is
superseded
by
like
if
we
do
all
of
our
work
on
github,
for
example,
like
it
doesn't
matter
what
we
say,
it
falls
to
the
github
policy
like
if
in
a
community
we
said
we
don't
want
you
to
analyze
our
data
period.
H
D
I
mean
also,
I
guess,
we're
part
of
the
lf,
so
the
lf
has
a
public
statement
that
they
have
more
restrictions
around
the
use
of
telemetry
data,
but
contribution
data.
They
consider
to
be
entirely
public.
So
with
the
lf
insights
dashboards,
they
have,
they
have
people's
names
explicitly
listed
and
next
to
their
contribution
levels,
and
they
view
that
as
entirely
public
data
and
that's
a
stance
that
the
lf
has
taken.
I've
seen
other
organizations
haven't
said
anything
at
all.
D
So
that's
the
starting
place,
but
then
also
they
choose
to
say
that
telemetry
data
is
more,
has
more
restrictions
around
how
you
use
it
and
how
you
publish
back
to
it,
and
so
they
they've
made
that
statement
in
regards
to
data
around
lf
projects.
So
that's
the
one
example
where
we
can
look
at
in
terms
of
how
the
lf
is
treating
this.
B
I,
like
it
a
lot
too,
and
I
think
that
we
can
use
you
know
a
few
minutes
of
this
call
to
do
like
a
little
working
session
just
like
how
we
develop
our
metrics.
We
just
have
a
doc
and
we
all
jump
in
and
and
add
our
our
comments.
So
I
don't
know
if
someone
wants
to
start
that
doc
and
we
can
even
you
know
next
week
could
be
the
first
time
that
we
take
five
minutes
to
do
that
if
everyone's
okay,
with
that
that's
cool,
any
strong
feelings
against
that.
H
B
H
Topics
that
kind
of
like
hits
all
corners
of
the
chaos
project
and
the
most
sensible
place
for
it
would
be
to
have
it
here.
B
B
That's
probably
already
done
right
he's
still
on
top
of
things.
Oh
man,
I
I
should
I
should
be
so
so
amazing
and
be
on
top
of
things
like
I
just
yeah.
I
don't
think
that's
ever
gonna
happen,
but
I
can
strive
reach
for
the
stars.
Okay,
thank
you,
georg,
and
thank
you
sophia.
I
really
appreciate
your
insights
with
all
of
this
so
much
great
stuff
to
add
I
just
I
love
it.
H
B
Awesome,
thank
you
matt,
amazing,
so,
productive
today
I
can't
even
stand
it.
This
is
so
great.
Okay,
we're
gonna
move
forward
because
we
only
have
10
minutes
and
we
do
have
a
few
other
things
to
talk
about.
So,
let's
hop
along
to
the
next
thing.
The
next
one
is.
We
want
to
talk
a
little
bit
about
zoom
security.
We
have
not
had
any
issues
since
the
one
day,
thankfully,
but
there
had
been
concerns
in
the
past
that
you
know
if
no
one's
in
the
zoom
channel.
B
How
do
we
know
that
someone's
not
using
it
while
we're
not
there?
So
that
has
been
a
concern
and
the
other
concern
is
for
the
office
hours
of
giving
people
the
opportunity
who
are
hosting
to
have
that
administrative
control,
which
I
think
we
solved
that
piece
that
I
can.
I
give
those
credentials
to
if
you're
hosting
office
hours
I
can
give
you
the
credentials.
B
So
that
way
you
do
have
control
and
and
maxie
did
the
office
hours
on
monday,
and
he
said
there
weren't
any
problems,
so
it
that
could
have
just
been
a
one-off
time
lucky
youvenad
for
having
to
deal
with
that.
But
so
I
guess
that
it
goes
back
to
what
we
want
to
do
and
I
think
matt.
So
you
said
you
were
going
to
look
into
some
security
options
that
we
might
have
from
zoom.
N
Yeah,
I
I
got
most
of
this
information
actually
off
of
the
zoom
security
pamphlet,
they're,
pretty
comprehensive
with
what
you
can
do
and
my
so
you've
already
covered.
One
of
the
recommendations
is
sharing
credentials
to
trusted
users.
There's
something
I
wanted
to
bring
up
is
that
you've
got
more
opportunities
for
issues
to
arise.
N
If
you
have
more,
people
with
financials
is
generally
how
it
goes,
and
I
was
wondering
if
we
could
start
a
chaos
zoom
for
office
hours
separate
from
the
regular
ones,
so
that
people
can't
log
in
as
kiosk
community
to
the
regular
one
with
their
office
hours,
login
or
whatever
something
I
wanted
to
bring
up.
We
don't
have
to
answer
that
now.
N
The
other
one
was
adding
a
simple
password,
so
something
that
doesn't
take
take
a
lot
of
time
to
put
in
or
yeah
to
the
link,
because
random
zoom
bombing,
I
know,
is
not
necessarily
a
common
issue,
but
it
is
a
consistent
issue.
It
does
happen
like
a
lot
just
like
there's
so
many
zoom
channels
and
so
many
random
numbers
you
can
put
in
that.
That
doesn't
happen
too
often
to
every
group.
So
that's
something
I
wanted
to
bring
up
too.
E
So
our
our
links
are
publicly
posted
all
right,
so
it's
not
a
adding
adding
the
password
at
the
end
of
the
publicly
posted
link,
wouldn't
wouldn't
solve
the
issue.
N
I
just
I
I've
known
that
people
can
put
in
a
random
number
into
zoom
and
occasionally
get
a
channel,
and
the
thing
I'm
wondering
about
is,
I
don't
think,
anybody's
coming
in
to
cause
problems
coming
into
the
kiosk
community
website,
because
that's
pretty
far
removed
from
like
things
you
can
search
on
google
and
find
a
random
zoom
link
if
you
want
to
find
a
zoom
like
the
bomb.
Basically,
I
don't
know
how
they
found
it,
but
I'm
guessing
that
it
came
from
a
random
link.
H
B
B
I
think
we
looked
at
this
when
we
first
set
this
whole
thing
up.
We
moved
it
from
the
uno,
and
that
was
one
of
the
things
that
was
kind
of
a
pain,
but
they
do
pay
for
it.
Like
elf
pays
for
it,
so
I
mean
the
other
option
would
be
us
to
pay
for
it
ourselves.
C
N
So
something
also
I
have
in
mind
is
that
preventative
measures
are
kind
of
limited
to
assume
whether
or
not
you
have
the
access
to
the
main
account.
But
I
think
guidelines
are
also
important
here.
It
might
be.
It
would
be
really
important
to
have
not
necessarily
a
pamphlet
that
you
give
to
people
that
say
this
is
how
you
do
it,
but
at
least
some
kind
of
something
on
the
handbook
or
something
that
says
this
is
the
easiest
way
to
mute.
N
Someone,
because
there's
a
few
different
ways
and
then
like
how
to
you
might
want
to
have
people
turn
off
them.
The
video
for
participants,
unless
someone's
in
the
meeting
with
them,
so
they
can't
just
go
in
and
play
somewhere
in
the
video.
That's.
These
are
just
kind
of
things
that
you
can
do
it's
really
hard
when
you
have
a
lot
of
people
in
a
meeting,
but
when
you
have
an
office
hours,
it's
a
lot
easier.
B
B
And
we'll
keep
poking
around,
I
think
vanad.
Also
in
a
conversation
he
and
I
had
mentioned
something
about
there's
a
way.
Apparently
you
can
only
keep
a
zoom
channel
open
during
certain
hours
and
if
it's
outside
of
those
hours,
then
you
can
open
it,
but
like
someone
would
have
to
request
permission.
So
if
we
kept,
you
know
like
here's,
here's
this
block
of
time
that
is
open
for
whoever
in
the
community
wants
to
use
the
channel
anything
outside
of
that
you
have
to.
B
You
would
have
to
get
approval
from
us
and
we
will
give
you
like
the
the
ability
to
open
it
up.
Something
like
that.
So
that
might
be
an
option
too.
I
don't
know
if
we
have
that
that
option,
since
we
are
kind
of
limited
on
our
zoom,
but
we
can
also
maybe
look
into
that
as
a
way
to
keep
people
from
abusing
the
zoom
channel
while
we're
not
around.
B
H
D
G
H
Community
of
many
interests
yeah,
I'm
not
terribly
concerned
about,
like
any
of
those
things.
To
be
honest
with
you,
you
know,
as
long
as
when
we're
having
meetings,
there's
always
a
host,
but
if
somebody's
zoom
bombing
we
can
kick
people
out
which
we
always
seem
to
have.
That
seems
to
be
the
biggest
thing
right
now.
O
Yeah
hi
it's
ildico.
Here
I
mean
if
it
really
is
a
concern.
I
think
there
is
a
setting
that
says
that
zoom
will
not
allow
people
to
join
without
a
host,
but
then
you
have
to
make
sure
that
there
is
someone
with
host
privileges
on
every
community
related
call
that
is
supposed
to
happen
so
that
can
be
challenging.
I
do
manage
a
zoom
account
for
a
community
and
honestly
dealing
with
the
modifications
and
stuff
sometimes
is
more
complicated
than
just
letting
these.
I
don't
know.
O
Hopefully,
accidents
happen
every
now
and
then,
unless
someone
is
abusing
to
the
account
to
the
extent
where
the
recordings
in
the
cloud
just
grow
in
above
a
certain
limit,
that's
definitely
something
to
worry
about.
I
personally
never
really
had
that
problem
before
with
that
other
community
zoom
account
when
it
comes
to
zoom
bombing.
O
Never
ever
let
anyone
to
post
the
link
on
any
social
media
account,
because
then
you
will
get
so
many
bombers
that
you
practically
have
to
shut
down
that
bridge.
For
for
that
hour
or
meeting,
we
did
have
that
experience
once
or
twice
when
someone
forgot
that
social
media
is
not
for
zoom
links
to
to
share
those.
O
So
I
think,
if,
if
we
have
that
guideline,
that
kind
of
just
tells
about
all
this,
that
that
should
help
when
we
have
an
online
event
where
we
are
using
zoom,
we
kind
of
try
to
make
sure
that
we
have
like
redirects
for
the
links
and
just
something
that
doesn't
point
directly
to
the
the
zoom
bridge
with
the
password
and
just
again
not
putting
anything
on
social
media
if
you
have
kind
of
a
step
that
people
have
to
take
like.
O
Oh,
this
is
where
you
find
info,
and
then
they
have
to
go
there
and
click
on
a
button
or
something
that
the
zoom
bombers
usually
don't
really
get
that
far.
I
think
it's
kind
of
not
how
they
do
this.
If
they
see
something
directly,
then
they
take
it.
If
they
have
to
click
on
links
and
buttons
and
stuff,
then
then
they
will
not.
O
So
if
it's
like
embedded
and
a
meeting
invite
in
a
button
in
the
google
doc
that
we
have,
I
think
that
should
be
good
enough
to
hide
it
in
in
our
experience.
But
again,
these
are
just
kind
of
what
we
tried
to
do
so
far,
so
yeah,
plus
one
two
or
a
thousand
for
having
guidelines
to
make
sure
that
anyone
who's
running
a
zoom
call
knows
all
the
best
practices
and
then
fingers
crossed
that
it
will
be
sufficient
enough.
B
B
We
are
oh
we're
at
the
end
of
time,
and
we
had
two
discussions
from
previous
meetings
that
we
did
not
get
along
or
get
to
so
we
will
bump
those
up
to
the
very
first
thing
that
we
talk
about
next
week.
If
those,
if
one
of
those
things
are
your
things,
I'm
so
sorry
we
did
not
get
to
them
will
get
to
them.
First.
Next
time,
chaos.