Open Source Software Development Fall 2018, Hunter College, Stewart Weiss
(Difference between revisions)
Line 38: | Line 38: | ||
=== Course Outline === | === Course Outline === | ||
− | + | # Context and Overview | |
− | + | ## Open-ness in general: open source, open data, open hardware, etc. | |
− | + | ## History and background of open source software | |
− | + | ## Open source culture and community | |
+ | # Contributing to Projects | ||
+ | ## Early and Easy Contributions | ||
+ | #* open wikis | ||
+ | #* open maps | ||
+ | ## Types of contributions to software projects | ||
+ | ## Ways of getting involved | ||
+ | # Tools and Technology | ||
+ | ## Programming Tools and Technology | ||
+ | #* markdown, make, gdb, Unix shells | ||
+ | ## Software engineeering tools required for group software projects | ||
+ | #* version control systems (e.g., git) | ||
+ | #* issue tracking | ||
+ | #* documentation tools (e.g., Doxygen) | ||
+ | ## Software engineering tools specific to distributed group projects | ||
+ | #* communication tools | ||
+ | #* remote, distributed version control (GitHub) | ||
+ | #* online, web-based issue trackers | ||
+ | # Intellectual Property Rights and Licensing | ||
+ | ## types of licenses | ||
+ | ## licensing your own work | ||
+ | ## avoiding plagiarism | ||
+ | # Project Evaluation and Studies | ||
+ | #* Evaluating the suitability of a project for the purpose of their contributing to it. | ||
+ | # Team Selection | ||
+ | # Project Selection/Assignment | ||
+ | ## Getting involved in the community | ||
+ | ## Setting up project development environment | ||
+ | ## Picking some issues to work on | ||
+ | ## Solving the issues and issuing pull requests | ||
+ | # Team Reports | ||
=== Notes to Instructor === | === Notes to Instructor === |
Revision as of 18:16, 13 January 2019
This page is under construction. For now the important information is the following link.
http://www.compsci.hunter.cuny.edu/~sweiss/course_materials/csci132/csci132_f18.php
Contents |
Overview
Course | Open Source Software Development, http://www.compsci.hunter.cuny.edu/~sweiss/course_materials/csci132/csci132_f18.php |
---|---|
Institution | Hunter College, CUNY, New York City |
Instructor(s) | Stewart Weiss, email: stewart.weiss@hunter.cuny.edu, http://www.compsci.hunter.cuny.edu/~sweiss |
Term | Fall 2018 |
Course Overview | An elective course for students who want to learn how to contribute to open source software projects |
Course Length | 15-week term |
Student Characteristics | mostly upper juniors and seniors, small size classroom (holds 20) |
Prerequisites | A data structures course |
Infrastructure | Held in a conference room with each student bringing a laptop |
Learning Objectives
- the student will become a contributing member of a software development community and have documented evidence of their contribution; and
- the student will document their efforts on this project by creating a blog that chronicles their work.
Assessment Methods
- contributions (30%) such as pull requests that have been accepted, or those that were not accepted but, deserve to be treated as if they were accepted;
- homework (30%) submitted in response to assignments that I post on the website or distribute in class;
- participation (40%) including attending meetings, completing the weekly blog posts, and oral presentations made to the group
Course Outline
- Context and Overview
- Open-ness in general: open source, open data, open hardware, etc.
- History and background of open source software
- Open source culture and community
- Contributing to Projects
- Early and Easy Contributions
- open wikis
- open maps
- Types of contributions to software projects
- Ways of getting involved
- Tools and Technology
- Programming Tools and Technology
- markdown, make, gdb, Unix shells
- Software engineeering tools required for group software projects
- version control systems (e.g., git)
- issue tracking
- documentation tools (e.g., Doxygen)
- Software engineering tools specific to distributed group projects
- communication tools
- remote, distributed version control (GitHub)
- online, web-based issue trackers
- Intellectual Property Rights and Licensing
- types of licenses
- licensing your own work
- avoiding plagiarism
- Project Evaluation and Studies
- Evaluating the suitability of a project for the purpose of their contributing to it.
- Team Selection
- Project Selection/Assignment
- Getting involved in the community
- Setting up project development environment
- Picking some issues to work on
- Solving the issues and issuing pull requests
- Team Reports
Notes to Instructor
- Tips, suggestions, lessons learned (warnings)...
Moving Forward
- what next steps are desirable or possible for this course
For this blank format: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License