Attn: component owners list

[Andriy Palamarchuk]

Please, take a minute to review the list of component
owners and give me a feedback privately or throught
the mailing list.

We need to define component owners to assign bugs to.
These people do not necessarily have to fix the bugs
forwarded to them, but will have more detailed
knowlege about the status of the component, overview
progress in bugs fixing.

The component owners will receive bugs after they will
be processed by the first line of bugs handling,
confirmed, probably already researched, with detailed
information. Goal of the whole process is to reduce
load on you more experienced developers. You won't
have to tell "update your Wine distribution" in 100'th
time. A few contributors are already doing this for
you ;-)

So far only a few people took ownership over separate
components:
* Guy L. Albetelli - common controls
* Dustin Navea - wine tools
* Andriy Palamarchuk - wine applications

List of candidates:
* Alexandre Julliard - wineserver, kernel, IPC
* Andreas Mohr - documentation, X11 driver
* Dimitrie O. Paun - GUI
* Laurent Pinchart - copy protection
* Hidenori TAKESHIMA - quartz, DirectShow (is the
scope too narrow?), DirectX (?)
* Dmitry Timoshkov - NLS, Unicode, keyboard I/O
* Francois Gouget - COM, OLE
* Martin Wick - sockets
* Huw Davies - TrueType support, printing

Available components:
* DOS support
* multimedia
* console
* files
* gdi
* loader
* net

Let me know what you would like to work on, if you
agree or not agree to own the component, change scope,
know good candidates.

I don't want to send bug reports to "black hole",
assigning them to a person which is not going to work
on them.

Look forward for your responses.
Andriy Palamarchuk

__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!
http://shopping.yahoo.com

[Shachar]

I was about to reply to your previous mail on this matter, suggesting 
myself as the component owner for BiDi. The reason I didn't do it was 
because I promised IBM, who have actually made some progress on the 
matter, I would wait a while longer for a decision to come whether they 
are able to relase their WINE BiDi support. This "while" is not over yet.

If they manage to relese their code, I think it is best someone from 
there take ownership of these things (of course, I would love to do so, 
but as I am doing this *off* hours, and they are doing it *on* hours, 
plus they have the code to back it up, I think it only makes sense. 
Don't want to take credit where it's not due).

If IBM come back with a negative answer, or don't come back with an 
answer at all within a reasonable time, I will start working on things 
myself. I would apretiate help from anyone who wishes to offer it, 
especially if they can read and write Arabic (it's been a long long 
while since I last tried, and I could never get the vocabulary).

If you are looking for an immediate scape-goat, use "winebugzilla at sun 
consumer org il"  as my email. This is a complicated anti-spam riddle 
that you are expected to solve in order to get to the real email used 
here. Say no more and live longer ;-).

Shachar

Andriy Palamarchuk wrote:
> Please, take a minute to review the list of component
> owners and give me a feedback privately or throught
> the mailing list.
>
> We need to define component owners to assign bugs to.
> These people do not necessarily have to fix the bugs
> forwarded to them, but will have more detailed
> knowlege about the status of the component, overview
> progress in bugs fixing.
>
> The component owners will receive bugs after they will
> be processed by the first line of bugs handling,
> confirmed, probably already researched, with detailed
> information. Goal of the whole process is to reduce
> load on you more experienced developers. You won't
> have to tell "update your Wine distribution" in 100'th
> time. A few contributors are already doing this for
> you ;-)
>
> So far only a few people took ownership over separate
> components:
> - Guy L. Albetelli - common controls
> - Dustin Navea - wine tools
> - Andriy Palamarchuk - wine applications
>
> List of candidates:
> - Alexandre Julliard - wineserver, kernel, IPC
> - Andreas Mohr - documentation, X11 driver
> - Dimitrie O. Paun - GUI
> - Laurent Pinchart - copy protection
> - Hidenori TAKESHIMA - quartz, DirectShow (is the
>
> scope too narrow?), DirectX (?)
> - Dmitry Timoshkov - NLS, Unicode, keyboard I/O
> - Francois Gouget - COM, OLE
> - Martin Wick - sockets
> - Huw Davies - TrueType support, printing
>
> Available components:
> - DOS support
> - multimedia
> - console
> - files
> - gdi
> - loader
> - net
>
> Let me know what you would like to work on, if you
> agree or not agree to own the component, change scope,
> know good candidates.
>
> I don't want to send bug reports to "black hole",
> assigning them to a person which is not going to work
> on them.
>
> Look forward for your responses.
> Andriy Palamarchuk

