WineHQ

Code-In

Revision as of 19:53, 9 November 2017 by AndreHentschel (talk | contribs) (General makeover)

Wine may join the next Google Code-In, so this page is for collecting potential tasks.

Code: Tasks related to writing or refactoring code

Add one more REG.exe option: Bug 19533 (split this into the single options)

Fix a WineHQ Website/Bugzilla/AppDB bug

====Make ping.exe call the Wine icmp API====a

Documentation/Training: Tasks related to creating/editing documents and helping others learn more

Document the install procedure for Wine on Linux Mint at our download page (see discussion/talk page)

Do a Video about compiling Wine on a Linux machine

Outreach/Research: Tasks related to community management, outreach/marketing or studying problems and recommending solutions

Do an updated slideshow possibly based on one from Dan Kegel

Do a Video about running an Application in Wine

Add a new Application to the AppDB

Add a new Testreport to an existing Application in the AppDB

Make a list of suggestions how Wine could be presented on OpenHatch

Quality Assurance: Tasks related to testing and ensuring code is of high quality

Run winetest on a Linux machine

Wine builds a set of unit tests that check the behavior of a large portion of the Windows API.
You can get it here at the bottom: https://test.winehq.org/data/
You can run it according to:
https://wiki.winehq.org/Conformance_Tests#Running_WineTest_in_Wine

Run winetest on a BSD machine

Wine builds a set of unit tests that check the behavior of a large portion of the Windows API.
You can get it here at the bottom: https://test.winehq.org/data/
You can run it according to:
https://wiki.winehq.org/Conformance_Tests#Running_WineTest_in_Wine

Run winetest on a Mac OS X machine

Wine builds a set of unit tests that check the behavior of a large portion of the Windows API.
You can get it here at the bottom: https://test.winehq.org/data/
You can run it according to:
https://wiki.winehq.org/Conformance_Tests#Running_WineTest_in_Wine

Run winetest on a Windows machine

Wine builds a set of unit tests that check the behavior of a large portion of the Windows API.
You can get it here at the bottom: https://test.winehq.org/data/
You can run it according to:
https://wiki.winehq.org/Conformance_Tests#Running_WineTest_on_Windows

Run a git bisect on a regression on the lower part of https://source.winehq.org/regressions

At WineHQ our regressions are tracked at https://source.winehq.org/regressions
At top are regressions which are already tracked down to a specific commit
and on the bottom there regressions which need a git bisect to track down the commit which caused it.
There are instructions at https://wiki.winehq.org/Regression_Testing on how to do that

Test old Wine bug in current Wine Version

Wine has lots of bug reports which get older and older without receiving an update,
one needs to download that application and test it in the latest version of Wine.
Here you can find bug reports not touched for a year which have a download link:
https://bugs.winehq.org/buglist.cgi?cmdtype=dorem&list_id=542286&namedcmd=1y%20old%20%2B%20download&remaction=run&sharer_id=4672

User Interface: Tasks related to user experience research or user interface design and interaction

none yet

This page was last edited on 9 November 2017, at 19:53.