-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
bfdf72c
commit 187063f
Showing
6 changed files
with
55 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: "Cost of Open Source" | ||
--- | ||
|
||
## What is the true cost of implementing open source solutions? | ||
|
||
- Is it essentially free? | ||
|
||
- What resources are required for proper implementation? | ||
|
||
## How to Contribute | ||
|
||
Contribute to the discussion here in GitHub Discussions:\ | ||
[What is the true cost of implementing open source solutions into clinical data analytic processes??](https://github.com/phuse-org/OSTCDA/discussions/4) | ||
|
||
## Guidance | ||
|
||
- Provide your thoughts and perspectives | ||
|
||
- Provide references to articles, webinars, presentations (citations, links) | ||
|
||
- Be respectful in this community |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
--- | ||
title: "Documenting Trust" | ||
--- | ||
|
||
## How do you document your trust in an open source solution? | ||
|
||
- How do we have document our trust that an open source solution is accurate? | ||
|
||
- How do we know if a third-party will accept our documentation of trust? | ||
|
||
## How to Contribute | ||
|
||
Contribute to the discussion here in GitHub Discussions:\ | ||
[How do you document your trust in an open source solution to satisfy a third-party inquiry?](https://github.com/phuse-org/OSTCDA/discussions/5) | ||
|
||
## Guidance | ||
|
||
- Provide your thoughts and perspectives | ||
|
||
- Provide references to articles, webinars, presentations (citations, links) | ||
|
||
- Be respectful in this community |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters