uabrc / uabrc/uabrc.github.io

Add information on Software Governance process for relevant software

Open
#1,014 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

fix: inaccuracy ⚠️
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What is inaccurate?

We don't have links for initiating Software Governance reviews of EULAs for scientific software. Researchers are generally (implicitly) permitted to use software with permissive licenses. However, no one at UAB has signatory authority to enter contractual agreements unless they are specifically designated or permitted to do so. So, any software that requires signing an agreement (EULA, purchase contract) requires a review by Software Governance and/or Legal.

The reason is because there is risk to UAB with entering into any contract or agreement. There is risk of fraud on the part of the software creator, risk of harm caused by the software, risk of cost from changing future terms, risk of lawsuits due to breach of contract or tort, and risk of harm from future loss of access to the software.

In practice, software that has zero dollar cost goes through this process very quickly as the risk to UAB is often very low.

I'll get information about how to start this process, and we can add it.

It's not our job to enforce the rules, but we can at least provide some guidance and another point of entry.

Where is the inaccuracy?

Anywhere we discuss software that meets one of the following:

  • Costs more than zero dollars.
  • Requires a purchase agreement.
  • Requires a contract.
  • Requires a subscription.
  • Requires human action to agree to any terms (such as clicking a button, checking a checkbox, writing a signature, typing "yes" and pressing enter, etc.). Usually related to End User License Agreements (EULAs) or other License Agreements.

Here are some examples:

  • VSCode and VSCode Server
  • 10X Genomics Software
  • Amber

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the documentation for references to VSCode, VSCode Server, 10X Genomics Software, and Amber, since no target file is named. Obtain the Software Governance and Legal review entry points, then add guidance or links wherever software requiring agreements, subscriptions, payment, or human acceptance is discussed.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.