Home

PSU CS 461/561

Open Source Software Development
Summer 2017 (Sections)

Things To Do:

• If you are not on the project list, it is almost too late! Contact me in class right away.

• Visit a Local Tech Event and write a report: http://calagator.org

  The event will ideally be related to Open Source at least in some vague way. The report should be just a paragraph or two describing who you visited and how it went. Submit your report via this Google Form.

• Prepare for your project presentation.

  Project presentations will be the last week of class. You are required to attend your assigned section for all class time that week. You must be prepared to present at your first class meeting. There are guidelines for your project presentation.

---

Welcome. This Wiki is dedicated to our project course in open source software development for the UNIX environment. The list of current projects is quite impressive.

This is a wiki. A wiki is a collaborative web site: once you're registered, you can (and should) help maintain these pages, and use the site as a work area. This wiki is hosted on GitHub under the project psu-oss-2017, which you and your summer project will join once you get started.

We will be using Slack as our primary course communications tool. You will be expected to be available to participate in the Slack discussion. You must use your @pdx.edu email address and your real name to sign up.

On the rare occasion that someone is hanging on IRC, they'll be at irc://irc.cat.pdx.edu:6667/osdl.

Much information is available at the pages of the 2016 offering of this course.

Other offerings that are still available: 2014, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007.

Contact Info

• [email protected] -- Bart Massey, your instructor.
• [email protected] -- For help with systems and software
• irc://irc.cat.pdx.edu -- Course IRC channel

User and Project Pages

Every developer/team should create a GitHub project under our organization. There's a list of things that should be in the project README.

Web Resources

• http://oss.cs.pdx.edu -- PSU OSS projects.
• http://www.cat.pdx.edu -- The PSU Computer Action Team.
• /. article -- OSS HOWTO (is this the original source?)
• On Naming an Open Source Project
• Ikiwiki Formatting -- Basic formatting for this Wiki engine.
• Git User's Manual -- Git Manual
• Official Git Tutorial -- Official Git Tutorial
• GIT troubleshooting guide- helps resolve ssh issues
• apply-license -- Bart's shell script for inserting license info into source code files. Thanks Bart!
• Open Source Licensing: Software Freedom and Intellectual Property Law by Lawrence Rosen
• The Case Against Patents
  • Bounty Hunters A fun metaphorical look at the evolution of patents
• Gitosis for git hosting A great way to host your own remote git repo
• A Little bit of OSS humor
• Really good hints for Vim from Bram

Entrepreneurship

• SCORE - Service Corps of Retired Executives: Great for general small-business advice, free.
• OTBC - Oregon Technology Business Center: Business startup incubator, great resources, cheap.
• PSBA - Portland State Business Accelerator: Don't know too much about their current status.
• Startup Weekend: Good way to get started in a friendly environment.
• Calagator: Go network.

Schedule

• Week 1, June 27-29:
  • Introduction, Projects
  • Project Setup
• Week 2, July 4-6:
  • July 4 is US Independence Day, no class meeting
  • Source Code Management with Git
• Week 3, July 11-13:
  • Scripting and Tools
  • Law and Ethics (slides)
• Week 4, July 18-20:
  • Debugging
  • Workflow
• Week 5, July 25-27:
  • Work Days
• Week 6, August 1-3:
  • Work Days
• Week 7, August 8-10:
  • Project Deployment
  • Business and Jobs
• Week 8, August 15-17:
  • Project Presentations

Final project requirements

Final project are due Friday of week eight of class at 5:00 PM. There will be no formal turn-in: instead, the project GitHub repository will be graded directly.

There is a checklist of project requirements. A deduction of between a half-grade and a full letter grade will generally be the result of failing to meet these requirements (especially the copyright/license requirement), so please use this checklist carefully.

---

A note on plagiarism: You are expected to follow the PSU student conduct code. Plagiarism is using other people's intellectual work (code, writing, ideas) without proper attribution. Open source is all about sharing code and ideas, but if you take them without saying where you got them you are a plagiarist; if I catch you I will be unimaginably unhappy.