Difference between revisions of "SBR600"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) (→Software Build and Release - SBR600) |
||
| Line 6: | Line 6: | ||
= Software Build and Release - SBR600 = | = Software Build and Release - SBR600 = | ||
| − | [[Category:SBR600]]This is a professional option in the CTY program. It has been offered since January 2009. | + | [[Category:SBR600]]Software build and release is the process of building (compiling, testing, and packaging) software for testing or in preparation for release, and the release and distribution of the built software and updates. |
| + | |||
| + | This course is a professional option in the [http://scs.senecac.on.ca/ Seneca School of Computer Studies] CTY program. It has been offered since January 2009. | ||
== SBR600 in Winter 2011 == | == SBR600 in Winter 2011 == | ||
| − | 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 Winter 2010 SBR600 class and continued in Fall 2010, 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. | + | This semester, students will be working directly with the Fedora project and other open source communities, on various build and release projects. Some of this work will be centered on the [[Fedora ARM Secondary Architecture]] project started by the Winter 2010 SBR600 class and continued in Fall 2010, 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 [[SBR600 Communication Tools|communication tools]]. Work performed in this course will be licensed using the relevant open source licenses used by the associated community. | 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 [[SBR600 Communication Tools|communication tools]]. Work performed in this course will be licensed using the relevant open source licenses used by the associated community. | ||
| + | |||
| + | Working in an open source community provides the opportunity to build solid real-world experience, your technical skills and reputation, and a network of contacts, all of which are useful in developing your career. | ||
This semester, in late January, some representatives from Seneca will be attending [[FUDCon Tempe 2011]] (Tempe AZ). | This semester, in late January, some representatives from Seneca will be attending [[FUDCon Tempe 2011]] (Tempe AZ). | ||
| Line 18: | Line 22: | ||
=== Course Materials === | === 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. | + | Students will require access to a personal Fedora 13 or Fedora 14 installation, either on their own laptop, on a virtual machine on their laptop, or on a SATA disk pack. |
=== Professor === | === Professor === | ||
| Line 26: | Line 30: | ||
=== Succeeding in SBR600 === | === Succeeding in SBR600 === | ||
| − | There are | + | There are three 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. | 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 is 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 is submitted by blogging. | ||
| + | |||
| + | 3. '''Be ambitious.''' In this course, you will need to be the driving force behind your project. The community will help you, but it's up to you to supply the energy. It's best to plan to make a bit of progress each day. | ||
== Weekly Outline == | == Weekly Outline == | ||
Revision as of 16:33, 14 December 2010
| Quick Links |
|---|
| Participants and Project Table Potential Project List Fedora ARM Secondary Architecture Course Outline Fedora Project Fedora documentation |
Contents
Software Build and Release - SBR600
Software build and release is the process of building (compiling, testing, and packaging) software for testing or in preparation for release, and the release and distribution of the built software and updates.This course is a professional option in the Seneca School of Computer Studies CTY program. It has been offered since January 2009.
SBR600 in Winter 2011
This semester, students will be working directly with the Fedora project and other open source communities, on various build and release projects. Some of this work will be centered on the Fedora ARM Secondary Architecture project started by the Winter 2010 SBR600 class and continued in Fall 2010, 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.
Working in an open source community provides the opportunity to build solid real-world experience, your technical skills and reputation, and a network of contacts, all of which are useful in developing your career.
This semester, in late January, some representatives from Seneca will be attending FUDCon Tempe 2011 (Tempe AZ).
Course Materials
Students will require access to a personal Fedora 13 or Fedora 14 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 (Winter 2011)
Succeeding in SBR600
There are three 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 is submitted by blogging.
3. Be ambitious. In this course, you will need to be the driving force behind your project. The community will help you, but it's up to you to supply the energy. It's best to plan to make a bit of progress each day.
Weekly Outline
See the Winter 2011 SBR600 Weekly Schedule for specific dates and topics.
Course Outline
See the online course outline for course details.
