MainInclusionPython-Boto

Differences between revisions 1 and 32 (spanning 31 versions)
⇤ ← Revision 1 as of 2005-11-29 10:24:37 →
Size: 1109
Editor: 195
Comment: create template
← Revision 32 as of 2009-09-21 20:22:03 → ⇥
Size: 3441
Editor: d14-69-66-169
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Main Inclusion Report for sourcepackage = ## page was copied from MainInclusionReportTemplate
= Main Inclusion Report for python-boto =
Line 5: Line 6:
 0. ''Availability:'' http://archive.ubuntu.com/ubuntu/pool/universe/s/sourcepackage, available for all supported architectures  0. ''Availability:'' [[http://archive.ubuntu.com/ubuntu/pool/universe/p/python-boto]]; available for all supported architectures or some subset ?
Line 7: Line 8:
  * Why is this package needed? What feature(s) does it add? Does upstream expect it? Plain text description of expected use
Line 10: Line 12:
  * No CVE entries.
  * No Secunia history.
  * No binaries running as root or suid/sgid.
  * Does not open any port.
  * Source code review:		   * [[http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=boto|CVE entries]]: ...
  * [[http://secunia.com/search/?search=boto|Secunia history]]: ...
  * Any binaries running as root or suid/sgid ? '''No''', only a python library. Any daemons ? '''No'''
  * Network activity: does it open any port ? Python-boto makes outgoing http connections to the ec2 metadata service, which runs on http://169.254.169.254. Does it handle incoming network data ? '''No'''
  * Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ?
  * Any source code review performed ? (The approver will do a quick and shallow check.)
Line 16: Line 19:
  * Package works out of the box without configuration.
  * No showstopper Debian bugs.
  * Good maintenance in Debian.
  * Active upstream.
  * No critical bugs in [http:// upstream bug tracker]
  * Does not deal with exotic hardware which we cannot support.		   * In what situations does the package not work out of the box without configuration ?
  * Does the package ask any debconf questions higher than priority 'medium' ?
  * [[http://bugs.debian.org/src:python-boto|Debian bugs]]: None
  * [[http://packages.qa.debian.org/p/python-boto.html|Maintenance in Debian]] is frenetic/vigorous/calm/dead ?
  * [[http://boto.googlecode.com|Upstream]] is frenetic/vigorous/calm/dead ?
  * [[http://|Upstream bug tracker]]: (mention any particularly relevant or critical)
  * Hardware: Does this package deal with hardware and if so how exotic is it ?
  * Is there a test suite 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 23: Line 32:
  * Meets the [http://www.pathname.com/fhs/ FHS], [http://www.de.debian.org/doc/debian-policy/ Debian Policy]
  * Meets [http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Debian library packaging guide] standards.
  * Standard debhelper/cdbs/dbs packaging, standard patch system.		   * [[http://www.pathname.com/fhs/|FHS]], [[http://www.de.debian.org/doc/debian-policy/|Debian Policy]] compliance ?
  * Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?
Line 27: Line 35:
  * All in main.   * python
  * python-support
  * Are these all in main ? '''Yes'''
 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)
 0. ''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 ?
 0. ''Internationalization:''
  * Are graphical applications translatable? Do they support gettext?
Line 30: Line 49:

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

''The author of this report should put their name here; reviewers will add comments etc. too''

Main Inclusion Report for python-boto

Requirements

  1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/p/python-boto; available for all supported architectures or some subset ?

  2. Rationale:

    • Why is this package needed? What feature(s) does it add? Does upstream expect it? Plain text description of expected use
    • Build dependency of ...

  3. Security:

    • CVE entries: ...

    • Secunia history: ...

    • Any binaries running as root or suid/sgid ? No, only a python library. Any daemons ? No

    • Network activity: does it open any port ? Python-boto makes outgoing http connections to the ec2 metadata service, which runs on http://169.254.169.254. Does it handle incoming network data ? No

    • Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ?
    • Any source code review performed ? (The approver will do a quick and shallow check.)

  4. Quality assurance:

    • In what situations does the package not work out of the box without configuration ?
    • Does the package ask any debconf questions higher than priority 'medium' ?

    • Debian bugs: None

    • Maintenance in Debian is frenetic/vigorous/calm/dead ?

    • Upstream is frenetic/vigorous/calm/dead ?

    • Upstream bug tracker: (mention any particularly relevant or critical)

    • Hardware: Does this package deal with hardware and if so how exotic is it ?
    • Is there a test suite 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:

    • FHS, Debian Policy compliance ?

    • Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ?

  7. Dependencies:

    • python
    • python-support

    • Are these all in main ? Yes

  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://launchpad.net/bugs/BUGNUMBER

The author of this report should put their name here; reviewers will add comments etc. too

MainInclusionPython-Boto (last edited 2009-09-22 15:19:28 by d14-69-66-169)