►
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
Now
she
can't
find
it
so
we're
I
just
got
it.
A
The
start
of
the
recording
so
today
is
november
12th,
the
arterios
architecture
workplace
mark
working
group.
We
do
have
some
excellent
news.
Tracy
miranda
from
the
cdf
says
that
we
are
in
and
that
they're
actually
working
on
the
the
press
release
so
very
exciting.
B
She
says
the
votes
are
all
in,
but
they're
going
to,
let
it
she
said
they'll,
just
let
it
be
out
there
for
two
weeks,
but
they
only
have
seven
votes
and
there
was
only
one
person
who
hadn't
voted
and
they
were
very
impressed
with
our
attendance
of
both
tocs
and
they
were
pretty
excited
about
every
the
the
community's
non-binding
plus
ones.
A
Yeah
we
flooded
them
with
with
the
plus
ones.
It's
great.
B
B
It's
kind
of
weird
for
steve
and
I
to
you
know
hand
our
baby
off
to
somebody
else,
but
it's
really
exciting
for
the
whole,
for
the
project
and
for
the
community,
and
you
know
for
the
solution
in
general,
I'm
I'm
just
I
couldn't
be
more
thrilled.
A
Screen
sorry
guys,
there's
struggling
with
it's
been
the
week
of
of
things,
just
not
quite
working
right,
and
it's
just
been
bizarre.
So
please
sign
yourself
in
on
the
docs.
The
attachment
to
the
doc
is
on
the
calendar,
invite
if
you're
looking
for
it.
A
All
right
there's
that
so
just
real
quick
on
the
agenda,
just
the
signup
process.
We
had.
We
identified
that
the
signup
process
was
the
bridge
between
wordpress
and.
A
Ortelius
or
deploy
hub
on
on
that
side,
there
are
some
problems
with
it
and
I've
reworked
it
and
it's
much
closer.
So
I
moved
the
signup
process
into
artelias,
so
we
can
get
that
everything
is
on
there.
A
The
one
thing
I'm
need
to
rework
is
I
finally
figured
out
what
some
of
the
underlying
problems
are
and
it
has
to
do
with
the
threading
on
a
servlet,
a
java
servlet
thread
that
the
the
thread
is
dying
or
the
the
request
is
dying
and
taking
the
thread
down,
so
things
never
complete
all
the
way.
So
I'm
doing
some
rework
on
on
that
on
the
I
should
have
that
out
this
week,
so
we
should
have
over
this
weekend
I'll
roll
it
out.
A
So
we'll
have
a
new
signup
process
as
part
of
that
which
will
make
it
a
lot
easier.
Then,
on
the
reporting,
microservices,
that's
kind
of
been
on
pause
after
the
hacktoberfest.
A
One
of
the
things
that
I
want
to
discuss
is
how
we
should
handle
passing
around
the
user
id
token.
So
one
of
the
things
that
comes
into
play
with
microservices
and
kubernetes,
and
things
like
that
is
it.
You
may
not
come
back
to
the
same
container
that
you
were
there
before.
A
So
your
transaction
from
your
first
transaction
that
you
may
do
make
a
container
a
in
the
cluster
and
then
your
second
transaction,
even
if
it
if
it's
even
it's
the
same
api
call,
may
hit
container
b
and
container
b
would
not
know
that
container
a
authenticated.
A
So
when
you
do
the
login,
the
login
returns
a
token
now
the
question
is:
should
we
just
return
the
token
or
so
every
transaction
going
forward
would
just
be
the
token,
and
we
look
up
based
on
the
token
who
the
user
is,
or
should
we
pass
along
the
user
id
and
token
as
well,
for
every
subsequent
call
going
forward.
A
The
one
thing
it
does
when
we
do
that
is,
we
know
the
user
id.
So
if
we
ever
need
to
look
at
logs
from
that
standpoint,
we
can
see
actual
user
id
in
the
log
stack
versus
trying
to
decrypt
tokens
from
the
log
viewpoint.
Just
want
to
get
your
guys
thoughts
on
that
which
way
we
should
proceed
on
that
anybody.
A
C
So
not
just
the
either
views,
but
yes,
let's
go
with
what
you
know.
What
is
the
industry-based
practices?
Nothing.
A
Right
and
I
did
look
at
oauth,
but
when
we
run
on
prem
for
a
so
if
we
take
artelius
and
put
it
on
prem
and
it's
running
in
a
kubernetes
cluster
or
in
a
docker
container
and
we're
going
to
implement
a
oauth
that
gets
tricky
because
most
companies
don't
want
people
to
use
their
like
their
gmail
address
or
their
github
account,
or
anything
like
that.
So
we'll
we'll
still
have
to
that's
the
reason
why
I
didn't
go
down
the
oauth
route.
A
We've
we've
done
that
in
the
past
and
we've
gotten
pushed
back
because
of
we've
actually
had
customers
asked
to
get
rid
of
that
authentication
because
it
was
being
confusing
with
their
internal
authentication
practices.
D
You
know
oauth
would
make
sense
if
we're
trying
to
interoperate
with
other
companies
and-
and
you
know
we're
having
to
you-
know-
have
like
a
sales
force
integration
and
have
you
know
them
be
able
to
get
authenticated
against
us.
You
know
for
stuff
that
we're
doing
internally
in
the
cluster.
I
don't
think
we
need
to
go
that
sort
of
route,
and
I
don't
know
how
much
you
guys
feel
like
that
sort
of
third-party
integration
is
important
to
where
we're
going.
A
I
think
you're,
you,
you
hit
it
the
nail
on
the
head
on
that
one
christopher,
because
I
think
right
now
we
should
just
focus
on
artelias
and,
like
I
said,
if
we
need
to
bring
in
if
down
the
road,
we
have
some
source
sales
force
integration
or
if
we
have
a
specific
integration
with
github
or
gitlab,
or
something
like
that
that
we
need
to
start
querying.
A
You
know
user
data,
about
the
user
id
or
like
the
github
organization.
I
think
that's
when
we
should
look
at
bringing
in
oauth
to
get
that
authentication
between
artelias
and
those
third-party
tools.
D
A
Yeah
yeah,
it
is
a
lot
of
work
in
the
past
when
we
we
implemented
it.
We
used
there's
a
third
party
tool
that
was
like
a
gateway.
It
was
like
a
oauth
gateway.
I
think
it's
like
oauth.io
or
something
like
that.
That
would
allow
you
to
gateway
through
their
system
to
the
other
ones,
to
set
that
up,
but
it
it
it
is
a
little
convoluted.
So
we'll
stick
with
user
id
token
on
that
front,
okay,
tracy,
why
don't
you
go
ahead
and
talk
about
what's
been
happening
on
the
personas?
A
I
know
last
time
we
were
talking
about
a
route
for
each
persona
and
we're
going
to
break
out
the
google
doc-
and
you
know
such
as
sre
and
stuff,
like
that,
let
you
go
through
what
you
guys
have
come
up
with
so
far,
because
that's
going
to
play
into
our
architecture
and
and
some
of
the
things
that
we
need
to
focus
on.
B
So
I
won't
go
too
deep:
we've
started
it.
There
is
a
kind
of
a
scratch
pad,
that's
called
the
ortelius
persona
doc,
and
what
that
led
me
to
is
just
building
out
a
proper
proof
of
concept
so
for
this
group,
if
you
take
a
if
you
could
take
some
time
and
look
at
the
proof
of
concept
and
some
of
the
needs
analysis
for
each
of
the
different
personas
that
we've
defined.
That
would
be
super
helpful.
B
Now
on
on
personas.
We
also
understand
that
nitu
is
going
to
start
working
on
personas
for
the
community,
not
just
for
end
users
of
the
of
ortilius
itself,
but
right
now,
we've
just
been
focused
on
end
users,
so
that
proof
of
concept
is
a
central
place
to
try
to
track
some
of
the
needs
for
each
of
those
personas.
A
And,
like
tracy
said,
we've
identified
two
major
groups
of
personas,
the
one
that
we're
going
to
be
focused
on
from
the
architecture
group
is
going
to
be,
and
marketplace
is
going
to
be
the
consumers
of
ortelius
those
personas
and
and
what
they
people
need
from
a
proof
of
concept
to
get
up
and
going.
The
other
group
is
community
members.
A
B
D
B
That
and
we'll
and
we'll
create
some
rewards
programs,
some
recognition
programs
for
each
of
those
personas.
A
And
one
of
the
things
that
we
are
are
kicking
around
as
part
of
the
rewards
are
the
badges
that
you
can
get
the
electronic
badges
and
then
also
there's
also
bounties.
I
don't
know
if
anybody's
been
involved
with
any
repos
that
are
using
bounties,
but
basically
you
can
get
bitcoin
for
issues
that
you
fix
and
things
like
that.
B
Yeah,
so
if
you
have,
if
anybody
has
any
ideas
of
how
they
would
like
to
see,
the
reward
system
be
put
together,
because
you
guys
are
the
ones
that
were
rewarding,
let
me
know
or
just
go
out
to
the
outreach
and
add
it
to
the
agenda
for
the
outreach,
and
I
will
take
a
look
at
it
before
the
outreach
meeting.
A
And
then
the
other
one
was
the
goals.
It's
a
high
level
delivery
plan.
This
is
what
was
over
in
the
google
sheets.
For
some
reason,
I
can't
get
it
to
open.
A
B
B
B
We
had
originally
discussed
the
website
improving
data,
graphs
and
maps,
importing
application,
based
versions,
publishing
our
first
marketplace,
and
then
this
beast
converting
dm
script
to
python,
and
then
I
added
interoperability,
because
I
believe
that's
something
we
really.
We
should
focus
on.
I
the
way
I
built
it
out
was.
I
had
steve
help
me.
B
B
I
do
have
some
things
in
here
that
are
specific
to
the
architecture
committee
and
as
we
until
we
really
grow
the
group,
I'm
guessing
that
most
of
the
folks
in
the
architecture
committee
are
going
to
be
doing
a
lot
of
these
other
steps.
So
here
it
is,
and
all
it's
it's
glory.
I
would
suggest
you
kind
of
take
a
look
at
it.
What
I
I
think
that
what
we
should
decide
is
so,
for
example,
we
have
this
beast.
B
I
have
identified
spinnaker
as
the
most
critical
of
all
of
these,
and
I
have
spoken
to
isaac.
I
can't
think
of
his
last
names,
ms
garga.
I
can't
think
of
his
last
name
right
now:
who's
the
cto
of
armory,
and
he
is
going
to
give
us
a
person
to
work
on
the
spinnaker
integration
at
least
give
us
the
definition
of
what,
where
we
think
it
should
go
and
if
they,
if
they
need
to
do
something
on
the
spinnaker
side,
they
can
add
it
to
their
roadmap
as
well.
B
That
we
have
defined
that
we
could
do.
I
don't
think
we'll
get
it
all
done,
but
I'd
like
to
get
a
kind
of
a
vote,
so
I
think
the
best
way
to
do
the
vote
would
be
to
put
it
on
the
sheet.
B
A
Plus
one
plus
just
do
a
vote
and
then
just
put
a
plus
one
by
it.
So
if
it's
already
at
plus
one
you
come
in,
make
it
plus
two
okay.
A
You
know
so
just
add,
add
to
what
you
think
is
gonna
be
important
and
if,
if
you
wanna
pick
a
couple,
let's
say
let's
focus
on
the
top
four,
so
you
get
four
votes
to
spread
across
the
different
categories.
One.
B
B
A
Week,
let's
put
an
end
date:
let's
go
ahead
and
vote
on
this
by
the
oh
a
week
from
tomorrow.
A
So
if
everybody
can
go
into
the
dock,
put
your
vote
in
and
that
way
it
gives
us
time
before
we
get
to
the
general
meeting
next
week
or
what
would
it
be?
Our
general
means
to
be
on
tuesday,
tuesday,.
A
Guess
we
can,
if
everybody
can
crank
through
it.
Just
you
know
it's
not
going
to
take
long
if
we
can
get
this
done
by
by
tuesday
our
vote.
That
will
be
something
that
we
can
take
to
the
general
meeting
of
what
we
identified.
So,
let's,
let's
make
it
a
goal
to
go
ahead
and
get
our
votes
in
by
tuesday.
B
C
E
B
B
B
There's
other
things
that
we
need
to
do
in
that
process,
but
I
feel
like
those
are
the
top
ones
and
then
the
other
stuff
is
just
the
nitty-gritty.
This
is
all
the
coding
everything
below
that
is
all
the
coding
and,
in
my
opinion,
I
think
that
this
interoperability
we
need
to
address
it
sooner
than
later,.
G
D
You
know
getting
that
sort
of
stuff
to
to
work
is
really
going
to
be
a
lot
easier
if
we
actually
have
somebody
that's
using
that
stuff
on
a
regular
basis-
and
you
know
I
think,
in
argo
cd,
we
should
be
able
to
find
somebody
because
that
I've
seen
that
come
up
a
lot.
But
I
just
don't
know
how
much
of
a
spinnaker
and
tech
time
population
is
out
there
for
us
to
find
that
user
advocate
sort
of
person
to
help
us
out.
D
B
So,
since
spinnaker
is
part
of
the
cd
foundation,
I
have
good
contacts
in
there
to
get
somebody
to
help
us
like,
like
somebody
from
armory.
B
I
think
that
they
could
give
us
a
somebody
from
armory
would
know
exactly
where
we
need
to
integrate
and
what
their
customers
are
asking
for.
A
And
I'm
I've
been
sitting
in
on
a
detecton
project
and
that
one
we
can
actually.
A
There's
other
tools
out
there
that
are
built
on
upon
tecton,
like
jenkins
x,
uses
tekton
under
the
covers
what
used
to
be
called
nebula.
Oh
it's
relay
from
puppet,
so
we
can
focus
something
like
on
puppet
relay
and
then
that
would
buy
us
the
techton
integration
type
of
thing.
But,
like
you
said
christopher,
I
think
I
think
the
big
one
is
getting
this.
A
This
spinnaker
one
they're
pretty
vocal
in
the
cdf,
so
if
we
can
make
them
get
some
visibility
and
and
right
on
their
toe
coattails,
I
think
that
would
be.
A
B
B
Yeah
argo
cd,
once
we
are
officially
part
of
the
linux
foundation,
I
think
I
can
find
somebody
from
the
cncf
to
introduce
me
to
some
of
the
folks
that
intuit
who
are
working
on
argo.
But
that's
that's,
going
to
take
us
a
little
time
for
me
to
build
a
relationship
to
get
a
favor.
A
Oh
and
then
I
have
something
I
just
slipped
my
mind
on
this,
never
mind
it'll
come
back
to
me.
Does
that
make
sense
what
we're
trying
to
do
here
with
the
now
the
the
spreadsheet
feels.
B
A
So
if
you
see
a
line
item
on
the
spreadsheet,
that
is
either
too
general
or
doesn't
make
sense,
feel
free
to
go
ahead
and
clean
it
up
and
expand
it
if
we
need
to.
This
is
just
the
first
pass
of
what
we're
looking
at
and
when
we
look
at
like
you
know
something
like
test
or
you
know,
install
a
platform
or
do
something
it's
very
generic.
A
You
know
underneath
the
covers
when
we
get
down
to
the
actual
coding
part
each
one
of
these
line
items
may
expand
into
you
know
two
to
four
github
issues
under
the
covers.
B
And
then,
if
we
could
talk
about
the
website,
just
briefly
owen,
are
you
still
there?
I
saw
that
you
signed
in
yeah,
I'm
still
here
great,
so
has
there
been
any,
have
you
thought
about
what
we
might
do
with
the
website
in
terms
of
the
platform.
H
Yeah,
so
I
haven't
didn't
have
much
time
to
work
this
week,
but
I've
got
an
initial
demo
of
a
workflow
to
show
to
folk
in
the
next
week
or
so,
and
to
kind
of
talk
through
once
we
can
actually
touch
it
and
have
a
play
with.
It
actually
see
what
that
would
look
like,
and
then
we
can
talk
a
little
bit
more
about
what
that
platform
should
be.
B
Okay,
super
you
just
let
me
know
when
you're
ready
to
do
that.
I
was
thinking
about
so
we
generally
have.
B
An
outreach
meeting
every
other
monday,
I'm
thinking
about
for
a
shorter
period
of
time,
not
to
something
permanently,
but
to
do
a
website
meeting
on
the
tues
on
tuesday.
So
we
have
a
general
community
meeting
every
two
weeks
on
tuesday,
I'm
thinking
about
making
that
meeting
weekly
and
we
focus
on
the
website
on
the
alternating
weeks.
B
B
Sometimes
it's
a
general
community
meeting
and
then
it's
the
website,
because
I
think
that
way,
we'll
get
the
website.
The
work
on
the
website
done
faster
and
get
it
off
our
plate
because
I
feel
like
this
is
a
low-hanging
fruit
that
we
could
probably
get
done
other
than
integrating
it
with
a
cell
number
c6,
which
is
building
out
a
cic
automation
from
git.
H
Yeah,
so
the
the
demo
workflow
I
was
putting
together
is
based
around
get
up
ci
actions.
Oh
sorry,.
B
H
A
All
right,
and
then
I
had
one
last
thing:
sasha
asked
for
and
for
to
do
a
walk
through
and
a
bunch
of
other
people
came
through
in
the
discord
about
that,
and
I
was
thinking
about
a
week
from
today
same
time.
Eight
o'clock
would
that
work
for
everybody.
A
Okay,
okay,
so
I'll
just
go
ahead
and
schedule
that
a
week
from
the
day-
and
basically
it's
just
going
to
be
a
a
walk
through.
So
you
guys
understand
the
more
from
a
development
perspective
of
how
things
are
hooked
together.
A
You
know
where
things
are
just
to
get
you
for
a
better
feel
go
over
some
of
the
terminology.
Most
of
you
know
what
the
terminology
is,
but
we'll
just
review
that
I'll
try
to
get
done
in
a
half
hour
or
less.
We
may
have
to
break
it
into
two
if
we
get
a
if
we
need
to
dive
deeper
into
some
stuff.
But
we'll
start
with
that
a
week
from
today
at
eight
o'clock
mountain
time.
A
Oh
no
problem
and
if
there's
any
other
things
we
did
put
together,
I
was
working
with
priyad
and
we
did
put
together
a
list
of
training
videos
that
we
need
to
do
and
there's
gonna
be
two
sets
of
training
videos,
one's
gonna,
be
community
training,
videos
like
how
to
do
a
pull
request,
training,
video
and
then
there's
another
one.
That's
gonna
be
like
how
to
run
your
first
deployment
using
ortelius
so,
like
I
said,
we're
breaking
these
into
two
groups,
because
you
know
one
of
our.
A
Our
high
level
goals
is
to
help
people
learn
how
to
do
open
source
and
then
the
other
side
is
how
to
learn,
ortelius
and
work
with
artelias.
So
what
we're
gonna
we're
gonna
work
with
those
two
sets
of
training
videos.
They're
gonna,
be
we're
looking
at
keeping
them
short
little
segments.
Maybe
five
minutes
ten
minutes
max
on
how
to
do
something.
A
So
we're
going
to
be
reaching
out
to
volunteers
just
to
record
some
of
the
raw,
the
raw
mp4s
about
the
different.
You
know
like
how
to
do
how
to
clone
a
how
to
fork
and
clone
is
one
of
the
the
videos
not
very
long.
We
just
but
we'll
need
somebody
to
go
and
do
that
record
it
and
then
pass
us
the
raw
mp4
and
then
we'll
have
somebody
edit.
A
It
add
on
our
our
front
logo,
clean
up
the
timeline
and
then
add
on
the
back
tail
end
part
and
then
publish
it
to
youtube.
A
B
And
I'm
going
to
go
ahead
and
add
a
resource
page
to
the
existing
artillia
site
and
I'll
include
the
links
sasha
that
you
have
been
passing
on
and
there
were
a
bunch
of
training
links
on
the
hacktoberfest
from
paige
from
digitalocean
that'll
also
collect
and
add
to
one
place
so
we'll
get
started
with
some
of
that
stuff,
even
though
it
won't
be
perfect.
It'll,
be
there.
A
So
that's,
I
think,
that's
all
I
had
on
the
list
that
give
you
that
heads
up
I'll
I'll
send
out
that
invite
after
we're
done
for
next
week
to
the
whole
group,
and
I
think
that's
all
I
have
anybody
else-
have
anything.
J
A
C
One
thing
which
I
want
to
add,
and
maybe
you
guys
can
correct
me
before
we
sit
across
our
preferences
on
this.
How
about,
if
you
know
you
see
you
and
tracy
can
probably
create
one
more
column
and
say
you
know
what
is
the
priority
for
you?
So,
for
example,
we
may
choose
rule
number
five,
but
row
number
five
is
the
lowest
priority
for
you
to
you
know
in
terms
of
obtaining
something.
A
Right
yeah,
we
can
do
that
we'll
add
on
our
what
we
think
are
our
priority
items,
and
then
that
way,
you
can
kind
of
see
what,
where
our
our
heads
are
on
this.
C
Correct
me,
you
know,
I
thought
this
would
be
a
good
idea
before
we
pick
up.
You
know,
items
from
this
whole
list.
A
Yeah
yeah
that
no
that's
a
great
a
great
suggestion,
because
you
know
we
have
the
big
picture
in
our
heads
and
that's
part
of
the
challenges.
We've
been
so
closely
coupled
to
this.
That
sometimes
that
that
you
know
it's
too
too
hard
to
see
what
needs
to
go
first
but
we'll,
but
that
makes
perfect
sense,
we'll
go
ahead
and
prioritize
that
and
give
you
an
idea
of
where,
where
our
minds
are
on,
what
we
think
is
gonna
be
needed.
Next.
B
D
B
B
If
you
came
on
late,
we
have
gotten
notice
from
tracy
miranda
that
we
are
in
the
there
has
been
no
objections
from
for
bringing
artelias
into
the
linux
foundation
and
under
the
cd
foundation
fold.
So
that
is
huge
for
us
guys
that
is
it's
and
gals.
It's
big.
It's
a
really
really
exciting.
It's
super
exciting.
B
A
Oh
and
because
there's
gonna
be
some
overlap,
there's
another
cdf
meeting
going
on
right
now,
it's
the
interoperability
meeting
and
one
of
their
topics
that
they
had
last
time
was
around
metadata
around
a
release
and
what
they
were
talking
about
is
exactly
what
ortelius
does
so
they're
gonna,
one
of
the
guys
over
on
that
side
was
going
to
start
a
proposal
or
a
document
about
what
data
should
be
gathered
for
around
the
metadata
for
a
release.
A
B
And
on
that
interoperability
note
I
think
what
we'll
do
in
the
future
is.
I
will
not
attend
the
architecture
calls
I
will
go
and
attend
the
interoperability
call.
So
we
have
somebody
on
that
from
ortillius.
A
Well,
we
may
just
need
to
bump
bump
our
call
over
to
another
time,
but
can
you
guys
see
my
screen
yeah.
B
A
So
one
of
the
interesting
things
when
you
look
at
so
spdx
real
quick
if
anybody
has
to
jump,
go
ahead
bounce,
but
what
it
has
to
do
is,
if
you
think,
like
a
node.js
package
or
python
package,
there's
information
that
they
want
to
start
collecting
around
those
and
a
lot
of
it
is
the
same
concepts
are
going
to
apply
to
ortelius,
because
if
you
look
at,
if
you
go
through,
basically
it's
like
this
json
data
that
you
collect
and
you
can
extract
it
out
of
the
package
and
gives
you
information
and
they
get
into
things
like
you
know
what
your!
A
What
should
your
your
date
format,
be
very
specific,
so
everything's
standardized
across
all
the
different
wait.
What
is
it
for
this
is
when
you
have
a
like
a
python
package,
you're
supposed.
B
B
A
So
what
are
the
licenses?
I
see?
What's
your
license,
you
know:
what's
your
your
copyright,
you
know
all
this
information
about
that,
but
the
interesting
part,
if
I
can
find
it
real,
quick.
A
B
Added
it
to
the
delivery
plan,
but
there
will
be
requirements
that
the
toc
asks
of
ortilius
with
regards
to
security
scanning
who
we're
using
we're
gonna
there's
a
as
an
incubating
project.
There's
gonna
be
things
that
we're
gonna
have
to
add.
B
Just
to
keep
that
in
mind,
that
might
be
something
steve
has
to
focus
on,
and
I
have
reached
out
to
phil
gibbs,
who
was
the
original
creator
of
a
lot
of
this
back-end
stuff
and
I
haven't
heard
from
him,
but
I'm
trying
to
get
him
to
come
back
to
the
community.
B
So
he
could
take
over
the
some
of
that
stuff
around
like
the
dm
script
of
python.
A
So
the
interesting
part
I
found
in
the
in
the
document
was
around
the
relationships
that
they're
looking
at,
and
this
is
something
that
we
can
pull
from
for
ortelius.
You
know
when.
A
You
know
a
depends
upon
b
dependency
of
manifest
of
build
dependency.
A
Now
the
part
that
we
have
a
you
know
runtime
dependencies
test
dependencies,
so
these
dependencies
are
interesting
that
we
may
need
to
start
looking
at
now.
The
complicated
part
is
when,
in
the
ortillius
world
we
can
have.
You
know,
50
component
versions
that
are
rolling
up
into
an
application
version,
and
then
how
do
you
do
this
roll
up
process?
A
I
think
the
groundwork
is
here
for
us
to
take
these
relationships
and
allow
us
to
roll
up
all
the
way
through
the
hierarchy
and
the
nice
thing
is.
If
we
look
at
this
this
standard
and
if
we
have
a
node.js,
that's
a
node.js
application,
that's
in
a
container
and
we
have
a
container
scan
that
can
go
and
pull
all
the
spdx
information
out.
We
put
that
into
our
database
and
then
our
component
versions
are
based
on
the
same
type
of
description.
A
Then
we
could
do
the
roll
up
very
easily
and
we
could
roll
up
all
the
way
from
the
individual
source
code
packages
through
everything,
that's
in
the
container
to
all
the
components
that
are
making
up
an
application.
All
the
way
up
the
the
tree
and
have
a
single
view
of
all
the
you
know
a
well-described
view
of
the
the
the
an
application
version
all
the
way
down
to
the
individual
files
that
are
out
there
in
inside
a
container.
So
it's
it's
interesting
thing.
Take
a
look
at
it
it.
A
I
think
so
that's
what
we've
got
to
look
at
is
to
look
at
how
we
can.
I
think,
I
think,
80,
almost
80
percent,
if
not
percent,
of
what
we
do
with
ortulius
is
gonna
cover
this
we're
gonna
call
things
different.
You
know,
like
this
case,
they're
talking
about
an
archive
file,
a
tgc,
well
that
in
our
world
is
going
to
be
a
instead
of
archive.
This
is
gonna,
be
a
component
that
contains
a
container
called
x.
F
A
So
it's
just
something
that
we
need
to
look
at,
because
I
think
we
can
really
leverage
a
lot
of
this
information
and
it's
been
out
there
for
a
while.
They
started
this
back
10
years
ago.
So
it's
a
pretty
mature
world
and
it
gets
into
you
know.
Even
if
you
look
at
and
I
skipped
over
it
but
licenses,
you
know,
every
single
node.js
package
has
a
license
associated
to
it.
We
should
be
able
to
roll
up
all
those
licenses
up
to
the
application
version
that
says
here
for
this
application.
A
When
you
go
to
your
security
group
or
your
auditors,
your
lawyers,
you
can
say,
here's
all
the
the
licenses
that
this
application
uses
and
it's
just
a
quick
and
we
just
generate
a
report
out
of
that
which
makes
it
super
easy
to
provide
that
peop
that
information,
the
people
that
are
asking
for
it,
because
that
comes
up
all
the
time
like
when
we
applied
for
to
be
members
of
the
cdf
I
had
to
go
through
and
list
every
single
license
that
we
used
underneath
the
covers
at
a
source
code
level.
A
So
and
it's
a
long
list.
It
grows
really
quick.
But
then
it
gets.
You
know
you
get
a
lot
of
repetitiveness
as
part
of
that,
but
that's
some
of
the
things
that
we
need
to
start
thinking
about.
So
take
a
peruse
at
it
and
you'll
get
an
idea.
It's
just
called
spdx.org.
A
I'll
throw
it
in
the
meeting
notes,
so
you
can
guys
can
have
it.
A
And
what
they
one
of
the
things
that
they
do
is
they
they'll
have
a
tool
that
you
can
actually
just
send,
there's
a
way
to
pull
out
the
a
json
file,
and
then
you
give
it
to
you
upload
it
somewhere
and
it'll,
validate
all
of
it
for
you
and
print
out
a
nice
report.
A
Yep
I'll
throw
it
in
the
the
minutes
here,
real
quick.
A
Okay,
I
think
that's
it
anything
else.
B
B
E
F
B
B
I'm
excited
too,
oh,
and
I
am
very
excited.
I
think
that
I'm
I'm
you
know
I'm
inspired
by
everybody
who
has
seen
the
need
and
said
hey.
This
is
something
we
need
to
fix
and
said
I'll
step
up
to
help.
So
it's
because
of
all
of
you
that
this
is
actually
becoming
a
reality,
and
I
think
all
of
you
from
you
know
they
always
say
from
the
bottom
of
your
heart,
but
it
goes
farther
than
that
really
we'll.
A
We'll
I
think
tracy
miranda
said
like
two
weeks
out:
they'll
have
the
official
and
then,
after
that,
we'll
do
donuts
and
beer.
E
B
D
A
D
F
B
I
really
missed
yeah.
There's
a
favorite
blue
bottle
place
over
by
the
convention
center
that
I
like
to
go
to
and
it's
right
around
the
corner
from.