►
Description
Come learn about new improvements in NuGet with PMs: Jiachen Jiang and Christopher Gill.
Featuring: Jiachen Jiang, Christopher Gill
A
A
A
And
we're
live,
I
believe,
hold
on.
Let
me
wait
for
the
actual
youtube
and
yeah
we're
live
on
twitch.
The
youtube
countdown
is
still
going,
there's
a
little
delay.
Okay,
yeah
we're
actually
live.
Just
confirming
sorry.
Hi.
Welcome
to
the
dot
net
community
stand
up
this
week
is
all
about
net
tooling,
I'm
kendra
havens.
I
host
a
lot
cody
and
jordan
couldn't
make
it
today,
but
we
have
awesome
other
guests
from
the
nougat
team,
chris
and
giachen.
Why
don't
you
introduce
yourselves
chris?
You
go
first.
B
All
right
yeah,
so
I'm
chris
and
I'm
a
pm
on
the
nougat
team.
I've
been
on
the
nougat
team
for
about
a
year
now,
but
I've
already
had
an
opportunity
to
work
on
a
pretty
even
share
of
features
on
nuget.org
and
on
nougat
and
visual
studio,
and
we're
really
excited
to
show
you
a
few
of
those
today.
So
I'm
excited
to
be
here
thanks
for
having
us
kendra.
C
A
Awesome,
okay,
so,
first
up,
I
have
a
couple
links
to
show
off.
Just
talk
a
little
bit
about
what's
happening.
We
always
have
a
little
url
list
if
you
want
to
follow
along
with
the
topics
that
we're
covering
okay,
it
is
in
chat,
hopefully
on
both
platforms
that
we're
streaming
to
I'm
getting
used
to
a
new
streaming
service
that
john
and
james
figured
out.
It's
awesome,
so
let
me
figure
out
how
to
share
my
screen.
A
Okay-
and
it
looks
like
it's
on.
Does
that
look
good
guys?
You
have
to
tell
me:
oh
did
it?
Oh
okay,
good
looks
good
okay,
so
the
first
one
is
microsoft.
Ignite
happening
in
september
register
sign
up
for
updates,
get
excited
about
it.
Will
I
have
a
talk?
Won't
I
I
don't
know
yet,
but
it's
best
to
lock
favors
the
prepared.
So
that's
what
we'll
be
doing.
A
This
website
also
has
a
bunch
of
like
promotions
and
vision,
content
and,
I
think,
even
stuff
from
last
year,
yeah
to
watch
on
demand
sessions
and
stuff.
So
you
can
kind
of
see.
I
don't
know
what
you're
missing.
We
also
had
a
bunch
of
cool
blogs
up
on
the
dotnet
blog,
so
matt
mitchell
took
a
deep
dive
into
how
dot-net
builds
and
ships,
which
is
great
because
we
had
a
bunch
of
repositories.
A
A
A
We
are
trying
to
improve
the.net
project
system,
so
we
have
a
few
questions
for
you,
especially
about
what
times
that
you
expect
things
to
be
happening
in
your
solution,
so
the
time
until
you
get
full
intellisense
or
the
solution
exploring
that
kind
of
thing,
so
we
want
to
yeah
engage
with
you
talk
about
it.
Project
system
is
all
open
source,
so
we're
just
trying
to
get
more
feedback
and
yeah
get
some
input.
A
We
got
a
survey,
cool
and
olia
wrote
a
really
cool
blog
post
about
webview2,
which
now
is
available
for
net
before
it
was
just
c
and
c
plus
plus
this
is
basically
hosting
or
rendering
web
content
inside
of
wpf
win
forms
or
win
ui
as
like.
A
control
which
is
really
really
nice
excited
for
webview,
too,
is
that
it.
C
And
you
know
what,
because
chris
and
I
are
both
pms
and
we
know
we
love
to
adhere
to
the
serial
types
of
pm,
so
we
have
a
powerpoint
presentation
prepared,
don't
worry,
I
know
I
know,
but
I
I
know
you
can't
see
how
many
slides
there
are.
But
I
promise
you
it's
not
a
lot.
So
I'm
going
to
share
my
screen
now
and
just
talk
through
some
of
our
slides.
C
Oh
perfect,
so
hi
everyone,
hi
friends,
we're
chris
chen
and
we
are
pms
on
the
nougat
team
and
we're
here
to
show
off
a
few
new
features
either
already
rolled
out
or
coming
soon
before
that.
However,
we
we
want
to
take
the
moment
to
adjust
to
address
a
really
burning
question
in
the
nuget
community,
and
I
think
chris
has
a
lot
to
say
on
this.
I
chris
has
been
here
for
a
while
more
than
I
have,
and
he
knows
this
is
a
matter
of
life
and
death.
C
B
How
do
you
pronounce
nougat
anyways,
so
we
act,
I
actually
just
tweeted
a
poll.
It
was
retweeted
by
the
official
at
nougat
account
so
check
it
out
and
vote
on
your
favorite
way
or
your
own
personal
way,
to
pronounce
nougat,
of
course,
nuke.
It's
just
how
I
say
it,
I'm
not
even
completely
convinced.
So
you
know
we
could
always
rebrand.
So
let
us
know.
C
Yes,
we
value
our
community
feedback
and
you
know
what,
depending
on
the
results
we
get,
maybe
maybe
the
nuget
team
will
have
a
little
sort
of
moment
of
introspection.
Try
to
figure
out,
you
know.
Is
it
what
we're
gonna
continue
to
be?
Maybe
we'll
be
new
jay
nugget
who
knows
we'll
find
out
so
many
options,
so
many
options
and
the
only
way
to
find
out
is
to
tune
in
for
the
rest
of
this
presentation,
because
we're
going
to
touch
upon
our
top
four
pronunciations
at
the
end.
A
C
C
Searching
has
been
an
area
of
frustration
for
customers
for
a
really
long
time
and
funny
story.
I
I
was
an
intern
at
microsoft
in
my
in
my
last
summer
and
I
actually
worked
with
nuget.
I
I
wasn't
on
a
nougat
related
team
at
all,
but
I
was
working
with
new
yet
and
I
just
remember
trying
to
track
down
packages
and
really
having
no
idea
what
to
do
so.
This
feature
is
actually
already
live,
so
what
I'm
going
to
do
is
click
through
the
current
feature.
A
Yeah,
I'm
really
excited
to
see
this.
I
think
especially
my
team
might
have
had
a
very
vocal
asks
in
the
past.
The
the
one
that's
most
occurring
to
me
is
like
filtering
for
a
rosalind,
analyzer
nuget
package
specifically,
but
this
is
mostly
our
problem
because
we
don't
have
a
great
platform
for
helping
people
discover
new
rosalind
analyzers
that
they
can
install
on
their
project
to
get
cool.
Oh
sorry,
I
can
add
your
screen
back.
Oh
awesome.
A
C
C
So
for
nuka.org
we
I
mean
okay
overall,
we
know
that
we
have
a
lot
of
packages
over
here
on
nuget
and
what
I'm
going
to
do
is
you
know
what
like
I've
heard
about
this
cool
package
called
coverlet?
I
don't
know
much
about
it.
I
I'm
looking
for
a
dot
net
global
tool,
so
I'm
I'm
just
going
to
type
this
in
and
okay,
eight
packages
cool,
but
I'm
looking
at
these
descriptions-
and
I
have
no
idea
which
of
these
is
the
actual
net
global
tool.
Kendra
like
just
from
a
quick
look.
A
C
Oh
man,
I
know,
and
sometimes
I'll
have
to
like
click
in
or
something
like
that
and
try
to
track
down
that
information
like
I'm.
I
don't
know
pm
soft
sorry
p.m,
sherlock
holmes
or
something
like
that,
and
even
so
I
can't
really
figure
out
if
this
is
what
I'm
looking
for,
but
now
drumroll
we
have
a
new
filtering
section
that
allows
us
to
filter
by
the
package
type.
So
let's
say
hey.
I
want
to
find
the
net
tool.
We
applied
that
and
wait.
Okay.
C
C
Oh
god,
it's
over,
I
mean
at
least
just
hold
or
press
f11.
Yes,
okay,
there
we
go
all
right.
It's
close
and
personal.
Here
are
the
variety
of
filters
that
we
have.
We
have
dependents
like
we
can
sort
by
dependency,
which
is,
as
you
can
see,
the
vast
majority
of
results
for
couplet,
but
we
also
now
have
different
ways
of
sorting
your
results,
because
people
have
different
priorities
when
they're
looking
for
packages
right,
maybe
I'm
a
net
developer.
Who
is
working
on
something
that
I
want
to
be
super
super
stable?
C
I
don't
want
any
sort
of
bugs
that
might
come
up,
even
if
the
material
is
super
cool
super
new.
All
of
that,
so
all
I
want
is
what's
most,
what
is
most
downloaded
of
all
my
results,
so
in
that
way
I'm
able
to
sort
like
this,
but
if
I'm
looking
for
the
newest
packages
possible,
then
I'm
getting
results
that
are
from
two
hours
ago,
15
days
ago,
and
suddenly
my
entire
priorities
are
just
entirely
realigned.
C
When
it
comes
to
what
package
they
need
for
their
project
with
package
compatibility
search
where
we
will
be
able
to
search
specifically
for
packages
that
can
run
on
a
framework
of.net
that
you
are
using,
so
if
you're,
a
very
seasoned
experienced
grizzled
net
developer-
and
you
say:
okay,
I
only
want
package
versions
that
will
run
on
my
very
old
version
of
net.
You
can
get
that
or
if
you're,
just
starting
out
and
you're
saying
okay,
I
need
net
framework
or
drug
net
core.
C
That's
also
an
option
for
you,
so
there's
no
need
to
squint
through
a
whole
bunch
of
small
texts
about
the
exact
dependencies
and
all
that
to
figure
out
what
your
package
can
run
on.
Something
else
we're
looking
at
is
scoring
metrics
for
packages
based
on
quality
security,
a
variety
of
other
issues
that
our
customers
have
expressed,
they're
totally
interested
in
that
they
want
to
know
which
packages
are
the
most
secure,
are
the
most
reliable.
So
now
we
have
to
find
a
way
to
make
sure
that
they're
getting
exactly
what
they
want.
A
C
And
that
actually
leads
right
into
my
last
point,
which
is
we're
still
figuring
out.
What
is
the
best
way
to
present
this
to
customers,
because
we
have
heard
that
people
are
excited
about
this,
but
we
don't
know
the
exact
way
we
want
to
implement
this.
So
if
you're
curious
or
have
any
thoughts
about,
what's
going
to
be
most
helpful
for
you,
tweet
at
us
send
a
message
in
the
chat
and
later
on
in
a
presentation.
We'll
also
have
a
link
for
you
to
set
up
a
call
with
us
to
chat.
A
A
C
A
B
B
So
just
to
be
clear,
this
is
a
feature
that's
currently
under
development
that
we
should
be
coming
soon
to
a
visual
studio
near
you,
but
there's
still
opportunity
to
give
feedback
and
make
sure
that
we're
doing
it
the
exact
way,
that's
going
to
provide
the
most
value
to
you.
But
let
me
show
you
what
we
have
in
mind
so
far,
so
for
those
of
you
who
are
unfamiliar
with
the
floating
version.
Essentially
it's
a
way
to
format.
B
Your
version
request
such
that
you
can
ask
for
the
highest
version
within
a
specified
range
using
the
star.
So,
for
example,
let's
say
I
request
one
dot
star.
What
I'm
asking
for
here
is
the
latest
available
version
within
the
one
dot
range.
So
if
I
have
these
available
versions,
it'll
resolve
to
1.1.
B
Now,
let's
say
I
keep
2
dot
star
and
the
package
author
releases,
two
new
package
versions,
2.2
and
3.0
the
ones
in
bold
right
here,
because
I
asked
for
2.star
it'll,
give
me
the
latest
version
in
the
2
dot
range,
so
I'll
resolve
to
2.2,
even
though
3.0
is
newer.
So
this
is
a
really
nice
way,
especially
if
you
have
some
dependencies
that
you
know
you.
You
have
more
control
over
that.
You
particularly
trust
you
automatically
get
updates
without
having
to
manually
go
through
the
update
process.
B
B
So,
first
let
me
go
over
what
that
experience
looks
like
today
in
visual
studio,
so
today
the
only
way
to
be
able
to
request
a
floating
version
is
to
do
it
manually
in
the
project
file,
which
already
might
not
be
the
best
experience
possible
right
in
general.
We
know
that
many
of
our
customers
like
to
be
able
to
do
everything
that
they
have
to
do
through
the
nuget
ui
in
visual
studio
they'd,
rather
not
have
to
manually
edit
the
project
file.
But
let's
go
through
this
example
here.
B
So
here
I've
requested
virgin
star
from
nuget.packaging
star
essentially
says:
hey,
give
me
the
latest
stable
version
for
this
package.
So
let's
see
what
that
does
in
the
nuget
ui,
let's
go
to
manage
nuget
packages
all
right.
So
here
you
can
already
see
that
something
looks
a
little
off.
It
says
I
have
version
0.0.0
installed,
which
is
not
a
version
that
actually
exists.
B
B
So,
of
course,
this
just
on
its
own
can
be
a
little
bit
frustrating
for
customers.
It
can
also
be
particularly
frustrating
when
you
update
to
a
new
explicit
version
of
nuget.packaging
and
because
you're
so
let's
say
I
go
to
5.6
and
because
it
doesn't
surface
that
you're
using
a
floating
version
right
now,
it'll
overwrite,
the
initial
value,
the
the
floating
version
you
requested
with
the
explicit
version.
So
if
I
go
back
to
my
project
file,
I
should
have
5.6,
but
it's
really
difficult
for
you
to
know
that
it's
going
to
do
that.
B
So
this
you
know,
there's
some
obvious
elements
here
like
showing
the
actual
proper
requested
version
in
the
version
list,
as
well
as
in
the
installed
field,
but
something
that
we
knew
would
add
a
lot
of
value
to
customers.
Experiences
would
be
to
not
not
only
show
the
correct
resolved
version
in
the
installed
and
packaged
list,
but
also
allow
you
to
request
custom
versions
directly
through
the
ui.
B
So
the
plan
here
is
to
turn
the
version
field
not
just
into
a
drop
down
of
the
existing
available
versions,
but
into
a
combo
box
field
that
actually
allows
you
to
put
in
custom
inputs.
So
here
I'll
be
able
to
input
star
and
it'll.
You
know,
add
the
value
to
the
list
and
it'll
and
once
I
click
update,
it'll
change,
the
value
in
my
project,
file
to
star
and
it'll
request,
the
latest
stable
version.
B
B
So
now
it's
a
lot
clearer
to
the
customer
that
they
have
a
exp
that
they
have
a
custom
version
request
specified,
while
also
showing
the
correct
resolved
information
so
essentially
put
a
lot
more
power
in
your
hands
to
be
able
to
play
around
with
your
version
requests
directly
through
the
visual
studio.
Ui.
B
Now
your
question
now,
your
next
question
might
be
all
right.
This
is
great
for
the
project
level
view,
but
what,
if
I
have
a
really
large
solution
with
a
lot
of
different
projects
and
a
lot
of
different,
potentially
different
versions
of
the
package
throughout
that
solution
that
I
want
to
try
to
consolidate.
B
So
that's
what
the
solution
view
is
for,
but
we
decided
that
we're
going
to
add
a
little
something
to
that
as
well
to
make
this
process
easier.
So
we
took
a
bit
of
a
cue
from
the
dot
net
cli,
where
they
show
you
the
requested
and
resolved
version,
and
we
created
an
extra
column
here
in
the
solution
view
box,
so
that
you
can
see
explicitly
what
versions
you've
requested,
even
if
it's
a
custom
version
like
a
star
and
the
version
it
actually
resolved.
To
now,
let's
say
I.
A
B
To
have,
I
want
all
my
packages
across
my
or
all
of
the
the
same
package
across
my
solution
to
have
the
same
version.
I
want
them
all
to
use
star,
for
example,
today,
there's
no
way
to
consolidate
that
easily.
If
you're
going
to
do
that
by
manually,
editing
the
project
file
you'd
have
to
go
through
every
single
project
file
and
add
star
to
it.
Well,
now
we'll
show
you
the
super
set
of
all
the
different
custom
versions
that
you
have
in
the
drop
down
list.
B
So
if
I
want
to
consolidate
all
of
my
projects
to
use
star,
I
can
do
that
really
easily
and
I
won't
create
any
misalignments
in
my
solution
so
to
show
you
a
demo
of
what
we
have
so
far
here.
You
can
see
I'm
going
to
request
4.10.star,
which
should
give
me
the
latest
version
in
the
4.10
range
for
mock
package
and
then
once
that's
installed,
it's
going
to
be
a
little
quick,
so
make
sure
you
take
a
look
at
the
version.
B
The
package
list,
as
well
as
the
installed
field
and
you'll,
be
able
to
see
that
it
properly
resolves
to
the
proper
version.
It
doesn't
show
me
4.10.0
by
default
that
went
a
little
fast
there
at
the
end,
but
you
could
also
see
that
it
showed
the
4.10.star
in
the
project
file,
so
essentially
the
kind
of
paradigm
change
that
we're
making
is
that
we
want
the
version
field
to
always
be
a
direct
reflection
of
what's
in
your
project
file.
So
there
shouldn't
be
so.
A
A
B
A
A
B
There
we
go
and
it'll
so
the
way
the
you
know,
the
the
version
I
don't
want
to
go
into
too
much
detail,
but
the
way
the
custom
ranges
work
is
that
I'll
take
the
minimum
version
that
you
specified.
So
today
this
works
perfectly
fine
in
in
the
project
file.
You'll
see
it
resolves
to
the
correct
requested
version,
but
if
I
go
to
manage
nuget
packages
right,
it
doesn't
surf,
even
though
it
shows
the
correct
resolved
version.
It
doesn't
show
me
that
I'm
using
a
custom
version
range.
B
A
B
A
B
Right
so
we're
still
working
on,
I
think
improving
our
documentation
around
guidance
for
best
practices
around
using
floating
versions
and
lock
files.
But
to
answer
the
question:
nuget
does
have
support
for
lock
files
and
you
can
use
a
lock
file
to
lock
down
your
dependencies
and
make
sure
that
you
have
repeatable
builds.
That
is
something
that
we
do
have
support
for.
A
B
B
A
I
could
imagine
we're
super
excited
to
be
releasing
like
parameter
hints,
and
it
gives
like
an
inline,
tiny
text
version
of
like
the
parameter
name
that
the
method
is
expecting,
so
you
can
kind
of
reuse
it.
I
could
imagine
some
some
kind
of
floating
tip
next
to
it
with
a
path
or
something
like
that.
C
B
As
you
type
in
so
let's
say
I
type
in
10.star
for
newtonsoft.json,
for
example,
the
the
metadata
in
the
package
details
pane,
will
automatically
reflect
what
that's
going
to
resolve
to
at
least
based
on
whatever
feed
you
have
selected.
So
that
means,
if
you
are
sometimes
playing
around
with
the
stuff
and
you're,
not
super
sure
what
10
dot
star
is
exactly
going
to
resolve
to.
We
can
show
you
a
preview
of
the
version
that
you're
getting.
A
A
B
B
A
A
B
Me
switch
there,
we
go
so
we
avoided
the
little
inception
thing
all
right.
So
the
next
big
feature
that
I'm
excited
to
announce.
You
know
some
of
you
who
follow
the
at
nougat
twitter
or
follow
me
on
twitter,
which,
if
you
don't,
you
should
may
have
seen
that
I've
been
recently
asking
for
customer
feedback
around
readme's
as
well.
B
So,
let's
get
into
it.
So
what
do
I
mean
by
embedding
and
displaying
a
readme?
So
what
I
mean
is
we
want
to
be
able
to
include
a
readme
file,
a
mark,
a
readme
markdown
file
in
your
nuget
package.
So
currently
there
actually
is
already
an
existing
workflow
to
add
documentation
to
your
package
today,
but
it's
a
post
package,
upload
step.
That
means
that
after
you
upload
your
packagenuga.org,
you
have
to
specify
either
a
url
to
your
readme
or
documentation
or
manually.
You
know
add.
C
B
Project
file,
you
can
also
add
it
using
the
package
readme
tag,
so
what
happens
after
you've
added
it
to
your
package?
So
let's
say
I've
added
my
readme
to
my
package.
The
next
step
is
to
upload
it
to
nuka.org
for
everyone
else
to
be
able
to
enjoy.
So
I'm
going
to
give
you
a
bit
of
a
preview
of
what
the
experience
for
the
manual
upload
process
on
nougat.org
is
going
to
look
like.
B
So
here
I'm
adding
my
package
and
you
can
see
that
there
is
a
preview
of
what
the
readme
file
is
going
to
look
like
on
nuget.org.
So,
if
you're
concerned
about
some
kinds
of
formatting
or
you
want
to
double
check
that
your
readme
looks
good
before
it's
shown
to
potentially
thousands
or
millions
of
people,
then.
B
Of
fans
yeah:
this
is
the
best
way
to
do
that,
and
just
to
make
sure
that
if
you
have
a
really
long
readme,
we
don't
push
a
submit
button.
Two
miles
down
the
page.
The
window
is
gonna,
be
a
limited
size
that
you
can
just
scroll
through
to
to
quickly
check
your
readme
file
before
you
finally
submit
now.
You
can
also,
of
course,
upload
your
package
using
the
cli.
B
B
Now
just
to
give
you
an
idea
of
what
the
end
experience
is
here,
I
want
to
show
you
a
side
by
side
of
a
really
popular
azure
package,
azure.storage.blogs
without
the
readme
and
with
the
readme,
so
you
should
be
able
to
immediately
tell
the
page
is
a
lot
richer?
There's
a
lot
more
information
at
your
fingertips
right
so
right
off
the
bat
if
they
uploaded
their
readme
today,
you'd
be
able
to
see
getting
started,
you'd,
be
able
to
see
key
concepts
about
the
package
and
examples
of
how
to
use
it
right.
B
So
today
we,
I
think
you
know
most
of
the
feedback
we
get
from
customers
is
hey.
Nougat
is
great
for
finding
packages
that
I
already
know.
I
want
it's
not
as
great
for
learning
about
packages
and
and
figuring
out
what
a
package
does
on
the
spot
without
having
to
bing
it
or
go
to
their.
You
know
linked
project
site
or
repo
to
see
the
readme.
A
B
So
I'm
really
excited
that
we're
gonna
make
the
package
details,
experience
on
nougat
a
lot
richer
and
let
people
not
only
you
know,
see
important
statistics
about
the
package
or
view
the
version
list
or
dependencies,
but
also
let
them
figure
out
what
it
answered.
The
question:
what
does
this
package
do
and
how
do
I
use
it?
Is
this
really
what
I
want.
A
B
Yeah
exactly
so
yeah,
so
we're
really
excited
from
the
package
author
standpoint.
Sometimes
we
get
hey.
You
know.
Nuget
is
a
little
limited
in
the
kinds
of
links
I
can
show
the
information
I
can
show
because
we
have
a
kind
of
a
you
know,
a
predetermined
sidebar
of
information
that
we
have
available.
B
A
Promote
your
open
source
repo,
so
you
can
get
contributors
and
yeah
exactly.
This
reminds
me
a
lot
of
the
visual
studio,
extensions
actually
and
how
a
lot
of
times
the
readme
is
exactly
what
we
have
on
the
visual
studio
marketplace:
extensions
page.
So
I'm
glad
this
is
like
oh
cool
same
deal.
We
can
use
this.
B
Yeah
exactly
and
the
other
really
exciting
part
about
it
is
you
know,
because
a
lot
of
readmes
also
have
things
like
examples
and
and
references
that
you
can
that
are
really
useful
to
you
as
you're
learning
to
use
a
package.
We
also
want
to
make
sure
that
this
was
quickly
accessible
from
visual
studio.
B
So,
in
addition
to
the
links
that
we've
already
had
in
visual
studio
in
the
past,
we'll
also
be
adding
a
field
for
the
readme
link.
So
once
you
click,
this
you'll
immediately
be
taken
to
the
readme
for
the
package
that
you're
looking
at.
So
let's
say
I'm
you
know
I'm
trying
to
work
with
a
library
I
just
installed,
but
I
forgot
how
to
use
a
particular
functionality
or
a
particular
command,
or
I'm
curious
how
this
is
going
to
work.
A
Awesome,
that's
super
cool.
I
just
I
guess.
The
question
that
occurs
to
me
is
if
I
already
have
a
readme,
because
my
nuget
package
is
open
source
and
it
automatically
is
like
part
of
the
repo
at
the
root.
We
probably
don't
have
any
like
detection
to
just
automatically
add
it.
People
will
keep
it
a
manual
step
for
it
to
show
up
on
nougat.org.
I
guess.
B
So
you
know
the
for
the
first
release.
We
are
not
planning
to
have
auto
detection
of
readmes,
the
reason
being
that,
because
we
haven't
set
that
precedent
for
the.net
ecosystem,
yet
not
necessarily
everyone
uses
the
readme
file
for
documentation,
like
might
be
a
more
common
practice
in
other
ecosystems,
so
just
to
make
sure
we
don't
surprise
our
customers
or
accidentally
upload
some
information
that
wasn't
the
documentation.
They
were
hoping
to
upload.
B
A
B
A
B
So,
like
I
was
saying,
I
think
we
mentioned
a
couple
times
earlier
about
the
experiences
that
are
coming
soon
to
visual
studio
into
nooga.org.
A
lot
of
these
are
still
in
progress,
even
though
they're
coming
relatively
soon
and
we'd
still
love
to
hear
your
feedback,
even
if
it
doesn't
make
it
into
the
initial
release.
You
know
we're
going
to
be
iterating
on
these
things
and
adding
to
them
going
into
the
future,
and
even
if
you
don't
have
comments
about
the
specific
features
that
we
mentioned
today
in
general,
we
love
to
hear
your
feedback.
B
B
Chris
ray
gill,
this
is
me
I'm
at
chris
ray
gill
jochen
is
at
jianjiang,
and
we
also
have
a
another
pm
john
who
you
may
have.
If
you
follow
the
nougat
account
or
you
follow
him
on
twitter,
you
may
have
heard
a
lot
from
because
he's
also
been
posting
the
link
I'm
about
to
get
to
asking
for
feedback,
so
something
that
we've
also
started
doing
very
recently
is
that
we've
committed
to
significantly
increasing
the
amount
of
customer
interviews
and
the
amount
of
customer
outreach
that
we're
doing
so.
B
But
yeah,
so
if
you
want
to
book
a
call
with
us
to
be
more
specific,
usually
it's
going
to
be
some
pm
and
a
couple
engineers
feel
free
to
go
to
aka.msla
talk
to
nougat
and
you'll,
be
taking
you'll,
be
taken
to
our
bookings
page.
So
we
have
a
few
of
the
features
and
areas
that
we
are
currently
working
on
specified
there.
B
So
you
can
schedule
a
specific
call
to
talk
about
floating
versions
in
the
pmui
or
readme's
on
nougat.org
or
finding
and
choosing
packages
like
john
chen
talked
about
earlier
with
the
filtering
process
or
the
scoring
metrics.
These
are
all
things
that
we
would
absolutely
love
your
feedback
on.
So
you
know
if
you
have
time
and
you
have
the
interest
check
out
the
link
and
schedule
a
call
with
us.
A
Guys,
I
just
want
to
say
I
really
admire
this.
It's
sometimes
really
hard
to
be
come
just
randomly
add,
like
a
public
end
point
to
a
team
that
has
been
maybe
not
like
closed
off,
but
I
guess
internal
development
has
been
happening
for
a
really
long
time,
so
I'd
really
admire
that
you're
getting
out
there
and
doing
the
live
streams
and
having
scheduling
all
this
stuff
so,
like.
I
hope
everyone
watching
knows
that
turning
point.
Maybe
this
is
exciting
things
that
are
happening.
That's
how
I'm
feeling
at
least
so
super
super.
C
Awesome
there
we
go
so
something
that
we
wanted
to
emphasize,
though,
before
we
go
into
hey
community
engagement.
Things
like
that
is
we
really
want
all
sorts
of
comments.
So
these
are
some
of
the
comments
that
we've
gotten
on
a
variety
of
surveys
and
we
read
them
and
we're
like
oh
they're.
They
make
us
feel
so
good,
we're
so
happy
like
awesome
and
then
we'll
just
take
one
step
outside
of
whatever
sort
of
survey
bubble
we
have,
and
then
we
see
things
like
if
you
could
search
rather
odd
mean
tweets.
C
A
C
C
I
don't
know
who
you
are,
but
I
think
you
should
write
a
book,
maybe
not
about
roasting
nougat,
but
don't
do
that.
Don't
please
yeah,
please
don't,
but
don't
restrict
creative
freedom.
No!
No!
No!
I
like
it.
No.
What
we
want
to
emphasize
is
that
a
bunch
of
these
quotes
here,
especially
the
will.
I
stopped
using
nougat
one,
that's
from
like
a
thousand
word
long,
blog
post
about
things
that
you
can
improve
on
and
actually,
as
I
was
reading
through
that
I
wasn't
going
like
oh
no
mean
tweets,
I
was
going
like
problems
are
opportunities.
C
You
don't
write
a
thousand
word
long,
blog
post
about
something
you
don't
care
about
at
all
and
you
aren't
going
to
hope
for
the
best
for
so
we're
really
excited
to
work
with
all
of
you
all
of
you
out
here
in
the
dot
that
stand
up
like
beyond.
All
of
that,
in
order
to
make
you
get
a
better
package
manager
for
everyone,
so
be
honest
and
we'll
be
honest
too.
A
C
B
A
B
C
B
C
B
C
Says
nupt?
Okay,
so
something
that
I
found
out
in
my
onboarding
process
that
completely
like
well,
not
even
horrified
but
just
stunned
me
for
a
moment,
is
that
sometimes
people
call
on
nougat
packages
nuggets
which,
which
makes
sense
because
nougat.
But
it
just
made
me
really
uncomfortable
to
like
read
through
threads,
where
people
are
going
like
yeah,
like
I'm
gonna,
add
some
nuggets
into
my
project
so
that
that's
an
additional
suggestion
for
that.
B
C
A
C
C
A
B
A
That
git
is
just
it
sounds
like
it's
get
related
and
it's
not
interesting.
Oh,
I
remember
I
was
gonna
say
when
you're
branding
things,
sometimes,
even
if
you
make
like
90
happy,
if
that
last
10
hates
the
option
that
you've
chose
it
might
not
be
worth
it,
maybe
go
for
something
a
little
bit
more
moderate
like
mid-range,
something
that
gently
pleases
everyone.
Nobody
loves.
I
don't
know.
A
C
C
B
I
actually
want
to
get
customer
feedback
here
right
because
we
want
to
do
everything.
You
know
we're
customer
obsessed
here
new
year.
We
want
to
make
sure
that
we,
you
know,
we
run
everything
by
our
customers.
If,
if
new
or
if
nugget
wins
the
poll,
does
anyone
want
us
to
change
the
install
button
to
order?
So
you
can
order
nuggets.