Joining the project

If you have found program errors, you should file a bug report in the menu on the left.

If you want to get involved in coding, documenting, testing, packing or any other project related task, you are extremely welcome to join PyChess mailing list, pychess-people, which should be the place almost all discussion takes place. All development questions should go there.

Now get a copy of the latest development sources from http://code.google.com/p/pychess/source To get write access to the tracker, send a mail to lobais@gmail.com

How development is usually done

PyChess uses a very open development structure. If you want to hack on a specific task in which you are interested, just let people know, so that they don't start hacking on the same thing, and they have a possibility to talk with you, if they are hacking on things which might interact with your project.

If you don't have any specific idea, just ask if people need help with something, and if there are any tasks more prioritized than other.

Documentation

Documentation is something every project needs, but which few (younger) projects have enough of.

In the svn there is a folder called doc, which contains API documents on the PyChess modules.

If you figure out how an documented piece of code works, feel absolutely free to add a few lines of documentation to help the next person in the same problem as you. :)

If you fail to figure it out, ask in the mailing list.

UML for Greco 0.6

The .dia file can be found in svn