User:Crantila/FSC/Schedule

Organized by project week number. The original schedule had a buffer-week at the end. This version is revised to compensate for the late start, which basically involved only removing that week.

1. (3 - 6 June): (now scheduled for completion on/by 2010-06-04)
   • Write message and find subjects for tutorial-algorithm testing, and target-audience testing. (done; see here)
   • Ask some friends for creative contributions.
   • Create development/testing environments (list is for personal reference):
     • Fedora 13 x64 (KDE only) on fwt (NO - remains F12 indefinitely, for technical reasons)
     • Fedora 13 i686 (KDE only) on hp (done)
     • Fedora 13 x86 (GNOME only) on fwt-vbox
     • I don't think that all the other vbox-testing things were really necessary.
   • Create a Google Calendar 'feed' of tasks and timelines. (calendar ready, but currently empty)
   • Hook into Fedora Planet to start blogging. (awaiting approval for a Fedora People account)
   • Revise schedule to account for late start. (basically done)
   • Finalize tutorial topics. (basically done)
2. (7 - 13 June):
   • Compile list of users/platforms willing to help with testing.
   • Send "yay" emails to music@ and planetccrma@ lists.
   • Begin Writing Tutorial Algorithms (these will require less research):
     • Sound Servers: JACK
     • Sound Servers: PulseAudio
     • Planet CCRMA: Repository Configuration (done)
     • Recording: Audacity
     • Synthesizers: SuperCollider
     • Typesetting: LilyPond
     • Typesetting: Frescobaldi
   • Learn about Qtractor, Rosegarden, and Ardour so that you can make distinct tutorial topics.
3. (14 - 20 June):
   • Test previous week's tutorial algorithms.
   • Finish writing tutorial algorithms (these will require more research):
     • Recording: Ardour
     • Synthesizers: FluidSynth/QSynth
     • Synthesizers: Rosegarden
     • Synthesizers: Qtractor
     • Training: GNU Solfege
4. (21 - 27 June):
   • Test previous week's tutorial algorithms.
   • Review algorithms, seeking possible mistakes or pitfalls, and forewarn about them.
   • Buffer week.
5. (28 June - 4 July):
   • Ensure contact is made with the Docs SIG about the evolution to an "official" document.
   • Begin writing documents on the Fedora Wiki (algorithms will already be on the Wiki):
     • Sound Cards
     • Sound Servers: ALSA, Phonon, and Informational Background
     • Sound Servers: JACK
     • Sound Servers: PulseAudio
     • Planet CCRMA: Informational Background
     • Planet CCRMA: Repository Configuration
     • Recording: Audacity vs. Ardour
     • Recording: Audacity
     • Synthesizers: SuperCollider
     • Typesetting: LilyPond
     • Typesetting: Frescobaldi
6. (5 - 11 July): Week of Canada Day
   • Finish writing documents on the Fedora Wiki:
     • Recording: Ardour
     • Synthesizers: FluidSynth/QSynth
     • Synthesizers: Rosegarden
     • Synthesizers: Qtractor
     • Training: GNU Solfege
   • Begin target-audience testing with previous week's material.
7. (12 - 18 July): Midterm
   • Continue target-audience testing.
   • Revise documents to incorporate target-audience comments.
   • Must have found editor, if the Guide is to be turned into an "official" document.
   • Write midterm report, due on 12 July.
8. (19 - 25 July):
   • Finish target-audience testing.
   • Finish revising documents to incorporate comments of target-audience tests.
9. (26 July - 1 August):
   • Convert document to DocBook XML?
   • Write and Test Optional Sections (Algorithms):
     • Kernel Optimization
     • Webcasting: Icecast
10. (2 - 8 August):
    • Finish converting to DocBook XML?
    • Write and Test Optional Sections (Prose):
      • Kernel Optimization
      • Webcasting: Icecast
11. (9 August): Project Completion.
    • Convert Optional Sections to DocBook XML
    • Write final report, due 16 August.
    • Create "snapshot" of all documents, due 16 August.
    • Write evaluation, due 16 August.
12. Return to real life.