@prefix ns1: <https://w3id.org/okn/o/sd#> .

@prefix ns2: <http://schema.org/> .

@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://w3id.org/okn/i/Agent/tpronk> a ns2:Person ;

ns2:name "tpronk" .

<https://w3id.org/okn/i/License/GNU%20Affero%20General%20Public%20License%20v3.0> a ns2:CreativeWork ;

ns1:name "GNU Affero General Public License v3.0" ;

ns1:url "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/LICENSE"^^xsd:anyURI .

<https://w3id.org/okn/i/Software/somef-demo-repo> a ns1:Software ;

ns2:license <https://w3id.org/okn/i/License/somef-demo-repo> ;

ns1:contactDetails """Contact person responsible for maintaining a software component

""" ;

ns1:contributingGuidelines """These guidelines were copied from [PychoPy](https://github.com/psychopy/psychopy/edit/dev/CONTRIBUTING.md)

# Have you ever contributed to an Open Source project?

Your first contribution can be a bit intimidating, but feel free to give it a try. If you get stuck, don't hesitate to ask for help in our [developer forum](https://discourse.psychopy.org/c/dev). This is also a good place to pitch your idea. Next up:

* **I won't program it myself.** Please file a [GitHub issue](https://github.com/psychopy/psychopy/issues).

* **I'd like to take a shot.** Read on to find out how!

# How to contribute

Contributing to PsychoPy consists of four steps:

1. Getting your own copy

2. Making your changes

3. Committing your changes

4. Submitting a Pull Request

## 1. Getting your own copy of the PsychoPy codebase

To be sure your improvements can easily be integrated, follow these steps:

1. **Make a [fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) of the [PsychoPy repo](https://github.com/psychopy/psychopy).** This provides you with your own copy of the PsychoPy source code.

2. **Inside your fork, make a new [branch](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-branches) for the feature you've got in mind.** If you'd like to fix a bug, base your new branch on the *release* branch. If you'd like to add a new feature, base it on the *dev* branch. We tend to name branches after the feature we're building. For example `olfactory_component`.

3. **Clone your fork to your hard drive.** Next, switch to the new branch and you're all set up!

Look [here](https://www.psychopy.org/developers/repository.html) to see how the PsychoPy repo is organized.

## 2. Making your changes

To help you get started with modifying PsychoPy, we've got some [developer guides](https://www.psychopy.org/developers/index.html). To try out your modified PsychoPy, do a [developer's install](https://www.psychopy.org/download.html#developers-install).

## 3. Committing your changes

Once you're happy with your changes, commit them to your GitHub repo. Please use the tags below in your commit and add an informative message.

- **BF:** bug fix. For fixing bugs in the *release* branch.

- **FF:** ‘feature’ fix. For fixing bugs in the *dev* branch.

- **RF:** refactoring

- **NF:** new feature

- **ENH:** enhancement (to existing code, but don't worry too much about the difference between this and NF)

- **DOC:** for all kinds of documentation related commits

- **TEST:** for adding or changing tests

## 4. File a Pull Request

Once you're done, it's time to add it to the central PsychoPy source code. File a [Pull Request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) from your own fork and branch to the PsychoPy repo. Be sure to target the right branch in PsychoPy (*release* or *dev*). Thanks for contributing!

""" ;

ns1:contributionInstructions """These guidelines were copied from [PychoPy](https://github.com/psychopy/psychopy/edit/dev/CONTRIBUTING.md)

# Have you ever contributed to an Open Source project?

Your first contribution can be a bit intimidating, but feel free to give it a try. If you get stuck, don't hesitate to ask for help in our [developer forum](https://discourse.psychopy.org/c/dev). This is also a good place to pitch your idea. Next up:

* **I won't program it myself.** Please file a [GitHub issue](https://github.com/psychopy/psychopy/issues).

* **I'd like to take a shot.** Read on to find out how!

# How to contribute

Contributing to PsychoPy consists of four steps:

1. Getting your own copy

2. Making your changes

3. Committing your changes

4. Submitting a Pull Request

## 1. Getting your own copy of the PsychoPy codebase

To be sure your improvements can easily be integrated, follow these steps:

1. **Make a [fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) of the [PsychoPy repo](https://github.com/psychopy/psychopy).** This provides you with your own copy of the PsychoPy source code.

2. **Inside your fork, make a new [branch](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-branches) for the feature you've got in mind.** If you'd like to fix a bug, base your new branch on the *release* branch. If you'd like to add a new feature, base it on the *dev* branch. We tend to name branches after the feature we're building. For example `olfactory_component`.

3. **Clone your fork to your hard drive.** Next, switch to the new branch and you're all set up!

Look [here](https://www.psychopy.org/developers/repository.html) to see how the PsychoPy repo is organized.

## 2. Making your changes

To help you get started with modifying PsychoPy, we've got some [developer guides](https://www.psychopy.org/developers/index.html). To try out your modified PsychoPy, do a [developer's install](https://www.psychopy.org/download.html#developers-install).

## 3. Committing your changes

Once you're happy with your changes, commit them to your GitHub repo. Please use the tags below in your commit and add an informative message.

- **BF:** bug fix. For fixing bugs in the *release* branch.

- **FF:** ‘feature’ fix. For fixing bugs in the *dev* branch.

- **RF:** refactoring

- **NF:** new feature

- **ENH:** enhancement (to existing code, but don't worry too much about the difference between this and NF)

- **DOC:** for all kinds of documentation related commits

- **TEST:** for adding or changing tests

## 4. File a Pull Request

Once you're done, it's time to add it to the central PsychoPy source code. File a [Pull Request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) from your own fork and branch to the PsychoPy repo. Be sure to target the right branch in PsychoPy (*release* or *dev*). Thanks for contributing!

"""^^xsd:anyURI ;

