►
From YouTube: Red Hat Enterprise Linux Presents (E21): Day in the life
Description
Are you considering a job as a developer? Have you ever wondered what it is like to work on Red Hat Enterprise Linux or its upstream projects? Then meet our guests as they discuss their experiences with Red Hat and developing open source software!
Follow us on Twitter
Eric: https://twitter.com/itguyeric
Chris: https://twitter.com/ChrisShort
#RedHat #RHEL #livestream
A
A
A
A
B
B
A
A
B
We
actually
planned
it
that
way,
because
we
wanted
to
demonstrate
what
it
was
like
to
be
a
systems
administrator
in
real
life
in
real
life.
It
never
fails
that
you
go
to
do
something
easy,
some
easy
maintenance
and
inevitably
you
have
30
days
in
a
month,
but
that's
when
that's
when
the
the
software
vendor
decides
to
work
on
their
stuff,
it's
at
the
exact
same
time
as
your
as
your
outage
window.
So
you
know
just
a
little
bit
of
real
life
on
on
the
show.
Yeah,
that's
my
story.
I'm
sticking
to
it!
B
Yes,
in
fact,
probably
more
nerdiness.
In
fact,
this
is
the
long
awaited
day
in
the
life
episode.
We've.
We've
we've
prompted
this
a
couple
of
times
on
on
previous
episodes,
so
I'm
really
really
excited
to
introduce
a
couple
of
amazing
folks.
In
fact,
I
will
let
each
of
you
each
of
you,
introduce
yourselves
and,
and
ladies
first.
C
Okay,
I'm
alexandre
fedora.
I
work
in
redhead
for
three
years
now
and
before
that
I
was
like
video
ambassador
fedor
contributor,
and
now
I'm
also
a
member
of
fedora
console,
and
my
primary
area
of
interest
is
building
the
infrastructure
for
real
development
building
the
workflows
and
the
processes
for
continuous
integration
inside
rel.
B
C
B
But
I
I
think
I
I
wasn't
intending
to
go
this
direction,
but
I
think
I
will
ask
that
question
what
what
is
the
culture
like
here
at
red
hat,
because
it
seems
it
seems
to
be
that
that
that's
that's
kind
of
the
big
thing
people
think
about
is
is
not
rel
or
security
or
a
hybrid
cloud
platform,
but
we're
known
very
much
for
for
our
culture.
So
how
does
red
hat
shape
up
and
how
does
how
does
that?
B
Compare
to
other
environments
you've
been
in
and
then
we'll
kind
of
backtrack
into
that?
You
know
how
you
got
started
and
things
that
and
and
one
other
quick
thing
if
you
are
watching
us,
live
we've
got
the
chat
open.
Please
by
all
means,
throw
your
questions
in
there.
I
would
love
to
get
your
all's
questions,
get
your
feedback,
and-
and
I
mean
they
are
here
for
you-
this
is
your
all's
hour.
So
definitely
preference
goes
to
to
live
questions
that
come
in.
D
D
We
were
already
quite
big.
According
to
some
other
colleagues,
I've
been
older
around,
I
think,
just
a
little
bit
about
a
hundred
thousand
people
and
now
a
lot
more
right
like
tenfold
or
more,
and
even
though
that
happened.
There
is
a
an
extremely
interesting
culture
of
communication
and
also
initiative
within
radar
in
general.
I
would
say,
although
there
are
many
differences,
because
at
this
point
where
that
has
so
many
you
know,
components
as
well,
which
is
what
I'm
used
to.
There
is
no
other
other
parts,
but.
B
D
General
there's
this
real
great
thing
about
communication
and
you
know
technical
knowledge
to
the
highest
level
everywhere.
Yeah,
it's
a
really
inclusive
culture.
I
would
say
at
least
that's
my
experience
of
the
little
bit
there.
I
guess,
but
I
I
maybe
feel
like
there's
a
lot
of
understanding
a
lot
of
sharing
you
know
within
within
our
walls,
even
though
it
makes
me
laugh
to
say
walls,
because.
D
So
one
of
the
defining
things
I
would
say
is
that
most
people
have
read
that
works,
probably
more
with
people
outside
the
product
than
the
people
reading,
at
least
in
the
development
department,
I've
I
spent
spend
so
much
time
upstream,
which
is
what
we
call
you
know
you
know
projects
whatever
they
are
mailing
based.
You
know
other
stuff
like
that,
irc
for
the
old
people,
or
whatever
slack
or
anything
today
like
most
of
my
life,
was
there
and
then
there
was.
D
C
Like
I'm
doing
this
thing
and
someone
else
will
do
the
talking
for
me,
it's
like
no
you're
doing
recording,
but
you
also
have
to
do
with
talking,
and
you
also
have
to
do
the
explanation
and
you
have
to
do
the
interaction,
because
all
of
that
is
still
on
you
and
you
need
to
own
it
and
you
you
need
to
own
the
topic
in
in
full.
So
you
cannot
hide
from
the
community
interaction.
It's
part
of
of
the
you
as
a
role
developer,
to
to
interact
with
the
community.
C
C
And
it's
just.
You
really
need
to
work
with
people
convince
each
and
every
person
to
try
this
out
and
to
get
on
on
board
with
this
change
and
so
on.
So
sometimes
I'm
really
like
it.
It
can
be
hard
you
know
to
to
make
such
changes,
but
it's
also
like
a
very
precious
thing.
In
red
hat
with
this
level
of
interaction
and
this
level
of
feedback,
and
we
with
real
development.
B
Well,
I
think,
to
prove
your
point.
You
just
have
to
answer
one
question:
I
mean
how
many
communication
tools
do
we
have
here
at
red
hat
and
I
think
the
answer
is
never
enough,
because
I
mean
I
have
an
entire
screen
on
my
mac
just
dedicated
to
just
communication
tools.
Just
so
I
can
keep
touch
with
all
the
different
teams.
B
Before
we
move
on
to
the
next
question
I
did
want
to
get,
I
did
want
to
kind
of
pick
up
one
other
thing,
because
you
came
to
red
hat
through
your
contributions
with
fedora.
So
I'm
I'm
kind
of
curious
what
what
it
was
like
working
working
elsewhere,
contributing
to
fedora
and
then
and
then
coming
to
red
hat,
to
continue
your
work
with
fedora.
What
was
that
experience
like.
C
B
B
Now
my
my
hobby,
I've
just
spent.
You
know
nine
hours
on
my
hobby.
What
do
I
do
so
if
it,
if
it
helps
I've,
I
recently
fell
in
love
with
dungeons
and
dragons
about
two
years
ago.
So
I
mean
if,
if
you're
looking
for
a
hobby,
that's
a
great
one,
especially
if
you're,
if
you're,
creative
and
you're
looking
for
a
different
outlet
to
kind
of
stretch,
those
those
creative
muscles
I
mean
I'm.
C
C
A
B
So
shifting
gears
a
little
bit,
how
did
you,
how
did
you
both
kind
of
get
into
the
the
developer
space
or
the
engineering
space?
However,
you
want
to
look
at
it.
Did
you
just
kind
of
stumble
into
it,
or
was
it
something
that
you'd
wanted
to
do
from
very
early
on
just
kind
of
tell
us
about
that
journey?
A
little
bit.
D
I
I
wanted
to
be
a
pilot,
then
I
started
wearing
glasses
and
I
decided
computers
were
my
thing
I
was
maybe
12
13.,
so
it
kind
of
was
early
on.
But
you
know
back
in
my
time.
Internet
was
not
the
thing
and
so
progress
was
you
know.
Whatever
book
you
could
find,
you
know
whatever
you
could
buy
and
then
university
you
know,
learn
this
thing.
Called
linux
learning
called
internet
from.
D
D
B
A
B
So
that's
that's
interesting.
You
said
you
left
mathematics
because
it's
kind
of
a
lonely
career
path,
but
development
I.t
can
can
be
pretty
lonely
as
well
did
did,
was
your
experience
different
was:
did
you
have
the
kind
of
interaction
and
collaboration
that
you're
looking
for,
or
was
that
something
you
got
here.
C
Yeah,
I
think
this
is
where,
like
the
the
feeling
might
be
different
for
people
who
are
doing
like
deep
development
in
one
specific
area,
but
I
believe
that
in
80
you
still
have
you
know
the
possibility
to
talk
more
with
people
around
they.
It's
like
it's
not
in
any
person
on
the
street,
who
will
understand
what
you're
doing,
but
at
least
like
not
a
single
person
right
so
in
mathematics.
C
You
really
do
have
like
your
scientific
advisor
and
maybe
two
colleagues
who
understand
what
you
what
you're
talking
about
like
in
in
the
whole
country
or
the
whole
world,
and
also
in
mathematics.
It's
about
it's
a
bit
too
strict
on.
How
do
you
interact
with
people,
and
I
mean
in
80
I
can
go
to
a
conference
and
present
a
thing
which
I
really
don't
know
about.
I
mean
I
want
to
state
a
question
and
I
want
to
engage
in
the
conversation
and
so
on
in
the
mathematics.
C
B
A
C
B
Yeah,
there's
there's
a
definite
culture
difference
there,
because
I
could
see
how
mathematics
would
be
closed,
whereas
open
source
kind
of
celebrates,
especially
with
with
the
onslaught
of
devops
and
agile
methodologies,
and
all
this
kind
of
things
that
hey
here's.
My
thing:
it's
it's
not
a
1.0
version,
so
you
know
it's
it's
half
broken.
But
what
do
you
think
it's?
It's
kind
of
celebrated
versus
versus
you
know
kind
of
shunned.
B
D
B
A
B
C
B
D
I
have
to
say
that
I'm
less
involved
heavily
in
upstream
communities
these
days
than
I
was
until
a
little
while
ago,
I've
been
getting
busier.
I
remember
somewhat
higher
level
of
work.
I'm
not.
I
think
I
have
one
package
still
that
I
own,
but
it's
I
own
it,
because
there
is
no
work
to
do,
and
so
that's
that's
easy.
D
I
still
have
a
couple
of
projects
of
mine,
very
small
things
around
the
early
stuff,
like
gs,
api
or
some
host
secret
stuff,
very
small
things,
very
small
things
that
don't
take
a
lot
of
my
time.
I
I
had
to
stop
working
on
the
big
ones,
because
I
couldn't
follow
them
well
enough
to
be
really
useful
anymore.
So
I
kind
of
on
the
sidelines
I
cheer
up.
I
follow
the
menu
list.
You
know
maybe
once
a
week
I
go
through
a
few
of
them
and
sometimes
I
surprise
someone
with
a
comment.
D
Like
hey.
You
said
nothing
for
six
months.
How
come
you
know
and
you
come
here
and
say
something
but
yeah.
The
extent
to
which
I
I
can
scale
is
limited
at
this
point,
but
I'm
still
having
a
ton
of
fun
following
up
on
the
you
know,
the
sidelines,
if
you
want
there's,
still
keep
tabs
on
all
the
projects
I've
been
contributing
in
the
past,
even
though
my
dad
would
say
anything
just
like
to
see
what
recording
happens
so.
D
C
I
guess
right
now,
I'm
not
doing
as
much
as
I
wish.
I
would,
and
I
do
have
one
package
to
maintain
in
fedora.
Is
it's
a
game?
Actually,
it's
a
mind
test
game.
I
several
years
ago
I
was
like
into
this.
You
know
blog
building
game
and
so
on,
and
but
I
stopped
playing
it
because
I
realized
that
playing
it.
Like
is
the
same
as
participating
in
open
source.
C
C
I
also
played
with
raspberry
pi,
and
I
have
a
even
library
to
switch
a
led
light
on
raspberry
pi
from
fedora,
like
turn
on
and
off
with
gpio
pin,
and
it
was
some
fun
experience
with
even
rebuilding
the
kernel
to
get
some
device
three
stuff
in
it
there
so
yeah
not
very
many
contributions.
I
guess,
but
some
some
interest
in
some
side
projects.
B
B
You,
you
could
kind
of
maybe
have
gotten
your
hands
in
a
little
bit
of
everything,
but
I
think
today
technology
is
just
so
vast,
there's
so
many
different
things
and
it's
so
complex
that
that
there's
there's
no
way
I
mean
I've
spent
a
decade
on
rel
and
and
now
I
work
on
the
marketing
team,
and
I
I
look
at
our
operating
system-
it's
just
like
yeah.
I
can.
Can
we
break
this
down
a
little
bit,
so
thankfully
we
have
pods
within
within
the
marketing
bu.
B
So
I
have
certain
areas
of
interest
that
that
I
focus
on,
but
it's
just
it's
so
vast
anyway,
not
to
not
to
jump
on
my
soapbox.
So
what
would
you
recommend
new
developers?
New
open
source
enthusiasts
learn
what
are
kind
of
the
things
that
you
deal
with
or
that
you
want
to
get
involved
with
or
that
you
think
are
are
coming
up.
That
will
be
important
to
the
industry.
B
C
Okay,
my
turn
now.
Okay,
so
what's
important
for
the
industry
or
important
for
rel.
So
if
we're
talking
about
work
in
in
distribution
of
kind
of
like
real
distribution,
then
obviously
like
fedora
is
the
way
and
you
once
you
get
how
we
understand
how
fedora
works.
You
get
the
rel
experience,
not
not
full
real
experience.
You
still
will
get
a
bit
of
surprise
how
huge
rail
is,
but
but
you
get
the
idea.
C
C
D
Guy
that
goes
behind.
You
know
every
single
new
thing.
I
would
say
that,
from
my
point
of
view,
you
should
really
I
go
through.
You
know
kind
of
a
logical
process,
maybe,
but
I
think
you
should
decide
early
on
whether
you
are
more
of
a
high
level
kind
of
guy
or
low
level
kind
of
guy,
because
they're
completely
different
thing.
D
D
B
D
D
I
really
need
to
figure
out
how
this
thing
works
and
then
I
kind
of
got
lost
in
the
rabbit
hole,
and
I
don't
remember
if
I
ever
ever
did
the
thing
that
I
started.
You
know
I
was
looking
for.
I
think
everyday
people
put
different
direction
by
the
end
of
it,
but
that's
the
thing
you
know
do
something
that
you
that
you
like,
and
at
least
that's
you
know
when
you
start
to
understand
how
things
work
and
from
there
on
you'll
find
you
know
the
right
path.
D
There
will
be
either
a
project
that
you
get
really
passionate
about
or
just
a
technology
without
being
you
know,
attached
to
a
specific
project,
and
you
can,
you
know
recover
experience
with
that
or
you
know
in
the
end,
each
one
has
a
different
path,
but
I
I
strongly
believe
that
you
need
to
do
something
that
you
like
doing.
Otherwise
you
know
it's
harder,
at
least
for
me,
it's
harder.
If
that
will
be
like
something
you
know,
there's
nothing.
D
Just
doing
a
job
for
money,
I
also
think
that's
perfectly
fine,
but
in
that
case
your
focus
will
probably
be
slightly
different,
won't
be
in
the
in
the
technology
itself.
It
will
be
something
else,
and
so
that
was
probably
something
you
should
decide
earlier,
whether
you
like
you
know,
I
love
you
know
coding,
you
know
for
coding
sake
or
if,
for
you,
it's
just
a
step
installed
to
something
else.
Some
people
are
very
excited.
You
know
dealing
with
the
management
of
the
project
or
the
product.
D
B
A
B
I
I
spent
years
as
a
systems
administrator
and
I
spent
years
trying
to
be
the
deep
low
level,
not
not
not
career-wise
but
technology-wise,
being
deep
in
the
code,
understanding
every
piece
of
the
operating
system
and
network-
and
that's
just
that's
not
me
where,
where
the
high
level
stuff
kind
of
makes
your
eyes
glaze
over.
That's
where
I
live.
Is
I
like
to
see
the
high
level
picture
and
it
took
me
probably
about
eight
years
of
my
career,
so
I
mean
I
was
close
to
30..
B
If
you
think
about
college
and
eight
years
in
in
the
career
field.
Before
I
realized,
I'm
a
generalist,
and
you
know
what
that's
okay,
it's
not
a
problem.
It's
it's
actually
a
strength,
and
so
it
took
me
a
few
years
to
to
pivot,
to
from
from
systems
administration
systems,
engineering
to
to
sales
and
now
to
marketing,
and
I
feel
like
I've,
finally
come
home.
So
take
it.
B
Take
it
from
me
and
in
my
years
of
experience
in
in
the
field
you
have
to
pivot
and
you
have
to
follow
what
would
excite
you,
because
otherwise
you're
you're
dealing
with
stress
you're
dealing
with
burnout,
and
if
you
don't
like
what
you
do,
I'm
I'm
sorry
I'm
not
financially
driven
so
there's.
If
I
hate
what
I'm
doing,
there
is
no
amount
of
money.
That's
going
to
make
that
better.
C
Do
you
really
want
to
bet
right
now
that,
like
this
profession,
if
this
job
will
survive
for
next
50
60
years-
and
you
want
to
plan
just
one
direction-
you
probably
want
to
try
it
and
like
get
some
experience,
but
it's
not
who
you
are
right,
you
you
are
yourself
you.
You
can
work
as
a
system
administrator
you're
not
limited
to
this
work,
you
you
can
like
explore
new
areas,
different
approaches,
you
can
invent
your
own
role
and
you
will
find
a
place
to
focus.
B
B
Now
they
were
probably
right
about
becoming
a
developer,
because
I
I
took
a
vb
basic
class
and
then
a
c-sharp
class
and
was
just
like
nope
and
then
literally
looked
across
the
hall,
and
there
was
a
networking
lab.
I
was
like
what
what
classes
do
I
have
to
sign
up
for
to
go
play
over
there.
They're,
like
oh
yeah,
we've
got
this
this
degree
field
about.
I
see
sorry,
I
chad
distracted
me.
B
B
C
C
A
A
I
am
a
solutions
architect
now,
but
deep
inside,
I
still
think
like
asus
7
yeah.
I
think
we
all
do
to
an
extent
right,
like
I
flip
that
switch
on
and
off.
Now,
though,
where
you
know
before
it
was
all
I
did
right,
like
was
just
just
admit
now,
it's
like
all
right.
I
got
a
sysadmin.
This
thing
I
forgot
to
marketing
that
thing.
I've
got
to
open
source.
This
thing
got
to
document
that
you
know,
like
all
these
skills
have
built
up
over
time
to
where
it's
like.
A
B
A
Right,
like
my
spouse,
has
no
idea
what
the
hell
I
do
like
technically,
but
she
knows
that
there's
lights
and
there's
a
camera
involved
and
that
kind
of
thing
right
like,
but
what
she
doesn't
realize
is
that
we
know
there's
things
happening
right.
You
know
we're
working
on
things
on
us,
however
downstairs
or
we're.
You
know
on
a
lab
and
you.
B
A
B
Yeah,
it's,
I
don't
think
it's
a
lack
of
love
for
systems
administrators,
it's
I
I
used
to
be
one.
I
spent
a
lot
of
years
as
as
a
sysadmin
and
there's
a
lot
of
parts
of
of
that
type
of
role
that
I
enjoyed,
but
in
the
end
it
just
it
wasn't
what
I
was
what
I
was
driven
to
do.
This
is
more
my
thing
and
in
fact,
the
the
systems
administration
work
that
I
do
nowadays
is
amazing.
I
get
to
basically
write
a
lab.
B
This
is
how
you
would
do
a
thing
if
you're
like
we
did
convert
to
real,
we
did
in
place
upgrades.
I
I
wrote
pretty
much
all
the
commands
based
on
documentation
on
other
people's
experiences
on
this
is
the
easiest
way
to
do
this
thing
we
want
to
convert
from
rel
seven
to
rel
eight.
This
is
the
easiest
way
to
do
it.
Does
this
fix
all
of
your
problems?
Does
this
take
care
of
every
use?
Use
case?
No,
but
this
this
covers
80
and
that's
that's
where
I
shine
and
what
was
great
was
we.
B
A
C
A
C
This
moment,
so
I
I
feel
like
it's:
it's
not
the
work
itself,
but
it's
some
impression
it
created
and
it
pulls
down
sometimes-
and
this
is
why
it's
evolving,
so
it's
not
disappearing.
Definitely
it's
just.
It
gets
renamed.
It
gets
introduced
in
some
different
way
and
so
on.
I'm.
I
wouldn't
like
say
that
we
should
get
rid
of
this
admins.
No,
but.
A
B
C
It's
it's
a
valid
work,
but
it
gets
some
evolution
to
to
get
away
from
that.
You
know.
Stereotypical
system
who
is
not
interested
in
anything
and
just
like,
doesn't
actually
do
anything
and
just
waits
for
his
pro
system
to
work.
It's
not.
The
good
kind
of
scissors
mean
and
we're
like
getting
involved
evolving
over
over
it
into
some
areas
where
you
actually
have
interest
in
some
development
of
your
systems
and
some
evolution
of
your
products,
and
so
on
so
yeah,
it's
it
it's
the
evolution
happens.
So
you
don't.
D
C
D
D
B
B
So
it
doesn't
matter
what
so
christian
says
that
the
term
is
considered
the
low-level
entry
job.
My
suggestions
is
that
it
should
be
changed
to
something
else,
because
today
sysadmin
are
more
like
sysops
and
not
just
admins.
That's
a
great
point
right
yeah!
That's
so,
and
I've
seen
different
I've
seen
different
cultures.
Different
companies
address
this
different
ways.
B
C
B
A
I
do,
I
think
you
do
too,
because
you
know
the
last
quote:
cis
admin
I
hired
was
actually
a
junior
role.
We
needed
a
junior
sys
admin
right
that
we
could
teach
and
kind
of
mold.
You
know,
take
your
deep
linux.
Knowledge
apply
that,
but
also
now
we're
going
to
add
on
to
that,
and
we
were
a
quote
devops
team.
So
you
know
we
need.
We
had
a
need
for
a
junior.
We
had
a
need
for
a
lot
of
seniors,
but
there's
plenty
of
gray
in
between
here
and
there.
B
A
B
C
You
cannot
understand
it
and
then
you
start
to
dig
in,
and
you
start
to
find
you
know,
connections
and
logic,
and
this
is
why
it
happened.
This
is
what
what
brings
it
and
then
you
start
to
untangle
things,
and
this
untangling
things
is
really
my
passion.
I
I
like
to
understand
it
and
to
explain
to
others
what
I
understood.
This
is
the
thing
which
I
really
enjoyed
explaining
to
people.
What
I
understood.
D
Feels
like
alexandra
is
into
debugging
the
organization,
I'm
more
on
the
programming
part
of
it.
I
guess
it's
I'm
as
a
as
a
team
being
a
pro
where
I
I
have
to
interact
with
a
lot
of
people
on
the
team
I
like
helping
out,
you
know,
more
junior
people
might
be
figuring
out.
What's
the
next
thing,
how
you
know
how
to
do
things,
but
also
there's
a
lot
of
part
of
my
job
is
connection
with
other
people
within
the
organization
within
rel
or
maybe
sometimes
also
outside
of
rail.
D
So
there's
a
lot
of
hello
is
basically
enabling
other
people
to
do
their
job.
I
would
say
at
this
point:
that's
my
probably
major
contribution
and
that's
what
I
kind
of
like
doing
at
this
time
in
my
career.
Sometimes
it's
frustrating.
Sometimes
it's
satisfying,
because
you
can
see
the
fruits
of
you
know
all
the
organizational
work
you
try
to
do
just
like
everything.
B
B
Looking
at
the
upcoming
features
and
then
figuring
out,
then
then,
to
christian's
point
I
get
to
put
on
my
sis
admin
hat
and
go
oh.
This
would
be
great
because
I
remember
this
time
where
I
had
this
problem
yeah.
So
now
this
feature
could
have
fixed
this
problem
with
like
three
commands
or
system
role
or
something,
and
then
it's
now
my
job.
It's
now
my
my
pleasure
to
then
go
out
and
tell
tell
our
our
sales
folks
tell
tell
the
community
to
tell
the
audience
at
this
show
hey
this.
This
feature
is
coming.
B
It's
it'll
help
you
fix
problems
like
this,
so
that's
that's
where
I
that's
where
I
really
activate
that's
where
I
get
excited.
So,
let's
kind
of
let's
kind
of
let's
kind
of
bring
that
that
that
process
to
the
forefront
is
there.
Is
there
something
cool
coming
out
with
with
rel?
Is
there
something
cool
you
guys
are
working
on
that
that
you'd
love
to
to
share
with
folks.
D
D
B
D
B
D
It
required
extraordinary
forcing
coordination
and
fun
fact.
It's
one
of
the
rare
cases
where
we
had
to
work
on
well
before
that
before
fedora,
and
the
only
reason
is
that
rally
is
smaller
than
fedora
less
packages
like
it's.
In
that
sense
it
has
less
packages,
and
that
means
less
dependencies
over
the
cell.
So
there
are
thousands
literally
thousands
of
packages
this
somewhere
pulling
up
and
sell,
but
thousands
is
better
than
ten
thousand,
so
it
was
easier
to
do
it.
Why
also
because
we
knew
the
process
was
going
to
take.
B
D
Years
since
the
first
time
you
started,
you
know
really
thinking
about
it
and
infinite
time.
That's
like
four
week.
This
is
three
releases
and
it
would
have
been
really
really
disruptive
and,
although
yes,
you
can
throw
bad
stuff,
you
go
higher
from
time
to
time.
You
don't
want
to
break
the
statement
releases
so.
D
Experience,
I
didn't
do
most
of
it.
Of
course,
other
people
in
my
team
did
it,
but
it
is
organizationally
and
the
sheer
amount
of
work
to
bring
that
thing
into
the
composes
into
the
built
rooms,
and
you
know
fixing
all
the
dependencies
and
you
know
explaining
or
helping
people
out.
That
was
a
that
was
a
great
experience.
I
think
it
would
be
a
very
interesting
one
when
it
comes
out,
so
I
think
that's
exciting.
For
me,
I
don't
know
how
exciting,
for
other.
A
D
A
change
in
the
in
the
architecture
of
the
ssl,
with
the
internal
architecture
that
has
repercussions
you
know
not
so
much
likely
to
more
modern
applications,
but
there
were
changes
to
be
made
approachable.
It's
not
like
something
that
you
have
to
rewrite,
or
your
support.
It's
not
a
different
library,
but
when
you
talk
integration
at
the
level
of
the
distribution,
if
you
change
a
single
function,
you're
gonna
break
a
dozen
or
more
packages
by
just
just
by
changing
semantics.
D
B
D
B
B
B
I
mean
it's
it's
out
there
and
and
the
the
work
that
that's
getting
done
with
openssl
everything
around
secure
supply
chain,
network-bound
disk
encryption
I
mean
I
could
list
off
six
different
things
that
are
top
of
mind
right
now,
for
not
just
red
hat,
but
our
upstream
projects
for
the
government
for
people
worldwide.
I
mean
it's,
it's
it's
no
small
task
and
I
mean
yeah
three
years
and
7
500
commits
that's
that's
a
lot.
That's
that's
a
lot
and
alexandra
your
your
turn.
What
are
you
excited
about.
B
C
C
B
C
For
example,
even
downstream
rebuilds,
like
alma
or
like
anyone,
can
basically
implement
certain
test,
suites
and
tests
and
to
stream
changes,
and
this
will
be
included
in
the
consideration
so
extending
this
community
contribution
collaboration
with
the
community.
This
is
what
I'm
totally
excited
about.
B
So
that's
I'm
really
excited
and
this
it'll
it'll
be
great
to
see
the
the
new
development
life
cycle
from
fedora
to
centos
stream
to
real
nine
in
place
because,
like
you
said,
more
people
can
get
involved
and
bringing
kind
of
the
resources
of
fedora,
centos
and
and
rel
together
to
just
make
a
an
even
more
secure
and
performant
operating
system.
So
there's
so
many
cool
things
going.
We'll
have
to
have
you
both
on
to
to
talk
about
that
kind
of
post
release,
because
real
night's
gonna
be
great.
B
There's
there's
some
great
stuff
coming.
In
fact,
if
you
would
like
putting
my
host
hat
back
on,
if
you'd
like
you
can
go
to
redhat.com,
try
rel
try
r-h-e-l
and
you
can.
You
can
download
copies
of
rel
and
I
believe
that
also
includes
beta
entitlements
now.
So
if
you
go
and
try
out
rel,
you
can
try
out
not
only
the
current
release
but
also
the
releases
to
come
before
we
wrap
up.
Is
there
any
any
any
any
place
either
of
you
would
like
to
send
folks.
D
B
Got
a
couple
of
fedora
servers
here
and
my
workstation
runs
fedora
34.
So,
although
a
couple
of
my
a
couple
of
my
more
crazy
friends
are
already
running
the
release
candidate
for
35.,
it's
like
yeah,
I'm
I'm
glad
that
you
can.
You
can
do
that,
but
I
do
live
streaming
and
podcasting
and
I
need
some
degree
of
reliability.
B
A
B
A
B
D
B
The
machine
doesn't
move,
that's
rpm,
that
she
is
a
package
that
breaks
everything.
Yeah
yeah,
I
mean
my
workstation.
In
fact
I
think
started
on
30,
maybe
31,
but
I've
done
in-place
upgrades
all
the
way
up
to
34
and
the
only
thing
I
ran
into
issues
with
this
last
time
go
figure
audio.
I
had
to
uninstall
the
the
audio
stack
and
reinstall
it
just
something
about
the
switch
some
of
the
changes
around
pipe
wire
and
having
been
around
for
my
my
individual
instance
being
around
for
a
while.
B
I
think
I
ran
into
into
some
kind
of
an
issue,
but
just
did
a
yum
reinstall
on
on
a
few
of
the
packages
and
no
problems.
It
works
like
a
champ
and
that's
in
place
upgrades.
So
that's
that's
that's
great
news
for
fedora
and
and
all
that
stuff
works
its
way
down
into
into
rel.
In
fact,
my
our
in-place
upgrade
show
a
few
weeks
ago,
notwithstanding.