[consulting] Structuring Security and Module Update Services

[Sam Cohen]

Then how many hours of work per month do you base your hosting agreement
on?

Sam


2009/3/27 David Hazel <dave at hazelconsulting.com>

> I just include it as part of the hosting agreement.
>
> You could always include the usual caveats about unforeseen conflicts, etc.
> etc.
>
>
> -dave
>
> 2009/3/27 Sam Cohen <sam at samcohen.com>
>
>> Hi all,
>>
>> 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.
>>
>> 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.
>>
>> 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 ?
>>
>> 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.
>>
>> Thanks,
>> Sam
>>
>> _______________________________________________
>> consulting mailing list
>> consulting at drupal.org
>> http://lists.drupal.org/mailman/listinfo/consulting
>>
>>
>
>
> --
> Email is not a secure form of communication!
>
> Technologist
> http://www.hazelconsulting.com/
> 253.686.0296
> dave at hazelconsulting.com
> skype: hazelconsulting
> gtalk:kananii
> ICQ: 366587185
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.drupal.org/pipermail/consulting/attachments/20090327/5408a28d/attachment.htm>