[TYPO3-ect] Official voting for Extension Award 2005

[Oliver Klee]

Hi,

sorry that it took me longer than expected to come up with a vote. I
want to contribute a vote that is more than just a gut feeling.

After the (short) vote, I'll mention my voting criteria. I'll post my
thoughts for the single extensions in the corresponding threads.

Elmar Hinz schrieb:
> ================================================================================
> Ballot
> ================================================================================
> 
> Distribute 5 votes for "Alltimestars" (max. 3 votes per extension):
> 
> [0] chc_forum: CHC Forum proposed by Michelle Heizer
> [3] cron_cssstyledimgtext: CSS styled IMGTEXT proposed by Hauke Haller
> [2] rtehtmlarea: htmlArea RTE proposed by by Ernesto Bashny
> 
> 
> Distribute 5 votes for "Newcomers" (max. 3 votes per extension):
> 
> [2] dam: Media (DAM) proposed by by Stefan Geith
> [2] timtab: TIMTAB Weblog proposed by Thomas Hempel
> [1] timtaw: TimTaw proposed by Frank Holzinger

Things I looked for in the extensions:
- Warnings in the EM: Most warnings can and should be avoided so that
the warning can fulfill their function of pointing to possible problems.
- Coding style: This influences how easy it is to read, understand and
modify the code, thus making it easy or hard for other developers to
help out. In addition, this makes avoiding, finding and fixing bugs easier.
  - readability of code
  - clear, complete and correct PhpDoc comments
  - comments when code is hard to understand
  - short methods (not longer than 2 screen pages)
  - GPL and copyright boilerplates at the top of each file
  - following the Typo3 coding guidelines
  - clear, easy-to-understand function and variable names, no
abbreviations or acronyms (and common sense is used for exceptions)
  - no commented-out code
- use of templates, no hard-coded HTML
- setup and constants are in static/ so that they are included only when
needed
- valid XHTML
- accessibility
- does the extension run mostly "out of the box"?
- does it integrate well into the concepts of Typo3?
- does it help in making the web a better place (help with
accessibility, web standards, slim/semantic code, vendor-independent
software)
- Is the manual easy to understand and helpful? Does it have meaningful
screenshots and examples? Are there no stubs from the manual example?
- If it add fields to tt_content, does it have a really really good
reason to do so?

Regards,


Oliver