wine users - Sep 2011 - I want to contribute code for wine and become a developer.

I am porting wine to MIPS and do some job in winebuild/ntdll/ etc. 
I am using qemu to translate x86 instruction and direct the win32 api call from
the qemu  to wine in MIPS version.

Wine on mips is running now! I want to contribute the modification to wine .
How can I do that?

Sounds like a big job.

You could start by forking wine's github repo, see
http://wiki.winehq.org/GitWine#head-0e6d3133a16d3a26de956c500675e5e623462a9e
checking in your changes to that,
and posting the URL on the wine-devel mailing list,
inviting people to look at your code.

Are all the changes your own, and are you releasing them under
the LGPL?

Administrator at PC-201108231454 /d/open_source
$ git clone git at github.com:yaosihai/wine.git mywine
Cloning into mywine...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

uhm....

On second thought: I see you only recently started (as in, last week).
Maybe it would suffice for you to follow the normal wine developer route,
see http://wiki.winehq.org/Developers

github is really for contributors that have already gotten up to speed
and are making lots of changes (imho).

I am confused by so many link on the pages.
Is there any simple way to contribute the code for wine? 
Wine on MIPS is running very smooth and I have added a lot of code in
NTDLL/winebuild/wingcc . I want to share with you.
Or I just upload the the zipped package ?

On Sat, Sep 3, 2011 at 05:52, yaocong <wineforum-user at winehq.org>
wrote:
> I am confused by so many link on the pages.
> Is there any simple way to contribute the code for wine?
> Wine on MIPS is running very smooth and I have added a lot of code in
NTDLL/winebuild/wingcc . I want to share with you.
I suggest you skim through/read in the following order:
http://wiki.winehq.org/DeveloperFaq
http://wiki.winehq.org/Developers-Hints
Maybe http://wiki.winehq.org/HackingTips
http://wiki.winehq.org/GitWine

and perhaps more importantly http://wiki.winehq.org/SubmittingPatches
> Or I just upload the the zipped package ?
Submitting a big blob is a sure way to get it ignored.

yaocong wrote:
> I am confused by so many link on the pages.
> Is there any simple way to contribute the code for wine? 
> Wine on MIPS is running very smooth and I have added a lot of code in
NTDLL/winebuild/wingcc . I want to share with you.
> Or I just upload the the zipped package ?
You're asking in the wrong place. This is the user's forum. Questions
about submitting patches should be directed to the developer's mailing list.

yaocong wrote:
> I am confused by so many link on the pages.
> Is there any simple way to contribute the code for wine? 
> Wine on MIPS is running very smooth and I have added a lot of code in
NTDLL/winebuild/wingcc . I want to share with you.
> Or I just upload the the zipped package ?

It seems to me that your OS (FA) is already using a modified version of Wine, so
you have to plublish your changes anyway. you can first start with uploading
your patches somewhere, then splitting them by module(winegcc/...) is the first
consequence.

Then they should be in a state like my ARM patches were:
http://source.winehq.org/git/wine.git/commitdiff/171c9a532750566d3c786b4d7c1ab807a1265b5e
http://source.winehq.org/git/wine.git/commitdiff/27fb36b39e611ff470ca970279671e33e087e155