"No Vendor Lockin" and The drupalshop ecosystem
Submitted by liorkesos on June 29, 2009 - 17:39
Your session in a few words:
The dynamics of projects migrating between drupal shops, practical examples of the "no vendor lock-in" requiement.
Date:
July 1, 2011 - 01:39
Track:
Business development and strategy
Session Type:
Panel
Level of expertise:
Beginner
Language:
English One of the most appealing things to customers about open-source at large and drupal in particular is the "no vender lockin" argument.
This is thrown around by us as a drupal shop very often but I'd like to brainstorm and share "war stories" about how drupal projects "move" and change hands throughout the "drupalshop ecosystem" and why they move that way.
I think it's crucial to communicate how by applying best practices we can truly liberate our customers and give true substance to the "No vendor Lockin" cliche.
True choice happens when the customer can easily switch drupal vendors with a very low overhead or customers can take on huge projects cutting them in to pieces and working with several drupal shops to implement them.
I will try to invite additional drupal shop owners/project managers and talk a bit about.
- Experiences regarding incoming and outgoing projects
- How using drupal best practices enables true liberation to the client and why the client has to absolutly require it when he hires a drupal shop
- Cooperation examples - projects taken by several shops
- What modules or development patterns can help enforce best practices and cooperation (features, patterns etc..)
- Questions, Stories, moral support and group hugs
Co presenters:
