►
From YouTube: ASP.NET Community Standup - Jan 2, 2018 - Season Opener
Description
A
B
B
C
B
C
B
Irie
up
to
my
domains,
so
then
I
updated
Hansel,
minutes,
calm,
which
runs
on
on
pages
and
web
based
return
net
web
pages,
and
you
see
up
here
where
it
says
secure,
but
if
I
go
to
the
page,
its
insecure
mmm-hmm,
but
it's
not
insecure.
It's
like
oh
we're
mixed.
We
know
we
feel
we
were
weird.
So
then
watch
this
if
I
clear
the
log
and
hit
refresh
no
empty.
This
is
a
nice
little
tip,
right
click,
empty
cache
and
hard
reload
watch
secure,
secure,
scoffs,
screw
it
right
yeah.
So
then
what
do
you
do?
C
B
No
like
binary
whatever,
like
I,
have
no
idea
what
I'm
doing
but
I'm
just
gonna
start
deleting
lines
of
code
yeah.
It's
this
thing.
It's
this
commenting,
plug-in
called
intense
debate.
Is
your
Bitcoin
miner,
which
is
HTTP,
but
here's
the
part
that's
confusing,
because
I
was
literally
while
you
guys.
Well,
while
you
were
texting
me
frantically,
like
get
your
stuff
together,
Scott
I
was
teaching
my
niece
how
to
debug
this
problem.
Uh-Huh
and
I
failed.
A
B
A
C
C
B
A
A
D
D
B
A
A
D
D
B
C
B
A
A
D
A
B
B
A
B
A
A
C
B
A
A
B
C
A
B
B
D
B
D
B
C
B
C
A
C
B
C
Just
hide
them
before
I
talk
to
you,
alright,
so
anyhow,
these
are
the
links.
I
will
be
presenting,
there's
a
QR
code
for
people
that
do
that
thing
and
I
will-
and
it's
already
in
the
description
for
this
deal,
I
got
a
bunch
from
Andrew
lock.
So
this
one,
the
main
reason
I'm
pointing
this
out
is
this
is
an
excerpt
from
his
book
coming
out
soon
and
it's
been
in
meet
MEAP
for
a
while
Manning
early
access
program,
but
this
is
an
introduction
to
middleware.
So
this
is.
C
A
C
So
this
is
an
introduction
here,
yeah
this
get
ready,
because
this
it's
it's
good
and
Andrew
lock
up
yeah
here
we
go
so
here
is
the
battement
chord
docker
files.
What
I
love
about
this
is.
He
goes
into
all
the
different
possible
docker
files
that
there
are
that
you
could
use
for
our
asp
net
and
dotnet
core
explains
what's
in
them,
but
here's
the
gold,
I
think,
is:
he
explains
at
the
end
of
each
one
why
she.
A
A
Credit
I
mean,
for
example,
jQuery
famously
all
of
its
content.
The
good
documentation
came
from
an
agreement
with
pack
publishing,
which
is
how
they
got
all
their
great
API
Docs
with
jQuery,
as
they
did
across
licensing
deal
and
that's
how
they
got
it
so
I
mean
I,
don't
think
it's
out
of
the
realm
of
possibility
to
suggest
that
if
we
see
great
content,
the
doc
team
approaches
them-
and
we
say,
hey
we'd
love
to
you
know,
use
this
as
a
doc.
Could
we
copy
it
and
it
and
like
attribute
it
and
go
from
there?
A
C
Love
yeah
he's
got
the
what
should
use
it
for
at
the
end
of
each
one
and
then
in
each
at
the
top.
Each
one
quick
bullet
points.
What's
in
it,
so
yeah,
it's
just
beautiful,
I
love,
it
cuz
I,
forget
from
time
to
time,
I'm
like
which
was
the
one
with
you
know.
So,
for
instance,
here
he
talks
about
the
asp
net
core
build.
You
know,
has
a
pretty
warm
package
cache
stuff
like
that,
so
good
stuff
and.
A
C
Cool
one
other
one
from
Andrew
Locke,
it's
been
a
month
since
we
talked
he's
been
busy.
This
is
asp
net
core
apps
using
cake
and
docker
so
cake
using
cake
for
build
files,
and
he
explains
some
things
about
he
talks
about.
First
of
all,
you
may
be
tempted
to
jump
in
and
use
the
cake
core
CLR
package,
but
that
only
works
with
dotnet
core
one.
Oh,
so
he
talks
about
why
he
used
the
mono
base,
one
to
start
with,
explains
all
the
different
stuff
about.
C
You
know
optimization
for
cake,
build
scripts
and
docker
all
that
kind
of
stuff.
So
nice-
and
you
see
here
the
tiny
little
scroll
bar
there's,
there's
a
lot
to
this
one
that
very
useful
all
right,
I'm,
moving
away
from
Andrea.
Thank
you
Andrew.
So
this
is
from
Francisco
Francisco.
This
is
actually
part
4
of
a
series
on
mini
blog
core,
so
many
blog
core
we
featured
before
that's
from
Mads
Kristensen
and
here
he's
been
deploying
it
to
a
lot
of
different
things.
C
A
C
C
C
C
C
So
that
is
in
step
in
part
two,
it's
a
three
part
series
and
he
goes
through
and
shows.
Where
he's
registering
it,
he
says
he
even
calls
it
out.
This
is
the
exciting
part
he
said
most
of
exciting,
but
I
think
he
means
most,
but
so
here
he's
registered
it
and
he's
got
a
change.
I
thought
that
type
I
didn't
think
that
one
got
ported
over
to
core
all.
A
A
B
A
D
C
A
B
C
Okay,
this
is
a
nice
one
from
the
battement
Fox
folks
and
her
from
Entourage
and
he's
we
featured
some
of
his
stuff
before
he's
got
a
cool
little
tip
here
on
setting
up
different
launch
profiles
in
vs
code.
So
if
you
want
to
you,
know,
debug
and
launch
with
with
Chrome
Firefox
ie
etc,
he
shows
how
to
set
up
your
launch
Jason
to
do
that.
So
nice
little
tip
I
got
a
talk.
Faster
talking
got
net.
This
is
kind
of
a
run-through
of
your
different
options,
circa
now
for
bundling
and
minification.
C
A
C
Don't
see
web
pack
interesting,
okay,
no,
all
right,
that's
a
good
point
and
then
you
know,
then
there's
a
bunch
of
other
ones
too.
I
don't
know
the
ones
he
listed.
Okay,
so
Janek.
This
is
I,
don't
know
how
many
times
I've
had
to
do
this
back
when
I
was
working
in
like
financial
companies
exporting
to
excel
and
CSV
and
asp
net
core.
C
So
just
you
know
some
nice
utility
code
to
have
around
you
know
returning
files
text,
CSV
et
cetera,
alright
long
series
from
Rihan
alam
on
his
peanut
core
identity,
so
he's
not
quite
complete
on
it,
but
he's
working
through
this.
This
one
is
the
kind
of
getting
started
and
he's
building
up
to
an
angular
for
front-end
this
one
from
Jerry
Pelzer.
This
is
on
creating
authorization
policies.
Dynamically,
an
asp
net
core-
this
is
actually
a
tip.
C
C
Okay,
now
we've
got
some
more
kind
of
auth
stuff.
This
is
Damian
Bowden
talking
about
using
EF
core.
In
this
case
he
uses
sequel
Lite,
but
he
says
you
may
also
want
to
use
something
like
service
fabric
etc.
So
this
is
how
to
put
your
configuration
data
store
in
an
EF
core
database
so
and
as
usual
with
with
Damian
a
lot
of
code.
Here,
it's
very
in-depth,
so
good
stuff
speaking
of
identity,
server,
I
just
want
to
call
this
out.
We
do
some.
C
You
know
Dominic
and
Damian,
doing
or
Dominic
and
Brock
sorry
doing
tons
of
great
stuff
in
the
community,
and
here
they've
started
a
patreon
page
too.
You
know,
so
you
can
support
them.
If
you're
using
identity,
server,
I
recommend
that
you
go
out
and
support
them
on
patreon,
that's
fantastic!
That's.
C
That's
that's
a
big
thing
that
I've
been
thinking
about
looking
at
with
dotnet
foundation
in
general
is
the
whole
kind
of
you
know
these
open-source
projects
we
want
them
to
like
for
selfish
reasons.
Like
you
said,
we
want
them
to
be
around
long
term.
So
what
can
we
do
to
support
them
and
make
them
long-term?
C
Survivable
not
depend
just
on
one
person
not
depend
on
somebody
having
some
free
time
here
and
there,
but
you
know
make
it
make
it
a
thing
you
know,
and
so,
like
over
December
I
actually
spent
a
good
amount
of
time
going
back
and
forth
with
with
Brock
and
Dominic
trying
to
figure
what
would
be
the
best
thing
for
them.
We've
set
up
open,
collective
under
dotnet
foundation.
In
this
case,
we
both
decided
patreon
work
best
for
them
and
patreon
you.
C
This
is
kind
of
something
where
you
don't
need
an
umbrella
organization,
so
they
didn't
need
to
do
this
under
dotnet
Foundation.
But
this
is
something
where
both
that
and
open
collective
can
be
good
for
project
to
have
sponsors
and
take
donations,
and
that
kind
of
what's
the
twenty
second
explosion
of
what
patreon
is
like.
A
A
B
B
If
I
have
a
couple
thousand
people
give
me
a
buck,
I
could
live
on
that
right.
The
other
option
would
be
using
things
like
brave
or
tip.
You
know
it's
basically
an
online
tip
jar
with
patreon,
a
patreon
OMA,
which
it
is
you
could
say
well,
there's
a
secret
place
for
get
a
copy,
get
Hansel
minutes
to
two
days
before
the
public
sees
it
or
only
get
custom
videos
or
once
a
month,
I'll
Skype
you.
So
it's
almost
like
you
can
create
a
little
membership
type
thing.
A
B
B
B
A
B
B
C
These
are
the
expenses
are
transparent,
Wow,
so
both
both
money
coming
in
and
money
going
out.
You
can
see
everything,
so
the
idea
here
is
this
is
an
open
source
approach
to
finance
right,
and
this
is
great
because
you
know
maybe
for
an
open
source
project.
You
don't
want
to
just
I
I,
don't
know
if
I
give
money
to
an
open
source
project.
What
are
they
gonna
spend
it
on?
You
know.
A
A
C
C
A
A
A
C
A
B
The
word
he
doesn't
say
it
doesn't
say
why
that'd
be
a
good
question,
so
the
woman
who
started
this
project
is
Pia
man
Cheney
and
she
is
on
Hanselman.
It's
episode,
592,
okay
and
you
can
learn
about
when
they
created
this.
It
was
not
meant
originally
for
open-source,
it's
about
the
liquid
democracy
and
about
supporting
organizations.
It's
just
an
open
source.
Really,
you
know
works
for
this.
This
is
fascinating.
You
know
it's.
C
B
C
A
B
A
C
B
C
Interesting
so
one
thing
that
is
interesting
with
open
collective
is:
you
do
need
some,
like
you
said,
an
account
like
an
escrow
somebody
to
hold
the
money
for
you,
and
so
there
was
a
good
amount
of
work
going.
It's
set
up
to
create
new
accounts
to
create
new,
like
accounting
thing,
so
that
we
can
hold
the
money
without
it
getting
muddled
in
with
the
rest
of
the
dotnet
foundation,
yeah.
B
C
Yeah
so
there
this
was
kind
of
a
behind-the-scenes
thing.
I've
been
working,
sweet,
yeah,
cool
all
right.
So
that's
that's
them.
I've
got
a
bunch
of
quick
quick
hits
for
Steve
Gordon.
He
did
his
first
asp
net.
Video
he's
actually
done
one
since
then,
so
he
talks
about
how
he
did
it
and
then
he
talks
about
this
is
a
nice
short
video
I
think
like
5-10
minutes,
eight
minutes
on
exploring
applications
startup
and
then
he
has
another
one
on
docker
as
well.
C
So
that's
exciting
he's
been
writing
a
ton
of
great
posts
and
it's
nice
to
see
him
doing
some
videos
too
speaking
a
great
post
from
in
he's
done.
A
series
of
gotchas
here
was
one
I
think
we
may
have
mentioned
before.
Actually,
but
this
was
on
environment
variables
and
understanding
delimiter
differences
between
different
environments,
so,
whether
colons
or
under
double
underscores,
are
required.
C
B
C
A
We
will
add
features
that
can
constitute
a
breaking
change,
that
to
the
presence
of
a
file
before
may,
have
had
no
side-effects
in
a
certain
context,
but
in
a
new
the
major
version
it
might-
and
this
is
a
classic
example
when
we
added
the
feature
of
honouring
certain
aspects
of
launch
settings
from
the
command
line,
not
just
visual
studio,
which
was
always
the
intent
of
launch
settings,
didn't
wasn't
conceived
as
being
a
visual
studio,
specific
feature.
It
was
always
meant
to
be
something
that
could
other
tools
could
leverage
moving
forward.
A
We
did
it
in
two,
oh,
but
if
you
didn't
read
about
it,
and
you
just
thought
about
data,
then
it
might
take
you
by
surprise
and
yeah
to
a
lesser
extent,
that
also
occurs
in
minor
versions.
We
we
add,
features
and
if
you're
not
aware
of
them,
you
can
run
into
them
and
then
wonder
how
this
happen.
I've
never
seen
this
before
it's
like.
Well,
we
added
that
feature.
I'm
yeah
two
minor
versions
ago,
you
just
haven't
happened
to
run
into
it.
So
yeah.
Sometimes
it's
our
fault.
A
We
don't
do
a
good
enough
job
of
disseminating
all
the
details
around
changes
that
we
make,
which
is
something
we
cob
viously,
continue
to
improve
on
and
sometimes
I
think
people
just
update
blindly
and
assume
everything's
gonna
be
fine.
Like
it's
I
think
it's
a
balance
say
you
have
to
make
sure
you're
reading
stuff
and
we
have
to
write
it
as.
C
C
Okay,
one
last
from
him
and
then
I'll
try
and
wrap
up,
so
we
can
get
on
to
Alana
and
friends.
So
here
we've
got
here
was
one
where
his
hyperlinks
weren't
working
in
razor
pages,
and
he
had
not
realized
that
there
was
a
separate
view
on
imports
for
razor
pages.
As
opposed
to
you
know
the
main
view
imports
for
views
so
important
thing
there
that
there's
there's
view
imports.
You
do
need
one
for
your
pages
as
well.
Oh
yeah,.
C
A
C
A
C
And
one
last
one:
this
is
from
at
Warren
I'm,
just
gonna
make
you
aware
of
it
and
you
can
go
read
into
it
in
more
detail,
but
this
is
talking
about
open
source
dotnet
in
general
three
years.
What's
it
looking
like,
he
has
some
cool
things
where
he
you
know
goes
into
some
statistics
here.
He's
got
this
nice
graph
where
you
can
find
out
actual
community
versus
Microsoft
interactive
today,
yeah.
C
C
D
D
C
A
A
A
Very
briefly
about
some
of
the
big
themes
this
year,
so
January,
it's
January.
Obviously
it's
a
new
year
as
arbitrary
as
that
day
is
just
means.
We
got
to
some
point
we're
in
the
Sun.
Obviously
we
often
like
to
try
new
things
at
this
time
of
the
year
and
we're
still
in
the
middle,
obviously,
but
our
last
release
was
still
a
major
release,
we're
working
towards
the
next
minor,
but
we
haven't
shared
an
awful
lot
of
structured
detail
about
it.
Yet
we've
kind
of
I've
spoken
about
things
on
here,
but
we
have
enough
blog
posts.
A
We
only
recently
in
just
before
the
holiday
season
did
an
effort
to
make
a
lot
more
issues,
sort
of
public
that
we've
been
working
on.
There
been
a
smattering
of
them,
but
a
lot
of
the
work
was
still
in
sort
of
planning
phase.
There's
a
lot
more
of
that
stuff.
That's
public
now,
which
you
can
go
and
sort
of
troll
out
github
repos
for,
but
we
haven't
done
a
blog
post.
We
haven't
done
a
coordinated
session
with
the
dotnet
folks
or
anything
about
this
is
what
we're
doing
into
one.
A
This
is
the
themes
and
all
that
type
of
stuff
and
we
haven't
done
a
sort
of
a
full
year.
This
is
what
we
want
to
cover
in
2018,
so
we
will
do
that
this
month,
all
those
things,
and
so
we
will
have
a
I
think
it's
Scott,
my
boss,
Scott
hunter
and
Richard
Lander
who's,
my
equivalent
for
dotnet
and
myself
will
do
a
channel
9
video
to
talk
about
the
to
one
stuff
and
we'll
try
to
do
a
blog
post
the
same
day.
That
gives
a
high-level
sort
of
overview
of
all.
A
You
know
the
themes
and
all
the
features
that
we
plan
or
that
we're
currently
working
on
for
2.1,
and
hopefully
we
can
share
something
about
a
schedule.
Schedules
are
always
a
tricky
topic
because
we
don't
have
a
crystal
ball,
but
we
will
try
and
share
as
much
as
we
can,
but
just
rest
assured
that
we're
working
on
stuff
four
to
one-
and
we
still
you
know
currently,
plan
with
a
very
lowercase
P,
it
sort
of
promise.
It's
a
plan
to
have
it.
You
know
2.1
rly
out
sometime
in
the
first
half
of
this
year.
A
We
just
don't
know
when
yet
and
there
will
be
previews
as
normal.
Then
we
have
to
do
an
RC
and
all
that
type
of
stuff,
but
we'll
get
more
details
about
that
before
the
end
of
the
month,
so
yeah.
So
that's
you
know
it's
all
goodness.
We
have
some
themes
that
I've
already
covered
off
on.
We've
made
some
really
good
previously,
on
the
show.
A
We've
made
some
really
good
progress
and
a
lot
of
those
things
what's
not
particularly
good
right
now
is
trying
to
use
them
like
if
you're
brave
enough
to
try
and
use
that
stuff
using
our
nightly
builds.
There's
been
some
fairly
large
changes
that
haven't
fully
rippled
through
the
end-to-end
yet
which
can
make
it
a
little
hard
to
consume
a
lot
of
those
changes,
and
so
hopefully
that
will
get
better
over
the
coming
weeks
as
well.
Yeah.
A
So
we'll
talk
about
talk
more
about
that
in
the
coming
weeks,
I'm
off
to
London
next
week,
as
is
Hanselman
4
in
DC
London,
although
I
think
I'll
be
here
on
Tuesday,
so
we'll
still
have
the
show.
Next
week,
Joe
John
you're
not
coming
this
time
right,
I'm,
not
look!
I
know
so:
it'll
be
Fowler
and
Fowler
and
I
and
handsome
is
going
I.
A
Think
Guthrie
is
going
this
year
as
well,
and
there
might
be
some
other
folks
on
Microsoft,
but
that's
the
only
ones
I
know
if
the
top
of
my
head
other
than
that
I'm
not
traveling
this
year,
so
I'll
be
here
every
week.
I'll
do
a
show
every
week
other
than
the
week
I'm
in
London
week
after
next,
but
oven
that
we
brought
a
lot
along
because
we've
made
one
of
the
changes
that
we
made
as
part
of
the
new
year
was
revisiting.
How
we
manage
the
issues
in
our
repo.
A
We
had
some
discussions
internally
in
December
about
whether
we
wanted
to
experiment
and
trial
with
some
different
approaches
to
managing
the
issues.
For
those
who
don't
know,
we
have
quite
a
lot
of
repos
in
the
HP
net
org
on
github.
Some
of
them
contain
very
little
code,
and
some
of
them
are
very,
very
low
traffic.
They
don't
have
a
lot
of
issues
in
them
and
there
that
I
they
may
have
some
active
issues
or
some
or
some
issues
that
are
there.
They
haven't.
A
We
talked
on
talked
about
a
lot
of
long
period
of
time
where
they
mend
us
not,
may
just
not
have
very
many
shooters
at
all
and
so
to
try
and
alleviate
that
all.
But
we
also
have
this
home
repo
where
we
do
have.
A
lot
of
issues
had
had
a
lot
of
issues
and
we
did.
We
did
and
a
lot
of
them
were
very
stale
and
there
were
actually
many
hundreds
of
them,
and
so
it
had
gotten
to
the
point
where
it
was
it
becoming
very
difficult.
A
If
we
wanted
to
try
and
address
this,
this
problem
of
issues
of
potentially
appearing
in
multiple
places,
how
will
we
go
about
how
we
gonna
go
about
sort
of
rationalizing
that
we
also
had
a
lot
of
instances
where
people
just
didn't
know
where
to
log
an
issue,
and
it's
not
limited
to
just
a
spin
out.
We
don't.
A
We
didn't
have
issues
logged
in
the.net,
repos
that
we're
really
free
to
Annette
and
so
we'd
have
a
lot
of
issues
that
have
to
be
moved,
but
we
know
very,
very
often
have
issues
logged
in
the
home
repo,
which
really
should
have
been
logged
in
one
of
the
sub
repos
and
then
for
whatever
reason
for
better
or
worse,
mostly
our
fault,
they
just
would
sit
there
and
not
really
have
anywhere
near
the
attention
that
they
should
have.
I.
Think
there
were
like
700,
open
issues.
D
A
A
Probably
you
know
a
lot
of
detail
in
there
that
should
get
attention,
and
so
as
an
effort
to
try
and
improve
that
this
year
we
decided
to
basically
declare
bankruptcy
on
a
lot
of
issues
that
were
over
a
certain
period,
so
over
a
certain
age
that
is,
they
hadn't
been
active.
No
one
had
commented
on
them
in
what
3
months,
3
months,
3
months
off,
because
anyone
is
free
to
reopen
issues
in
the
home
repo
them.
You
can
always
do
that.
A
A
If
I'm,
if
I'm
a
customer
and
I
want
to
log
in
issue,
how
do
I
know
which
repo
to
do
it
in
and
especially
for
these
smaller
repos,
it
can
be
difficult
to
know
which
one
to
put
it
in,
depending
on
what
part
of
the
system
you're
using
and
then
the
other
part
of
it,
which
is
just
a
you,
know,
owl
issue.
The
process
management
issue
is
like.
How
often
do
we
look
at
those
repos?
A
You
know
just
setting
up
alerts
for
all
those
repos
isn't
particularly
helpful
because,
as
you
can
imagine
with
that
many
repos
and
then
the
number
of
issues
we
get
relying
on
email
to
do.
Our
tree
aging
is
not
a
particularly
useful
tool,
and
so
we
took
the
decision
to
rationalize
those
repos
down
to
the
home
repo
so
effectively.
We
we
didn't
actually
disable
issues,
but
we
effectively
disabled
issues
in
about
20
repos,
the
20
years
of
20,
lowest
traffic,
repos
and
I.
A
A
In
turn,
and
so
as
a
result
of
that
we
basically
kept,
we
started
out
this
experiment
with
the
the
lower
traffic
repos.
Obviously,
because
we
wanted
to
test
the
waters
and
see
how
well
this
process
does
or
does
not
work,
and
if
it,
you
know,
ends
up
working
quite
well
and
we'll
give
it
a
period
of
time.
A
Obviously,
before
we
make
that
decision,
we
may
end
up
rolling
this
out
to
more
of
the
repos,
if
not
all,
of
them
so
including
the
bigger
repos
like
Razer
and
Kestrel
and
MVC
and
etc,
which
today
have
still
maintaining
you
know
all
their
issuer
management
in
those
repos.
And
you
know
as
part
of
looking
at
this,
we
we
looked
at
all
the
the
pros
and
cons
of
doing
it.
A
We
literally
have
like
many
dozens
of
repos
that
you,
you
validly,
could
put
an
issue
in
depending
on
what
part
of
the
system
you're
using
and
I.
Think
history
has
shown
us
that,
that's
probably
just
too
many
I
think
it's
fair
to
say
that
the
repo
granularity
was
initially
set
up,
not
with
the
idea
of
issue
management
in
mind,
but
with
the
experience
of
developers
who
are
coding
and
a
lot
of
the.
A
If
you
think
back
to
how
project
Jason
and
DNX
worked,
which
is
when
we
built
these
repos,
there
was
a
very
there
was
a
tight
mirror
between
the
repo
granularity
and
how
project
Jason
works.
The
ability
was
to
substitute
packages
for
source,
going
in
and
being
able
to
make
a
code
change
in
a
single
repo
and
look
at
the
effects
of
that
without
having
to
build
the
entire
system.
Those
were
kind
of
the
foundations
upon
which
the
original
repo
architecture
was
designed.
A
I,
don't
think
that
architecture
was
particularly
good
for
or
issue
management
it
froze
for
a
framework,
the
size
of
house
which
isn't
you
know,
it's
not
small,
it's
not
the
biggest
framework
in
the
world,
but
it's
a
very
it's
a
decent
sized
framework
with
about
I,
don't
know
30
people
at
Microsoft
to
have
to
deal
with
those
issues
and
then
obviously
a
much
larger
audience
outside
of
there
who
have
different
needs,
and
so
we're
trying
this
out.
Obviously
we'll
take
feedback.
Obviously,
anytime
we
make
any
type
of
change.
A
That's
impactful,
especially
one
that
impacts
people's
inboxes.
We
get
lots
of
good
feedback
which
we
have
and
sorry
about
the
sudden
increase
of
email
on
day
one
of
the
new
year.
That's
never
a
good
thing.
I
would
say
from
personal
experience
if
you're
relying
on
email
to
get
your
notifications,
where
stuff
having
in
github
I,
think
there
are
better
ways,
but
maybe
I
get
a
lot
more
than
most
people.
Maybe
it
works
well
for
for
some
people,
but
certainly
with
the
scale
that
we
work
at
email.
D
A
A
Is
another
one
that
comes
up
Roslyn
does
a
pretty
good
job
of
managing
and
triaging
issues
and
labeling
them
with
sub
labels
for
different
parts
of
the
product
and
then
core
effects
like
the
actual
dotnet
repo
core
effects
which
contains
not.
You
know
it's
not
one
thing.
It
sounds
like
it's
one
thing,
but
next
ended
libraries
and
core
effects,
but,
as
is
many
dozens
of
other
packages
that
aren't,
if
standard
library
and
a
whole
bunch
of
other
code
as
well
and
in
this
course
y'all
are,
and
they
all
use
various
sort
of
variations.
A
That's
a
funny
phrase
of
a
similar
theme.
You
know,
like
you,
basically
a
lot
of
issues
that
cover
the
fairly
disparate
code
bases,
but
don't
have
some
commonality
in
one
place
and
they
use
labels
and
processes
and
some
automation,
bots
and
things
to
manage
that.
So
we're
gonna
try
it
out,
and
we
said
we
did.
We
looked
through
the
pros
and
cons.
A
We
acknowledge
that
there
are
some
things
that
are
harder
to
do
with
this
setup,
or
it's
certainly
different
to
how
you
might
be
doing
it
today
and
so
we're
gonna
see
if
we
can
come
up
with
new
workflows
that
work
for
both
us
and
the
community.
In
doing
so
so
early,
it
was
a
couple
of
wrinkles
in
the
migration
I
think
at
one
point
the
bot
was
closing
pr's
that
it
shouldn't
have
been
and
stuff
like
that,
but
we
cleaned
all.
D
Yeah
yeah
I,
fixed
I,
fix
those
yeah.
There
were
I,
I
started
out
sort
of
people.
Ask
me
like.
So
how
did
you
do
this?
I
did
not
manually.
Do
it?
I
wrote
a
bunch
of
scripts.
I
used
the
octo
Canet
library,
which
is
comes
from
kenhub
and
I,
wrote
some
maisman
at
core
console
applications
and
start
out
migrating
one
issue,
and
then
you
can
look
at
the
time
stamp.
So
you
probably
see
the
rate
at
which
I
did
things
you
can
see
when
they
were
created.
D
C
A
A
If
the
only
good
that
comes
out
of
this
is
that
there's
a
renewed
attention
on
how
issues
are
getting
logged
phrase
be
net,
who
sees
them
how
quickly
they
get
assigned
to
the
right
person
at
a
today.
That'll
be
worthwhile
if
you
have
to
roll
back
everything,
but
we
create
some
new
tools
to
make
that
better,
I
think
it'll
be
worthwhile,
because
I
think
it's
fair
to
say
that
we
had.
A
We
got
into
a
situation
where
there
were
so
many
repos
and
so
many
issues
so
much
debt
that
it
was
difficult
for
us
to
look
at
that
and
figure
out
well.
This
is
how
we're
going
to
resolve
it,
but
keep
the
same
process
that
we
have
right
now
we
figured
it
was
a
good
time
to
try
something
a
little
bit
different
and
see
if
we
could
come
out
the
other
side
with
with
with
a
better
process.
It's
not
finished
yet
like
we
still.
We
have
the
process
for
servicing.
A
A
Yeah
so
like
what
is
the
process
for
I
found
a
bug
and
I
wanted
to
be
considered
for
servicing
of
the
current
release,
rather
than
please
pick
it
fix
in
the
next
release,
and
then
once
we
get
to
a
minor
and
then
we
have
the
to
train
thing
happening
again,
where
we
have
an
LTS
release
and
a
current
release.
How
does
that
work
on
github?
Like
all
you
know,
for
anyone
like
how
do
we
manage?
We
found
this
bug
and
we
fixed
it
in
the
in
the
next
minor
release.
A
But
how
do
we
mark
it
as
a
candidate
for
the
patch
and
like
I,
want
all
that
to
be
very
transparent,
very
clear
so
that
we
don't?
You
know
we
mitigate
or
minimize
the
opportunity
of
making
mistakes,
because
you
know
what
happens
it's
it's
complicated.
Well,
we
live
in
and
we
want
to
make
sure
that
it's
this
much
process
around
this
is
necessary
to
reduce
the
amount
of
times
we
get
things
wrong.
So
it's.
C
A
So
we
we've
been
using
github
projects
to
do
the
10,000
foot
view
of
a
milestone.
So,
for
example,
we
used
it
during
our
two
one
planning
internal
planning
exercise
we're
now
using
it
for
our
sort
of
active
work
exercise.
So
it
only
focuses
on
features.
It
doesn't
cover,
obviously,
by
tracking
bugs
and
things
in
the
project
isn't
particularly
helpful.
It's
just
too
big,
there's
too
many
of
them
specially
at
the
scale
of
a
spin
on
it.
Maybe
for
a
very
small
library.
It
makes
a
lot
of
sense.
We
also
use
projects.
A
We
use
projects
are
better
to
say,
like
within
repos.
We
use
projects
for
feature
areas,
so
in
MVC,
which
is
quite
a
large
frame
work
we
are
doing
targeted.
Work
like
in
2.1
around
api
is
which
we
call
kodkod,
and
we
have
some
stuff
around
Razer.
So
we
have
sub
projects
that
we've
created
so
that
sub
parts
of
the
team
can
organize
their
work
and,
like
we
know
it's
not
stipulated,
we
don't
say
it
must
have
these
columns
or
anything
they
just
kind
of
self
organize,
and
do
that,
so
we
can
quickly
see.
A
But
from
my
point
of
view,
is
the
PM
I
was
very
interested
in
using
projects
just
forgot
to
see
a
large
dashboard.
It's
like
here's,
the
scope
of
what
we
are
planning
for
this
current
will
or
the
current
work,
and
then
by
looking
at
that,
I
can
say
this
is
what's
currently
being
assigned
and
is
being
worked
on.
A
This
is
the
ordered,
prioritized
backlog
of
things
to
go
in
this
next,
like
for,
basically
when,
when
a
developer
becomes
free
and
they
need
to
pick
what
work
to
do
next
other
than
bugs
what
is
the
next
thing?
They
pick
off
the
backlog
right
so
or
github
issues.
Don't
help
you
with
that.
There's
no
prioritization!
You
need
to
use
something
that
can
give
you
prioritization
for
that
projects.
Give
you
that
capability,
because
you
can
order
them,
so
we've
been
starting
to
use
it
for
that,
and
then
we
can
very
quickly
see.
A
Oh,
we
have
enough
work
right
now.
If
you
just
basically
correlate
a
card
with
the
number
of
people
that
we
have
to
fill
the
team
with
work,
it
also
allows
you
to
very
quickly
see
this
feature.
Area
is
owned
by
this
program
manager
and
this
developer,
okay,
which
is
also
useful.
We
can
make
sure
that
the
right
people
are
involved
in
decisions,
and
so
we've
been
using
projects.
For
that
point
of
view,
it's
Christian
just
point
out,
though,
the
problem
with
organization-wide
projects
is
that
only
we
can
see
them
I
wanted
to
make.
A
You
have
to
be
a
member
of
the
organization
to
see
an
organization-wide
project
and
only
organization-wide
projects
can
have
issues
in
them
from
multiple
repos.
That's
a
limit.
Eight,
that's
a
limit,
a
limit,
ization
of
of
the
the
org
projects,
and
so
I
would
very
much
like
to
be
able
to
have
our
active
work
project
at
some
point
be
open
to
everyone,
so
anyone
can
just
go
and
see.
What's
the
team
currently
work
on
when
it
comes
to
features
and
enhancements,
like
things
aren't
bugs,
what
are
they
working
on?
A
A
Where
can
I
look
at
the
list
of
things
that
we're
thinking
about
so
I
can
go
and
make
a
case
for
changing
that
priority,
like
that
information
is
not
captured
anywhere
in
github
today,
there's
no
tool
in
github
that
lets
you
do
other
than
projects,
but
if
you're
spread
across
multiple
repos,
they
don't
help
you
and
so
there's
a
hope
that
by
making
some
of
these
changes,
we
could
start
to
leverage
some
of
those
tools
down
the
permits
and
the
sonic
guarantee.
But
it's
a
hope.
B
A
A
So
far,
I
think
most
of
the
comments
that
the
the
cons
that
people
have
pointed
out
are
all
things
that
we
had
considered
so
far.
I,
don't
think,
there's
been
anything
so
far.
That
was
like.
Oh
my
god,
we
didn't
really
think
of
that.
We
had
considered
all
of
those
and
determined
that
we
felt
the
benef.
The
potential
benefit
of
this
experiment
could
outweigh
those
cons
now
I'm
not
saying
like
in
all
things.
A
Whenever
you
talk,
we,
unfortunately,
are
isn't
really
a
good
way
of
a/b
testing
this
or
like
doing
it
in
parallel,
like
you,
can't
just
have
to
try
it
and
deal
with
the
pain
and
then
determine
whether
it
was
worthwhile
with
the
benefits,
and
so
that's
what
we're
doing
but
yeah
like
everything
that
I've
seen
pointed
out
so
far
like
we
did,
talked
about
and
go
well
yeah.
That's.
C
D
Repos,
don't
get
migrated
it's
a
home
or
or
maybe
we
sign
no
well,
there
I've
heard
today,
cuz,
you
know
this.
This
affects
not
only
the
community
affects
people
here.
Also
working
on
you
know,
on
this
project
and
I've
heard
that
there
do
exist,
some
tools
out
there
that
lets
you
get
notifications
filtered
by
only
certain
labels.
So,
as
Danny
mentioned,
we
will
make
sure
that
we
at
least
tag
things
with
a
repo
label.
D
So
every
issue
and
the
home
repo
we
have
a
repo
:,
whatever
their
appropriate
repo,
is
so
repo
:
HTTP
abstractions
we
phone
:,
whatever
it
is,
and
that
there
exists
tools
out
there
that
people
have
written
that
lets.
You
get
notifications,
filter
based
on
these
things,
and
so
we
might
be
able
to
recommend
some
of
these
tools
for
people,
because
we
think
everybody
might
need
it,
and
so
that
is
a
negative
okay.
Well,
if
I
have
to
use
another
tool,
now
that's
not
ideal,
we
agree,
that's
not
ideal,
but
they're.
D
What
I
think
we've
the
conclusion
we've
arrived
at
is
that
no
tool
exists
that
solves
all
of
the
problems
like
we
could
just
remove
the
issue
Travis
from
github,
like
we
consider
that
at
one
point
one
time
ago,
to
use
some
other
system.
We
experiment
with
using
JIRA
is
a
very
popular
bug,
tracking
tool
and
you've
seen
that
probably
used
and
some
other
projects
you
work
with,
and
there
are
just
too
many
downsides
to
using
JIRA.
It's
not
synched
with
github.
The
permissions
are
different
and
it's
it
just
didn't
work
for
us.
D
C
D
D
D
We
need
for
certain
issues
with
you,
know
the
pull
request
and
metadata
about
the
pull
requests
and
all
these
kinds
of
things,
and
it
takes
about
30
seconds
to
refresh
the
page,
and
so
we've
written
tools
and
we've
tried
working
on
optimizing
and
we
have
made
improvements
to
it,
but
even
they
have
limitations
and
so
we're
just
trying
to
find
the
right
balance
between
these
different
things.
And
again
we
we.
We
agree
with
the
feedback
that
we've
gone.
We
just
think
that
the
the
balance
is
kind
of
yes,
yet
to
be
found.
A
A
And
if
someone's
pointed
out-
but
we
are
not
the
only
org
that
is
expressed
this
this-
this
not
concerned,
but
like
has
found
that
once
you
get
to
a
certain
size
on
github
I
haven't
seen
like
the
the
canonical.
This
is
how
you
manage
large
issues
like
a
large
frameworks
with
shoes
on
github,
like
everyone
has
tried
different
things,
and
everyone
has
had
github
issues
isn't
enough
by
itself
and
that's
why
all
these
tools
exist,
and
but
you
know,
every
every
project
has
slightly
varying
needs.
But
anyway
it's.
C
Pointed
out
here
at
Carol,
Sigmund
did
on
the.net
team.
Did
a
I'm
I've
seen
him?
Do
a
presentation
at
dotnet
fringe
talking
about
how
they
manage
issues
and
he's
got
some
sort
of
tool
for
that,
and
then
someone
else
on
this
also
pointed
out
octo
box,
which
I
think
probably
works,
but
I
don't
know
if
it
would
scale
to
a
lot.
D
A
You
know
there
is
a
github
sort
of
I
think
it's
a
github
view
where
you
can
basically
any
org
your
be
yeah
I
know:
Fowler
spends
a
lot
of
his
ages.
Looking
at
that
and
I
just
can't
do
it
like
this
just
so
much
stuff
on
that,
but
I
do
find
that
yeah
I,
don't
look
at
every
issue.
Obviously
this
is
too
many
of
them.
Mm-Hmm.
D
But
I
I
wrote
all
the
spot
like
on
vacation
or
holiday,
as
some
of
you
over
the
last
few
days
like
you
know,
yesterday
was
not
a
workday,
nor
were
the
two
days
before
that
and
that's
when
I
I
was
just
like.
Oh
I'll
sit,
you
know
watching.
Oh
the
new
episode
of
the
new
series
season
of
black
black
mirror
watch
that
having
finished
it,
no
spoilers
we're
all
inside.
D
A
I
do
genuinely
hope
that
this
will
make
it
easier.
I
mean
when
we,
when
we
look
at
the
pros
and
cons,
we
do
prioritize
certain
audiences
over
others.
I
mean,
let's
be
totally
honest,
like
we
tend
to
prioritize
people
who
might
be
coming
to
log
or
find
an
issue
for
the
first
time
or
who
don't
use
github
as
frequent
like
every
day.
A
D
A
We
have
a
lot
of
issues
there
as
a
result,
and
so
we
didn't
really
have
a
good
process,
because
all
the
issues
that
we
worked
on
daily
is
developers
and
PMS
were
in
the
other
repos
and
so
again,
part
of
this
is
a
try
and
if
we
centralize
the
gaze
towards
one
place,
it'll
likely
get
more
attention,
etcetera,
etc.
So
yeah,
like
I,
said
we'll
monitor
animal
and.
D
There's
some
really
good
comments
and
hearing
about
poking
kid.
How
about
to
get
helps
credit
there's
a
lot
of
the
features.
Sometimes
you
feel
like
they've,
been
there
forever,
but
github
projects.
That's
a
brand
new
feature.
It's
only
been
around
a
few
months.
The
like
things
like
issue
templates,
mm-hmm,.
A
D
C
D
C
C
D
D
Announcements
yeah
now
one
thing
is
worth
noting,
for
example,
the
announcements
repo.
We
have
currently
no
plan
of
no
combining
that,
because
the
announcements
repo
is
meant
to
be
the
super
low
traffic
there's,
you
know,
you'd
be
lucky
to
even
see
one
post
there
a
day
and
we
lock
all
the
issues
there
and,
if
you're,
some
of
you
might
remember
because
I
know
some
of
the
people
here
on
the
chat
are
people
have
been
around
for
ages
and
ages.
D
C
D
I
think
it's
kind
of
been
serving
its
purpose,
but
you
know
well:
I
could
see
with
a
home
repo
experiment
that
this
is
an
experimental
we
are.
We
are
I've,
been
reading,
all
the
feedback
Damien's
been
reading
the
feedback,
and
you
know,
hopefully
we
can
come
up
with
something
that
is
makes
everybody
equally
unhappy.
Yeah.
A
I'm
that's
the
best.
We
can
really
hope
for
in
a
democracy
or
Republic,
as
this
is
really
unless
a
christian
makes.
It
makes
the
point
which
I
think
I
tried
to
address,
but
he
says
that
you
find
ironic
that
you
haven't
been
able
to
handle
the
issues
in
home
already,
but
still
want
to
funnel
everything
else
into
the
same
bucket.
Everyone
else
everything
else
in
the
same
bucket
and
that's
what
I
meant
by
saying
that
by
by
drawing
by
focusing
more
on
it,
you
tend
to
find
solutions
to
those
issues.
A
I
think
the
reality
is
no
one
codes
in
home
today
and
so
the
issues
in
home.
If
I
want
to
be
incredibly
blunt
and
a
little
unfair,
basically
go
there
to
die
before
what
we
did
a
few
days
ago,
because
it
wasn't
part
of
any
developers
workflow
on
the
team.
It
wasn't
part
of
an
engineering
managers
workflow
or
even
a
p.m.
everything
we
do
day-to-day
is
about
managing
the
work
that
developers
on
the
team
are
doing
majorly
or
it's
answering
email
and
the
home
repo.
Just
wasn't
part
of
that
float
now.
A
It
was
an
annulment
of
our
failing,
as
we
had
700
open
issues
in
there
that
were
frankly,
just
completely
forgotten
about,
and
so,
as
I
said
at
the
beginning,
in
some
ways
we
declared
bankruptcy
on
those
ones
and
we're
starting
again
afresh
with
a
with
a
modified
process
and
we'll
see
how
this
one
works
out.
We
don't
profess
to
get
it
right,
we're
gonna,
try
it
out
and
see
how
it
goes.
Anyone
who's
ever
worked
on.
A
large
project
will
know
that
you
know.
A
Process
change
is
part
of
refining
how
you
work
on
something
and
changing
stuff,
as
you
go
along
as
you
learn
stuff
is
what
you
do
so
you
know
Bay
with
this.
We're
gonna,
try
it
out
and
see
how
it
goes
and
we'll
we'll
figure
it
out
and
the
Christian
it's
a
to
have
to
work
around
yeah
I
mean
he's
saying
it's
sad.
A
You
have
to
work
around
quite
unquote,
missing
github
features
and
I
will
say:
we've
been
making
that
same
complaint
to
people
that
give
hope
for
many
many
years
it
to
be
fair,
like
they
didn't
build,
github
solely
for
projects
like
aus.
You
know
it
has
to
cater
for
a
massive
spectrum
of
different
project
types
and
they've
done
very
well.
I
mean
they've
added
a
lot
of
features
that
I've
been
pleasantly
surprised
and
they
don't
the
thing:
is
they
don't?
A
D
D
A
Showed
up
one
day
like
the
idea
is
that
the
protected
branches
showed
up
one
day
yeah,
you
know,
there's
a
lot
of
really
but,
and
those
things
aren't
needed
in
small
projects.
Protected
branches
is
very
much
around.
You
know
large
code
bases
with
lots
of
branches,
lots
of
people
contributing,
and
you
want
to
ensure
that
you
don't
accidentally
pushed
off
into
the
wrong
place.
That's
considered
your
master
or
whatnot,
so
yeah,
so
I
think
a
lot
of
those
features
have
been
happy
to
see.
Get
I.
A
Think
issues
is
one
of
those
areas
where
you
could
argue
that
you
know
they
could
add
a
lot
more
sort
of
advanced
stuff,
but
I
think
the
pushback
would
be
anything
they
add
beyond.
What
they
have
right
now
would
would
very
much
become
that's
the
word
I'm
looking
for
it
has
to
be
opinionated
by
definition
like
right
now,
issues
a
very
rudimentary.
A
Beyond
that
requires
them
to
to
sort
of
stipulate
structure.
You
know
like
there's
no
related
issues.
Today
you
can
tag
issues
but
they're,
not
formally
related.
You
can't
do
hierarchies,
for
example,
and
we
trialed
building
bots
to
create
hierarchy
trying
to
mimic
like
you
know,
you
could
define
a
feature
or
use
a
story
and
then
you
would
have
associated
work
items
like
there's.
A
Nothing
like
that
in
github
projects
are
very
much
a
reaction
to
people
building,
Kanban
boards
and
those
type
of
things
for
github,
and
they
seem
to
work
pretty
well,
except
for
the
things
that
we've
talked
about
when
you
get
to
a
multi
repos
there,
a
problem
and
so
yeah
I
hope
that
at
least
shares
our
thoughts
behind
it
and
you
know,
keep
giving
us
the
feedback
and
we'll
be
patient.
You'll
be
patient.
A
D
D
D
A
A
D
B
C
B
I,
like
my
job
very
happy,
happy
to
pay
the
rent,
Thank
You
Microsoft,
paying
me
money,
but
when
I'm
on
vacation
for
two
weeks
at
Christmastime,
I
feel
very
retired
and
did
not
know
my
password
this
morning,
mm-hmm
and
I
did
a
password
reset,
which
was
fun.
Are
you
guys,
positive
and
upbeat
and
like
awake,
or
do
you
feel
this
week
is
kind
of
a
crappy
week
and
you're
gonna
feel
better
next
week?
So.
A
B
A
Exactly
what
I
did-
and
it
wasn't
really
until
last
night
that
I
allowed
myself
to
think
about
what
I
would
want
to
achieve
in
this
short
week
before
I
cuz
I'm
going
to
London
next
week,
as
are
you
Scott
I
mentioned
when
you're
of
the
room
and
there's
some
stuff
I
have
to
get
done
before
then,
but
yeah.
So
like
yes,
I
agreed
that
it
was.
It
was
lovely,
not
thinking
about
work
for
a
week
and
I'd
like
to
be
able
to
figure
out
how
to
do
that.
More
often,.