CSCI-UA 480 (Open Source Software Development)

Complete peer evaluations the link was sent to you through Piazza.

Blog posts for this week:

• report on team project progress - concentrating on your own contributions to the team

• look at the license for the project that your team is working on and determine what are the rules established by that license (what can one do, what is not allowed, what must one do)

• You should also update your "contributions" table with any new contributions (do not include the team work in there).

Presentation content:

• brief intro to the project
• how complicated was the installation of development environment
• what went wrong
• what went well
• summary/descriptions of types of contributions that the team made
• how easy was it to collaborate within the team
• if you were doing this again, would you pick the same or different project

Blog posts for this week:

• report on the rescheduled open data week events, if you attended any

• report on team project progress - concentrating on your own contributions to the team

• You should also update your "contributions" table with any new contributions (do not include the team work in there).

Blog posts for this week:

• report on the rescheduled open data week events, if you attended any

• a reflection on the invited talk: what do you think about the Google's approach to open source

• report on team project progress - concentrating on your own contributions to the team

• Visit the code of conduct document for the Go project. Read the document and explain the benefits of having such a document for a project. Do you think other projects would benefit from having such document? Does the project that your team is working on have a code of conduct document. If so, post the link to it.

• You should also update your "contributions" table with any new contributions (do not include the team work in there).

Blog posts:

• come up with three questions for Danna for Tuesday
• describe the progress that you group made in working on the project, are you (as an individual) able to actively participate in what the group is working on? what are your specific task in the work on the project?
• report on any additional contributions
• report on any open data events that you might have attended this week

Contributions list: in your blog create a file called contributions.md. The document should contain a table with a list of all of your Contributions so far. The table columns should be "week #", "contribution", "contribution type". The first column should just include the week number in which you made your Contributions. The second column should contain the name of the project/site to which the contribution was made and a link to your specific contribution and a brief description ("article edit", "issue reported", "pull request", …). The third column should state what type of contribution in is: "course website", "Wikipedia", "Other".

To incorporate this document into your blog, edit the layouts/default.html document and add

<a href="{{ site.baseurl }}/contributions">Contributions</a>

after line 31 (or after the line that contains the link to the About page, <a href="{{ site.baseurl }}/about">About</a>).

Make sure that you have access to a Linux-like environment:

• a terminal on Mac is fine
• a terminal on Linux is fine
• for Windows, you can use the Ubuntu subsystem, setup a virtual machine or use Cloud 9 (talk to me if you need help with any of that - I have a virtual machine image that you can use, I also have a Cloud 9 team account that I can give you access to).

Team assesment and plan:

• Based on the team, what are the strengths and weaknesses of the team in terms of being able to participate in the project you selected? (Use your teammates' blog posts to assess their strengths and weaknesses)
• Come up with a common meeting time (2 hours block outside of class) to which all team members can commit. Come up with an alternative meeting time (2 hours block outside of
  class) to which all team members can commit - the second time slot will serve as an alternative for weeks during which the first time slot does not work and as a second meeting time during weeks when you need to be able to spend more time working together.
• Create a list of milestones that you need to achieve in order to be able to successfully contribute to the project you selected.

Setup team repositories:

• create a team repository with the fork of the project that your team selected
• create another team repository that will be used for coordinating work on the project (use the project board to set up your milestones)

Readings:

• How to fix a bug in open source software by Richard Schneeman

• How to Report Bugs Effectively by Simon Tatham

• plus all of the resources linked from the slides if you can

Code triage:

• create CodeTriage.com account
• pick a project or two or three
• either wait for the emails with issues or start looking at the issues on the project pages
• triage some reports (Keep in mind that you are working in a real world! Be nice, be professional. )

• if you are not comfortable with using git from the terminal, go through the tryGit tutorial

• make a contribution to Wikipedia or any other WikiCommons project (it can be as small or as large as you wish);

  • create an account on Wikipedia
  • select an article to contribute to
  • make your changes
  • blog about it; describe the following things
    • how you selected the article to contribute to,
    • what the contribution was
    • include the link to the contribution page for your account (in the upper right corner of any page there is a menu with the Contributions as one of the items - when you are logged in, this link shows your contributions

Readings:

• Producing Open Source Software by Karl Fogel,
  • chapter 3, section on Version Control (pages 52-61)
• ProGit by Scott Chacon and Ben Straub,
  • Getting started (pages 5-18)
  • Git Basics (pages 19 - 56)

• if you have not done so already, go to Piazza and vote for the date of the midterm exam

• start looking for Wikipedia articles to which you can contribute (these could be small edits that fix broken links or typos, or something much more significant if you feel ready for it); next week you will need to include links to your edits in the blog posts

• make your next post (due Feb. 4, midnight), try to discuss the following ideas:

  • explain (in your own words) the difference between software development following the cathedral model and software development following the bazaar model; which of the two environments would you be more comfortable
  • The Cathedral and The Bazaar essay has 19 “lessons”. Pick two of these that you find to be the most intriguing, interesting, telling, or ones that you simply liked. Quote them in your blog and try to explain what they’re supposed to mean.

• read the materials posted for class 1 and 2 (note that some of them may be linked to from the slides).

• setup your course blog (due Jan. 28, midnight):
  • locate your repository in the class organization, it should be called YOUR_NETID-weekly
  • goto Settings and scroll down to GitHub Pages section
  • switch the None option to master branch
  • edit the about.md file to include some information about yourself (make sure that you are using mardown to format this page)
• make your first post (due Jan. 28, midnight)
  • in the _posts directory, edit 2018-01-28-week01.md file to update your first week blog post
  • answer the following points in your post (each item should be in its own section)
    • open source (what do YOU think about when you hear the term "open source"? what are some advantages of open vs. closed source, what are some potential problems with open source?)
    • projects: list names of four open source projects that you regularly use or that influenced you in some way in the past; give brief descriptions for each, explain why you use it and what the alternatives might be (note, the projects do not have to be source code based)
    • questions for Tom: come up with two (or more) questions that you would like to ask Tom Callaway from RedHat when he visits the class next week

• complete this questionnaire - if you do not have a GitHub account, create one first