Comments

• 

  4 days ago by dgarcia | Reply

  Interesting project, I was thinking about extending the service to be able to produce some kind of graphs like:

  • br.opensuse.org/graph/bar/project
  • br.opensuse.org/graph/pie/project

  • 

    4 days ago by adamm | Reply

    You could also use parameters to current endpoints to have different output,

    • ?type=bar
    • ?type=pie

    But from release management perspective, or for project view, these outputs may not be very helpful. What they are looking for is having actionable data, not relative data. Output of form,

    x86_64   |  [** | green, success]       |     [** | green, success ]
                  |  10 | red, failed                 |     [ 8 | red, failed ]
                  |  8  | orange, unresolvale |  .. ]
    aarch64  |
    i586        |
    s390x     |
    ppc64le  |
                   |  standard                      | ports
    

    is actually much more useful. Ideally, we want to see these actionable items, and ignore the "building 10000" or "blocked 200". If they exist, fine, but visibility of small numbers is more important than actual, relative data that we normally associate with bar or pie charts.

  ×
  Edit Comment 11181
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  - Use hyphens
  - for unordereed
  - lists
  
  This is an [link to example.com](http://example.com/)
  
  This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
  You could also use parameters to current endpoints to have different output, * `?type=bar` * `?type=pie` But from release management perspective, or for project view, these outputs may not be very helpful. What they are looking for is having *actionable* data, not relative data. Output of form, x86_64 | [** | green, success] | [** | green, success ] | 10 | red, failed | [ 8 | red, failed ] | 8 | orange, unresolvale | .. ] aarch64 | i586 | s390x | ppc64le | | standard | ports is actually much more useful. Ideally, we want to see these actionable items, and ignore the "building 10000" or "blocked 200". If they exist, fine, but visibility of small numbers is more important than actual, relative data that we normally associate with bar or pie charts.
   
  ×
  Reply to adamm
  You could also use parameters to current endpoints to have different output,
  • ?type=bar
  • ?type=pie
  But from release management perspective, or for project view, these outputs may not be very helpful. What they are looking for is having actionable data, not relative data. Output of form,
  x86_64   |  [** | green, success]       |     [** | green, success ]
                |  10 | red, failed                 |     [ 8 | red, failed ]
                |  8  | orange, unresolvale |  .. ]
  aarch64  |
  i586        |
  s390x     |
  ppc64le  |
                 |  standard                      | ports
  
  is actually much more useful. Ideally, we want to see these actionable items, and ignore the "building 10000" or "blocked 200". If they exist, fine, but visibility of small numbers is more important than actual, relative data that we normally associate with bar or pie charts.
  ---
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  - Use hyphens
  - for unordereed
  - lists
  
  This is an [link to example.com](http://example.com/)
  
  This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
   
×
Edit Comment 11178
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Interesting project, I was thinking about extending the service to be able to produce some kind of graphs like: * br.opensuse.org/graph/bar/project * br.opensuse.org/graph/pie/project
 
×
Reply to dgarcia
Interesting project, I was thinking about extending the service to be able to produce some kind of graphs like:
• br.opensuse.org/graph/bar/project
• br.opensuse.org/graph/pie/project
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview