From Fedora Project Wiki
m (added task)
(status update; added days for Week 2; added "Daily Task Calendar" link)
Line 1: Line 1:
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.
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.
[http://www.google.com/calendar/embed?src=0km2me3maihq83jq739s7h144g%40group.calendar.google.com&ctz=America/Toronto Daily Task Calendar]


# (3 - 6 June): (now scheduled for completion on/by 2010-06-04)
# (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 [[User:Crantila/FSC/RequestForTesting|here]])
#* Write message and find subjects for tutorial-algorithm testing, and target-audience testing. (done; see [[User:Crantila/FSC/RequestForTesting|here]])
#* Ask some friends for creative contributions.
#* Ask some friends for creative contributions. (done, with one volunteer so far)
#* Create development/testing environments (list is for personal reference):
#* 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 x64 (KDE only) on fwt (NO - remains F12 indefinitely, for technical reasons)
#** Fedora 13 i686 (KDE only) on hp (done)
#** Fedora 13 i686 (KDE only) on hp (done)
#** Fedora 13 x86 (GNOME only) on fwt-vbox
#** Fedora 13 x86 (GNOME only) on fwt-vbox (having problems getting the vbox kernel modules working)
#** I don't think that all the other vbox-testing things were really necessary.
#** 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)
#* Create a Google Calendar 'feed' of tasks and time-lines. (calendar ready, but currently empty)
#* Hook into Fedora Planet to start blogging. (awaiting approval for a Fedora People account)
#* Hook into Fedora Planet to start blogging. (connected, but Blogger is down at the moment)
#* Revise schedule to account for late start. (basically done)
#* Revise schedule to account for late start. (finished)
#* Finalize tutorial topics. (basically done)
#* Finalize tutorial topics. (finished & ongoing)
# (7 - 13 June):
# (7 - 13 June):
#* Compile list of users/platforms willing to help with testing.
#* Send "yay" emails to music@ and planetccrma@ lists, asking for help with testing.
#* Send "yay" emails to music@ and planetccrma@ lists.
#** Compile list of volunteers willing to help with testing.
#* Learn about Qtractor, Rosegarden, and Ardour so that you can make distinct tutorial topics.
#* Begin Writing Tutorial Algorithms (these will require less research):
#* Begin Writing Tutorial Algorithms (these will require less research):
#** Sound Servers: JACK
#** Sound Servers: JACK (Monday)
#** Sound Servers: PulseAudio
#** Sound Servers: PulseAudio (Monday)
#** Planet CCRMA: Repository Configuration (done)
#** Planet CCRMA: Repository Configuration (done)
#** Recording: Audacity
#** Recording: Audacity (Tuesday)
#** Synthesizers: SuperCollider
#** Synthesizers: SuperCollider (Friday, Saturday)
#** Typesetting: LilyPond
#** Typesetting: LilyPond (Wednesday)
#** Typesetting: Frescobaldi
#** Typesetting: Frescobaldi (Wednesday)
#* Learn about Qtractor, Rosegarden, and Ardour so that you can make distinct tutorial topics.
# (14 - 20 June):
# (14 - 20 June):
#* Test previous week's tutorial algorithms.
#* Test previous week's tutorial algorithms.

Revision as of 04:15, 7 June 2010

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.

Daily Task Calendar

  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. (done, with one volunteer so far)
    • 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 (having problems getting the vbox kernel modules working)
      • I don't think that all the other vbox-testing things were really necessary.
    • Create a Google Calendar 'feed' of tasks and time-lines. (calendar ready, but currently empty)
    • Hook into Fedora Planet to start blogging. (connected, but Blogger is down at the moment)
    • Revise schedule to account for late start. (finished)
    • Finalize tutorial topics. (finished & ongoing)
  2. (7 - 13 June):
    • Send "yay" emails to music@ and planetccrma@ lists, asking for help with testing.
      • Compile list of volunteers willing to help with testing.
    • Learn about Qtractor, Rosegarden, and Ardour so that you can make distinct tutorial topics.
    • Begin Writing Tutorial Algorithms (these will require less research):
      • Sound Servers: JACK (Monday)
      • Sound Servers: PulseAudio (Monday)
      • Planet CCRMA: Repository Configuration (done)
      • Recording: Audacity (Tuesday)
      • Synthesizers: SuperCollider (Friday, Saturday)
      • Typesetting: LilyPond (Wednesday)
      • Typesetting: Frescobaldi (Wednesday)
  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.