►
From YouTube: July 27, 2021 Ortelius General Community Meeting
Description
A review of the Governance document, the service catalog release and the summer schedule is included in this meeting.
A
A
The
13th-
maybe
yes,
on
oh
interesting
on
friday,
the
13th
of
august.
We
will
do
a
governance,
working
committee,
kind
of
kickoff,
so,
if
you're
interested
in
working
on
the
governance,
I
am
going
to
go
through
it
really
quick
here,
there's
a
document
that
I'm
going
to
go
ahead
and
share,
so
everybody
make
sure
you
can
get
to
it.
We
made
some
changes,
I'm
just
going
to
go
over
that.
So
you
can
be
thinking
about
it.
We
put
it
in
the
chat
and
yes,
please
sign
in
to
the
this
document
in
case.
A
Okay,
so
we're
working
on
bylaws
for
a
governance
board
governance
boards
are
important,
because
if
we
ever
get
to
a
point
that
we
can
say
that
we're
we
want
to
apply
to
be
a
graduated
project.
We
have
to
have
a
governance
board
and
the
governance
board
will
be
allow
us
to
create
different.
I
guess
you'd
call
roles,
so
I
worked
on
this
document
over
last
week.
A
The
important
things
that
I
want
to
cover
in
particular
is
how
we
have,
at
this
point,
been
talking
about
laying
out
the
governance
board,
so
the
way
that
the
governance
board
itself
would
work
is
we've
copied
this
after
jenkins
as
much
as
possible,
but
we've
added
additional
seats
in
the
same
way
that
kosuke
stayed
on
the
board
with
jenkins.
We
have
put
steve
taylor
as
the
permanent
fixture
on
the
governance
board
and
he
can
remain
on
the
board
until
he
decides
to
step
down.
A
Then
there's
an
additional
six
board
members
in
our
elections
and
that
will
kick
off
in
september.
We'll
have
two
well,
three
people
run
for
two-year
terms
and
three
people
run
for
one-year
terms.
This
allows
us
to
have
a
rotating
board
because
there'll
be
follow-up
elections
every
year.
Now
the
people
who
run
for
one-year
terms
can
run
for
re-election,
and
then
they
would
have
a
two-year
term.
So
only
in
the
first
election
do
we
have
people
with
one-year
terms.
A
No,
no
single
company
or
organization
shall
have
employees
or
reps
that
make
up
more
than
50
percent
of
the
board
and
we'll
follow
the
you
know.
The
standard,
robert's
rules
of
order
and
running
the
board
there
will
be
the
governance
board
once
once.
Formed
and
elected
will
have
officers
and
they
have
to
have
a
minimum
of
two
officers.
A
A
So
those
are
five
total
we
probably
would
have
one
more
so
each
each
person
on
the
board
would
have
a
a
a
role,
and
then
we
have
two
additional
people.
These
are
non-voting
board
attendees
and
they
will
be
there's
going
to
be
two
positions
that
are
non-voting.
A
We
often
call
them
non-binding
because
they
can
provide
input
in
what
they
think
it
does
how
a
dis
decision
should
be
made,
except
that
only
the
elected
board
gets
to
vote
and
there'll
be
two
of
those
one
will
be
a
general,
a
a
chairperson
for
the
champions
and
a
chairperson
for
the
ambassadors
right
now,
steve
is
serving
as
this
chip
the
champion
chair
and
siddharth
is
serving
as
the
de
facto
ambassador
chair.
A
So
we
want
to
have
those
as
elected
positions,
and
those
elected
positions
will
be
always
be
invited
to
the
board
and
be
part
of
the
board
discussions,
and
then
I'm
leaving
it
open
where
the
board
can
invite
other
individuals.
So
we
can
have
the
board
open
or
they
can
or
the
board
can
decide
to
have
those
decisions
closed
that
will
be
left
up
to
the
board.
If
the
board
wants
it
to
be
open,
anybody
can
attend
and
anybody
can
have
a
non.
A
A
non-binding
vote,
but
they'll
have
to
have
at
least
invite
these
two
individ,
these
two
individuals
to
the
board.
The
way
the
elections
will
work
is
we
will.
We
will
have
the
elections
each
september,
and
I
don't
think
I
went
through
this
before
we
didn't
change
any
of
this.
The
general
members
of
the
community
will
be
encouraged
to
nominate
themselves
or
others
to
the
board.
Anyone
can
be
nominated
to
the
board,
so
let's
say
we
decide.
We
want
to
nominate
tracy
miranda
to
be
on
our
board.
A
Even
though
she's
not
part
of
the
ortillius
community,
she
can
be
nominated
to
the
board,
but
only
people
who
are
right
now,
I'm
going
to
do
it
based
on
everybody
who's
in
the
google
groups.
So
you
have
to
be
officially
part
of
the
google
groups
in
order
to
be
able
to
vote
those
in
those
emails
that
are
in
the
google
groups
will
be
sent
to
a
let
them
know
that
there
is
a
vote
coming
and
that
we
want
to
use
this
voting
a
voting
service.
A
There
is
this
document,
and
then
there
is
another
document
that
covers
this
in
a
powerpoint,
but
this
is
where
the
core
of
the
material
is
so
I'd
encourage
you
to
take
a
look
at
it.
A
If
there's,
if
you've
been
on
a
board
before,
if
you've
worked
in
an
open
source
community
and
we're
forgetting
something
about
the
the
governance
board,
that
we
need
to
be
reminded
of
and
needs
to
be
added,
please
just
go
ahead
and
add
it,
and
then
we
will
have
our
meeting
on
the
13th
to
cover
it
and
right
now,
since
we
don't
have
a
board,
it
would
just
be
a
general
member
whoever's
on
the
working
committee
for
that
governance
board,
we'll
get
to
approve
or
not
approve
and
we'll
work
on
it
until
we
get
it
done,
and
we
have
to
have
it
done
by
september
the
24th
and
ready
to
send
out
the
votes.
A
So
we
did.
I
think,
there's
been
a
lot
of
work
done
on
it.
I
don't
know
how
much
more
work
that
we
will
put
on
it
in
it
until
the
13th,
so
any
updates
will
be
super
appreciated,
there's
also
another
doc,
that's
darth
and
the
folks
who
are
working
on
the
the
podcast.
We
still
really
need
to
get
our
podcast
going,
I'm
not
even
going
to
think
about
it
until
september,
but
there
is
a
shared
doc
out
here
and
let
me
quickly
see
if
I
can
find
it.
A
A
Let
me
just
look
with
shared:
where
would
they
have
put
it
and
steve?
While
I
do
this,
if
there's
anything
you
want
to
cover
and
I'll
find
this
other
yep.
B
So
just
a
quick
thing
on
the
board:
it's
it's
really
good
to
put
that
on
the
resume,
so
you
know
think
about
it.
You
know
running
for
the
board.
You
know
it's
one
of
those.
When
people
look
at
your
resume,
it's
definitely
a
plus
to
have
on
there
when
you're
working
with
the
open
source
community
and
your
board
member.
B
B
So
most
of
everything
has
been
focused
around
the
components
I'm
going
to
go
into
this
one
component,
and
you
can
see
that
we've
split
the
boxes
apart.
We.
B
Service
catalog
information
like
the
service
owner,
the
email,
the
phone
numbers
and
then
to
the
next
part,
is
we
brought
in
the
readme
file
so
as
part
of
the.
B
Our
python
program,
that
fits
into
like
the
jenkins
pipeline,
we
actually
grab
the
readme
file.
That's
the
markdown,
coming
from
the
git
repo
and
we've
brought
that
in
so
we
have
a
full
markdown
of
for
this
service.
You
know
what
the
readme
is
and
then
also
the
swagger.
B
We
brought
that
in
as
well
ukash
that
this
is
where
I
took
your
code
that
you
gave
me
and
and
brought
it
in
so
yeah.
It's
actually
interactive
when
we
can.
Actually,
you
know,
do
different
things
with
it
right
here
inside
of
the
the
ortelius
ui
and
then
what
we've
been
working
on
lately
is
scanning
for
cves
and
licenses.
B
We
actually
have
a
package
out
there
that
doesn't
have
a
license,
and
then
we
have
a
you
know
all
the
different
licenses
and
I
can
click
on
these
and
it'll.
Take
me.
Actually,
let
me
go
to
a
different
one.
Pick
the
wrong
one
go
to
mit,
see
if
that's
gonna
bring
it
it'll,
bring
us
actually
to
the
license.
That's
part
of
the
spdx
spdx
tracks,
all
the
licenses
that
are
out
there
and
that's
what
this
long
list
is.
B
So
that's
some
of
the
stuff
that
we're
bringing
in
cves
will
work
the
same
way.
Well,
we'll
have
the
the
package,
the
cve
in
the
package
and
a
link
over
to
dive
into
the
cbe
details.
B
Some
of
the
other
things
we
did
was
we
moved
some
of
the
the
boxes
around.
So
the
deployments
we
moved
to
the
bottom
and
I
believe
the
dependency
map
is
now
down
here.
I
don't
know
if
this
is
where
they're
going
to
stay,
but
I
just
got
them
out
of
the
way
for
now,
so
we
can
get
get
all
get
all
the
service
catalog
data
together.
B
B
C
B
Be
really
big
yeah
and
in
the
coding
I've
been
focusing
on
bringing
in
the
the
new
data
and
once
we
figure
out
where
we're
going
to
move
this,
then
I'll
get
it
resized.
So.
B
Okay
and
then
we'll
just
add
some
some
a
larger
size
to
that.
That's
not
a
problem.
A
I'm
thinking
that,
though
the
dependency
map
you
have
these
other
map,
like
you,
have
deployed
environments
right.
B
Yeah
there's
some
boxes
that
we
like
endpoints,
that's
a
very
short
list.
Key
value
pairs
can
be
a
smaller
list
and
it
can
grow
for
bringing
in
like
a
whole
properties
file
for
a
cluster
for
the
service.
So
this
scroll
bar.
B
Yeah
and
there's
some
things
like
this
one
consuming
applications
is
usually
just
fifty
percent
of
the
screen,
because
it's
such
a
small,
but
I
just
had
to
move
them
some
things
around.
A
A
If
anybody
wants
to
start
working
on
any
kind
of
documentation
for
this
now
steve
is
there
a
place
that
we
can
get
to
it
yet.
B
No,
I
have
not
checked
this
in
yet
I'm
still,
I
I
should
have
it
by
the
end
of
the
week.
I
should
have
something
out
there.
Part
of
it
is.
B
We
have
to
change
the
installation
instructions,
because
this
is
based
on
microservices
so
to
install
and
use
this
now,
instead
of
just
being
a
single
docker
container,
it
needs
to
run
in
kubernetes,
so
the
install
process
is
is
going
to
be
the
first
thing
that
gets
documented
and
there
will
be
changes
like
helm,
charts
that
will
be
created
and
stuff
like
that
to
do
the
deployment
so.
A
Do
you
have
tickets
open
for
that?
So
anybody
might,
if
anybody's
interested
in
working
on
that
through
the
summer
the
summer
break,
might
be
an
interesting
project.
B
B
Part
of
that
out
here,
yet
we
do
have
things
like
updating,
docker
images
to
get
ready
for
that
going
into
kubernetes,
but
we
don't
have
the
like
the
the
istio
or
nginx
routing
in
place
for
kubernetes.
We
don't
have
a
ticket
for
that
I'll.
Add
those
things
so
they'll
be
out
there
to
use.
B
So
that's
kind
of
where
we're
at
it's
coming
along
really
nice.
So
that's
what
we
have
and
gonna
be.
You
know.
Some
of
the
things
that
we'll
have
to
do
is
we'll
actually
be
using
artelius.
B
D
B
That's
what
I
have
going
on
and
thank
you
so
much
for
working
on
this
he's
been
a
big
huge,
huge
help,
pulling
all
the
data
together
from
the
microservice
perspective.
We've.
Actually,
one
of
the
things
that
we've
done
is
put
a
wrapper
around
some
of
the
cyclone
and
python
scanning
tools.
B
B
B
B
A
Okay,
the
other
doc
that
I
was
going
to
share
with
you.
Everybody
should
have
it
now,
it's
in
the
chat.
This
is
this
is
the
outline
for,
if
you're
going
to
host-
and
this
is
what
we
hope-
that
we
will
be
doing
in
the
fall
as
we'll
really
kick
these
podcasts
off
and
we'll
have
different
people
hosting
and
different
people.
Presenting
that
way,
everybody
gets
an
opportunity
to
be
a
personality
and
everybody
gets
an
opportunity
to
be.
A
Somebody
interviewed.
So
this
is
just
what
the
it
will
look
like.
It's
a
suggestion
of
how
the
show
should
run
things
to
look
at
if
you
want
to
add
anything
for
this,
just
a
template
is
like
here's,
some
reoccurring
questions,
the
two
things
we
ask
everybody
on
the
show
tell
us
something
about
cloud
native
that
you
recently
learned
and
what's
one
thing
you
wish
you
would
have
known
sooner,
and
so
it's
just
a
format.
A
So
if
you
want
to,
if
you're
interested
in
being
involved
in
it,
that
has
been
shared
with
everybody
and
you
guys
can
take
a
look
at
it
and
add
what
you
want
and
put
anything
out
there
that
you're,
you
think
it
should
look
like
and
then
we'll
probably
have
a
a
call
on
it
in
the
in
the
ambassador,
calls
in
the
early
part
of
september
and
start
reading
them,
because
we
have
everything
else.
A
I
think
in
order
to
do
it,
and
I
think
we
are
up
at
seven
minutes
before
our
30
minutes
is
up.
I
am
going
to
open
it
up
to
everybody
and
ask
if
there's
anything
that
we
have
missed,
that
we
should
be
talking
about
or
any
other
anything
that
anybody
wants
to
cover
before
heart.
We
close
out
our
last
community
meeting
before
our
summer
break.
B
Tracy,
can
you
post
that
link
back
in
the
chat
it
didn't
come
across
you?
It
was
the
old.
It
was
the
wrong
link.
A
A
A
And
I
think
we
have
potentially
a
new
person
hudson,
you
want
to
introduce
yourself.
A
Well,
thank
you
for
coming.
I'm
glad
you
were
able
to
make
it
to
our
our
our
last
one
of
the
of
the
summer
yeah
the
summer
everybody's
been
working
so
hard,
it
just
made
sense,
but
hudson
we
are
going
to
continue.
The
architecture
calls.
So
everybody
you'll
see
on
your
calendars
that
you
still
have
architecture
meetings
and
we
need
to
do
that
because
of
the
work
we
need
to
do
to
get
the
release
that
steve
just
showed
out
the
door.
A
So
if
you
have
not
started
contributing
and
this
this
would
be
a
really
good
area
to
do
so,
especially
if
you
want
to
learn
more
about
kubernetes
and
running
installers
and
some
of
the
basic
stuff
that
we're
doing
on
that.
That
would
be
a
good
project
to
start
on
and
as
everybody
here
knows,
but
hudson
you
may
not
know
you
could
always
reach
out
to
steve
steve.
Would
you
post
your
your
calendar.
A
B
So
I
just
on
the
arcturus
website.
If
you
go
over
to
ask
the
expert,
there
will
be
the
for
me
just
to
click
on
that
and
it
will
bring
up
my
calendar
and
you
can
pick
a
time
and
that
works
for
you
and
then
tracy's
is
out
there
as
well.
Also
if
you
need
to
do
a
one-off,
I'm
on
the
the
discord
channel.
B
So
that's
the
easiest
way
we
do
have
a
lot
of.
If
you
have
like
a
question
on
how
to
do
something
or
if
you're
looking
for
something
the
fastest
way
is
to
post
it
on
the
the
discord
channel,
because
there's
more
people
watching
that
and
they
can
jump
in
and
get
you
what
you
you
need.
B
Yep
that
works-
I
will
be
here
working
on
the
you
know,
wrapping
up
our
service
catalog
release
so
feel
free.
Whenever
you
can,
you
know
whatever
time
works
on
for
you.
That's
on
my
calendar.
Just
go
ahead.
Grab
that
time
slot
and
usually
the
I
think
that
one
is
like
15
minutes
or
a
half
hour,
but
if
we
need
to
take
more
time,
we
can
as
part
of
that
process,.
A
All
right,
everybody,
if
we
don't
talk
to
you
sooner,
have
a
great
august,
get
some
down
time.
Go
hike,
jump
in
some
water
do
whatever
it
is.
That
makes
you
happy,
because
september
is
going
to
get
busy
again
and
with
september
we
have
a
show
starting
again.
It'll
just
be
it'll
just
start
adding
up.
So
I'm
hoping
you
all
can
take
some
good
down
time.
I
plan
on
riding
horses
for
the
next
four
weeks.
I'm
going
to
do
that
as
much
as
I
can.
B
And
what
I'll
do
is
when
I
get
those
issues
created
around
documentation
and
the
kubernetes
for
our
microservices,
I
will
ping
everybody
on
discord
to.
Let
you
know
that
there's
new
issues,
if
you
want
to
grab
something
to
to
take
a
look
and
work
on
if
you're,
not
an
expert
in
any
of
that,
that's
not
a
problem,
we
will
work
with
you
to
teach
you
the
skills
that
you
need
to
implement
those
things
so
alrighty.
Thank
you.
Everybody,
hey.