Difference between revisions of "OSD600"
| Line 11: | Line 11: | ||
* Describe the history and philosophy of an open source project | * Describe the history and philosophy of an open source project | ||
* Choose between the various open source licenses understanding the implications for users, developers, and the software community in general | * Choose between the various open source licenses understanding the implications for users, developers, and the software community in general | ||
| − | * Use the communication modes particular to the open source world through participation in such things as GitHub, | + | * Use the communication modes particular to the open source world through participation in such things as GitHub, Slack, wikis, etc. |
* Use the tools of open source development, for example: distributed revision control; documentation tools; automated build and test systems; debuggers; source code utilities; tracking systems; on-line resources, etc. | * Use the tools of open source development, for example: distributed revision control; documentation tools; automated build and test systems; debuggers; source code utilities; tracking systems; on-line resources, etc. | ||
* Work with a pre-existing large source code base | * Work with a pre-existing large source code base | ||
| Line 19: | Line 19: | ||
==Major Project== | ==Major Project== | ||
| − | This is a project course, and the majority of each student’s mark will come from work done on a real development project. The primary goal of this project is to get students involved in the open source development community and its | + | This is a project course, and the majority of each student’s mark will come from work done on a real development project. The primary goal of this project is to get students involved in the open source development community and its codebases. Through this experience students will learn about the processes, tools, and practices involved in developing software as part of a large open source community. Students will also have the opportunity to contribute their own code to real-world software projects, thereby gaining important experience. |
===Philosophy=== | ===Philosophy=== | ||
| Line 25: | Line 25: | ||
Many of the practices inherent in open source development will seem to go against the structures often set in place for similar course work. For example, students are typically forbidden to collaborate with peers, to copy from the web, etc. However, these rules must be re-evaluated in the context of proper and pragmatic open source development practices. | Many of the practices inherent in open source development will seem to go against the structures often set in place for similar course work. For example, students are typically forbidden to collaborate with peers, to copy from the web, etc. However, these rules must be re-evaluated in the context of proper and pragmatic open source development practices. | ||
| − | First, consider the typical rules around cheating and plagiarism. In this | + | First, consider the typical rules around cheating and plagiarism. In this course, students are encouraged to work within the set of best practices natural to open source development. Open source developers do not write from scratch what already exists and is freely available for use. Students should be thinking in terms of code reuse. It is acceptable for students to use code from other open source projects, so long as the license is amenable to the use. |
Second, consider the typical restrictions on peer-collaboration. In this project students are encouraged to work together, to help one another, to look at each other's code, etc. Open source collaboration is about leveraging the collective knowledge of a community to help solve the problems of the individual. | Second, consider the typical restrictions on peer-collaboration. In this project students are encouraged to work together, to help one another, to look at each other's code, etc. Open source collaboration is about leveraging the collective knowledge of a community to help solve the problems of the individual. | ||
| Line 36: | Line 36: | ||
* Give others encouragement and credit when they offer help | * Give others encouragement and credit when they offer help | ||
* Use existing open source code whenever possible | * Use existing open source code whenever possible | ||
| − | * Be open to helping others and to being helped | + | * Be open to helping others and to being helped |
==Intellectual Property== | ==Intellectual Property== | ||
| Line 47: | Line 47: | ||
* '''80%''' - Project Deliverables (e.g., code, Pull Requests, documentation), marked in terms of quality, quantity, process, etc. | * '''80%''' - Project Deliverables (e.g., code, Pull Requests, documentation), marked in terms of quality, quantity, process, etc. | ||
| − | ** '''10%''' - [[OSD & DPS909 | + | ** '''10%''' - [[OSD & DPS909 Fall 2019 - Release 0.1|Release 0.1]] due Fri, Sept 20 |
| − | ** '''30%''' - [[OSD & DPS909 | + | ** '''30%''' - [[OSD & DPS909 Fall 2019 - Release 0.2|Release 0.2]] due Thurs, Oct 31 |
| − | ** '''20%''' - [[OSD & DPS909 | + | ** '''20%''' - [[OSD & DPS909 Fall 2019 - Release 0.3|Release 0.3]] due Wed, Nov 20 |
| − | ** '''20%''' - [[OSD & DPS909 | + | ** '''20%''' - [[OSD & DPS909 Fall 2019 - Release 0.4|Release 0.4]] due Fri, Dec 6 |
| − | * '''20%''' - Labs | + | * '''20%''' - Labs: will be marked using a Pass/Fail rubric (i.e., no subjective grading will be applied). Students are expected to complete all course labs in order to pass the course. |
==Resources== | ==Resources== | ||
| − | * [[DPS909 & OSD600 | + | * [[DPS909 & OSD600 Fall 2019]] |
* [https://seneca-open-source.slack.com Seneca Open Source Slack] (sign-up with your @myseneca.ca email) | * [https://seneca-open-source.slack.com Seneca Open Source Slack] (sign-up with your @myseneca.ca email) | ||
* [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet] | * [http://zenit.senecac.on.ca/~chris.tyler/planet/ Open Source@Seneca Planet] | ||
Revision as of 13:55, 1 September 2019
Contents
Topics in Open Source Development
Subject Description
This course introduces students to the technological, social, and pragmatic aspects of developing open source software through direct involvement in large open source projects. Students will learn to use the tools, techniques, and strategies of open source developers. This is a project-based programming course.
Course Outcomes
Upon successful completion of this course students should be able to:
- Discuss the issues and currents in open source and open source development
- Describe the history and philosophy of an open source project
- Choose between the various open source licenses understanding the implications for users, developers, and the software community in general
- Use the communication modes particular to the open source world through participation in such things as GitHub, Slack, wikis, etc.
- Use the tools of open source development, for example: distributed revision control; documentation tools; automated build and test systems; debuggers; source code utilities; tracking systems; on-line resources, etc.
- Work with a pre-existing large source code base
- Write software that integrates and interacts with existing open source systems. For example: add-ons; bug fixes; new features; etc.
- Work collaboratively with fellow students and members of the open source community.
Major Project
This is a project course, and the majority of each student’s mark will come from work done on a real development project. The primary goal of this project is to get students involved in the open source development community and its codebases. Through this experience students will learn about the processes, tools, and practices involved in developing software as part of a large open source community. Students will also have the opportunity to contribute their own code to real-world software projects, thereby gaining important experience.
Philosophy
Many of the practices inherent in open source development will seem to go against the structures often set in place for similar course work. For example, students are typically forbidden to collaborate with peers, to copy from the web, etc. However, these rules must be re-evaluated in the context of proper and pragmatic open source development practices.
First, consider the typical rules around cheating and plagiarism. In this course, students are encouraged to work within the set of best practices natural to open source development. Open source developers do not write from scratch what already exists and is freely available for use. Students should be thinking in terms of code reuse. It is acceptable for students to use code from other open source projects, so long as the license is amenable to the use.
Second, consider the typical restrictions on peer-collaboration. In this project students are encouraged to work together, to help one another, to look at each other's code, etc. Open source collaboration is about leveraging the collective knowledge of a community to help solve the problems of the individual.
Third, consider the sharp dividing line between student projects in most programming courses. For the most part, students are evaluated on their ability to do a particular project or to solve a particular problem on their own. The outcome is measured against peer outcomes. However, in this course students are not in competition with their peers; rather, they are all working on one large project (e.g., Mozilla) with many sub-projects within it. As a result, there is no clean line to divide one student’s work from another, or even student work from that of the open source community. This means that collaboration between students and even other members of the open source community is acceptable practice.
To summarize, students should:
- Help each other, contribute to one another’s projects
- Work with and within the open source community
- Give others encouragement and credit when they offer help
- Use existing open source code whenever possible
- Be open to helping others and to being helped
Intellectual Property
Given that this course is focused on open source development, and given that students work on real open source codebases, all student work will become open source. The particular license used will be determined based on the particular project and open source project.
Grading
Detailed grading information will be discussed later in the term. Below is a breakdown of how students will be graded, and this blog post gives more details about the rationale:
- 80% - Project Deliverables (e.g., code, Pull Requests, documentation), marked in terms of quality, quantity, process, etc.
- 10% - Release 0.1 due Fri, Sept 20
- 30% - Release 0.2 due Thurs, Oct 31
- 20% - Release 0.3 due Wed, Nov 20
- 20% - Release 0.4 due Fri, Dec 6
- 20% - Labs: will be marked using a Pass/Fail rubric (i.e., no subjective grading will be applied). Students are expected to complete all course labs in order to pass the course.
Resources
- DPS909 & OSD600 Fall 2019
- Seneca Open Source Slack (sign-up with your @myseneca.ca email)
- Open Source@Seneca Planet
Archives
- OSD600 Fall 2007
- OSD600 Fall 2008
- DPS909 and OSD600 Fall 2008 Weekly Schedule
- OSD600 Winter 2009
- OSD600 Fall 2009
- OSD600 Fall 2010
- OSD600 Summer 2010
- OSD600 Fall 2011
- OSD600 Fall 2012
- OSD600 Fall 2013
- OSD600 Fall 2015
- OSD600 Winter 2017
- OSD600 Fall 2017
- OSD600 Winter 2018
- OSD600 Fall 2018
- OSD600 Winter 2019
