There are several way to join this exciting porting project. In the current state we need developers, who will write the basic classes.

How you can help:

• you can start with finding a target in the page, checking out the source and start hacking (please let us know, if you have taken a task) or
• simply look into the sourcecode and try to fix any remaining stuff or
• if you have visual c++ and assembler code experience you can install the Qt 3 evalution release from Trolltech and help the developers in case they have problems in understanding the Qt internals.
• you can watch the mailing lists for porting problems and do some knowledge research or design concepts for the specific topic or
• you can donate money, which covers some of the costs involved in developing the Qt port. See the donation page for further informations.
• .... if you have other impressive ideas, how to help, let us know.

In any case you can contact us on the mailing list. It is only a simple mail far away.

Patch submits

If you have patches, send it to the mailing list. When sending patches, following the rules below makes it easier for us to put them into the cvs.

• prefix a [PATCH] in the subject line of your mail, so that we can differ patches from the other mails.
• add a ChangeLog entry for the patch (a function related short description about the changes)
  For example:

  some cleanup
  xyz(): added handling ...
  class abc: bug fix ...
  
  

  See GNU ChangeLog Standards for a detailed format specification)
• Indent the files you have changed with astyle -slP --convert-tabs to avoid unwanted patch output. You can get astyle from http://astyle.sourceforge.net/.
• create the patch in the unidiff format with function names based on the Qt source root directory. See an example:

  cd /c/src/qt3-win32
  cvs diff -up src/kernel/qapplication.cpp > /tmp/patchxyz.patch
  

• pack bigger patches with bzip2 and attach this file to the email.

Thanks for your efforts.

Happy hacking.