►
From YouTube: Ortelius General Community Meeting - November 3, 2020
Description
The General Community Meetings review the overall project progress with updates from the Architecture/Markeplace and Outreach Working Groups.
A
B
Hey
hello,
everyone,
my
name
is
nitin
bhandari
and
I
am
a
graduate
student
in
computer
science
at
university
of
new
mexico
I'll
be
graduating
in
december
2020
and
yeah.
Looking
for
full-time
opportunities
right
now,
and
as
far
as
my
open
source
contribution
is
concerned,
I
mean
I
haven't,
contributed
to
any
open
source
till
now,
but
yeah.
A
B
A
Hold
it
up
higher
there
we
go.
You
got
the
top
presenter
award
at
devops
world,
which
is
pretty
awesome
because
his
talk
centered
around
this
particular
issue
that
we're
attempting
to
solve
with
with
ortilius.
So
that
was
pretty
exciting
that
we
had.
He
had
a
huge
amount
of
people
show
up.
They
stayed
on
for
almost
the
entire
time
and
his
topic
was
pretty
relevant.
A
D
D
D
We
did
run
into
problems
with
the
we
are
seeing
problems
with
the
bridge
between
wordpress
and
sas
the
sas
version,
and
I'm
going
to
work
on
removing
that
this
week
and
it
may
go
into
next
week
to
get
to
get
that
coding
done.
We
did
talk
about
our
goals,
the
top
ones
for
q1
q2,
were
the
website
redesign
and
that
we
there's
a
meeting.
Last
week,
a
bunch
of
people
met
with
mark.
A
D
A
Overall,
summary
of
that
is
that
there
are
a
couple
of
tools
we
need
to
come
up
with
an
a,
I
think,
persian.
You
were
going
to
work
on,
maybe
a
design
for
the
front
end.
So
we
have
an
idea
of
what
we
need
to
include
in
it
and
there
are
different
tools
that
could
be
used,
but
I
think
everybody
agreed
that
markdown
was
probably
what
we
wanted
to
stick
with,
even
though
there's
something
called
ascii
docs,
which
I've
never
seen
before.
I've
never
used.
A
There
were
pros
and
cons
on
both,
but
even
the
jenkins
folks
said
that
more
people
are
interested
in
using
markdown
than
ascii
docs.
So,
whatever
you
know,
a
hugo
server
may
be
what
we
want
to
stick
with,
so
we
can
build
it
in
and
owen
thought
that
markdown
we
could
create
headers
and
footers
around
the
markdown,
and
it
would
suffice,
siddharth
and
pershot.
You
guys
were
there
I
wanted.
Is
it?
Was
there
any
other
takeaways
from
that
that
steve,
steve
and
nitin
should
hear.
E
D
A
D
And
we
can,
we
could
get
to
that
part,
because
we
have
there's
a
lot
of
options
now
and
that's
some
of
the
things
in
architect.
What
we've
been
doing
on
the
development
side
is
we're
actually
using
github
actions
as
well
as
google
cloud
build,
so
we're
mixing
in
ci
cd
tools,
sprinkling
them
around
here
and
there
to
do
some
automation.
D
D
Yeah
for
the
yeah,
so
the
way
they
they
have
jenkins
wired
into
the
the
jenkins
website
repo.
So
when
you
do
a
pull
request
that
a
bunch
of
automated
stuff
happens-
and
this
is
this-
is
the
same
thing
like
with
the
cdf
landscape-
I
don't
have
ever
seen
that
or
the
cncf
landscape
anytime,
there's
a
pull
request
and
the
pull
request
gets
approved
after
all
the
reviewers.
D
So
that's
what's
happening
with
a
lot
of
these
hooks
that
we
have
into
into
github
is
once
we
do
something
once
we
do
a
pr
and
we
go
through
a
series
of
steps,
then
we're
good
to
go
all
the
way
automated
from
there.
So
that's
kind
of
like
the
the
process
is
everything
is
focused
around
the
pull
request.
D
B
So
just
just
a
question
I
wanted
because,
like
I
am
not
aware
of
ci
cd,
so
much
so
you
are,
you
were
talking
also
about
like
incorporating
github
actions
and
during
the
conference
I
heard
like
people
I
mean,
along
with
jenkins
many
people
use
like
travis,
ci
circle,
ci
and
those
stuff
also
right.
So
any
particular
reason
why
we
are
using
jenkins
over
here.
D
Well,
jenkins,
is,
is
one
of
the
projects
in
the
cdf,
and
we
like
to
so
there's
jenkins,
jenkins,
x,
tecton
and
screwdriver
are
the
four
cdf
projects,
so
we
like
to
support
those
tools
as
well
as
part
of
the
process.
You
know,
but
that
doesn't
mean
you
know
right
now.
It's
we're
all
over
the
place
as
part
of
what
we
have
for
a
cdi
cd
tool
right.
D
A
But
certainly
supporting
one
of
the
the
projects
is
going
to
be
our
best.
If,
if
we're
invited
into
the
cd
foundation,
what
we
really
need
to
do
is
make
sure
that
not
only
are
we
consuming
the
cd
foundation
dog
food
as
they
say,
we
also
need
to
make
sure
we're
integrating
with
all
those
those
tools.
So
we
have
integration
points
with
spinnaker
and
screwdriver
and
jenkins
and
jenkins,
x
and
techton.
D
D
A
D
A
A
D
E
D
F
A
A
I
only
have
heard
good
things.
I
haven't
heard
any
major
issues
that
they
would
have.
In
fact,
the
jenkins
team
wants
to
start
doing
cross
post
with
us
and
wants
to
do
find
out
more
how
they
can
integrate.
The
thing
about
jenkins,
is
you
have
to
remember,
is
that
it
doesn't
do
deployments
and
other
tools
in
the
market
in
that
space
does
well.
Spinnaker
does,
for
example,
so
jenkins
has
a
lot
of
motivation
to
find
out
ways
that
they
can
evolve
the
standard
jenkins
pipeline
to
support
microservices
in
a
in
a
more
sophisticated
way.
A
A
And
there's
a
lot
of
very
interesting
people
on
that
working
group.
If
you
have
any
interest
at
all
in
in
working
in
that
space,
there's
a
a
lot
of
very,
very
interesting
people,
working
for
really
big
companies.
On
that
you
know.
There's
the
two
james
is
from
cloudbees
there's
somebody
from
red
hat.
So
it's
an
interesting
group.
One
of
the
release,
people
from.
D
Ebay,
that's
right
and
then
the
the
thing
is
when
you
start
working
with,
especially
for
you
newton
when
you
start
getting
involved
with
these
folks-
and
you
start-
you
know,
talking
to
you-
know
the
one
of
the
senior
architects
at
ebay
that
when
you
go
to
apply
for
ebay,
you
could
say:
oh
yeah,
I've
been
working
with
this
person
on
this
open
source
project.
It
gives
you
an
a
leg
up,
so
we
can
help
you.
We
can
help,
introduce
you
to
people.
F
D
D
D
F
F
F
D
E
D
E
D
Do
you
think
we
need
like
a
like
a
should
we
brainstorm
like
on
on
some
on
some
topics
around
microservices
focusing
on
you
know,
maybe
some
high
level
topics
we
should
do
like
you
know
development
of
them
deployment
of
them.
You
know
configuration
management
around
them
or
do
we
should
we
get
into
something
a
little
more
detailed
at
that
level
or
just
keep
it
high
level
to
start
with?
What
do
you
think
would
work
better.
F
D
F
For
example,
in
network
group
like
we
have
a
micro
services
community
and
there
is
a
community
of
practice,
the
cop
and
since
I
you
know
part
of
the
devops
center
of
excellence
practice
manufacturing,
so
we
have
a
couple
of
conversations
with
them
and
we
do
interact
with
them.
So
maybe
you
know
I
can
use
my
influence
in
getting
c
view
or
tracy
for
let's
say
a
30
35
minutes
or
a
star
into
the
micro
services
community
catch
up
something.
D
E
A
A
A
D
D
D
A
D
For
these
goals
here
these
are
going
to
have
to
move
into
weekly
type
of
meetings.
Yeah,
that's
something
we're
we're
going
to
run
out
of
time.
If
we
don't
have
that,
even
if
they're
just
quick,
I
know
like
the
the
tecton
c
hub
and
catalog
they're
they're,
basically
gotten
to
the
point
where
it's
pretty
much
wrapped
up,
so
their
weekly
meetings
are
just
getting
canceled
a
couple
hours
beforehand,
because
there's
no
agenda
for
them.
So
that's
all.