Difference between revisions of "Winter 2009 SBR600 Weekly Schedule"
Chris Tyler (talk | contribs) (→Week 1 (January 12) - Introduction) |
Chris Tyler (talk | contribs) (→Tuesday) |
||
Line 18: | Line 18: | ||
*** Distribution | *** Distribution | ||
*** Mirroring | *** 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 | * Course Layout | ||
** Project-based course | ** Project-based course |
Revision as of 13:23, 15 January 2009
Please note:
- The schedule here is tentative.
- Week-by-week details will be filled in as the course progresses.
Contents
- 1 Week 1 (January 12) - Introduction
- 2 Week 2 (January 19) - Overview of the Build and Release Processs
- 3 Week 3 (January 26) - Working with Open Source Communities
- 4 Week 4 (February 2) - Project Release 0.0
- 5 Week 5 (February 9) - Basic Build I
- 6 Week 6 (February 16) - Basic Build II
- 7 Week 7 (February 23) - Basic Build III - Project Release 0.1
- 8 Study Week (March 2)
- 9 Week 8 (March 9) - Server Farms & Distributed Processing I
- 10 Week 9 (March 16) - Server Farms & Distributed Processing II
- 11 Week 10 (March 23) - Server Farms & Distributed Processing III - Project Release 0.2
- 12 Week 11 (March 30) - Supporting Technologies I
- 13 Week 12 (April 6) - Supporting Technologies II
- 14 Week 13 (April 13) - Project Release 0.3 & Presentations
- 15 Exam Week (April 20)
Week 1 (January 12) - 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.
- Brief overview of the process
- Course Layout
- Project-based course
- Working with Open Source
- Working with the Fedora Project
- Communication Tools
- Course Outline
- Visit the CDOT Area
Thursday
- Makefile Basics
- Targets, Dependencies, and Commands
- Implied rules (e.g., .o files)
- Examples
Readings/Resources
- Two simple makefile examples
ToDo:
Communication Lab: By Thursday, January 15, 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 Winter 2009 SBR600 Participants page
Lab 1: By Wednesday, January 21:
- Build 2 packages from Source
- The NLED editor from http://cdot.senecac.on.ca
- Any package that uses autoconf -- SourceForge might be a good place to look for such packages.
- Blog about the experience.