This week, Linux Out Loud chats Linux topics to teach.
Welcome to episode 05 of Linux Out Loud. We fired up our mics, connected those headphones as we searched the community for themes to expound upon. We kept the banter friendly, the conversation somewhat on topic, and had fun doing it.
04:44 Raspberry Pi Rack Bracket
11:08 Linux in Education
35:17 PSU Shopping
42:22 3D Fidget Button
Hey @TheWendyPower, I know you were chatting about using git for the projects that your kids co-op (I think that’s how you spell that ) will be working on. I actually worked with my wife to make some intro to git based detailed guides & she recorded the meeting for going over those guides with GWC (Girls Who Code) at UNC Charlotte. We mainly went over the basics of using git, and we used VScode (for a few reasons). We did this, because she is in charge of a web team for redesigning their website and no one knew how to use git (our college doesn’t really teach it to us).
We covered the entire setup process (installing vscode (personally for Linux I normally use the flatpak or snap (snap is my personal favorite) but I just linked to the official installer in the guide because the confinement of at least the flatpak can be weird for new people) + git (most Linux desktop distros have git installed by default (in my experience)), authenticating to GitHub (GH) (using GH’s integrated auth (creates a personal access token IIRC) so they can enable two factor authentication (2FA) and not have to worry about ssh keys & is platform agnostic), forking, cloning, modifying files and committing those modified files, branching, and pull requests (PRs). We didn’t go into any deep details, but mainly cover high level with step by step instructions so people could get familiar with how to use it.
I think that specifically the forking and branching + PRs would be really good for your use case. That would allow the kids to play around with whatever code you have in their own forks + branches, and then create PRs to submit the modified files to your upstream repo (or delete and start over again if they really mess stuff up ). GH has also made it pretty easy to pull upstream changes, so once you merge their PRs they can pull in all the new changes from the web-ui.