[consulting] first post - offer of some regular part-time work

[Marty Landman]

Yeah I agree - on both counts.

At 11:45 AM 1/28/2015, Bill Fitzgerald wrote:
>Please take this off list.
>
>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.
>
>That's an avoidable process issue waiting to explode.
>
>Cheers,
>
>Bill
>
>On Wed, Jan 28, 2015 at 8:40 AM, Mulindwa 
><<mailto:dmulindwa at gmail.com>dmulindwa at gmail.com> wrote:
>
>Am available and interested
>On Jan 28, 2015 1:22 AM, "jsf" 
><<mailto:jfreeman at gmail.com>jfreeman at gmail.com> wrote:
>Greetings Drupal Consultants list members:
>
>
>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:
>
>A NY-based interactive studio is seeking a 
>self-starting, responsible, Drupal developer to undertake the following tasks:
>
>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.
>
>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!)
>
>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.
>
>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. Â
>
>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.
>
>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.
>
>Thanks in advance!
>
>Joshua
>(jfreeman at gmail dot com)
>
>
>--
>
><http://www.joshuasfreeman.me>http://www.joshuasfreeman.me
>
>_______________________________________________
>consulting mailing list
><mailto:consulting at drupal.org>consulting at drupal.org
>https://lists.drupal.org/mailman/listinfo/consulting
>
>
>_______________________________________________
>consulting mailing list
><mailto:consulting at drupal.org>consulting at drupal.org
>https://lists.drupal.org/mailman/listinfo/consulting
>
>
>_______________________________________________
>consulting mailing list
>consulting at drupal.org
>https://lists.drupal.org/mailman/listinfo/consulting