►
From YouTube: Updates on the sp-dev-docs issue list support model
Description
This PnP community demo is taken from the bi-weekly SharePoint Developer Community - General Development Special Interest Group (SIG) call recorded on January 23, 2020.
In this 12-minute video, Andrew Connell – Microsoft MVP explains changes recently made to the SharePoint / sp-dev-docs issues list on GitHub. Updates to guidance (process, policy) and submission template as well as a number of older issues were closed. The changes are focused on getting the right questions in the right place for quicker resolution. Note: Closed issues may be reopened, if still relevant.
Presenter: Andrew Connell (Voitanos) | @andrewconnell
Supporting materials:
• SharePoint / sp-dev-docs issues – wiki page and repo on GitHub - https://github.com/SharePoint/sp-dev-docs/wiki/Issue-List#january-2020—closed-all-old–un-tracked-issues.
All SharePoint PnP Developer Community demos: https://www.youtube.com/playlist?list=PLR9nK3mnD-OWSbg0o9a7mx_E7s2u7h_o2
Learn more about the SharePoint developer community at: http://aka.ms/sppnp.
A
B
Gonna
drop
a
link,
real
quick
into
the
chat
or
refer
to
that
in
just
a
minute.
So,
as
best
I
said
at
the
beginning
of
the
call,
we
made
a
bunch
of
changes
to
the
issue
list,
just
some
process,
some
policy
and
some
actual
changes
that
we
made
it
looks
like
I
made
all
these
changes
and
I
just
want
to
make
sure
it's
very
clear
to
everybody.
B
This
is
not
some
unilateral
thing
that
I
did
I'm,
simply
the
actor
or
the
one
that
whose
user
account
got
tagged
with
everything,
so
it
looks
like
I
was
the
kind
of
going
through
it
like
crazy
in
the
issue
list.
These
are
all
these
are
all
things
that
I'm
going
to
share
with
you.
Well,
it
looks
like
I
did
them.
They
were
all
done
with
a
lot
of
conversation
with
Microsoft.
There
was
a
lot
of
debate
with
this.
It
was
not
a.
It
was
not
something
that
was
done
and
a
very
off-the-cuff.
B
We
did
this
for
many
many.
We
talked
about
this
for
many
many
many
weeks
internally
before
we
did
this
so,
and
everything
was
approved
by
Microsoft
definitely
open
to
feedback.
So
let
me
kind
of
explain
what
we
did
here,
there's
a
handful
of
things
that
we
ended
up
doing
so
what
you
see
here
I've
got
the
issue
list
here.
First
of
all,
if
you
jump
over
to
the
wiki,
there
are
now
a
few
new
pages
in
the
wiki
you'll
see
them
in
the
section
in
the
navigation
off
on
the
left-hand
side.
B
So,
first
of
all
the
issue
list
and
then
there's
a
handful
of
other
things
that
we
have
listed
over
here.
If
you
take
a
look
at
the
issue
list
page
this
kind
of
explains
what
the
general
like
policy
and
is
with
the
issue
list.
As
far
as
Microsoft
looks
at
it
specifically
like
what
does
belong
in
the
issue
list,
what
does
not
belong
in
the
issue
list?
B
The
approach
to
closed
issues,
the
approach
to
locked
issues,
I'll
talk
about
those
in
just
a
minute
as
well
as
some
issue
templates
now
I'm
not
going
to
walk
through
all
this
stuff
I'm
going
to
kind
of.
Let
you
look
at
this
that
you're
on
your
own
at
your
own
time,
and
we
will
continue
to
update
this
as
needed.
The
special
oxygen
section
I
have
at
the
very
bottom
is
the
link
that
I
posted
to
the
chat
just
a
minute
ago,
and
this
explains
all
the
stuff
that
happens
yesterday.
B
So
specifically,
what
we
did
and
I'm
gonna
jump.
I'll
come
back
to
this
in
just
a
minute,
but
one
of
the
big
things
are
big
additions
that
we
have
to
the
issue
list
is
that
now,
when
you
go
over
to
the
issues
and
you
go
to
create
a
brand
new
issue,
you
will
be
presented
with
a
first,
the
first
step
here
of
what
kind
of
an
issue
you're
going
to
create.
Is
it
a
bug
or
an
error
report?
Is
it
a
generic
issue?
B
That's
kinda
like
what
we
had
before
this
generic
question
or
generic
issue
is
gonna,
be
the
same
thing
if
you
click
on
this
blank
issue,
a
feature
request
just
as
a
heads
up
as
we
explained
in
the
wiki
feature,
requests
don't
belong
in
the
issue
list.
We
want
those
going
to
user
voice
because
that's
where
Microsoft
engineering
triage
is
new
feature
requests
to
add
them
to
the
to
their
backlog.
So
as
it
explains
in
the
issue,
if
you
go
to
create
it,
it
will
fly
out.
B
I'll,
explain
it
going
to
preview
here
that
it
will
say
that
if
you,
if
you
do,
submit
this
as
a
feature
request,
it
will
automatically
labeled
as
a
feature
request,
and
it
will
be
automatically
closed,
which
will
point
you
to
user
voice,
feel
free
to
use
this.
If
user
voice
isn't
gonna,
give
you
the
formatting
and
stuff
that
you
want,
and
you
want
to
reference
the
issue
that
was
created,
but
we
just
trying
to
guide
people
in
that
direction,
that
you
will
be
automatically
tagged
and
closed
with
the
user
voice
requests.
B
The
other
thing,
too,
is
that
that
you
see
down
here
is
that
there
are.
There
are
things
that
we
don't
that
this
issue
list
is
not
for
so
it
is
primarily
for
developer
issues
or
develop
or
development
SharePoint
development
issues.
If
this
is
an
issue
that
is
related
to
end
user
administrator,
the
end
user
experience
admin
stuff,
those
things
belong
in
the
tech
community
site.
If
it
is
a
feature
request
again,
it
goes
as
user
voice
as
well.
So
all
of
that
stuff
is
going
to
end
up.
B
B
This
thing
please
delete
this
guidance
that
you
see
here
in
this
line,
delete
this
one
line
before
you
submit
it
and
then,
at
the
very
end
we
even
put
like
you
know,
developer
environment,
stuff
that
we're
looking
for
all
this
stuff
helps
us
quite
a
bit
in
helping
you
the
more
information
you
can
provide
the
better.
It
is
now
some
of
the
big
things
that
we
ended
up
doing
some
big
changes
that
we
ended
up
doing
to
the
issue
list.
B
First,
there
was
a
sweeping
action
that
affected
and
look
at
my
notes
awfully
250
of
our
760
to
open
issues.
So
what
we
ended
up
doing
is
there
was
a
time
last
year,
really
break
falls
down
into
three
different
categories.
First
of
all,
there
was
a
time
last
year
when
the
labeling
capability
that
we
have
in
our
issue
list
wasn't
working,
and
so
we
had
roughly
80
some
issues
that
had
no
labels
assigned
to
them.
B
Instead
of
walking
through
each
one
of
those
issues
that
to
figure
out
what
this
was,
what
category
can
we
apply
it
to?
In
addition,
those
80
issues:
they
had
no
activity
on
them
for
way
over
six
months,
so
we
took
the
approach
of
instead
of
taking
the
time
to
detail
each
individual
issue
and
trying
to
triage
each
of
those
80
individual
issues
that
a
lot
of
them
very
well
may
no
longer
be
a
problem
or
an
issue
or
whatever
we're
gonna
go
ahead
and
close
them.
B
But
when
we
closed
everything
that
everything
got
a
comment
assigned
to
it
with
a
link
to
one
of
their
new
sections
in
the
wiki,
that
explains
what
we
did,
why
we
did
it
and
how
you
can
remediate
that
process.
So
if
an
issue
of
yours
was
automatically
closed
or
if
it
was
automatically
locked,
which
I'll
explain
in
a
second,
we
explained
how
you
can
remediate
that
it's
not
like
the
last
straw
that
you
see
when
that
happens.
B
So
that
was
one
change
we
did
another
change
that
we
did
is
that
we
went
back
and
we
looked
at
all
issues
that
had
that
were
open,
that
had
no
activity
on
them
in
over
seven
months,
and
that
means
there
been
no.
There
were
no
updates
to
it.
There
were
no
questions
that
were
asked.
Nobody
did
anything
with
these
issues.
B
They
were
effectively
old
things
that
nobody
was
doing
it
very
well
could
have
been
that
some
of
these
were
are
still
relevant
today,
that
they're
still
bugs
that
are
out
there
and
they
haven't
been
addressed
totally
get
it.
We
have
when
issues
are
recognized
as
a
bug
by
Microsoft
they're
put
inside
of
a
diff
there
added
to
an
internal
backlog
like
a
DevOps
board
for
at
Microsoft.
B
Here's
how
you
can
remediate
that
and
how
you
can
do
it
and
there's
already
people
that
have
been
doing
that
stuff.
We've
we've
seen
a
couple
I've
seen
a
couple
issues
get
submitted
by
people
overnight.
I
go
to
these
closed
issues,
you'll
see
where
someone
said
this
thing
that
you
know:
hey
here's,
how
I
want
to
go
I
want
to
get
that
issue
open
back
up,
so
they
referenced
the
issue
and
then
we
went
back
and
we've
we've
already
gone
back
to
this
issue
and
we've
already
unlocked
it
and
opened
it
back
up.
B
B
Everybody
believes
this,
but
generally
speaking
on
an
open
repo
like
what
we
have
here
when
an
issue
is
closed,
people
generally
see
that
as
resolved
or
conversation
over-
and
you
may
not
agree
with
that,
but
that's
the
vast
majority
of
how
people
see
stuff
when
we
had
a
closed
issue
and
someone
would
go
in
after
six
months
and
say
I'm
having
this
problem,
can
someone
help
me?
Nobody
was
seeing
that
and
that's
leaving
a
really
bad
experience
for
that
one
user,
or
at
least
nobody
is
seeing
it
that
was
not
contribute.
B
That
was
not
already
involved
with
that
issue.
So
if
I
was
involved
in
the
conversation
in
the
original
issue,
then
yeah
I'm
gonna
get
an
email
update,
but
if
I
wasn't
then
I'm
never
gonna
see
what
this
person
asked
and
they're
gonna
think
that
nobody
cares.
So
what
we
did
is
we
followed
a
process
that
a
lot
of
other
repositories
do
and
we
went
ahead
and
lock
those
any
issues
that
were
closed
and
they've
had
no
activity
in
seven
days.
B
So,
if
it
is,
she
gets
closed
and
then
has
no
activity
in
seven
days
it
gets
locked,
and
that
means
that
nobody
can
add
any
more
comments
to
it.
Women
that
happens.
We
also
add
a
comment
saying
here's:
why
we
locked
it?
If
you
don't,
if
you
don't
agree
that
this
should
have
been
locked,
then
here's
how
you
can
go
back
and
remediated,
and
you
see
here
I'm
even
on
the
screenshot
I,
have
a
link
here
going
to
our
wiki.
That
explains
here's
how
you
do
that
and
effectively.
B
It's
just
go
open
a
new
issue
reference.
This
one
tell
us
why
all
right
and
we're
not
going
to
we're
not
trying
to
keep
people
from
posting
stuff
we're
just
trying
to
make
it
a
more
efficient
place
to
go
through
and
to
address
people's
feedback.
Okay,
there
are
also
automations
that
have
been
set
up
so
that
this
will
happen
automatically
in
the
future.
So
if
you
received
a
whole
bunch
of
emails
over
night,
that
said
issues
were
closed
and
then
you
deleted
all
those
notifications-
and
you
saw
a
bunch
more
show
up.
B
This
automation
runs
every
24
hours
and
it
will
check
to
see.
Are
there
any
issues
that
have
been
closed,
that
also
have
no
activity
on
them
and
if
so,
go
ahead
and
lock
them
you'll
see
stuff
that
that's
being
done
by
this
bot,
and
we
have
a
couple
other
little
automations
and
stuff.
That's
like
that
as
well.
That's
generally,
the
the
big
changes
that
we've
made.
B
We
put
that
in
there
as
well
and
some
extra
explanation
on
some
of
our
issue:
labels
that
we
use
and
such
so
I
want
to
turn
this
back
over
to
the
next
presenter,
but
again
I'll
be
on
the
chat
and
I'm
happy
to
answer
any
detailed
questions
about
this,
and
if
you
have
any
feedback
on
stuff
that
we
did,
that
you
don't
like
or
stuff
that
we
did,
that
you
would
suggest
that
we
should
also
consider
and
do
again.
The
idea
here
is
this
issue
this
we
want
to
make
it
engaging.
B
We
want
to
make
it
the
best
resource
for
you
to
be
able
to
ask
questions
and
submit
issues
and
errors
that
you
find
with
the
SharePoint
developer
experience,
but
we
also
have
to
follow
a
couple
little
rules
here
to
make
sure
that
we
can
do
stuff.
Someone
tells
me
that
hey
I
ran
I,
did
this
in
the
power
and
the
SharePoint
admin
Center,
and
it
didn't
work.
How
do
I
fix
this?
It's
like.
We
can't
do
anything
about
that
in
this
issue
list
that
really
goes
in
the
tech
community
site
or
as
a
real
issue.
B
A
Wasn't
actually
too
many
questions
on
the
chat
for
now?
Let's,
let's
see,
if
we
get
more
when
Chris
starts,
presenting
I
want
to
recap
and
true
kernels
wasn't
the
person
who
created
the
process?
He
wasn't
the
person
who
made
the
decisions,
he
wasn't
the
person
who
who
now
accidentally
closed
your
issue.
It
was
a
decision
by
Microsoft
and
we
work
with
a
lot
of
the
MVPs
and
because
that's
how
we
scale.