►
From YouTube: ContribEx: Bi Weekly Meeting 20200520
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
everyone
today
is
the
May
20th
bi-weekly
meeting
for
a
sick
country
to
experience
my
name
is
Bob
killin
mr.
Bobby
tables
across
all
the
things,
with
a
pretty
light
agenda
for
today,
but
I'll.
Kick
it
off
with
sort
of
our
you
know,
routine
things.
First
and
foremost,
we
abide
by
the
CNC
F
code
of
conduct,
which
essentially
boils
down
to
please
be
excellent
or
each
other.
A
If
anyone
would
like
to
volunteer
as
a
note-taker,
that
would
be
awesome
and
if
you
just
toss
your
name
in
the
agenda
by
the
note-taker
section,
there
that'd
be
that'd,
be
great
and,
lastly,
for
our
normal
routine
stuff.
Do
we
have
any
new
contributors
on
the
line
that
would
like
to
introduce
themselves.
B
A
B
A
George
is
actually
a
hosting
office
hours
right
now,
the
morning
session
looked
like
it
went
pretty
well,
I
had
to
drop
for
part
of
it
and
I
know
that
they're
going
to
be
having
a
networking
specific
one
next
month,
community
meeting
wise
things
are
looking
good
for
the
contributor
summit.
We
don't
have
any
updates
for
that.
I
honestly,
don't
expect
any
updates
for
a
bit,
but
we'll
see
how
things
go
with
the
steering
committee
election.
No
real
change,
since
our
last
updates.
C
C
From
of
Gordon
community
bridge,
so
the
Goosen
of
gold
actually
update
that
we
does
have
any
updates
until
late
June,
so
everything
is
smooth.
Now
our
mentees
have
been
selected,
so
they
are
at
community
bond,
encouraged
right
now
with
community
bridge.
We
are
the
final
station
all
selections
we
have
one
slot
granted
of
for
Gannett
is
CSI
working
group
and
they
have
selected
their
main
key
and
another
slot
was
granted
to
user
experience
group
in
their
first.
A
A
Okay,
moving
right
along
off
to
github
management,
so
this
one
we've
talked
about
a
few
times
before,
and
it's
the
github
or
cleanup.
We
had
our
mailing
list
discussion
on
the
contributes
mailing
list
and
had
general
support
for
it.
We
just
need
to
be
very
clear
on
the
verbage.
It
has
also
been
socialized
with
the
chairs
and
team
leads
in
our
in
the
the
monthly
meetings,
and
so
far
everyone
has
been
very
much
in
favor
of
it
long,
especially
cleaning
up
the
inactive
owners.
A
A
No
updates
on
slack
infra
computer
documentation.
The
big
thing
here
is:
we
have
I,
updated
our
reviewer
guidelines
and,
if
it's,
it
could
now
use
a
second
round.
Well,
it's
probably
like
a
ferret
or
300
reviews.
At
this
time,
I
was
pretty
much
a
complete
rework.
So
if
you
have
some
free
time
to
review
that
that'd
be
much
appreciated.
E
E
A
E
So
I
wonder
what
would
be
the
fastest
way
to
get
that
done?
We
don't
have
to
just
decide
that
here,
but
if
I
could
see
like
the
Institute
of
all
the
docks
and
then
another
Institute
like
how
the
docks
are
nested
in
each
other's
and
that's
like
a
flow,
that's
existing
and
how
do
we
tighten
up
the
flow
we.
F
So
design
question
that's
came
up.
Much
earlier
is
a
contributor
site.
If
we're
doxy
theming
it.
Oh
nice
mug.
If
we're
doxy
theming
it
does
that
mean
it's
gonna,
come
from
an
actual
sort
of
hugo
structured
repo,
or
are
we
still
doing
the
thing
where
we
take
stuff
from
the
community
repo
and
pipe
it
into
something
else?
So.
A
So
we
have
to
like
we
add
the
metadata
and
all
that
for,
like
you'll,
see
the
header
and
the
contributor
guide,
all
that
section
there
eventually
you
know
things
might
shift
over,
but
we'd
have
to
see
people
using
that
more.
Before
doing
that,
the
last
time
we
brought
up
spinning
out
the
documentation
with
the
community
remote
repo
there,
a
significant
pushback.
F
E
I
feel
like
maybe
there
is
a
tendency,
what
to
perfect
specific
areas
of
safe
documentation
and
then
the
documentation
as
a
whole
is
perhaps
duplicative
or
can
be
reduced.
I
duped,
oh
yeah,
and
then
there's
also
a
nesting
option.
Like
you.
When
you
have
an
outline,
you
have
your
high-level
theme,
you
break
it
down
into
further
details
and
then
further
details
and
that
might
with
this
dog
the
oxide.
It
might
be
more
possible
to
necess
more
clearly
yeah.
A
A
There
is
some
more
Help
Wanted
issues
with
this
as
well.
These
are
the
things
we
want
to
nail
out
before.
Pushing
live.
I
have
that
linked
in
the
issue
there.
It's
mostly
fixing
some
little
bugs
adding
the
computer
calendar
back,
and
then
we
have
to
finish
like
transferring
the
domain
over
into
Dubuque
AIDS
and
for
a.
G
Quick
one
for
the
first
item
there,
the
the
icon,
I,
think
that
might
be
because
you're
using
you
go
minify
that
sometimes
breaks
SVG
files,
that's
one
liners
and
looking
at
the
the
website
that
looks
like
it
has
broken
it
up.
Okay,
so
if
you
either
add
an
SVG
file
instead
of
having
it
well,
you
already
have
that
nevermind.
So
what
we
did
for
another
site
was
just
disable
minified,
because
they're
super
small
anyway
and
yeah
just
ran
with
it.
That
way,.
B
A
So
if
you
can't
make
it
you
know,
or
you
know,
if
you
don't
see
anything
on
the
agenda,
you
know
no
big
deal
and
then
we'll
couple
that
with
sending
the
notes
to
the
list.
So
if
something
was
discussed
that
you
are,
you
know
have
an
opinion
on
and
you
weren't
able
to
make
it.
You
can
then
follow
up
on
the
list.
E
A
A
A
E
H
H
D
A
Marketing
would
still
have
their
own
meeting.
This
would
just
be
rolling
in
to
our
much
less
attended
meetings
like
our
contributor
documentation.
Our
issue
triage
issue
triage,
will
now
just
sort
of
be
on
the
tail
end
of
the
meeting
and
give
people
an
opportunity
to
drop
if
they
don't
want
to
be
around
for
that
yep.
H
F
F
D
I
F
A
E
So
I
think
those
have
all
been
pretty
transparently
communicated
over
slack
channels
and
threads,
but
basically
I
have
one
question
for
you:
Horrors
that
we
had
talked
about
on
that
CNCs.
The
channel
about
meeting
with
Lukasz
next
week,
ish
to
just
get
more
of
a
face-to-face
interaction
around
like
what
the
purpose
of
the
dashboards
are
and
just
get
for
me
like
also
to
get
some
more
context
on
them,
so
that
I
can
relate
to
this
team.
Is
that
possible
to
set
up
for
next
week.
F
E
D
E
I
just
see
that
there's
some
packaging
improvements
to
those
that
they're
not
fully
described
so
that
a
user
would
actually
be
able
to
spot
the
value,
and
perhaps
through
some
of
the
discussions
that
we've
been
having
some
of
that
information
has
been
surfaced,
but
there's
also
just
the
actual
use
of
usability
directions.
What
are
the
different
numbers,
meaning?
Where
do
they
come
from.
E
F
I
A
A
E
E
A
Time
for
you
to
drop
me
sorry,
Don,
then,
let's
see
you
have
the
the
next
thing
to
the
119
process.
Improvements.
Yes,.
D
E
Have
a
debate,
but
essentially
what
I
see
is
a
lot
taking
place
all
at
once
and
it
may
not
all
be
necessary.
So
this
is
for
the
release
team,
and
this
has
been
validated
by
members
of
the
release
team
and
so
basically
what
the
goal
is.
How
do
we,
how
do
I
help
them
do
fewer
higher
value
things
related
to
process
improvements,
and
so
first
that
I
was
wondering
if
I
pay
you
done.
E
Maybe
you
can
just
pull
this
link
up,
actually
that
you
have
to,
but
basically
just
getting
all
the
items
that
I
can
find
related
to
release
team
process
improvements
in
a
single
place
and
then
so
I've
shared
this
link
with
that
spreadsheet
and
then
there's
four
primary
steps
to
the
release
cycle,
and
then
I've
got
I've
created
tabs
for
those
four
sets.
Did
you
see.
A
E
E
Right
I:
do
it
all
the
time
yeah?
So
here
you
go
here
is
basically
the
dump
of
items
things
topics
there
is
even
sub
project
boards,
I've
told
all
of
the
enhancement
sub
project
board
items
one
by
one
into
this
and
then
the
column
a
this
meant
for
everybody
to
just
clarify
where
which
stage
in
the
release
cycle
it
fits
under
and
there's
right
now
a
diagram
with
these
four
stages
of
the
release
cycle.
It's
on
github,
and
so
it's
what
you
see
here
featured
to
finish
and
shoot
your
work.
E
There's
two
more
blue,
yeah
I
think
they
were
categorized
and
there's
also
yeah.
There's
the
release,
notes
and
the
release
and
then
the
overall
process.
So
there's
five
stages,
total
Oh
bugs.
So
you
have
a
tab
for
every
stage
and
then
the
goal
here
is
for
the
team
to
meet
asynchronously
after
I
give
a
presentation
a
couple
weeks:
June
first
I
think
what
are
the
must
show
it's
nice
to
have
and
won't
do
this
items
so
that
they
can
prioritize
for
each
category.
E
You
know,
like
all
the
feature,
definition
of
the
feature,
work,
etc.
So
what
are
the
most
urgent
and
then
what
are
the
highest
impacts,
lowest
effort,
and
then
this
should
ideally
cut
down
like
they
might
be
able
to
consolidate
some
of
these
ideas
and
at
least
they
can
unset
119
and
one
finals
that
are
based
on
the
highest
value
goals
instead
of
things
that
might
be
really
time-consuming.
But
it's
not
very
high
value.
I.
E
Then,
if
it's
like
a
huge
need,
maybe
there's
a
way
to
break
it
down
into
smaller
bits
so
that
they
can
achieve
the
highest
value.
Part
of
that
stated
goal
in
some
reasonable
amount
of
time
that
they
can
define
whether
it's
for
119
or
120,
and
then
the
goal
of
this
is
to
clarify
exactly
what
is
the
happy
path
for
the
release
cycle,
because
that's
not
diagrammed
anywhere
in
Sasha
green
notes
and
he's
also
in
Germany,
sometimes
very
funny.
It.
E
E
Yeah
exactly
so
I'm
sorry
that
was
a
long
explanation,
but
it's
kind
of.
Hopefully,
you
can
see
like
how
I'm
approaching
some
of
these
bigger
questions,
and
the
goal
is
that
with
cascading
darvid
with
seamless
flowing
process,
then
you
have
also
the
organic
sig
needs
to
like
also
manifest
upwardly
some
improvements
and
then
in
the
middle.
E
Hopefully,
at
some
point
you
have
the
to
meet,
but
I
think
that,
because
the
release
team
and
the
release
like
it's
so
fundamental,
any
positive
effects
and
impacts
there
will
cascade
downward
and
it
can
also
set
other
things
around
the
release
process
on
a
better
path
by
driving
that
change.
They've
already
been
working
on
this.
So
it's
it's
already
happening
and
it's
just
a
way
to
accelerate
some
of
that
for.
A
Some
of
it
a
lot
around
enhancement,
workflow
Jeremy
Rickard,
has
been
picking
up
a
lot
like
has
been
working
on
developing
tooling.
That
might
help
a
good
chunk
of
it
will
probably
become
more
public
here
soon.
Once
a
enhancements
meeting
is
set
up
under
cigar
ch
I
can
I
can
loop.
You
into
that
conversation
too.
That.
A
E
E
D
F
E
F
F
E
I've
seen
this
in
every
company,
usually
a
team
will
just
have
a
goal
like
fixed
rocks,
it'll
be
so
broad
and
so
big
that
they
can't
possibly
achieve
it
and
any
reasonable
like
short-term
timeframe,
and
so
they
need
to
break
it
down
so
that
they
can
make
incremental
progress.
So
that
might
be
what's
happening,
but
I
would
have
to
look.
I
did
see
some
of
the
118
goals
being
converted
into
items,
but
it
might
be
that
the
one
in
16
and
17
are
not
there.
Yet.
D
F
D
E
F
E
Asking
everybody
dumped
whatever
you
know
about
in
there.
That's
all
you
have
to
do
just
get
it
in
that
sheets
and
then
we
will
look
at
all
of
it.
Stephen
also
I
was
having
a
really
long
session
I
offered
to
help,
but
he
said:
I
have
to
go
through
all
of
this
stuff,
like
70%
of
it
can
probably
get
gone
or
just
we
reorganized
in
a
more
like
similar
way,
so
I
needed
to
check
in
with
him
on
that.
E
J
E
D
K
But
I
don't
think
I
know
you
I'm
going
here:
hi
I'm.
A
L
Go
for
it.
I
talked
to
Katherine
about
the
gender-based
moderation,
there's
a
pretty
good
and
proposal
out
there
for
it.
I
started
working
on
it
and
I
hope
to
have
it
finished
in
the
next
three
to
four
to
two
three
weeks
at
least
my
goal.
My
time
would
hope
to
have
a
PR
open
in
like
two
weeks
time,
depending
on
how
workers,
but
since
we
are
in
Germany
I
four
days
now,
free
time
where
which
I
can
spend
on
this
particular
issue,.
A
J
Yeah
I
did,
let's
just
talk
about
slack
for
a
little
bit,
I
feel
like
with
Katherine
moving
on
that
we
should
prob
like
we
should
probably
have
like
an
actual
sub
project.
Meeting.
I
just
want
everyone
to
keep
an
eye
out,
especially
people
in
Asia
in
Europe.
We
will
definitely
need
to
go
through
the
moderators
again
another
some
inactive
ones
that
we're
gonna
have
to
prune
out.
So
if
you
know
anybody,
preferably
if
they're
kubernetes
organizer
already
and
they
have
to
sit
and
slack
all
day
anyway
in
their
Europe
and
Asia,
that's
like
a
no-brainer.
J
So
if
you
have
anybody
in
mind
once
we
have
the
meeting
we're,
you
know,
we're
gonna
do
a
call
for
moderators
and
all
that
kind
of
stuff.
So
it's
a
good
good
way
for
people
to
contribute
if
they
have
to
sounds
like
anyway,
and
as
always,
anybody
who's
working
on
maintaining
the
tools
and
stuff
that's
gonna
be
need
to
be
a
thing,
but
it
sounds
like
Pierre
Marquis
you're,
making
good
progress
there
as
far
as
figuring
out
where
we
are.