Merge pull request #32 from phuse-org/highlight-status

highlight status
phuse-org · Sep 4, 2024 · 893d07a · 893d07a
2 parents 64b8e94 + 05c8ec9
commit 893d07a
Show file tree

Hide file tree

Showing 13 changed files with 13 additions and 12 deletions.
diff --git a/.gitignore b/.gitignore
@@ -12,3 +12,4 @@ _book/
 _rendered/
 intro_files
 intro.html
+index.tex
diff --git a/OSmodels.qmd b/OSmodels.qmd
@@ -1,5 +1,5 @@
 ---
-title: "OS Business Models"
+title: "(-) OS Business Models"
 ---
 
 ## What open source models are available for businesses?

diff --git a/cost.qmd b/cost.qmd
@@ -1,5 +1,5 @@
 ---
-title: "Cost of Open Source"
+title: "(-) Cost of Open Source"
 ---
 
 ## What is the true cost of implementing open source solutions?

diff --git a/fundOS.qmd b/fundOS.qmd
@@ -1,5 +1,5 @@
 ---
-title: "Funding OS"
+title: "(-) Funding OS"
 ---
 
 ## Is it possible for industry fund open source?

diff --git a/legal.qmd b/legal.qmd
@@ -111,7 +111,7 @@ To further safeguard the project, organizations could consider implementing a fo
 
 ### Cyber Resilience Act
 
-Another topic brought up by James Black is the ["Cyber Resilience Act"](https://www.european-cyber-resilience-act.com/){target="_blank"}. The Cyber Resilience Act is a significant piece of legislation that will introduce new responsibilities specifically for organizations and companies providing open-source software. This act aims to enhance the overall cybersecurity posture of the digital ecosystem by establishing a robust framework for managing cyber risks. 
+Another topic brought up by James Black is the ["Cyber Resilience Act"](https://www.european-cyber-resilience-act.com/){target="_blank"}. The EU Cyber Resilience Act is a significant piece of legislation that will introduce new responsibilities specifically for organizations and companies providing open-source software. This act aims to enhance the overall cybersecurity posture of the digital ecosystem by establishing a robust framework for managing cyber risks. 
 
 For open-source providers, this could mean implementing more stringent security measures, conducting regular vulnerability assessments, and ensuring timely patching and updates. It may also necessitate greater transparency about their security practices and more rigorous reporting of security incidents. 
 

diff --git a/longrun.qmd b/longrun.qmd
@@ -1,5 +1,5 @@
 ---
-title: "OS in the Long Run"
+title: "(-) OS in the Long Run"
 ---
 
 ## How do we ensure that the solutions being developed today will exist in the long run?

diff --git a/match.qmd b/match.qmd
@@ -1,5 +1,5 @@
 ---
-title: "Numerical Matching"
+title: "(-) Numerical Matching"
 ---
 
 ## What if open source languages and commercial software (such as SAS), do not match numerically with the analysis results they give?

diff --git a/summary.qmd b/summary.qmd
@@ -1,5 +1,5 @@
 ---
-title: "What is Open Source?"
+title: "(-) What is Open Source?"
 ---
 
 ## What is Open Source?

diff --git a/trust.qmd b/trust.qmd
@@ -1,5 +1,5 @@
 ---
-title: "Establishing Trust"
+title: "(-) Establishing Trust"
 ---
 
 ## Can an open source solution be trusted?

diff --git a/user_dev.qmd b/user_dev.qmd
@@ -1,5 +1,5 @@
 ---
-title: "User Development"
+title: "(-) User Development"
 ---
 
 ## How do you transform the traditional Statistical Programmer into the future Data Scientist?

diff --git a/users.qmd b/users.qmd
@@ -1,5 +1,5 @@
 ---
-title: "User Support"
+title: "(-) User Support"
 ---
 
 ## How do we support users in managing an ever-evolving environment of Open Source solutions?

diff --git a/whatelse.qmd b/whatelse.qmd
@@ -1,5 +1,5 @@
 ---
-title: "What Else?"
+title: "(-) What Else?"
 ---
 
 ## What else can we do?

diff --git a/why.qmd b/why.qmd
@@ -1,5 +1,5 @@
 ---
-title: "Why Open Source?"
+title: "(-) Why Open Source?"
 ---
 
 ## What is the 'why' for using open source solutions in pharma clinical data analytics?