From Fedora Project Wiki

(significant revision)
Line 35: Line 35:
 
* Write information on [[https://fedoraproject.org/wiki/Releases/14/Spins|this page]].
 
* Write information on [[https://fedoraproject.org/wiki/Releases/14/Spins|this page]].
 
* Get a beat written for the Release Notes ([[User:Crantila|Christopher]]).
 
* Get a beat written for the Release Notes ([[User:Crantila|Christopher]]).
 +
* Contact the [[SIGs/Spins|Spins SIG]] to notify them of our project, and ask for help.
 +
* Convert this page to [[Spins_New_Spin_Page_Template|the format suggested by the Spins SIG]].
  
 
== Primary Packages ==
 
== Primary Packages ==

Revision as of 01:16, 22 July 2010

Remember: this is a wiki, so your contributions of all kinds are welcomed!

Goals

  • Create a Fedora spin configured with software and optimizations designed for audio creation work.

Contributors

Status

  • 2010-07-22: Creation of the Spin Development page.
  • 2010-07-18: There has been renewed interest on the music list in developing a Fedora Music Creation spin.

Timeline

The aim is to release with the next mainstream Fedora release, Fedora 14 "Laughlin," currently scheduled for 26 October 2010 (see [[1]]).

Due to the amount of testing required, and the number of things that might go wrong, there will be a meeting in the future to determine whether to treat the Spin as a mature, usable spin, or as one in testing for Fedora 15.

Tasks

If any of these areas interest you, please put your name next to an item, and indicate when you think you might be able to complete the task, etc.

  • Develop the list of primary audio packages.
  • Develop the list of other audio packages.
  • Develop a list of system tweaks to improve the user experience.
  • Build initial kickstart file based on primary audio packages.
  • Publish the first cut via torrent/site for SIG feedback. (crantila: this should be done via fedorahosted?)
  • Make a cool name for the spin.
  • Prioritize tasks; assign them to people.
  • Team up with Artwork for themes and CDs/DVDs.
  • Document "primary" software (Christopher).
  • Get space at fedorahosted to store development materials.
  • Write information on [page].
  • Get a beat written for the Release Notes (Christopher).
  • Contact the Spins SIG to notify them of our project, and ask for help.
  • Convert this page to the format suggested by the Spins SIG.

Primary Packages

The spin developers consider this group of packages to cover key audio creation areas.

Written Music / Sheet Music

crantila: Do we need these at all? We're looking to create a spin targeted for audio creation. People using LilyPond might be better off doing it in the standard distribution, unless they want other audio creation programs. The point is that we don't need to include it as essential software, so let's cut it out and reduce the size of the installation media.

  • LilyPond
    • LilyPond-mode for Emacs
    • Frescobaldi
    • InkScape
    • LilyPondTools for jEdit

Recording and DAWs

  • Audacity [1.3.12-beta]
  • Ardour
  • Qtractor
  • Rosegarden
  • Traverso

Sound Analysis

  • Praat

Synthesis

  • Keyboard:
    • zynaddsubfx
  • Effects:
    • rakarrack
  • Sampling:
    • FluidSynth & Qsynth
    • LinuxSampler
    • Qsampler
  • Processing/Languages:
    • SuperCollider 3.4
    • PD-extended
    • CSound 5

Sound Server and Configuration

  • qjackctl
  • jack or jack2 (crantila: jack2 should be a top priority)

Kernel and Drivers

  • Real-time kernel
  • FFADO: FireWire audio capture/output

crantila: aren't USB & MIDI already included by default?

Default Desktop Environment(s)

crantila: If we end up with a DVD, it may be possible to include GNOME and KDE, and maybe even others. Probably only one would fit on a CD. They all have their advantages, so I suggest voting by FAS username. That way, we can pick what would please the greatest number of existing audio creation users.

GNOME:

KDE:

  • crantila

XFCE:

Other Packages

These packages would be nice to have, but shouldn't be necessary for release.

  • SuperCollider

Bugs

We want to keep track of new and existing bugs. Maybe some cached BugZilla queries?

Links to Further Information

  • Audio Software Packaging (crantila: what does this mean?)
  • Packages Requiring Testing (koji and bodhi)