DPS909 and OSD600 Fall 2013 Notes

From CDOT Wiki
Revision as of 14:01, 5 November 2013 by Nmayuranathan (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


The fall is broken into two parts. First, general open source and and community (i.e., Mozilla) specific skills and ideas are taught. Students learn how to deal with the tools, techniques, and practices of their chosen project and its community. Second, we go deep into open web development with a case study.

Part I – Essential Open Source Development Skills and Concepts


  • TODO
    • Create an account on this wiki for yourself (note: requires manual creation)
    • Add your info to the Fall 2013 Open Source Students page.
    • Create a blog (wordpress or blogspot or whatever) and create a feed category or tag called "open source"
    • Read the Blog Guidelines for instructions on how to use your blog in the course
    • Add your blog feed and info to the Open Source@Seneca Planet List so that it appears in the OpenSource@Seneca Planet
    • Pick one Closed and one Open license/eula, and read them from start to finish. Pick 3 things that struck you, blog about it and your reactions to the readings this week.
    • Begin learning how to use IRC for communication. We'll cover this in detail next week, but it's better to get started early.

Mozilla, Git

  • TODO
    • Start learning git!: Watch video tutorials and/or Read chapters 1 and 2 of Pro Git, etc.
    • Install and Setup git locally
    • Get a project: Project List (projects will be introduced on Thursday)
      • What is it?
      • What are you doing for 0.1?
      • What does it involve in the way of technologies?
      • What do you need to learn in order to do it, how will you learn it?
      • What fears or concerns do you have?
    • Setup ssh keys on matrix for your github account

Learning Git

Release 0.1

  • Everything you need for your first release:
    • A blog post titled "Release 0.1" which includes a write-up of what you did, your results, links to resources and material/code/commits/bugs/etc you have created.
    • If you've tried something and failed, please document that too (failing to get something going on the first try isn't the same as failing in general).
    • If you have finished a code change, make sure you get it into a bug and ask for review
    • An actual release of one form or another. That is, code in github or the like. You need to have something to show.
    • Due: Friday Sept 27th, but will be accepted until Monday Sept 30th without penalty.

Part 2 – Adobe Brackets