X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fhelpwanted.html;h=5e05e65f40b67a1418871eae69dbc31717055a8f;hb=a463b2c2ed452f1ee1497fbc19921c910de93237;hp=4cd92b97a95225a53cbde798200361f77c7cd974;hpb=a3ee0aa1bb7c3f9dfc5b13b4e72522c10a22ad05;p=mesa.git diff --git a/docs/helpwanted.html b/docs/helpwanted.html index 4cd92b97a95..5e05e65f40b 100644 --- a/docs/helpwanted.html +++ b/docs/helpwanted.html @@ -1,12 +1,20 @@ - + + + + + Help Wanted + + + -Help Wanted +
+ The Mesa 3D Graphics Library +
- + +
- - -

Help Wanted / To-Do List

+

Help Wanted

We can always use more help with the Mesa project. @@ -15,30 +23,60 @@ Here are some specific ideas and areas where help would be appreciated:

  1. -Enable -Wstrict-aliasing=2 -fstrict-aliasing and track down aliasing -issues in the code. +Driver patching and testing. +Patches are often posted to the mesa-dev mailing list, but aren't +immediately checked into git because not enough people are testing them. +Just applying patches, testing and reporting back is helpful. +
  2. +Driver debugging. +There are plenty of open bugs in the bug database.
  3. -Windows 98/NT driver building, maintenance and testing +Remove aliasing warnings. +Enable gcc's -Wstrict-aliasing=2 -fstrict-aliasing arguments, and +track down aliasing issues in the code.
  4. -Maintenance and testing of lesser-used drivers, such as DOS/DJGPP, GGI, etc. +Contribute more tests to +Piglit.
+

+You can find some further To-do lists here: +

+ +

+Common To-Do lists: +

+

-If you want to help with Mesa, first join the Mesa developer's +Legacy Driver specific To-Do lists: +

+ + +

+If you want to do something new in Mesa, first join the Mesa developer's mailing list. Then post a message to propose what you want to do, just to make sure there's no issues.

-

+

Anyone is welcome to contribute code to the Mesa project. By doing so, it's assumed that you agree to the code's licensing terms.

Finally: -

+

  1. Try to write high-quality code that follows the existing style. @@ -46,6 +84,6 @@ Finally:
  2. Test your code thoroughly. Include test programs if appropriate.
- - - +
+ +