►
From YouTube: CHAOSS DEI Working Group
Description
Meeting Summary is here: https://chaoss.discourse.group/t/dei-working-group-july-12-2023/207
Meeting minutes are here: https://docs.google.com/document/d/1MzDk84BL7FfHDxbFxJz39M72V2Hfc5Y6oCPhOl6woxo/edit#heading=h.8o4sxp2w1mwl
A
Welcome
everybody:
this
is
the
chaos
Community
Dei
meeting.
So
this
is
where
we
talk
about
kind
of
all
things:
diversity,
equity
and
inclusion.
We
have
a
variety
of
different
things
that
are
kind
of
going
on
in
this
space
and
a
few
that
I'd
like
to
talk
about
today.
So
I
put
the
minutes
in
the
chat
and
you
could
oops
sorry
add
yourself
and
just
tell
us
how
you're
doing
today,
I
got
caught
in
the
rain.
A
B
Thanks
for
the
spot,
but
thanks
man,
I'm
I'm,
Daniel
I'm,
with
gitlab
just
like
John,
and
on
the
we're,
both
under
developer
relations
and
I'm,
specifically
on
a
contributor
success
team.
So
we
kind
of
try
to
make
the
open
source
contribution
process
better
at
gitlab,
both
trying
to
grow
the
community
and
trying
to
improve
the
process
of
actually
contributing
to
git
lab
gotcha.
A
A
So
basically,
we
work
with
event
organizers
to
think
about
how
they're
centering
Dei
within
their
own
projects
and
I,
know
Katie
and
Anita
and
Sean
myself.
Amongst
many
many
other
people
have
been
involved
in
this
process,
I
just
one
of
the
things
that
I
continue
to
kind
of
struggle
with
at
least
on.
This
is
how
we
can
kind
of
expand.
Katie
you've
probably
heard
this
a
million
times
but
like
how
we
can
how
we
can
expand
the
number
of
events
that
apply
to
Dei
event.
Badging.
A
We
work
really
closely
with
the
Linux
foundation
and
Linux
foundation
events
and
we've
badged
over
a
hundred
events
that
are
usually
related
to
like
ossna
or
osseu.
You
know
those
and
kind
of
the
ancillary
events
I've
tried
to
to
connect
with
other
foundations
without
you
know
kind
of
under
the
same
premise,
without
much
success
in
terms
of
kind
of
getting
this
started,
I
just
so
I'm
still
I'm
still
really
struggling
with
how
to
connect
with
open
source
projects
or
open
source
like
host.
A
B
A
C
I
mean
I'm
new
here,
so
I
I'm,
not
sure
that
this
has
been
discussed
before
or
maybe
it
has
but
like
the
LF
is
like
a
you
know,
pretty
large
Network
yep
and
they
have
you
know
various
umbrella
organizations
like
openssf
and
cncf
and
then
within
those
you
know,
other
organizations
there
may
be
additional
projects
like
within
the
CNC.
Obviously
they
have
a
lot
of
projects
at
different
levels
within
finnos
I
know
they
have
like.
C
But
now
maybe
there's
a
discussion
like
at
the
LF
around
like
what
is
the
value
of
badging
to
these
different.
You
know
sub
communities
or
kind
of
nested
communities,
and
maybe
they
can
help.
You
know
if
we,
if
you
understand
like
where
does
this
fit
in
the
lf's
priorities,
maybe
you
can
shape
the
initiative
in
a
way
that,
like
they
can
help
push
it
out
to
those
groups.
A
It
does
make
sense
because,
like
in
that
scenario
like
we,
we
do
badge
say
like
cncf
or
kukan
I
should
say
you
know
what
I
mean
and
we
have
bad
kind
of
the
LF
events.
But
I
do
like
the
idea,
because
there
are
a
lot
of
900
projects
within
the
LF
itself.
That
could
probably
be
connected
with
more
directly.
So
I
do
like
that.
It's
a
good
idea.
E
So
one
of
the
I
think
one
of
the
things
I've
brought
up
in
the
past
is
kind
of
kind
of
go
go
to
where
these
other
communities
are
at
and
kind
of
meet
them
where
they're
at
rather
than
than
trying
to
get
them
to
come
here.
So
an
example
of
that
would
be
maybe
to
do
a
panel
or
a
presentation
on
badging
at
non
Linux,
Foundation
conferences,
right,
I,
think
we,
we
probably
have
to
be
careful
if
we
do
that,
so
that
we're
not
coming
in
kind
of
being
preachy
I
like.
F
E
C
F
E
True
true,
but
I
think
there
there
are
also
some
perceptions
from
other
other
communities.
That
I
think
we
need
to.
We
need
to
be
careful
kind
of
managing
those
perceptions,
but
I
agree:
yeah,
we're
not
a.
We
are
not
Linux.
Foundation
focused
as
an
organization
I
think
we're
very
open
to
collaboration
with
a
bunch
of
different
communities,
and
we
don't.
We
don't
do
anything.
That's
directed
specifically
at
the
Linux
Foundation.
E
A
A
G
G
C
C
The
git
lab
side,
you
know
essentially
their
multiple
ways.
People
can
host
open
source
projects
on
gitlab,
but
many
of
like
the
larger
ones.
That
would
be
at
the
scale
that
they
would
be
hosting
their
own
event.
As
an
example
would
likely
be
part
of
the
get
lab
for
open
source
program,
and
so
we
may
be
able
to
like
include
some
kind
of
mention
of
this
in
an
email.
You
know
blast
out
to
that
group,
but,
like
they,
notifications
through
the
platform,
tend
to
be
for
things
like
deprecations.
G
D
A
Demographic
information,
you
know
what
I
mean
we
can
do
a
public
review
and
it's
all
done
via
an
issue.
Project
badging
is
quite
different
that
we
we
really
couldn't.
If
we
anticipated
projects
to
go
through
an
evaluation
towards
Dei
doing
a
human
review
would
just
really
be
impossible.
I
guess
the
number
of
projects
just
far
outweighs
the
number
of
number
of
events,
and
so,
as
part
of
the
project
badging
update,
we
have
been
working
with
the
all-in
project
to
propose
a
dei.d
file
and
I
can
bring
up
that
file
really
fast
here.
A
F
F
F
A
So
what
what
we're
doing
with
with
all
in
is
asking
projects
who
are
participating
in
the
project
badging
program
and
again
this
is
still
very,
very
early,
we're
still
in
Pilot
phase
to
include
a
dei.md
file
as
part
of
their
as
part
of
their
org
or
repository.
Then
the
dei.md
file
is
a
file
that
asks
projects
to
reflect
on
or
published
chaos
metrics.
A
The
file
itself
can
be
kind
of
filled
out
in
any
way
that
the
project
feels
is
appropriate
for
their
project,
because
naturally,
every
project
is
different
from
every
other
project
and
like
the
ways
that
one
project
may
approach
project
access
is
naturally
different
than
a
way
a
different
project
would
approach
access
and
so,
as
part
of
part
of
this
program,
what
we're
asking
is
is
for
projects
to
include
this
dei.md
file
in
the
repository
and
then
as
part
of
that
Sean
I'm.
Now
going
to
pull
up
your
should
I
just
pull
up.
A
F
A
F
A
F
There's
some
yeah
there's
some
really
nice
front-end
mock-ups
that
the
ks
Africa
team
has
put
together
and
they're
busy
wiring
it
into
a
fully
functional
site
right
now,
if
you
want
to
know
more
about
the
badging
project,
I've
put
some
links
to
Google
Docs
in
here,
I,
don't
know
if
met
with
met
sharing.
Basically,
if
you
click
on
Project
badging
information,
you
get
a
Google
doc
link.
F
That
kind
of
gives
you
the
high
level
overview
that
we
developed
last
fall
when
we
were
first
working
on
this
idea
and
then
apply
for
the
project
badge.
Basically,
you
go
to
the
project
badging
website
a
maintainer
will
of
a
project
is
able
to
sign
up
and
request
for
a
Dei
badge.
For
that
project
we
decided
that
a
person
needs
to
be
a
maintainer,
because
we
don't
want
anyone,
weaponizing
our
geodet
MD
Badges
and
like
getting
other
projects
reports
and
things
we
want
the
person
applying
for
the
badge
to
be
a.
F
You
know
a
maintainer
someone
who
can
verify
has
some
rights
to
actually
do
this
for
the
project,
and
so
we
check
that
here
and
then
there's
a
bot
that
scans
the
Dei
dot
MD
file
next
and
there's
a
link
to
a
doc
that
sort
of
explains
a
little
bit
more
about
how
that
works,
and
that
involves
the
website
and
interactions
with
GitHub,
where
it'll
actually
scan
the
dei.md
file
and
then
send
the
maintainer
an
update,
indicating
whether
or
not
they
have
a
well-formatted
dei.md
file.
I.
F
The
working
time
frame
is
like
a
day
or
two,
and
so
the
website
will
check
for
the
report
over
here
and
then,
once
it's
completed,
it's
sent
to
the
maintainer
garage
level.
Bronze
is
complete
the
main,
so
the
website
maintains
a
list
of
all
the
badged
projects
and
the
levels
they're
at
it
publishes
new
badge
projects
on
the
website
and
it
then
emails.dei.md
status
in
the
auger
report
and
a
little
markdown
snippet
for
showing
the
badge
on
their
readme
file
on
the
repo
and
then
TBD
is
the
silver
badge
level,
gold
and
platinum.
A
The
couple
things
to
point
out
is:
we
have
there's
two
parts
that
are
going
on,
so
one
is
just
asking
projects
to
include
the
dei.md
file,
which
is
scanned
for
the
presence
of
and
just
making
sure
it's
well
formatted.
We
can't
we
can't
really
guarantee
the
text.
That's
in
the
dei.md
file,
we're
asking
the
community
members
to
kind
of
reflect
on
the
text
that's
in
there
and
if
dei.md
file
is
not
representing.
A
A
Here
are
some
things:
here's
some
data
that
we
see
we're
not.
Judging
on
the
on
the
report.
I
mean
here
are
things
that
you
may
want
to
think
about
when,
when
just
trying
to
improve
inclusivity
within
your
project,
so
an
applicant
really
gets
two
things:
they
get
the
bronze
badge
simply
by
having
the
dei.md
file
present
in
their
repository,
and
then
they
get
a
report.
That's
really
complementary
to
that
product.
A
Badge,
foreign,
we're
moving
forward,
we're
in
Pilot
phase,
so
we
do
have
a
project
that
has
kind
of
agreed
to
participate
to
go
through
this
workflow,
because
we
anticipate
that
it's
not
going
to
be
perfect
by
any
means
nope,
and
this
is
just
for
our
get
lab
friends
here.
This
is
not
intended
to
be
a
GitHub
exclusive
kind
of
thing.
This
is
about
improving
yeah
Dei
within
projects.
F
And-
and
it's
Our
intention
to
eventually
or
to
build
the
GitHub,
the
git
lab-
excuse
me
version
of
this.
We
just
scoped
it
to
GitHub
for
the
pilot
so
that
we
would
keep
the
technical
scanning
part
simpler.
But
Our
intention
is
to
employ
this
on
gitlab
as
well,
and
we
would
love
to
work
with
gitlab
to
make
that
happen.
F
Answer
now
and
I
should
say:
it's
always
been
Our
intention
to
me
because,
like
it's
not
because
you're
here,
it's
actually
something
that
we've
talked
about
from
the
people.
Yeah,
definitely
definitely
on
the
road
map
yeah.
It's
it's
like
not
like
we're
talking
about
not
because
you're
here,
but
because
it's
always
been
on
the
roadmap,
and
this
is
just
a
moment
of
opportunity.
Yeah.
A
A
F
I
I
just
had
a
meeting
with
chaos
Africa
right
before
this,
and
my
sense
is
they're,
pretty
close
to
being
able
to
deploy
the
site
like
if,
if
we
said,
deploy
the
site
next
week,
I
think
that
would
be
no
problem,
so
I
think
we're
really
what
they're
doing
right
now
is
trying
to
make
some
of
the
content.
That's
extensive,
more
easily
digestible,
so
they're,
just
doing
so,
I
would
say:
readability,
findability
and
beautification
work
on
places
where
the
content
got
bulky.
Okay,.
F
A
A
The
silver
level
is
going
to
ask
applicants
to
include
attention
to
two
additional
chaos
metrics
and
then
subsequently,
you
know
as
they
move
forward.
They
have
to
attend
to
an
additional
set
of
chaos.
Metrics
might
be
worth
you
know,
starting
to
think
about
of
the
metrics
that
we
currently
have
developed.
A
A
A
B
C
B
F
Yeah,
it's
a
one-off
review,
and
so
when
a
project
applies
for
the
next
badging
level,
we'll
do
a
comparison
of
the
metrics
from
the
first
badging
level,
the
metrics
from
the
second
badging
level,
looking
for
growth
in
the
areas
that
are
prescribed
by
the
metrics
that
are
there.
So
we
do
do
inclusive
language
scanning,
of
course,
but
we'll
also
provide
general
advice
and
what
we
don't
do
is
give
the
projects
a
score.
F
It's
it's
just
a
sort
of
a
scan
and
some
recommendations
and
for
the
bronze
level
badges
like
we've
had
interested
projects
for
the
pilots
that
have
perhaps
like
two
or
three
individuals
who
are
contributing
to
the
project
and
in
those
cases
really
all
we
can
look
at
is
the
dei.md
file
and
the
size
of
the
project
being
quite
small
and
recommend
ways
that
they
can
encourage
the
development
of
a
community
around
their
project,
because
that
would
be.
That
would
be
an
important
objective
if
they
were
shooting
to
climb.
F
So
at
some
badging
level
there
has
to
be
some
demonstration
that
indeed,
you've
got
a
community
forming
around
it,
that
it's
not
the
same
three
people
who
were
there
when
they
applied
for
bronze,
but
we
haven't
decided
how
to
make
that
determination
or
apply
that
logic
or
not.
So
that's
kind
of
an
open
question
for
the
project.
Badging.
A
Yeah
and
also
kind
of
raise
something
like
my
head,
the
at
the
project.
So
at
the
event
when
we
do
event
badging
those
are
one-off
for
the
one-time
event
and
if
the
event
occurs
next
year,
they
apply
for
a
badge.
Again,
we
are
going
to
have
an
expiration
date
on
Project
badges,
so
we're
going
to
be
keeping
a
tally
of
the
projects
that
have
received
the
badge,
but
they
will
expire.
F
A
F
F
I
think
you
know
following
you
know
some
of
the
guidelines:
nutty
egg
ball
and
others
have
laid
out.
You
know
there
are
projects
that
will
simply
be
public
and
open
source,
but
not
have
communities
around
them
and
you
know
I
think
it's
I
think
a
bronze
dei.md
badge
is
pretty
excellent
and
you
know
if
your
intention
as
a
maintainer
isn't
to
grow
a
community,
then
there's
probably
a
limit
to
how
much
inclusivity
you
can
bring
to
the
open
source
world
right
because
there's
a
commitment
of
mentoring
involved
in
you
know
actually
living
the
inclusivity.
A
B
And
so
basically
git
labs
in
the
process
of
trying
to
revamp
our
contributor
programs,
and
that's
the
programs
for
open
source
contributions
back
to
gitlab
itself.
The
product
and
one
of
the
things
I've
been
pushing
for
was
to
get
the
organizations,
diversity,
inclusion,
belonging
value
to
kind
of
fold
into
the
open
source
community,
and
you
can
see
this
issue
put
together
by
Nick
who's.
The
director
of
the
contributor
success
team
and
one
of
the
ideas
that
Nick
kind
of
was
pitching
here
was
doing
like
Grant
programs
to
try
to
increase
diversity.
B
Efforts
in
the
community,
especially
one
of
the
things
I
went
through,
was
the
Linux
Foundation
study
into
open
source
contributions,
and
the
kind
of
the
idea
of
the
of
time
was
kind
of
the
big
one
that
stood
out
of
not
being
inclusive
of
everybody
not
having
the
same
amount
of
time.
And
so
the
idea
here
of
trying
to
do
a
grant
program
to
buy
time
for
people
to
people
from
underrepresented
groups
to
make
contributions
back
to
open
source.
B
So
that
was
kind
of
how
this
first
idea
happened.
And
then
we
got
feedback
from
like
the
legal
compliance
team.
Saying
that
this
is
sort
of
complex,
because
how
are
you
identifying
people
that
are
from
an
underrepresented
group
so
itself,
even
asking
people
to
self-identify
itself
becomes
a
legal
question
and
so
I
haven't
wanted
it
to
just
sort
of
die
off
there.
B
I
want
to
see
well
what
what
can
we
do
to
work
on
this
for
gitlabs
community
and
what
are
other
open
source
projects
doing
which
is
kind
of
how
we
found
chaos
and
all
in
I'm,
trying
to
figure
out
like
what?
What
do
other
projects
do
to
try
to
increase
diversity
efforts
or
to
you
know
not
only
to
promote
a
safer
space
for
open
source
Community?
But
how
do
you
do
things
like
buy
time
for
for
contributors
that
might
not
have
it?
How
do
you
incentivize
people
to
contribute
recognize
contributors
from
underrepresented
groups?
B
D
C
G
A
F
I
I,
my
first,
my
first
like
shot
after
a
brief
consideration,
is
that
I
think
this
is
a
positive
version
of
the
much
mind
bug
Bounty.
So
the
bug
Bounty
is
about.
You
know
paying
people
to
fix
things
which
can
lead
to
the
firefighter
starting
the
fires
and
all
kinds
of
other
misbehavior,
but
I
don't
see
a
way
to
game.
This,
like
this,
actually
seems
like,
like
a
concrete
way
to
financially
support
a
project
by
and
also
encouraging
them
to
be
more
inclusive.
A
Was
kind
of
the
difference
between
the
types
of
contributions
that
say
a
maintainer
is
looking
for
and
a
newcomer
who
is
interested
in
getting
started
in
open
source,
and
sometimes
those
can
be
kind
of
different
from
one
another.
So
there
can
be
people
who
want
to
participate
in
open
source
because
it
provides
an
opportunity
to
get
involved
in
technology.
It
provides
a
great
opportunity
to
to
learn,
but
the
ability
to
say
contribute
to.
In
this
case.
A
So
in
your
case,
are
you
looking
to
identify
people
who
have
strong
technical
skills?
You
know
what
I
mean.
I
saw
some
documentation
in
there,
but
it
might
help
to
try
to
understand
the
different
skills
of
different
people
and
how
you
would
welcome
those
different
types
of
skills,
because
you
know
like
what
Sean
might
ask
for
a
contributor
to
Auger
might
be
a
little
bit
different
than
what
we
might
do
when
we're
just
kind
of
working
on,
say,
documentation,
yeah,.
B
B
A
B
So
we
do
we're
trying
to
recognize
more
with
any
kind
of
contribution,
contributing
to
a
discussion
and
an
issue
contributing
to
events
to
this
community
chat,
not
just
code
contributions,
not
just
people
who
are
heavily
technical
and
a
lot
of
increase
in
focus
on
our
documentation
to
make
things
easier
for
first-time
contributors.
That's
kind
of
been
my
focus.
B
What
we
haven't
really
done
yet
is
looking
at
the
inclusion
inclusivity
of
people
from
underrepresented
groups,
and
so
that's
kind
of
The,
Next,
Step,
I,
think
for
this
program
and
and
that's
kind
of
where
the
block
hit
of
from
legal
of
how?
How
can
you
ask
people
to
self-identify
and
then
and
then
take
it
from
there
and
also?
B
A
D
That
would
be
the
end
for
them,
whereas
people
that
have
been
in
the
community
for
like
a
long
time
and
doing
all
of
this
I
think
it's
to
be
good.
To
start
from
that
angle
of
people
that
have
been
in
devoting
more
time
appreciating
those
people
before
going
to
like
I,
don't
know
I,
don't
know
how
to
speak
with
it.
But
yes,
I
think
it's
a
great
idea
but
I
think
it's
good
to
also
start
with
people
that
have
been
doing
or
devoting
a
lot
of
time
over
the
years
and
appreciating
them
for
that
work.
D
B
No,
that
that's
a
really
great
point
and
that's
kind
of
one
of
the
fears
too,
is
that
if,
if
people
are
contributing
because
of
incentives,
will
they
become
a
return
contributor
to
the
project?
Will
they
stay
on
the
project
and
grow
with
the
community
or
once
once
you've
met
the
incentive?
And
you
got
that?
Are
you
gone
and
you
know,
then
the
part
of
that
is
on
us
as
an
open
source
project
to
make
it
a
good
experience
and
that
you
want
to
come
back.
B
But
we
don't
really.
You
know,
because
we
do
like
a
lot
of
hackathon
events
and
giving
away
swag
or
gift
cards,
and
sometimes
we're
not
sure
if
people
are
just
doing
it
for
the
for
the
swag
or
do
they
want
to
be
a
part
of
the
community
and
be
a
part
of
the
project
and
I
think
that's
always
a
hard
thing
to
figure
out.
A
A
So
we
have
chaos,
Africa,
we're
starting
chaos,
Latin
America
and
we're
starting
chaos
in
the
Balkans,
and
we
suspect
that
that
the
way
open
source
engagement,
Works
in
different
regions
of
the
world
right,
not
even
a
suspicion,
but
the
way
that
open
source
engagement,
Works
in
different
regions
of
the
world
is
different,
and
we
need
to
understand
that
to
really
try
to
improve
access,
not
just
the
chaos
project
itself,
but
really
our
incentive
here
is
to
improve
access
to
open
source
at
large.
You
know,
like
the
rising
type
lifts.
A
D
D
B
B
We
have
a
really
good
all
over
the
world
kind
of
base
for
our
contributors
of
where
everyone's
coming
from
there
are
some
restrictions
that
come
up
like
legally
with
like
even
like
giving
out
the
swag.
There
are
certain
countries
we
can't
actually
send
things
to
we
found
and
then
with
this
idea
for
the
diversity,
Grant
programs,
it
was
kind
of
brought
up
that
you
know
there's
certain
countries.
B
We
can't
ask
that
question
to
and
that
if
we
were
going
to
try
to
get
this
started,
it
might
have
to
start
with
just
the
United
States
as
like
a
first
part
of
the
program
and
figure
out.
If
that
can,
if
it
can
work
and
then
and
just
kind
of
what
legally
we're
allowed
to
do
and
I'm
someone
who
doesn't
understand
it,
I'm,
not
a
lawyer,
I,
don't
understand
any
of
that
kind
of
compliance
side.
So
my
kind
of
idea
was
like
well,
there
has
to
be
someone
else
out
there.
B
A
C
D
A
That's
great
so
there's
kind
of
two
paths
here,
so
one
is
all
in
for
maintainers
and
that's
kind
of
where
the
project
badging
fits.
You
know
what
I
mean
it's
like
to
help
maintainers
of
projects
best
centered
Dei
within
their
own
within
their
own
projects,
but
then
there's
also
a
program
called
all
in
for
students
and
that
had
run
here,
I
think
Anita.
You
can,
if
you're
more
familiar
with
it,
maybe
than
I
am.
But
it
has
run
once
here
in
the
United
States,
in
partnership
with
I
think
mostly
hbcus
yeah.
F
D
G
F
D
Oh
yeah,
it
is
so
that's
the
next
all
in
that
we're
walking
on
right
now
to
bring
it
to
like
universities
in
Africa,
so
that
they
also
get
the
chance
to
experience
this
country
not
only
contributing
to
open
source,
but
also
getting
some
form
of
incentives.
While
doing
that,
and
also
like
internship
opportunities
as
well.
A
B
That
that's
awesome,
so
that's
all
in
for
students,
program
partner
with
hbcus
I,
definitely
look
into
that.
We
like
we
have
a
partnership
with
Google
summer
of
code
to
get
interns
like
I'm
working
with
an
intern
from
Google
summer
of
code
right
now,
and
that
actually
brought
up
good
questions
about
inclusivity,
because
the
technical
setup
to
contribute
to
gitlab
is
quite
large,
like
as
far
as
the
you
know,
CPU
and
such
and
so
we're
kind
of
wondering.
Well,
how
can
we
procure
no.