►
Description
In this episode of Desktop Community Standup you will meet some of our key OSS contributors and the WinForms team members working with public PRs. We will talk about the process of submitting, reviewing and accepting PRs and other nuances of OSS development.
Community Links: https://www.theurlist.com/desktop-standup-2020-09-24
Featuring: Olia Gavrysh (@oliagavrysh), Igor Velikorossov (@IgorRussKie), Hugh Bellamy, Tobias Käs
A
A
Hello,
everyone,
I
think
we're
live.
Thank
you
so
much
for
joining
our
desktop
community
to
stand
up.
My
name
is
olia
gavish,
I'm
a
program
manager,
on.net
team,
focusing
on.net
desktop,
and
I
have
amazing
guests
today
with
me,
so
this
episode
will
be
focused
around
open
source
development
and
contributing
to
microsoft
repositories.
A
A
A
A
B
B
Yes,
yes,
and
I
interviewed
why
online
as
well,
so
it's
awesome
and
my
role
is
to
look
after
winforms
runtime.
It's
anything
to
do
when
you're
on
your
app
and
to
make
sure
your
app
is
running
correctly.
It's
running
the
way
you
expect
it
to
run
and
that's
what
primarily
my
job
is.
Obviously
I'm
not
alone
in
this,
and
I
get
help
from
my
team
members
and
obviously
wonderful,
open
source
contributors
who
I
have,
but
it's
primarily
my
role,
my
responsibility
to
make
sure
that
windows,
phones,
runtime,
behaves
at
its
opposed.
B
Let's,
let's,
let's
step
back
a
little
bit,
I've
been
in
open
source
for
quite
a
few
years
now,
so
I've
been
on
both
sides
of
open
source
has
been
as
a
contributor
and
as
a
reviewer.
So
I
do.
I
appreciate
the
the
joy
when
your
contribution
is
accepted
and
I
appreciate
the
the
sadness
and
frustration
where
your
contribution
is
is
not
even
acknowledged
or
or
it's
when
when
rejected.
So
so
I
try
to
to
work
with
this
and
appreciate
every
contribution
I
get
and
when.
B
Before
raising
a
pull
request
to
us
or
in
any
repository
in
general,
is
it's
a
good
thing
to
talk
with
the
team
to
act
like
knowledge,
hey,
I
want
to
work
on
this
issue.
Is
this
issue
still
available
and
discuss
how
you
want
to
approach
the
issue
because
you
may
be
thinking
of
the
issue
in
in
a
small
narrow
situation
or
in
our
case
where
the
team
may
be
looking
at
the
significantly
more
general
case
like
in
wind
forms?
B
We
have
a
lot
of
consumers
around
the
world
right
and
oh
yeah,
yes,
and
as
a
user
you
you
may
have,
you
may
have
found
the
bug
which
frustrates
you
obviously,
but
you
solving-
or
you
may
be
solving
for
your
specific
case
without
regret
how
how
the
users
may
be
using
it
without
knowing
where
the
team
is
planning
to
take
I'm
saying
front
time.
So
it's
a
good
idea
to
talk
with
the
team
first
and
ask
questions.
Asking
questions
is
always
good
to
find
out.
B
What's
the
best
way
to,
I
guess,
solve
the
issue,
address
the
issue
and
once
it's
done
once
you
understand
or
have
I,
I
guess,
appreciation
how
that
needs
to
be
solved.
Then
it's
a
good
time
to
raise
pull
requests
and
the
pull
request
is
all
is,
is
a
discussion
right?
It's
don't.
We
don't
expect
to
have
a
pull
request,
which
is
finished
in
first
go.
B
Quite
often,
there
may
be
several
iterations
to
call
requests
where
you
send
something
to
us
and
we'll
look
at
and
say
and
provide
some
suggestions
where
they
can
be
functional
suggestions,
so
something
missing.
So
something
is
incorrect
or
can
be
improved
further
or
it
can
be
non-functional
where
you
know
you
don't
adhere
to
our
styling,
for
instance,
guide,
guidelines
etc.
B
So
what
makes
a
good
fear
to
me
pull
request
is
all
about
review
experience.
It's
no
longer
about
the
author
at
this
stage.
It's
all
about
the
reviewer,
because,
as
an
author,
I
presume
you
understand
the
problem.
You
understand
the
solution.
Now
we
buy
by
submitting
a
pull
request.
Now
you
need
to
convince
me
as
a
reviewer
that
your
solution
is
correct
and
is
good
and
acceptable
as
well
as
I
need
to
be
able
to
understand
your
solution.
B
Right
and
and
a
good
pi
is
the
one
which
is
small
and
and
targeted
right,
because
if
your
pull
request
starts
addressing
multiple
issues,
it
becomes
very
difficult
to
reason
about
it,
and
we
will
very
much
likely
ask
you
to
actually
break
it
down
or
may
shut
it
down,
because
it's
not
addressing
a
single
thing.
It
may
be
addressing
multiple
things
and
another
thing:
a
good
pi
contains
tests
right.
So
so,
if
there
is
a
problem
we
we
want
to.
B
A
B
B
C
B
B
B
B
A
B
G
petro,
it's
235
and
I
stand
at
201,
so
yeah
I
I
have
some.
I
have
some
catching
up
to
do
and
and
the
fourth
one
is
tobias,
which
is
45
so
but
tobias
doesn't
send
as
many
pull
requests,
but
he
provides
extremely
valuable
guidance
and
expertise
to
us,
which
is
absolutely
appreciated,
makes
my
life
significantly
easier.
B
A
B
B
That's
that's
pretty
much
it
I
you
can
find
me
in
twitter
as
well.
I
do
respond
to
twitter.
You
can
find
me
in
gita.
I
do
respond
in
gear
every
now
and
then,
but
primarily
is
github
again
with
this
two
two
fellows.
I
have
them
on
speed
dial,
but
I
don't
use
that
privilege
theory
often.
I
can
prefer
github
because
it's
it's
it's
a
public
domain
and
everyone
can
see
the
conversation
we
can
learn
from
this.
We
can
always
refer
back
to
conversation
we
had,
which
is
which
is
useful.
A
A
B
Other
things
is
where
our
contributors
have
suggestions,
api
suggestions
and
they
go
hey.
It
wouldn't
be
nice
to
have
this
feature
in
forms
such
as
stars
dialogue,
which
we
mentioned
back
in
may
and
for
api
suggestions.
We
have
a
template
where
we
ask
an
offer
or
suggestion
to
think
through
the
issues.
We
don't
accept
it
just
random,
drive-bys
and
say:
hey
just
implement
this
feature,
someone
walks
away.
B
Now,
if
you
want
this
feature,
you
you
work
with
us,
you
think
through
the
api
which
that
that
feature
would
involve
how
that
api
would
fit
into
the
existing
wind
forms
runtime
and
the
designer
how
we
would
affect
the
accessibility
issues,
and
once
we
discussed
that
at
length,
and
we
have
a
good
appreciation
and
feeling
and
the
community
chimes
in
and
provides
feedback,
then
we
take
it
to
the
next
level.
Take
it
to
email
and
the
company
say,
saying:
hey.
B
We
have
a
wonderful
proposal
which
we
think
is
worthy
of
conclusion,
and
we
ask
emo
and
other
cool
fellows
and
girls
at
the
api
review
board
to
play
devil's
advocate
and
ask
tough
questions
of
us
and
help
us
shape
even
better
api
that
we
can
come
up
with,
and
once
we
have
a
sign
off.
We
put
that
feature
back
into
runtime
repo,
and
it
may
be
that
the
team
would
work
on
it
or
more
often
than
not.
It's
we
put
it
out
for
the
community
contribution.
B
B
He
provided
a
number
of
valuable
proposals
for
this
view,
enhancement,
and
we
got
most
of
them
in
already,
and
there
is
still
a
few
up
for
grabs.
So,
if
you're
interested
in
being
contribute
contributing
to
winforms
and
be
part
of
the
story
and
help
to
shape
the
story
with
us,
you're
welcome
to
come
and
contribute,
and
we
have
few
other
api
which
have
been
reviewed
and
accepted
for
implementation.
The
upfront
graphs
you're
welcome,
come
in
and
work
on
them
as
well.
B
I
appreciate
every
contribution,
no
matter
how
big
or
small
like
if
a
fixing
it
a
typo
in
the
documentation
is,
is
fully
appreciated,
like
don't
be
afraid,
don't
think
that
you
need
to
be
not
a
seasoned
like
a
veteran
developer
right,
that
you
need
to
be
a
computer
science
degree
graduate
or
anything
like
that.
No,
you
don't
have
to
like
if
you
find
something
which
you
think
you
can
tackle
like
you
know,
fix
a
typo.
It's
appreciated.
B
A
A
A
Oh,
that
is
very
nice
thanks
to
everyone
on
the
team
for
contributing
to
continuing
to
invest
in
bin
forms.
It
has
really
clean
and
well
thought
out
controls
and
apis,
plus
a
great
visual
design
experience
that
makes
it
showy
to
work
with
well.
Thank
you
so
much
for
these
kind
words,
and
I
want
to
thank
our
open
source
contributors
and,
as
igor
just
said,
we
received
so
much
input
from
the
community.
So
thank
you
community
for
developing
it.
B
A
A
Right
yeah,
I'm
a
huge
fan
of
that
feature
myself
and
just
to
add
to
iger's
response.
We
are
reviewing
visual
studio
feedback
tickets.
That
is
a
ticket
that
you
can
go
in
visual
studio
in
the
top
right
corner
and
submit
a
feature
request.
So
we
are
taking.
We
are
looking
through
all
those
tickets,
we
are
prioritizing
them
and
some
of
them
will
go
to
dotnet
six
as
well.
So
if
you
have
any
ideas,
suggestions,
feedback,
please
file
it
through
visual
studio
feedback.
A
We
will
read
every
single
of
them
and
we
appreciate
your
help
and
your
opinion
on
it
right
and
I
think,
eager
to
you.
My
last
question
to
you
was:
do
you
have
any
interesting
story
through
all
the
time
that
you
all
those?
What
is
it?
Two
years
a
year
year
and
a
half
year
and
a
half
yeah
that
you've
been
working
with
open
source
community?
Do
you
have
any
fun
story
to
tell
us
or.
B
Yeah
I
mean
well
my
it's
it's
a
difficult
gig
to
to
be
sort
of
a
frontman
of
the
open
source
repository
right,
be
that
microsoft
or
say
I'm
sorry,
frontman
at
git
extensions.
That's
another
open
source
project,
I'm
helping
with
just
shameless
plug
git
extensions.
Is
a
windows
ui
for
git.
It's
a
feature
rich!
It's
windows
forms
applications!
That's
why
I
guess
it
has
a
special
place
in
my
heart
and
why
I'm
participating
in
it.
B
It's
it's
difficult,
gig,
but
it's
very
enjoyable.
I
get
to
interact
with
a
lot
of
people,
I'm
sort
of
blessed
with
getting
people
like
you
and
tobias
helping
in
winforms.
I
have
wonderful
people
helping
to
build
git
extensions
so
some
days
some
days
are
tougher
because
when
I
have
400
emails
sitting
in
my
mailbox
because
he
generated
204
requests
overnight
and
I
need
to
review
and
I
feel
well,
I
do
feel
pressure
that
I
need
to
acknowledge,
pull
requests
and
issues
in
timely
manner.
B
As
I
said,
because
I
coming
from
open
source
background,
I
fully
appreciate
how
frustrating
it
may
be
when
you're
seeing
them
when
you
spend
your
time
quite
often
after
work.
After
your
family,
you
went
to
bed,
you
you're,
trying
to
fix
something,
you're,
sending
full
requests,
and
for
days,
weeks
months
and
sometimes
years
these
new
crickets.
B
At
least
we
have
a
label
and
prioritize
it
and
and
one
more
thing
as
a
team,
we
have
weekly
triages.
So
if
you
submitted
an
issue
typically
dude
on
friday
morning,
sydney
time
which
is
firstly
in
seattle,
so
if
you
send
it
on,
you
know,
on
friday
or
saturday
it
may
be
a
week
or
sometimes
two
weeks,
because
we're
too
busy
before
we
prioritize
you,
if
you
so,
don't
feel
that
you
know
you
send
it
to
to
know
where
we'll
we'll
look
at
it
and
and
prioritize
and
put
it
in
appropriate
milestone.
B
A
Yeah,
thank
you
so
much
sugar
exxon.
I
want
to
thank
you
for
all
your
work
and
all
your
enthusiasm
and
for
being
so
proactive
and
very
excited
about
the
product.
We
are
super
happy
to
have
you
on
with
you
and
thanks
for
very
valuable
insights.
Now
I
want
to
spend
a
few
minutes
answering
the
questions
and
then
we
can
move
to
our
next
guest.
So
there
was
a
question
about
porting.
A
Porting
for
libraries
from
dotnet
framework
to
dotnet
core
and
yes,
we
have
a
portion
doc.
I
placed
the
link
to
it
in
the
chat
so
check
it
out
it's
on
microsoft,
docs
and
it
has
step-by-step
instruction
how
to
port
your
libraries
from
the
framework
to
dotnet
core
porting
from.net
core2.net
5
is
very
easy
in
visual
studio
in
your
properties.
You
just
go
to
page
with
target
framework
and
in
the
combo
box
you
choose
between
core
and
dotnet
file,
so
that
experience
is
very
easy.
A
A
A
They
will
have
to
remain
windows
only
because
we
have
a
very
strong
dependencies
on
windows
apis
and
for
us
to
work
around
those
dependencies
would
mean
to
ride
those
platforms
from
scratch,
and
but
there
are
multi-platform
desktop
solutions
we
are
working
on.
It's
called
maui,
so
go
ahead
check
it
out.
If
you
need
the
solutions
for
linux
and
other
platforms.
B
A
A
A
A
All
right
and
with
that,
we
can
move
to
our
next
guest,
hugh
bellamy
and
he
must
have
invented
the
source
generator
and
the
time
stretching
machine,
because
he
is
able
to
pump
thousands
of
lines
of
code
into
no
time
as
eager
said
just
while
we
were
watching
for
this
community
to
stand
up.
He
submitted.
What
triple
requests
is
that
correct
and
he
is
the
biggest
contributor
to
winforms
repository
and
one
of
the
biggest
contributors
to
dotnet
as
a
whole,
and
we
know
his
alias
is
huby
so
hugh.
A
E
Sure,
first
thanks
for
having
me
and
always
thanks
for
reviewing
all
the
pull
requests.
I
know
some
cumberland,
especially
thanks
to
eagle
recently
you've
been
absolutely
fantastic.
I
live
in
london
and
I've
just
graduated
from
the
university
of
oxford.
I've
read:
philosophy:
politics,
economics,
ppe,
so
my
background
isn't
really
in
coding
or
computer
science
per
se,
but
I've
sort
of
taught
myself
to
code
from
a
young
age
and
have
made
apps
and
things
like
that.
E
I
have
a
job
at
accenture
in
tech
management,
consulting
that
was
supposed
to
start
in
september
2020.
But
it's
now
been
moved
to
february.
2021,
there's
a
lot
of
covered,
so
I'm
looking
for
temporary
jobs
at
the
moment,
maybe
pulling
pints
software
development
plenty
of
microsoft,
political
risk,
consultancy
and
parliamentary
researcher
jobs
for
mps.
A
Yes,
well,
that
is
so
impressive.
That
programming
is
not
even
your
main
speciality
and
thanks
again
for
helping
us
so
much
with
the
contributions.
Do
you
mind
telling
us?
How
did
you
start
contributing
to
binform's
repository
and
do
you
contribute
to
other
repositories?
How
all
that
open
source
contribution
adventure
started
for
you.
E
E
Yeah,
so
quite
a
lot
to
dotnet
runtime
as
well.
I've
done
some
low-level
stuff
in
mono's,
mid
gdi
class,
so
that's
the
port
of
gdi
plus
for
linux
and
mac
and
ultra
windows.
I've
done
a
little
bit
of
stuff
with
the
swift,
open
source
framework
that
is
actually
not
obviously
not
a
microsoft
one,
but
I
did
a
bit
of
porting
to
pulling
swifter
windows.
I
was
involved
in
that
effort.
A
Wow
very
nice.
Well,
thank
you!
So
much
for
your
contributions
and
another
open
source
contributor
that
we
already
had
a
chance
to
briefly
talk
to
is
tobias
cass
and
about
this
person
say
that
he
reads
binary
code
and
recompile
windows
and
comb
in
his
head,
and
he
also
has
a
hash
table
in
his
head
and
able
to
retrieve
a
link
to
github
conversation
in
one.
A
A
D
A
F
F
Well,
well,
when
the
ui
frameworks
were
announced
for
open
sourcing,
I
was
most
interested
in
wpf
because
it
had
a
lot
of
close
source
parts.
A
lot
of
source
code
was
already
available
as
reference
source,
so
I
already
started
a
lot,
but
because
wpf
got
started
really
slow.
I
turned
up
two
winches
and
started
commenting
on
pull
requests
and
issues
mostly
when,
when
it
was
about
complicated
interop
or
com
scenarios,
where
I
could
share
my
knowledge.
A
F
Learning
wpf
is
really
hard.
I
think.
Back
in
the
day,
there
were
a
lot
of
posts
when
visual
studio
was
ported
to
wpf.
So
there
are
many
interesting
things
to
learn
from
it,
and
I
also
studied
what
microsoft
did
with
visual
studio
to
port
it
to
wpf.
There
are
a
lot
of
things
to
learn
from
it.
It
took
me
about
two
years
to
learn
wpf
in
details
to
know
to
know
everything
how
it
works
in
in
in
its
implementation.
A
F
F
A
B
There's
obviously
reason
why
we
have
you
know
both
technologies.
All
right,
winforms
is
is
is
easy
to
start
with,
like
the
learning
curve
is
significantly
simpler
right
you,
you
have
that
drag
and
drop
experience
like
you
just
you
know
a
few
buttons
on
your
phone
and
f5
and
and
then
you
have
your
little
app,
whereas
with
the
wpf
the
significantly
a
steeper
learning
curve,
because
you
need
to
learn
the
intricacies
of
xaml,
the
binding,
the
mvpm
or
whatever
that
model
they
use
behind.
B
So
it's
technically
more
complicated
to
create
a
layout,
but
there
are
benefits
at
least
calmly
to
say
use
wpf
if
you
want
to
have
custom
rendering,
if
you
want
to
have
custom,
styling
and
stuff,
the
wind
forms
catching
up
in
that
direction,
we're
not
going
to
go
zaml
away,
but
we're
hoping
to
provide
some
features
which
which
allow
you
to
easily
well
helping
easily
to
to
apply
styling
and
we
improving
in
the
rendering
department.
So
if
you
watch
the
previous
community.
B
F
I
agree
mostly
wind
fast
is
great
for
modular
composition
of
existing
controls,
but
not
so
great
for
writing
your
own.
It's
a
lot
of
work,
but
the
design
experience
is
really
great
compared
to
wpf,
where
you
have
a
complete
control
over
everything,
and
if
you
want
to
build
an
integrated
experience,
it's
it's
much
better
than
in
wind
forms.
F
If
you
want
to
replace
the
complete
ui
style
in
our
applications,
we
actually
use
both
wind
forms
for
composing,
modular
phones,
and
if
we
need
a
complete
control,
we
use
wpf
to
build
a
special
experience,
for
example,
product
planning,
a
calendar
control
or
something
like
that
is
way
too
complicated
to
build
in
wind
forms,
because
you
have
to
write
code
for
everything
and
wpf.
You
can
just
use
more
appropriate
abstractions.
A
E
Yeah
I'd
say
so
it's
it's
faster
than
ever.
It's
it's
more
easy
to
use
than
ever.
I
think
I'm
not
following
as
much
the
working
designer
in
terms
of.net
core,
but
I'm
sure
that's
you
know
that's
getting
that
to
the
point
where
it's
feature
equivalent
and
probably
even
better
so
I'd
say
so
I
would
agree.
A
Yeah,
absolutely,
I
would
also
agree,
and
we
are
as
a
team
investing
in
winforms.
We
continue
our
work
on
it,
so
that
is
definitely
the
platform
that
has
future
it
will
be
carried
2.5.6
and
so
on,
and
we
are
working
on
the
designer
4.net
5
right
now
it
will
be
at
functional
parity
and
it
will
have
even
better
performance.
We
have
jeremy,
a
developer
on
our
informs
team
who
and
dustin
these
guys
made
significant
improvements
into
performance
and
memory
allocations
and
in
the
previous
episode
you
could
hear
more.
A
E
You
know
the
fact
you
guys
are
taking
all
these
contributions
that
have
additional
risks
associated
with
it
like
something
like
cleanups
cause,
those
bugs
down
the
line
shows
that
you're
actually
invested
in
the
sort
of
long-term
future
of
the
product
itself.
So
that's
that's
so
that
you
can
see
as
well.
B
Well,
did
you
know
that
winforms,
despite
the
channel
community
feeling,
is
still
the
biggest
desktop
workload
in
visual
studio
like
we,
we
more
use
than
wpf
or
uwp,
and
whatever
else
like,
so
we
there
is
a.
There
is
a
big
future
yeah
in
winforms,
because
there
is
a
lot
of
investment,
we're
not
deprecating,
and
we
only
want
to
make
it
better.
A
Yeah
perfect.
Thank
you.
There
was
a
question
about
winforms
ecb
host
on
azure
and
yeah.
As
your
scenarios
are
the
scenarios
we're
thinking
about.
Please
give
us
more
feedback,
let's
file
feature
requests
and
describe
what
exactly
you're
missing
how
you
would
like
experience
to
be
that
is
super
valuable
to
us
and
that's
how
we
prioritize
our
work
and
build
our
roadmap
and.
A
Does
the
functional
parity
in
the
designer
4.5
mean
that
devexpress
controls
and
designer
windows
will
work
in
the
vin
forms
designer?
We
are
working
with
third-party
controls,
such
as
devexpress
tulare,
grapecity
infrastic,
and
we
are
helping
them
to
enable
all
their
controls
for
dotnet,
five
and
future.
So,
ideally,
you
will
have
all
the
control
vendors
support,
supporting
new
informs
platforms.
A
A
E
The
windows
flat
from
using
windfalls
and
in
terms
of
my
experience
as
a
remote
worker
or
member,
I
think
I've
sort
of
felt
as
if
I'm
a
microsoft
employee.
Most
of
the
time
I
mean
I'm
looked
into
the
conversations
and
what
the
pr's
are
reviewed
quite
thoroughly
and
honestly
with
lots
of
different
members
contributing.
So
it's
it's
really
fun
to
be
linked
in
so
I've
had
a
very
positive
experience.
E
A
Perfect-
and
I
have
one
more
question,
so
I
will
be
alternating
between
our
open
source,
talk
and
answering
the
questions
in
the
chat.
So
right
now
we
have
in
in
visual
studio
the
templates
default
to
dotnet
core
31
when
you
create
a
new
winforms
project.
Is
this
by
design
any
plans
to
set
default
2.05?
A
Yes,
this
is
by
design
and
it
will
be
set
to
dotnet
5
once
the
full
version
of
net
5
will
be
released,
which
will
happen
in
november
right
now.
The
net
5
is
still
in
the
preview
and
we
don't
set
the
default
experience
to
preview
version,
but
once
we
move
to
the
net
5,
that
would
be
the
default.
Thank
you
for
the
question
and
yeah
tobias.
A
F
A
F
A
Yeah
that
sorry,
that
is
the
most
optimal
way
for
us,
because
with
that
we
also
get
some
telemetry,
regarding
which
version
of
the
designer
you
are
using,
etc,
but
you
also
can
reach
us
out
on
the
github
repository
via
twitter.
Whichever
channels
you
prefer
a
visual
studio
feedback
channel
is
the
easiest
way
for
the
team
to
process
your
feedback,
so
that
is
our
preferred
way.
Iger
did
you
want
to
say
something.
B
Well,
I
was
pretty
much
wanted
to
say
the
same
and
just
to
mention
that
we
take
vs
feedback
seriously
as
well
as
github.
I
know
a
few
members
of
the
community
had
an
impression
that
submitting
bs
feedback
goes
nowhere
for
our
specific
team.
It's
not
the
case.
We
do
take
ideas,
feedback
seriously.
It
gets
sprouted
to
the
team,
they
review
it
and
they
prioritize
it.
That
may
not
be
the
case
for
some
other
repository
so
for
windows
in
general,
as
a
feedback
for,
but
for
the
designer
we
prioritize
triage
all
the
issues.
B
A
Yeah
absolutely
and
we
as
a
winforms
team,
are
doing
our
best
to
enable
the
full
experience
for
the
designer
as
soon
as
we
can.
That
was
a
lot
of
work
for
us
because
we
had
to
make
it
to
build
it
on
the
completely
different
approach
and
architecture,
but
we're
getting
there
it's
already
much
much
better
than
it
was
before,
and
we're
finalizing
the
editing
missing
pieces,
pieces,
etc.
A
E
I'd
probably
start
by
by
looking
at
some
project
priorities,
I
guess
sort
of
what
what
what
what's
the
work
that's
going
on
in
the
project.
What
are
they,
what
are
people
prioritizing
so
a
way
to
do
that
is
look
at
the
open,
pr's
and
issues
to
figure
out
what
are
the
people
working
on?
I
guess,
and
how
can
I
help
out
on
that?
So
I
mean
obviously
the
classics
as
well:
you've
got
the
labels
up
for
grabs,
easy
needs
code
coverage,
there's
one
for
like
needs
testing
as
well.
E
So
that's
a
very
good
way
to
sort
of
get
yourself
to
understand.
What's
going
in
the
project
and
then
therefore
you
can
understand
how
to
contribute
to
things.
I
think
also
remember
contributing
isn't
just
as
we
said
earlier,
isn't
just
prs,
although
you
know
I
I
tend
to
accomplish
most
of
my
prs.
I
mean
the
beer
has
submitted
many
great
issues
and
not
just
issues
but
analysis
on
issues.
E
E
I
mean
this
is
something
I
aired
on
when
I
started
contributing,
I
submitted
sort
of
big
pr's.
I
had
thousands
of
lines
of
changes
and
if
I
split
them
up
a
bit
more
then
maybe
it
would
even
be
easier
for
eagle
to
review
them,
so
try
to
split
things
into
different
commits
if
you
can't
do
that
within
the
sort
of
if
everything
is
in
the
same
pl,
definitely
split
it
up
into
commit
and
then
finally,
as
we
said
earlier
as
well
add
tests,
it
can
be
a
bit
hard
to
do
that.
E
I
mean
in
complex
sort
of
ui
scenarios
or
activex
and
only
interrupt
or
own
air
interrupt
and
office
in
drop,
but
I
mean
there's
been
some
good
movements
there.
So
I
know
jeremy
has
created
this
sort
of
emf:
validator
that
can
validate
user
interfaces.
So
that's
also
quite
a
good
sort
of
you
know
we're
developing
the
testing
frameworks
to
help
you
out
there.
F
E
B
B
B
A
And
they
have
a
command
contribution
was
a
great
experience
for
me.
No
improvement
come
to
mind.
Thank
you
so
much
we're
very
happy
to
hear
that,
and
we
want
to
thank
you
for
your
contribution.
We
really
appreciate
your
help
and
there
was
a
question
about
design
patterns
for
winforms,
so
in
wpf
the
mvvm
is
the
most
used
pattern,
which
pattern
do
you
recommend
for
vinforms
apps?
A
A
A
Questions
if
there
are
no
more
questions,
then
I
want
to
thank
everybody
for
joining
us
today.
You
can
always
find
us
on
twitter.
My
handle
is
olia.
Goverish
igor
is
ruski.
You
can
post
your
twitter
handle
in
the
chat
either,
and
I
want
to
thank
our
contributors
as
well.
Thank
you
for
joining
us
at
your
late
night
and
vigor
joined
us
in
the
middle
of
the
night.
I
believe
it's
3
a.m.
For
you
right
now,
right
yeah.