►
Description
[SIG ContribEx] GitHub Administration Subproject Bi-Weekly Meeting for 20211202
A
Hello,
everyone-
this
is
the
december
2nd
2021
edition
of
the
trivex
github
administration,
subproject
meeting
this
meeting
is
being
recorded,
will
be
placed
on
youtube
and
we
follow
the
cncf
code
of
conduct.
Please
be
excellent
to
each
other.
This
might
be
a
pretty
quick
meeting.
We
we
ended
up
having
to
postpone
from
last
week
as
a
number
of
folks
were
out
of
the
office,
but
we'll
quickly
run
through
what
we
have
bob
you're.
First
up
with
eccla
now.
B
A
B
Is
we
broke
it?
We
broke
it
multiple
times
now
so
running
it
in
this
sort
of
dry
run
mode.
Non-Blocking
mode
has
been
good.
At
this
point,
I
would
not
suggest
migrating
over
to
it
till
sometime
next
year,
especially
like
there's
a
I
can
drop
a
link
to
the
feedback
form,
but
there's
like
things
where
commits
even
from
the
same
author.
In
the
same
pr,
only
some
of
them
are
being
recognized
by
easy
cla.
C
Totally
makes
sense,
I'm
following
the
threat
on
github,
where
people
are
like
crazy
and
issues
publicly
so
yeah,
like
I
completely
agree
with
you
here,
we
are
like
we
are
in
touch
with
the
lfx
team
internally
on
this
one
and
like
amy
specifically,
is
like
is
trying
to
to
like
trying
to
solve
this.
The
like
kind
of
like
the
communication
issue
here,
but
for
now
like
where
in
the
community
head
like.
I
completely
agree
that
we
should
not
migrate
by
by
the
end
of
the
year.
A
Process
as
far
as
the
the
like
keeping
it
on
in
a
dry
run
mode,
is
it
potentially
creating
confusion
for,
for
especially
newer
contributors
ones,
who
will
go
through
the
current
cli
process?
Sign
it,
but
then
easy
cla
will
still
be
complaining,
even
though
we
know
it's
supposed
to
be
complaining.
So.
B
They
they
are
syncing,
it
they're
syncing
it
so,
like
the
I
forget,
when
the
last
sync
was,
but
they
are
doing
them,
something
like
weekly
or
something
like
that.
So
it
is
capturing
people
awesome,
and
it's
just
that
yeah.
The
biggest
thing
would
be.
New
contributors
will
be
potentially
confused
by
it.
B
A
Well,
it's
one
of
those
situations
where,
like
you
know
there
is,
there
is
no
non-prod
environment
as
far
as
the
number
of
contributors
that
we
have,
we've
done
all
the
kind
of
non-prod
testing
that
we
can.
We
kind
of
have
to
test
it
perking
production
here,
but
you
know
at
least
we're
we're,
seeing
and
surfacing
those
errors
up
and
the
one
other
question
that
I'd
have
is
like
is
the
lfx
team?
B
They've
been
keeping
track
of
them
in
a
separate
spreadsheet,
so
like
each
person
that
posts
in
the
the
the
one
open
issue
that
we
have,
they
basically
will
like
look
at
it.
There's
a
couple
cases
that,
like
I,
I
actually
think
people
who
have
a
cla
sign
in
the
old
system
still
have
it
tied
to
like
their
old
employer
or
something
like
that,
and
they
haven't
actually
updated
it
themselves
right.
A
C
D
A
So
the
the
catacota
author
profile,
I'm
gonna,
switch
hats
a
couple
times
here
so
on
the
just
the
regular
contribute
side.
Talking
about
this
particular
thing,
the
cataclysm
author
profile
side,
I
think,
don't
think
we've
fully
figured
out
how
to
do
that.
I
know
I
think
this
is
gonna,
be
part
of
the
mentoring.
Some
project
and
josh
is
going
to
sponsor
this
as
like
a
sub
project
owner.
A
So,
like
the
the
author
profile,
like
what
my
understanding
looking
at
the
documentation
is
like
you
go,
create
the
author
profile
and
then
once
you
create
the
author
profile,
you
get
a
a
web
hook
secret
from
that
author
profile
and
then
on
the
github
side.
You
configure
the
web
hook
with
like
okay.
So
here's
the
payload,
the
payload
url,
going
to
to
the
catacota
itself,
and
then
you
take
the
secret.
D
A
A
A
A
If
there
is
anything
out
of
band,
we
could
talk
about
it
either
in
the
github
management
channel,
on
slack
or
on
the
mailing
list,
and
bring
up
anything
like
async
that
we
need
to
deal
with
there.
But,
okay,
so
not
hearing
any
objections.
I
will
go
ahead
and
cancel
that
meeting
for
the
23rd
of
december.