Skip to content

Commit 486f9c4

Browse files
authored
Merge pull request #8 from ResearchObject/update-config
Update config, README, and contributor docs
2 parents 4380d02 + e27b308 commit 486f9c4

File tree

10 files changed

+833
-34100
lines changed

10 files changed

+833
-34100
lines changed

CODE_OF_CONDUCT.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Contributor Code of Conduct
2+
3+
Contributors to the RO-Crate community, including this tutorial, are expected to comply with our [Code of Conduct](https://github.com/ResearchObject/ro-crate/blob/main/CODE_OF_CONDUCT.md) to ensure an open and inclusive environment. You may email [email protected] to report any Code of Conduct concerns.

CONTRIBUTING.md

Lines changed: 133 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
# Contributing
2+
3+
[RO-Crate][roc-site] and [The Carpentries][c-site] (who provide the lesson template)
4+
are open source projects,
5+
and we welcome contributions of all kinds: new lessons, fixes to
6+
existing material, bug reports, and reviews of proposed changes are all
7+
welcome.
8+
9+
## Contributor Agreement
10+
11+
By contributing, you agree that we may redistribute your work under [our
12+
license](LICENSE.md). In exchange, we will address your issues and/or assess
13+
your change proposal as promptly as we can, and help you become a member of our
14+
community. Everyone involved in [RO-Crate][roc-site] agrees to abide by our
15+
[code of conduct](CODE_OF_CONDUCT.md).
16+
17+
## How to Contribute
18+
19+
The easiest way to get started is to file an issue to tell us about a spelling
20+
mistake, some awkward wording, or a factual error. This is a good way to
21+
introduce yourself and to meet some of our community members.
22+
23+
1. If you do not have a [GitHub][github] account, you can [send us comments by
24+
email][roc-contact]. However, we will be able to respond more quickly if you use
25+
one of the other methods described below.
26+
27+
2. If you have a [GitHub][github] account, or are willing to [create
28+
one][github-join], but do not know how to use Git, you can report problems
29+
or suggest improvements by [creating an issue][repo-issues]. This allows us
30+
to assign the item to someone and to respond to it in a threaded discussion.
31+
32+
3. If you are comfortable with Git, and would like to add or change material,
33+
you can submit a pull request (PR). Instructions for doing this are
34+
[included below](#using-github). For inspiration about changes that need to
35+
be made, check out the [list of open issues][issues] across the Carpentries.
36+
37+
Note: if you want to build the website locally, please refer to [The Workbench
38+
documentation][template-doc].
39+
40+
## Where to Contribute
41+
42+
1. If you wish to change this lesson, add issues and pull requests here.
43+
2. If you wish to change the template used for workshop websites, please refer
44+
to [The Workbench documentation][template-doc].
45+
46+
## What to Contribute
47+
48+
There are many ways to contribute, from writing new exercises and improving
49+
existing ones to updating or filling in the documentation and submitting [bug
50+
reports][issues] about things that do not work, are not clear, or are missing.
51+
If you are looking for ideas, please see [the list of issues for this
52+
repository][repo-issues], or the issues for [Data Carpentry][dc-issues],
53+
[Library Carpentry][lc-issues], and [Software Carpentry][swc-issues] projects.
54+
55+
Comments on issues and reviews of pull requests are just as welcome: we are
56+
smarter together than we are on our own. **Reviews from novices and newcomers
57+
are particularly valuable**: it's easy for people who have been using these
58+
lessons for a while to forget how impenetrable some of this material can be, so
59+
fresh eyes are always welcome.
60+
61+
## What *Not* to Contribute
62+
63+
Our lessons already contain more material than we can cover in a typical workshop,
64+
so we are usually *not* looking for more concepts or tools to add to them.
65+
As a rule,
66+
if you want to introduce a new idea,
67+
you must (a) estimate how long it will take to teach
68+
and (b) explain what you would take out to make room for it.
69+
The first encourages contributors to be honest about requirements;
70+
the second, to think hard about priorities.
71+
72+
We are also not looking for exercises or other material that only run on one platform.
73+
Our workshops typically contain a mixture of Windows, macOS, and Linux users;
74+
in order to be usable,
75+
our lessons must run equally well on all three.
76+
77+
## Using GitHub
78+
79+
If you choose to contribute via GitHub, you may want to look at [How to
80+
Contribute to an Open Source Project on GitHub][how-contribute]. In brief, we
81+
use [GitHub flow][github-flow] to manage changes:
82+
83+
1. Create a new branch in your desktop copy of this repository for each
84+
significant change.
85+
2. Commit the change in that branch.
86+
3. Push that branch to your fork of this repository on GitHub.
87+
4. Submit a pull request from that branch to the [upstream repository][repo].
88+
5. If you receive feedback, make changes on your desktop and push to your
89+
branch on GitHub: the pull request will update automatically.
90+
91+
NB: The published copy of the lesson is usually in the `main` branch.
92+
93+
Each lesson has a team of maintainers who review issues and pull requests or
94+
encourage others to do so. The maintainers are community volunteers, and have
95+
final say over what gets merged into the lesson.
96+
97+
## Other Resources
98+
99+
General discussion of [RO-Crate][roc-site] happens on the
100+
[RO-Crate GitHub repository](https://github.com/ResearchObject/ro-crate) and in our
101+
[community spaces](https://www.researchobject.org/ro-crate/community),
102+
which everyone is welcome to join.
103+
You can also [reach us by email][roc-contact].
104+
105+
The Carpentries is a global organisation with volunteers and learners all over
106+
the world. We share values of inclusivity and a passion for sharing knowledge,
107+
teaching and learning. There are several ways to connect with The Carpentries
108+
community listed at <https://carpentries.org/connect/> including via social
109+
media, slack, newsletters, and email lists. You can also [reach us by
110+
email][cp-contact].
111+
112+
113+
[roc-contact]: mailto:[email protected]
114+
[roc-site]: https://www.researchobject.org/ro-crate/
115+
[repo]: https://github.com/ResearchObject/packaging_data_with_ro-crate
116+
[repo-issues]: https://github.com/ResearchObject/packaging_data_with_ro-crate/issues
117+
[cp-contact]: mailto:[email protected]
118+
[cp-site]: https://carpentries.org/
119+
[dc-issues]: https://github.com/issues?q=user%3Adatacarpentry
120+
[dc-lessons]: https://datacarpentry.org/lessons/
121+
[dc-site]: https://datacarpentry.org/
122+
[discuss-list]: https://carpentries.topicbox.com/groups/discuss
123+
[github]: https://github.com
124+
[github-flow]: https://guides.github.com/introduction/flow/
125+
[github-join]: https://github.com/join
126+
[how-contribute]: https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github
127+
[issues]: https://carpentries.org/help-wanted-issues/
128+
[lc-issues]: https://github.com/issues?q=user%3ALibraryCarpentry
129+
[swc-issues]: https://github.com/issues?q=user%3Aswcarpentry
130+
[swc-lessons]: https://software-carpentry.org/lessons/
131+
[swc-site]: https://software-carpentry.org/
132+
[lc-site]: https://librarycarpentry.org/
133+
[template-doc]: https://carpentries.github.io/workbench/

LICENSE.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
layout: page
3+
title: "Licenses"
4+
root: .
5+
---
6+
7+
# Training Materials
8+
9+
© Copyright 2021-2025 University of Technology Sydney, The University of Manchester UK and RO-Crate contributors.
10+
11+
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
12+
13+
http://www.apache.org/licenses/LICENSE-2.0
14+
15+
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
16+
17+
## Changes
18+
19+
This tutorial has been adapted from the revised [RO-Crate introduction for 1.2](https://www.researchobject.org/ro-crate/1.2-DRAFT/introduction.html) by Stian Soiland-Reyes. Changes include:
20+
* Rewriting to tutorial style with exercises
21+
* Adaptation to Galaxy Training Material rendering
22+
* Explicit links to RO-Crate specifications
23+
* Example changed to different organization and license
24+
* Modiied for Carpentries style
25+
26+
# Examples
27+
28+
The RO-Crate JSON-LD examples and solutions are distributed under [CC0 1.0 Universal (CC0 1.0) Public Domain Dedication](https://creativecommons.org/publicdomain/zero/1.0/). This means they can be re-used freely without any requirements for attribution or licence.
29+
30+
31+
# Trademarks
32+
33+
"Software Carpentry" and "Data Carpentry" and their respective logos
34+
are registered trademarks of [Community Initiatives][CI].
35+
36+
[ci]: http://communityin.org/

README.md

Lines changed: 4 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,6 @@
1-
# FIXME Lesson title
2-
3-
[![Create a Slack Account with us](https://img.shields.io/badge/Create_Slack_Account-The_Carpentries-071159.svg)](https://swc-slack-invite.herokuapp.com/)
4-
5-
**Thanks for contributing to The Carpentries Incubator!**
6-
This repository provides a blank starting point for lessons to be developed here.
7-
8-
A member of the [Carpentries Curriculum Team](https://carpentries.org/team/)
9-
will work with you to get your lesson listed on the
10-
[Community Developed Lessons page][community-lessons]
11-
and make sure you have everything you need to begin developing your new lesson.
12-
13-
## What to do next
14-
15-
Before you begin developing your new lesson,
16-
here are a few things we recommend you do:
17-
18-
* [ ] Decide on a title for your new lesson!
19-
Once you've chosen a new title, you can set the value for `lesson_title`
20-
in [`_config.yml`](_config.yml)
21-
* [ ] Add the URL to your built lesson pages to the repository description\*
22-
* [ ] [Add relevant topic tags to your lesson repository][cdh-topic-tags].
23-
* [ ] Fill in the fields marked `FIXME` in:
24-
* this README
25-
* [`_config.yml`](_config.yml)
26-
* [ ] If you're going to be developing lesson material for the first time
27-
according to our design principles,
28-
consider reading the [Carpentries Curriculum Development Handbook][cdh]
29-
* [ ] Consult the [Lesson Example][lesson-example] website to find out more about
30-
working with the lesson template
31-
* [ ] If you are planning to write your lesson in RMarkdown,
32-
[create a `main` branch and set this as the default branch in your repository settings][change-default-branch]
33-
* [ ] Update this README with relevant information about your lesson
34-
and delete this section
35-
36-
37-
\* To set the URL on GitHub, click the gear wheel button next to **About**
38-
on the right of the repository landing page.
39-
The lesson URL structure is **https://carpentries-incubator.github.io/<repository-slug\>**:
40-
a repository at https://github.com/carpentries-incubator/new-lesson/ will have pages at
41-
the lesson URL https://carpentries-incubator.github.io/new-lesson/.
1+
# Packaging Data with RO-Crates
422

3+
This lesson is intended to teach users how to use [RO-Crate](https://www.researchobject.org/ro-crate/) (Research Object Crates) for packaging research data.
434

445
## Contributing
456

@@ -50,7 +11,7 @@ We'd like to ask you to familiarize yourself with our [Contribution Guide](CONTR
5011
the [more detailed guidelines][lesson-example] on proper formatting, ways to render the lesson locally, and even
5112
how to write new episodes.
5213

53-
Please see the current list of [issues][FIXME] for ideas for contributing to this
14+
Please see the current list of [issues](https://github.com/ResearchObject/packaging_data_with_ro-crate/issues) for ideas for contributing to this
5415
repository. For making your contribution, we use the GitHub flow, which is
5516
nicely explained in the chapter [Contributing to a Project](http://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) in Pro Git
5617
by Scott Chacon.
@@ -64,6 +25,7 @@ Current maintainers of this lesson are
6425
* Stian Soiland-Reyes
6526
* Stuart Owen
6627
* Douglas Lowe
28+
* Eli Chadwick
6729

6830

6931
## Authors

config.yaml

Lines changed: 29 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
---
12
#------------------------------------------------------------
23
# Values for this lesson.
34
#------------------------------------------------------------
@@ -10,36 +11,36 @@
1011
# incubator: The Carpentries Incubator
1112
# Note that you can also use a custom carpentry type. For more info,
1213
# see the documentation: https://carpentries.github.io/sandpaper-docs/editing.html
13-
carpentry: 'incubator'
14+
carpentry: "incubator"
1415

1516
# Custom carpentry description
1617
# This will be used as the alt text for the logo
1718
# carpentry_description: "Custom Carpentry"
1819

1920
# Overall title for pages.
20-
title: 'Packaging Data with RO-Crates'
21+
title: "Packaging Data with RO-Crates"
2122

2223
# Date the lesson was created (YYYY-MM-DD, this is empty by default)
23-
created:
24+
created:
2425

2526
# Comma-separated list of keywords for the lesson
26-
keywords: 'software, data, lesson, The Carpentries'
27+
keywords: "software, data, lesson, The Carpentries"
2728

2829
# Life cycle stage of the lesson
2930
# possible values: pre-alpha, alpha, beta, stable
30-
life_cycle: 'beta'
31+
life_cycle: "beta"
3132

3233
# License of the lesson materials (recommended CC-BY 4.0)
33-
license: 'CC-BY 4.0'
34+
license: "Apache 2.0"
3435

3536
# Link to the source repository for this lesson
36-
source: 'https://github.com/fishtree-attempt/convert_lesson_2/'
37+
source: "https://github.com/ResearchObject/packaging_data_with_ro-crate"
3738

3839
# Default branch of your lesson
39-
branch: 'main'
40+
branch: "main"
4041

4142
# Who to contact if there are any issues
42-
contact: 'team@carpentries.org'
43+
contact: "ro-crate@researchobject.org"
4344

4445
# Navigation ------------------------------------------------
4546
#
@@ -64,39 +65,35 @@ contact: '[email protected]'
6465
# - another-learner.md
6566

6667
# Order of episodes in your lesson
67-
episodes:
68-
- 01-introduction.md
69-
- 02-folder-as-crate-root.md
70-
- 03-metadata-descriptor.md
71-
- 04-root.md
72-
- 05-root-metadata.md
73-
- 06-cross-references.md
74-
- 07-data-entities.md
75-
- 08-contextual-entities.md
76-
- 09-authorship.md
77-
- 10-validating.md
78-
- 11-triples.md
79-
- 12-html-preview.md
80-
- 13-complete.md
81-
- 14-next-steps.md
68+
episodes:
69+
- 01-introduction.md
70+
- 02-folder-as-crate-root.md
71+
- 03-metadata-descriptor.md
72+
- 04-root.md
73+
- 05-root-metadata.md
74+
- 06-cross-references.md
75+
- 07-data-entities.md
76+
- 08-contextual-entities.md
77+
- 09-authorship.md
78+
- 10-validating.md
79+
- 11-triples.md
80+
- 12-html-preview.md
81+
- 13-complete.md
82+
- 14-next-steps.md
8283

8384
# Information for Learners
84-
learners:
85+
learners:
8586

8687
# Information for Instructors
87-
instructors:
88+
instructors:
8889

8990
# Learner Profiles
90-
profiles:
91+
profiles:
9192

9293
# Customisation ---------------------------------------------
9394
#
9495
# This space below is where custom yaml items (e.g. pinning
9596
# sandpaper and varnish versions) should live
9697

97-
98-
carpentry_description: Lesson Description
99-
url: https://preview.carpentries.org/convert_lesson_2
100-
analytics: carpentries
98+
url: https://www.researchobject.org/packaging_data_with_ro-crate/
10199
lang: en
102-
workbench-beta: yes

0 commit comments

Comments
 (0)