1,885
edits
Changes
→SBR600 Only: Practical quiz
{{Admon/important|Tentative Schedule - Fall 2012|Please note that the schedule here is tentative. Week-by-week details will be added as the course progresses.}}
This is the Fall 2012 weekly schedule for the [[DPI908]] and [[SBR600]] courses.
Previous semester: [[Winter 2012 SBR600 Weekly Schedule]]
<!-- ---------------------------------------------------------------------------------------------- Week 1 ------------ -->
= Week 1 (September 3) - Introduction === Wednesday (September 5) ==
=== Welcome ===
* About this course
# [[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 - Building from Source & RPM Packaging = == Monday (September 10) ==
=== Using ''make'' ===
# Send your [[SSH]] public key to your professors so they can create accounts for you on the [[CDOT Development Systems]].
==== Creating an RPM Package ====
=== To Do ===
By '''TuesdayMonday, January 24September 17''':
* [[DPI908/SBR600 RPM-Writing Lab|RPM-Writing Lab]]
<!-- ---------------------------------------------------------------------------------------------- Week 3 ------------ -->
= Week 3 (Jan 24) - The Fedora Build System =# [[SBR600 Mock and Koji Lab]], Signing and Repos =
== Tuesday Monday (September 17) == === Mock === Mock is a tool which builds a package using rpmbuild in a 'cleanroom' environment. This has several advantages:* it tests the completeness of the BuildRequires in the spec file* it avoids the installation of a lot of tools (BuildRequires) on the main host system* it permits different tools and tool versions to be used for the build than are installed on the host (e.g., building for F18 on an F16 system) Background information on using Mock:* [[:fedora:Using_Mock_to_test_package_builds|Using Mock to test package builds]] === Using Koji to Test on Multiple Architectures === * [[:fedora:PackageMaintainers/UsingKoji|Using Koji]] === To Do === By '''Wednesday, September 19''':# [[DPI908/SBR600 Mock Lab|Mock Lab]]# [[DPI908/SBR600 Koji Lab|Koji Lab]]
=== Guest Lecturer: Dennis Gilmore, Fedora Release Engineer, Red Hat, Inc. =Wednesday (September 19) ==Dennis is Fedora's release engineer. He will be visiting Seneca Centre for Development of Open Technology (CDOT) this week and has agreed to give a guest lecture on Tuesday.
== Thursday = To Do ===
<!-- ---------------------------------------------------------------------------------------------- Week 4 ------------ -->
=Week 4 = 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 ===
=== Creating a Repository-release RPM =Monday (October 15) ==
=== ToDo Python Primer ===
[[SBR600 Python Lab# Create a signed repository containing your RPM package.# Create an RPM package that will install your repository configuration file and the key (repository-release package).# Test it.# Blog about this lab, and include a link to your repository-release package and the repository URL.|Python Lab]]
== Thursday =Study Week and FSOSS =
= 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.
== 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]]