Repository for R4R F25 cohort weekly journals.
Journals are an essential part to learning, applying and reporting your progress through Roots 4 Resilience and FOSS.
Each journal has 3 parts:
| Name of Entry | Entry Type | Due Date of Entry |
|---|---|---|
| Rose, Thorn, Bud | - Write what worked/what is applicable to your research during the FOSS session (Rose); - What you didn't understand as well/what you think would be challenging to apply to your research (Thorn) - What could potentially be applied to your work? (Bud) |
Due immediate Wednesday following FOSS, 11pm |
| Research Application | Following up the R4R Thursday discussion, write how the weekly covered material is applicable/not applicable to your work. If applicable, give clear examples of the application; If not, describe in detail why not. | Due prior to following FOSS session |
| Cohort meetup discussion | Give a summary of the discussed topics that are relevant to your work. | Due prior to following R4R session |
Submissions are carried out in 2 steps:
- Forking the repository (one time step!)
- Pull requests (done each time you want to make a submission)
Forking is the action of copying a repository AND keeping it connected to the source (copying but severing the connection is called Importing).
This allows to create your own copy of the journaling repository. You can make changes to the Branch of the copied repository without altering the source.
Once you are satisfied of your changes, you can then create a Pull Request in order to submit your weekly journals.
The following steps have to be executed once.
- Fork the original repository (this repository): at the top of the page, find the "Fork" button.
- In the Creat a Fork page, ensure that (1) "Copy the
mainbrach only" is ticked off and then (2) click the "Create fork" button.
Upon creating a Fork of the original repository, you will find the clone in your list of repositories under your own account.
- Navigate to your own account, and select the "R4R_F24-journals" repository.
- (1) Click the Select the Branches button (you will see main on it) and (2) Select your name. If you can't see it, click View all branches and select your name.
- Select the journal you want to edit; For example reasons I chose
journal_01-02sept25.md.
- Click on the Edit function (pencil on the top right side).
- Edit the entry using Markdown (use the Markdown guide to learn the correct use of the Markdown syntax). Once finished, click on the "Commit changes..." button, on the top right.
- (1) Give a constructive, succint message; (2) VERY IMPORTANT: make sure to select "Commit directly to the
<YOUR NAME>branch"; (3) Press "Commit changes".
- You should be automatically be brought to your fork's main page; (1) Sanity check: ensure that there is a message saying "This branch is
#commit ahead ofCosiMichele/R4R_F25-journals:<YOUR NAME>". (2) In the yellow message box, click "Compare & pull request".
- (1) Sanity check: ensure that base and head repositories are both
<YOUR NAME>. (2) Click "Create pull request".
At this point you will have submitted your journal! It's tedious in the beginning but in no time you will get the hang of it!