►
From YouTube: 2022 12 15 Docs Office Hours
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
Welcome
to
the
Jenkins
documentation
office
hours.
This
is
the
EU
US
edition
here
on
December
15th.
Today,
right
now
we
have
myself
markway
and
Bruno
varactan
joining
us.
Thank
you
for
joining
us
and
on
the
agenda.
Today
we
have
some
action
items.
A
We
are
looking
to
focus
on
a
couple
different
topics
going
into
the
new
year
and
some
blog
posts
that
just
came
out.
We
have
a
lot
of
ideas
and
discussion
topics
for
the
December
newsletter.
This
is
going
to
be
a
recap
of
Jenkins
over
the
last
year,
so
we
want
to
make
sure
that
we
highlight
as
much
and
as
many
great
things
that
we
were
that
were
accomplished
this
year,
as
we
can
several
different
topics
and
we
have
some
a
lot
of
ideas
already
for
what
we
can
include.
A
So
we
want
to
have
a
bigger
discussion
with
the
community
at
large
and
see
what
other
people
are
thinking
of
or
what
they
might
want
to
see,
and
it
goes
from
everything
from
platform
modernization
itself
all
the
way
to
the
advocacy,
Outreach
sponsors.
A
Every
facet
of
Jenkins
is
something
that
we
want
to
highlight
in
this
case
and
then
the
last
few
items
we
have
on
the
list
here
we
do
have
another
LTS
coming
up,
that's
going
to
be
released
in
January
on
the
11th
there's
going
to
be
a
break
due
to
the
holidays
at
the
end
of
the
month.
So
a
little
bit
of
delay
there,
but
just
yesterday
the
RC
release
candidate
has
been
shared.
It's
ready
to
test
it's
good
to
go.
A
A
A
There
will
be
lots
to
discuss
on
that
at
a
later
point
in
time,
but
that
is
something
that
we're
working
on
and
then
finally,
just
the
a
couple
blog
posts
or
other
pull
requests
that
we've
had
come
up
recently
that
are
really
interesting
and
like
to
have
discussion
around,
since
they
do
address
a
couple
of
things
that
impact
Jenkins
as
a
whole,
so
anything
that
I
might
have
missed
or
anything
else
that
anyone
wants
to
add
to
the
agenda
today.
A
You
cool
all
right.
Thank
you
very
much.
So
first
things.
First
on
the
afternoon
items
right
now
we
are
working
on
a
project
to
go
through
any
of
the
tickets
that
have
been
created
in
jira
in
the
website
category.
These
are
issues
that
were
submitted
regarding
the
Jenkins
site,
documentation
other
parts
of
it
like
that.
A
However,
they
are,
for
the
most
part,
older
and
potentially
have
been
actioned
on
since,
even
though
the
ticket
might
not
have
been
updated
so
right
now,
what
we're
doing
is
we've
Alex
Fridays
has
created
a
GitHub
ticket
for
that
to
go
through
and
review.
Mark
and
I
have
been
going
through
the
list
of
remaining
issues
finding
out
what
can
be
closed.
A
What
doesn't
need
to
be
there
what
still
might
be
relevant
and
what
we
can
do
to
you
know,
move
that
migrate
it
into
the
GitHub
so
that
we
can
track
everything
properly,
get
the
progress
going
and
you
know
make
those
make
that
information
just
steadily
available
and
and
where
it
should
be.
That'll
also
help
us
Focus
everything
into
one
place,
as
opposed
to
being
split
between
jira
and
GitHub,
so
benefits
all
around.
A
A
The
holidays
are
going
to
include
time
off
for
a
lot
of
folks
around
here,
but
that's
something
that
will
work
together
on
as
I'm
taking
over
from
Mark
for
documentation
officer
for
Jenkins,
we'll
be
working
together
to
get
to
that
point,
and
once
we
have
that
going
we'll
be
able
to
provide
some
more
information.
A
Oh
cool
I
mean
Mark,
wanted
to
add
that
there
was
only
70
issues
remaining
on
the
website
project,
so
we've
been
able
to
close
out
a
lot
I
think
there
I
at
least
looked
through
100
or
something
and
I
know
Mark
had
looked
through
more
so
we've
got.
A
We've
done
a
lot
of
work
on
that
already,
even
though
it's
only
been
a
couple
weeks,
which
is
great,
and
then
we
had
a
few
blog
posts
that
were
published
recently,
one
the
first
one
here
is
regarding
the
Google
summer
of
code
mentorship-
and
this
was
written
by
jean-mark
lesson
and
just
goes
over
the
idea
of
being
a
mentor
for
Google
summer
of
code
and
other
projects
and
programs
that
we
work
with.
She
go
to
Africa
Richie
stuff,
like
Oktoberfest.
A
Being
a
mentor,
is
really
really
important
and
helps
push
these
along.
You
get
to
feel
like
you
were
contributing
helping
people
you
get
to
flex
your
knowledge
if
you're
a
mentor
and
it's
not
a
full-time
commitment.
It's
a
smaller
commitment
that
we're
looking
for
not
talking
full
day
dedication
or
anything
like
that.
You
can
see
here.
A
We've
got
about
five
to
eight
hours
per
week
and
that's
you
know,
that's
doable
for
a
lot
of
folks,
but
for
mentorship,
it's
a
really
crucial
part
of
all
the
projects
that
we
work
in,
and
we
want
to
make
sure
that
we
can
share
that
with
people
potential
mentors
existing
users
that
maybe
have
not
thought
about
this
sort
of
thing
before
and
new
users
that
are
getting
into
Jenkins
and
contributing
a
lot
you
know
recently,
especially
we've
got
new
release,
leads
there's
a
lot
of
people
joining
up
and
with
hacktoberfest
now
coming
gone,
we've
had
a
ton
of
new
contributors
that
may
be
interested
so
definitely
share
this
out
as
much
as
you
possibly
can
make
sure
that
you
know.
A
A
A
Users
of
Jenkins
won't
be
affected
in
the
same
way,
but
jfrog,
who
we
want
to
thank
as
a
continuing
sponsor
of
Jenkins,
wants
to
perform
some
maintenance
just
to
make
sure
that
everything's
working
properly
for
artifactory.
This
will
look
like
six
hours
of
downtime
between
I
think
it's
11,
A.M,
Israel
or.
B
A
And
we'll
also
the
Jenkins
infrastructure
status
page
will
also
be
updated
with
that
downtime
window.
So.
B
Click
that
link
Kevin,
so
we've
got
it
in
the
in
the
there
we
go
notice
that
it
it
says,
hey
here's,
the
here's,
the
status
and
as
that,
as
that
outage
resolves,
this
page
will
be
updated
to
show
what
the
resolution
time
was
perfect.
Great.
A
Is
there
any
other
place
that
they
might
that
this
might
be
relevant
to
I
know?
We
have
the
community
thread
also
talking
about
it,
and
we
were
talking
earlier
about
making
sure
that
the
tweets
and
other
notices
are
set
up.
Is
there
any
other
communication
or
Avenue
that
we
need
to
be
aware
of
on
that
Mark?
The.
B
The
advocacy
Sig
meeting
earlier
today
recommended
two
additional
places
that
Jenkins
CI
GitHub
organization
and
the
Jenkins
info
GitHub
organization
and
I
submitted
pull
requests
to
those
two.
So
so,
if
they're
merged,
then
those
pages
will
be
updated
as
well:
wonderful
and
if
they're
merged
tomorrow,
that's
already
Friday
before
it
before
the
Sunday
of
the
outage.
So
that's
that's
quite
good.
A
And
yeah,
okay,
following
that,
we
did
publish
our
November
newsletter
just
a
couple
weeks
ago
or
on
December
5th.
So,
just
again,
our
monthly
newsletter
highlighting
November
for
Jenkins
a
lot
of
the
governance
updates.
We
had
our
elections,
security
updates,
infrastructure
updates,
again
standard
of
what
our
newsletter
is
now
meant
for
and
again
this
is
a
little
bit
less
than
what
the
year-end
recap
will
be.
A
It's
gonna
be
a
massive
post
comparatively,
but
a
lot
of
wonderful,
wonderful
updates,
a
lot
of
great
information
and
once
again,
just
a
wonderful
way
to
highlight
our
community,
our
users
and
anyone
that
you
know
is
part
of
the
Jenkins
project.
B
C
C
I
will
do
my
best
and
of
course,
each
time
I
think
it's
just
about
perfect
and
then
the
review
begins,
and
so
many
people
Point
your
finger
at
all
the
mistakes
I
made.
But
that's
perfectly
fine
with
me.
A
It's
Community
effort
and
I
feel
like
everyone's
putting
it
together.
So
it's
it's
on
everyone-
Bruno,
not
just
you
but
yeah,
and
and
as
an
aside
on
that
too,
for
the
December
newsletter
since
there's
gonna
be
so
much,
and
since
we
want
to
make
sure
that
a
lot
of
these,
if
not
all,
of
these
topics
are
at
least
mentioned,
highlighted
to
some
degree
I'm
going
to
be
looking
through
it
very
carefully
myself
and
reviewing
it
along
with
Mark
to
make
sure
that
everything
is
good
to
go
on
that
one.
A
So,
ideally,
you
won't
have
to
worry
about
as
much
of
that
in
this
case
since
I'll
be
helping
you
out
and
working
on
it
as
well,
and
but
for
me
it's
a
lot
of
making
sure
like
it's
it's.
What
I
want
to
do
is
make
sure
that
these
topics
are
put
on
there.
A
So
if
you
know,
if
Damien
provides
a
platform
update
or
you
know,
I'm
providing
the
documentation
update,
there's
a
lot
of
different
things
that
could
be
in
different
places,
topics
that
might
you
know
be
coinciding
with
other
topics
or
other
ideas,
but
at
the
end
of
the
day
we
just
want
to
make
sure
everything's
sorted
properly
and
connected
and
makes
sense
and-
and
you
know
most
importantly
highlights
what
we've
been
able
to
do
in
Jenkins
over
the
last
year.
So.
A
Yeah
and
yeah
and
again
like
this,
is
a
big
one.
There's
a
lot
of
information,
that's
going
to
be
there
so
I'm!
This
is
pretty
much
one
of
my
main
focuses
for
the
next
week
or
so,
and
you
know-
and
obviously
we
might
not
have
it
published
before
the
end
of
the
month,
because
it's
a
monthly
yearly
recap
so
that
might
come
in
that'll
come
in
January,
but
between
now
and
the
publishing
date
I'm
here
for
anything
that
you
need
okay
and
then
the
last
blog
post.
A
That
we
want
to
look
at
here
is
something
that
basil
crows
has
just
put
together
for
us,
which
is
really
nice.
But
this
is
about
the
Jenkins
plugin
development
and
that
fact
that
we
now
require
Java
11
as
the
minimum
requirement
for
Jenkins.
So
this
is
to
address
concerns
issues,
questions
any
kind
of
General
apprehension
about
it.
A
Basil
has
done
A,
really
lovely
job
and
put
this
together
with
charts
links,
really
good
examples
and
logic
and
reasoning
behind
a
lot
of
these
changes,
and
what's
going
on,
this
was
just
published
a
few
minutes
last
hour,
so
very
new
to
the
blog,
but
very,
very
important
in
addressing
some
questions
and
concerns
that
folks
have
had
over
the
last
recently.
B
Yeah,
so
could
you
go
back
to
that
graph,
Kevin
yeah,
of
course,
up
that
one
that
one
that
little
thing
on
the
right
is
a
point
of
dramatic
Pride
notice
that
the
red
line,
Java
11,
is
greater
than
the
green
line.
Java
8..
So
we
have
data
that
says
that
Jenkins
users
are
in
fact
switching
to
Java
11..
Now,
if
you
look
at
the
slope
of
the
curve
there,
it's
quite
similar
to
the
slope
of
the
Java
8
adoption
curve.
B
So
so
it
gives
us
good
hope
that
we're
going
to
see
Java,
11
adoption
continue
now
I'm
even
more
excited
by
that
Java
17
curve,
because
that's
a
much
steeper
slope
than
previous
next-gen
jdk
adoption
curves
right
when
during
the
jdk
11
period,
you
see
the
early
parts
of
the
Java
11
thing.
The
slope
of
that
curve
is
almost
dismaying.
B
C
I
wasn't
there
in
2018
2019
when
the
switch
to
Jetta
11
started,
but
I
have
the
feeling
that
everybody
in
the
core
European
team
and
in
the
infra
team,
is
pushing
for
the
adoption
of
GDK
17,
so
I
think
it's
a
first
in
the
history
of
Jenkins,
maybe
yeah
yeah,
that's
a
good
thing.
We're
almost
not
late
right.
A
Thanks
Kevin
yeah,
of
course,
thank
you
Mark
for
all
the
additional
contacts
that
really
helps-
and
this
is
really
great
to
see
and
especially
with
I,
know
the
Java,
17,
adaption
and,
and
so
far
it's
been
really
really
reassuring
and
really
giving
us
the
results,
we're
looking
for
fixing
a
lot
of
things
and
making
life
easier
so
that
that
last
little
curve,
like
you
said
that
steep
gradient
is
really
nice.
A
Let's
see
because
great
so
so
now
that
we've
gotten
through
the
action
items,
just
we
can
go
over
the
December
newsletter
topics,
ideas,
Mark
and
I-
put
this
together
recently
and
it's
been
coming
since
doc's
office
hours
as
well
last
week.
A
So
this
is
just
something:
that's
going
to
be
an
ongoing
project
for
the
time
being
as
we
move
towards
creating
it,
but
just
looking
through
this,
we
have
a
lot
of
different
topics:
platform,
modernization,
user
experience,
improvements,
development,
acceleration
website,
improvements,
localization
simplification,
our
Jenkins
governance,
Board
elections
and
officer
elections.
The
Outreach
and
advocacy
that's
been
performed
over
the
last
year.
Security
updates
we've
had
lots
of
those
infrastructure,
changes
and
updates
and
sponsor
contributions.
A
These
are
very
vast
and
cover
a
lot
of
ground.
Is
there
anything
that
we
could
add
to
this
list
in
terms
of
a
general
topic
or
here
to
highlight,
or
if
you
notice
anything
that
is
already
categorized
here
or
listed?
Is
there
something
you'd
like
to
see
for
it
specifically?
Is
there
something
that
you
know
maybe
looks
related
to
something
you
had
in
mind
or
and
isn't
there?
We
can
add
it
yeah
I'm
just
curious
to
see
what
everyone
else
might
think.
A
And
we
have
a
lot
of.
We
also
have
a
lot
of
content.
For
almost
all
of
these
things,
we've
had
blog
posts
about
Job
11
job
17..
The
system
D
was
a
big
change
over
earlier.
In
this
year
we
have
a
blog
post
for
and
then
this
the
more
General
topics
stuff
like
back-end
dependency
and
front
end
dependency,
updates,
making
sure
that
we're
staying
at
the
Forefront
of
that.
B
A
C
B
Make
the
translation
easier
for
Bruno
Bruno?
Is
there
any
guidance
you
want
to
give
in
terms
of
how
we
lay
out
that
Google
doc
so,
for
instance,
I'm
tempted
Kevin?
If
you
jump
up
to
the
sort
of
the
topmost
on
the
required
Java
11
support,
Java,
17
and
system
D
migration
I'm
prone
to
embed
links
to
to
more
details
into
each
of
those
saying
look
here:
is
it
okay,
if
they're
embedded
as
hyperlinks
or
does
that
make
your
experience
doing
the
ASCII
doc
awful.
C
No,
no,
that's
fine,
that's
okay,
lists
and
embedded
links
is
fine
with
me.
Okay,.
B
A
A
Yeah
either
way
and
yeah
and
I
think
and
as
Mark
now.
This
is
something
I
just
thought
of.
As
far
as
all
these
items
go
when
we,
when
we
point
them
out
on
the
newsletter,
should
we
look
to
keep
it
brief
and
keep
it
to
a
few
sentences
for
each
item
since
there's
going
to
be
a
lot
or
indicate
like
obviously
there,
where
we
have
the
blog
post,
we
can
link
to
it
and
share
that
and
let
that
do
a
lot
of
the
talking
for
us.
B
Yes,
so
for
me,
I
think
brevity
will
be
useful
here.
I
would
assume
even
more
important
is
that
we
want
some
intermixed
images
scattered
throughout
this
thing,
so
that
people
have
the
visual
relief
of
breaking
and
breaking
a
large
block
of
text
with
with
pictures
of
something.
So
it
may
be
a
Java
for
the
ux
improvements,
those
those
should
be
UI
screenshots
for
I
was
thinking
for
the
pipeline
steps
documentation,
improvements,
screenshots
of
the
page
for
for
some
of
the
others.
B
It
may
the
vision,
presentation,
I
think,
for
instance,
if
Cloud
bees
is
willing
to
allow
public
access
to
the
devops
world
recording.
We
should
embed
the
link
to
that
video
or
even
better
get
their
permission
to
put
it
on
YouTube
in
the
Jenkins
account.
So
then
it
then
it
gets
registered
right
in
the
page
as
a
nice
clickable
clickable
link.
So
those
kind
of
things
for
me
are:
are
they
they
improve
the
chances
that
people
will
read
it?
B
The
other
piece,
I
guess
with
something
this
long
is
we
probably
better
start
with
a
table
of
contents,
so
that
people
can
read
the
summary
of
hey
here's
this
this
this?
This
and
now
maybe
another
question:
do
we
have
too
many
themes
so
count?
Could
you
help
me
with
a
quick
count
of
the
themes
Kevin?
It
looks
like
there's
at
least
12
or
15.
B
C
With
the
main
topics,
and
then
they
go
in
Greater
details,
I
think
of
the
pine
64
newsletters
that
are
read
earlier
these
days.
So
maybe
we
could
have
less
subjects
in
the
first
part
and
then
maybe
do
something
bigger
later
on
in
the
documentation,
just
a
suggestion.
I'm,
not
sure
that
would
be
a
good
idea,
though.
B
But
so
how
does
the
tldr
concept
in
the
prime
newsletter
work
so
they
do
a
one
sentence
series,
a
series
of
one
sentence
items
or
how
does
it
work?
No.
C
A
I
think
it'd
be
more
something
like
in
2020.
Peter
Jenkins
was
able
to
do
X,
Y
and
Z,
and
a
big
thanks
to
everyone
that
helped,
maybe
like
one
or
two
other
ideas
that
you
want
to
share
in
that,
and
then
everything
would
be
just
kind
of
formatted.
After
the
fact
at
least
I,
don't
know
how
it
works
with
Pioneers
one
I
just
know:
I've
seen
some
tldrs
like
that.
B
A
Yeah
I,
like
that,
a
lot
personally
I
think
that
would
be
a
really
good
format
and
especially
where
now
you
can
just
kind
of
list
everything
out
as
you're
going
through
it,
and
it's
okay,
that
it's
as
long
as
it
is
because
you've
already
got
this
here,
you
can
jump
to
where
you
need
to
be
if
we
set
it
up
like
that,
yeah.
No,
that's
a
that's
a
good
I
like
it
a
lot
personally
and
yeah.
A
A
A
Okay,
yeah
I
know
Mark
and
I
have
gone
over
this
list
a
handful
of
times
and
we're
looking
for
any
other
additional
input.
Ideas
stuff
like
that
Bruno
as
far
as
the
stuff
that
you've
been
working
on
I
know
that
you're
leading
the
some
of
the
platform
Sig
meetings
and
stuff
like
that,
is
there
anything
that
you'd
want
to
make
sure
is
listed
here
or.
C
Love
to
but
I
think
I
would
have
to
discuss,
maybe
with
Damian
about
that.
But
I
have
a
few
subjects
about
Docker
images
for
the
agents
and
also
alternative
platforms
like
arm32
arm,
64.
I
think
those
kind
of
progress
we
made
this
year
could
or
should
appear
in
that
section,
but
I
have
to
discuss
that
with
Damian,
because
what
I
see
is
as
important
is
maybe
not
seen
as
with
from
other
people
as
important
it's
just
because
the
kind
of
things
I
like
which
is
not
the
case
for
everybody
so
we'll
see.
A
Okay,
perfect
yeah.
No,
of
course,
do
whatever
you
need
to
do
talk
to
Damian.
You
know
obviously
figure
out
what
you
what
you
want
to,
but
I
mean
if
we're
gonna
do
a
tldr,
something
like
that
where
we
are
listing
out
smaller
ideas.
I
like
we
can
include
more.
If
that's
the
case,
I
don't
want
to
overload
it
obviously
and
make
it
too
too
big
but
yeah,
depending
on
how
we
get
to
that
list.
Maybe
maybe
it's
worth
putting
that
in
there?
Maybe
that's
in
the
development
acceleration.
A
A
B
But
well
so
so
the
the
docker
ones
that
you
were
discussing
Bruno
I,
think
are
good
fit
under
the
platform
topic
up
above
they're
they're,
clearly,
clearly,
platform,
modernization
and
platform
platform
enhancements
right,
Docker,
Images,
new
platform
support
and
oh
actually,
let's
I,
get
regularly
reminded.
Instead
of
the
word
Docker.
Let's
use
the
word
container
yeah.
B
A
Okay,
cool!
That's
awesome!
Thank
you
very
much,
bro
yeah
that
sounds
great
I
like
yeah,
and
it's
I
like
the
different
perspectives
and
I
and
thought
processes,
because
even
if
one
of
like
Mark
Ryan
doesn't
think
it's
important,
it
might
be
very
important
to
the
people
that
are
not.
A
You
know
able
to
say
as
much
or
aren't
taking
a
minute
to
share
that
with
us.
So
I
think
that's
always
very,
very
valuable
to
discuss
and
figure
out-
and
you
know
at
the
very
least,
find
out
discuss,
decide
whether
or
not
it
is
so
yeah.
Thank
you
very
much.
A
Yeah
we
had,
we
had
some
website
improvements
like,
and
that
was
thanks
to
a
lot
of
the
work.
In
the
Google
summer
of
code
projects,
we
had
the
chico
Africa
contribution
contributions
constantly,
which
were
really
great
in
helping
us
with
revamping
some
of
the
screenshots
and
a
lot
of
the
inclusive
naming
stuff.
They
were
also
able
to
provide
new
examples
and
all
sorts
of
testing,
which
was
great
so
a
lot
of
that
stuff's
going
to
be
there
I
think,
and
we
have
the
blog
post
for
that.
A
So
we
can
always
link
to
that
directly.
As
far
as
some
of
the
website
stuff
goes
mark
would,
with
stuff
like
the
web
components
fall
under
this
too
I
know,
Gavin
was
working
a.
B
Lot
on
not
not
deployed
yet
and
I'm
not
sure
we're
going
to
get
them
deployed
by
by
end
of
year,
so
okay,
so
they
could
be,
but
but
actually
I
was
thinking.
We
might
successfully
eliminate
a
well,
no,
not
really
sorry,
no
I
take
it
back.
I
was
going
to
say
we
could
can
combine
website
improvements
under
Google
summer
of
code,
but
that
only
works
for
one
of
the
three
items
that
are
there.
So
that's
a
bad
choice.
B
A
Okay,
because
I
yeah,
that
sounds
good
because
I
feel
like
these
could
also
fit
into
like
user
experience,
improvements
or
something
along
those
lines,
because
that
does
affect
how
people
are
using
the
Jenkins
site
itself,
but
yeah
and
then
Alex
brandes
did
a
lot
of
work,
just
kind
of
getting
the
crowd
in
piece
going.
A
I
spent
a
lot
of
time
at
doc's
office
hours
earlier
this
year,
going
through
it
talking
about
it,
just
showing
what
is
possible
with
it,
which
is
really
great,
so
I
want
to
make
sure
that
that
is
highlighted
really
a
lot.
Obviously,.
A
And
yeah
we
can
table
that
for
right
now
this
document's
always
available,
and
so
is
getter
Matrix.
Any
other
chat
channels
that
you
want
to
throw
an
idea
in.
Please
like
message
me
or
notice
me
whatever
it
is
by
all
means
so
that
we
can
add
that
in
and
then
we
are
over
time
a
couple
minutes
so
just
to
kind
of
finish
things
up
again,
we
have
the
LTS
2.375.2
coming
that'll
actually
be
released
in
January,
but
we
have
a
lot
of
the
pre-work
done
right
now.
A
So
the
change
login
upgrade
guide
the
release
candidate
backboarding.
All
of
those
things
have
been
either
submitted
or
merged
already,
so
any
reviews
any
ideas
on
that
much
appreciated,
and
then
there's
been
discussion
about
the
pipeline,
Docker
plugin,
what
that
means
for
Jenkins
what
that
means
for
the
documentation.
It's
a
lot,
far
more
far-reaching
than
initially
thought.
So,
there's
going
to
be
a
lot
of
discussion.
A
That
won't
be
something
that
gets
resolved
until
January
the
very
earliest,
but
it
is
something
that
we
are
very
very
mindful
of
and
working
on,
because
this
can
affect
a
lot
of
people
in
different
ways
and
then,
finally,
just
a
quick
note
that
there
was
a
pull
request
that
Mark
had
made
suggesting
that
board
member
rules
can
be
modified
a
little
bit
right
now,
but
there's
five
board
members,
one
being
concierge
and
then
the
rest
are
elected.
If
the.
A
If
there
are
it's
more
than
fifty
percent
of
representation
by
a
company,
it's
not
allowed
so
just
discussing
ways
to
work
around
that
talk
about
ways
to
engage
people
and
get
them
on
the
governance
board
as
well,
but
something
we
can
talk
about
later,
no
worries
there
anything
else
and
we
wanted
to
discuss
chicken
mention,
if
not
I,
think
we're.
Okay,
we'll
end
things
here
and
the
recording
will
be
available
in
about
24
to
48
hours,
and
thank
you
so
very
much
as
always
for
joining
us
here.
A
We
will
have
a
section
next
week,
so
we'll
check
in
again
before
going
on
going
on
omia
for
a
little
bit
so.