►
From YouTube: "Beer & Donuts" Ortelius Celebration acknowledging the acceptance of the Ortelius into the CDF
Description
December 8th, 2020 marked the day that Ortelius was officially added as a Incubating Project in the Continuous Delivery Foundation. Contributors, End-Users and supporters joined together to celebrate the accomplishment and hard work. A meeting filled with heart and happiness.
B
A
I
met
at
collab
net
and
he's
still
coaching
us
today,
tim
kelton
from
descartes
labs
he's
a
co-founder
of
descartes,
labs,
a
brilliant
mind
and
one
of
the
first
people
I
started
talking
to
about
the
challenges
around
google,
a
kubernetes
environment
and
organizing
microservices
in
terms
of
versioning
and
his
mentor.
Doug
orr
and
if
you
are
from
google
doug
orr,
is
a
sort
of
an
infamous
name
in
google.
A
Doug
was
one
of
the
senior
engineering
directors
at
google
around
the
kubernetes
project,
so
he
knows
kubernetes,
probably
better
than
anyone,
and
he
has
been
on
our
technology
oversight
committee
from
the
beginning.
He
and
tim
then
of
course,
there's
phil
gibbs,
who
was
the
one
of
the
masterminds
behind
the
domain
structure.
A
Giving
us
some
insights
in
what
netflix
is
going
through,
in
fact,
component
sets
was
something
we
first
heard
from
him,
hank
hendrickson,
who
is
from
bp.
I
found
him
in
the
same
way.
I
found
many
of
you.
He
has
some
very
interesting
perspectives
on
on
managing
microservices
in
a
really
large
environment
and
then
christopher
palmer.
Who
is
one
of
our
end
users,
who
has
been
super
supportive.
B
A
Us
over
the
last
year
and
has
really
rooted
for
us
and
quite
honestly,
understood
the
importance
of
versioning
and
the
domain
structure
that
ortilius
has
so
I
don't
know
if
any
of
you
are
on
here,
but
we
love
you
and
thank
you
so
much
for
making
this
happen.
We
couldn't
have
done
it
without
this,
this
this
level
of
a
toc
board,
giving
us
the
encouragement
and
making
sure
that
we
were
on
the
right
track
and
building
a
product
that
was
important
to
everyone.
A
Now
I
am
going
to
open
up
the
floor
to
phil
gibbs.
I
think
phil
should
just
say
hello,
because
he
is
really
hung
on
and
has
been
around
all
this
time
he
has
watched
us
he's
been
hired
by
us,
he's
been
terminated
by
us,
but
we
still
love
him
and
we've
been.
You
know,
rooting
for
his
his
his
code.
All
this
time
and
and.
E
Well,
hello,
I
mean
to
be
honest,
the
the
domain
structure,
although
it
fits
really
well
with
microservices.
At
the
time
we
were
developing,
deploy
what
was
deployment
manager.
The
domains
were
with
we're
there
to
just
to
split
up
in
individual
teams
right.
So
the
idea
was
that
you
would
get
components
that
were
shared
across
project
teams.
E
So,
for
example,
you
know
java,
runtimes
and
odbc
libraries
and
that
kind
of
thing
would
be
would
be
generated
as
a
sort
of
global
level.
So
it's
a
as
a
team
structure.
Sorry
it's
a
global
structure
and
then
individual
teams
could
inherit
those
components
from
other
teams
right.
So
it
meant
that
you
could.
It
was
essentially
enforce
the
delivery
of
certain
components,
right
that
was
shared
across
old
teams,
and
individual
teams
could
have
their
own
local
updates
of
application.
E
So
you
could
have
you
know
a
us
administrator,
a
european
administrator.
You
could
still
share
the
global
data,
but
each
individual
regions
could
have
their
own
components
and
then,
within
those,
the
teams
could
have
their
components.
So
it
was
this
idea
of
a
hierarchy
where
you
could
share
things
and
then,
if,
if
somebody
developed
something
locally
that
they
wanted
to
share
with
everybody
else,
for
example,
they
just
moved
it
up
the
domain
tree
and
then
everyone
else
sees
it
right.
E
They're
seeing
they
can
develop
their
own
components,
they
can
see
their
components
and
only
their
components,
but
if
they
wanted
to
and
bring
things
in
from
from
outside,
they
could
do
right.
So
if
someone
creates
a
global
level,
they
could
they
could.
They
could
bring
it
into
their
project
team.
So
that
was
the
idea
behind
the
domain
model
and
it
covered
not
only
components
but
applications
users.
E
You
know
a
user
could
go
into
a
certain
domain
and
be
and
have
access
only
to
that
region,
for
example,
or
that
team
or
everywhere,
depending
on
where
you
were
so
that
was
that
was
the
concept
as
tracy
said
it.
Never
really
it
never
really
took
off,
because
it
was
designed
more
or
less
to
be
for
in-house
application
development
and
for
on-prem
solutions,
and
it
was,
it
was
unfortunate.
It
was
released
more
or
less
as
everything
started
to
shift
to
the
cloud
right.
E
So
we
never
really
got
that
that
sort
of
traction
with
it,
but
the
concept
was
still,
it
was
still
quite
valuable
and
it
was
tracy's
insight.
I
think
in
to
say
well,
hang
on
this
is
this
domain
model
is
perfect
for
microservices.
That
I
think
has
has
made
that
shift,
because
yeah
the
con,
the
concept
was,
was
great
for
what
it
was,
but
it
fits
the
platform
exceptionally
wrong
right.
E
A
A
A
A
C
A
We
have
the
potential
to
do
that.
The
domain
structure
as
phil
just
described
it,
has
that
now,
since
since
bill
and
james
and
robert's
time,
we
have
obviously
sassified
it.
We
have
added
a
lot
of
features
around
managing
containers
and
but
we
have
kept
the
core
of
that
domain
structure
and
the
versioning.
A
B
A
A
C
C
There's
been
all
kinds
of
discussions
about
what
would
be
appropriate
for
that,
and
I
think
this
might
be
the
reason
that
we
actually
come
up
with
one
so
so
figuring
out
how
to
have
operational
code
for
one
of
the
projects
is
going
to
be
kind
of
interesting
discussion.
I
think
so
I'm
looking
forward
to
it,
though
so
I
love
the
idea
of
a
service.
A
Gave
him
two
answers?
I
said.
First
of
all,
this
is
a
big
problem.
Microservices
are
complex
and
we
have
an
amazing
back-end
database
that
we
can
start
adding.
You
know
fields
and
data
to
to
track
everything
that
needs
to
be
that
we
should
track,
but
we
need
to
have
the
community
tell
us.
It
is
a
community
problem
to
solve,
and
I
said.
A
Secondly,
we
want
to
be
able
to
build
that
marketplace
and
it
should
be
in
an
open
source
community
and
those
really
were
the
two
driving
factors
of
why
it
should
be
moved
into
there
now.
The
third
one
is
has
more
heart,
and
that
is
this
is
a
time
for
people
to
start
learning
about
microservices
and
kubernetes,
and
what
better
way
to
have
an
open
source
project,
that's
taking
on
one
of
the
core
problems
and
solving
it.
A
D
A
On
discord,
yeah
he's
chicks,
there's,
sasha,
wharton
karam
down
on
the
corner
in
the
cool
spaceship
tatiana
aisha.
These
are
some
of
the
folks
who
have
really
really
stepped
up
early
on.
We
also
have
nitu
jane,
I
don't
know
if
she's
on
and
perishot
they
were
the
ones
to
take
on
take
on
roles
as
community
managers
right
off
the
bat.
A
And
then
we
have
folks
like
owen
adams
and
marky
jackson,
who
have
come
from
a
really.
They
know
the
open
source,
community
and
they're
helping
us
stay
on
track
and
build
a
community
that
is
is
solid,
so
every
and
then,
of
course,
I
couldn't
this
day
would
not
be
together
here.
If
it
wasn't
for
tracy
miranda
that
we
call
ourselves
tracy
squared-
or
at
least
I
call
ourselves
tracy
squared.
A
A
F
F
Awesome,
thank
you.
Tracy
number
one
yeah
shout
out
to
to
all
your
work
as
well
and
efforts
in
pulling
together
this
amazing
community.
We're
super
thrilled
to
have
you
all
in
cdf,
and
you
know
we
always
say
open
sources
is
all
about
the
community
and
we're
only
limited
by
the
capacity
of
people
and
the
more
folks
that
come
in
and
get
stuck
in
the
more
we
can
do
so
really
thrilled
to
have
you
all
join
in
and
yeah
welcome.
F
B
No,
I
don't,
I
think
the
only
thing
I
want
to
say
tracy,
it's
just
great
to
see
you
and
steve.
It
feels
like
it's
been
so
long,
and
I
know
we've
been
up
to
so
many
different
things.
I
think,
since
obviously
we
parted
ways,
I
guess,
but
it's
great
to
see
all
of
that
work-
that
I
think
I
mean
our
companies
for
those
that
don't
know
you
described.
We
worked
in
this
ecosystem.
That
was,
if
you
like,
in
the
the
shadow
of
ca,
and
I
think
well
from
our
perspective,
it
was
very
much
cino.
B
Openmate
was
a
bit
more
diverse,
but
we
we
had
that
specialism
and
again
we
were
forced
to
innovate,
and
you
know
back
in
the
day
around
that
deployment
piece
as
we
saw
agility,
continuous
delivery
and
continuous
deployments
become
more
and
more
popular,
along
with
the
the
devops
and
agile
movements
and
yeah
just
working
with
the
likes
and
of
robin
and
phil.
It's
been
a
pleasure
and
then
bring
that
together
with
what
we
did
with
openmake
yeah.
B
D
D
So
if
there's
a
scientific
research
project
like
at
a
university
that
you
know
about
you
know
or
if
there's
like
some
financial
open
source
code
out
there,
that's
based
on
microservices
and
kubernetes,
if
you
can
give
them
my
name,
we're
looking
to
bring
in
those
types
of
of
open
source
projects
into
the
the
domain
catalog.
That
tracy
was
talking
about.
D
G
E
D
A
I
have
a
great
story
for
you,
so
I
was
raised
in
southern
california
in
this
little
area
called
bloomington,
which
is
really
poor
and
everybody.
The
only
thing
there
was
to
do
is
to
ride
mini
bikes
or
motorcycles,
and
we
had
this
family
down
the
street
full
of
boys
and
they
rode
motorcycles
all
the
time
and
I
would
go
over
to
their
house
and
make
them
fix
my
you
know
my
bikes,
my
kickstand
or
whatever
broke,
and
they
were
cute.