►
From YouTube: Ortelius and RedHat Emporous Go To Market
Description
The Ortelius and RedHat Emporous team talks about what a go-to-market strategy and story would look like.
A
B
So
today
we
were
going
to
have
a
less
technical
discussion,
I
believe
and
a
more
practical
discussion
about
what
this
partnership
could
potentially
look
like.
We
have
had
some
thoughts
on
it.
Steve
may
still
have
some
architectural
questions
and
whatever
concerns
that
we
may
have
come
up
with
or
concerns
that
you
guys
have
come
up
with.
B
So
Steve,
do
you
have
anything
any
follow-up
questions
that
you
need
to
ask
or
Jay
to
us
or
Andrew
or
any
or
Alex,
or
any
of
you
or
Jen.
C
It's
the
big
thing
on
our
side
is
just
the
timing
of
when
you
kind
of
foresee
your
spec
proposal
or
the
extensions
being
available
and
which
oci
registries
you
expect
to
start
implementing
those
first.
Would
it
be
like
Quay
or
you
know,
another
open
source
project,
starting
with
that?
That's
kind
of
where,
where
I
would
like
to
start.
D
Andy,
do
you
wanna?
Let's
see
I
had
been
kind
of
leading
this
stuff,
but
Andy
is
really
our
open
source
face
and
and
leader
for
this,
so
we
had
planned
at
this
meeting
to
make
sure
that
he
had
the
reins
and
I
recede
into
the
background.
Yeah.
E
Jason
go
ahead
and
kind
of
Step.
You
know
back,
you
know,
play
Homer
Simpson
and
walk
back
into
the
the
weeds
there
so
be
able
to
answer
any
questions.
Etc
moving
forward.
So
especially,
you
know
Tracy.
If
we're
looking
to
schedule
he's
continuing
to
schedule
them.
You
know
work
through
me
from
now
on.
So
just
let
Jay
been
into
the
project,
as
I
said,
will.
B
E
Can
do
that
so
from
a
at
least
from
a
registry
standpoint
you
know,
obviously
you
know
Red
Hat,
you
know
having
our
own
registry
product
as
well.
We'd
be
looking
to
you
know,
implement
this
within
Quay
first
and
then
looking
to
use
that
as
kind
of
a
starting
point
to
then
show
how
it
can
be
used
and
then
promote
it
out
to
other
registry
distributions.
F
D
C
D
That
so,
okay
yeah.
C
Fair
enough
and
and
I
believe
Jen.
You
said
last
time
that
you're
getting
close
to
publishing
some
of
the
spec
changes
that
you're
going
to
propose
and
so
I
just
kind
of
want
to
find
find
where
you're
at
on
that
front.
A
So
we
do
have
an
open
issue
and
we
had
some
discussions
last
week
about
our
approach.
I
still
don't
have
anything
documentation
wise,
but
I
can,
after
this
meeting,
send
out
where
it
will
be
and
the
issue
that
you
can
keep
an
eye
on.
Oh.
C
A
C
And
and
then
just
from
from
our
side,
I'm
going
through
and
updating
our
architecture
and
Design
with
all
of
the
schema
objects
that
we're
going
to
kind
of
need
to
be
storing
and
retrieving
and
stuff,
like
that,
the
information
that
we're
going
to
try
to
grab
I'm
hopeful
I'm
going
to
try
to
get
that
done
by
the
end
of
the
week.
C
B
And
then
so,
I
have
some
questions
about
internally.
I,
don't
know
how
you
guys
want
to
answer
this.
How
is
Emporia
sitting
with
red
hat?
Is
this
something
that
you're
getting
some
support
from
Red
Hat?
Is
this
I
mean?
Where
is
the
project
within
red
hat.
D
Let's
see,
there's
a
lot
of
Grassroots
support
for
it
across
the
the
portfolio
and
we
should
have
a
an
answer
from
the
top.
So
this
month.
C
Then
I
I
know
this.
Is
you
know
the
long
term
there's
going
to
be
some
changes
to
some
of
the
package
managers
to
have
the
package
managers
push
things
to
oci
versus
their
lack
of
a
better
word
native
Registries?
What
which
package
managers?
Are
you
first
going
to
look
at
tackling
and
have
you
reached
out
to
those
folks
yet.
D
I'll,
that's
actually
been
a
topic
recently
is
like:
how
can
we?
How
can
we
scope
down
to
you
know
it
can
do
so
many
things
we
need
to.
We
need
to
pick
one
thing,
focus
on
it
and
and
deliver
on
that
and
and
keep
going
from
there.
So
we
haven't,
we
haven't
picked
that
yet,
but
we
recognize
that
we
need
to
do
that
and
we
need
to
do
that
like
in
the
next
two
weeks
or
so.
C
Foreign,
are
you
guys,
leaning
towards
like
node.js
or
you
know,
which
ones
do
you
think
you're
going
to
be
targeting.
D
I
I
don't
know
because
that's
not
I'm,
not
in
the
I'm,
not
a
decision
maker.
There
I'm
happy
for
anyone
to
yeah,
okay,
Andrew
Andrew
may
happen
to
know
more
than
I
do
with
this
on
that
question,
but
he
may
also
be
in
the
same
boat.
E
C
Yeah
I
wasn't
sure
if
you're
gonna
pick
like
a
smaller
Library
like
Ruby
or
if
you're
going
to
go
for
the
like
a
big
one
like
node
npm,
you
know,
or
if
you
can
do
something
in
the
middle
it'll,
be
interesting
to
to
see
what
what
you
guys
pick.
B
B
So,
in
terms
of
where
you're
moving
to
in
in
getting
it
established
as
an
open
source
project,
I
know
initially
in
your
doc,
you
sent
to
me
your
thoughts
were
to
move
it
into
the
cncf.
B
E
We're
still
very
early,
so
we
have
not
started
any
conversations
with
the
cncf.
Yet,
however,
we
always
kind
of
lean
towards
cncf,
because
it's
you
know,
a
very
well-known
Cloud
native
community.
E
We
are
obviously
obviously
always
interested
in
hearing
opinions
from
others
for
other
destinations.
So
did
you
or
the
team
have
an
idea
of
where
you
might
want
it
to
go?
If
it
didn't
go
to
the
cncf.
B
So
I'm
on
I've
been
on
the
board
of
both
this
continuous
delivery
foundation
and
I'm.
Also
on
the
board
of
the
open
source
security.
Foundation
I've
worked
pretty
closely
with
the
Linux
Foundation
now
for
the
last
four
years.
The
problem
I
see
with
the
cncf.
If
it's
it's
just
so
big,
it
really
is,
you
can
get
lost
in
it,
I
believe
then
they
they
now
have
something
they
call
the
sandbox.
B
So
you
can
it's
easier
to
get
into
the
cncf
and
in
the
past
you
had
to
have
at
least
250
GitHub
stars
to
even
be
considered,
and
it
takes
a
lot
to
get
get
to
an
incubating
level.
So
there's
just
a
lot
of
there's
just
a
lot
of
CNC
app
projects.
E
That
should
be
funny,
I
had
a
conversation
earlier
today
about
get
opscom
and
how
they've
actually
moved
away
from
kubecon
and
are
moving
towards
cdcon
and
open
source
Summit.
Just
because
you
get
lost
in
the
sea.
That
is,
you
know
the
pre-event
to
kubecon.
B
Right
and
you
know
just
because
I
mean
the
cncf
is
home
to
kubernetes
and
everybody
just
said
we're
going
to
just
be
underneath
kubernetes,
but
the
kind
of
solutions
and
tooling
we're
talking
about
is
really
more
appropriate
to
the
devops
pipeline.
It's
really
what
we're
we're,
having
a
conversation
about
and.
B
B
If
the
open
ssf
had
an
open
source
way
to
bring
in
open
source
projects,
we
may
consider
bringing
it
into
the
open
openssf,
because
we
are
really
focused
so
much
around
s-bombs
and
the
collection
of
security
and
devops
intelligence,
but
the
CDF
is
really
the
most
appropriate
home
for
us,
so
I
would
say
looking
at
bringing
it
into
the
CDF
would
be
a
would
be
better
for
you
than
the
cncf.
Now.
That
being
said,
your
repository
would
need
a
whole
lot
of
work
to
get
that
done.
F
Oh,
it
was
just
whatever
whenever
it
was,
whenever
you
were,
it's.
F
I
was
just
gonna,
throw
a
kind
of
a
curveball
in
there
because,
as
we
were
as
we
were,
developing
the
the
imporus
concept
over
the
past
year,
or
so
we
had,
we
had
We've
looked
at
like
what
is
imporus
and
you
know
how
what
are
different
use
cases
and
things
like
that
and
and
another
another
open
source
Foundation.
That
I
had
found
that
I
thought
had
maybe
would
be
a
good
fit.
F
Also
was
the
hyper
Ledger,
Foundation
and
I
know
that
might
sound
kind
of
strange
on
on
it
on
the
surface.
F
B
We
do,
and
just
you
know,
I
don't
think.
We've
ever
spoken
to
you
about
this,
but
we
are
doing
a
project
with
xrp
Ledger.
We
got
a
a
grant
to
look
at
building
an
immutable,
s-bomb
Ledger
that
we're
currently
working
on,
and
so
we
I
get
that
totally
do
but
I
believe
that
what
the
fear
that
your
your
people
I
like
to
call
your
peeps,
would
probably
you'll
find
them
in
the
CDF
more
so
than
any
hyperledger
open
source
or
the
cncf.
B
Now
there's
the
other
option
is
you
could
become
a
pretty
quickly?
You
could
become
a
sub-project
of
ortilius
and
already
have
the
open
source
Community
behind
you
and
we
could
build
it
that
way
and
potentially
our
community
then
would
help
build
the
the
back
end
to
it.
So
there
are
ways
to
get
in
fast.
I.
B
Do
think
that
the
CDF
would
look
at
you
pretty
closely,
but
I
think
that
they
would
be
looking
at
your
community
and
and
have
some
concerns
about
the
size
of
your
your
existing
community,
so
they're
just
challenges
in
getting
recognized
and
the
reason
why
we
would
ask
that
question
is
because
for
attilius
in
order
for
us
to
start
using
your
back
end,
we
would
need
you
to
be
already
accepted
as
an
open
source
Community
somewhere,
because
our
we
wouldn't
certainly
wouldn't
want
to
build
something
that
was
ended
up
being
proprietary.
B
So
that
is
that's
one
one
kind
of
for
us
to
adopt.
It
would
be
one
hurdle
we'd
have
to
get
over
and
it
didn't
wouldn't
matter
to
us
what
open
source
Community
you
were
in.
We
would
love
for
you
to
be
either
in
the
in
the
CDF
so
that
we
were
at
least
sister
projects.
B
E
B
And
if
you
became
a
sub-project
of
artillius
and
later
wanted
to
become
a
full-on
project
of
your
own,
that's
certainly
doable
as
well.
You
would
still
just
create
an
emporious
repository
as
you
have
it
and
we
would
consider
it
a
sub
project
of
ortilius
until
you
were
able
to
get
in,
have
the
community
base
to
get
yourself
at
a
level
that
the
CDF
would
say
hey.
This
is
a
real
open
source
project.
It's
not
just
Red
Hat
behind
it.
B
That
being
said,
there
are
other
projects
out
there
that
have
small
communities
that
are
contributing
like
like
shipwright,
so
you
know
one
one
company's
behind
it
and
they
have
a
few
open
source
developers
in
the
community.
That's
also
working
on
it.
So
that's
just
an
area
that
you'll
have
you'll,
definitely
have
to
overcome
and
then
as
a
joint
solution.
B
What
are
the?
What?
What
can
we
talk?
What
would
be
our
go
to
market
story?
What
is
that
go
to
market
Story?
Look
like
I
think
that
that
they
are
from
the
artillius
side.
We
have
some
ideas
of
what
that
would
look
like.
But
what
are
your
thoughts
and
what
are
the
features
of
artillius
that
are
important
to
you.
F
Can
I
can
I
jump
in
on
this
one
Andrew
Go
For,
It
Go,
please
so
we
we've
said
sorry
I.
Have
you
on
my
phone
too
sorry
I
apologize
for
the
no
video
here,
one
of
one
of
the
things
that
we
we
had
that
looking
at
artillius,
that
was
in
of
interest
to
me
was
was
and
I
think
I'd
made
made.
The
statement
in
the
meeting
that
I
was
the
last
meeting.
I
was
in
with
you
guys
the
imporus.
F
If
we,
if
we
take
or
this
the
the
schema
or
or
schemas
or
maybe
a
more
encapsulated
in
terms
of
ontology,
that
ortilius
is
using
and
register
that
with
in
emporis,
then
I
I
think
that
it
Imports
becomes
on
some
levels,
becomes
ortilious
and
and
then,
and
then
you
get
the
distribution
and
and
some
of
the
advantages
that
that
we
see
in
importance
there.
F
So
I
think
that
one
of
the
one
of
the
most
interesting
parts
of
ortillas
to
me
is
is
the
schema
or
or
or
overall
ontology
there
and
then
and
then
I
see
a
potential
go
to
market
being
being
that
integration
using
enforce.
As
as
the
distribution
mechanism
for
oratelius.
B
I
know
we
have
a
UI,
we
don't
have
a
good
back
end
to
track
a
whole
bunch
of
data,
and
that's
why
we
we're
looking
we
we
did
get
that
Grant
from
xrp.
We
got
a
75
000
Grant
to
take
a
look
at
using
their
blockchain
to
track
that
level
of
data
which
we're
we're
playing
with
right.
Now
that
doesn't
mean
we'll
go
with
it.
B
It
just
means
that
we've
started
a
POC,
because
if
you
look
at,
we
were
just
on
a
Toc
meeting
and
one
of
the
board
advisors
asked
us
about
that.
You
know
why
would
you
want
to
go
to
a
kind
of
a
blockchain
architecture
and
when
we
explain
the
amount
of
data
that
we're
talking
about
and
the
cost
of
managing
that
data?
B
And
you
know
the
blockchain-
is
ledger
technology
really
cuts
that
into
a
fraction
we're
talking
about
cents
instead
of
thousands
of
dollars
that
that
is
our
one
of
our
bigger
challenges
in
managing
all
that
s-bomb
information.
It's
a
massive,
a
data.
It's
huge.
B
E
B
It's
not
one
one,
you
know
it's
not
just
reconciling
a
merchant
to
a
customer,
it's
a
lot
of
data.
So
that's
the
problem
we
are
trying
to
solve
so
certain
you're,
certainly
you're
you're
back
in
databases
and
interest
to
us
to
do
that
and
the
relationship
for
us.
You
know
we're
smoke,
we're
small
ortelius
is
small.
Deploy,
have
a
small
to
have
a
red
hat
as
part
of
the
community
and
working
together
on
solving
this
problem
would
be
huge
for
us,
I'm
I'm
not
going
to
to
lie.
E
E
Yeah,
it's
there's,
there's
a
lot
that
we,
as
Jay
mentioned
earlier,
our
go
to
market
strategy,
especially
after
our
conversation
we
had
last
week
or
two
weeks
ago.
The
days
are
meant
you
know.
Merging
together
is
we
need
to
be
more
succinct
in
our
messaging
and
what
we're
focusing
on
instead
of
trying
to
boil
the
ocean
and
that's
what
we've
been
working
on
as
a
team
to
what
that
will
look
like,
because
otherwise
our
vote
with
those
we
have
no
go
to
market
strategy
or
a
very
fractured
one.
E
B
Right
and
I
think
the
part
of
the
challenge
is
building
out
those
Cooperative
Integrations
I,
guess
you
could
say
with
all
the
different
package
managers,
because
we
know
from
experience
that
it
you
have
to
play
with
people
where
they're
at
it's
hard
to
get
them
to
come
to
you.
You
have
to
go
to
them
and
we
have
been
spending
quite
a
bit
of
time,
just
building
Integrations
and
pointing
to
data
and
bringing
it
over
as
opposed
to
creating
the
data
ourselves
and.
A
B
Is
a
bit
of
a
difference
between
your
strategy
and
ours
and
some
of
those
areas,
even
though
I
know
that
in
your
original
kind
of
what
you
want
to
do
now,
you
do
want
to
point
to
the
data
which
we
already
have.
So
we've
already
done
that
a
lot
of
that
worked
for
you,
so
that
it's
it
feels
like
it's
the
right
fit.
It
really
does
I
I
think
that
the
biggest
concern
we
have
is
to
make
sure
you're
going
to
be
part
of
an
open
source
Community
before
we
we
jump
in.
E
Yeah
totally
agree
I,
it's
something
that
our
team
is
taking
to
Heart
everything
we're
hearing
from
you
and
your
community
and
we
are
going
to
be,
and
it's
one
of
the
things
that
we're
also
doing
is
just
kind
of
just
leveling
up
our
community
outreach,
so
we're
finishing
a
Rebrand
of
emporious
from
Universal
reference
that
should
be
done
in
the
next
couple
days,
we're
hoping
and
then
being
able
to
talk
about
how
we
can
better,
promote
and
work
with
the
community
to
hear
more
feedback.
It's.
B
Hard
community
building
is
one
of
the
hardest
jobs
I've
ever
done
to
build.
The
ortillas
community
I
literally
spent
a
solid
year,
happened
to
be
during
a
pandemic,
so
it
was
a
good
time
to
do
it
reaching
out
to
certain
profiles
on
LinkedIn
people
that,
from
around
the
world,
I
mean
Sasha's
on
the
on
the
call
today
and
he's
from
South
Africa
and
I
met
him,
because
I
saw
his
profile
and
said.
B
This
looks
like
the
kind
of
person
that
we'd
love
to
have
on
our
open
source
community
and
I
literally
reached
out
to
probably
over
a
thousand
people
in
the
course
of
a
year
to
build
those
250
Plus
members
that
we
have,
and
out
of
that
we
have
about
50
people
who
are
actually
contributing,
I,
think
and
I.
We
have
about
100
100
115
different
GitHub
Forks,
so
there's
people
out
there
working
on
stuff,
but
it
takes
it's
a
huge
lift.
It's
it's
harder
to
build
a
community.
That's
the
product.
B
Very
difficult:
there's
a
lot
of
noise,
there's
a
lot
of
Open
Source
projects
for
people
to
get
involved
in,
and
you
have
to
find
the
individuals
who
are
interested
in
solving
this
particular
problem.
You
know
people
who
really
want
to
work
on
this
particular
problem
and
that's
how
I
went
about
doing
it.
I
looked
at
a
lot
of
LinkedIn
profiles.
Did
some
automation
to
say
hey.
This
is
what
we're
doing.
Would
you
be
interested
and
I
talked
to
a
lot
of
people
over
the
course
of
a
year.
B
B
It
may
be
a
little
easier,
but
I
do
still
think
that
bringing
Red
Hat
into
either
the
CDF
or
under
the
artillius
project
is
the
fastest
way
to
get
you
up
and
running
as
an
open
source
project,
so
that
we
can
have
some
serious
conversation
about
doing
this.
Integration.
E
B
Mean
so
I
think
the
challenge
would
be
as
if
they
just
find
out
a
upper
management
is
going
to
give
you
guys
the
thumbs
up
to
continue
with
this,
and,
if
that
happens,
how
we
can
help
you
get
to
an
open
source
status.
B
And
I'm,
you
know
if
you
guys
get
the
the
thumbs
up,
Andy
I'm,
so
happy
to
work
with
you
on
building
out
that
go
to
market
message.
Our
messages
are
pretty
close
anyway,
so
we
could
put
together
a
pretty
interesting.
You
know,
artillius
with
an
emporious.
B
Registry
or,
however,
we
want
to
describe
it
because
I
hate
to
use
some
of
the
older
terms,
I
think
that
you,
when
you
were
using
the
a
universal
object,
reference
is
a
good
term
I,
don't
think
we
should
throw
it
away.
I
think
it
clarifies
what
your
your
you're
trying
to
do,
but
we
certainly
could
put
together
an
interesting
story.
Yeah.
E
F
B
It's
more
of
a
what
than
a
name
right,
but
sometimes
having
the
what
is
so
important.
We
struggle,
sometimes
with
our
what
you
know.
We
don't
have
something
that
in
three
words
can
describe
what
we're
doing
I
try
to
call
us
an
Evidence
store,
but
I
think
a
universal
object.
Reference
is
a
good
way
to
describe
the
what
of
what
emporius
is
doing.
So
it's
it's
hard.
All
this
stuff
is
really
hard.
Messaging
is
hard
get
building.
E
B
I
know,
that's
true,
I
know,
that's
true,
but
I
think
we
could
have
a
good
time
working
together
and
I
think
we
can
make
some
good
progress
and
it
would
be
I
think
the
go
to
market
story.
We
could
we
could
build
up
pretty
strong
and
I
do
believe
that
our
open
source
Community
would
be
excited
to
have
red
hat
us.
You
know,
working
with
red
hat
would
help
would
help
our
own
community.
G
B
So
everybody's
time
is
our
committee
of
our
Outreach
group,
so
he
runs
our
Outreach.
He
does
a
lot
of
podcasts
and
coordinates
to
all
of
everybody's
who's.
Presenting
where
are
we
getting
coverage
in
the
right
places
so
I
know
Simon
would
be
totally
excited
to
be
able
to
have
something
to
talk
about
in
Outreach
that
we
were
doing
work
with
red
hat.
G
B
And
for
that
matter,
any
of
you
on
the
call,
if
you
want
to
you,
know,
talk
about
what
you're
doing
with
the
emporis
Simon's
demand
to
reach
out
to
and
I
actually
managed
the
CDF
online
Meetup.
So
we
can
talk
about
it
there
as
well.
So
we
have
a
lot
of
avenues.
B
Yeah-
and
you
know
the
and
the
CD
Foundation
has
something
that
they
call
the
pipeline
at
devops.com
that
they
do
on
a
regular
basis.
These
are
all
the
you
get
more.
You
get
so
much
more
love
when
you're
part
of
the
CDF
than
you
would
be.
The
cncf.
E
I
have
I
love.
B
C
So
what
are
going
to
be
the
it
sounds
like
you
guys
have
a
couple
weeks
of
stuff
to
work
through
so
should
we
just
do
the
next
meeting
in
two
weeks
you
think,
or
should
we
go
out
to
three.
B
I
think
we
should
wait
until
they
hear
if
they're
gonna
get
a
thumbs
up
from
from
upper
management.
Yeah.
E
So
what
I'll
do
is
Tracy
I'll
work
with
you
to
work
on
the
timing.
You
and
I
will
just
collaborate
in
general.
Just
on
the
whole
community
outreach.
You
know,
collaboration
between
our
groups
and
then,
when
the
time
is
appropriate,
we
can
get
everyone
back
together.
Just
so
we
can
have
productive
conversations.
How
does
that
sound
sounds.
B
Great
I
think
that
that
makes
sense
it
does
because
we
would
want
to
know
that
the
project
is
getting
upper
management,
support
and
then
and
they're,
okay
with
pushing
it
out
to
an
open
source
community
and
then
we'll
just
have
to
figure
out
that
part.
E
B
B
B
And
you
know
Andy
we
used
to
live
in
Chicago.
We.
F
B
For
long
Steve's
from
Chicago-
and
we
do
go
there
on
if
I
go
to
there
to
visit
family
on
somewhat
regular
basis,
we're
out
there
we'll
have
to
meet
you
at
Sheffield's
or
something.