Changes

|<div style="background:#ffff00">[[Fall 2010 2013 SBR600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2013 SBR600 Participants|Participants and Project Table]]<br/>[[Fedora ARM Secondary ArchitectureSBR600 Potential Projects|Potential Project List]]<br />[[Fall 2013 SBR600 Presentation Schedule|Release Presentation Schedule]]<br />[https://scs.senecac.on.ca/course/sbr600 Course Outline]<br />[[Fedora ARM Secondary Architecture]]<br />[http://pidora.ca Pidora]<br />[http://fedoraproject.org Fedora Project]<br />[http://docs.fedoraproject.org/ Fedora documentation]<br />[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]<br />[http://koji.fedoraproject.org Fedora Koji]<br />[http://koji.pidora.ca Pidora Koji]

[[Category:SBR600]]This Software build and release is a professional option the process of building (compiling, testing, and packaging) software for further testing or in preparation for release, and the release and distribution of the CTY program. It has been offered since January 2009built software and updates.

== SBR600 This course is a professional option in Fall 2010 ==the [http://scs.senecacollege.ca/ Seneca School of Information and Communication Technology] [https://scs.senecac.on.ca/cty CTY] program. It has been offered since January 2009.

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.in Fall 2013 ==

In SBR600, you'll be working directly with the Fedora project and other open source communities, on various build and release projects. This semester, most projects will focus on improvements to [http://pidora.ca Pidora], a [[:fedora:Fedora Remix|Fedora Remix]] for the [http://raspberrypi.org Raspberry Pi]. Note that, unlike some other project-based courses, the results of the projects done in SBR600 will be incorporated into Pidora, 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.

Students * Course information and labs are online.* You will require access to a personal Fedora 18 or Fedora 19 installation, either . This may be on their your own laptop, on a virtual machine on their your laptop, on an SSH-accessible system (such as a home desktop computer), or on a SATA disk packor USB drive for use with the Seneca computers.* Recommended (optional): [[Purchase a Raspberry Pi]]

SBR600 is taught by [[User:Chris Tyler|Chris Tyler]] (Fall 2010).

There are two 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.

12. '''Work in the open source communityBlog.''' The projects we will be doing are too large and too unfamiliar for you to succeed entirely on Tell your own. You will need to use the community's knowledgeprofessor, connectionsyour colleagues, and resources to succeed well. Respect the community's standards, tell the community and everyone else what you're doing. Write a lot and write well, ask when you have a questioninclude good technical content, and incorporate links to all relevant resources and the product of your work, and pull write often. Almost all of your own weight within the communitywork in this course is submitted by blogging.

23. '''BlogBe ambitious.''' Tell your professorIn this course, you will need to be the driving force behind your colleagues, the project. The communitywill help you, and everyone else what but it's up to you're doing. Write well, include good technical content, and incorporate links to all relevant resources and supply the product of your workenergy. Most '''It's best to plan to make a bit of your work in this course are submitted by bloggingprogress each day.'''

== [[Fall 2010 SBR600 Weekly Schedule|Weekly Outline]] ==

See the [[Fall 2010 2013 SBR600 Weekly Schedule]] for specific dates and topics.

See the online [https://scs.senecac.on.ca/course/sbr600 Course Outlinecourse outline] for course details.