[Francois Gouget]

On Thu, 9 May 2002, Andriy Palamarchuk wrote:
[...]
> - Francois Gouget - COM, OLE

Hmm, not COM and not OLE. But you can mark me for Winelib, Winemaker and
general compatibility between Wine headers and Windows headers.
You can also put me on the icmp library (although I did not touch it for
the longest time, but noone else did either, so either I did a good job
or this library is particularly useless ;-)
I may also be coaxed into monitoring msvcrt issues if no-one else
volunteers for it.

Btw, did you check out the WineHQ's Who's Who?
http://www.winehq.com/about/index.php?who

It needs a serious update and contains each developper's 'specialty'
which is pretty much the same as the information you are currently
gathering.

[...]
> I don't want to send bug reports to "black hole",
> assigning them to a person which is not going to work
> on them.

That could be a problem. Free time regularly seems to become negative!

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
      Any sufficiently advanced bug is indistinguishable from a feature.
                            -- from some indian guy

[Andriy Palamarchuk]

Francois, thank you for the feedback.

--- Francois Gouget  wrote:
> On Thu, 9 May 2002, Andriy Palamarchuk wrote:
> [...]
> > - Francois Gouget - COM, OLE
>
> Hmm, not COM and not OLE.

Ok, who wants to handle COM/OLE?
> Btw, did you check out the WineHQ's Who's Who?
> http://www.winehq.com/about/index.php?who
>
> It needs a serious update and contains each
> developper's 'specialty'
> which is pretty much the same as the information you
> are currently
> gathering.

Thanks. I used that source of information too. Agree -
it needs update.
> [...]
> > I don't want to send bug reports to "black hole",
> > assigning them to a person which is not going to
>
> work
> > on them.
>
> That could be a problem. Free time regularly seems
> to become negative!

The real goal of all this noise with Bugzilla to take
easy tasks from core developers and give really hard
ones ;-)

Andriy

__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!
http://shopping.yahoo.com

[Marcus Meissner]

On Thu, May 09, 2002 at 02:22:36PM -0700, Andriy Palamarchuk wrote:
> Francois, thank you for the feedback.
>
> --- Francois Gouget  wrote:
> > On Thu, 9 May 2002, Andriy Palamarchuk wrote:
> > [...]
> > > - Francois Gouget - COM, OLE
> >
> > Hmm, not COM and not OLE.
>
> Ok, who wants to handle COM/OLE?

Well, I volunteer. :)

Ciao, Marcus

[Dimitrie O. Paun]

On May 9, 2002 01:28 pm, Andriy Palamarchuk wrote:
> - Dimitrie O. Paun - GUI

Hey, I think that's a bit too ambitious for the time I have
available... Common controls would have been much better,
but those are taken by Guy now :)

Anyhow, I'll be away for a while, I might sign up when I get back...

[Guy L. Albertelli]

Dimi

I would be very glad of help on common controls. I think "common controls"
is big enough to keep both of us busy. I would recommend that we be
co-owners of this part.

Guy
----- Original Message -----
From: "Dimitrie O. Paun" 
To: "Andriy Palamarchuk" ; "wine-devel"

Sent: Thursday, May 09, 2002 9:55 PM
Subject: Re: Attn: component owners list
> On May 9, 2002 01:28 pm, Andriy Palamarchuk wrote:
> > - Dimitrie O. Paun - GUI
>
> Hey, I think that's a bit too ambitious for the time I have
> available... Common controls would have been much better,
> but those are taken by Guy now :)
>
> Anyhow, I'll be away for a while, I might sign up when I get back...
>
> --
> Dimi.

[Dimitrie O. Paun]

On May 10, 2002 10:21 pm, Guy L. Albertelli wrote:
> Dimi
>
> I would be very glad of help on common controls. I think "common controls"
> is big enough to keep both of us busy. I would recommend that we be
> co-owners of this part.

