Login / Status
developer.Resource
Home . Documentation . Document Library . Extension Manuals
Sponsors
hosted by punkt.deTYPO3 and Open Source MagazineAOE Media

1.7. Helping out

For this extension, there are still many unimplemented feature ideas. Help is very welcome! There are several ways in which you can help:

Reporting bugs

If you find any bugs or would like to propose a feature, please create yourself an account at the bug tracker and then report the issue under the product Seminar Manager. Make sure to provide the following data when reporting a bug:

  1. the version of this extension which you're using

  2. the version numbers of TYPO3, PHP and MySQL

  3. what steps need to be taken to reproduce the bug (1. click here, 2. enter this ...)

  4. what you expect to happen

  5. what actually happens instead

Buying some work

Besides the described possibilities, you can also pay the author's time to fix a certain bug, implement a certain feature for you or generally dedicate some time to this extension (there always are small things to do that improve this extension without directly being related to a special feature). The overall development speed depends on funding.

Do-it-yourself

If you want to provide a patch for just a single bug or feature, the simplest way is to e-mail a tested patch to Oliver (see below).

If you want to help with more than one bug or feature, you're very welcome to join the extension development team. Please create yourself an account for the bug tracker.

Before you begin to create some piece of code for this extension, please

  1. Read the development workflow as described above

  2. Get yourself the current files from the SVN repository (always work on the latest version of the files!). If you are working on more than one item, it is highly recommended to have a separate SVN tree for each task so that applying and creating patches is easy.

  3. Maybe it wouldn't be wrong to contact Oliver before working - just for cross-checking.

Then do your work and check the following points:

  1. Make sure your code works on your local installation (test it!).

  2. Create a patch and either attach it to a bug report or send it to a member of the development team for this extension to give it a peer review.

  3. As soon as the review process is finished, we'll take care of integrating your code to the SVN.