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

[Muzaffer Tolga Ozses]

Isn't this list for consulting ie. some sort of finding contractors?
On 29 Jan 2015 18:14, "David Landry" <david at dmwl.net> wrote:

> Please take this conversation off-list.
>
> —
> David Landry
>
>
> On Thu, Jan 29, 2015 at 11:07 AM, jsf <jfreeman at gmail.com> wrote:
>
>> Hi Tom,
>>
>> You may have sent this already and it's in another thread.. what is your
>> rate?  Can you please send me a few links to look at?
>>
>> Thanks!
>>
>> Joshua
>>
>> On Wed, Jan 28, 2015 at 11:37 AM, Tom Printy <tprinty at gmail.com> wrote:
>>
>>>  Would love to help you put with this. Lease contact MW at 847-235-6267
>>> ext 101 to discuss the details.
>>>
>>> Thanks Tom
>>>  On Jan 27, 2015 4:22 PM, "jsf" <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
>>>>
>>>> _______________________________________________
>>>> consulting mailing list
>>>> 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
>>>
>>>
>>
>>
>> --
>> [image: View Joshua S. Freeman's profile on LinkedIn]
>> <http://www.linkedin.com/in/jfreeman>
>> http://www.joshuasfreeman.me
>>
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> https://lists.drupal.org/mailman/listinfo/consulting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20150129/88de1076/attachment-0001.html