►
From YouTube: CHAOSS DEI Event Badging Meeting, December 7, 2022
Description
Links to minutes from this meeting are on https://chaoss.community/participate.
A
A
It's
been
a
while,
since
we've
met
it
was
like
a
month
since
we've
met
because
of
that
U.S
Thanksgiving,
so
yeah
I
hope
everybody's
doing
good.
A
First,
one
is
just
a
reminder-
and
everybody
here
already
knows
this,
because
they've
heard
it
so
many
times
already,
but
we'll
just
put
it
out
there.
One
more
time.
No
meetings
from
December
12th
to
January
9th
I
should
say
no
cast
working
group
meetings.
There
is
an
extra
auger
Workshop,
that's
gonna
happen
next
Monday
on
the
December
12th.
A
But
if
we
want
to
keep
working
in
this
working
group,
we
want
to
keep
working
through
slack
and
async.
That's
completely
fine
I!
Imagine
we
might
get
some
badges
some
badge.
Applications
in
December,
so
I'll
still
be
around
checking.
I
know
Ruth
checks
also,
so
so
yeah
we'll
be
around
if
anybody
wants
to
keep
working
the
next
one
is
a
big
huge
thank
you
to
Oma
and
damilola.
A
If
I'm
pronouncing
that
right
for
our
badging
Wiki,
that
helps
share
kind
of
just
like
the
history
of
badging
What
It,
Is,
Why,
We,
Do
It,
just
to
have
some
extra
documentation
around
this
in
the
repo
as
well.
So
this
is
really
great
initiative.
So
thank
you
to
those
two
folks.
B
A
We
were
just
started,
so
we
just
want
to
remind
you
both
that
there
are
no
meetings
from
this.
No
I
should
say
in
a
working
group
meetings.
Official
chaos
working
group
meetings
from
December
12th
to
January
9th,
but
we
will
keep
working
because
the
badging
applications
keep
coming
so
like
we'll
still
be
around
some
of
us
anyway.
So
I
just
want
to
make
that
clear,
and
then
this
we
were
just
looking
at
this
badging
Wiki
as
well.
A
I
do
have
a
question
for
Ruth
on
this.
Is
this
information
also
going
to
be
on
the
badging
website,
and
is
it
going
to
be
the
same?
Is
it
going
to
match
wow.
C
C
You
know
the
history
of
Diagon
initiative,
because
I
think
when
Omar
joined
she
had
some
issues
with
understanding
the
metrics
like
how
the
you
know
apply
to
real
life
scenarios,
so
I
think
that's
what's
the
reason
she
puts
behind
this
document
to
help
newcomers
get
on
boarded
like
events
pattern
and
the
information.
That's
there
is
just
for
events
pattern.
So
I
think
this
will
just
leave
on
that
Wiki,
the
Wiki
page,
except
we
want
to
create
a
blog
post
out
of
it
to
put
on
the
DI
button
website.
A
Yeah
that
makes
a
lot
of
sense,
I,
wonder
if
we
should
make
do
we
say
that
we
just
kind
of
say
welcome.
Maybe
we
could
make
that
clear
here
on
that
home
page
that
that
is
like
kind
of
the
purpose
of
the
document.
Just
so
we
keep
it
straight
internally.
A
So
and
then
my
other
question
was
how
does
this
plug
into
the
community
handbook
or
the
knowledge
base
on
that
side?
Is
this
the
same
information,
or
are
we
just
kind
of
pointing
people
to
the
wiki
here
or
the
badging
website
aware,
like
okay,
so,
okay,
Anita,
says
Wiki
will
be
a
reference
doc?
Okay,.
C
A
I,
just
don't
want
us
to
have
like
you
know,
a
lot
of
different.
C
Is
there
something
the
knowledge
base
currently
I
think
I've
lost
on
knowledge
base,
but
like
when
you
say
the
stuff
is
not
going
to
be?
Is
for
budget.
C
A
Okay,
so
for
review,
okay,
so
I'm,
just
thinking
like
we
have
other
so
anything
for
a
a
reviewer
should
go
in
the
wiki.
C
Idea
for
the
week
was
to
help
people
kind
of
you
know,
especially
for
you
guys,
because
so
that's
why
I
should
prepare
that
document.
So
awesome.
A
C
We
have
initially
we
had
that
whole
documentation
on
the
handbook
and
the
conversation
we
had
that
day
was
since
it's
going
to
be
on
the
websites,
the
DI
website.
We
should
just
have
a
one-page
readme
that
shows
everything
about
budging.
Okay,
when
it's
back
to
more
information
on
the
websites
or
on
the
repo
right,
we
would
still
have
that
content
on
the
repo,
but
the
knowledge
base
will
only
pull
that
with
me
to
the
sites.
D
D
C
D
C
C
A
And
I'm
so
sorry
to
keep
harping
on
this.
We
do
have
also
and
I'm,
not
sure
how
these
fit
in,
but
we
have
this
info
for
applicants
info
for
reviewers
and
the
info
for
reviewers.
We
have
like
this
reviewer
guide,
and
this
has
some
links
down
here.
Should
we
just
merge
these
into
the
wiki
I
feel
like
that
would
make
sense
like
we
don't
need
them
in
two
places.
C
C
So
we
have
the
history:
what's
the
di
button,
why
goals
and
bad
info
I
think
we
can
keep
it
after
badging
flow?
Like
we
view
our
rules,
I
think.
A
C
D
D
D
So
go
back
to
yeah,
so
then
this
is
really
this
front.
Look
will
really
be
all
for
applicants
really
when
it
comes
down
to
it,
it'll
be
who
we've
badged
and
then
just
really
just
yeah.
Taking
a
look
at
this,
this
ends
up.
Looking
like
it's,
it's
really
just
from
an
applicant
perspective
at
this
point,
which
is
fine
and
then
the
wiki
is
to
help
reviewers.
C
A
Yeah
agreed
I'll
I'll,
put
more
information
in
that
issue
after
the
meeting
I
just
didn't
want
to
like
take
up
time,
So
yeah.
Thank
you
so
much
for
that
context.
Ruth,
that's
really
great
work
from
them.
I
really
appreciate
them
working
on
this
I'm
kind
of
pulling
it
together,
especially
from
a
newcomer
perspective.
That's
super
super
helpful.
So
thank
you.
Oh
man.
A
Okay,
next
is
the
badging
website
update
just
wanted
to
double
check
with
Kingsley
to
see
if
there's
an
update.
Sorry
to
put
you
on
the
spot
here
same
to
you
Enoch
after
that
I'm
gonna
do.
B
I
I
I
think
you
really
have
more
of
the
designs
for
like
next
year.
That's
for
the
budgeting
project,
so
you
have
more
designs
ready
for
implementation
next
year.
Well,
at
the
moment,
let
me
just
share
what
we
have.
D
B
So
we
have,
of
course
we
have
a
few
screens.
E
B
For
implementation
and
I
believe
you
know
kind
of
streaming
spoken
on
this,
so
what
we
now
did
was
trying
to
you
know
prep
the
design
for
mobiles,
so
we
have
a
couple
of
screen.
Some
of
it.
I
think
we
are
actually
done
with
some,
but
then
I.
Of
course,
I
had
my
own
review
feedback
I
still
trying
to
make
things
more.
B
For
example,
screens
like
this
actually
look
so
long,
so
my
issue
was
like:
are
there
options
we
could
explore
to
reduce
the
scrolling
time
so
for
the
design
this
design
is
done,
but
I
think
I
just
had
some
issues
with
usability
I
feel,
like
user
will,
spend
so
much
time
scrolling
through
and
since
it's
really
not
like
the
text
of
view,
and
that
will
really
be
a
pain
point,
so
I
think
it's
more
of
the
usability
issue.
So
that's
why
I
wish
they
have
these
Pages
here.
B
So
we
have
the
screen
for
the
Mobile
screen
for
to
view
the
badge
events.
So
this
is
actually
what
we
have
for
desktop
view,
and
this
is
the
experience
we're
creating
for
the
mobile
interview
to
kind
of
make
it
more
adaptive,
like
so
I
think
something
goes
with.
So
some
of
the
screens
like
I
said
most
are
actually
like
with
regards
to
the
ones
ready
for
implementation.
Some
of
these
mobile
screens
are
edible,
I'm,
just
looking
at
ways.
B
We
could
actually
improve
visibility
and,
of
course,
I
believe
we
all
agree
with
me
that
you
know
visiting
a
sites
like
this,
where
you
have
to
scroll
through
all.
This
is
like
damn
too
long
and
still
maybe,
when
I'm
able
to
figure
that
out
then
I'll
push
I'll
push.
This
particular
designs
to
implementation.
I
know
that,
and
you
know,
kind
of
shape
can
also
consider
working
on
the
mobile
view,
but
for
now
I
had
a
brief
call
with
the
design
team.
B
But
before
this
call
and
I
think
we
talked
about
some
of
these
and
I
don't
know,
maybe
some
of
them
I
want
to
do
some
stuff,
but
then
I
think
they're.
Also
aware
that
scares
is
going
on
break
so
I
think
we
have
more
experience
to
share
when
we
are
back
from
like.
B
And,
of
course,
one
of
the
things
that's
actually
been
going
on
inside
these
actually
the
design
system
and
we're
just
building.
This
is
still
part
of
the
project.
You
know
we
keep
building.
This
keeps
getting
bigger
and
bigger
position
with
me.
I'm
very.
B
To
any
training
community,
so
that's
the
feedback.
I
have
you
know,
I,
don't
know
if
you
have
questions
or
we
have
suggestions
and
I
know
that,
especially
for
the
mobile
view,
like
I,
said
really
looking
at
some
ways.
We
could
make
this.
You
know
maybe
shorter
and
simpler,
so
I
really
appreciate
any
feedback
or
comments
or
Solutions.
We
have
on
this.
D
B
A
I
think
this
looks
amazing,
amazing
and
such
great
work
from
the
whole
team.
Just
so
grateful
for
all
those
who
are
working
on
this
project
and
just
it's
just
wonderful.
B
B
A
Suggestion
might
be
is
if
there's
a
way
to
pull
some
of
that
information
out
and
just
put
it
in
a
separate
page
I,
don't
know
how
you
feel
about
that
or
like
how
flat
you
want
the
website
to
be,
or
if
it's,
okay,
to
have
a
bunch
of
different
pages
and
clicking
in
and
out
I.
Don't
I,
don't
know
like
I'm,
not
definitely
not
a
usability
expert,
but
I
do
agree
that
it
does
look
kind
of
long
to
scroll
all
the
way
down.
B
A
And
then
my
my
second
just
statement
is
that
if
hopefully
you
all
have
everything
you
need
from
like
just
a
logistical
implementation
standpoint,
a
technical
standpoint
like
if
you
need
accounts
or
like
I,
don't
whatever
you
need
just
let
me
know
and
I
think
Ruth
had
been
trying
to
reach
out
to
me
too,
but
like
just
let
it.
Let
me
know,
let
me
or
Matt
know,
and
we
can
provide
whatever
kind
of
support
you
all
need.
B
C
Exactly
so
in
terms
of
implementation,
we
recently
like
we
started
the
walk
some
months
ago.
You
know
set
up
like
and
I'll
soon
hand
this
over
to
you
know,
but
it
looks
there
like
the
the
structures,
the
work
and
to
some
extents
we
stopped,
and
then
we
are
back
again.
I
just
dropped
the
link
to
the
the
hosting
page.
Initially
we
had
it
on
Heroku,
but
since
Heroku
stops
their
free
plan,
we
had
to
move
to
Netflix.
C
So
this
link
shows
the
work
that
has
been
done
so
far,
which
I
have
not
seen
and
I'm
just
looking
at
it
now
so
Enoch
yeah,
you
can
take
it
from
here.
B
F
Impressive
impressive,
okay,
yeah
kind
of
looks
like
is.
C
F
No,
not
your
screen,
it's
not
really
optimized
yet
should
work
I
think
there
are
no
limits
to
the
with
its
size.
So
that's
why
it's
like
that,
but
it
can't
be
a
problem
with
your
screen.
F
So
on
top
of
what
Ruth
is
trying
to
share
I've
been
trying
to
like
she
was
saying,
we
have
resumed
our
contribution
and
I'm
happy
that
when
changes
are
made,
this
link
updates
straight
away.
I
deleted
the
Heroku
deployment
because
we
no
longer
had
access
to
it
and
we
have
a
new
person
who
is
helping
me
out
to
manage
this
development.
F
He
requested
I
call
him
TK,
because
the
other
name
was
a
little
bit
so
to
mention
out
in
full,
but
right
now,
I'm
I
I'm
doing
some
rebasing,
which
is
the
hardest
thing
in
using
jit,
because
I
have
technical
requests.
I
want
to
merge
together,
but
they
have
almost
20
files
that
have
been
changed
with
more
than
like
30
lines
of
code,
50
lines
of
code,
but
hopefully
before
tonight
ends
I'll
be
able
to
have
resolved
all
those
into
one
single
file
because
they
are
over.
F
Like
30
commits
that
I'm
looking
into
and
they're
from
different
requests
by
the
time
that
is
done,
we
should
be
able
to
have
our
about
page,
looking
almost
like
how
it
is
in
the
figma
files
at
least,
and
then
it
was
the
home
page
and
then
I
am
going
to
make
some
more
Issues
new
issues,
because
after
this
repressing
and
matching
the
triple
requests
into
one
single
file,
of
course,
there
are
issues
that
I
have
already
realized.
F
That
I
need
to
be
worked
on
and
also
that
some
contributors
can
contribute
to
to
optimize
this
page
and
also
add
onto
the
UI
to
make
it
look
like
the
figma
file
so
before
the
call
actually
Ruth
just
slacked
me,
I
had
forgotten
about
this
meeting.
I
was
fighting
with
all
those
commitment
changes
to
make
sure
that
they
look
so
pretty
well
understand
that.
A
F
F
F
Okay,
I
wanted
to
show
these.
F
Just
showed
up
all
right:
it's
loading.
G
F
So
if
you
can
see
from
this
screen,
it
is
a
little
bit,
not
optimized,
which
is
not
a
problem.
It's
the
problem
of
the
word,
but
from
my
screen
it
looks
pretty
because
I
think
whoever
developed
this
was
using
a
similar
screen
size
to
mine.
F
There
are
three
changes
that
are
not
yet
here.
So
I
think
this
looks
pretty
like
what
is
in
figma
down
here.
There
is
something
you
see
down
here.
B
F
Footage
is
already
there,
but
it's
in
a
different
pull
request,
so
after
rebelling,
okay
and
if
I
can
just
try
to
reload
this
I'm
loading
this
actually
from
localhost,
because
I
am
making
the
changes
from
there.
F
You
can't
be
able
to
see
it
when
you
are
I've
not
yet
pushed
the
changes,
but
if
I
run
that
from
my
machine
here
and
show
you
how
that
footer
looks
like
it's
not
the
best
I'm,
not
saying
it's
not,
but
I'm
like
it's
not
like
how
it
is
on
the
figma
files,
but
hopefully
we
are
going
to
see
how
that
changes.
So
let
me
just
reload
this
from
a
different,
my
difference
and
see
how
it
looks
like
so.
This
is
another
pull
request
that
I'm
trying
to
match
with
the
other
one.
F
So
this
is
how
the
footer
looks
like
from
another
pull
request.
So
a
lot,
some
changes
have
to
be
made
like
I
can't
see.
I,
don't
know
whether
this
is
the
right
font
and
also
the
mobile.
The
mobile
view
is
not
the
best.
Oh
I
can't
scroll
this.
F
I
hope
they
are
I'm
using
my
eyes
to
guess
so,
I'm
not
sure.
So
there
are
few
changes
that
will
need
to
be
made,
but
I
want
to
make
these
changes
up.
I
want
to
put
these
changes
up
then
make
and
and
compare
them
again
as
the
figma
files
see
what
needs
to
be
changed,
create
issues
for
them,
and
then
you
can
have
all
these
issues
optimized
as
soon
as
possible.
F
Otherwise
there
is
I
think
there
will
be
progress,
and
this
would
be
done
if,
if
we
have
the
response
that
we
had
at
the
beginning
of
this
of
this
contribution,
I'm
sure
by
the
end
of
January
this
one,
this
won't
be
an
issue.
We
shall
love
our
site
up
and
running
so
yeah.
F
A
F
If
the
response
of
the
developers
is
like
the
way
it
was
we're
just
touching,
then
I
am
definitely
sure
you
will
have
it.
E
F
Interface
or
the
UI,
we
would
have
a
little
bit
of
delay
into
plugging
into
the
application,
but
the
UI
the
static,
the
static
views
will
be
ready.
D
F
Sure
that
is
I
was
hoping
to
cross
the
river
when
I
reached
there.
So
something
I've
not
yet
thought
of.
D
Okay,
if
you,
if
you
want
it
to
be
a
sub
domain
of
chaos,
dot
community,
you
do
and
we
haven't
done
that
I,
don't
think
in
the
chaos
project
and
that
may
or
may
not
be
possible.
We
can
certainly
put
the
request
in
but
I'm
not
sure
where
the
requests
will
be
received.
Oh
go
ahead:
Sean
yeah.
G
I
have
put
a
request
in
and
I
think
when
we
were
testing
the
changeover.
They
did
one
for
us,
but
then
I
had
one
get
lost
in
a
transition.
D
Approach
might
be
to
just
simply
have
it
as
a
like
Elizabeth,
something
that's
managed,
potentially
through
WordPress,
just
as
its
own
as
its
own
page,
and
then
the
the
other
option
is
just
to
have
it
completely
be
its
own
website
like
we
just
get
a
new
domain
called
like
you
know,
chaos
Dei
event,
badging.
You.
B
A
A
B
G
D
F
Sorry,
I
I
I'm,
it's
not
really
something
that
I
thought
of
first,
but
I
would
much
mention
this
I
think
could
be
cool
having
badging.cars.community
than
having
really
a
separate
platform
earlier
on.
We
thought
it
would
be
an
independent
platform
because
we
wanted
to
have
project
badging
on
it
and
we
thought
it
was
going
to
expand
Beyond.
What
we
had
originally
but
looks
like
it
won't
go
beyond
what
we
already
have
and
they'll
just
be
Improvement
and
interventions.
F
So
if
we
can
have
that
subdomain
I
think
it
would
be,
it
would
be
a
good
thing
to
do
because
then
it
also
even
feels
like
yeah.
This
is
part
of
chaos
too.
It's
not
like
a
separate.
F
B
F
And
if
it
works
out
really
and
we
can
have
access
to
the
sub
domain,
we
could
start
using
it
straight
away.
D
Where'd
I
put
it
I,
guess
it's
just
that
bad!
Oh
hot
yeah
yeah
that
how
to
connect
with
this,
and
so
right
now
on
the
website
redesign.
We.
D
F
D
F
A
Feel
like
the
intent
anyway,
is
to
have
that
application
page
eventually
be
on
this
page,
be
on
the
new
website.
But
that's
that's
the
piece
that's
going
to
be
tricky
to
to
plug
in,
because
that's
the
thing
that
does
all
the
work
that
has
like
interactive
stuff.
So
to
your
point,
Matt,
we
maybe
want
to
think
about
a
bridge
or
like
a
stop
gap
of
like
what.
D
B
D
B
D
B
B
B
D
F
B
F
F
G
Just
go
ahead.
Well,
it's
soft,
but
do
your
best.
F
G
F
Got
interrupted
with
the
network,
someone
was
trying
to
reach
me
from
another
platform.
I
I
was
saying,
I
think
I,
don't
know
how
we
can
do
that,
but
I'm,
seeing
that
budging
that
budging
page
could
be
really
redundant.
We
could
have
that
redirect
directly
to
the
budging
website
when
it
is
up,
because
the
information
that
is
that
that
I'm,
seeing
in
the
budging
page
on
the
chaos
website
on
the
chaos
website,
is
almost
the
same
and
more.
G
F
And
then
it's
linking
to
the
sub
domain
I,
don't
know
the
ux
of
that,
but
at
least
I
think
we
can
do
away
with
that
page
Kingsley
can
advise
on
the
user
experience.
B
Okay,
thank
you.
You
know
you're
right
that
the
information
we
have,
of
course,
similar
information
and
I,
think
we
have
actually
have
more
on
debugging
websites.
You
like
currently
being
developed
even
more
wrong,
so
I
think
as
long
as
it's
like
a
solid
domain
to,
of
course,
the
careers
websites-
I,
don't
I,
don't
think,
there's
anything
wrong
with
like
redirecting
for
now,
except
maybe
just
through
using
to
a
completely
strange
environments.
G
E
B
Okay,
so
that's
great
and
I
also
wanted
to
add
that
Eve
at
all,
you
are
redirecting,
then
this
should
be
like
an
action
so
equal
to
action
that
will
take
user
like
it
doesn't
departure
where
they
are
coming
from,
because
now,
if
you
look
at
this,
the
I
think
the
action
the
user
is
supposed
to
take
now
maybe
apply
for
a
badge
and
then,
of
course
you
we
are
redirecting
user
to
this
page
where
maybe
just
come
to
know
how
to
know
that.
So
how
do
they
go
back?
E
A
E
From
it,
so
if
they
are
going
to
go
away
to
the
to
the
submit
your
event,
badge
page
make
sure
that
everything
they
need
on
this
page
can
be
read
and
does
not
need
to
be.
They
don't
have
to
come
back
to
this
page
and
then
go
back
to
the
badging
page
again.
A
Yeah
I
think
it
is
I,
think
it's
I
think
that's
what
they're
saying
is
that
the
badging
website
will
actually
have
more
information
than
this
page,
but
just
the
the
question
is
like
the
actual
application
of
like
where
they
fill.
That
in
is
that
going
to
be
ready
on
the
new
site,
so
yeah
I
think
we're
good
yeah.
E
A
E
C
Yeah
so
I
think
we
should
maintain
this
page.
C
We
can
have
that
whole
summary,
and
then
we
link
them
back
like
on
this
page
to
the
to
the
upcoming,
like
the
websites
and
something
else.
While
we
also
need
to
maintain
this
page
is
that
we
also
do
not
have
meat
figured
out
about
how
we'll
do
it
on
the
budget
website
like
the
application
process.
C
So
we
should
when,
when
we
have
that
figured
out,
we
can
just
have
like
a
summary
of
Dei
badging
on
this
page,
and
then
we
link
people
back
like
this
is
to
get
more
information
and
to
apply
to
the
main
badging
website.
When
that
is
open
running
so
I
think
we
should
still
maintain
this
page
because
then
it's
part
of
their
exercise,
so
they
don't
leave
what
they
were.
Looking
for
and
then
navigate
to
another
website.
A
A
F
Yeah,
it's
completely
fine
that
I
have
something
to
share
I
I
I,
I
I
was
having
issues
with
the
previous
review
ones,
because
some
of
them
did
have
rights
to
edit
checklist,
and
it
was
bothering
us
until
we
found
out
where
the
issue
was
so
in
that
line.
F
I
was
trying
to
see
how
we
can
try
to
automate
that
so
that
the
people
that
become
reviewers
can
automatically
have
a
right
to
edit
the
checklists
which
helps
to
reduce
our
change
to
our
errors
in
the
logs,
so
that
so
that
we
only
mind
about
the
things
that
are
really
very,
very
important
to
look
at
I
was
discussing
with
Ruth
and
I
told
if
I,
if
I
was
coming
up
with
something
which
I
want
to
share
here
and
see
how
plausible
that
looks
like
to
you
all
so
I
I
was
I,
told
Ruth
that
we
could
come
up
with
something
like
these
and
then
I'm
link
it
somewhere
in
our
in
our
in
our
Pages
or
in
our
chats
with
the
reviewers.
F
For
now,
until
the
budging
website
is
up
so
like
a
GitHub
form-
and
this
is
not
on
the
on
the
real
repository
it's
on
my
repository-
the
one
I
used
for
testing
so
I
I
had
I
I
had
made
a
GitHub
form.
E
F
Is
like
a
review
application
form
which
only
helps
for
the
name
and
the
slack
name
and
then
on
clicking,
submit
I
thought
that
this
form
would
automatically
trigger
the
the
budging
Bots
to
add
the
reviewer
to
the
to
the
review
team,
which
automatically
gives
you
some
rates
to
the
events
and
diversity,
inclusion
repository
so
that
you
can
be
able
to
edit
to
edit
and
and
and
submit
like
reviews
on
the
checklist,
then
also
it
it.
F
It
will
using
your
slack
name
due
to
any
badging
badging
channel
the
slot
Channel.
That
is
something
I'm
still
developing
so
far
at
least
I'm
done
with
the
automation
of
automatically
adding
the
reviews
to
the
review
team
in
GitHub.
The
only
thing
I'm
still
now
figuring
out
is
how
to
use
their
name
and
be
able
to
identify
whether
they're,
ready
in
the
budging
channels.
F
The
the
documentations
of
the
slack
API
are
a
little
bit
obscure
and
they
are
giving
me
a
little
bit
of
headache,
so
I'm
still
trying
to
figure
that
out.
So
once
that
is
done,
I
want
to
introduce
it
fully
to
you
all
and
see
how
that
looks
like,
but
I'm
thinking.
If
it
takes
long
and
the
the
budging
website,
May
proceed
its
importancy
and
we
may
not
get
it's,
we
may
not.
F
We
may
not
get
to
use
it,
but
if
it
happens
before
the
budging
website
is
anywhere
I'm
thinking,
it
would
be
something
we
would
use
and
always
Point
new
reviewers
here,
so
that
when
they
fill
in
this
form
on
submitting
this
new
issue
automatically
does
all
the
other
magic
it
needs
to
do
by
giving
them
access
to
all
the
information
in
the
badging.
In
on
on
the
badging
repository
and
in
the
marketing
channels,
I,
don't
know
whether
there
was
a
lot
of
information.
A
F
A
We
could
even
add
that
as
a
as
a
check,
so
when
a
new
Badger
joins
that.
A
I
go
through,
and
so
we
could
add
this
to
to
that.
If
that
would
be
helpful
Enoch
do
you
know
what
I'm
saying
I.
F
If,
if
you
can
say,
I
tried
it
out,
I
made
a
sample
just
as
some
photos
a
test
to
see
how
that
works
out,
and
if
you
see
when
I
made
one
one
application,
just
a
test
application.
It
brought
me
this.
This
is
like
an
MD
file
that
has
links
to
a
reviewer
guide,
reviewer
role,
submission
guidelines.
F
There
is
another
one
I
thought
there
were
two
that
I
made:
oh
yeah,
then
it
adds
just
a
label.
This
level
is
just
to
to
to
help
to
see
about
the
the
issues
to
know
that
this
is
this
is
a
review
application
issue,
or
this
is
a
reviewer
I
mean
like
a
review
for
an
event,
but
I
hope
this
is
the
checklist
you're
trying
to
say
which
points
reviewers
to
different
resources.
They
can
have
access
to.
F
So
it's
not
it's
not
like
a
checklist,
but
it
it's
like
a
a
comment
that
has
links
to
where
reviewers
can
find
more
information.
They
want
to
get
acquainted
with
how
the.
A
Doc
that
we
give
to
new
reviewers,
it's
a
checklist
for
them,
for
we
call
it
next
steps
and
that
new
Badger
info
form
you
know.
Maybe
we
could
combine
that
somehow,
with
what
you're
doing,
although
the
signal
information
would
be
private,
so
we
probably
wouldn't
want
to
put
that
in
there,
but
maybe.
F
Okay,
yeah
sure,
I
I
think
it
would
be
good
to
look
into
it
right
now.
What
I'm
trying
to
solve
is
the
functionality.
Then
I
can
look
into
the
content.
The
content
later
yeah.
A
A
G
D
I
know
we're
at
time,
but
I
was
thinking.
Maybe
something
to
think
about
is
on
the
website.
This
is
connecting
back
to
the
website.
Work
is
having
like
a
link
that
says
something
like
explore:
explore
our
badging
bot
to
know
how
this
process
works.
It's.
F
F
F
Okay
and
and
then
that
whole
confusion
made
me
lose
track
of
Matthew's
questions.
F
F
D
Issued
like
just
everything
and
I'm
wondering
if,
right
now,
the
badging
bot
is
kind
of
just
embedded
in
the
it's
just
kind
of
embedded
in
like
how
the
work
gets
done
and
it's
not
super
transparent
for
people.
D
Okay,
so
I
was
wondering
if
we
might
want
to
try
to
raise
the
badging
Bots
profile
a
little
bit.
You
know
what
I
mean
like
on
the
website.
Just
saying
hey,
you
know.
A
lot
of
this
is
automated,
and
if
you
want
to
investigate
how
the
badging
bot
works,
you
can
take
a
look
here,
and
this
would
just
be
for
like
applicants
or
reviewers
I,
don't
think
that
anybody
would
necessarily
spend
a
lot
of
time
looking
at
it,
but
it
might
just
be
nice
to
to
draw
that
work
forward
a
little
bit.
F
I'm
sure
I
am
I,
don't
know
who's
I
just
feel
like
someone
is
trying
to
say
something:
oh
okay,
I
I,
I
I'm,
making
more
improvements.
G
F
Budging
board
for
now,
because
in
the
end
we're
going
to
use
it
as
it's
going
to
be
a
layer
that
is
going
to
be
on
top
of
the
budging
website.
F
Some
things
may
be
hidden
from
the
reviewers
and
also
the
applicants.
But
in
the
background,
what
is
here
gives
us
like
a
framework
that
we
are
going
to
use
while
we
are
trying
to.
While
we
are
trying
to
join
the
budging.
D
Website
with
automations
that
may
be
needed,
yeah
no
I,
I
totally
get
that
and
I'm
just
all
I'm
trying
to
get
at.
Maybe
somebody
can
help
me
say
it
a
little
better
is
that
the
badging
bot,
like
it's
just
critically
important
for
how
this
process
works
and
if
we
could
just
really
highlight
like
a
link
to
the
GitHub
repository,
if
anybody
is
curious,
just
because
this
is
Dei
related
work
and
people
might
have
an
interest
in
any
of
the
automation
work
that's
occurring
in
a
Dei
process.
D
F
To
answer
your
understanding
of
your
question,
I
do
not
know
how
much
more
like
how
how
how
which
process
currently
needs
to
be
like
be
open,
because,
as
far
as
I
know,
our
readme
kind
of
highlights
all
the
automation
process
that
really
the
the
bot
does
and
Ruth
also
is
trying
to
make
sure
that
the
documentation
and
the
wikis
and
all
the
documents
she's
working
with
really
highlight
what
the
budgeting
board
does.
F
The
process
that
every
review
goes
through.
Okay,
so.
F
I
think
there
is
already
information
for
that
could
be
hidden
or
not.
I,
don't
know
how
accessible
it
is.
But
of
course,
when
you
come
to
the
budging
board
and
look
at
the
readme,
there
is
already
information
of
what
the
flow
of
how
that
automation
happens.
Anything
more
than
that.
That
needs
to
be
really
clarified
on
two
automation
process.
I
think
we
can
have
that
conversation
later,
but
I
think
so
far.
The
information
that
is
there
is
just
basic
enough
for
someone
to
have
a
view.
What
happens?
B
A
A
Of
time,
thank
you,
everybody
for
coming
and
just
a
reminder.
Our
next
meeting
is
not
until
January
something
I,
don't
know.
Yeah.
A
Was
yeah?
We
are
out
of
time,
but
yes,
I'll
just
share
really
quick.
Just
a
week,
oops
oh
I
lost
my
tab
here,
hold
on.
A
Yes,
we're
at
94
applications,
which
is
from
my
just
manual
accounting,
so
hopefully
I
counted
right,
but
we
are
yeah.
So
I
don't
know
if
we
want
to
do
something
special
around
like
if
we
get
to
a
hundred
I,
don't
know
or
do
we
want
to
tweet
it
do
we
want
to
do.