# Increase the level of the courses to minimize crossover overlap with current CTY courses program and to make the program more attractive to experienced Junior- and Intermediate-Level system and /network administrators.# Require a certain base level of competency with basic Linux system administration tasks, including use of the command line and basic installation of Linux on a PC. For students with borderline ability in these areas, a pre-program workshop could be held.# Move Python to an early point in the scripting courses. Have the first scripting course cover some basic Bash scripting and then go into Python; have the second course cover advanced Bash scripting and then advanced Python or Perl. (The last offering of the scripting course droped PHP in favor of Python).# Schedule the program so that it can be completed by attending two days per week. Place the lecture periods for all classes on two days (for example, Monday/Tuesday) and plan the labs in such a way that they can be performed in person or remotely and/or hold the 2nd class in each course online.# Incorporate cross-course projects where students will be working directly within the Fedora community (see below).

# Require a certain basic level of competency with basic Linux system administration tasks, including use of the command line and basic installation of Linux on a PC. For students with borderline ability in these areas, a pre-workshop could be held. # Move Python to an early point in the scripting courses. Have the first scripting course cover some basic Bash scripting and then go into Python; have the second course cover advanced Bash scripting and then advanced Python or Perl. # Schedule the program so that it can completed by attending two days per week. Place the lecture periods for all classes on two days (for example, Monday/Tuesday) and plan the labs in such a way that they can be performed in person or remotely. Note that the Fedora project is actually a collection of approximately 5800 RPMs (software packages groups) that are packaged, integrated, built, tested, and distributed using highly-automated tools (Koji, Mash, Revisor, Punji, etc). Within the Fedora umbrella we have a lot of latitude for many different types of student involvement.

'''SYA/SPR/NAD would will have combined project work.''' Students will work directly with the Fedora project to complete a project from a list of potential projects selected in consultation with the Fedora community. In the first semester, students will take their work to a "0.3" completion level -- stable basic functionality.