Posted by zorp on May 23, 2009 at 11:00pm
I have put together the first revision based on the discussion we had at the How to buy Drupal workshop at Drupal Camp Copenhagen.
This is a initial list that will need a lot of work until we have complete set of guidelines clients can use to review their choice of Drupal provider.
Contributing to Drupal
In what way(s) are the provider contributing to Drupal and in what ways are you as a client/user willing to contribute work back to the Drupal community
Keywords to be implemented:
- This is best practice - if contrib you would make code better...
- Saftey net
- Ask if provider is open sourcering
- Make sure provider is contributing
- Contribute custom modules, themes
- Keeping the Project alive
- Help on updating modules
- Keeps your site vendor-independant
- Sponsorships
Quality Assurance
- Do your provider do any quality assurance
- Coding style
- Folllowing Drupal guidelines
- Standard for testing
- Testing
- Unit test,
- Stress test
- Coding Style
- Keeps your site vendor-independant
- Coding Conventions
- Don't hack core
- Keep business logic and presentation layer apart
Theming / Design
- Make sure provider has prober Drupal Themers
- Ask about subtheming
- Startout themes -> Zen etc. etc.
- Dynamic theming
- Blocks use
- Pros / cons
- Advice
- Use cases, do your provider do use cases.
- Standard compliance
- Browser compatability
Support / Training
- Do you provide support
- How fast do you provide
- Security updates
- Training
- Bug fixing, what define a bug (reproduceable)
- What level of support do I need?
- How is the availability?
- Security updates?
Hosting
- how is hosting handled
Simplicity
- dont invent a spaceship without documentation
- dont invent a spaceship that is allready inveted