►
From YouTube: Sept 21 - Ortelius General Meeting
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
A
B
A
So
a
couple
things
that
we
have
going
on
the
service
catalog
I've
gotten
the
like
a
a
website.
Basically
it's
the
service,
catalog
version,
all
the
work
that
we've
been
doing
with
the
microservices
and
the
changes
to
monolith
that
has
all
been
the
the
devops
process
has
all
been
streamlined.
So
when
we
make
coding
changes,
they
actually
get
pushed
out
to
dev.ortelius.io.
A
I
am
in
the
process
of
setting
up
a
corresponding
version
of
the
documentation.
That's
can
be
dev
specific
to
match
up
with
the
service
catalog,
so
we'll
have
another
domain.
I
believe
it's
gonna
be
dev
docs
that
ortilius
that
I
owe
here
in
a
couple
days.
A
So
I
have
when
you
check
in
on
a
the
service
catalog
branch
for
the
documentation
that'll
get
pushed
over
to
the
the
docs
at
that
level
to
the
new
doc
website.
So
we'll
have
the
old,
the
old,
the
current
documentation
and
a
new
documentation
will
be
up
and
going
in
parallel.
So.
B
Why
don't
you
just
show
them
the
process
of
going
through
it.
B
Go
to
artelia
show
and
go
ahead
and
review
the
how
to
sign
into
the
testing.
A
Yeah,
so
on
the
artelia's
home
page,
there
is
just
a
little
sign
up
section.
When
you
fill
it
out,
you
can
put
anything
you
want
for
company
project
name.
A
It's
a
little
slow.
We
haven't
put
a
lot
of
horsepower
behind
it,
so
that's
where
it
takes
a
little
bit
to
on
the
caching
side.
So
I've
just
said:
I've
just
slide
in
as
an
admin.
So
you'll
have
your
your
domain
that
will
be
available
and
we'll
have
a
couple
components.
The
hipster
store
will
be
out
there
as
part
of
the
sample
data
that
we'll
have
out
available.
After
the
sign
up,
we
go
and
bootstrap
the
hipster
store
sample
data
underneath
your
domain.
A
One
of
the
things
I
need
to
add
is
a
way
for
you
to
go
ahead
and
add
in
the
additional
service
catalog
data
like
the
readme,
the
swagger,
the
licenses
and
the
cbes
right
now.
This
is
not
part
of
the
import
process.
So
there's
just
a
couple.
Little
api
calls
that
we
need
to
make
to
populate
this
for
your
testing
data.
A
So
it's
not
not
anything,
that's
a
huge
monumental,
but
when
you
do
see
like
the
hipster
store,
these
will
be
empty.
To
start
with,
I
did
run
into
a
couple
things
if
you
do
run
into
an
issue:
just
go
ahead
and
open
the
issue
under
the
arterius
artillerius,
webs
github
repo
and
just
tag
it
under
the
service
catalog.
A
One
of
the
things
I
ran
into
yesterday
was,
if
you
go
into
like
an
application,
the
front-end
side's
a
little
confusing,
because
it
it
doesn't
hide
one
of
the
boxes.
So,
like
you
see
the
swagger
and
the
readme
are
still
here
well,
they
shouldn't
they
shouldn't
be
on
an
application.
A
So
there's
a
couple
rows
that
are
showing
up
some
things
that
are
getting
overlaid
and
things
like
that.
So
that's
like
one
of
the
issues
I
have
to
make
sure
it's
opened
and
we
take
care
of
that
on
the
on
the
front
end
side,
but
that's
basically,
it's
real
simple,
just
go
ahead
and
sign
up
and
you'll
get
your.
You
know.
Whatever
you
put
in
for
your
username
and
password,
that's
what
you'll
be
able
to
log
into
justdev.org.io.
A
On
that
front-
and
I
think
that's
the
main
stuff-
was
there
anything
else
you
wanted
me
to
cover
on
that
tracy.
B
A
The
hipster
store
import
data
was
created
two
years
ago
and
doesn't
know
anything
about
swagger
or
readme
or
cves
or
licenses.
So
the
data
for
the
hipster
store
is
like
two
years
old.
B
Let's
forget
about
the
hipster
store
for
a
minute.
Let
us
somebody
if
we're
testing
it,
we
should
probably
be
creating
new
components
to
test
it.
Does
this
stuff
not
work?
Should
we
not
try
to,
because
these
are
the
areas
that
I
had
tickets
open
to
test,
so
I'm
kind
of
confused
as
to
what
we
can
do
to
test
these
areas,
regardless
of
the
hipster
store.
A
A
I
don't
think
it's
been
documented,
yet
that
is
on
the
list
to
get
documented.
A
Well,
we
could
just
test
some
of
the
existing
components
already
pre-loaded
to
make
sure
they're
they're.
Looking
good
like
I
said
this
is
messed
up
here.
You
can
see
that
we
have
change
requests
that
are
are
scrolled
off
to
the
wrong
page.
There's
a
bunch
of
layout
issues
that
we
have
the
dependency
map
is
too
small,
and
those
are
types
of
things
that
we
just
needed
to
make
sure
that
we
have
eyes
on
to
make
sure
everything
looks
good
to
start
with.
A
B
A
Yes,
like
the
edit
button
you
could
go
in,
like
I
mean
here's
the
issue
right
now,
we
we
went
into
edit
mode
and
we
lost
all
of
the
pager
duty
information.
Okay,
so
because
there's
no
scroll
bar
it's
it's
little.
Things
like
that
that
that
need
to
be
that
we
need
to
start
with.
B
A
Shortcut,
okay,
repo
and
just
just
tag
it
as
the
service
catalog.
B
B
A
So
and
that's
where
the
documentation
needs
to
be
built
out
like,
for
example,
we
have
no
documentation
explaining
what
a
service
owner
is
or
what
the
slack
channel
means.
So
those
those
things
need
to
be
added
to
the
documentation
that
can
be
started
right
now,
without,
as.
C
A
So
just
moving
on
to
the
git
ops
side,
the
australian
working
group,
they
have
argo
up
and
running.
They
have
a
pretty
good
hand
on
argo,
adam
from
dynatrace
who's.
Familiar
with
captain
has
joined
the
group
and
it
looks
like
we're
kind
of
working
around
a
proof
of
concept.
That's
going
to
include
argo
captain
and
ortelius,
so
there
will
be
some
interaction
with
ortulius
and
the
get
repos,
and
then
argo
will
be
looking
at
the
git
repos
and
captain's
going
to
be
the
orchestration
tool.
A
So
ortiz
will
need
to
be
need
to
start
sending
and
receiving
events
from
captain
and
probably
argo.
Argo
sends
events
at
some
points.
So
that's
that's
kind
of
that's
getting
closer,
so
you're.
If
you're
interested
in
that
that's
on
thursdays
and
it's
8
30
sydney
time
in
the
morning.
A
Yep
then
we
have
our
podcast.
B
And
there
is
the
I
put
the
link
in
the
chat.
A
Yes,
if
you
want
to
go,
listen
to
it,
it's
just
a
quick,
a
quick.
B
And
and
sergio
has
a
a
podcast
he
put
out
there
as
well.
So
there's
two
and
I
have
updated
the
website
on
the
events
page.
It
has
the
of
our
our
new
podcast
channel.
So
all
of
those
will
be
showing
up
on
the
on
the
page
so
steve.
If
you
could
just
go
to
ortillius.io
and
go
to
that
page.
B
So
we
have
the
information
about
the
the
the
blog
about
hacktoberfest
is
out
there.
We
do
have
a
a
webinar
coming
up
on
october,
1st,
which
steve
will
go
through
how
to
contribute,
and
then,
if
you
scroll
down
the
podcasts
are
out
there.
A
And
these
are
on
buzz
sprout
right.
A
Cool-
and
I
thought
thank
you
arvin
for
interviewing
me
and
setting
this
up.
It
ended
up
being
just
over
10
minutes,
10
minutes
and
17
seconds,
so
it
ended
up
being
the
the
perfect
length
for
a
little
intro
into
what
artelias
is
doing
around
hacktoberfest.
B
And
if
you
look
at
the,
if
you
go
onto
the
google
groups
under
the
I'm
going
to
create
I'm
going
to
have
to
create
a
shared
drive,
I
believe,
because
I
do
have
an
opening,
an
introduction
opening
for
the
podcast.
So
if
you
do
one
I'm
going
to
create
a
space,
so
you
can
download
the
content.
A
So
siddharth
created
it
and
I
was
able
to
get
into
it,
so
it
should
be
fully
shared
to
the
google.
B
B
And
if
you
could
put
that
that
link
in
the
chat
and
everybody
on
the
call,
if
you
could
make
sure
you
could
get
to
that
drive.
A
So
now
we
have
the
outreach.
So
what
do
you
have
going
on
in
the
outreach
side.
B
So
we
are
focused
on
two
things:
for
the
outreach
side,
which
is
the
hacktoberfest
and
getting
ourselves
set
up
for
the
the
governance
elections
next
monday.
We
will
open
up
the
nominations,
so
please
consider
nominating
yourself
or
certainly,
if
there's
somebody
that
you
believe
should
be
on
our
governing
board
nominate
them.
You
don't
just
have
to
nominate
yourself.
You
can
nominate
other
people,
but
if
you
do
nominate
somebody
reach
out
to
them,
maybe
send
them
an
email
and
ask
them
if
they
would
be
interested.
B
So
that's
happening
on
the
27th,
so
we're
all
set
up
for
doing
that.
The
forms
are
all
created.
It's
just
a
matter
of
me,
making
them
public
and
then
hacktoberfest.
We
have
got
all
of
our
collateral
for
hacktoberfest
ready.
It's
all
been
posted
on
social
networking,
so
I
think
that
we're
pretty
much
done
with
doing
whatever
we
need
to
do
for
hacktoberfest
and
we
hadn't
planned
on
doing
any
other
activities
just
yet.
But
I
will
start
thinking
about
the
december
8th
event,
so
I
will
get
that
that
part
moving
forward.
A
So
on
the
hacktoberfest
for
some
of
you
folks
have
been
around
a
while.
We
will
need
help.
A
You
know
guiding
people
reviewing
pull
requests
those
types
of
things
if
you're
interested-
and
you
don't
think
you
have
the
right
permissions
in
github.
Let
me
know-
or
if
we,
if
you're
trying
to
do
something
in
github,
I
think
most,
everybody
should
be
set
up
to
be
able
to
do
like
review,
prs
and
approve
them,
and
things
like
that
and
comment
on
issues.
A
But
if
you
run
into
something
just
shoot
me
a
note
and
we'll
get
it
sorted
out,
but
we
will
need
some
additional
help
for
people
reviewing
stuff
to
make
sure
looks
good.
Last
year
we
did
have
a
couple.
People
come
through
that
were
trying
to
spam
our
project,
creating
some
bogus
prs
with,
like
a
one
word,
change
in
a
document
just
so
they
can
get
their
their
credit.
A
Have
any
other
comments
or
if
I'm
missing
anything
here.
A
So
I
think
that's
gonna
be
it
for
today
it's
good
to
see
you
dt
welcome
back.
We
haven't
seen
you
for
a
little
bit
hope
things
are
going
well.
B
B
C
B
Did
they
send
you
a
like
any
kind
of
little
image
or
something
yeah
yeah?
They
kind
of.
B
Would
you
say,
could
you
send
that
to
me
and
I'll
put
it
out
on
hootsuite.
C
Yeah,
should
I
email
you
that's.
B
B
A
So
please
everybody
enjoyed
her
session.
It
should
be
a
good
one.