Stuff that bugs:
This is all the stuff that was written down on the postit notes when you were asked what bugged you most about taking over Drupal installs from other coders
- Usage of wrong tools(module) to solve a problem
- No source control (cvs / svn / git)
- CORE HACKS
- Contrib module hacks
- Huge "do every thing" custom modules
- Output generation that isn't wrapped in theme functions or has been placed in tpl files
- Bad design implementation
- No comments
- Drupal standards (code) has not been followed
- Crappy theming mess up things when turning on new modules or upgrading
- Only use stable or tested modules
- Wierd function names
- Stuff has been put in the wrong places
- Undocumented hacks
- Magic code
- Devel.module in production sites
- Business logic in theming layer
- *-dev versions of modules
- Core CSS overwrites CAOS!
- One million installed modules where only a few is used
- Use of DEAD contrib modules
- Missing documentation
- Functionality in the theming layer
- Incompatible modules
- Immature modules
- Hacked blocks in user.module - Hacks in core
The proposed categories for the check-list
To get the check-list organized into some categories, everyone wrote down a bunch on postit notes
- Project specification
- Documentation
- Guidelines / Best Pratice
- Quality Assurance
- Meetings
- Interface (ex. editors)
- Compliance
- Minimum modules (ex. cck, views)
- Theming
- Design
- Design pattern
- Contributing to the Drupal community
- Development methods
- Hosting
- Install profiles
- Simplicity
- Requirements
- Publishing and peer-Reviews of custom modules
- Code quality measurement
- Support
- Drupal customizations
- Connection / Support by the open source community
- Maintainability