I just include it as part of the hosting agreement.<br><br>You could always include the usual caveats about unforeseen conflicts, etc. etc.<br><br><br>-dave<br><br><div class="gmail_quote">2009/3/27 Sam Cohen <span dir="ltr"><<a href="mailto:sam@samcohen.com">sam@samcohen.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all,<br><br>I am now going to be offering all my clients security and module updates as an ongoing service -- I know. I should have done it all along. <br>
<br>I'm curious how others structure this service. Do most of you do it at a regular interval (to cover modules) or just every time there's a new release. <br>
<br>My thought is to offer an option where every time there is a Drupal release I will install it and at that time I will check for any module updates and install those as well. But pricing wise, it's tricky, because what if you run into trouble due to a module upgrade that leads to a conflict. Not to mention, the time you should take for testing ? <br>
<br>It seems like the safest way to offer this service is to just say you will bill hourly for whatever time it takes every time there is a release. Is that how others do it? If not, how much time to you typically charge/take for this. <br>
<br>Thanks,<br><font color="#888888">Sam<br>
</font><br>_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Email is not a secure form of communication!<br><br>Technologist<br><a href="http://www.hazelconsulting.com/">http://www.hazelconsulting.com/</a><br>253.686.0296<br><a href="mailto:dave@hazelconsulting.com">dave@hazelconsulting.com</a><br>
skype: hazelconsulting<br>gtalk:kananii<br>ICQ: 366587185<br>