Would also like to contribute to Wine

[Reece Dunn]

I am interested in the Wine project, and my manager at work has
accepted my request to work on it.

I work for a company that develops Windows software, so as I have
access to Visual Studio, and thus the sources for ATL, MFC and the
msvc runtime (provided with the full version of Visual Studio), I
state that I will not participate in the development of these
components.

I have not seen, and do not intend on seeing, any of the Windows source code.

I am interested in the following.

1. Writing tests for various parts of Wine, initially the RECT API. I
know that this is a simple API, but even the simplest API needs tests.
I will expand on this set as time permits. Is it possible for me to
write tests for ATL and/or the msvc runtime, as this is not
implementing those API?

2. Investigating the failing tests (e.g. the new, unknown message in
the monthcal tests on Vista) and how to fix them properly.

3. Improve the user32/comctl32 controls. I would like to address the
outstanding issues with these if I can.

4. Microsoft Active Accessibility (MSAA)/User Interface Automation
(UIA). I would like to get this working with the various Linux
accessibility API, so that more people will have access to Windows
applications running on Linux+Wine.

5. Microsoft Text-To-Speech API (part of the sapi DLL). This is on my
wishlist and is likely beyond my capabilities to get working. It is
used by applications like Dragon Naturally Speaking and Cepstral
SwiftTalker. Here, there is supporting voices installed on Windows
that use the SAPI interface directly, and voices installed on Linux
that implement different APIs.

6. Get theming working with the user32 controls and Window frames. Get
the theming support working with GNOME themes as well.

7. Anything else I can think of.

I would be interested in improving Wine to help get more applications
running on Wine. Does anyone know if there are some common things that
are holding Wine up, or is it more a per-application problem as each
application is hitting different problems in Wine?

- Reece

[Tomas Carnecky]

Reece Dunn wrote:
> I am interested in the Wine project, and my manager at work has
> accepted my request to work on it.
>
> I work for a company that develops Windows software, so as I have
> access to Visual Studio, and thus the sources for ATL, MFC and the
> msvc runtime (provided with the full version of Visual Studio), I
> state that I will not participate in the development of these
> components.

IIRC Alexander Julliard (the chef here) said that people who've seen any
sources from Microsoft can't contribute to wine.

tom

[Michael Stefaniuc]

Tomas Carnecky wrote:
> Reece Dunn wrote:
> > I am interested in the Wine project, and my manager at work has
> > accepted my request to work on it.
> >
> > I work for a company that develops Windows software, so as I have
> > access to Visual Studio, and thus the sources for ATL, MFC and the
> > msvc runtime (provided with the full version of Visual Studio), I
> > state that I will not participate in the development of these
> > components.
>
> IIRC Alexander Julliard (the chef here) said that people who've seen any
> sources from Microsoft can't contribute to wine.
> That referred to the stolen ones or those you can look at when you sign
> a NDA. ATL, MFC and msvc are different; you just cannot work on those
> DLLs in Wine.

bye
	michael
-- 
Michael Stefaniuc               Tel.: [phone]
Sr. Network Engineer            Fax.: [phone]
--------------------------------------------------------------------
Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart
Handelsregister: Amtsgericht Stuttgart HRB 153243
Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham,
                 Werner Knoblich

[John Klehm]

Are the rules for contributing anywhere on the website?  I can't seem
to find them, if they aren't maybe they should be?  This seems like a
prime topic for the FAQ.  I'd write it myself but I don't know exactly
what all the different rules are.

Regards,
John

On 9/5/07, Michael Stefaniuc <mstefani(a)redhat.com> wrote:
> Tomas Carnecky wrote:
> > Reece Dunn wrote:
> > > I am interested in the Wine project, and my manager at work has
> > > accepted my request to work on it.
> > >
> > > I work for a company that develops Windows software, so as I have
> > > access to Visual Studio, and thus the sources for ATL, MFC and the
> > > msvc runtime (provided with the full version of Visual Studio), I
> > > state that I will not participate in the development of these
> > > components.
> >
> > IIRC Alexander Julliard (the chef here) said that people who've seen any
> > sources from Microsoft can't contribute to wine.
> > That referred to the stolen ones or those you can look at when you sign
> > a NDA. ATL, MFC and msvc are different; you just cannot work on those
> > DLLs in Wine.
>
> bye
>         michael
> --
> Michael Stefaniuc               Tel.: [phone]
> Sr. Network Engineer            Fax.: [phone]
> --------------------------------------------------------------------
> Reg. Adresse: Red Hat GmbH, Hauptstätter Strasse 58, 70178 Stuttgart
> Handelsregister: Amtsgericht Stuttgart HRB 153243
> Geschäftsführer: Brendan Lane, Charlie Peters, Michael Cunningham,
>                  Werner Knoblich

[Juan Lang]

On 9/5/07, John Klehm <xixsimplicityxix(a)gmail.com> wrote:
> Are the rules for contributing anywhere on the website?  I can't seem
> to find them, if they aren't maybe they should be?  This seems like a
> prime topic for the FAQ.  I'd write it myself but I don't know exactly
> what all the different rules are.

No, but you're right, that would be a great topic for the FAQ.  It's a
wiki - why don't you start editing it with what's been on this list
lately?  No contributions from anyone that's looked at Windows source
code, whether stolen, under NDA, or disassembled.  No contributions to
ATL or msvcrt (or MFC, if we ever implement one) from anyone that's
seen their sources.  I think that about covers "the rules" as I know
them, and turning that into FAQ form would be helpful!

Thanks,
--Juan

[John Klehm]

> No, but you're right, that would be a great topic for the FAQ.  It's a
> wiki - why don't you start editing it with what's been on this list
> lately?  No contributions from anyone that's looked at Windows source
> code, whether stolen, under NDA, or disassembled.  No contributions to
> ATL or msvcrt (or MFC, if we ever implement one) from anyone that's
> seen their sources.  I think that about covers "the rules" as I know
> them, and turning that into FAQ form would be helpful!
>
> Thanks,
> --Juan

FAQ entry for your review:

http://wiki.winehq.org/FAQ#head-9564014242a1a22b24e775dbd00ed66f7f32d372

John

[Juan Lang]

> FAQ entry for your review:
>
> http://wiki.winehq.org/FAQ#head-9564014242a1a22b24e775dbd00ed66f7f32d372

Looks good to me!  Thanks John,
--Juan