Welcome. Here is the course description from the RIT website:
Undergraduate Seminar in IGM is intended to allow for special one-time offerings of undergraduate topics or to allow faculty to pilot new undergraduate offerings. Specific course details (such as the course topics, format, resource needs, and credit hours) will be determined by the faculty member(s) who propose a given special-topics offering.
This year, IGM Faculty have determined these details as folows:
At the heart of this course are 5-week release cycles. Unlike the RIT HFOSS course, that focuses on one large team project, this course will have multiple tightly-scoped project releases (or "hacks".)
Release Cycle Breakdown
|Week 1||Ideation and Proposal. Community Contribution Assigned.|
|Week 2||Development. Community Contribution Due.|
|Week 4||Testing and Documentation|
|Week 5||Packaging and Release|
Each cycle will include a community contribution assignments, in addition to each hack.
All code developed by students in the course must be licensed (by the student) under any one of the licenses approved by the Open Source Initiative.
Your code that you write is your code, with which you can do what you will; true. However, if you’re unwilling to license code you write for a Free/Open Source course with a Free/Open Source license, you may be in the wrong course.
Not only will students be releasing their own projects, they will also be contributing to other projects and communities as well. These contributions will fall into one of four categories:
Assignments are due at 4:59pm of the day they are marked as due, to be useful in class.
Late submissions will be deducted 10% per day they are late.
Your final grade for the semester will be derived from the following weights.
|FOSS Dev Practices (Blog posts, commits, tickets, IRC)||25%|
All texts will be made available via the Open Educational Resources page.
Final Course Grades
Attendance is required for this course. Students are allotted 2 excused absences per semester.
Subsequent absences will result in a 10% reduction of your final letter grade for each class missed.
Blog updates – students are required to keep a blog to which they post updates about their investigations, progress, success, and pitfalls. This blog can be hosted anywhere, but must be added to the course participant page (there are instructions on how to do this in Homework - First Flight).
- You must make at least one blog post per week to receive full credit. A week Ends on Sunday at 11:59pm.
- You must participate regularly in the course’s IRC channel: asking and answering questions.
- Contributions to the course curriculum, syllabus, and rubric are factored in here as well.
Blogging is good for you and good for the FLOSS community at large.
Every class for the first portion of class, any student has the opportunity
to give a
lightning talk on a
topic of their chosing. Your lightning talk must be less than 5 minutes in
length and must be at least remotely related to the course material.
You will receive +1 extra credit points towards your final grade for every
lightning talk you give. Only the first 2 lightning talks offered will be allowed during a given
class. Talks will be chosen from among those offered by students on a