Weekly Meetings Notes

[camilavargasp]

June 30, 2022

Attendance: Angel, Daphne, Sam, and Camila

Notes

• We talked about making a website instead of a book
• Why a website?
  • Learn Quarto by doing!
  • Have a place where we can show who we are, what we do, and how we came together.
  • Have blog posts about the tools we share within the group!
  • Have a centralized place where we gather all of our shared resources.

Next steps

• Use issues in this repository to plan, coordinate, and communicate ideas.
• Create the website in Quarto
• Publish it through GitHub pages.

[camilavargasp]

Thursday, Jul 7, 2022

Attendance: Althea, Sam, Daphne, Nick, Camila

Notes

• We live code to build our website!
• Sam’s resource for MEDS

Next steps

• Creating a protocol for contributing!
• How do we collaborate on this website
  • Branching?
  • Look into NCEAS scicomptask README for inspiration

[camilavargasp]

Thursday, July 14, 2022

Attendance: Angel, Haley, Daphne, Camila

Notes

• Recap of how we created the website
• Changed organization name to Data Coding Club
• Changed repo name to match organization name -- website URL has been updated
• Decided to use branches for collaborating and then using pull requests to merge into main and publishing

Next Steps

• Camila with draft the collaboration protocol on the README of this repository
• Next week, we will each create our own branch to start "collaborating"
• The first contribution can be our personal description
• Brainstorm a fun structure for our descriptions

[camilavargasp]

Thursday, July 21

Attendance: Angel, Althea, Haley, Sam, and Camila

Notes

• We discussed collaborating using branches.
• We all agree that following Matt's advice and metacatui/CONTRIBUTING.md, we are going to use branches for each feature we add to the website.
• This means, for example, if Haley is going to work on the theme and aesthetics of the website, she will create a new branch named something like epperly_theme. She would then present what she did to the group, and we would merge her changes to the main branch through a pull request.
• We will use protected branches, so everyone has to approve pull requests to main.
• main is the branch that is going to be deployed.
• We then started playing around to understand how branches work. We created personal branches from the command line and push them.
• The idea was that each of us got to create a new branch named lastname_test and then push that local branch to the remote.
• See issue #7 for more details on this exercise and some git commands we played around with.

Next Steps

• Send out a poll to see if people want to meet next week. Some of us can't make it
• Divide in conquer to see who wants to take ownership of what tasks
  • Them and the overall look of the website
  • Create the different pages and describe what will go on them
  • Write our collaboration/contribution protocol in the README of the repo
• Define how we want to present ourselves

[camilavargasp]

Thursday, August 4

Attendance: Angel, Althea, Haley, Nick, and Camila

Notes

• Collaboration: Make a branch per task/feature where we all collaborate. To avoid merge conflict we communicate through Slack when someone has pushed changes. Make sure always to pull first!
• We protected the main branch. We set the rule that at least 1 person has to approve the pull request before merging to main.

Next Steps

• Delete our test branches
• Camila will create a branch to update the Our Team page
• We all write our bios and push changes to this branch. Make sure to communicate via Slack when you are making changes.
• Add a sentence about what you want to achieve with this website project.

[camilavargasp]

Thursday, August 11

Attendance: Daphne, Haley, Nick, Camila

Notes

• We learn about the command quarto preview --> let you preview the website live ina window of your browser. You have to press the stop buttonon the terminal to end the preview.
• We installed font awesome to add cool icons easily.
• Here some documentation about Font Awesome Extension for Quarto and how to install it.
• Create a section for Data recipe - here is how we do this... eg website
• Create a section for "data bites" - short descriptions/ snippets of fun cool things (eg: git command, how to set a cash token for different token time)
• What do we want our landing page to be? Description about our team and what we do here?

Next Steps

• Merch branches!