Honestly, I was surprised to read that there are rules in regards to commit messages and commits in general. It makes sense that it's good practice/rule to avoid as much unnecessary whitespace in a commit as much as possible. I'm glad to read that there's a whole command to check for that for our convenience. Honestly, I found it to be an unwritten rule to include no more than 50 characters in a commit message, but I suppose it's necessary to make that a written one. I can discern that all of these rules are made to make the world of osse as smooth and convenient as possible. Already taken a python class and a data structures class, I got experience with git and GitHub, but so far this class is helping me receive a more in-depth understanding of how it works. I honestly had no idea that we could use git through the command line, but now I can see the importance/improvement of using it this way rather than IDE's like PyCharm and WVS. After reading FOSS definitions, it makes me reflect on how they relate to Runestone Academy. There had to have been a "Benevolent Director" involved throughout it's development history. I imagine there have been instances where someone "forked" the project for improvements and they probably utilized a tracker at some point.