If we can be co-owners, by all means. I know a few of them very well, and
it only makes sense to split them. As you say, they are quite big,
important (IMO), and they still require a lot of work to get them 100%
functionally complete.

--
Dimi.

[Andriy Palamarchuk]

--- "Dimitrie O. Paun"  wrote:
> On May 10, 2002 10:21 pm, Guy L. Albertelli wrote:
> > Dimi
> >
> > I would be very glad of help on common controls. I
>
> think "common controls"
> > is big enough to keep both of us busy. I would
>
> recommend that we be
> > co-owners of this part.
>
> If we can be co-owners, by all means. I know a few
> of them very well, and
> it only makes sense to split them. As you say, they
> are quite big,
> important (IMO), and they still require a lot of
> work to get them 100%
> functionally complete.

I'm very glad when there are more than one developers
interested in some component. As we know there is tons
of work in any Wine subsystem.

For convenience I prefer to have one person for one
component even in case when this person actually does
less work then others.

Andriy

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

[Dimitrie O. Paun]

On May 13, 2002 01:01 pm, Andriy Palamarchuk wrote:
> For convenience I prefer to have one person for one
> component even in case when this person actually does
> less work then others.

Sure, I understand. Guy can forward stuff to me as he sees fit.

--
Dimi.

[Andriy Palamarchuk]

--- "Dimitrie O. Paun"  wrote:
> On May 13, 2002 01:01 pm, Andriy Palamarchuk wrote:
> > For convenience I prefer to have one person for
>
> one
> > component even in case when this person actually
>
> does
> > less work then others.
>
> Sure, I understand. Guy can forward stuff to me as
> he sees fit.

This is completely up to you guys. The process can be
reverse - you can forward bugs to Guy ;-)

I suggest you to search for bugs, assigned to Guy and
take ones he did not start to work on. These will be
with NEW status. Status becomes ASSIGNED when you
actually accept the bug. It is better to accept a bug
only if you work on it. Otherwise leave it with NEW
status, somebody else can pick it up.
So in each moment of time there will be a few bugs
with status ASSIGNED, assigned to you, a few with
status ASSIGNED assigned to Guy and the rest will be
with status NEW, assigned to Guy.

Andriy

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

[Huw D M Davies]

On Thu, May 09, 2002 at 10:28:38AM -0700, Andriy Palamarchuk wrote:
> - Huw Davies - TrueType support, printing

Works for me.
> Available components:
> - gdi

You can put me down for this too if you like.

Huw.

[admiral coeyman]

List,
    I'd like to be listed under DOS, but I'm not good enough to be in charge of
anything.  Right now, I cannot even get wine to compile.  ( signal 11 on
control.c )  
    God Bless,
    	--Robert 'Admiral' Coeyman

[Andreas Mohr]

On Sat, May 11, 2002 at 01:44:53AM -0400, admiral coeyman wrote:
> List,
>    I'd like to be listed under DOS, but I'm not good enough to be in charge of
> anything.  Right now, I cannot even get wine to compile.  ( signal 11 on
> control.c )

Can you fetch older versions of control.c via CVS until you find one
that doesn't bail out ?
Could you fix the current control.c then in order to make it compile
again for you ?
(create a cvs diff from the working version to the current version to
review changes made in between)

[admiral coeyman]

Andreas Mohr,
> >   I'd like to be listed under DOS, but I'm not good enough to be in charge of
> >
> > anything.  Right now, I cannot even get wine to compile.  ( signal 11 on
> > control.c )
>
> Can you fetch older versions of control.c via CVS until you find one
> that doesn't bail out ?

Signal 11, segfault, is commonly a memory problem.  My system has 128 Megs and
cat /proc/meminfo shows my system ram in excess of 127 million bytes.  128 Megs
is in excess of 131 million bytes.  
    I got it to work by removing the -O2 from the Makefile.  It's the copy of
control.c under the programs directory.  Once I got that one file to compile,
the rest of the source compiled easily.  This system might have problems of its
own.
> Could you fix the current control.c then in order to make it compile
> again for you ?

