Home

###TODO

• New features:

  • Keyboard navigation when viewing a SR
  • Open text files on double click
  • Refactor OBSXmlReader (parse lists, include home directories)
  • Implement submit requesting
  • Implement properties dialog for project/package
  • Implement a search tool
  • Show outgoing requests, declined requests
  • Implement a plasmoid
  • Enable forwarding SR (Request State Editor). Forward to project from _link
  • Manage downloaded xml files (ie: package lists)
  • Implement search in the build log viewer
  • Implement auto refresh in the build log viewer
  • Fix upload of multiple files
  • Implement drag and drop of file out of Qactus (download file)
  • Refresh project/package list on creation of project/package
  • Implement watchlist? Can be obtained with GET /person/

• Misc:

  • Create an AppImage
  • Build a Debian package

• WIP:

  • Make Qactus a complete OBS client (ie: new features like creating projects/packages and so on)
    • Copy package
    • Link package
    • Download files, binaries
    • Edit spec, changes

• Known issues for v0.7.0:

  • if an OBS instance doesn't require authentication (except for sr actions), any username/password will be accepted. When trying to do any sr action, he or she will be prompted for giving the right credentials.

• All versions

  • Clean duplicate code
    • someSelectionModel->selectedIndexes()
    • OBSPackage vs OBSStatus [done]
    • getBuildResults() MainWindow vs RequestStateEditor
  • Fix MainWindow::insertResult()

####Done

• Improve tray icon (show notifications on creating/branching/copying/deleting)
• Go to home project feature
• Support self-signed certificates
• Show dialog with SSL error
• Add dialog for adding OBS instances other than openSUSE's (ie: PackMan).
• Improve memory consumption
• Add proxy support
• Add diff to request state change dialog
• Improve notifications
• KWallet support. It uses QtKeychain.

###Ideas Adrian Schröter suggests

• Monitoring status changes by calling "osc -d results -w". The HTTP call hungs until something happens. Then you would get the new status.

Note: The asterisk (*) can have two meanings in osc. Either it is the "dirty" flag, this means the server knows that the scheduler has to check the repository state again. For example when a source change happened, but the scheduler did not check the repository state yet. So the state may still be in succeeded/failed, but it is known that this is going to change.

The other situation where osc prints the asterik is when the build has finished, but the repository is not yet published. When using --verbose switch you see a more detailed output here. This is the code in osc for this:

        if res['dirty']:
            waiting = True
            if verbose:
                res['status'] = 'outdated (was: %s)' % res['status']
            else:
                res['status'] += '*'
        elif res['code'] in ('succeeded') and res['repostate'] != "published":
            waiting = True
            if verbose:
                res['status'] += '(unpublished)'
            else:
                res['status'] += '*'

• Adding builds to be monitored by dragging and dropping its OBS URL into Qactus. [done]
• Having special links on OBS that deliver some file with some specific mimetype so the desktop handler could deliver it to Qactus. This needs some more thinking about how to integrate it into current webui.

Raymond Wooninck suggests:

• being able to see all requests open for a certain group.
• add a review tab (comments + accept/decline buttons) [done]