Re: Re: How are we doing?

----Message d'origine----
> De: Alexandre Julliard <julliard(a)winehq.org>
> A: Detlef Riekenberg <wine.dev(a)web.de>
> Date: Thu, 01 Jun 2006 11:45:10 +0200
> Copie à: wine-devel(a)winehq.com, Mike Hearn <mike(a)plan99.net>
> Sujet: Re: How are we doing?
>
> Detlef Riekenberg <wine.dev(a)web.de> writes:
> > During the Time, things changed and I get confused more and more times
> > about "special Developers" and "other Developers", as well as "special
> > Patches" and "other Patches". 
> > (It's also Possible, that i did not see the big differences before).
>
> There's no such thing as special developer vs. other developer, it's
> more like a linear scale based on trust: the more I trust a developer
> the easiest it is for him to get his patches committed. The only way
> to earn trust points is by submitting consistently good patches.
>
> That doesn't mean you can't get stuff in if you aren't trusted, but it
> means it will require extra scrutiny, which is why it's very important
> at the beginning to send small patches that are easy to review. Once
> you have earned enough trust you can get away with being a bit more
> sloppy (but not too much, or you'll lose trust points again ;-)

It's possible to see on wiki the "trust points" positions  ? :)
And on each WWN, see the variations (seems the famous kde buzz) :)

Anyway, adding an explaining page on wiki for "how to begin as wine developper" may help a lot

Regards,
Raphael

How are we doing?

[Alexandre Julliard]

fenix(a)club-internet.fr writes:
> It's possible to see on wiki the "trust points" positions  ? :)
> And on each WWN, see the variations (seems the famous kde buzz) :)

The commit logs contain the time of the change and the time of the
commit, so you could use that to build a top-10 of the developers with
the best patch-to-commit times ;-)

-- 
Alexandre Julliard
julliard(a)winehq.org

How are we doing?

[Michael Stefaniuc]

Alexandre Julliard wrote:
> fenix(a)club-internet.fr writes:
> > It's possible to see on wiki the "trust points" positions  ? :)
> > And on each WWN, see the variations (seems the famous kde buzz) :)
>
> The commit logs contain the time of the change and the time of the
> commit, so you could use that to build a top-10 of the developers with
> the best patch-to-commit times ;-)
> Wont work quite well as the time of the change can be way older than the
> time the developer submitted his patch.

bye
	michael
-- 
Michael Stefaniuc               Tel.: [phone]
Sr. Network Engineer            Fax.: [phone]
Red Hat GmbH                    Email: mstefani(a)redhat.com
Hauptstaetterstr. 58            http://www.redhat.de/
D-70178 Stuttgart

How are we doing?

[Mike Hearn]

On 6/1/06, Alexandre Julliard <julliard(a)winehq.org> wrote:
> > It's possible to see on wiki the "trust points" positions  ? :)
> > And on each WWN, see the variations (seems the famous kde buzz) :)
>
> The commit logs contain the time of the change and the time of the
> commit, so you could use that to build a top-10 of the developers with
> the best patch-to-commit times ;-)

Heh :) Bear in mind that it depends a lot on the patch and what kind
of work you're doing. Getting some clearly correct typo fixes in for
an obscure DLL is going to be a lot easier even for 'untrusted'
developers than, say, implementing SetThreadPriority which touches the
core of Wine in a sensitive area and is somewhat controversial.

There's no special privilege for CW employees or SoC students, though
we appreciate it may look that way at first glance. I'm a CW employee
on and off (more off than on lately due to university) and I get
patches rejected all the time <chuckle> :)

thanks -mike