<div dir="ltr"><div><div><div><div>Please take this off list.<br><br></div>And please also be wary of any arrangement where QA is the sole responsibility of the dev (ie, with no client review and signoff on changes) yet the dev has to "make things right" at their own expense if the client identifies an issue post rollout.<br><br></div>That's an avoidable process issue waiting to explode.<br><br></div>Cheers,<br><br></div>Bill<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 28, 2015 at 8:40 AM, Mulindwa <span dir="ltr"><<a href="mailto:dmulindwa@gmail.com" target="_blank">dmulindwa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Am available and interested</p>
<div class="gmail_quote"><div><div class="h5">On Jan 28, 2015 1:22 AM, "jsf" <<a href="mailto:jfreeman@gmail.com" target="_blank">jfreeman@gmail.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Greetings Drupal Consultants list members:<br><br><br>If you are very comfortable installing, monitoring and maintaining Drupal 7 websites and interested in taking on some part-time/occasional hourly work please read on:<br><br>A NY-based interactive studio is seeking a self-starting, responsible, Drupal developer to undertake the following tasks:<br><br>1) Agree to receive and read automated emails regarding updates to Drupal core and Drupal modules for 2 Drupal 7 sites belonging to one of our client.<br><br>2) Block 1 - 3 hours every other week (possibly every week... not sure yet) to complete non-emergency/non-critical Drupal core and module updates in strict accordance with well-established Drupal best-practices (which we will, of course review with you prior to awarding you this job!)<br><br>3) Proactively coordinate with us, so we may coordinate with our client, any updates to Drupal core or Drupal modules that are critical/emergency and must take place as soon as possible, assuming a scheduled bi-weekly update window is not hours away.<br><br>4) Agree to be responsible and accountable for your work. Both of these sites have staging and production versions. It is expected that you will first make the updates/upgrades to the staging sites and test your work. If you run into problems, you’ll back the changes out and we can discuss what to do next before you do more work. If everything goes smoothly on the staging sites, you will proceed to make the upgrades/updates to the production sites. Again, you will test your work. If there are problems, you will revert to the pre-upgrade/update version of the site and contact us to discuss what to do next. <div><br></div><div>5) If you really wind up breaking something, you are responsible, on your dime, to at least put things back to the way they were before you began working.<br><br>If you are interested in taking on this work, please let me know. Send me your contact information, resume, some links to your work, 3 references and a desired hourly rate.<br><br>Thanks in advance!<br><br>Joshua</div><div>(jfreeman at gmail dot com)<br><br><br>--<br><br><a href="http://www.joshuasfreeman.me" target="_blank">http://www.joshuasfreeman.me</a>
</div></div>
<br></div></div><span class="">_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org" target="_blank">consulting@drupal.org</a><br>
<a href="https://lists.drupal.org/mailman/listinfo/consulting" target="_blank">https://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br></span></blockquote></div>
<br>_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="https://lists.drupal.org/mailman/listinfo/consulting" target="_blank">https://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br></blockquote></div><br></div>