►
From YouTube: Ortelius Outreach March 14, 2022
Description
Submitting talks to OpenSSF, DevOps Institute and podcast are the topics of this March 14th Outreach call.
A
B
Hi
everybody
so
today
is
monday
march
14th
outreach
meeting
for
ortelius.
Let
me
go
ahead
and
share
my
screen.
A
Off
the
ground
she
has
announced
a
group
I
am
on
the
I
am,
I
am
an
ambassador.
I
got
the
cdf
online
meetup
organizer
writes
back.
A
So
you
know
we
can
start
thinking
about.
We
want
to
do
something
with
that.
We
can
do
something
with
that.
I
was
going
to
do
something
with
the
cdf,
the
events-
cd
events
group
first,
but
was
there
something
that
we
were
going
to
do
specifically
with
them?
B
A
B
Yeah,
it's
it's
the
same
concept,
but
it's
under
you
know
the
cdf
organization
versus
the
cncf
side,
so
the
linux
foundation
is
broken
up
into
all
these
kind
of
sub
organizations
and,
like
there's
the
open,
ssf,
there's
the
open
source
security
foundation,
the
cncf,
the
cdf
and
there's
a
bunch
of
other.
I
think
there's
one
like
around
ai
edge
computing.
Those
types
of
foundations
are
out
there
as
well.
D
B
B
So
the
next
one
on
our
co
coding,
I
have
put
together
a
list
of
the
issues.
Let
me
find
them.
B
And
I
wasn't
sure
I
kind
of
broke
it
down
and
I
could
I
may
have
broken
it
down
to
granular,
but
what?
Because
we
have
the
same
changes
needed
across
multiple
repos
for
our
micro
services.
I
broke
one
broke
it
down
for
each
one,
so
we
could
kind
of
split
it
out
across
folks
at
that
level.
I
don't
know
if
that's
too
granular
at
that
level,
but
it
gives
us
an
opportunity
to
have
each
person
be
able
to
to
grab
an
issue.
B
This
first
set
with
the
updating
the
component
tamil
arvin
and
sasha,
worked
on
last
time
and
they're
still
going
through
it.
There's
a
couple:
pull
requests
out
there
that
I've
seen
in
the
in
the
different
repos
I
arvind
ended
up
putting
the
wrong
name
in
some
of
them,
so
I
have
to
go
back
and
make
that
correction
before
they
get
merged.
B
Also
sergio's
had
been
adding
on
repairs
tag
for
like
a
bug
level
issue,
so
those
those
are
out
there
as
well
to
hunt
down
as
part
of
that
process.
Utkarsh.
I
didn't
put
your
the
graphing
as
a
co-coding
event.
Unless
you
want
to,
I
wasn't
sure
how
far
along
we
were
at
that
point
to
really
branch
out
and
have
a
bunch
of
people
trying
to
work
on
that
that
issue.
D
I
think
that
is,
that
is
correct,
so
because
you
know
we
don't
need,
like
multiple
people
working
on
that
issue,
right.
Okay,
so
yeah.
B
And
then
there's
other
ones.
A
lot
of
this
stuff
is
mostly
around
like
devops.
You
know
this
is
all
like
our
artifact
hub
is
showing
f
and
that's
coming
from
our.
I
believe
our
chrome
was
able
to
go
through
and
fix
a
bunch
of
stuff,
but
we
just
didn't
get
follow
through
all
the
way.
So.
A
I
would
just
assign
that
to
sergio
he's
our
security
officer,
so
he
probably
should
look
at
that.
B
A
B
A
B
Yes,
so
on
arvin
you
put
the
wrong
name
in
for
the
component
names,
the
wrong
domain
name.
D
B
C
You
just
put
it
in
the
in
the
thread.
B
B
Yes,
I
could
put
it
in
the
issue
which
one's
and
also
we
need
to
make
sure
when
you
do
a
pull
request,
that
the
pull
request-
references
the
issue.
So
let
me
see
if
I
can
find
one
of
your
pull
requests.
B
So
like
on
this
one,
the
there's
a
github
action
and
if
you
want
to
automatically
close
the
issue,
you
have
to
reference
the
issue
in
the
initial
comment,
when
you
create
the
pull
request,
everyone
do
you
remember,
which
one
was
your
one
of
the
microservices
you
were
working
on.
I
think
it
was
like
this
store
yeah.
C
B
Yeah,
so
I
got
the
front
end
one.
So
in
the
initial
comment,
where
you've
created
the
issue,
you
can
well
the
way
it
is
the
way
a
character
looks
is
you
would
say,
fixes.
B
Artelias
and
then
let's
say
it
was
415
or
something
like
that
was
the
the
issue
number
when
you
do
that
format
like
that
it'll
automatically
close
the
issues,
otherwise
we
just
have
to
remember
to
go
close
them
manually,
but
it's
not
a
a
big
deal.
D
B
Message
right,
you
could
do
it
in
the
commit
message
or
when
you
initially
create
the
pull
request
I'll,
send
you
I'll
make
sure
there's
the
link
out
there
on
how
to
to
do
it.
It's
github's,
really
particular,
and
if
you
don't
get
in
the
right
place,
it
won't
automatically
happen,
but
we
want
to
make
sure
that
we're
cross-referencing
the
issues
with
the
pull
requests.
B
So
even
if
we
just
put
it
in
as
a
comment
we'll
be
able
to
get
make
sure
there's
a
cross
reference,
so
we
can
make
sure
everything
gets
closed.
So
on
your,
for
example,
on
this
one
here
it
was
where's
our
tamil
file.
B
B
Size
I
just
have
to
go
through
and
review
and
make
sure
that
they're
in
the
right
places-
and
I
just
haven't-
had
a
chance
to
get
caught
up,
but
that's
like
the
change
that
we
need
to
make
is
to
make
sure
that
the
the
hipster
store
microservices
are
going
to
the
hips
in
the
correct
hipster
store
domains
and
then
their
artillious
microservices
are
going
into
the
artillious
microservices
domain.
B
So
that's
kind
of
what's
happening
on
on
that
front
with
the
issues
and
stuff,
let
me
go
back.
B
So
that's
where
I've
been
added
those
labels
on
oops.
B
And,
like
I
said,
a
lot
of
this
right
now
is
just
getting
our
our
devops
pieces
cleaned
up.
There
are
some
coding
pieces
like
hunting
down
a
null
pointer.
This
is
more
of
a
documentation
issue.
That's
gonna,
be,
I
think,
yeah
I'll
be
in
a
doc
repo.
So
that's
gonna
be
a
markdown.
B
This
is
another
devops
stuff.
So
what
we
need
to
do
is
get
a
lot
of
this
devops
stuff
out
of
the
way.
So
we
have
clean,
builds
and
everything
being
recorded
correctly
in
for
the
the
data
around
the
microservices,
because
there's
more
more
information
that
we
need
to
keep
adding
to
our
micro
services,
so
adding
like
a
spdx.
B
That
we
can
use
to
create
our
s-bombs
that
will
scan
so
that's
another
like
devops
things
that
we
have
to
to
do
at
that
level.
So
that's
kind
of
where
we're
at
for
the
co-coding
event.
B
It
makes
it
easy
when
we
have
so
many
repos
and
the
same
change,
that
we
can
kind
of
divide
and
conquer
on
getting
these
updates
out
there
and
then
obviously,
then
we
have
to
make
sure
that
all
the
issues
get
closed.
So
once
we
get
it
everything
merged
that
we
get
the
issue
list
cleaned
up
as
well.
That's
why,
when
you
start
using
the
the
pro
requests
and
cross-referencing
the
issues,
that'll
auto
do
auto
close
for
you
at
that
level.
B
Any
questions
on
that,
so
that's
kind
of
where
we're
at
for,
like
the
first
pass
of
the
co
coding
and
we'll
we'll
tackle
another
set
of
these
on
thursday.
We'll
go
through.
Make
sure
that
we
have
all
these
done
and
then
we'll
go
on
to
like
the
the
s-bomb
for
cyclone
at
that
level
and
then
there's
other
cve
issues
that
we
still
have
to
keep
track
of,
because
if
you
wh,
where
I'm
looking
at
it.
B
It
should
show
our
vulnerabilities,
which
is
a
an
f
and,
I
believe,
chrome,
fixed
part
of
this.
I
think
he
fixed
the
base
image,
but
we
just
got
to
follow
through
all
the
way
to
make
sure
that
it's
good
to
go.
I
think
some
reason
has
to
do
some
research,
but
I
think
what's
happening
is
the
version
that
of
the
helm
chart
of
the
image
that
the
helm
charts
pointing
to
is
an
old
version.
So
it's
still
picking
up
the
old
cves
old
vulnerabilities,
even
though
we
fixed
it.
B
So
that's
kind
of
where
we're
at
on
that
front.
Let
me
jump
back
to
here.
B
And
so
tracy,
I
don't
know
if
it's
if
that
list
is
too
long
to
add
to
the
to
the
web
page,
but
maybe
we
could
just
add
some
general
categories
to
the
web
page
to
let
people
what
know
what
their?
What
we're
looking
for.
So.
A
A
You
think
that
you
can,
you
can
do
so.
B
A
B
Yeah,
so
we
have
one
two:
three:
we
have
like
six
up
for
grabs.
A
B
And
we
did
most
of
we
started
on
them
last
architecture
meeting
and
we
just
need
to
finish
them
up.
A
B
And
like
this
one
for
like
adding
spdx
s-bomb
to
our
microservices,
I
can
break
that
one
down
into
because
we
have
our
s
eight
or
nine
microservices.
I
could
break
that
down
into
nine
issues
if
it
makes
sense,
so
we
can
divide
it
up
that
way.
B
Yes,
that
is
a
big
change,
so
I
was
not
trying
to
we
have
that
issue,
but
it's
not
a
part
of
the
co-coding
event.
Okay,.
B
So
what
I'm
trying
to
do
to
get
to
is
being
able
to
get
a
release
out.
We
haven't
had
a
release
out
for
over
a
year,
and
this
little
stuff
is
just
holding
us
back
to
get
it
get
to
get
the
release
out.
A
So
yep
anything
you
want
me
to
I'll
touch
base
with
you
in
terms
of
what
you
want
me
to
add
for
the
the
blog.
B
Okay,
okay,
yeah.
I
think
it's
just
gonna
be
like
these,
these
six
five
or
six,
that
we
have
okay,.
A
B
And
then
from
there,
okay
and
then.
A
On
the
t-shirts
I'm
trying
to
figure
this
out,
so
I've
been
talking
to
him.
What
my
our
problem
is
is
that
I
want
a
lighter
t-shirt,
one
that
is
a
mix
of
rayon,
polyester
and
cotton,
so
they're
not
really
heavy,
and
a
lot
of
the
ones
that
are
affordable
are
pure
cotton
and
they're
kind
of
heavy.
So
I'm
trying
to
find
a
lightweight
cotton
and
apparently-
and
I
just
learned
this
over
the
weekend-
is
that
when
you
use
a
rayon
and
polyester
most
of
the
shirt
presses,
I
can't
handle
it.
A
C
A
B
Yeah
then
we
have,
I
think
the
call
for
pay
for
cdcon
is
over.
B
A
All
right,
so
we
are
still
looking
for
a
person
to
speak
for
this
year
for
this
month's
podcast,
if
anybody's
interested
and
being
on
the
podcast,
just
let
syme
know,
and
then
I
put
in
the
the
chat,
the
docs
for
the
may
20th
visionaries
event
if
you
are
going
to
get
your
name
added
to
that,
all
you
got
to
do
is
we're
looking
for
10
minute
talks
this
time
and
I've,
given
a
few
suggestions
on
what
we
can
do
and
it
looks
like
we
have
utkarsh
has
got
his
in
and
simon's
got
his
in
so
arvin.
A
And
that
comes
up
really
fast.
This
is
the
middle
of
march,
so
we
have.
We
have
basically
two
months
to
pull
it
together,
which
is
a
bigger
run
that
we
usually
have.
We
usually
do
it
in
the
last
four
weeks.
B
I
that's,
we
should
probably
start
looking
at
other
call
for
papers.
There's
gonna
be
some
more
shows
coming
up
that
we
should
probably
keep
an
eye
out
for
okay.
B
Yeah
that
one's
a
weird
one,
because
it's
like
it
kind
of-
does
come
into
the
service
catalog
around.
But
I'm
not
you
know
I've
never
been
to
that
one.
So
I
don't
know
what
their
their
typical
topics
are.
Yeah,
who
krishna
awesome,
have
you
ever
been
to
or
arvind
have
you
ever
been
to
container
co
or
container?
D
Actually,
like
most
of
the
cloud
native
products,
they
have
their
own
cons.
So,
like
argo,
has
argo
con
and
similarly
few
other
products
have
their
own
conferences.
B
A
Okay,
well
steve
you,
yes,
we
could
submit
to
this
up
until
today,
I'll
I'll,
submit
one
and
I'll.
Let
me
post
it
in
case.
Anybody
else
is
interested
in
trying
to
get
something
in
today.
B
But
if
anybody
sees
those
you
know,
let's
try
to
keep
track
of
them,
so
we're
not
trying
to
scramble
the
last
day
to
to
do
a
submission
like
today,
and
I
it's
going
to
be
one
of
those.
I
think
some
of
these.
B
With
the
transition
from
where
a
lot
of
these
shows
are
trying
to
go
back
in
person,
and
they
don't
quite
know
if
they're
doing
high,
you
know
where
the
speaker
has
to
be
in
person
or
so.
A
So
the
ones
that
we
really,
I
think,
the
the
one
the
easy
ones
to
get
into.
I
don't
know
if
it's
easy
but
easier,
are
anything
any
of
the
skill
up
days.
That
devops
institute
is
having
they
have
one
a
month
and
they're
different
topics,
so
we
should
start
submitting
to
be
into
those.
A
Let
me
look
if
let
me
look
for
events,
so
this
month
is
over.
It's
this
month,
actually
is
happening
in
three
days
march.
17Th
is
this
months.
A
A
17Th
is
on
kubernetes
and
then
I
believe
april
21st
is
cicd,
so
we
should
be
looking
at
submitting
talks
for
the
april
21st
event.
Let
me
just
oh.
B
A
Now,
let's
see
a
cfp,
but
I
know
I
don't
think
it's
closed
yet
see.
This
is
the
thing
I
could
go.
Look
at
slack
and
I
have
to
go
hunt
through
slack
to
my
previous
stuff
I'll
find
out
where
the
cfp
is
for
the.
I
think
that
they'd
have
it
really
obvious.
B
Oh
and
also
on
the
the
devops
institute,
they
do
do
an
ambassador
program
there
as
well.
B
So
if
you
want
to
become
an
ambassador
around
a
specific
topic,
so
like
cicd
or
you
know,
service
catalog
or,
however,
you
want
to
do
it,
you
can
get
involved
in
that
organization
as
well
for
doing
talks
and
that
one's
good.
If
you
want
to
get
your
name
out
as
a
speaker
and
then
you
kind
of
work
up
the
ladder
to
the
bigger
talks
from
there.
A
Okay,
so
to
become
a
speaker
for
the
april
cicd
event,
I
just
put
the
link
to
the
page
and
then
you
scroll
down
and
you
submit
that
an
email
to
them
and
they'll
send
you
a
form
and
what
I
would
suggest
is
you.
Let
them
know
that
you
are
working
on
the
ortilius,
open
source
project
and
we'll
try
to
get
some
artillious
talks
into
that
event.
A
A
So
here's
session
eyes-
I
don't
know
how
I
log
into
this-
was
it
through
google.
A
All
right
so
here's
my
talks
and
I
think
you
can
look
through
events
here
and
only
speakers
of
public
profile
said.
Oh
okay.
Well,
I
have
spoken
before
at
here's,
my
swamp
up
ones.
Well,
I
guess
not.
I
thought.
Maybe
I
could
search
the
sessionize
the
events
and
then
submit
it,
but
apparently
I
don't
have
access
to
that.
A
B
Oh,
it's
gonna.
Try
to
find
you
talks.
A
B
A
A
Right
so
now
you
get
now
now
there's
a
list
of
them,
so
my
suggest
my
suggestion
would
go
ahead
and
set
up
a
sessionize
account
and
then
you
can
go
through
these
and
see
them.
I
thought
skill
updates
was
in
here,
but
I
don't
see
skill
of
days.
I
thought
for
sure
they
were
using
session
eyes,
but
that's
one
way
to
go
about
finding
talks
that
you
might
be
interested
in,
but
do
try
to
submit
an
email
to
the
folks
at.
A
And
they're
having
a
in
person
festival
in
in
denver.
So
here
are
the
here's.
This
is
happening
this
week
and
so
then
the
next
month
will
be
ci
cd.
We
have
devsecops,
we
we
can.
We
can
submit
easily
to
this
one.
We
can
submit
a
ton
to
this
one,
I'm
not
sure
how
much
we'll
be
able
to
do
that
one,
but
we
can
do
probably
do
some
stuff
around
cloud
native.
A
And
utkar
arvind
before
I
did
you
ever
get
a
chance
to
look
at.
I
know
steve's
got
you
got,
have
you
has
you
doing
some
stuff?
Did
you
ever
take
a
look
at
cookie
cutter
or
backstage.
A
A
I
feel
like
we
really
should
be
thinking
sooner
than
later
about
getting
an
integration
done
to
backstage,
and
I
don't
oh
karsh.
I
don't
think
it
would
be
very
hard
there
may
be,
because
they
have
tags
that
we
could
associate
to
our
domains
and
they
and
there
they
have
all
the
other
information.
So
I
feel
like
we
should
be
able
to
bring
it
over.
D
Yeah
I
mean
like
I'm
still
investigating.
A
Okay,
I
think
that
would
be
a
really
interesting
partnership
for
us
and
I'll
I'll
make
sure
they
have
the
two
of
you
invited.
Should
I
get
a
response
back
from
the
guy
from
rhodey.
B
B
All
right,
just
this
coming
thursday
we're
going
to
do
the
co-coding
event
again
same
time
same
start
time
as
today,
but
we'll
go
like
into
an
hour
hour
and
a
half
just
depending
on
how
we're
we're
moving
along.