►
From YouTube: [SIG Contribex] Bi-Weekly Meeting for 20220607
Description
[SIG Contribex] Bi-Weekly Meeting for 20220607
A
A
B
A
B
C
A
A
D
F
E
D
D
D
B
D
F
F
F
F
Thanks
yeah,
there
may
be
a
problem
to
solve
and
that
I
don't
know
if
a
single
zapier
function
can
work
for
multiple
accounts,
so
we
may
have
to
create
a
new
zap
every
time,
so
I
would
be
interested.
Perhaps
if
that
is
the
case
like
finding
a
more
elegant
solution,
but
for
now
things
work,
you
know
the
concept
X1
has
been
working
steadily
trending
over
the
videos
and
so
yeah
I'm
fairly,
confident
that,
as
we
incorporate
most
suits
like
everything
will
be
fine,
but
I
will
reach
out
if
any
support
them.
D
D
D
A
C
C
We
had
a
few
other
kind
of
housekeeping
items
that
we
need
to
take
care
of
with
GitHub,
with
updating
our
team
and
updating
some
of
our
role
handbooks
we're
doing
a
project
right
now
trying
to
get
all
of
our
leads
to
update
their
role
handbooks
with
explicit
Shadow
requirements.
Originally,
when
we
designed
the
roles
we
defined,
what
you
need
to
have
in
order
to
do
the
role
since
a
shadow
is
just
someone
who
is
training
to
take
over
the
role.
But
a
lot
of
folks
we
found
are
confused
by
the
term
Shadow.
C
They
don't
really
know
what
that
means.
So
we're
trying
to
add
more
explicit
guidance
in
all
of
our
documentation,
so
we're
adding
a
section
in
each
role,
handbook
that
is
Shadow
requirements,
which
is
the
things
that
you
need
to
have
with
maybe
some
guidance
on
the
things
that
you
can
learn
as
a
shadow
and
also
making
it
clear
everywhere
that
a
shadow
is
someone
who
is
going
to
take
over
a
lead
position.
A
E
A
A
A
E
A
B
B
A
E
No
one
sec,
so
I
have
been
sort
of
prepping.
The
migration
of
the
kinterbeck's
lists
over
to
kubernetes,
managed
lists,
and
so
far
everything
looks
good.
I
still
need
to
do
the
export
and
import,
but
if
that
works
and
then
it's
just
like
setting
a
date
in
a
cutover,
then
documenting
it
and
trying
to
get
the
other
six
to
do
the
same.
E
E
D
E
D
D
D
So
that's
the
plan,
the
we
also
need
to
rev
the
software,
but
I'm
waiting
to
see
if
I
can
actually
get
one
more
difficult
fix
in
the
the
difficult
fix
having
to
do
with
case
sensitivity
right
now,
Electro
is
case
sensitive
in
places
where
it
shouldn't
be,
but
the
problem
is
that
fixing
that
is
a
total
refactor
of
the
code,
so
so
we'll
see
if
I
get
that
done
before
the
election.
Otherwise
we
just
put
docs
in
warning
people.
E
D
No
because
the
problem
is
that
the
comparison,
the
comparison
with
your
logged
in
GitHub
ID
is
being
made
individually
like
in
all
kinds
of
places,
and
it's
and
it's
just
being
made
as
a
list
comprehension.
It's
not
anything,
it's
not
a
function.
Okay,
so
the
first
rewrite
is
that
we
need
to
take
all
those
comparisons
and
redirect
them
to
a
utility
function.
That's
the
rewrite
part!
Then
we
can
do
whatever
we
want
the
utility
function,
but
first
they
need
to
be
centralized
similar.