OSS - Revision history

Lsokolowski1 at 09:11, 23 February 2026

2026-02-23T09:11:50Z

@@ Line 24: / Line 24: @@
 ** Contributing Guide (CONTRIBUTING.md)
 ** API documentation (Swagger, Sphinx, Docusaurus, etc.)
 = Main Keys/Concerns =

Lsokolowski1 at 13:44, 13 February 2026

2026-02-13T13:44:05Z

← Older revision		Revision as of 13:44, 13 February 2026
Line 1:		Line 1:
	{{Draft}}		{{Draft}}

	[[Category:private]]		<!-- [[Category:private]] -->

	;title: OSS Training Course		;title: OSS Training Course

Lsokolowski1: /* Concerns */

2026-02-12T23:49:12Z

Concerns

← Older revision		Revision as of 23:49, 12 February 2026
Line 1,189:		Line 1,189:
	= Concerns =		= Concerns =
	Failure modes that hurt trust, adoption, and scientific credibility of open-source research software		Failure modes that hurt trust, adoption, and scientific credibility of open-source research software
	# Unmaintained dependencies leading to security vulnerabilities		# '''Unmaintained dependencies''' leading to security vulnerabilities
	# Hardcoded credentials or exposed configuration secrets		# '''Hardcoded credentials''' or exposed configuration secrets
	# Outdated documentation or broken installation procedures		# '''Outdated documentation''' or broken installation procedures
	# Inactive issue trackers or unresolved pull requests		# '''Inactive issue trackers''' or unresolved pull requests
	# Lack of clarity regarding maintenance status		# Lack of clarity regarding '''maintenance status'''

	= Avoiding Those Common Failures in OSS =		= Avoiding Those Common Failures in OSS =

Lsokolowski1 at 23:47, 12 February 2026

2026-02-12T23:47:26Z

@@ Line 55: / Line 55: @@
 = Open Source Software in Research: Strategy, Practice, and Impact =
-Open Source Software (OSS) as a strategic, technical, and scientific asset for research institutes, illustrated with real-world examples.
+Open Source Software (OSS) as a strategic, technical, and scientific asset for research institutes, illustrated with some real-world examples.
 ----
@@ Line 1,186: / Line 1,186: @@
 * Community over individual ownership
 </div>

Lsokolowski1 at 23:22, 12 February 2026

2026-02-12T23:22:48Z

← Older revision		Revision as of 23:22, 12 February 2026
Line 59:		Line 59:
	----		----

	== ~~Slide~~ 1 — The Strategic Role of OSS in a Research Institute ==		== 1 — The Strategic Role of OSS in a Research Institute ==
	Open Source Software is foundational to modern research practice.		Open Source Software is foundational to modern research practice.

Line 73:		Line 73:
	----		----

	== ~~Slide~~ 2 — Real-World Example: CERN ==		== 2 — Real-World Example: CERN ==
	CERN treats software as a first-class research output.		CERN treats software as a first-class research output.

Line 91:		Line 91:
	----		----

	== ~~Slide~~ 3 — OSS and Publicly Funded Research ==		== 3 — OSS and Publicly Funded Research ==
	Open software aligns with public funding principles.		Open software aligns with public funding principles.

Line 106:		Line 106:
	----		----

	== ~~Slide~~ 4 — Real-World Example: European Commission & EOSC ==		== 4 — Real-World Example: European Commission & EOSC ==
	The European Open Science Cloud (EOSC) promotes OSS.		The European Open Science Cloud (EOSC) promotes OSS.

Line 123:		Line 123:
	----		----

	== ~~Slide~~ 5 — Licensing Choices: Why They Matter ==		== 5 — Licensing Choices: Why They Matter ==
	Licenses define legal reuse.		Licenses define legal reuse.

Line 134:		Line 134:
	----		----

	== ~~Slide~~ 6 — Real-World Example: NumPy & SciPy ==		== 6 — Real-World Example: NumPy & SciPy ==
	NumPy and SciPy originated in academic research.		NumPy and SciPy originated in academic research.

Line 150:		Line 150:
	----		----

	== ~~Slide~~ 7 — Permissive vs. Copyleft Licenses ==		== 7 — Permissive vs. Copyleft Licenses ==
	Two main license families are common in research.		Two main license families are common in research.

Line 165:		Line 165:
	----		----

	== ~~Slide~~ 8 — Real-World Example: GNU Scientific Software ==		== 8 — Real-World Example: GNU Scientific Software ==
	GNU scientific tools use copyleft licenses.		GNU scientific tools use copyleft licenses.

