Difference between revisions of "SBR600"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
Line 30: | Line 30: | ||
2. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. Write well, include good technical content, and incorporate links to all relevant resources and the product of your work. Most of your work in this course are submitted by blogging. | 2. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. Write well, include good technical content, and incorporate links to all relevant resources and the product of your work. Most of your work in this course are submitted by blogging. | ||
− | == | + | == Weekly Outline == |
See the [[Fall 2010 SBR600 Weekly Schedule]] for specific dates and topics. | See the [[Fall 2010 SBR600 Weekly Schedule]] for specific dates and topics. | ||
Line 36: | Line 36: | ||
= Course Outline = | = Course Outline = | ||
− | See the online [https://scs.senecac.on.ca/course/sbr600 | + | See the online [https://scs.senecac.on.ca/course/sbr600 course outline] for course details. |
Revision as of 13:15, 30 August 2010
Quick Links |
---|
Weekly Schedule Fedora ARM Secondary Architecture Course Outline Fedora Project Fedora documentation |
Contents
Software Build and Release - SBR600
This is a professional option in the CTY program. It has been offered since January 2009.SBR600 in Fall 2010
This semester, students will be working directly with the Fedora project, on various build and release projects. Some of this work will be centered on the Fedora ARM Secondary Architecture project started by the January 2010 SBR600 class, and the rest of the projects will focus on other aspects of the Fedora build process. The skills required will vary according to the project selected.
Note that, unlike some other project-based courses, the results of the projects done in SBR600 will be incorporated into the Fedora project (or other open source projects) and have a real impact on other people. For this reason, projects must be completed in collaboration with the relevant open source communities, using relevant communication tools. Work performed in this course will be licensed using the relevant open source licenses used by the associated community.
Course Materials
Students will require access to a personal Fedora installation, either on their own laptop, on a virtual machine on their laptop, or on a SATA disk pack.
Professor
SBR600 is taught by Chris Tyler (Fall 2010)
Succeeding in SBR600
There are two keys to success in this course:
1. Work in the open source community. The projects we will be doing are too large and too unfamiliar for you to succeed entirely on your own. You will need to use the community's knowledge, connections, and resources to succeed well. Respect the community's standards, tell the community what you're doing, ask when you have a question, and pull your own weight within the community.
2. Blog. Tell your professor, your colleagues, the community, and everyone else what you're doing. Write well, include good technical content, and incorporate links to all relevant resources and the product of your work. Most of your work in this course are submitted by blogging.
Weekly Outline
See the Fall 2010 SBR600 Weekly Schedule for specific dates and topics.
Course Outline
See the online course outline for course details.