ns1:dateCreated "2023-11-28T12:30:28+00:00"^^xsd:dateTime ;

ns1:dateModified "2023-12-12T15:35:54+00:00"^^xsd:dateTime ;

ns1:description "This repo aims to provide values for each metadata field that SOMEF (v0.9.4) can extract" ;

ns1:hasAcknowledgments """This demonstration repo was created during the maSMP hackathon at [ZB MED](https://www.zbmed.de/en) sponsored by [NFDI4DataScience](https://www.nfdi4datascience.de). NFDI4DataScience is a consortium funded by the German Research Foundation (DFG), project number 460234259.

""" ;

ns1:hasBuildFile "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/Dockerfile"^^xsd:anyURI ;

ns1:hasCodeOfConduct """# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our

community a harassment-free experience for everyone, regardless of age, body

size, visible or invisible disability, ethnicity, sex characteristics, gender

identity and expression, level of experience, education, socio-economic status,

nationality, personal appearance, race, religion, or sexual identity

and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,

diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our

community include:

* Demonstrating empathy and kindness toward other people

* Being respectful of differing opinions, viewpoints, and experiences

* Giving and gracefully accepting constructive feedback

* Accepting responsibility and apologizing to those affected by our mistakes,

and learning from the experience

* Focusing on what is best not just for us as individuals, but for the

overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or

advances of any kind

* Trolling, insulting or derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or email

address, without their explicit permission

* Other conduct which could reasonably be considered inappropriate in a

professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of

acceptable behavior and will take appropriate and fair corrective action in

response to any behavior that they deem inappropriate, threatening, offensive,

or harmful.

Community leaders have the right and responsibility to remove, edit, or reject

comments, commits, code, wiki edits, issues, and other contributions that are

not aligned to this Code of Conduct, and will communicate reasons for moderation

decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when

an individual is officially representing the community in public spaces.

Examples of representing our community include using an official e-mail address,

posting via an official social media account, or acting as an appointed

representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported to the community leaders responsible for enforcement at

.

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the

reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining

the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed

unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing

clarity around the nature of the violation and an explanation of why the

behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series

of actions.

**Consequence**: A warning with consequences for continued behavior. No

interaction with the people involved, including unsolicited interaction with

those enforcing the Code of Conduct, for a specified period of time. This

includes avoiding interactions in community spaces as well as external channels

like social media. Violating these terms may lead to a temporary or

permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including

sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public

communication with the community for a specified period of time. No public or

private interaction with the people involved, including unsolicited interaction

with those enforcing the Code of Conduct, is allowed during this period.

Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community

standards, including sustained inappropriate behavior, harassment of an

individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within

the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],

version 2.0, available at

https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct

enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at

https://www.contributor-covenant.org/faq. Translations are available at

https://www.contributor-covenant.org/translations.

""" ;

ns1:hasDownloadUrl "https://github.com/tpronk/somef-demo-repo/releases"^^xsd:anyURI ;

ns1:hasExample "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/executable_example.ipynb"^^xsd:anyURI ;

ns1:hasExecutableInstructions """There is no code in this repo that can be run.

""" ;

ns1:hasExecutableNotebook "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/executable_example.ipynb" ;

ns1:hasFAQ """Frequently asked questions about a software component

""" ;

ns1:hasInstallationInstructions """##Installation instructions

A set of instructions that indicate how to install a target repository

""" ;

ns1:hasLongName "somef-demo-repo" ;

ns1:hasSourceCode <https://w3id.org/okn/i/SoftwareSource/somef-demo-repo> ;

ns1:hasSupportScriptLocation "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/script_file.sh"^^xsd:anyURI ;

ns1:hasUsageNotes """##Usage examples

Assumptions and considerations recorded by the authors when executing a software component, or examples on how to use it.

""" ;

ns1:hasVersion <https://w3id.org/okn/i/Release/132091437> ;

ns1:identifier "https://zenodo.org/badge/latestdoi/450496579"^^xsd:anyURI ;

ns1:issueTracker "https://api.github.com/repos/tpronk/somef-demo-repo/issues"^^xsd:anyURI ;

ns1:keywords "topic1, topic2, topic3" ;

ns1:name "tpronk/somef-demo-repo" ;

ns1:readme "https://raw.githubusercontent.com/tpronk/somef-demo-repo/main/README.md"^^xsd:anyURI ;

ns1:softwareRequirements """Pre-requisites and dependencies needed to execute a software component.

""" ;

ns1:supportDetails """Guidelines and links of where to obtain support for a software component

""",

"""[](https://gitter.im/OpenGeoscience/geonotebook)

""" .

<https://w3id.org/okn/i/SoftwareSource/somef-demo-repo> a ns2:SoftwareSourceCode ;

ns1:codeRepository "https://github.com/tpronk/somef-demo-repo"^^xsd:anyURI ;

ns1:name "tpronk/somef-demo-repo" ;

ns1:programmingLanguage "Common Workflow Language",

"Dockerfile",

"Jupyter Notebook",

"Shell" .