►
From YouTube: .NET Foundation Project Spotlight - Oqtane
Description
.NET Foundation Marketing Committee member Isaac Levin spoke to Shaun Walker, creator of Oqtane. For more detail, be sure to check out the Project Spotlight page
https://dotnetfoundation.org/projects/spotlight?project=Oqtane
A
B
Sure
yeah,
I'm
sean
walker,
I'm
a
technical
director
with
cognizant
soft
vision-
and
I
guess
my
claim
to
fame
is
that
I
was
the
original
creator
of
an
open
source
project.
Called.Net
nuke
now
been
rebranded
as
dnn,
but
I've
been
a
long-time
contributor
to
the
open
source
ecosystem
within.net
and
I've
also
been
involved
with
the.net
foundation
for
many
years
since.
Actually,
since
2014.
A
B
B
A
Oh,
that's
awesome,
so,
let's
take
a
step
back
and
kind
of
talk
about
like
modular
frameworks
right
and
why
those
are
valuable
for
for
developers,
especially
net
developers.
Right
when
you
build
out
applications,
you
have
tons
of
different
components
right,
you
know.
If
you
are
an
e-commerce,
you
might
have
a
shopping
cart,
you
might
have
a
login
mechanism,
or
what
have
you-
and
it
sounds
to
me
like
octane-
allows
users
to
kind
of
build
with
an
existing
template
or
a
way
that
makes
it
easier
to
get
started.
Is
that
fair.
B
You
know
some
services
and
things
that
you
can
build
on
top
of,
whereas,
like
a
modular
framework,
is
a
bit
different
in
that
you're,
probably
not
expected
to
modify
that
framework
at
all.
It's
intended
to
be
a
product
in
its
own
right,
but
it
provides
you
with
extensibility
points
like
interfaces
that
you
can
connect
to
with
your
custom
code
so
that
you
can
add
additional
functionality.
B
A
That's
great,
and
so
I
want
to
talk
about
the
way,
the
way
that
you
build
in
the
technology.
That's
using
because
blazer
is
awesome.
Can
you
kind
of
speak
to
a
little
bit
about
why
you
decided
to
build
octane
and
one
of
the
main
reasons
why
you
felt
the
the
obligation
to
say
of
okay?
Let's
build
out
a
modular
framework,
you
know
with
the
newest
technology
that
that's
came
out
recently.
B
It's
it's
interesting
because
I
built
many
kind
of
frameworks
over
time.
Dot.
Nanook
is
probably
the
most
well
known,
but
it's
funny
because
why?
Why
do
I
like
to
build
frameworks?
Probably
because
I'm
lazy
in
the
sense
that
I
don't
like
writing
the
same
code
over
and
over
and
over
again
right
there?
There
are
some
fundamentals
that
are
part
of
every
application
that
you
really
shouldn't,
be
writing
from
scratch
every
time
and
and
that's
where
frameworks
come
in
right,
where
they
provide
some
sort
of
commodity
type
functionality.
B
That
is,
you
know
that
typically
exists
in
most
applications
and
you
get
that
for
free
out
of
the
box,
and
then
you
can
focus
on
building
your
your
specific
business
logic
that
you
know
that
is
trying
to
solve
your
business
problem
yeah.
So
I
think
that
that's
so
that
was,
I
guess,
the
main
motivation
I
get
more
specifically
for
octane.
B
B
That
are,
you,
know,
innovative
and
you
know
really
pushing
the
envelope
and
that's
where
I
really
was
attracted
to
blazer,
because
it
has
a
really
rich
component
model
behind
it.
Much
like
some
of
the
the
front-end
javascript
frameworks
too,
but
I'm
a
c-sharp
developer,
and
so
I
feel
a
lot
more
comfortable
in
that
environment
than
I
do
with
javascript.
So
seemed
like
the
perfect
fit.
A
A
So
you
came
up
with
an
idea
like
I'll
build
something
that's
actually
involved
instead
of
building
a
ton
of
hello
world
type
of
applications
right,
so
you
know
I
would
love
to
know,
obviously,
as
you're
going
through
the
process
like
blazer
just
launched
at
dotnet.conf,
like
that
was
what
a
couple
of
weeks
ago
in
the
middle
of
november
for
people
in
the
future.
I
it's
and
it's
fairly
new,
so
I'm
actually
been
following
the
previews
for
a
long
time
right
so
yeah.
Do
you
want
to
talk
a
little
bit
about?
A
B
A
B
Yeah,
that's
definitely
a
bit
of
a
challenge
yeah.
So
when
I
started
getting
involved
with
blazer
and
started,
you
know
downloaded
the
the
preview
bits
it
was.
This
was
in
october
november
of
2018,
and
so
at
this
point
in
time
you
know
blazer
hadn't
even
come
out
of
the
experimental
phase
from
microsoft.
The
asp.net
team
was
working
on
it
internally,
but
it
still
had
an
experimental
label
on
it,
and
so
I
had
well.
Obviously
I
had
a
really
good
knowledge
of
what
I
had
like
that.
B
The
concepts
that
I
had
used
to
build
dnn-
and
I
thought
you
know
blazer-
has
a
lot
of
dynamic
capabilities
to
it
and
it's
based
on
components.
So
can
I
use
those
concepts
to
build
something
in
blazer
natively
from
the
ground
up
that
that
acted
similarly
to
what
dnn
was
capable
of?
And
so
yes,
I
was
able
to
do
that,
but
along
the
way
you
know,
microsoft
was
releasing
new
preview
bits
every
month,
and
so
often
my
proof
of
concept
application
would
get
broken,
and
then
I
have
to
figure
out
why
it
was
broken.
B
I
didn't
actually
release
the
1.0
version
until
microsoft
released
full
support
for
webassembly,
and
that
was
in
may
of
2020.
So
only
six
or
seven
months
ago
and
then
worked
through
a
number
of
you
know
subsequent
versions.
You
know
just
you
know,
stabilization
type
releases
until
I
decided
that
I
should
probably
move
forward
with
the
microsoft
release
train
and
so
with
net
5
new.
B
You
know
a
new
version
of
blazer
came
out
and
I
wanted
octane
to
run
on
that
immediately,
and
so
the
community
did
a
bunch
of
work
to
make
that
happen,
and
we
released
octane
2.0
on
november
11th,
so
to
coincide
with
uh.netconf
and
in.net.
Five
and
the
reception's
been
really
positive.
So
quite
happy
about
that
decision.
A
B
Go
ahead.
Most
of
the
credit
probably
belongs
to
microsoft.
For
that,
because
the
going
from
a.net
core
3.1
application,
to.net
5,
was
actually
really
straightforward.
I
mean
microsoft
really
took
care
to
not
have
a
lot
of
breaking
changes
between
those,
so
the
transition
or
the
the
migration
path
to
the
dot
at
five
was
actually
really
straightforward.
A
That's
great
it's
great
to
hear
because
I,
in
the
past,
obviously
migrating
from
different
versions
of
frameworks
is
always
a
challenge
right,
so
yeah,
it's
good
to
hear
that
going
from
3.1
to
5
is
at
least
for
octane.
Didn't
you
know
essentially
make
you
have
to
rewrite
from
scratch,
or
you
know
reconfigure
your
you
know
your
hosting
models
and
anything
like
that.
Yeah.
B
The
other
cool
thing
was
that
if
you
had
built
extensions
for
octane
based
on
net
core
3.1
after
octane
was
upgraded
to
dot
net
5.
Those
extensions
that
were
compiled,
on.net
core
31,
still
worked.
There
was
without
any
compatibility
issues,
so
that's
it's
also
pretty
cool
right,
so
that
just
means
that
the
underlying
bits
were
fully
compatible,
and
I
was
quite
impressed
by
that.
A
It's
great
to
hear
us,
so
I'm
curious,
so
obviously,
based
on
what
you're
you
know,
you're
talking
about
with
octane,
it
seems
like
there's
been
a
ton
of
work
and
ton
of
help
from
the
community
and
I'd.
Imagine
because
people
see.
Oh.
This
is
a
very
interesting
concept,
right,
modular
frameworks
built
on
the
newest
bits
that
exist
right.
You
know
what
was
the
initial
community.
I
guess
you
could
say
reaction
or
in
like
was
there
a
ton
of
interest?
Was
there
a
oh
okay?
This
is
kind
of
cool,
but
I'm
not
not.
B
Yeah
it's
interesting
because,
because
the
concepts
that
were
used
in
octane
were
very
similar
to
what
were
used
in
dnn,
I
initially
thought
that
the
community
members
who
had
participated
in
dnn
would
be
you
know
the
first
adopters
they'd
be
the
ones
who
would
see
the
similarities
and
and
if
they
wanted
to
experiment
with
newer
technology
that
they
would
give
it
a
try.
But
that's
not
what
ended
up
happening.
B
It
was
actually
a
completely
new
community
that
formed
around
octane
tended
to
be,
I
guess,
younger
developers,
developers
that
were
very
interested
in
blazer
technology
developers.
That
much
like
me
didn't
really
like
javascript
that
much
so
they
like
the
the
whole
promise
of
writing
c
c-sharp
on
the
front
end
and
then
only
more
recently,
I've
seen
more
of
an
influx
of
developers
from
the
dnn
community
taking
a
look
at
at
octane.
B
A
A
A
A
A
B
Yeah,
so
I'm
not
even
really
thinking
about
net
six
at
all.
At
this
point
yeah,
I
I
mean
I'm
excited
about
net
six,
because
microsoft
recently
published
a
few
documents
that
are
sort
of
previews
of
the
the
themes
they
would
like
to
tackle
in
six,
and
one
of
them
is
cultivating
and
growing
the
open
source
ecosystem
around.net.
B
So
that's
cool
because
that
that's
great
for
octane
as
well,
but
in
terms
of
more
of
the
the
technical
road
map
for
octane,
like
you
said,
so
it
had
a
2.0
release
that
coincided
with
dot
net
5.,
but
there's
like
with
open
source
projects,
there's
almost
no
limit
to
the
number
of
features
that
can
be
added,
and
sometimes
sometimes
the
feedback
from
the
community
can
be
like
overwhelming,
and
it's
pretty
clear
where
you
should
be
applying
your
efforts
and
sometimes
it's
random
right.
It's
all
over
the
place.
B
You
know,
and
people
are
requesting
things
that
you
never
even
anticipated
with
with
octane.
There
have
been,
I
guess,
category,
a
few
categories
where
people
have
been
making
the
most
requests
so
far
and
and
one
was
in
the
early
proof
of
concepts.
I
decided
that
I
would
initially
only
support
sql
server
and
the
different
sort
of
derivatives
of
it.
B
You
know
how:
how
easy
is
it
truly
for
developers
to
create
custom
solutions
based
on
a
framework,
and
I
know
that
this
is
a
focus
for
microsoft
as
well,
but
it
has
to
be
a
focus
in
octane.
You
know,
unless
it's
like
super
easy
for
developers
to
get
started
and
be
productive.
You
know
the
framework
is
really
not
going
to
be
that
successful
and
so
that
that's
got
to
be
an
area
of
focus
as
well.
A
Yeah,
I
I
totally
agree.
Yes,
you
kind
of
hinted
at
a
little
bit
that
you've
gotten
a
ton
of
pull
requests
right
so
for
developers
that
are
interested
in
either
trying
out
octane
for
their
own
solutions
or,
if
they
feel
like
they
want
to
contribute
to
octane.
What
is
the
best
way
for
them
to
start
that.
B
Clearly,
like
obviously
on
github,
there
is
the
main
repo
and
we
have
a
dev
branch
and
a
master
branch
right
now.
The
master
is,
you
know
just
for
bug,
fixes
in
case
any
major
issues
come
up
and
we
need
to
quickly
be
able
to
issue
like
a
maintenance
type
of
release,
but
most
of
the
developments
going
on
in
dev
right
now.
It's
it's
usually
a
good
idea.
B
A
good
example
is,
you
know
we
try
to
stay
away
from
too
many
third-party
dependencies
on
other
projects,
just
just
to
keep
things
simple
and,
and
so
that
that
is
to
give
you
know,
developers
who
would
like
to
contribute
to
octane.
You
know
some
some
guidelines
right,
don't
try
to
pull
in
every
dependency
you
can
think
of
into
the
project,
because
that
probably
won't
be
accepted.
So
it's
good
to
set
those
expectations
up
front
so
that
people
don't
spend
a
lot
of
time
and
effort
and
then
are
disappointed.
B
The
other
thing
I
find
is
which
is
difficult
to
try
and
curb
people's
enthusiasm
right
a
lot
of
first
time,
users
of
octane
will
show
up
they'll,
you
know,
download
the
source
code,
they'll,
take
a
look
and
there'll
be
certain
things.
Maybe
that
don't
follow
their
coding
preferences
and
then
they'll
they'll
submit
pull
requests
right.
B
Those
pull
requests,
don't
fix
any
bugs,
they
don't
add
any
enhancements
they're
just
that
person's
personal
preference
on
the
way
things
should
have
been
coded,
and
I
have
a
a
difficult
time
with
those
types
of
pull
requests
because
they
take
a
lot
of
time
to
review.
Sometimes
they
don't
add
a
lot
of
value.
Sometimes
they
actually
break
things
because
they
don't
adhere
to.
You
know
backward
compatibility
principles,
and
but
this
is,
I
guess,
one
of
the
challenges
of
being
a
maintainer
of
an
open
source
project.
B
Is
you
spend
a
lot
of
time,
reviewing
things
and
actually
rejecting
them
and
saying?
No
and
and
then
you
feel
like
the
bad
guy,
because
you
know
that
people
you
know,
put
their
passion
into
it,
but
I
mean
like
any
product
right
you
have
to
you
have
to
manage
it.
You
have
to
keep
it
moving
in
the
right
direction.
A
Oh,
I
I
mean
I've
been
very
vocal
about
you
know,
people
that
you
know
like
to
open
pull
requests
to
kind
of
you
know
adhere
to
what
their
principles
are
right,
but
I
think
one
of
the
things
that's
very
interesting
as
well
is
you
mentioned
that
you
have
kind
of
a
a
a
guidance?
You
know
a
set
of
guidance
documents,
which
is
very
valuable.
I'd.
A
B
B
There
is
a
bunch
of
work
that
was
done
in
2.0
by
a
community
member
to
set
up
at
least
the
the
automated
sort
of
doc
effects
generation
of
api
documentation
based
on
the
source
code,
which
is
awesome
so
at
least
that's
published,
but
in
terms
of
more
elaborate
you
know,
articles
or
filling
out.
You
know
the
use
cases
for
using
these
apis,
that's
a
weak
area
and
yeah.
It's
it's.
It
seems
like
it's
really
difficult
to
encourage
people
to
get
involved
in
the
documentation
area.
A
Yeah,
I
think
you
know,
there's
a
running
joke
about
developers
not
like
not
liking
to
write,
documentation
or
document
their
code
or
whatever
right
like.
So
I
think
it's
not
really
a
it's
cliche,
but
it's
very
accurate.
So
I
think
if
there
are
some
folks
out
there
that
are
more
interested
in
helping
out
with
technical
writing
or
documentation,
because
you
know
maybe
they
they
don't
see
that
they
can
provide
any
value
by
adding
code
because
they
don't
have
an
idea
for
a
feature
or
an
enhancement.
B
A
B
A
I
think
one
of
the
things
as
well
that
we
should
talk
about
is
you
you
mentioned
that
you
have
worked
with
for
a
while
with
the
dot
net
foundation.
I
would
like
to
kind
of
know.
You
know
that
a
little
bit
about
what
your
role
is
on
the
dotnet
foundation
and
and
what
you
feel
like
the
dotnet
foundation
provides
to
you
as
a
developer.
As
you
know,
stu
is
a
maintainer
of
a
project
in
the
foundation.
B
Yeah,
so
my
current
role
is,
I
am
the
chair
of
the
project
committee
and
I've
been
acting
in
that
role
since
february
of
2020,
and
I
guess
sort
of
the
reason
why
the
project
committee
was
formed
is
to
help
projects
early
in
the
stages
of
when
they
make
the
application
to
become
a
member
project
and
then
help
them
once
they've
become
an
actual
project
with
any.
You
know,
advice
or
guidance
that
we
can
provide
to
them
prior
to
the
the
project
committee
being
formed.
B
Is
we
kind
of
constructed
a
a
charter
for
the
project
committee,
which
said
you
know?
This
is
how
we
should
evaluate
project
applications
when
they
come
in
pretty
simple
criteria,
but
I
mean
how
does
it
align
with
the
foundation
values
and
then
is
it
a
mature
project
in
the
sense?
Is
it
active,
you
know:
does
it
have
a
community
around
it?
Is
there
multiple
developers
who
are
contributing
to
it,
just
basic
activity,
kind
of
things
and
we're
basing
all
that
on
public
metrics
that
we
can
capture
from
github?
B
And
so
we
published
that
as
the
charter,
so
that
it's
pretty
clear
you
know
this
is
how
we're
evaluating
things
and
the
community
knows.
There's
not
sort
of
you
know
sort
of
a
hidden
agenda
or
you
know
secret
criteria,
that's
being
used
behind
the
scenes,
it's
all
pretty
transparent
and
then
every
month
we
review
the
project
applications
as
they
come
in.
We
review
them
against
the
charter
and
then
for
those
who
are
deemed
to
be.
B
You
know,
sort
of
worthy
of
being
part
of
the
the
foundation
based
on
their
maturity
and
and
the
fact
that
they
adhere
to.
You
know
the
the
eligibility
criteria.
Then
we
actually,
we
pass
those
on
to
the
board
as
a
recommendation
and
it's
ultimately
up
to
the
board
of
directors.
So
whether
or
not
projects
are
accepted,
the
project
committee
doesn't
have
any
authority
in
its
own
right
right.
B
There's
a
lot
of
individual
things
that
come
up
here
and
there
when
it
comes
to
projects,
questions
about
licensing,
questions
about
trademarks,
questions
about
you
know
how
to
use
the
infrastructure
questions
about.
You
know
the
types
of
services
that
are
offered,
but
those
are
very
like
I
wouldn't
say
that
there's
a
general
category,
those
kind
of
things
come
in
that
are
they're
pretty
random
and
different
things
will
flare
up.
B
You
know
now
and
again,
and
that's
also
where
the
project
committee
gets
involved
to
to
try
and
you
know,
help
those
projects
with
whatever
issues
they're
encountering
and
so
that
that's
mainly
where
I've
been
participating
in
in
the
foundation.
But
that's
only
been,
I
guess
in
2020
prior
to
that
I
was
a
member
of
the
advisory
council
and
that
advisory
council
would
meet
monthly
with
the
executive
director
to
discuss.
A
No,
I
I
can
contest
to
that,
I'm
a
part
of
the
marketing
committee.
So
obviously
you
know
the
advisory
council.
That's
a
lot
of
freight.
If
you're
worried
about
project
onboarding
and
membership
and
marketing,
it's
it's
a
lot.
For
you
know
a
handful
of
folks,
so
br
separating
everything
out
to
marketing
allows
the
different
groups
to
be
autonomous
and
kind
of
come
together
and
kind
of
report
back
to
the
board
about
what
you
know.
Some
of
the
initiatives
that
we're
trying
to
accomplish
in
a
way
that's
a
bit
more
managed.
Otherwise,
it's
just
okay.
B
A
Yeah
and
you
know
as
we're
closing
out-
I
just
want
to
obviously
you
know
you're
a
volunteer
for
some
of
the
work
on
the
donette
foundation.
So
thank
you
for
that.
Also,
you
have
a
project
on
as
a
part
of
the
foundation,
so
thank
you
for
being
a
part
of
it
and
for
folks
that
they
want
to
know
more
about
octane
like
it's
all
available
on
github.
A
All
the
information
about
octane
that
you
need
will
be
on
this
project
spotlight
page,
and
I
think
you
know
I
want
people
to
go
out
and
try
octane
see
if
there's
you
know
see
if
it
can
bring
value
to
your
development
work,
and
if
you
have,
you
know
the
urge
to
contribute.
I
imagine
that
sean
will
appreciate
that
very
much.
B
Absolutely
yeah,
I
was
actually
pretty
excited
with.net
comp.
I
had
the
opportunity
to
to
actually
present
at
it
for
the
first
time
and
I
did
a
session
on
building
dynamic
applications
with
blazer
and,
of
course,
used
octane
as
the
example
of
that
and
yeah.
I
think
that
I
I
kind
of
ran
out
of
time
in
my
session,
but
I
got
the
bulk
of
the
the
content
covered.
So
I
was
pretty
happy
about
that.