Project

General

Profile

action #94838

Make qem-dashboard a proper public open source project

Added by okurz 3 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-06-29
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

I wonder why I even need to write this, we are working at SUSE, right? :) (If still not convinced see opensource.suse.com/ and https://intra.suse.net/company/living-our-values-everyday/ and if you don't want to talk to me about this then talk to others, e.g. bzoltan1)

Acceptance criteria


Related issues

Related to QA - action #97274: qam dashboard improvement ideasNew2021-08-20

Blocks QA - action #94588: [qem] dashboard.qam.suse.de to be included in approval qam-openqaNew2021-06-23

Copied to openQA Project - action #95821: Make qa-maintenance/openQABot a proper public open source projectNew2021-06-29

History

#1 Updated by okurz 3 months ago

  • Blocks action #94588: [qem] dashboard.qam.suse.de to be included in approval qam-openqa added

#2 Updated by kraih 3 months ago

I also prefer making everything open source from the start. Main reasons not to do so here were that, a) the project was just a proof of concept until recently, b) openQABot and SMELT are closed source, c) ease of deployment from our gitlab instance, since Jan already has ansible set up there for pipelines. Aside from the code being pretty much useless without having a SMELT instance, the main concern will be deployment from GitHub to the dashboard machine. Oh, and of course naming the project. :)

#3 Updated by okurz 2 months ago

  • Copied to action #95821: Make qa-maintenance/openQABot a proper public open source project added

#4 Updated by cdywan about 1 month ago

As I understand it there's nothing blocking us here besides finding a new name. If CI can't easily be setup on GitHub I wouldn't consider that a problem, since this is about development and not about production deployments.

#5 Updated by kraih about 1 month ago

cdywan wrote:

As I understand it there's nothing blocking us here besides finding a new name. If CI can't easily be setup on GitHub I wouldn't consider that a problem, since this is about development and not about production deployments.

Deployment to production is currently triggered by commits to the repo (after all tests pass in CI).

#6 Updated by okurz about 1 month ago

  • Related to action #97274: qam dashboard improvement ideas added

Also available in: Atom PDF