►
From YouTube: [SIG ContribEx] Weekly Meeting for 20230524
Description
[SIG ContribEx] Weekly Meeting for 20230524
A
Hello
and
welcome
everyone
to
the
Wednesday
May
24th
edition
of
the
Sig
contributor
experience,
bi-weekly
meeting
I'm
your
host
Castle
fields,
a
reminder
we
do
operate
under
a
code
of
conduct
which
essentially
says
to
be
respectful
of
your
fellow
attendees
and
speakers
and
generally
be
excellent
to
each
other.
A
A
Thank
you
to
the
folks
who
have
already
been
adding
their
names
to
the
attendees
list.
Before
we
kick
off
with
our
agenda.
Is
there
anyone
new
on
the
call
who
wants
to
say
hello,
excuse
my
cat
she's
new?
She
says
hello,
but
if
there's
any
new
contributors
on
the
call,
we
like
to
offer
an
opportunity
here
at
the
beginning
of
the
meeting
for
you
to
unmute
and
tell
us
a
little
bit
about
yourself
or
you're.
Welcome
to
post
in
the
chat
totally
optional.
A
B
D
Haven't
heard
anything
from
Nigel,
but
it
as
Bob
said
it
should
be
soon
cool
a
volunteer
to
help
Nigel
as
semi-emeritus
semi,
backup
so
I'll
ping
him
this
week
and
find
out
where
we're
at.
A
I
am
certainly
trying
to
keep
an
eye
out
for
announcements
about
the
opening
of
that
issue.
I
knew
a
few
folks
who've
been
interested
in
getting
involved
with
that,
so
I'll
make
sure
to
share
that
with
them.
Once
it's
available
any
other
discussion
around
events.
A
B
I,
don't
think
they're,
like
the
the
two
programs,
have
spun
down
I
shut
down,
I
archived,
the
two
slack
channels.
So
there's
nothing
currently
ongoing.
E
We
did
get
some
feedback
from
Marche
regarding
what
can
be
done
better,
so
the
summary
of
that
is,
we
basically
need
a
better
way
to
filter
people,
in
terms
of
who
we
admit
the
last
one
was
pretty
much
well.
It
was
almost
first
come
first,
sir.
We
need
basically
reflect
like
a
higher
depending
on
what
the
cohort
is.
So,
for
example,
if
it's
at
at
least
like
maybe
knowing
Golan
could
have
been
a
prerequisite
product
reviewer
called
because
that
was
something
that
they
struggled
with.
B
Was
the
same
thing
in
the
CLI
one?
The
the
big
problem
was
most
of
the
mentees
said
that
they
already
know
go
and
were
already
familiar
with
parts
of
it
already
and
to
be
frank,
they
lied.
E
Yeah
yeah,
so
we
were
brainstorming.
A
few
ways
to
just
basically
have
a
better
criteria.
One
obvious
one
is
odd
member,
but
we
know
how
that
is.
That's
an
obvious
one.
Another
one
is
showing
that
much
trouble
contributions
like
any
form
of
contribution.
Just
to
that
that
is
another
one
then,
like
I,
don't
know
like
a
while
back
iron
had
a
python
script
which,
like
suggested
reviewers,
based
on
get
histories
and
stuff
like
that,
but
there
were
a
few
issues
with
that.
E
E
There
could
be
a
valid
candidate,
the
few
ideas
for
brains
that
you
operate,
somebody
in
the
summit,
but
definitely
something
to
do,
take
a
look
at
more
definitely.
A
E
A
B
Someday
in
journal,
this
will
happen
again.
It's
usually
Sig
or
subproject
initiated
so
Rob
in
the
in
the
Gateway
API
I
was
thinking
of
potentially
doing
one.
B
There
was
another
one
that
was
being
considered
for
I
think
it
was
customized,
but
on
very
like
hey.
We
might
want
to
consider
doing
this
type
thing.
A
B
We
do
have
docs
for
it
in
k,
Community
in
the
mentoring
subdirectory,
so
we
could
potentially
PR
something
there
with,
like.
You
know,
make
sure
there
is
a
greater
scrutiny
on
applicants.
E
That's
already
a
very
big
problem
in
the
community,
because
that's
the
main
reason
people
had
hesitate
to
Mentor
folks.
That
is
it's.
It
might
not
be
worth
that
time
in
the
long
run.
So
if
that's
the
feedback
they
get
from
an
a
new
mentoring
structure,
then
like
we
might
lose
any
potential
six
that
might
be
willing
to
adopt
it
in
the
future.
So
I
I
think
before
we
do
any
more
cohorts
be
adding
that
into
the
mentoring,
markdown
I
think
should
be
done.
A
B
B
They
basically
do
their
assignment,
and
then
they
leave
I've
talked
to
contributor
strategy
a
bit
about
this
and
trying
to
gather
some
metrics
to
sort
of
see
like
you
know,
but
let's
track
the
path
of
of
these
people.
A
bunch
of
them
have
moved
on
from
kubernetes
to
like
other
projects
in
the
ecosystem,
but
few
stay
here.
C
A
All
right
with
that,
shall
we
move
into
contributor
comps
anyone
there
hear
from
that
group
this
week.
C
F
Bed
I
put
underneath
my
desk
because
she
still
likes
to
have
stuff
over
her
head.
So
I
put
some
notes
in
here.
Real
quick,
I
think
caslin
you
can
like
I
had
to.
If
I
forgot
anything,
we
need
some
zapier
connections
created
to
the
back
end
services
that
are
going
to
be
used,
specifically
Drive,
Zoom
and
I
thought.
F
C
F
E
F
A
a
whatever
and
contribex
here's
you
know
how
to
get
there
through
this
group
kind
of
thing.
There's
an
idea
floating
around
about
doing
Twitter
spaces,
since
we
do
have
a
Twitter
account
and
then
this
week's
meeting
is
virtual
and
Slack.
A
Yeah
I
wanted
to
talk
more
about
the
shadowing
and
the
Twitter
spaces
every
now,
and
then
I
like
to
bring
up
the
fact
that
we
have
Shadow
roles
open
in
our
meetings
and
I
realized
after
doing
that
this
week
and
talking
with
many
of
our
student
attendees
about
it.
But
folks,
don't
know
what
shadow
means
I
probably
should
have
should
have
clicked
earlier,
with
all
the
problems
that
we've
had
with
it
with
the
contributor
Summit
and
everything.
A
But
a
lot
of
the
folks
think
that
shadow
means
an
opportunity
just
for
them
to
get
mentored
and
do
not
get
the
part
where
it's
you're
expected
to
take
over
the
lead
role
yeah.
So
we're
going
to
be
updating
our
documentation
to
say
everywhere.
Shadow
means
you
are
going
to
take
over
a
lead
role
right
and
here
are
the
criteria
for
what
you
would
need
to
have
already
in
order
to
work
towards.
A
A
These
are
the
things
you're
probably
going
to
learn
as
you're
shadowing
Not,
a
Bad
Thing
to
document,
so
I'll
probably
be
working
with
our
leads
to
try
and
get
that
additional
detail
added
to
each
rule
book
and
then
we're
going
to
try
to
make
the
terminology
of
Shadow
very
clear
throughout
our
documentation,
something
that
we
might
want
to
consider
for
like
contributor,
Summit
and
other
things
as
well.
A
And
if
there
are
no
comments
on
that,
then
Twitter
spaces,
like
Chris,
said
yeah,
someone
mentioned,
maybe
we
should
hold
the
Twitter
space.
While
we
were
joking
around
talking
about
something
we
were
like
wait
a
second,
we
do
have
a
Twitter
account
and
we've
never
considered
holding
Twitter
spaces.
A
A
All
right,
we
still
need
to
sync
with
Craig
Peters,
about
the
status
of.
B
F
B
Progress,
it's
tildear
as
we
were
going
to
connect
later
and
get
it
sorted
out:
okay,
cool!
Let.
A
That's
important:
it's
important
the
way
that
we
decided
to
design
that
anyway
sounds
good
and
then
maybe
we'll
work
on
the
contributor
site
more
at
the
next
contributor
or
Summit
that'd,
be
another
fun
session.
Do
more
on
that.
It.
A
You
should
keep
that
in
mind.
So
next
item
moderation
and
media
Nigel.
A
F
Yeah
I'm
trying
to
log
into
everything
right
now
so
I.
A
B
So
it'll
probably
be
either
later
this
week
or
sometime
next
week,
but
there's
gonna
be
some
comms
going
out
because
we're
seeing
an
increased
use
of
GitHub
actions
in
the
project.
Oh
okay,
which
is
you
know,
it
isn't
necessarily
bad.
It's
largely
used
for
simple
things
which
you
know
is
fine,
that's
like
even
in
the
contributor's
site,
you
know
repo.
We
use
it
to
essentially
run
a
Cron
job,
just
like
hey
update
the
site,
every
12
hours.
B
The
problem
is:
is
that
a
lot
of
us
don't
know
GitHub
actions
well,
and
there
are
some
very
large
and
dangerous
foot
guns.
Yes,.
B
How
Bluey
I
I
won't
go
into
detail.
B
F
B
That
is
literally
something
I
brought
up
with.
I
was
just
like
I
want
to
limit
these
things
from
being
used
right.
F
That
that's
kind
of
sad
darn.
F
B
A
F
I
just
checked
the
zapier
account
we're
not
good
Bob.
Sorry,
okay,.
B
No
worries
I
I
will
log
into
the
account
at
least
make
a
couple
connections
later:
cool.
A
A
Open
Mic
discussion,
time.
First,
item
migration
to
manage
groups
for
contribex.
B
So
I
have
set
up
managed
groups
under
kubernetes.io
for
contribex.
B
The
the
main
list
is
just
going
to
require
more
coordination,
because
it's
you
know,
dropping
a
message
to
the
current
list.
Saying
like
you
know,
this
is
going
to
change
on
the
state.
We
make
the
change,
we
import
the
users
and
basically
lock
the
the
current
list.
We
also
have
to
update
the
various
places
in
6.yaml.
B
But
that
is
something
we
we
want
to
get
going
on
and
sort
of
create
a
Playbook
on
just
because
we're
having
so
many
more
other
sigs
having
problems
with
the
just
general
Google
Groups.
A
Makes
sense
something
that's
been
happening
for
a
while
good
to
see
that
moving
and
a
it
sounds
like
you
all
are
also
documenting
as
you
go
along
for
all
of
the
other
groups
that
are
going
to
need
to
do
this
right,
so
documentation
will
also
be
forthcoming.
I!
Imagine
after
this
because
I
imagine
you're
using
this
as
a
basis
for
a
lot
of
the
documentation
right.
B
B
There's
some
like
little
key
indicators
that
kind
of
pop
up
that,
like
honestly,
takes
like
a
human
to
really
take
a
look
at
and
sort
of
see
like
good
example.
They'll,
add
a
PR
that
adds
a
function
that
doesn't
have
any
test
cases
or
they
will
that
function
like
even
though
they
add
that
function,
it's
not
actually
implemented
in
any
other
places.
B
Other
thing,
like
sort
of
common
patterns
that
I
have
personally
seen
have
been
you
know:
they'll
have
a
very,
very
verbose
like
you,
honestly,
I
I,
like
I,
can
tell
what
chat
gbt
writes
these
days.
I
can
tell
it's.
It's
becomes
easier
to
just
tell
what
it's
ritzing
and
so
like
they
tend
to
have
a
very
verbose
response
in
an
issue.
B
But
then,
when
dealing
with
responses
on
the
you
know,
PR
review
or
responding
to
an
issue
it
tends
to,
like
you
know,
be
a
very
different,
Styler
Cadence
and
again
there's
just
like
little
indicators
like
that
that
pop
up
I
said
we
are.
We
are
not
the
only
project
facing
this.
It's
happening.
B
It's
mostly
in
the
bigger
projects
but
like
rust,
has
Cena
Cena
electron
has
seen
it
I,
think
I
think
vs
code
like
yeah
yeah,
most
of
most
of
the
larger
projects,
have
seen
it
and
no
one
has
a
good
solution.
Yet
so
kind
of
you
know,
brainstorming
potential
ideas,
but
like
really
it's
just
kind
of
like
you
know,
keep
something
in
the
back
of
your
head
for
now
like.
B
If
something
you
know,
if
you
randomly
have
an
idea
of
potentially
how
to
deal
with
this
in
the
shower
like
jot
it
down
in
and
please
mention
it
because,
frankly,
the
problem
is
only
going
to
get
worse.
B
B
F
A
A
C
Possible
to
use
a
tool
like
gpt0
or
GPT
output,
output.
F
Detector
I
was
about
to
say
there
are
some
safety
tools
right.
I
feel
like
this
is
the
perfect
use
case
for
him.
Chad
good
point.
C
I
I
know
that
for
our
last
devops
days
conference
they
use
this
tool
to
for
the
cfps
to
detect
if
people
were
using
chat
GPT.
So
oh
I.
A
B
F
F
Is
this
like
you
have
to
check
it
for
like
actual
usage,
and
things
like
that
right,
like
that's
a
tough
one,
I
did
just
ask
it.
I
got
a
nice
response
chair
somehow.
D
That
only
scratches
the
surface
of
into
license
violations.
B
Don't
yeah.
B
So
for
at
least
the
code
generation
ones
like
sometimes
if,
like
some
of
the
ones
that
I
have
seen
where
people
are
generating
code,
they
literally
will
take
the
GitHub
like
issue
title
or
of
like
the
the
you
know.
The
issue,
or
you
know,
take
a
description
from
the
issue
and
literally
punch
it
into
the
thing
and
basically
take
the
generator
code
from
that
and
paste
it
in.
B
B
No,
no
and
other
projects
and
GitHub
are
thinking
about
this
problem
too.
So
if
one
of
the
collective
people
think
of
something
it
will
definitely
get
get
shared
out.
B
C
A
B
D
A
A
Legally
speaking,
like
a
AI
watermark,.
D
A
F
F
A
I
think
we're
probably
good
on
our
discussion
for
today,
so
we'll
go
ahead
and
stop.
Our
recording
folks
are
welcome
to
hang
out
bye,
YouTube.