Boosters Team/Projects/FactoryStatus

From openSUSE

Current page

• Factory status page

Features

• overview of failing packages (with days since last success)
  • status filtering is already be done by backend, so we should extend with a "broken since" field.
• overview of maintainerless packages
  • How does it qualify ? no bugowner defined neither in package nor project nor in devel packages and projects ?
• coolo's comment (file based)
  • Comments may could be stored in frontend attribute system.
• upstream information provided by freshmeat digger (_Marcus_)
  • should use data from download_url source service
• project.diff warning in devel project
  • project.diff will most likely disappear in future, so we may should extend source server search for modified packages in devel definition
• "different .changes" warning
  • do not spend too much time here, we should rethink the changlog system
• warning about devel projects without sources or without .changes
  • again something for the source server search IMHO

Ideas

• should be browsable by devel project
• should have a "my packages" view
  • should be done with the "My Projects" page in mind
  • an api call for it might make sense, to support this also in osc
• integrate repo check
  • could become part of repository state (not yet existing)
• should be either directly or related to api server
• should no longer be centric to factory
  • IMHO a case by case decision
• should allow custom comments, should allow upload of upstream informations from outside
  • Attribute system has been designed to support permissions of certain groups for certain fields. However, it is not yet implemented, but might make sense to do so for this.
• if there is a pending request, it should be possible to show the patch
  • In general a request handling is missing, showing and accept/reject/... handling.
• possibility to visualize package dependencies (what depends on package 'foo' ?)
  • To be done for OBS 1.7
• Connect Marcus' version crawler to hermes
  • again, data from source service download_url should be used as base

Maintenance

• Dirk wants to have a similiar (or possibly the same page) for 11.2 maintainenance
• Voting for a specific update (also applies to Factory updates during freeze)
  • hm, this is voting for a submit request or voting for a package in a devel package definition ?
• Comments on current status (e.g. "waiting for fix")
  • Status of a request ?
• possibly bugzilla whiteboard connection

Current Implementation

• two perl scripts, one to scan the build service and generates xml file (~coolo/factory-status.xml) and one to generate the .XML
• HTML is using jquery to hide/show entries and sort table

Related

• Marcus's upstream version digger
• repo check (mls and dirk)
• Vincente's collab server
• Duncan's ruby digger
• 'Pkgstars' to reward contributors (feature 306343)