►
From YouTube: May 20, 2022 Beer and Donuts
Description
Join the Ortelius team as they celebrate their contributors and summarize their work over the last 6 months.
A
We
are
already
hearing
ourselves,
but
right
now
we
are
live.
Remember
we
are
in
twitch,
we
are
on
youtube
and
we
are
on
linkedin.
I
already
sent
the
links
on
discord
channel.
I
will
be
sending
here
to
shout
out
to
send
to
everywhere.
Just
share
use
the
chat
where
we
we
are
going
to
be
mainly
in
twitch
chat.
So
let's
go
ahead
and
tracy.
It's
all
yours.
B
C
D
B
B
B
We
also
do,
as
we
know,
presentations
that
we're
going
to
be
hosting
that
will
be
on
twitch
as
sergio
indicated
and
those
presentations
have
all
been
pre-recorded
as
soon
as
this
is
over,
we
will
start
using
that
content
over
the
course
of
the
next
six
six
months
to
drive
more
more
traffic
to
our
website,
and
that
brings
me
to
a
point
that
I
forgot
to.
Oh,
I
forgot
to
put
my.
I
bet
you
guys
can
hear
me
better
now,
a.
B
B
We
have
250
google
group
members
so
when
we
send
out
an
email,
it's
now
going
out
to
250
members
and
we
have
67
committers,
so
we
have
definitely
defined
a
pretty
awesome
growing
community.
The
the
community
continues
to
grow.
I
can
say
what
we
haven't
done
as
well
is
the
67.
Even
though
we
have
67
committers,
we
need
more
activity
around
pull
requests
and
when
steve
gets
back,
I
think
I'll
have
him
talk
about
that?
Just
for
a
minute.
B
You
know
it's
always
good
to
talk
about
what
you
did
well,
as
well
as
how,
where
areas
that
we
need
to
improve
on
outreach,
is
doing
really
really
well.
Syme
has
really
taken
this
project
on
and
has
has
done
a
great
job
of
the
podcast.
In
particular,
we
had
four
podcasts
this
year
so
far,
which
is
great,
because
this
is
only
month
five.
The
podcasts
are
are
getting
out
there,
depending
on
who
it
is.
B
People
are
starting
to
pick
it
up
and
and
watch
the
podcast
we
have
brad
mccoy
is
doing
a
presentation
in
valencia
at
the
cd
events,
I'm
doing
a
presentation
at
supply
chain
security
con
I'm
doing
one
at
jfrog,
I'm
doing
one
with
trisentis
and
I'm
also
doing
one
at
cdcon.
So
we
are
getting
the
ortilius
message
out
through
some
of
these
activities.
B
So
if
you've
been
part
of
one,
my
I
think
my
suggestion
here
in
this
area
is:
we
need
more
of
you
to
be
brave
to
submit
for
doing
these
talks.
Some
of
you
are
really
really
good
presenters
and
I've
noticed
that
you're
a
little
hesitant
to
like
to
submit
to
a
devops
world.
I
think
we
all
have
to
be
a
little
more
brave.
We
need
a
little
bit
more
of
arvin's
approach.
B
Arvind
always
puts
his
self
out
there
and
I'm
always
so
proud
of
him
when
he
does
so
some
of
the
work
that
we've
done
on
the
product,
just
because
some
of
you
are
not
on
the
architecture
meeting,
so
just
some
areas
that
we
have
focused
on.
So
we
really
focused
on
solving
some
of
the
problems
around
supply
chain,
one
of
the
problems
that
we
started
hearing
about,
that
we
were
able
to
add
as
a
feature
into
ortilius.
Is
this
aggregation
of
s-bom
information
up
to
the
application
level?
B
So
what
we
did
was
we
started
aggregating
that
data
up
so
now
at
the
application
level,
you
can
view
an
s-bomb
and
you
can
view
all
the
the
vulnerabilities
based
on
all
of
the
underlying
microservices
we're
the
only
ones
right
now
that
are
capable
of
producing
this
in
the
catalog.
So
it's
an
area
that
we
should
be
super
proud
of
now.
On
that
same
note,
we
added
package
search
searches
across
all
applications.
So
you
can
you
can
submit
this
when
I
ran
this
search.
B
I
just
said
every
everything
show
me
every
package
I'm
using,
but
you
could
put
in
here,
for
example,
log
for
j,
and
you
could
see
every
application,
that's
consuming
log4j
and
you
could
see
what
version
of
the
application
it
is.
What
component
is
using
it
and
what
version
of
the
package
it's
using
so
now
we're
starting
to
take
the
intelligence
around
this
devops
gathering
and
starting
to
use
it
to
produce
important
kind
of
reports.
B
E
E
E
So
what
we're
planning
to
do
with
the
xrpr
ledger
is
be
able
to
store
a
component
version,
the
json
definition
for
a
component
version
on
the
blockchain
and
then
in
the
ledger,
and
then
in
the
doing
the
same
thing
for
an
application
version
and
storing
that
json
definition
on
the
blockchain
ledger
as
well.
This
gives
us
an
immutable
view
of
what
those
versions
look
like
and
it's
going
to
fit
well
into
the
the
supply
chain
concept,
because
everything
in
the
supply
chain
people
are
trying
to
make
it
immutable.
E
Those
type
of
things,
so
the
actual
implementation
is
going
to
be
in
using
xrpl
and
nfts,
which
is
non
non-fungible
tokens
as
part
of
the
backing
place.
So
that's
what's
kind
of
happening
on
that
front,
just
a
shout
out
to
ukarsh
and
joseph
that
did
a
lot
of
work
around
this
and
helped
help
us
move
it
along.
So
we
can
actually
get
the
ripple
folks
to
look
at
our
code
base
and
stuff
like
that.
So
been
a
big
help
on
that
front.
E
So
let's
say
you
have
a
component
version
out
there.
It
has
two
vulnerabilities
and
then
somebody
finds
a
new
one
today,
because
the
blockchain
is
immutable.
We
wouldn't
be
able
to
go
back
and
update
that
to
say
that
there's
three
vulnerabilities
now,
but
we
would
be
able
to
make
that
association
in
real
time
to
the
vulnerability
database
and
show
that
there's
now
three
three
vulnerabilities.
When
yesterday
there
were
two.
E
So,
if
you
think
about
you
know
you,
you
have
to
know
like
what
operating
system
or
what
hardware
the
binary
was
built
on.
Was
it
built
on
an
arm
or
an
amd
processor,
because
that'll
change?
How
the
output
of
the
program
is
what
what
version
of
the
operating
system?
What
patches
are
on
the
operating
system
for
the
compiler?
All
that
information
needs
to
be
stored
in,
and
that's
going
to
come
through
as
different
s-bombs
that
we
will
go
through
and
aggregate
together
and
throw
on
the
blockchain.
B
So
if
any
of
you
are
curious
and
want
to
know
more
about
s-bomb
steve
did
write
a
really
interesting
blog
out
on
the
deploy
hub
site
steve.
You
want
to
pull
that
up
and
maybe
put
it
in
the
chat
and
some
of
you
may
know,
but
I
was
elected
to
the
board
of
the
open
ssf
as
the
general
member
for
the
community.
B
So
I
we
got
invited
to
go
to
washington
dc
last
week
and
we've
been
on
a
what
they
call
one
of
the
streams
for
better
securing
open
source
software
and
the
stream
that
we're
on
is
called
s-bombs
bombs
everywhere,
and
one
of
the
areas
that
we
saw
as
a
problem
is
the
accessibility
of
s-bombs
and
the
use
of
it.
Because
we
all
have.
We
have
the
ability
to
generate
s-bombs
now,
but
nobody
really
uses
them.
B
People
are
starting
to
think
about
applying
them
in
some
way,
but
not
really
so
that
this
was
some
of
the
motivation
in
making
sure
that
we
are
exposing
s-bombs
and
associating
them
to
an
application
version
and
then
figuring
out
a
way
using
blockchain
to
make
them
immutable.
So
that's
kind
of
the
the
genesis
of
of
this
particular.
B
Platform,
I
guess
you'd
call
it
so
that's
where
the
money
would
end
up
going
and
we
would
use
it
to
help
pay.
Some
of
the
developers
who've
been
working
on
the
blockchain
effort
for
their
work,
so
it
would
be
probably
a
short
kind
of
burst
because
it's
really
a
poc,
but
this
gives
us
some
funding
to
actually
pay
some
of
the
people
who
have
been
working
on
this
all
right,
and
on
that
note,
let's
talk
about
badges.
Some
of
you
may
have
gotten
a
badge
over
the
period
of
the
the
evening.
B
Let's
just
go
over
some
of
the
folks
mark
eisenberg,
he
was
got
a
badge
at
the
ambassador
bronze
level.
He
did
a
podcast
for
us.
We
have
three
or
actually
four
new
speakers.
We
have
turja
miklos,
pavin
and
pia.
They
are
our
first
time
speakers
at
the
at
the
summit
today,
so
you
will
be
able
to
hear
some
of
their
their
talks.
All
of
them
have
come
to
us
from
different
individuals.
B
B
Sometimes
you
know
contributing
in
this
way
is
important
to
kind
of
get
your
your
profile
improved.
So
let's
say
you
want
to
do
it
present
a
talk
at
kubecon
or
any
of
the
linux
foundation,
events
or
a
devops
world.
They
will
often
ask
you
for
recorded
versions
of
your
presentations
in
the
past.
This
was
really
hard.
B
So
if
you
have
never
done
a
presentation
these
every
six
month,
events,
there
are
a
lot
of
workforce
to
put
together
they're
fun.
We
have
sergio
to
thank
for
really
pulling
all
of
this
information
together
and
and
building
the
platform
to
present
it,
but
it
gives
you
the
opportunity
to
get
your
name
back
out
there
in
terms
of
doing
presentations
and
that's
the
that's
one
of
the
main
reasons
why
we
do.
It
is
so
that
the
community
has
a
platform
to
kick
off
their
outreach.
B
So
now
he
is
now
one
of
our
legends,
so
he
has
now
received
a
bronze
in
the
at
the
legend
category.
For
those
who
may
not
know
how
we
have
this
structured,
we
have
three
categories
that
you
can
earn
badges
in.
We
have
ambassadors
who
are
our
outreach
group,
so
anybody
who
participated
for
example,
on
today's
presentations
are
part
of
the
ambassadors.
B
Syme
has
reached
a
silver
level
for
ambassador.
He
has
done
a
great
job
with
building
out
the
outreach
community.
He
continues
to
really
push
that
podcast,
and
that
is
super
important
because
he's
doing
it
on
a
monthly
basis,
so
we're
starting
to
get
kind
of
repeat
business,
and
he
has
been
able
to
recruit
some
very
interesting
folks
for
doing
that,
and
then
we
have
our
superstar
for
this
time,
which
is
sergio
he
has
achieved
silver
legend.
B
B
I
we,
I
also,
I
think
I
forgot,
let
me
see,
did
I
I
think
I
might
have
forgotten.
Yes,
I
did.
I
forgot
victor
farsik.
He
has
also
received
a
he's
at
the
ambassador
bronze
level
for
participating
in
a
a
podcast,
so
anybody
who
participated
in
a
podcast
over
the
course
of
the
last
five
months
also
got
a
bronze
badge
all
right
now
we
are
actually,
I
say
head
to
twitch,
but
we're
not
going
to
do
that.
Quite
yet.
B
So
we
decided
to
really
talk
about
why
we
created
a
microservice
catalog
in
the
first
place
and
sasha
is
going
to
leave
that
discussion
so
we're
going
to
for
the
next.
You
know
15-20
minutes,
we're
really
going
to
talk
about
the
genesis
of
a
microservice
catalog,
because
we
want
to
use
this
opportunity
to
to
do
some.
C
B
C
E
C
B
C
B
You
get
better
at
it,
the
more
you
do
it,
the
the
more
the
better
you
get
at
it,
brian
dawson.
I
saw
that
he
just
he
joined
brian.
Could
you
say
something
about
that,
because
you've
been
doing
presentations
for
a
long
time?
And
you
know
this
visionary
summit
is
really
part
of
educating
and
providing
everyone
a
platform
to
learn
to
present.
F
Wow
8
a.m.
Wisdom
that
I
am
a
little
short
of,
but
but
no
I
mean
I
I
think
you
have
the
point
it
really
is
practice
makes
perfect.
I
myself
have
what
you
know
was
kind
of
just
thrust
into
a
presenting
role
at
one
of
our
game
developer
conference
conferences.
When
I
was
younger,
I
was
definitely
shy.
F
F
B
Nobody
else
until
then
that
I
had
that
I
had
no,
no
other
presentation
that
I
had
done
had
done
that
for
us,
so
I
was
able
to
then
once
I
had
that
done
done,
that
presentation
for
devops
world.
I
used
that
to
apply
for
other
speaking
engagements,
so
I
have
cloudbees
to
thank
for
my
opportunity
to
be
able
to
to
to
speak
because
it
was
really
hard.
I
still
have
not
been
accepted
at
kubecon,
yet
I
look
forward
to
that.
B
Got
in
there
I
I've
not
achieved
that
yet,
and
I
I
I
continue
to
try.
I
submitted
recently
for
kubecon
in
october,
so
we'll
see
what
happens,
but
I
get
I
gets
accepted
in
so
many
others,
and
it's
because
I
had
that
one
opportunity
to
have
my
presentation
recorded
and
then
people
people
see
that
I
actually
could
present.
So,
if
you're,
a
good
presenter,
we're
gonna
capture
it
and
you
can
use
it.
E
Yeah,
that
was
one
thing
you
know
when
everything
was
in
person
for
trade
shows,
nobody
recorded
anything
yeah,
and
none
of
you
know
all
that
knowledge
was
just
kept
in
that
in
those
conference
rooms
for
a
couple
days
and
then
you
went
home
and
it
all
was
lost,
which
was
a
shame
and
nowadays
with
folks
recording
stuff
and
pushing
it
out.
I
think
we're
getting
information
out
to
a
wider
group,
which
is
great
yeah,
sasha
you're
up
you're
up.
C
B
So
sometimes
you
stumble
into
you
can
kind
of.
I
call
it
force
gumping
your
way
into
a
new
idea,
but
if
you
think
about
our
history
in
terms
of
where
deploy
hub
came
from,
we
in
a
previous
company
called
openmake
software
were
really
into
builds
software.
Compiling
links,
that's
all
we
thought
about
all
the
time
was
how
to
make
the
build
faster,
how
to
make
it
more
accurate
how
to
control
it,
how
to
tighten
it,
how
to
make
sure
you
didn't,
have
debug
flags
running
in
a
production
environment.
B
Not
everything
uses
the
same
compiler
in
a
monolith
application
you
may
have
different,
you
may
have
a
resource
compiler
and
you
have
a
regular
compiler.
So
every
object
had
its
own
thing
right.
It's
had
its
own
way
of
doing
things
when
we
started
looking
at
how
we
were
shifting
from
monolith
to
microservices.
B
We
started
understanding
something
really
important,
and
that
was
we
lose
the
logical
application,
which
means
that
we
don't
have
a
way
to
control
dependencies
as
they're
moving
across
the
life
cycle
in
the
same
way
as
we
did
if
a
new
library
was
updated
and
git,
and
now
you
recompile
every
application
that
uses
that
statically
linking
it
and
pushing
it
out
to
production.
So
how
do
you
solve
that
problem?
And
that's
really
where
we
started
thinking
about
how
to
build
out
a
component
driven
release
process
and
that's
really
how
we
thought
about
it?
B
A
component
driven
release
process
and
phil
gibbs,
who
wrote
some
of
the
back
in
started,
understanding
that
it
wasn't
just
a
component
driven
release
process,
but
we
needed
to
version
it.
We
needed
to
understand
the
versions
in
order
to
be
able
to
do
incremental
releases
and
when
you
think
about
a
microservice
world,
every
microservice
is
independently
deployed,
so
we
are
always
doing
incremental
releases.
B
So
you
pull
all
that
together
and
you
step
back,
and
you
say
how
do
you
solve
it,
and
you
begin
thinking
about
things
like
service
catalogs
and
how
a
service
catalog
solved
the
problem
for
enterprises
for
managing
the
bigger
applications
that
an
athletic
that
a
enterprise
would
use
and
how
to
centralize,
where
those
bigger
applications
or
those
big
bigger
services
were
like
what
version
of
oracle?
Should
we
download
if
we're
going
to
stand
up
a
new
environment?
B
B
Which
is
why
we're
still
thinking
about
s-bombs,
because
it's
the
essence
of
everything
that
we
we
have
always
done
from
the
beginning
of
our
career
in
terms
of
tracking
changes?
It's
a
configuration
management
problem
that
we're
solving,
but
that
term
now
is
called
supply
chain
management,
so
basically
we're
it's
the
same
thing,
just
a
new,
a
new
just
a
new
angle.
C
Oh,
it's
super
great.
I
also
remember
having
my
first
conversation
with
you
when
you
said
you
have
a
passion
for
mapping,
well,
cartography,
right,
yep
and
that's
where
earlier
stems
from
right
and
it
kind
of
makes
complete
sense
how
otilius
maps
microservices,
but
it's
really
cool.
How
that
whole
thing
fits
together.
C
E
E
Yeah,
so
one
of
like
tracy
was
saying
one
of
the
things
that
we
recognized
is
we
needed
to
represent
deployable
objects
as
components
and
to
dive
in
a
little
more,
we
needed
to
look
at
the
versions
of
those
components,
because
you
could
have
one
version
in
production:
that's
different
than
the
version.
That's
in
qa
that's
different
than
the
version,
that's
in
development,
so
we
needed
to
have
that
that
versioning
com
aspect
to
ortelius
and
that
allowed
us
to
really
look
at
how
things
changed
over
time.
Now.
E
The
next
thing
that
we
recognized
was
that
you
needed
to
package
together
those
component
versions
into
something
that
you
can
represent
at
the
application
level.
You
could
also
think
of
an
application.
We've
been
toying
with
this
for
years
is
whether
we
should
stick
with
application
go
to
project
or
solution
or,
however,
you
want
to
think
of
it.
But
there's
going
to
be
the
next
higher
level
where
we
package
those
component
versions
into
an
application
version,
and
that's
where,
because
we
have
that
logical
application
version,
we
can
actually
diff.
E
You
know
what
are
what
com,
what
components,
change
between
production
and
what's
in
the
the
pre-prod
environment,
so
the
sres
can
see
what
type
of
impact
they're
they're
gonna
get
when
they
roll
this
out.
So
that
was
one
of
the
the
key
things
that
we
put
into
artelias
now,
one
of
the
challenges
that
we're
kind
of
having-
but
I
think
it's
going
to
work
out-
is
we're
recognizing,
like
docker
images,
which
we
consider
a
component
version,
have
packages
within
them,
so
we
actually
have
components
within
components
right
now.
E
E
So
that's
kind
of
like
where
the
s-bomb
comes
in
we're
looking
at
taking
the
s-bomb,
which
is
going
to
list
out
the
package
level,
information
associate
that
to
the
component
version
and
then
we'll
do
another
level
of
aggregation
of
the
component
versions
up
to
the
application
version
level.
Now
some
of
the
things
that
we
haven't
gotten
into
at
the
s
bomb
level
is
like
how
to
record
hardware
s
bombs.
C
B
Oh,
quite
some
time
ago,
actually
so
before,
deploy
hub
was
created,
we
had
the
base
of
vortilius
was
owned
by
a
company
called
open
make
software.
It
was
the
metamorphosis
of
our
build
tool,
turning
into
a
release
management
tool,
because
people
kept
asking
us
to
manage
releases,
but
I
always
I
didn't
really
feel
like,
even
though
the
team
at
the
time
believed
that
there
would
be
one
release
tool
to
rule
them
all.
I
never
believed
that.
I
always
believed
that
you
know
every
component
has
its
own
logic.
B
B
We
did
a
lot
of
magic
when
it
comes
to
restructuring
the
company
so
that
the
the
code
base
that
is
now
ortillius,
could
come
out
of
openmake
software
and
go
into
deploy
hub
and
then
deploy
hub,
contributed
that,
but
we
knew
I
knew
years
before
that
I
wanted
to
have
an
open
source
version
of
this
particular
product.
You
know
there
is
something
to
be
said
as
you
get
as
you
progress
in
your
career
and
you
get
a
little
older.
B
You
want
to
do
something
and
give
something
back
to
the
community
who's.
Given
you
so
much,
and
this
this
career
for
me
has
been
amazing
and
I
think
open
source
is
the
best
way
to
do
that.
So
a
lot
of
people
think
that
you
know
giving
your
code
away
is
kind
of
crazy,
but,
to
be
honest,
there's
a
couple
of
ways
to
build
a
product
like
this.
One
way
would
be
to
go
out
and
get
funding,
and
you
know:
have
the
vc
types
manage
it
and
make
decisions
on
where
the
product
should
go.
B
You
you
end
up
selling
your
company
early
when
you
do
that
which
means
you're
letting
go
of
your
the
code
base
anyway.
The
second
way
would
be
to
take
the
open
source
route,
which
means
that,
instead
of
handing
it
off
to
a
vc,
we're
handing
it
off
to
the
community
and
allowing
the
community
to
drive
where,
where
and
how
the
product
is
going
to
be
built,
and
ultimately
those
products
are
always
much
better
than
what
a
vc
board
can
decide
on,
because
they're
going
to
just
focus
on
income
income
income,
which
is
important.
B
But
if
we
were
to
do
that,
I'm
guessing
that
we
would
still
be
looking
at
trying
to
solve
monolithic
problems
because
that's
where
most
of
the
money
is
right.
Now
it's
not
in
microservices
everybody.
We
talk
about
them,
but
most
companies
are
still
doing
monolithic
development.
Not
a
lot
of
companies
are
doing
microservices
we're
looking
at
solving
a
problem
that
most
companies
will
see
in
maybe
two
or
three
years.
B
C
B
B
That
is
one
of
the
areas
that
we
need
to
improve
on
and
then
the
other
area
that
we
need
to
improve
on.
While
it's
starting
to
improve
is
adoption-
and
I
know
that
sergio
has
talked
about
that.
So
I
think,
as
we
look
the
from
now
to
the
next
six
months
of
in
our
beer
and
donuts,
we
will
hopefully
have
some
adopters
doing
these
presentations.
B
We
had
one
that
was
going
to
depeche,
but
he
had
to
he.
He
just
couldn't
pull
it
together,
and
I
know
that
next
time
he
in
december,
I
think
he
will
do
a
presentation
on
on
their
adoption.
But
that's
those
are
areas
that
we
need
to
focus
on
in
terms
of
improving
this
particular
open
source
community.
B
C
B
C
E
E
E
E
B
I
have
things
on
my
wish
list
too.
I
I,
I
think
we
should
start
having
a
discussion
about
integrating
with
backstage,
because
if,
if
there's
folks
already
have
adopted
backstage
and
they
they
tag
their
when
they
register
microservice
and
backstage
you
can
tag
it
and
those
tags
could
be
directly
mapped
to
our
domains
and
then
we
could
start
doing
the
versioning
on
the
back
end.
So
I
think
we're
interesting
complement
to
backstage
and
backstage
is
also
a
cncf
project.
It's
probably
going
to
be
graduating
soon.
E
E
E
One
of
the
other
things
that
we're
working
on
on
the
deploy
up
side
is
like
a
dev,
app
devops
adoption
dashboard.
You
know
how
well
are
our
teams
adopting
devops
practices
and
once
we
get
that
done,
we'll
push
that
back
down
into
or
push
that
up
into
ortilius
as
part
of
that
process.
So,
like
I
said
things
change
so
quickly
in
in
in
our
world,
but
that's
what
it
looks
like
for.
Probably
the
next
six
months.
C
C
B
B
Thing
we
need
to
do
is
we
need
to
talk
about
doing.
We
have
a
proper
governance
board
now
and
now
that
governance
board,
we
need
to
talk
about
doing
elections
for
a
proper
technology
oversight
committee.
So
that's
kind
of
we
we've
got
all
the
pieces
in
place.
We
do
have
a
technology
oversight
committee,
but
they
have
been
kind
of
recruited.
B
C
B
C
B
B
B
Anybody
who
wants
to
learn
more
about
how
to
build
microservices,
because
ortilius
is
a
true
microservice
architecture
now
has
offered
some
challenges,
because
I
don't
think
the
industry
is
ready,
including
microsoft
in
their
marketplace.
So
we've
had,
we
we've
run
into
some
problems
with
that,
but
it
is.
It
is
a
true
microservice
environment.
So
anybody
who
wants
to
be
part
of
microservice
team
and
learn
that
and
have
already
already
has
like
go
or
python
or
even
js.
C
B
C
E
Guarantee
that
that's
not
me
I've,
I
try,
but
I
fail
I
can.
I
can
deal,
do
do
the
technical
stuff,
but
yeah
kirsch
is
definitely
right
that
if
we
had
somebody
that
would
be
able
to
you
know,
look
at
the
issues,
help
figure
out
how
to
group
them
together
how
we
can
get
some
focus
on
it.
I
think
that
would
be
a
huge
help
to
get
some
fast
coding
done.
B
Well,
we're
planning
on
trying
to
have
dinner
with
with
brian
and
marky
jackson
next
week,
so
maybe
we
can
recruit
marky
to
come
back
because
he
is
an
excellent
project
manager.
I
know
that
he's
gotten
other
things
going,
but
man
it'd
be
great
to
have
him.
Take
a
look
at
some
of
our
stuff,
we'll
we'll
shoot
for
that
any
brian.
Do
you
think
we
have
any
chance.
B
Okay,
well,
that
takes
us
to
the
end
of
this
first
section
of
beer
and
donuts.
I
hope
you
all
enjoyed
this
live
version
of
it
and
congratulations
to
everybody
who
got
a
badge
proud
of
you
all
and
thank
you
for
all
the
hard
work
for
those
of
you
who
are
climbing
the
ladder
and
getting
into
those
legend
and
the
silver
levels.
It's
it's
not
an
easy
task
to
do.
We
do
have
it
set
up.
We
have
to
do
some
work.
B
B
A
Yes,
so
while
we
are
a
little
ahead
and
we
have
some
time,
we
are
going
to
do
a
little
break,
we
are
going
to
have
a
little
space
for
and
awesome
videos
about
ufos.
So
we
will
like,
watching
and
and
stepping
ahead
so
take
this
break
recharge
your
batteries,
because
we
are
going
to
start
a
huge
stage
for
lining
towels.
There
is
nine
of
them
and
four
are
really
awesome,
so
don't
miss
a
stream.
We
were
sharing
the
agenda.
A
We
have
countdown,
so
you
have
like
pretty
all
the
information
to
just
scale
your
your
technical
stage
and
anything
you
need.
So,
let's
see
you,
everyone
in
the
stream
just
hit
the
chat
every
time
you
need.
It
chill
hope
you
enjoyed
this
so
watch
you,
and
I
will
see
you
at
the
end
because
we
have
a
close
install
and
we
will
back
and
soon
so
meanwhile
see
you
in
the
stream
bye,
bye.