Andy Chase <[email protected]>

Please DocuSign: Liquid Labs - Contractor Agreement_Signature Page.DOCX
8 messages

░░░░░░░░░░░ via DocuSign ░░░░░░░░░░░Tue, Jan 10, 2017 at 3:00 PM
Reply-To: ░░░░░░░░░░░ <[email protected]>
To: Andy Chase <[email protected]>

Andy Chase <[email protected]>Tue, Jan 10, 2017 at 8:01 PM
To: ░░░░░░░░░░░ <[email protected]>
Some questions I have about with this contract: (allowed for by section 11.5):

"including source code developed by Contractor ... generally applicable to other Customer projects"

I'm more then willing to sign over code that applies to projects I do for gigster, but not stuff that might possibly apply in general to gigster projects, since that would be literally everything else.

Particularly since this clause survives forever according to 4.2 and confirmed no time limitation by section 13. Section 7 says I can't sign this broad of a clause since it could apply to other contracts I have open and I have other contracts for other specific clients.

To clarify:

Signing over copyright for work I do for gigster: Cool
Signing over work for every other type of work I do (for example: open source work, upwork clients, toptal clients, employment, etc): Not cool

"Contractor agrees to indemnify Gigster from any and all claims, damages, liability, settlement, attorneys’ fees and expenses, as incurred, on account of the foregoing or any breach of this agreement"

So gigster can do something really awful and I can't seek damages? That doesn't seem fair unless gigster is planning on saying that they can't file suit against me either. Again section 8 seems to indicate that I can't file remedy against gigster violating this agreement.

"does not contain any third-party software, including without limitation, “open source,” “copy left,” “public” or other similar code or anything derived from or based on any of the foregoing"

So I can't derive code from examples from django or flask documentation, cited stack overflow snippets, etc. etc. in my work? I'm not sure that would be a very effective way to operate.

Best regards,
Andy.


[Quoted text hidden]

Andy Chase <[email protected]>Mon, Jan 23, 2017 at 11:36 AM
To: ░░░░░░░░░░░ <[email protected]>, [email protected]
Hey Gigster support,

I hope your day is going well!

Would you guys mind looking over my questions regarding this contract? I might have sent them to the wrong person.

Best wishes,
Andy.
[Quoted text hidden]

░░░░░░░░░░░ ░░░░░░ <[email protected]>Mon, Jan 23, 2017 at 4:23 PM
To: Andy Chase <[email protected]>
Cc: Gigster Support <[email protected]>, ░░░░░░░░░░░ <[email protected]>
░░░░░░░░░░░ to bcc.

Andy,

░░░░░░░░░░░ can help discuss your questions, he is leading up our onboarding for he network.
[Quoted text hidden]
--

░░░░░░░░░░░ ░░░░░░
Operations / HR @ Gigster

░░░░░░░░


Andy Chase <[email protected]>Sat, Jan 28, 2017 at 11:22 PM
To: ░░░░░░░░░░░ ░░░░░░ <[email protected]>
Cc: Gigster Support <[email protected]>, ░░░░░░░░░░░ <[email protected]>
░░░░░░░░░░░,

Please see my question above. Let me know if you have any questions about my questions and I will try and clarify.

I hope that I am not bothering your organization; my goal is simply help understand the contract here and hopefully this will also make sure any future top-tier talent isn't turned away by your possibly spooky wording!

Best,
Andy.
[Quoted text hidden]

░░░░░░░░░░░ ░░░░░░░ <[email protected]>Mon, Jan 30, 2017 at 12:04 PM
To: Andy Chase <[email protected]>
Hi Andy,

I apologize for the slow response on this.

Appreciate your caution - Gigster's success is defined through us making sure our developers are taken care of. We have yet to have a disagreement (much less a legal battle) over the terms here. We have completed thousands of successful milestones and payments without issues with the terms and we unfortunately cannot adjust them on a case by case basis.

I hope that you will still consider working with Gigster.

Regards,
░░░░░░░░░░░
[Quoted text hidden]

Andy Chase <[email protected]>Mon, Jan 30, 2017 at 12:32 PM
To: ░░░░░░░░░░░ ░░░░░░░ <[email protected]>
Thanks for the response ░░░░░░░░░░░.

To clarify, you're not able to answer questions regarding the contract at this time?

Best,
Andy.
[Quoted text hidden]

░░░░░░░░░░░ ░░░░░ <[email protected]>Tue, Jan 31, 2017 at 12:31 PM
To: Andy Chase <[email protected]>
Hi Andy,

Unfortunately, not at this time.

Regards,
░░░░░░░░░░░
[Quoted text hidden]