Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How should the signing party sign the contract? #12

Open
3 tasks
ei8fdb opened this issue Nov 22, 2021 · 5 comments
Open
3 tasks

How should the signing party sign the contract? #12

ei8fdb opened this issue Nov 22, 2021 · 5 comments
Assignees
Labels
compliance/contracting This label relates to the compliance and contracting workflow. ux This label relates to UX work

Comments

@ei8fdb
Copy link

ei8fdb commented Nov 22, 2021

Additional context

This is a sub-issue of #9 and #10.

We want to find out what options the contractor should have to sign the contract. The research is into what the community reaction would be to electronic signtures and based on this OTF will then make a decision.

So far, there are 2 options for signing contracts:

  1. the contractor downloads the contract PDF, signs the relevant area and then uploads the signed copy
  2. using an e-signing service which provides the contractor and OTF staff with a link to sign the contract electronically

Options for 2. above fall under 2 categories:

  1. self-hosted, open source options
    Some possibe options are:
  1. 3rd party services
    Some possible options are:

Research

The objective of this research is to find out community reaction. To find this out we'll carry out research with:

  • previouly funded/currently funding projects
  • PMs
  • AC members
@ei8fdb ei8fdb self-assigned this Nov 22, 2021
@ei8fdb ei8fdb added the ux This label relates to UX work label Nov 22, 2021
@fourthletter
Copy link

fourthletter commented Nov 22, 2021

  • Select Adobe sign because of security
  • We've agreed the best option is a e-signing service which provides the contractor and OTF staff with a link to sign the contract electronically
  • Both OTF and contractor needs to have the same option to ensure parity, ie both needs to e-sign.

@ei8fdb ei8fdb changed the title How will the signing party sign the contract? How should the signing party sign the contract? Nov 22, 2021
@fourthletter
Copy link

fourthletter commented Jan 25, 2022

Research

  • Synthesize UX research in February
  • Share findings with OTF and developers internally in February

@ei8fdb ei8fdb added the compliance/contracting This label relates to the compliance and contracting workflow. label Feb 23, 2022
@Erioldoesdesign Erioldoesdesign self-assigned this Mar 10, 2022
@fourthletter
Copy link

This issue is no longer needed right now because the contract will not be signed in Hypha. The contractor will sign the contract outside of Hypha.

@Erioldoesdesign
Copy link

Erioldoesdesign commented Apr 12, 2022

This issue is no longer needed right now because the contract will not be signed in Hypha. The contractor will sign the contract outside of Hypha.

Does the workflow for how a contractor signs the contract outside of hypha need mocking up? @fourthletter

@fourthletter
Copy link

On May 4 OTF and SimSec decided on option 1: the contractor downloads the contract PDF, signs the relevant area and then uploads the signed copy. A fully executed singed copy of the contract is uploaded into the WebApp, and is available to the contractor on their 'Projects' page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compliance/contracting This label relates to the compliance and contracting workflow. ux This label relates to UX work
Projects
None yet
Development

No branches or pull requests

3 participants