Weekly Journal/Blog
Every student will maintain a journal for this class, with entries made on a weekly basis. Writing a journal is a way to improve your communication skills. The journal also serves as a record of what you have accomplished in this class. We will use a blog as the medium for these journal entries.
You will be given a public repository for this course-related blog. The fact that it is public implies that anyone in the world can read what is put into this blog. The exact instructions for how to set up the blog are in the README.md
file in the blog repository on GitHub that I have created for you. The blog template is in the class organization at
https://github.com/hunter-college-ossd-spr19/weekly
Your individual blog is named
https://github.com/hunter-college-ossd-spr19/gh-username-weekly
where gh-username
is your GitHub account name. The blog repository is set up in such a way that your blog serves as the source code for a web-page hosted on GitHub, using GitHub Pages
. For information about GitHub Pages
, see What is GitHub Pages. Because GitHub Pages
has been activated for this repository, you will automatically have a webpage at the URL
https://hunter-college-ossd-spr19.github.io/gh-username-weekly/
where gh-username
is your GitHub account name.
Your blog entries must be written using Markdown. It is very important that you make them as professional-looking as possible, and using Markdown will make this possible. Because the blog files are hosted on GitHub, you can use either the standard Markdown syntax or GitHub-Flavored Markdown. Help with Markdown can be found at the following sites:
Each week, by Thursday night, a new post should be added to the blog for the week ending that day. For example, the first day of classes is Friday, January 25, so the first week is from January 25 through January 31.
There is directory in your repository
https://github.com/hunter-college-ossd-spr19/gh-username-weekly
named _posts
. This directory was filled with three files initially, named
2019-02-01-week01.md
2019-02-08-week02.md
2019-02-15-week03.md
respectively. The blog post for the first week is created by editing the first file, for the second week, the second file, and so on. You should create new files as the semester advances, using the exact same form for their names.
The blog post for a given week should be based on the following conditions:
If an assignment was given that specifically asked for something to be written in the blog for the week, then the post for the week should include whatever
was requested in the assignment.Whether or not anything was assigned, the post for that week should include a summary of all course-related activity.
If you have made any contributions of any kind, whether they are to OpenStreetMap, Wikipedia, or any software project, the post should include a list of those contributions.
A Rubric for Assessment of Blog Posts
Blog posts are a component of your grade in the course. I have never found a good way to assign a numerical score to narrative writing, like a blog post. Nonetheless, these posts must be assessed. Therefore, I am using the following ordinal scale for assessing the posts. "Ordinal" means that it is linear but that the numbers have no arithmetic properties other than one being larger or smaller than another. A score of 3 is not three times as good as a score of 1.
Grade | Assessment |
---|---|
3 | The post is thoughtful, well-written, well-formatted, satisfies the stated objectives for the posts for the given week, and demonstrates a significant amount of effort. |
2 | The post is not particularly thoughtful, adequately-written, adequately-formatted, and satisfies the stated objectives for the posts for the given week, and demonstrates a modest amount of effort. |
1 | The post satisfies the stated objectives for the posts for the given week, but not much more. There is little thought given to it, and almost no effort. |
0 | The post was not written. |