I'm running ecgs 2.91.66 .  My Glibc is 2.1.3.  It's probably time for an
upgrade.
    God Bless,
    	--Robert 'Admiral' Coeyman

[Russell Howe]

On Sun, 2002-05-12 at 05:42, admiral coeyman wrote:
> Signal 11, segfault, is commonly a memory problem.

[snip]
> I got it to work by removing the -O2 from the Makefile.

Optimisation causes the compiler to use quite a bit more memory, so any
memory errors are likely to trip it up. I'd run memtest on that box if I
were you. You'll probably get sig11's if you try to build the kernel as
well. It *could* be a gcc bug though (which I guess is why it was
suggested you should checkout an older version of the file, to see what
was tripping the bug, if anything). More likely hardware though.

*I* get sig11's when I start X using the mga driver and have no idea why
(it used to work then one day it didn't!). fbdev works just fine, and I
can't seem to trip any errors in the RAM so what it is I have no idea!

[Ove Kaaven]

On 12 May 2002, Russell Howe wrote:
> Optimisation causes the compiler to use quite a bit more memory, so any
> memory errors are likely to trip it up. I'd run memtest on that box if I
> were you. You'll probably get sig11's if you try to build the kernel as
> well. It *could* be a gcc bug though (which I guess is why it was
> suggested you should checkout an older version of the file, to see what
> was tripping the bug, if anything). More likely hardware though.

No, he said he uses egcs 2.91, so it's more likely a gcc bug. Egcs has
many bugs, one or two of which very very often turn up during Wine
development.

[admiral coeyman]

Russell Howe,
> On Sun, 2002-05-12 at 05:42, admiral coeyman wrote:
> >   Signal 11, segfault, is commonly a memory problem.
>
> [snip]
> >   I got it to work by removing the -O2 from the Makefile.
>
> Optimisation causes the compiler to use quite a bit more memory, so any
> memory errors are likely to trip it up. I'd run memtest on that box if I
> were you. You'll probably get sig11's if you try to build the kernel as
> well. It *could* be a gcc bug though (which I guess is why it was
> suggested you should checkout an older version of the file, to see what
> was tripping the bug, if anything). More likely hardware though.

I ran memtest and everything looks good.  I don't recall when I last did a
kernel conpile, but I keep that updated as much as I can.  Maybe it's time to
update egcs.  Hopefully, compiling and installing that will not cause
problems.  This is a slackware 7 system with an updated kernel and networking
programs.
> *I* get sig11's when I start X using the mga driver and have no idea why
> (it used to work then one day it didn't!). fbdev works just fine, and I
> can't seem to trip any errors in the RAM so what it is I have no idea!

There has to have been some kind of a change.  I do notice that the newer
kernels are allocating memory differently.  Most of my ram is devoted to cache
when my system is idle and synced.
    God Bless,
    	--Robert 'Admiral' Coeyman

[Andreas Mohr]

On Sun, May 12, 2002 at 12:42:56AM -0400, admiral coeyman wrote:
> Andreas Mohr,
> > >   I'd like to be listed under DOS, but I'm not good enough to be in charge of
> > >
> > > anything.  Right now, I cannot even get wine to compile.  ( signal 11 on
> > > control.c )
> >
> > Can you fetch older versions of control.c via CVS until you find one
> > that doesn't bail out ?
>
> Signal 11, segfault, is commonly a memory problem.  My system has 128 Megs and
> cat /proc/meminfo shows my system ram in excess of 127 million bytes.  128 Megs
> is in excess of 131 million bytes.

It's NOT.
In fact it's (almost ?) never been a memory problem during Wine development.
> I'm running ecgs 2.91.66 .  My Glibc is 2.1.3.  It's probably time for an
> upgrade.

^^^^^^^
You could say that.

But before please try to fix compile on the 2.91.66 version if you can do that.

Thanks ! :-)

[Francois Gouget]

On Sat, 11 May 2002, admiral coeyman wrote:
> List,
>    I'd like to be listed under DOS, but I'm not good enough to be in charge of
> anything.  Right now, I cannot even get wine to compile.  ( signal 11 on
> control.c )

Could it be a compiler version issue? Which version of gcc are you
using?

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
        War doesn't determine who's right.  War determines who's left.