Difference between revisions of "Fall 2009 SBR600 Weekly Schedule"

From CDOT Wiki
Jump to: navigation, search
(Initial Text)
 
(Added detail and corrected dates.)
Line 2: Line 2:
 
* The schedule here is tentative.
 
* The schedule here is tentative.
 
* Week-by-week details will be filled in as the course progresses.
 
* Week-by-week details will be filled in as the course progresses.
 
  
 
= Week 1 (September 8) - Introduction =
 
= Week 1 (September 8) - Introduction =
Line 39: Line 38:
  
 
== ToDo: ==
 
== ToDo: ==
Communication Lab: By Thursday, September 10, Set up your accounts (wiki, IRC, FAS2).
+
'''Communication Lab: By Wednesday, September 9, Set up your accounts (wiki, IRC, FAS2).'''
 
* Create a blog post which will appear on the OpenSource@Seneca Planet, containing:
 
* Create a blog post which will appear on the OpenSource@Seneca Planet, containing:
 
** A portion of an IRC conversation you've had with someone on a Fedora or Seneca IRC channel.
 
** A portion of an IRC conversation you've had with someone on a Fedora or Seneca IRC channel.
Line 46: Line 45:
 
* Add an entry to the [[Fall 2009 SBR600 Participants]] page
 
* Add an entry to the [[Fall 2009 SBR600 Participants]] page
  
Register for [[http://fsoss.ca/ FSOSS]].
+
'''Register for:'''
 +
* [http://fsoss.ca/ FSOSS]]
 +
* [[:fedora:FUDCon:Toronto_2009|FUDCon Toronto 2009]]
  
Lab 1: By Tuesday, September 15:
+
'''Lab 1: By Tuesday, September 15:'''
 
* Build 2 packages from Source
 
* Build 2 packages from Source
 
** The NLED editor from [http://cdot.senecac.on.ca http://cdot.senecac.on.ca]
 
** The NLED editor from [http://cdot.senecac.on.ca http://cdot.senecac.on.ca]
Line 61: Line 62:
 
-->
 
-->
  
= Week 3 (September 22) - Creating RPM Packages =
+
= Week 3 (September 22) - Creating RPM Packages I =
  
 
<!--
 
<!--
Line 163: Line 164:
  
 
* Take the software you compiled last week and package it (not Nled!). Blog about the experience. Include a link to your source RPM (and optionally your binary RPM) from your blog.
 
* Take the software you compiled last week and package it (not Nled!). Blog about the experience. Include a link to your source RPM (and optionally your binary RPM) from your blog.
 +
-->
  
= Week 4 (September 29) =
+
= Week 4 (September 29) - Creating RPM Packages II=
  
 
<!--
 
<!--
Line 224: Line 226:
 
-->
 
-->
  
= Week 5 (February 9) =
+
= Week 5 (October 6) - Compositing =
  
= Week 6 (February 16) =
+
= Week 6 (October 13) - Distributing =
  
 
<!--
 
<!--
Line 239: Line 241:
 
-->
 
-->
  
= Week 7 (February 23) =
+
= Week 7 (October 20) - Server Farms I =
 +
 
 +
= Study Week (October 27) =
  
= Study Week (March 2) =
+
* [http://fsoss.ca FSOSS 2009]
 +
* [http://opensourceweek.ca Toronto Open Source Week]
  
= Week 8 (March 9) =
+
= Week 8 (November 3) - Server Farms II =
  
 
<!--
 
<!--
Line 267: Line 272:
 
-->
 
-->
  
= Week 9 =
+
= Week 9 (November 10) - Distributed Processing =
  
 
<!--
 
<!--
Line 304: Line 309:
 
-->
 
-->
  
= Week 10 (March 23) =
+
= Week 10 (November 17) - Virtualization =
= Week 11 (March 30) =
+
= Week 11 (November 24) - Monitoring & Management =
= Week 12 (April 6) =
+
= Week 12 (December 1) - Presentations =
  
 
<!--
 
<!--
Line 329: Line 334:
 
-->
 
-->
  
= Week 13 (April 13) =
+
= FUDCon (December 5-7) =
= Exam Week (April 20) =
+
 
 +
* Please plan on attending the Saturday Unconference.
 +
 
 +
= Week 13 (December 8) - Wrap-=
 +
= Exam Week (December 15) =
 +
 
 +
* There is no exam in this course.

Revision as of 22:29, 7 September 2009

Please note:

  • The schedule here is tentative.
  • Week-by-week details will be filled in as the course progresses.

Week 1 (September 8) - Introduction

Tuesday

  • Welcome
  • Introductions
  • Intro to Build & Release
    • Brief overview of the process
      • Versioning & repository systems
      • Compilation
      • Testing
      • Packaging
      • Compositing
      • Release
      • Distribution
      • Mirroring
    • These steps vary according to the particular project/product. For example, when distributing software physically, "Release" means performing a RTM, where the final "gold disk" is sent to the duplicating house to be mass-produced; but when distributing software electronically, "Release" means sending the software to the online distribution system. The sequence of steps also varies between projects/products.
  • Course Layout
    • Project-based course
    • Working with Open Source
    • Working with the Fedora Project
  • Communication Tools
  • Course Outline
  • Visit the CDOT Area

Thursday

  • Make
  • Makefile Basics
    • Targets, Dependencies, and Commands
    • Implied rules (e.g., .o files)
    • Examples
  • Building software from a source tarball using a makefile

Readings/Resources

ToDo:

Communication Lab: By Wednesday, September 9, Set up your accounts (wiki, IRC, FAS2).

  • Create a blog post which will appear on the OpenSource@Seneca Planet, containing:
    • A portion of an IRC conversation you've had with someone on a Fedora or Seneca IRC channel.
    • A link to your User page on the Seneca wiki
    • A link to your User page on the Fedora wiki
  • Add an entry to the Fall 2009 SBR600 Participants page

Register for:

Lab 1: By Tuesday, September 15:

  • Build 2 packages from Source
    • The NLED editor from http://cdot.senecac.on.ca
    • Any package that uses a configure script -- SourceForge might be a good place to look for such packages.
  • Blog about the experience.

Week 2 (September 15) - Overview of the Build and Release Processs

Week 3 (September 22) - Creating RPM Packages I

Week 4 (September 29) - Creating RPM Packages II

Week 5 (October 6) - Compositing

Week 6 (October 13) - Distributing

Week 7 (October 20) - Server Farms I

Study Week (October 27)

Week 8 (November 3) - Server Farms II

Week 9 (November 10) - Distributed Processing

Week 10 (November 17) - Virtualization

Week 11 (November 24) - Monitoring & Management

Week 12 (December 1) - Presentations

FUDCon (December 5-7)

  • Please plan on attending the Saturday Unconference.

Week 13 (December 8) - Wrap-

Exam Week (December 15)

  • There is no exam in this course.