►
From YouTube: Sigstore Community Meeting - Sept. 20, 2022
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).
A
C
I've
been
on
PTO
the
last
few
days,
but
I
can
I
make
a
poor
man's
attempt
at
it,
and
the
game
be
corrected.
If
my
information's
out
of
date,
I
know,
we've
been
trying
to
push
towards
the
definition
of
the
1.0
release
of
recore,
we
have
a
couple
PRS
that
have
been
going
in
to
help
clarify
API
status,
as
well
as
some
bug
fixes
that
have
gone
in
I
believe,
but
that
that's
the
definition
and
burn
down
at
one
point.
A
B
Yeah
yeah
I'm
gonna
be
incredibly
unhelpful
and
say:
there's
a
bug
and
I
would
like
it
fixed
and
I
have
no
idea
how
to
fix
it,
but
it
seems
like
possibly
one
of
the
recent
record
releases
is
resulting
in
cosine
signatures
flaking
out
intermittently.
It's
enough
that
a
couple
Downstream
open
source
projects
have
seen
it,
including
salsa
framework.
We've
seen
it
internally
at
chain
guard
and
so
I
would
love
to
help.
B
I
just
have
no
idea
how,
but
basically
I
just
want
to
call
this
out
and
because
it
seems
maybe
maybe
worth
worth
prioritizing,
and
so
if
I
can
have
assistance
in
prioritizing
it
and
again
I'm
happy
to
help
dig
into
it.
Though
I
don't
know
that
I
have
the
context.
D
I'm
thinking,
probably
Astra,
and
maybe
myself
and
if
you're
interested
we
can
start
trying
to
chase
this
down,
and
if
anybody
else
has
expertise
in
this
and
wants
to
I
mean
the
the
process
for
chasing
on
the
last
one
was
long
and
of
course
you
know
when
we
see
it
we're
like.
Oh
but
I,
don't
know
if
it's
it's
something
similar.
D
You
know
I'm
trying
to
think
about
things
that
have
I
think
the
first
thing
would
probably
be
to
look
at
what's
gone
out
in
record.
Recently.
That's
touched
inclusion
proofs,
so
they
can
set
up
some
time
saying
try
to
do
a
little
bit
of
group
chasing
down
bug
great.
B
B
The
way
the
one
you
filed
about
recore
flakes.
E
I'll
have
some
time
at
the
end
of
the
week
to
look
at
it.
It's
likely
probably
I
I'm,
not
clear
what
version
of
Rico
was
writing
at
the
time.
So
I
don't
even
know
if
the
fix
for
this
that
it
was
in.
C
B
Got
it
got
it
got
it
cool
yeah,
so
I'm
I'm
happy
as
long
as
as
long
as
y'all
y'all
are
working
on
it
and
I
I
volunteer
myself.
If
you
want
to
wrote
me
in
I,
want
to
avoid
too
many
cooks
but
feel
free
to
to
reach
out.
If,
if
I
would
be
helpful,.
B
D
D
D
An
identity
provider
providing
email
actually
is
giving
us
identities.
It
looks
like
an
email.
The
ladder
should
be
very
quick
to
add
planning,
hopefully
doing
that
this
week
the
tests
there's
a
little
discussion
on.
If
this
is
a
ga
block
or
a
fast
follow,
I'm
going
to
be
approaching
it
as
just
trying
to
get
as
many
tests
in
as
possible,
but
I
think
we're
getting
to
a
fairly
good
State
I
brought
up
in
our
GA
sync
this
week,
we'll
probably
want
to
do
a
release
candidate.
D
Once
we
have
these
in
soonish,
okay,.
D
And
I
think
I,
don't
know
what
was
said
for
record
1.0
because
I
missed
the
beginning,
but
I
think
it's
the
same
thing
here
we'll
we
need
to
decide
how
long
we
want
to
have
a
release
candidate
out.
D
We
definitely
don't
want
to
cut
a
release.
Candidate,
wait
just
a
day
and
then
cut
1.0.
D
I
think
it's
worth
noting:
we
had
a
security
advisory
to
go
out
and
I'm
finding
that
right
now,
it's
paste
feel
free
to
take
a
look
at
this.
Thank
you
to
Asura
and
Cody
for
helping
out
with
getting
the
fixes
in
and
for
that
here
it
is
the
the
tldr.
Is
there
were
a
number
of
verification
issues
with
verified
blob,
and
this
goes
through
each
of
them.
This
also
fixes
an
issue
that
we
described
publicly
around
the
verification
of
expired
certificates.
A
Okay
and
get
sign,
we
have
an
update
here
who
added
that
in
go
ahead.
G
Yeah,
so
just
just
a
small
update
that
this
isn't
specific
to
just
get
signed
because
it
also
affected
cosine,
there's
a
fixed
two,
six
or
six
door
for
fixing
the
out-of-bound
flow.
This
also
is
coupled
with
some
discussion
in
the
six
door,
six
door
issue
about,
since
Google
is
deprecating
out
of
bounds.
Oauth
anyway,
do
we
want
to
just
deprecate
it
entirely
and
just
sort
of
fall
back
to
device
flow
for
oauth.
G
So,
if
you're
interested,
we
should
probably
create
another
issue
in
six
or
six
story
to
discuss
this
more.
But
if
anyone
has
any
hot
takes,
I
would
love
to
hear
them
I'm
generally
in
favor
of
it
I.
Don't
think
it
makes
a
a
huge
difference
for
what
we
want
to
do
as
long
as
we
can
still
authenticate
without
it,
without
a
browser
and
like
a
headless
VMS,
something
like
that
foreign.
D
I
think
that
sounds
good
as
long
as
the
a
browserless
flows
are
still
supported,
and
it
seems
like
device
is
effectively
the
replacement
for
out
of
band
at
this
point.
So.
A
Okay,
moving
on
yeah,
so
clients
our
root
project
say
we
have
an
update
for
six
during
golang.
This
looks
interesting
Zach.
Do
you.
B
Wanna
yeah
less
lesson
update
than
than
a
shower
thought
that
I
wrote
down,
but
one
one
of
the
things
I've
been
noticing
is
is
there's
a
little
bit
of
friction
to
using
Sig
store
as
a
library
and
go,
which
is
a
little
bit
ironic.
Given
that
that's
where
all
the
infrastructure
is-
and
you
know
in
theory
would
be
the
best
implementation,
I
think
that's
actually
related
I
think
you
know
cosine
and
all
the
all
the
other
code
was
kind
of.
B
We
didn't
have
any
prior
art
to
learn
from
and
when
we
were
building
it
and
so
the
structure
of
the
code's
a
little
off
the
the
sort
of
API
interfaces
that
are
exposed
are
a
little
off
and
I
think
totally
like
that's
how
software
Works,
but
it
would
be
nice
if
the
experience
for
Library
users
and
go
was
a
little
bit
better
and
I
have
a
proposal
I
think
to
do
that
feel
free
to
rip
it
to
shreds
I'll,
probably
I'll
probably
play
with
some
of
these
ideas,
regardless
in
a
repo,
that's
unofficial,
for
a
while
and
see
if
see,
if
anything
fun
comes
out
of
it,
but
the
the
long
and
short
of
it
is
I'm
interested
in
introducing
another
repository
called
six
door
go
that
would
be
analogous
to
the
six
door:
python,
six
door,
RS,
six
door,
JS
and
Ruby
six
door.
B
So
thanks
for
breaking
the
combo
Ruby
folks,
but
would
basically
be
a
language,
Library
client
for
go
and
I
think
I
think
that
would
sit
ult
for
now.
It
would
just
be
an
experimental
on
its
own
thing
in
the
long
run.
If,
if
that
goes
well,
we
would
possibly
refactor
cosine
to
depend
on
that
and
move
a
lot
of
logic
out
of
cosine
and
make
cosine
a
relatively
thin
shim
that
mostly
does
oci
stuff
and
so
on.
So
feedback
feedback
welcome,
including
positive
feedback.
B
Thank
you.
Thank
you,
folks,
in
the
chat,
if
you
want
to
stroke
my
ego
but
but
yeah
feedback
welcome
and
I'll
I'll
think
on
it
a
week
or
two.
If,
if
there's
nothing,
super
negative,
I
will
probably
experiment,
and
if
you
are,
if
you
have
good
ideas,
I'm
happy
to
include
you
also
in
in
experimenting
as
well,
so
so
reach
out
to
me
in
slacker.
The
stock.
B
Whining
yeah,
yeah,
sorry
and
I
I
want
to
recognize
that
in
this
meeting,
I've
basically
had
two
two
agenda
items
that
were
me
complaining
about
things
and
not
fixing
them
myself.
So
hopefully,
hopefully,
this
one
I
will
ultimately
do
some
work
towards
myself.
Yeah.
A
Not
just
echoing
some
of
the
comments
that
I
think
it's
a
great
idea
and
certainly
I
feel
from
a
user
perspective
having
six
Togo
as
a
distinct
client
makes
a
lot
of
Senses,
especially
as
we're
trying
to
piece
together
the
landscape
and
tell
folks
how
to
navigate
and
what
they
should
be
using
foreign
folks.
Please
take
a
a
deeper
look
at
the
proposal.
A
Any
updates
on
the
well-named
language
clients
do
you
have
anything
Java,
python,
arrest,.
D
I'll
I
guess
I'll
just
shout
out,
even
though
it's
sort
of
unrelated
that
Python's
recent
release
now
is
signing
with
Sig
store,
which
is
slightly
related
to
the
python
client
here,
since
it
mentions
using
that
to
verify.
But.
D
We
also
just
fixed
the
bug
in
the
in
in
think
store,
Sig
store,
which
we'll
go
into
cosine.
That
will
allow
cosine
to
also
verify
the
signatures
on
the
python
website,
since
previously,
the
the
way
that
the
certificates
were
presented
there
was
a
bug,
was.
A
Cool
yeah.
No,
so
some
folks
highlight
that
so
yeah
great
to
hear
that
fixed.
A
Okay,
but
yes,
I
think
that's
that's
huge,
so
yeah
I
think
so
highlighting
that's
really
nice
to
see,
see
python
artifacts
now
six
door
signed.
C
Yeah
I
guess
I'm
gonna
defer
to
maybe
Hayden
or
or
Simon,
because
I
wasn't
at
the
ga
meeting
yesterday.
So
I
don't
have
the
latest.
D
I
I'll
take
a
I'll,
take
a
stab
at
and
Simon
feel
free
to
chime.
In
too
we
don't
have
too
many
more
updates.
We've
went
through
all
of
the
open
tasks
found
that
a
number
of
tasks
are
still
open.
So
there
was
some
discussion
around
looking
at
burn
down
to
try
to
figure
out
why
things
you
know
are
still
open
and
figure
out.
What
do
we
need
to
do
to
get
things
wrapped
up?
D
A
Okay,
moving
on
so
yeah
stitching,
Tech
from
the
project
roundups
and
ga
to
looking
at
docs,
Outreach
and
events,
so
we'll
skip
straight
to
the
hacktoberfest
section.
So
folks
may
be
aware:
Oktoberfest
is
coming
up
in
October.
There's
already
been
some
chatter
in
the
slack
Channel
I
think
there's
definitely
a
lot
of
interest
from
folks
in
participating
in
Oktoberfest,
so
yeah
I
wanted
to
highlight
it
here.
A
This
year's
hacktoberfest
each
repo
has
to
opt
in
so
in
the
past
they
have
been
issues
with
Spam
and
Reapers
who
haven't
wanted
to
participate.
They
end
up
getting
spammed
with,
like
very
trivial
pull
requests
which
can
be
exhausting
for
maintainers,
so
as
to
counter
that
this
year
we
do
have
to
explicitly
opt
in
so
I
think
we
wanted
to
start
thinking
about
which
repos
do
want
to
opt
in
and
as
base
requirements.
A
I
believe
they
need
like
some
folks
who
are
willing
to
review
what's
coming
in
and
also
a
set
of
issues
which
can
be
tagged
with
good
first
issues
or
hacktoberfest
yeah.
F
I
could
add
a
little
more
context
to
if
you
have
for
folks
who
don't
know
I'm
Lisa
Talia,
Ferry,
I
I'm
on
the
I've
been
on
the
hectare
Fest
advisory
committee,
the
last
two
years
and
after
they
started
doing
the
opt-in.
Things
have
been
a
lot
better
for
maintainers.
In
my
opinion,
and
this
year
they
want
to
focus
on
non-code
contributions.
F
So
our
plan
is
to
do
some
to
focus
on
the
docs
repo
in
particular,
which
could
definitely
use
some
love,
but
I
I
think
it
would
be
great
to
also
think
about
how
we
could
intentionally
label
some
good
first
issues
for
code
contributions
to
grow,
our
community
too
and
I'm
happy
to
work
with
folks
on
that
and
in
the
in
the
slack
Channel
or
we
could
also
have
like
a
separate
reading
to
discuss
if
there's
interest,
Eric
I,
don't
know
if
you
want
to
add
anything
from
your
perspective
to.
E
A
Great
yeah:
no
thanks
for
that
and
just
send
some
comments.
Yeah
so
Hayden's
recommending
we
opt
the
services
like
Rico
and
full
Co
out
as
we're
pushing
towards
1.0
and
shouldn't
add
to
unnecessary
work.
I
think
that
sounds
good
and
I
can
put
that
out
as
like
here's,
what
we're
proposing
and
share
that
with
the
wider
slack
Channel
cosine
looks
like
it
possibly
opt
in
just
because
we
do
have
a
bunch
of
good
first
issues
and
I
know
there
was
interest
in
slack
any
thoughts
on
that
repo,
specifically
yeah.
B
Broadly
I
think
Hayden's
Hayden's
take
is,
is
a
good
one.
I
think
you
know
we
want
to.
We
want
to
keep
movement
in
the
services
focused
on
on
GA
blockers
cosine
actually
might
be
quite
a
good
fit,
because
many
of
these
are
not
particularly
urgent
issues.
B
They'd
be
relatively
easy
to
Mentor
folks
through
it
shouldn't
be
quite
the
time,
commitment
that
some
some
that
you
might
need
to
get
up
to
speed
on
the
services,
so
I
think
cosine
is
if
we
can
find
you
know
folks
who
are
willing
to
volunteer
their
time
to
to
mentor
and
review
and
I'll
I'll
start
by
saying
I'm
happy
to
do
it.
Oh
yeah,
docs,
I,
love,
docs
hopeful
Lisa
in
your
experience,
do
folks
contribute
to
docs
in
Oktoberfest.
F
Yeah,
they
do
I,
think
I
think
what
we
would
want
to
try
to.
We
would
want
to
try
to
have
issues
for
good
first
issues
for
docs
too,
and
make
sure
that
those
that
they're
like
meaningful
contributions
and
not
just
like
a
change
of
like
an
adjective
or
something
like
that.
Sometimes
sometimes
you
get
peers
like
that.
A
Cool
okay,
this
sounds
good
sounds
like
maybe
I'll
put
together
a
little
Landing
dock
for
hacktoberfest
and
a
place
where
people
can
sign
up
as
mentors
or
as
just
support,
helping
identify
issues
and
things,
and
then,
if
there's
any
other
repos
we
haven't
mentioned
or
any
of
the
language
clients.
If,
if
folks
are
interested
in
welcoming
new
contributors
in
a
position
to
do
so
for
hacktoberfest
yeah,
you
can
add
it
to
that
doc
and
Lisa
I've
seen
some
things
about
pre-tember
as
I.
F
Number,
which
is
supposed
to
be
to
help
yeah,
maintainers
and
open
source
repos
to
kind
of
prep
before
Oktoberfest
I
think
that
yeah
maybe
next
week
we
could
start
to
go
through
some
issues
and
see
which
ones
could
be
labeled
as
good
first
issues
across
cosine
and
dots.
And
if
we
want
to
add
anything
else-
and
maybe
just
like
add
some
structure
there
and
in
in
the
past,
when
I
have
added
structure,
it
has
worked
pretty
well
Erica.
E
Yes,
just
one
suggestion
related
to
prep
Timber,
we
could
maybe
add
some
templates
docs
that
people
using
cosine
can
also
add
to
their
repositories,
maybe
like
how
to
verify
signatures
some
something
around
that
for
people
who
use
cosine
on
their
projects.
I
don't
know.
E
A
A
Yeah
I
like
that
I
guess:
that's
the
other
side
of
this,
welcoming
folks
into
our
community
and
building
our
contributors,
but
also
using
hacktoberfest
as
a
way
to
maybe
make
contributions
to
projects
which
are
open
to
it
about
using
yes,
signing
signing
things.
A
A
A
Okay,
Switching
to
events
open
source
Europe
was
last
week.
I
think
I
saw
a
bunch
of
good
stuff
from
anyone
who
was
there
who
wants
to
give
us
a
debrief.
D
D
C
Yeah
I
did
a
a
brief
session
on
six
door
at
the
beginning
of
open
ssf
day
on
Tuesday,
which
was
well
received,
I
also
plugged
the
the
aforementioned
python
signing
announcement,
which
I
think
was
well
received.
I
know
Billy
had
a
couple
talks
on
good
sign
and
six
store,
so
overall
I
would
say
was
you
know
a
lot
of
shout
outs
to
the
community.
The
work
that
we're
doing
a
lot
of
good
discussion,
I
hadn't
had
a
chat
on
or
a
talk
on
privacy.
C
Preserving
features
of
transparency,
Logs
with
I
think
some
interesting
thoughts
for
folks
to
consider
in
the
context
of
larger
regulatory
environments
and
I
we
had
UC
kukinen
also
give
some
talks
around
the
the
work
with
tough,
as
well
as
some
experiences
using
six
door
within
the
python
community.
So
lots
of
good
lots
of
good
activity
to
happen
last
week
in
Dublin.
That
would
encourage
folks
to
go
look
at
the
recordings
or
check
out
the
slides.
D
I
think
by
the
way
recordings
will
be
up
in
I
think
they
said
30
days.
If
you
have,
if
you
went
to
the
event,
you
can
access
the
recordings
now
via
the
link
go
into
your
email,
foreign.
A
When
they're
available,
but
yeah
I
think
to
everybody
who
was
there
and
gave
talks
and
participated,
yeah
nice
to
have
you
all
flying
the
flag,
the
six
door
and
Security
in
general,
okay,
six.com,
so
folks
may
have
seen
the
schedule.
Physics.Com
is
now
out.
So
many
thanks
to
the
program
committee
for
pulling
that
all
together,
it's
really
nice
to
see
I
think
we've
got
like
14
different
companies
represented
in
in
the
12
different
talks,
so
yeah
all
sorts
of
different
things.
A
We've
got
case
studies
deep
Dives
and
yeah
specific
things
around
the
projects,
foreign,
so
yeah
I
haven't
got
an
update
on
registration
numbers
yet,
but
do
register
if
you're
planning
to
go
I
think
we're
limited
to
about
200
in
the
room
and
then
the
other
thing
just
to
bring
your
attention
to
is
six
to
Awards.
A
So
we
have
nominations
for
those
I
think
are
running
till
the
end
of
today
and
then
we'll
probably
close
them
out
and
get
get
them
in
front
of
the
TSC
for
for
them
to
make
the
final
decision.
So
if
you
do
know
contributors
end
users,
ambassadors,
please
do
go
and
mentioned
books,
good
work
and
nominate
them
for
a
six
star
award.
Sorry
I'll
drop
the
link
in
afterwards
any
questions
since
icon.
A
Okay,
blog
posts
I've
got
a
couple
in
the
pipeline
from
earlier
that
just
need
cleaning
up
and
review
so
yeah.
Nothing
I
think
the
main
one
I
have
maybe
is
on
on
the
new
logos,
just
making
sure
we
let
folks
know
officially
kind
of
where
to
find
the
logos
and
that
we
have
switched
over
and
that
they
are
logos
available
for
the
sub
projects
as
well.
Also
just
to
encourage
folks
if
they
didn't
know
that
already
to
be
aware
and
start
using.
The
new
logos.
A
Foreign
office
hours
just
a
call
for
any
presentations
or
things
from
a
user
perspective
folks
have
for
office
hours.
Let
me
know
for
next
week:
okay,
we've
got
some
any
other
business,
some
Marina.
Why
don't
you
go
ahead?.
H
Yeah,
just
a
quick
announcement,
I
guess
so
at
kubecon,
on
Thursday
at
2,
30
we're
having
a
toughen
and
Toto
contrib,
Fest
and
I'm
hoping
to
get
some
six-star
folks
there
as
well.
So
we
can
do
some
some
work
on
the
kind
of
the
collaborations
between
all
these
projects
and
get
everyone
in
the
same
room.
So
if
folks
are
interested
it's
a
hour
and
a
half
long
session,
but
I
think
the
idea
is
that
we
can
all
write
some
code
get
some
get
some
stuff
started.
A
B
Yeah
in
case
you're,
not
sick
of
hearing
from
me
today,
so
the
there
was
one
issue
and
and
some
work
on
it
and
some
some
good
work
by
Frederick
on
that.
Precipitated
me
asking
this
question,
but
I
think
it's
come
up
over
and
over
again,
and
it
basically
is
when
we
think
about
six-door
apis
and
data
structures
and
data
formats.
B
Should
we
be,
we've
been
defining
a
lot
of
those
in
protocol
buffers,
and
should
we
be
thinking
of
those
primarily
as
protocol
like
as
Proto
interfaces
or
primarily
as
Json
interfaces,
which
is
what
they
often
get
serialized
to
over
the
network
and
might
be
how
they
get
serialized
on
disk?
And
this
has
a
bunch
of
important
implications
for
mainly
how
we
encode
things
so
the
the
big,
the
big
one
is
like:
how
do
you
represent
certificates
or
like
any
binary
data
right?
B
A
bytes
data
in
produce
gets
base64
encoded
when
you,
when
you
serialize
it
to
Json,
and
this
can
sometimes
have
surprising
effects
which
have
led
to
in
in
the
past
double
base.
B
64
encoding
things
which
is,
which
is
pretty
bad,
I,
think
it's
it's
pretty
unwieldy
to
work
with,
and
so
on
and
I
I
think
there
we
could
make
the
world
of
of
six
door
a
better
place
by
picking
one
and
sticking
with
it
sort
of
saying
we're
going
to
privilege
the
proto-representation,
and
we
should
make
that
nice
and
easy
and
idiomatic
to
work
with
or
we're
going
to
privilege
the
Json
implementation
and
we're
going
to
make
that
nice
and
easy
to
work
with
relatively
I
know
how
I
feel
but
I,
don't
I
don't
want
to
influence
anyone
in
the
room.
B
So
I
don't
have
a
plan
for
for
resolving
this
question.
I
just
wanted
to
bring
it
up
solicit
some
some
hot
takes
and
then
maybe
after
some
discussion,
I'll
I'll
propose
some
some
next
steps
towards
making
a
decision,
but
I
guess
first,
is
the
problem
clear
I
know:
I
was
it's
a
high
context
thing,
but
I
wanna,
I
wanna
take
a
a
moment
for
clarifying
questions.
B
Okay,
seeing
none
hot
takes:
okay.
D
I
mean
I,
you
know,
as
someone
who
stares
us
together
gets
too
much
I
I
guess:
I
have
an
opinion
that,
like
certificates
as
Pam,
is
probably
a
more
standard
representation
of
certificates
over
the
wire
than
doing
encoded.
There
I
think
for
the
other
fields.
You
know,
we've
had
a
bit
of
discussion
on,
you
know,
should
bright
arrays
become
hex,
encoded
or
not,
and
I
don't
know
if
that's
really
standard
I
think
the
answer
is
probably
no
so
to
me.
D
I'm
kind
of
special
casing
certificates
and
maybe
keys
I,
just
left
a
comment
around
this
for
what
it's
worth.
We
don't
have
keys
in
there
right
now.
So
maybe
this
is
a
moot
point,
but
just
thinking
about
the
pem
does
give
you
the
ability
to
encode
a
little
bit
of
extra
information
in
the
header,
and
maybe
there
is
some
value
in
that
in
certain
cases,
yeah
I
think
for
Westworth.
D
We'll
probably
need
to
continue
having
this
conversation
offline
or
maybe
set
up
some
some
time
to
discuss
this
a
little
bit
more
I.
Think
with
folks
who
are
interested
just
because
I,
don't
I,
don't
think
we
have
right.
Now
we
have
a
one-to-one
vote,
excellent.
C
C
What
I
am
passionate
about
is
having
apis
that
are
well
documented,
explicit
and
intuitive
and
so
I'm
I'm
less
concerned
about
the
protocol
semantics
unless
they
cause
a
dilution
of
interfaces
being
poorly
documented,
poorly
described
and
not
explicit
so
I
guess
the
I
have
a
preference
which
is
protobufs,
but
I
could
live
with
a
world
where
Json
is
ultimately
the
standard.
As
long
as
we
try
to
make
sure
that
it
is
well
documented,
explicit
and
well
understood
so.
B
Cool
yeah,
so
I
I
see
a
suggestion
in
in
chat
from
from
Trevor
to
move
this
to
something
like
a
GitHub
discussion
and
I.
Think
that's
a
a
great
use
of
of
a
feature
like
that,
because
it's
not
quite
an
issue,
but
it
does
isn't
going
to
necessitate
a
bunch
of
people
arguing
with
each
other
over
text.
So
I
will
I
will
go
ahead
and
set
that
up.
That's
a
good
way
to
facilitate
I
think
some.
B
Some
aggregation
of
preferences
Tracy
telling
people's
votes
in
the
chat
is
perhaps
not
the
most
scalable
thing
in
the
world.
So
I'll
I'll
set
that
up
link
it
here
and
send
it
out
in
Slack
foreign.
A
Otherwise,
we're
going
to
move
on
to
introductions,
so
this
is
a
section
for
anybody
who
wants
to
say
hello,
introduce
yourself
if
you're
new
to
the
community
yeah
so
say
time,
please
feel
free
to
use
it.
A
Gonna
give
a
couple
more
seconds
in
case
you're
unmuting
thanks
Trevor,
okay,
it
doesn't
sound
like
anyone.
So
let's
leave
it
there
thanks
everybody
for
joining,
see
you
next
week,
bye.