MainInclusionReportJACK

Differences between revisions 8 and 10 (spanning 2 versions)
Revision 8 as of 2009-09-09 17:24:25
Size: 2684
Editor: 17
Comment:
Revision 10 as of 2009-09-09 17:43:10
Size: 4113
Editor: 17
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Main Inclusion Report for Jack-Audio-Connection-Kit (JACK)= = Main Inclusion Report for Jack-Audio-Connection-Kit (JACK) =
Line 12: Line 12:
  * Only binaries in jackd, none of which are suid/sgid: realtime capabilities are nowadays granted to users/groups though /etc/security/limits.conf   * Only binaries in ''jackd'', none of which are suid/sgid. Note: realtime capabilities are nowadays granted to users/groups though /etc/security/limits.conf
Line 17: Line 17:
  * Jack needs some audio output device to connect to in order to start. This might fail if such a device is not available, or if another process is keeping a device occupied that does not support multiple concurrent connections.
  * Jack does not ask any debconf questions.
  * [[http://bugs.debian.org/src:jack|Debian bugs]]: only wishlist items are open right now.
  * [[http://packages.qa.debian.org/j/jack.html|Maintenance in Debian]] is calm
  * [[http://jackaudio.org|Upstream]] is calm
  * [[http://trac.jackaudio.org/jack/|Upstream bug tracker]]: nothing particularly relevant or critical there either it seems
  * In what situation does the package not work out of the box without configuration?
   * Jack needs some audio output device to connect to in order to start. This might fail if such a device is not available, or if another process is keeping a device occupied that does not support multiple concurrent connections.
   * Some configuration may be required for optimal performance (i.e. low latency) depending on the audio card used. [[https://help.ubuntu.com/community/HowToJACKConfiguration|Configuration instruction]] are available at help.ubuntu.com.
  * Does the package ask any debconf questions highter than priority 'medium'?
   * Jack does not ask any debconf questions.
  * Debian bugs: [[http://bugs.debian.org/src:jack|only wishlist items are open right now]]
  * Maintenance in Debian: [[http://packages.qa.debian.org/j/jack.html|Is calm]]
  * Upstream: [[http://jackaudio.org|Is vigorous]]
  * Upstream bug tracker: [[http://trac.jackaudio.org/jack/|nothing particularly relevant or critical there either it seems]]
  * Hardware: This package deals well with most commonly available consumer and semi- and professional audio cards.
  * Is there a test stuie in the upstream source or packaging?
  * Is it enabled to run in the build?
 0. ''UI standards:''
  * User-visible strings are internationalized using standard gettext system ?
  * Package with translatable strings builds a PO template during package build ?
  * End-user applications ship a desktop file ?
Line 30: Line 40:
 0. ''Maintenance:''
  * How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.)
  * Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ?
  * Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian)
Line 33: Line 47:
 0. ''Internationalization:''
  * Are graphical applications translatable? Do they support gettext?
Line 38: Line 54:
''The author of this report should put their name here; reviewers will add comments etc. too'' Author: [[https://launchpad.net/~slavender|Scott Lavender]]

Main Inclusion Report for Jack-Audio-Connection-Kit (JACK)

Requirements

  1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/j/jack-audio-connection-kit; Available for all supported architectures.

  2. Rationale:

    • Build dependency of the 'jack' alsa plugin (now disabled in libasound2-plugins, see launchpad bugs 197957 and 84900)

    • ...
  3. Security:

    • No CVE entries known.

    • No Secunia history known

    • Only binaries in jackd, none of which are suid/sgid. Note: realtime capabilities are nowadays granted to users/groups though /etc/security/limits.conf

    • jackd is of course a daemon, but is not automatically started on startup
    • jackd does not listen for network connections itself - it requires the installation of a separately available 'netjack' driver for this.
    • No source code review is performed that we know of.
  4. Quality assurance:

    • In what situation does the package not work out of the box without configuration?
      • Jack needs some audio output device to connect to in order to start. This might fail if such a device is not available, or if another process is keeping a device occupied that does not support multiple concurrent connections.
      • Some configuration may be required for optimal performance (i.e. low latency) depending on the audio card used. Configuration instruction are available at help.ubuntu.com.

    • Does the package ask any debconf questions highter than priority 'medium'?
      • Jack does not ask any debconf questions.
    • Debian bugs: only wishlist items are open right now

    • Maintenance in Debian: Is calm

    • Upstream: Is vigorous

    • Upstream bug tracker: nothing particularly relevant or critical there either it seems

    • Hardware: This package deals well with most commonly available consumer and semi- and professional audio cards.
    • Is there a test stuie in the upstream source or packaging?
    • Is it enabled to run in the build?
  5. UI standards:

    • User-visible strings are internationalized using standard gettext system ?
    • Package with translatable strings builds a PO template during package build ?
    • End-user applications ship a desktop file ?
  6. Standards compliance:

  7. Dependencies:

    • ...
    • Are these all in main ?
  8. Maintenance:

    • How much maintenance is this package likely to need ? (Simple packages may largely take care of themselves; complex packages will need dedicated developers paying attention to them.)
    • Who is responsible for monitoring the quality of this package and fixing its bugs ? Are they Ubuntu or Debian developers ?
    • Who is the package bug contact in Ubuntu? (Needs one if its a nontrivial package which does not fully maintain itself through Debian)
  9. Background information:

    • The general purpose and context of the package should be clear from the package's debian/control file. If it isn't then please explain.
    • What do upstream call this software ? Has it had different names in the past ?
  10. Internationalization:

    • Are graphical applications translatable? Do they support gettext?

Reviewers

MIR bug: https://bugs.launchpad.net/BUGNUMBER

Author: Scott Lavender * Contributor: Arnout 'raboof' Engelen

MainInclusionReportJACK (last edited 2010-03-16 12:37:56 by vininim)