►
From YouTube: 2023 03 30 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
All
right
and
welcome
to
Jenkins
documentation
officers
office
hours.
This
is
the
March
30th
edition
2023..
Thank
you
all
for
coming.
Today
we
have
myself
Bruno
over
up
and
and
mark
Waite
joining
us
in
the
in
the
meeting
and
for
our
agenda.
We
have
a
couple
new
blog
posts
to
mention
and
highlight
the
Jenkins
Awards
voting
period
is
now
closed.
A
A
And
finally,
this
is
something
that
we
were
going
to
discuss
last
week,
but
I
wanted
to
hold
off
make
sure
that
we
have
a
full
house
to
discuss
and
we'll
talk
about
chat,
gbt
and
documentation
and
where
things
are
at
a
little
bit,
there
are
good
and
bad
things
to
it
and
benefits
and
takeaways
that
we
can
really
use,
but
we'll
get
there
anything
else
on
the
that
we
need
to
put
on
the
agenda
today
or
talk
about
no
already
do
that.
A
A
A
So
yeah
so
super
important
to
take
a
look
and
update
things
as
necessary,
since
this
is
in
effect.
C
Yeah
and
most
of
my
mission,
sorry,
for
inserting
most
of
my
machines
are
using
Jenkins
through
Docker,
so
I
said,
but
I
I've,
almost
forgotten,
I
have
three
machines:
x86,
arm32
and
r64,
which
are
using
Docker
through
the
package
manager.
So
I
followed
the
tutorial
and
it
did
work
thanks
a
lot.
Mark
all
went
fine.
A
Fantastic
thanks
for
letting
us
know
Bruno
and
thanks
to
basil,
for
helping
make
sure
that
the
instructions
are
accurate
for
for
right
now.
A
Next,
up
on
the
blog
post,
so
Bruno
actually
was
has
is
in
the
process
of
writing
some
posts
about
Android
and
Jenkins.
This
is
the
first
one
and
from
what
I
read
Bruno
goes
into
a
description
and
a
brief
history
of
what
Android
and
Jenkins
relationship
is
look
like
or
lack
thereof,
how
they
work
together
and
how
to
make
Android
Builds
on
Jenkins
or
use
or
sorry.
C
C
Yeah,
we'll
talk
later
on
about
chat,
GPT
and
so
on,
but
first
of
all
the
image
you
see
there
is
a
work
by
an
AI
tool.
Called
mid-journey
I
had
a
few
credits,
so
I
just
has
something.
Could
you
do
something
about
the
bug
trade
mascot
and
the
Jenkins
Butler
and
boom
I
got
this
image?
Why
not?
They
are
again.
That's
cool
and
I.
Don't
have
any
more
credits
for
me
Johnny,
so
you
won't
see
any
other
of
my
assisted
creations
and
another
thing
about
chat.
C
C
A
A
This
is
fantastic,
though
Bruno,
it's
a
really
lovely
backstory
and
the
insight
to
things
that
might
not
get
talked
about
or
discussed
on
the
and
Heron
Jenkins
documentation.
So
this
is
really
nice
to
have
and
I
think
opens
the
door
and
I
mean
you
said
it
yourself
in
this.
Does
it
sound
strange
enough
for
appealing
enough
to
you
to
get
involved
like?
Let's
go,
that's
that's
the
kind
of
attitude
we
want
to
have,
and
you
know
bring
people
in
give
them
a
reason
to
come,
join
us
and
check
out
Jenkins.
A
So
this
is
this
sort
of
stuff
that
does
that
really
well.
Thank
you.
So
much
Kevin
yeah,
of
course,
all
right
great.
So
next
up
on
the
list
agenda
again,
the
Jenkins
Awards
voting
period
ended
on
March
28th.
So
that
has
closed
a
massive.
Thank
you
to
all
participants
and
nominees.
A
This
wouldn't
be
possible
without
anyone.
So
that's
crucial
and
the
award
the
award
winners
will
be
announced
and
presented
with
their
awards
at
cdcon.
This
coming
May
8th
to
9th.
So
look
out
for
that
and
yeah
more
to
come
on
that
the
manage
Jenkins
UI
changes.
These
are
changes
that
came
about
in
the
weekly
release
2.395,
and
this
change
essentially
simplifies
a
lot
of
the
settings
names
to
be
one
or
two
words.
Instead
of
manage
plugins.
This
is
plugins.
A
Instead
of
configure
tools
and
security,
it's
you
know,
tools
or
just
credentials
stuff
like
that.
So
the
idea
is
that
in
simplifying
the
settings
names,
it
just
makes
it
a
lot
easier
for
people
to
navigate
and
users
to
work
within
a
really
nice
really
clean
big
thanks
to
Jan
for
doing
all
that,
and
so
we've
had
some
updates
for
the
text
of
itself.
A
Of
course,
and
then
the
other
thing
that
we
need
to
update
are
screenshots
within
the
documentation
and
we
do
actually
have
some
contributors
working
on
that
as
we
speak,
I've
been
working
with
them
on
making
sure
that
the
screenshots
are
really
well
done
and
clear
and
high
quality
and
making
sure
that
things
are
aligned
with
the
existing
documentation
and
only
changing
what
we
need
to
change,
and
it's
been
really
great.
I've
had
a
lot
of
good
conversations
and
collaboration
with
newer
contributors
that
are
getting
started
with
Jenkins.
A
It's
really
fun
and
it's
a
really
nice
way
to
contribute
participate,
be
a
part
of
it
like.
We
always
talk
about
without
needing
to
have
expertise
in
any
area
so
and
on
top
of
that,
along
with
the
screenshot
updates,
I'm,
looking
I'm
looking
into
guidelines
and
best
practices
for
screenshots
and
image
images
which
I'm
going
to
collect,
put
together
and
compile
and
submit
it
as
a
pull
request
to
add
to
the
contributing
guide.
A
A
I
need
to
do
some
work
to
make
sure
that
everything
is
okay
there
and
that
we're
setting
everyone
up
for
Success
when
it
comes
to
adding
these,
and
that
will
be
like
I,
said,
I'll
submit
that
as
a
pull
request
and
I
will
post
in
the
community.jenkins.io
discourse
site
to
make
sure
that
that
conversation
is
being
held
with
the
rest
of
the
community.
A
A
Next
upon
me
gento.
So
there
was
an
update
to
the
books
pages.
Recently.
We've
had
folks
submitting
a
lot
of
new
books
to
the
jenkins.io
site,
so
we
have
a
new,
updated
Books
page.
We
have
a
disclaimer
to
explain
that
you
know
the
books
are
sorted
from
newest
to
oldest
and
we
have
removed
the
numbered
ordering
so
that
there's
no
mistake
of
ranking
this
is
really
important,
since
we
don't
want
to
appear
to
be
recommending
one
author
over
another
or
saying
you
know
this
book
is
the
best.
A
We
want
everyone
to
have
the
opportunity
to
make
those
decisions
on
their
own,
we're
here
to
bring
that
information
to
the
user
base
and
there's
definitely
going
to
be
some
guidelines
on
book
submissions
as
well
in
the
contributing
guide.
A
That's
another
thing
that
I'm
working
on
and
adding
again
it
will
be
part
of
a
separate
pull
request
that
will
also
submit
and
share
with
community
and
on
a
small
note
on
that
documentation,
submissions,
a
little
bit
of
formatting
and
a
couple
other
items
that
shouldn't
inherently
change:
how
anyone's
adding
content,
but
just
to
make
life
easier
for
everyone
when
it
comes
to
reviewing
those
pull,
requests
being
able
to
provide
really
clear
and
consistent
feedback
and
constructive
feedback
and
overall,
just
making
sure
that
that
collaboration
is
smooth
and
I.
A
I
feel
like
one
of
the
things
that
I'm
trying
to
work
on
now
is
more
responsive
communication
and
engagement
with
the
community.
So
that's
another
way
that
we
can
really
stick
to
that
and
help
and
engage,
while
also
making
things
a
little
bit
more
clear.
A
And-
and
there
was
a
recent
PR
to
fix
the
footer-
make
sure
that
it
stays
on
the
bottom
of
the
page,
as
it
is
here,
some
larger
screens.
It
displays
a
little
wonky,
but
it
was
something
that
we
I
emerged
need
to
be
reverted
now
we're
back
to
where
we
were
prior.
So
the
bottom
footer
here
is
actually
a
web
component
that
was
created
by
Gavin
Mogan.
A
So
the
original
pull
request
was
a
little
off
base
in
the
sense
of
where
the
change
should
have
happened,
but
we
resolved
it
reverted
back
and
everything
was
okay
and
if
anything
too,
thank
you
to
gymnac
who
for
working
with
the
user,
Mama
who's,
one
of
the
Google
summer
of
code
participants
he's
being
very
ambitious
and
looking
to
make
that
change.
That's
amazing!
We
want
to
see
that
sort
of
stuff
and
the
community
engagement
is
really
where
all
we
all
live.
A
So
thank
you
to
both
of
you
for
your
work
and
then
the
last
item
on
the
agenda
that
I
had
today
and
I
wanted
to
leave
some
room
because
I
feel
like
this
could
be
a
longer.
Conversation
is
chat,
GPT
and
where
that
stands,
and
what
we
can,
what
we
want
to
do
with
that
in
terms
of
documentation.
A
All
that
being
said,
I
am
personally
biased
against
it,
but
only
because
I'm,
a
writer
and
I.
This
is
my
well.
This
is
what
I
do
so
it's
a
little
different,
however,
being
a
writer
I
also
recognize
how
difficult
writing
can
be
and
how
it's
really
not
the
easiest
thing
in
the
world
for
folks,
if
it's
not,
you
know
something,
that's
constantly
being
done
or
reinforced
or
just
in
general
documentation
can
be
really
finicky
or
specific
and
yeah.
A
It's
it's
tough
saying
things
in
the
right
way
can
always
be
a
bit
of
a
challenge
even
for
someone
who's,
a
native
speaker
of
a
language
I
struggle
with
English,
constantly
no
surprise
here,
but
there's
a
lot
of
benefits
there
and
I
think
it's
important
to
really
be
aware
of
the
benefits
and
the
help
and
and
the
good
things
that
chat
GPT
can
provide,
while
also
recognizing
its
limitations
and
their
fact
that
there
is
a
user
element
to
chat
gbt,
and
it
can
only
go
as
far
as
the
person
putting
in
information
it
is
AI
is
capable
of
a
lot
of
autonomous
things,
but
at
the
end
of
the
day,
it's
not
all
on
itself,
that
is
on
the
user
if
they
are
creating
this
content
to
test
and
verify
and
make
sure
that
what
chat
GPT
is
putting
out
is
factually
correct.
A
One
of
the
things
that
we've
been
we've
noted
is
that
with
stack,
Overflow,
they've
actually
just
gone
ahead
and
say
outright
that
chat.
Gbt
is
banned
due
to
the
fact
that
it's
overwhelming
them
for
moderation
and
from
a
response
point
of
view
where
the
responses
themselves
are
worded
really
well
come
across
as
really
confident
and
unassuming,
but
there
might
be
something
wrong
with
that
and
then
and
it's
that's
on
the
onus
of
the
user
and
the
reviewer
to
check
and
make
sure
that
everything
is
correct.
A
But
we
should
make
sure
that
we're
submitting
things
that
are
factually
accurate
before
we
get
to
that
point.
All
that
being
said,
I
want
to
make
sure
that
this
is
open
and
explored
appropriately
and
I.
Don't
want
to
shut
anyone
down
or
say
we
shouldn't
use
it
like
I,
said:
there's
a
lot
of
benefits,
so
Mark
Bruno.
What
are
your
feelings
and
thoughts
towards
chat?
Gpt.
C
So
I
shot
myself
in
the
food
well
I've
been
experimenting
with
Chad
GPD.
These
last
weeks
at
first
I
was
really
reluctant
to
even
have
a
look
at
it.
I
didn't
have
an
account
anything
I
don't
want
to.
You
know.
Everybody
was
talking
about
chat,
GPT
and
before
that
everybody
was
talking
about
web
free
and
before
that
everybody
was
talking
about
nfts
or
blockchain
crypto,
as
no
I
won't
go
into
that
train,
but
I
saw
more
and
more
example
of
people
saying
oh
wow.
C
It
was
so
helpful
and
I'm.
You
know
it
took
me
only
two
hours
to
solve
a
problem
that
would
have
taken
me.
Maybe
two
days
or
something
so
I
said.
Oh
really,
and
then
I
saw
also
some
people
saying
this
thing
is
way
too
confident
and
it
says
bad
things
as
if
this
was
a
definite
truth.
C
So
I
was
intrigued
and
I
thought
to
myself.
Well,
let's
give
it
a
try.
So
I've
tried
it
for
several
things,
one
of
the
things
I've
used.
It
is
for
starting
a
new
subject.
For
example,
when
I
don't
know
much
I
just
have
the
very
beginning
of
an
idea.
Then
I'll
ask
it
how
to
to
reformulate,
to
change
it
and
to
give
me
some
other
ideas
and
then
I
have
something
like
a
pitch.
You
know
which
is
more
interesting
than
my
first
idea.
Other
things
are
also
a
help
for
writing.
C
Tutorials,
because
most
of
the
time
I
tend
to
forget
some
of
the
commands
I
entered
despite
using
the
history
on
Linux,
for
example,
and
this
thing
has
been
able
to
help
me
in
some
cases
when
I
was
you
know,
for
example,
I
start
on
the
Linux
machine,
where
I
already
have
lots
of
packages
installed
and
I
think
that
everybody
should
have
those
packages,
but
no
in
the
real
world
people
don't
have
these
packages
installed
and
chat.
C
Dpt
is
able
to
tell
me,
maybe
you
should
add
these
commands,
and
so
I
guess
this
space
for
slightly
better
tutorials
and
the
last
thing.
I
have
another
thing
too,
before
the
last
thing
lately
on
community
discourse,
Jenkins
Jenkins,
oh,
you
know
the
forum
for
Jenkins.
C
There
are
lots
of
questions
and
I
didn't
feel
okay
with
some
questions,
never
having
any
answer,
and
unfortunately
my
knowledge
of
Jenkins
is
not
that
big.
So
sometimes
I
wanted
to
help
and
get
some
answers
to
people
without
knowing
the
subject
so
I
asked
chat,
GPT
for
some
help
and
yeah.
Sometimes
it
gave
me
some
very
convincing
answer
that,
where
plenty
wrong
some
of
them
I,
was
able
to
spot
the
wrongness
of
it.
C
You
know
because
I
usually
test,
but
sometimes
the
question
is
so
complicated
or
so
far
away
from
my
knowledge
base
that
I'm
not
equipped
with
what
I
need
to
test
so
I
may
have
answered
a
few
times
with.
C
How
is
could
would
you
know
conditional?
Maybe
that's
a
lead.
You
should
explore,
but
one
time
I
totally
failed
and
I
didn't
change
the
message.
I
didn't
say
this
was
helped
by
chat
GPT.
This
was
generated
by
cha,
GPT
and
I
gave
an
answer
that
was
100
wrong
and
sounding
overconfident
and
somebody
spotted
it.
Thank
you
basil
for
that
and
yes,
that's
the
little
bit
of
the
thing.
C
I
get
that
if
you
want
to
use
jgbt
fine,
you
will
learn
some
things,
but
please
take
the
time
to
test
review
and
even
discuss
with
chatgpt,
because
sometimes
you
spot
something
fishy
and
you
tell
tajibiti
I,
think
you're
wrong
and
then
it
will.
We
think
reformulate,
make
other
proposals,
and
sometimes
it
will
guide
you
through
the
correct
answer,
but
sometimes
no
it
doesn't
know
everything
about
Jenkins
and
yeah,
so
I'd
say
maybe
not
ignore
chat
dpd.
You
could
give
it
a
try,
but
with
a
grain
of
salt.
A
Bruno
I
I,
like
I,
said
I
I,
agree
completely,
I
think
there's
a
lot
to
take
away
from
it
and
things
to
maybe
hold
back
on
or
be
more
critical
of,
but
there's
there's
good
with
it
and
there
and
it's
helped
you.
You
gave
examples
of
how
it's
helped.
You,
like
that's
invaluable
that
matters,
but
obviously
with
good
and.
C
Bad
everything-
and
you
know
sometimes
I-
have
some
bad
hair
day
and
you
know
I'm
all
sometimes
an
old
grumpy
man
and
when
I
want
to
answer
somebody
most
of
the
time.
What
I
would
write
is
not
as
benevolent
as
I'd
like
it
to
be
so.
Yes,
I've
also
used
it
once
or
twice
when
I
wanted
to
answer
Jenkins
Community
user,
and
it
was
not
kind
enough.
It's
not
what
I
feel
really
inside,
but
sometimes
you
you'll
know
yeah.
C
A
Thank
you
very
much.
I
appreciate
you
sharing
all
that
Mark
how
how
about
yourself.
B
So
I
liked
I
liked
the
argument
from
Gavin,
Morgan
and
spinnak
in
the
chat
session,
where
they
noted
it
may
be
undetectable
right.
The
use
of
the
use
of
chat,
GPT
May
in
fact
be
undetectable
because,
if
someone's
using
it
as
a
coach
or
as
a
help,
and
then
they
validate
the
steps
themselves
and
they
and
they
refine
the
steps
refine
whatever
it
created.
B
It
fundamentally
looks
like
human
writing
and
we
just
don't
have
the
tools
to
say
you
were
assisted
by
a
bot,
because
we
can't
tell
the
difference
right
to
Bruno's
point
of
Turing
test
right.
If,
if
Alan
turing's
assertion
was,
if
you
can't
tell
the
difference
between
the
computer
and
a
human
being,
you
you,
you
can't
tell
the
difference,
and-
and
so
this
case
it's
that's
real-
now,
I'm
still
worried.
B
B
If,
if
the
machine
is
if
machines
are
submitting
answers
and
you're
relying
on
the
skills
of
a
subject
matter
expert
like
stack
Overflow,
does
and
like
we
do
it's
very
easy
to
see
that
humans
validating
those
steps
are
going
to
take
much
take
much
longer
than
the
machine
that
created
the
steps
the
that
imbalance
will
overwhelm
so
so
I
think
I.
Think
it's
fair
for
us
to
have
a
Paul
I
think
it
would
be
fair
for
us
to
have
a
policy
that
allows
us
to
do
what
they
say,
which
was
Kevin.
B
If
you
go
back
to
that
one
where
they
at
the
bottom
of
the
stack
Overflow
page,
they
say
moderators
are
allowed
to
to
suspend
for
up
to
30
days.
If
someone
is
copying
and
pasting
GPT
content
onto
the
site,
it
may
be
that
we
say
we,
we
broaden
it.
Instead
of
saying
GPT
content,
we
say
content
of
questionable
validity.
Validity
are
content
which
has
because
it's
it's
not
so
much.
The
problem
with
for
stack,
Overflow
I
think
is
not
so
much
that
they
they
that
it
was
generated
by
machine.
B
It's
that
it
damages
The
credibility
of
the
site
by
its
mere
existence.
Right
and
and
if
we
look
at
something
and
say
we
had
a
chat,
GPT
generated
documentation,
pull
request
to
jenkins.io,
not
long
ago,
we
looked
at
it,
reviewed
it
it.
It
was
phrased
marvelously.
Oh
my
sakes,
it
was
well
phrased,
confident,
well
stated
and
good
content,
except
for
the
parts
that
were
completely
wrong
and-
and
that
was
the
dismaying
thing
it's
like.
B
Oh
my
sakes,
all
of
the
hints
that
I
would
usually
use
to
detect
this
might
be
wrong
lack
of
confidence
in
the
phrasing
or
or
incorrect
tenses
on
verbs
or
whatever,
whatever
hints
might
have
been
there
for
me,
were
not
there,
and
the
only
check
I
had
as
a
subject
matter
expert
was
to
be
sure,
I
validated.
Every
single
item
that
was
written
there
now
now
that
that
document
had
it
been
right,
would
have
been
exactly
the
right
thing
to
merge,
but
if
it
had
it
was
given
that
it
was
wrong.
B
It
would
have
been
incorrect
to
merge
it
because
now
we've
got
something
published
as
authoritative.
That's
just
wrong
right!
So
now,
I've
I've
said
an
awful
lot.
The
idea
is
I
think
it's
healthy
to
have
a
policy
that
says
we
expect
content
to
be
good
quality
and
we
reserve
the
right
to
ban
people
who
submit
poor
quality
content
and
we've
seen
poor
quality
content
coming
from
chat,
GPT
generated
answers.
C
Oh
okay,
I
see
all
the
problems
with
chat,
DBT
and
AI
tools
for
Jenkins.
The
first
one
is
that
if
people
get
their
answers
from
chat
GPT,
they
may
never
tell
write
it
down
everywhere
on
you
know,
on
the
web,
so
on
on
Jenkins
or
whatever.
So
the
answer,
if
it's
not
already
somewhere
in
the
documentation,
will
be
lost
forever
and
that's
a
pity
for
the
Jenkins
project.
C
The
other
thing
is:
if
we
don't
manage
to
spot
the
shot
GPT
generated
and
it
makes
its
way
into
the
documentation,
then,
as
you
said,
Mark
this
will
be
a
new
source
of
Truth,
which
is
wrong,
which
is
completely
wrong
and
then
the
next
generation
of
chatipity
will
be
trained
on
that
wrong
data,
and
so
it
will
degrade
over
time
and
it
will
worse
and
worse
and
worse
and
that's
a
problem
for
me.
B
A
good
point
on
the
the
training
Source,
because
so
I
asked
Google
bard
a
chat,
GPT
competitor
to
describe
how
to
adopt
a
Jenkins,
plugin
and
I
was
thoroughly
impressed
because
it
did
a
good
job
of
quoting
from
the
Jenkins
adopt
a
plug-in
page,
except
for
the
pieces
that
it
got
wrong.
Yeah
and
the
second
or
third,
it
offered
three
variants,
and
the
second
and
third
variant
were
better
than
the
first
variant,
but
I
had
to
as
a
subject
matter,
expert,
evaluate
that
content
and
and
decide.
B
Okay,
which
of
these
actually
is
stating
things
because
they
all
looked
very
good,
so
yeah.
Okay,
now
now
in
terms
of
a
I
I
like
Bruno,
your
observation
that,
given
that
we
can
expect
machine
learning
to
use
our
content
our
documentation
as
a
reference
as
a
training
Source
right,
we
hope
it
does.
Then
that
gives
us
even
more
incentive
to
want
for
the
material
to
be
accurate.
To
be
well
stated
to
be
to
be
all
those
things
and
an
item,
objective,
chat,
GT
GPT
helps
us
do
that
better
great,
but
the
the
goal.
B
Yeah
so
okay,
I've
I've,
thus
argued
both
sides
of
the
argument
and
that's
shameful
because
I
don't
have
a
I,
don't
have
an
easy
answer
on
on
I
I'm,
not
I,
know
I,
think
I
understand
why
stack
Overflow,
Bandit
I
think
it's
a
it's
an
unhealthy
thing
for
them
to
and
potentially
for
us.
If
we
became
overwhelmed
by
chat,
GPT
answers
or
jet
chat,
GPT
based
based
pull
requests,
we
would
have
to
say
outright
band.
A
I
think
if
you
go
ahead,
wow
sorry
I
was
just
gonna,
say:
I
think
it's!
It's
also
something
to
keep
in
mind
com,
looking
at
a
pull
request
versus
a
community
response
or
Forum
post,
or
something
like
that,
because
the
pull
requests
we
at
least
have
the
opportunity
to
review
and
check
that
and
stuff
before
it
gets
posted,
whereas
the
community
response,
it's
like
it's
instantaneous
and
it's
yeah
that
we
can
verify
in
the
information.
A
If
we
have
the
opportunity
to
not
so
much
if
that
opportunity
never
arises
so
there's
there's
definitely
use
for
it,
I
think,
but
it's
it
has
to
be
with
the
understanding
that
it's
not
perfect
and
100
accurate
every
single
time
and
that
you
do
need
to
as
a
user,
really
make
sure
that
what
what
is
happening
is
correct.
So
yeah.
B
Gavin's
one
of
Gavin's
Gavin's
points
in
the
chat
channels
was
that
as
a
pull
request,
submitter
I
am
responsible
for
the
accuracy
of
my
content,
no
matter
what
source
generated
it.
It's
ultimately
going
in
my
name
and
therefore
I'm
responsible
for
accuracy
of
that
content
that
didn't
that
still
doesn't
resolve.
My
worry
that
yeah,
but
a
big
organization
like
stack
Overflow,
was
found
that
their
their
moderators
were
being
overwhelmed
by
this
and
and
it's
I
I,
don't
have
a
solution
for
that,
but
I
I
think
it
may
just
be.
B
We
put
into
a
policy
statement
that
we
are
allowed
to
ban
people
if
they're
if
they
are
generating,
non-useful
or
or
poor
quality
content,
and
that's
that's
a
that's
a
policy
that
could
live
independent
of
any
AI,
because
if
we
get
junk
junk
pull
requests
from
hacktoberfest,
we
ban
them.
If
we
get
junk
pull
requests
from
Google
summary
of
code
contributors,
whether
they're
generated
by
a
bot
or
not,
we
ban
them
right.
We,
we
are
not
shy
about
banning
people
who
waste
our
time
with
junk
right.
A
And
yeah,
and
especially
where
Chachi
PT
has
a
lot
more
moderators
available
to
do
that
moderation,
it's
it's!
It's
telling
that
they're
just
outright
saying,
don't
even
think
about
it,
so
yeah
yep,
yeah.
A
A
Even
if
we
put
that
policy
in
place,
it's
still
something
that
can
be
discussed
at
a
later
point
in
time,
but
more
to
come
on
that
and
we'll
we'll
come
back
to
it.
Thank
you
very,
very
much
for
joining
today
appreciate
it.
The
video
will
be
available
24
to
48
hours
and
we'll
see
you
next
week.
Thank
you
again
have
a
great
rest
of
your
day.
Thank
you.
Bye-Bye.