Skip to content

Updated URLs to the Project Management Protocol in the best practices section #454

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bouweandela merged 2 commits into from
Feb 25, 2026
Merged

Updated URLs to the Project Management Protocol in the best practices section #454

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2f1afd8
update Project Management Protocol link
bakhshir Feb 24, 2026
1571554
Add new contributor details to CITATION.cff
bakhshir Feb 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CITATION.cff
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,10 @@ authors:
family-names: Vargas Honorato
given-names: Rodrigo
orcid: "https://orcid.org/0000-0001-5267-3002"
- affiliation: Netherlands eScience Center
family-names: Bakhshi
given-names: Rena
orcid: "https://orcid.org/0000-0002-2932-3028"
repository-code: "https://github.com/NLeSC/guide"
abstract: >-
This is a guide to software development and projects at
Expand Down
4 changes: 2 additions & 2 deletions best_practices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Use a version control tool like `git` to track changes in your codebase.
This allows you to retrace your steps when debugging, keep your repository clean, easily collaborate with others asynchronously and more.
More info: [The Turing Way chapter on Version Control](https://book.the-turing-way.org/reproducible-research/vcs), [RSQkit chapter on Version Control](http://everse.software/RSQKit/using_version_control).

**At the Netherlands eScience Center:** we always use version control and we preferably use GitHub as our online repository and collaboration platform (see the [Project Management Protocol on our intranet](https://nlesc.sharepoint.com/sites/home/SitePages/Project-procedures.aspx) (only accessible to Netherlands eScience Center employees)).
**At the Netherlands eScience Center:** we always use version control and we preferably use GitHub as our online repository and collaboration platform (see the [Project Management Protocol of the Netherlands eScience Center](https://doi.org/10.5281/zenodo.17117777).

## Testing

Expand Down Expand Up @@ -61,7 +61,7 @@ Since source code is protected by copyright, to allow people to use your code it
For more information, see [The Turing Way chapter on licensing](https://the-turing-way.netlify.app/reproducible-research/licensing) or the [RSQkit Licensing software task](http://everse.software/RSQKit/licensing_software).

**At the Netherlands eScience Center:** our first choice is the Apache v2 license.
See the [Project Management Protocol on our intranet](https://nlesc.sharepoint.com/sites/home/SitePages/Project-procedures.aspx) (only accessible to Netherlands eScience Center employees) for more details on licensing and our intellectual property policies.
See the [our Project Management Protocol](https://doi.org/10.5281/zenodo.17117777) for more details on licensing and our intellectual property policies.

## Software management plans

Expand Down