►
From YouTube: .NET Foundation Project Spotlight - DNN
Description
.NET Foundation Marketing Committee member Isaac Levin spoke to Mitchel Sellers, one of the maintainers of DNN. For more detail, be sure to check out the Project Spotlight page
https://dotnetfoundation.org/projects/spotlight?project=DNN%20Platform%20(Formerly%20DotNetNuke)
A
B
B
Yeah,
the
the
best
way
to
think
about
it
is,
you
know:
dominant
nuke
is
a
cms
platform
built
on.net
that
allows
developers
to
rapidly
build
applications
that
need
some
content
management
functionality.
That's
also
been
formally,
you
know,
marketed
as
an
application
development
framework
right
with
users,
roles,
security,
page
management,
url,
redirects,
those
kinds
of
things,
it's
a
tool.
B
A
B
So
the
biggest
differentiator
with
got
is
that
we
are
the
largest
open,
source.net
cms
that
we're
aware
of
that
is
out
there
we've.
The
project
has
been
around
since
it
was
originally
high
by
spy
portal
way
back
in
2002.
I
believe
so.
We've
seen
a
lot
of
growth.
We
have
a
very
passionate
development
community,
so
we
have
a
lot
of
maintenance,
we're
doing
regular
releases
and
we're
moving
that
project
forward.
There
are
other
platforms
out
there.
A
B
Extension
points
for
all,
almost
all
of
the
various
pieces
of
functionalities,
so
that,
if
you
don't
like
the
way
that
authentication
works,
you
can
swap
it
out
with
something
else.
You
don't
like
the
way
that
you
know
other
features
work.
We
can.
You
know
work
with
that
and
we're
continually
evolving
to
bring
the
project
further
and
further
forward
with
technology,
and
it's
really
that
that
growth
and
ability
that
makes
us
a
very
powerful
tool
set.
A
For
developers,
awesome
thanks
thanks
for
that,
I
think
you
know
one
of
the
things
that
you
called
out.
That,
I
think
is
very
important.
Is
you
mentioned
the
largest
net
open
source,
sorry
opensource.net,
cms,
right
so
obviously
being
in
the
open
I'd.
Imagine
that
there
are
tons
of
contributors
to
this
project
right.
So
do
you
want
to
talk
a
little
bit
about
you
know
the
project,
maintainer
team
and
then
talk
about
community
contribution.
B
Yes,
so
we
are,
you
know,
as
you
mentioned,
we
have
a
very
broad
base.
We
have
a
really
broad
base
of
individuals
that
are
active
using
the
platform
and
that
you
start
to
see
a
little
bit
of
a
funnel
from
those
that
are
actively
using
it
to
those
that
are
contributing
issues
to
those
they're
developing,
and
then
we
have
our
core
group
of
maintainers
we've
organized
ourselves
into
a
group
of
four
lead,
maintainers
or
or
team
leads.
B
If
you
will,
I
am
the
team
lead
over
the
over
the
technology
side,
so
I'm
in
charge
of
working
with
things
for
our
release
pipelines.
Our
security
is
also
overseen
by
myself
and
some
of
the
higher
level
stuff
there
with
getting
things
out
the
door
making
sure
our
new
packages
are
published,
making
sure
that
all
of
that's
done.
We
also
have
a
strategy
lead
which
is
helping
us
kind
of
form.
Some
of
our
future
strategy.
B
We
have
a
developer
lead,
which
is
focused
on
developer
experience,
improving
getting
started
for
new
developers,
getting
started
for
those
that
are
new
contributors,
and
then
we
have
an
awareness
lead.
That's
really
there
to
help
us
better
project
ourselves
as
a
project
on
what
we
can
do,
how
we
can
get
help
for
people.
You
know
managing
website
blogs
those
kinds
of
things
to
really
help.
Some
of
that
outreach.
B
A
Side
awesome
so
definitely
sounds
like
a
lot
to
bite
off
is
one
of
the
leads
that
you
said
so
one
of
the
things
that
I
love
talking
about
when
I,
when
I
talk
about
open
source
communities,
is
just
how
you
get
started
right
so
say:
I'm
a
developer
and
I've
been
using
dnn
for
a
little
bit,
but
I
feel
like
there's
one
area
that
I
can
definitely
give
back.
You
know
whether
that
be
you
know,
building
documentation
or
testing
or
developing.
So
how
would
I
get
started
actually
being
a
contributor.
B
So
our
contributing
process
is
pretty
easy.
We
remember
the.net
foundation,
so
any
contribution.
One
of
the
things
that
throws
people
for
a
loop
is,
we
do
have
the
cla
license
bot
when
you
go
and
actually
submit
your
thing,
so
you
don't
want
to
forget
about
that,
but
really
we
keep
our
process
simple,
where
we'd
like
to
see
an
issue
documented
with
what
is
going
to
be
contributed
from
a
developer.
B
So
if
it's
a
programming,
change
a
database
change,
something
like
that,
an
issue
being
created
in
the
main
repository
so
that
we
know
what's
coming
in,
and
it's
also
really
nice
if
you're
planning
to
actually
resolve
the
issue.
To
make
a
note
in
that
initial
submission:
hey,
I'm
gonna
fix
this.
If
you're
new,
I
want
to
get
started,
we
also
have
a
number
of
issues
that
exist
already
that
have
been
tagged
by
complexity,
so
future
minor
future
major
future
revision
to
kind
of
tag.
B
B
A
For
those
contributions,
that's
awesome,
so
one
of
the
things
is
somebody
who
likes
to
contribute
to
open
source
projects
in
the
dynamic
ecosystem
is
having
a
well.
I
definitely
don't
want
to
be
somebody
that
has
to
scrounge
through
github
issues,
to
try
to
find
something
that
I
might
be
interested
in
sounds
to
me
like
a
very
organized
process,
for
you
know
you
said
different
levels
of
severity
and
things
like
that.
So
that's
great
one
of
the
things
that's
also
interesting
to
me
is
how
you
got
started
as
a
part
of
dna
right.
B
Yeah
I
started
with
dnn
years
ago
12
13
years
ago,
really
and
exactly
I
actually
was
forced
into
using
it
for
a
job
when
I
was
working
at
wells,
fargo
they're,
like
hey,
you're,
in
charge
of
maintaining
this
thing.
I
know
this
is
kind
of
cool.
This
is
in
the
early
2x
3x
days.
You
know
we're
currently
on
nine,
it's
gonna
be
9.8
and
you
know
I
got
started
and
started
to
use
it.
Then
I
was
working
with
you
know:
a
boss,
that's
like
hey!
B
You
have
to
use
evernote
at
conferences
and
technology
events.
Sure
you
guys
are
paying
that
led
to
oh
there's,
a
diamond
nuke
event,
which
was
back
in
the
day
was
paired
with
dev
connections.
I
had
done
some
kind
of
cool
stuff
with
work,
so
I
submitted
a
session
topic.
So
then
I
started
talking
about
doing
things
with
dnn
and
I
started
using
some
projects
that
were
ancillary
that
had
kind
of
fallen
off
with
support
and
like
hey
I'll
step
in
and
get
help,
so
I
started
maintaining
the
documents
module.
B
B
Sometimes
I
have
way
too
much
time
to
dedicate
apparently,
but
it's
it's
for
good
and
we've
done
amazing
things
as
an
open
source
project,
especially
where
we
had
a
big
lack
right.
We
had
a
time
place
where
people
couldn't
trust
us
and
that's
been
our
hardest
bit.
Really.
It's
not
even
getting
started,
it
wasn't
even
me
getting
started
in
the
beginning.
It's
now
that
we
are
truly
open
source.
Again
we
have
the
support
of
the
foundation.
It's
getting
people
to
understand.
We
will
accept
your
contributions.
A
A
That
doesn't
mean
that
you're
going
to
accept
every
pr
that
gets
submitted,
but
but
it
does
mean
that
if
you
put
thoughts
in
how
you're
going
to
contribute
and
what
you're
going
to
contribute,
the
team
is
definitely
going
to
help
you
every
step
of
the
way,
which
I
think
is
amazing,
and
I
I
think
that's
just
a
great
opportunity
for
people
that
want
to
come
and
provide
new
insights
or
new
experiences
to
dnn,
like
that.
It's
welcome
so
awesome.
A
B
So
we've
recently
employed
a
different
strategy,
so
we
we
took
back
over
from
a
community
perspective
shortly
after
the
9.2.2
release
and
we're.
Currently,
we
will
be
releasing
9.8.0
release
candidate
later
on
this
week
and
we
took
over
after
what
everyone
kind
of
refers
to
as
oh,
that
release
that
we
all
don't
want
to
deal
with
again
where
breaking
changes
were
released
in
a
non-major
version.
B
But
we
have
a
certain
milestone
that
we
wanted
to
hit
on
the
9.x
series
before
we
get
to
10.,
because
what
we
understand
is
that
it's
easier
for
people
to
upgrade
with
minor
releases
and
revision
releases
where
we're
not
introducing
breaking
changes
or
maybe
bumping
up
dependency
versions,
we're
adding
new
functionality
but
we're
adding
new
functionality
in
a
non-breaking
manner.
So
that's
our
current
emphasis
is
to
make
sure
that
we
get
the
project
as
far
as
we
can
and
we
have
a
secure.
We
have
a
security
and
stability
milestone.
B
That's
what's
actually
holding
us
back
from
going
to
a
10x
release.
We
have
a
goal
of
an
optional
security
compliance
thing
that
we
want
with
nine
and
we're
actually
gonna
be
able
to
achieve
that
with
9.8.0
with
the
release
candidate.
When
it
comes
out
once
we
get
there
right,
then
we
can
go
to
10
and
what
we've
been
trying
to
do
with
that
is.
We
are
evolving
and
we
will
be
having
breaking
changes,
but
we
also
understand
that
our
users
have
been
around
for
a
long
time
right.
B
We
have
people
that
have
upgraded
from
3x
from
forex
we're
talking
about
websites
that
have
been
in
existence
for
five
ten
plus
years
right.
We
have
people
that
have
spent
literally
millions
of
dollars
on
custom
development
on
single
applications
that
are
built
that
anew.
So
we
want
to
be
able
to
give
people
the
most
secure
platform
possible
using
the
minor
and
revision
releases,
but
then
we
want
to
be
able
to
be
as
nimble
as
we
can
to
move
forward
into
new
technology
and
that's
what
we've
been
using
as
our
current
dividing
lines.
B
B
B
We
are
doing
a
release
candidate,
the
week
of
october
5th.
Traditionally,
our
release
candidates
are
out
there
for
two
weeks,
assuming
that
no
issues
are
found
before
they
become
a
real
release:
full
disclosure.
We
anticipate
that
this
religious
candidate
will
take
longer.
We
are
replacing
in
this
release
the
file
manager,
which
is
one
of
the
biggest
underpinning
components,
that's
utilized
in
the
platform
and
currently
has
a
dependency
on
a
2013
version
of
teller,
which
we
all
know
is
not
a
good
thing.
A
Awesome.
That's
absolutely
awesome,
I'm
glad
to
hear
that
you
know
everybody's
done
it
right
where
you
have
a
dependency
that
you
keep
looking
at,
you
keep
looking
at,
you
keep
looking
at
and
you're
like.
Oh,
this
is
going
to
be
a
challenge
right.
It's
it's
great
to
hear
that
you
know
you
had
a
similar
experience
and
you
were
able
to
overcome
it
so
kudos
to
that.
A
So
as
we
wrap
up
one
of
the
things
I
want
people
to
be
very
clear
of
is
that
you
know
dnn
is
a
part
of
the.net
foundation
and
the
dotnet
foundation
has
you
know
multiple
different
avenues
for
projects
to
take
advantage
of
right.
So
you
know
one
of
the
things
and
I
don't
know
if
you
were
a
part
of
the
team
that
came
in
to
bring
dna
into
the
dotnet
foundation.
But
do
you
maybe
want
to
talk
about?
You
know
one
of
the
decision
making
points
that
led
you
to
join
the
donna
foundation.
B
Yeah,
so
I
was
involved
shortly
there
after
the
project
actually
joined
in.
I
have
been
a
candidate
for
the
batman
foundation
board
as
well,
so
I'm
really
keen
in
what
the
dot-net
foundation
can
do
for
the
projects,
but
as
a
project
leader
really,
we
would
not
be
where
we
are
today,
if
it
weren't
for
the
deafness
foundation,
the
support
that
we
get
from
a
project
perspective,
we
azure
devops.
B
B
All
of
that
is
being
executed
on
resources
that
were
provided
to
us
by
the.net
foundation,
as
well,
as
you
know,
continue
pushing
for
us
to
improve
our
processes
to
be
more
secure
and
those
kinds
of
things.
We
have
a
lot
of
great
support
from
the
foundation
and
also
it
gives
us
a
means
to
be
able
to
clean
up
some
of
the
things
that
we
had
before.
B
By
having
the
resources
provided
by
the
foundation,
we
have
a
level
of
assistance,
that's
beyond
our
current
leadership
that
allows
us
to
be
able
to
continue
this
project
forward.
Our
end
users
right
are
able
to
be
convinced
right
that
that
project
will
be
able
to
continue,
and
it's
even
some
of
the
little
things
right.
The
cla
pods
that
make
sure
that
we
get
license
agreements
from
everybody
that
contributes
to
our
repository
huge
for
us,
and
it's
also
huge
for
the
end
users
from
an
independent
perspective
and.
A
A
Well,
I'm
glad
to
hear
that
I'm
glad
to
hear
you
know.
You
say
that
the
donut
foundation
has
been
extremely
beneficial
for
you
as
a
project
maintainer,
and
it
just
to
call
out
that
the
foundation
would
not
exist
without
amazing
projects
like
dnn
as
well
as
major
contributors
to
those
projects
like
you.
So
thank
you
for
that.
So
we're
going
to
wrap
up
and
I
want
to
just
say
thank
you
to
mitchell
for
coming
on
and
chatting
with
us
and
you
know
mitchell.
Do
you
have
anything
parting
to
say.
B
We
nothing
more
than
you
know
whatever
project
it
is
that
you
believe
in
right,
contribute,
contribute,
contribute
but
contribute
contributing
to
those
projects
can
be
anything,
it
can
be
submitting
issues,
it
can
be
testing
or
release,
it
can
be
contributing
code,
it
can
be
supporting
developers
and
github
sponsors
right.
We,
we
have
a
small
group
of
core
maintainers
that
are
ridiculously
passionate
for
some
unknown
reason
for
our
project,
sometimes,
but
anything
to
give
back
to
those
that
are
giving
into
these
projects.
So
much
that's
what
keeps
us
going
as
maintainers.