1,885
edits
Changes
→SBR600 Only: Practical quiz
Previous semester: [[Winter 2012 SBR600 Weekly Schedule]]
<!-- ---------------------------------------------------------------------------------------------- Week 1 ------------ -->= Week 1 (Jan 10) - Introduction === Tuesday Wednesday (September 5) ==
=== Welcome ===
* About this course
=== Intro to DPI908/SBR600 - Software Build & Release ===
* [[DPI908/SBR600 Overview of the Build and Release Process|Brief overview of the Build & Release process]]
* Introduction to the Fedora Project
** [[:fedora:Main Page|Fedora Project]]
** Working with the Fedora Project
** [[SBR600|Course Outline]]
** [[DPI908|Course Outline]]
* How this Course Works
** [[DPI908/SBR600 Communication Tools]]
** How coursework is submitted
* Differences between [[DPI908 ]] and [[SBR600]]* Future** Winter 2013 Semester*** Project continuation course** Upcoming Events*** [http://fsoss.ca Free Software and Open Source Symposium 2012]*** [[:fedora:FUDCon:Lawrence_2013|FUDCon Lawrence 2013]]
=== To Do ===
'''By Monday, September 10:'''# [[DPI908/SBR600 Communication Lab|Communication Lab]]# [[DPI908/SBR600 Fedora Installation|Fedora Installation]] {{Admon/important|CDOT Wiki Issues|There is an issue with some email sent from the CDOT Wiki system to MySeneca email accounts. This will prevent important e-mail such as initial temporary passwords, e-mail confirmations, and password resets from being received. This issue is currently being examined by Seneca ITS and we expect a resolution soon. '''The deadline for the communication lab is being extended due to this issue.'''}} <!-- ---------------------------------------------------------------------------------------------- Week 2 ------------ --> = Week 2 (Jan 17) - Building from Source & RPM Packaging, Mock, and Koji =
== Tuesday Monday (September 10) ==
=== Using ''make'' ===
* [[SBR600 make and Makefiles|make Make and Makefiles]]
=== Building from Source ===
* [[RPM Queries|Querying the RPM database]]
==== Creating an RPM Package =Using SSH === * Using [[RPM Packaging ProcessSSH]]- a Review** Using public/private keypairs** Passphrase protection** Keyrings
==== Resources ====
=== To Do ===
By '''ThursdayWednesday, January 19September 12''':# [[DPI908/SBR600 Build-from-Source Lab|Build-from-Source Lab]]# [[SBR600 RPM-Writing Lab|RPM-Writing Lab]]# Send your [[SSH]] public key to [[User:Chris Tyler|your professor]] professors so he they can create accounts for you on the [[CDOT Development Systems]]. == Wednesday (September 12) == ==== Creating an RPM Package ==== * [[RPM Packaging Process]] === To Do === By '''Monday, September 17''':* [[DPI908/SBR600 RPM-Writing Lab|RPM-Writing Lab]] <!-- ---------------------------------------------------------------------------------------------- Week 3 ------------ -->= Week 3 - Mock and Koji, Signing and Repos =
== Thursday Monday (September 17) ==
=== Mock: Testing BuildRequires ===
=== To Do Using Koji to Test on Multiple Architectures ===
=== To Do ===
== Tuesday Wednesday (September 19) ==
==== The Fedora Build System ======== How Koji Works =To Do ===
= Week 4 (Jan 31) =
== Tuesday/Thursday Monday (September 24) and Wednesday (September 26) ==
=== Project Selection ===
* Link your project title on the [[Winter 2012 SBR600 Participants|participants page]] to a page of the same name to create a project page. Copy the contents of the [[Sample Project]] page to your project page and fill in the details.
** Release 0.1: Proof of concept (e.g., a first draft of a package, a basic script, infrastructure set up on a test system) - Note that this must include the release of ''something'', not just research, and must be done in consultation with the community.
** Release 0.2: Initial working state - Whatever you are working on -- package, script, infrastructure configuration -- should be working, although it may not be feature-complete, fully deployed, or fully documented. Feedback from the community should be solicited. If there is a review process required to submit upstream, it should be started.
** Release 0.3: Completed working state - The work is complete and documented. Any upstream review, whether formal or informal, has been completed, feedback has been incorporated into the project, and the work has been committed beento the appropriate repositories (or released in an appropriate manner).
* You must have a strategy in place for reaching your targets.
== Tuesday =To Do === * Prepare your project page and project plan presentation.
=== Creating a YUM repository ==Week 5 =
=== Testing ==Week 7 =
=== Creating a Repository-release RPM Using GIT ===
=Week 9-13 == * Project Plan Presentations (work* Schedule:** 0.1 Milestone: TBA** 0.2 Milestone: TBA** 0) ===.3 Milestone: TBA
= Week 9 - O.1 Release Presentation =* Project pages are due. Link from the ''Projects'' column of the Please book your time slot on [[Winter Fall 2012 DPI908/SBR600 Participants]] table to a Presentation Schedule| the presentation schedule page for your project; use the [[Sample Project]] template for your project page, and fill in as much detail as possible.* Be prepared to give a professional, detailed, but very brief (2- to 4-minute) presentation on your project plan. Include:** Your approach to the problem.** Contacts and resources you've identified.** Your plans for each release. Note that at each release you will be expected to actually '''release''' something -- an RPM, a script, test results -- as appropriate to your projectfirst come first server basis. Identify what you are intending to release at each stage:*** 0.1 Release - proof of concept*** 0.2 Release - initial functionality*** 0.3 Release - tested and usable** Challenges and potential pitfalls that you have identified, and your approach to mitigating those challenges so that you can complete your project on time regardless of things beyond your control.** Time for a brief Q&A/Feedback session at the endEach presentation should take no more than 10 minutes.
= Week 6 (Feb 14) 11 - 0.2 Release Presentation =* Please book your time slot on [[Fall 2012 DPI908/SBR600 Presentation Schedule| the presentation schedule page]] on a first come first server basis.* Each presentation should take no more than 10 minutes.
=Week 12 - Practical Quiz / Research Paper Discussion = Tuesday == Wednesday ===== Using GIT '''SBR600 Only''': Practical quiz ===* The quiz consists of one task: you will need to update an RPM to the latest upstream version of the software. For example, if the package is foo-2-1 and there is a new upstream version 3 of foo available, you will need to produce a foo-3-1 package. It would be worthwhile practicing this task in advance.* The practical quiz will be in T3076 (which not our normal room) so that lab computers will be available.* Make sure that you have access to your Fedora system, either on your laptop, on a removable disk pack, or through an SSH connection to one of your computers at home. Verify your arrangements! You may want to bring a Fedora Live system on USB or DVD as a backup.* You may use your notes and online resources during the quiz. However, you may not share information with other people during the quiz.
== Thursday ='''DPI908 Only''': Discussion about the [[DPI908 Research Paper]] ===* Meet in the usual room
=Week 13 - Wrap-up == To Do ===GIT Lab* Clone the repository at ssh://sbr600@scotland.proximity.on.ca/~/certs/* Add your cert using the instructions in the readme.txt file.* Blog about your experience.
* The 0.3 Presentations are '''CANCELLED'''. Your 0.3 release is still due on '''December 8 at 11:59 pm.'''== Monday = Week 7 (Feb 21) =
== Wednesday ==
* Wrap-up - final opportunity to get help and feedback on your 0.3 release
<!--
= Exam Week =
-->
= Guest Lecture Notes =
* [[DPI908/SBR600 Guest Lecture-Paul Whalen-20121119]]