Line 181:		Line 181:
	----		----

	== ~~Slide~~ 9 — Minimum Best Practices for Publishing Research Software ==		== 9 — Minimum Best Practices for Publishing Research Software ==
	Research software should meet baseline standards.		Research software should meet baseline standards.

Line 195:		Line 195:
	----		----

	== ~~Slide~~ 10 — Real-World Example: EMBL-EBI ==		== 10 — Real-World Example: EMBL-EBI ==
	EMBL-EBI publishes bioinformatics software openly.		EMBL-EBI publishes bioinformatics software openly.

Line 213:		Line 213:
	----		----

	== ~~Slide~~ 11 — Documentation as a Research Output ==		== 11 — Documentation as a Research Output ==
	Documentation supports reproducibility.		Documentation supports reproducibility.

Line 226:		Line 226:
	----		----

	== ~~Slide~~ 12 — Versioning, Releases, and Citation ==		== 12 — Versioning, Releases, and Citation ==
	Stable versions enable scientific referencing.		Stable versions enable scientific referencing.

Line 237:		Line 237:
	----		----

	== ~~Slide~~ 13 — Real-World Example: Zenodo + GitHub ==		== 13 — Real-World Example: Zenodo + GitHub ==
	Many institutes integrate GitHub with Zenodo.		Many institutes integrate GitHub with Zenodo.

Line 255:		Line 255:
	----		----

	== ~~Slide~~ 14 — Governance When Opening Internal Code ==		== 14 — Governance When Opening Internal Code ==
	Open code requires explicit governance.		Open code requires explicit governance.

Line 267:		Line 267:
	----		----

	== ~~Slide~~ 15 — Real-World Example: Apache Software Foundation ==		== 15 — Real-World Example: Apache Software Foundation ==
	ASF provides a mature governance model.		ASF provides a mature governance model.

Line 285:		Line 285:
	----		----

	== ~~Slide~~ 16 — Managing External Contributions ==		== 16 — Managing External Contributions ==
	External contributions need structure.		External contributions need structure.

Line 298:		Line 298:
	----		----

	== ~~Slide~~ 17 — Positioning OSS as Scientific Impact ==		== 17 — Positioning OSS as Scientific Impact ==
	Software impact is measurable.		Software impact is measurable.

Line 309:		Line 309:
	----		----

	== ~~Slide~~ 18 — Real-World Example: Research Software as Impact ==		== 18 — Real-World Example: Research Software as Impact ==
	Examples:		Examples:
	* R language ecosystem (originated in academia)		* R language ecosystem (originated in academia)
Line 324:		Line 324:
	----		----

	== ~~Slide~~ 19 — Technical Repository Management ==		== 19 — Technical Repository Management ==
	Engineering practices support trust.		Engineering practices support trust.

Line 337:		Line 337:
	----		----

	== ~~Slide~~ 20 — Real-World Example: NASA Open Source ==		== 20 — Real-World Example: NASA Open Source ==
	NASA publishes and maintains OSS.		NASA publishes and maintains OSS.

Line 355:		Line 355:
	----		----

	== ~~Slide~~ 21 — Key Takeaways ==		== 21 — Key Takeaways ==
	* OSS is strategic research infrastructure		* OSS is strategic research infrastructure
	* Licensing shapes reuse and impact		* Licensing shapes reuse and impact

Lsokolowski1 at 23:19, 12 February 2026

2026-02-12T23:19:00Z

← Older revision		Revision as of 23:19, 12 February 2026
Line 363:		Line 363:
	* Automation sustains quality over time		* Automation sustains quality over time

	== Extended Details ==		= Extended Details =
	Unfold it with the '''Expand''' button on the very right side below		Unfold it with the '''Expand''' button on the very right side below
	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">

Lsokolowski1 at 23:16, 12 February 2026

2026-02-12T23:16:41Z

Show changes

Lsokolowski1 at 23:02, 12 February 2026

2026-02-12T23:02:01Z

Show changes

Lsokolowski1 at 22:54, 12 February 2026

2026-02-12T22:54:46Z

← Older revision		Revision as of 22:54, 12 February 2026
Line 55:		Line 55:

	= Extended Details =		= Extended Details =
			Unfold it with the button on the very right side below
	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">
	= Modern Software Development Practices (Python & JavaScript) =		= Modern Software Development Practices (Python & JavaScript) =

Lsokolowski1 at 22:52, 12 February 2026

2026-02-12T22:52:52Z

← Older revision		Revision as of 22:52, 12 February 2026
Line 51:		Line 51:
	-->		-->

	Extended Details		= Main Keys/Concerns =
			todo

			= Extended Details =

	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">
	= Modern Software Development Practices (Python & JavaScript) =		= Modern Software Development Practices (Python & JavaScript) =