Comments

• 

  over 3 years ago by alnovak | Reply

  I see two large sources of data that would be useful to include:

  • supportconfigs - these are either attached to Bugzilla, or available (short-term) on a filesystem - present great overview of our customers' environment

  • L3 metadata - for L3 bugs (~ 3000 / year), there are data that may be highly relevant for the clustering as well, among other:

    • customer identification
    • what PTFs (fixed packages) were delivered in the case, what was the feedback on those

  • 

    over 3 years ago by gboiko | Reply

    Hi @alnovak

    Thank you for your feedback! I will try to include those as well in the analysis.

    Even though I already had in mind L3 metadata, I haven't thought of supportconfigs, nice hint, thank you!

  ×
  Edit Comment 4886
  # 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
  Hi [@alnovak](/users/alnovak) Thank you for your feedback! I will try to include those as well in the analysis. Even though I already had in mind L3 metadata, I haven't thought of supportconfigs, nice hint, thank you!
   
  ×
  Reply to gboiko
  Hi @alnovak
  Thank you for your feedback! I will try to include those as well in the analysis.
  Even though I already had in mind L3 metadata, I haven't thought of supportconfigs, nice hint, thank you!
  ---
  # 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 4884
# 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
I see two large sources of data that would be useful to include: - supportconfigs - these are either attached to Bugzilla, or available (short-term) on a filesystem - present great overview of our customers' environment - L3 metadata - for L3 bugs (~ 3000 / year), there are data that may be highly relevant for the clustering as well, among other: - customer identification - what PTFs (fixed packages) were delivered in the case, what was the feedback on those
 
×
Reply to alnovak
I see two large sources of data that would be useful to include:
• supportconfigs - these are either attached to Bugzilla, or available (short-term) on a filesystem - present great overview of our customers' environment

• L3 metadata - for L3 bugs (~ 3000 / year), there are data that may be highly relevant for the clustering as well, among other:

  • customer identification
  • what PTFs (fixed packages) were delivered in the case, what was the feedback on those
---
# 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
 
• 

  over 3 years ago by mslacken | Reply

  I had the same idea last year, but did not really succeed. You might want to have a look at: https://github.com/mslacken/ml-bugs I also gave a talk at the Super Compute 2019: https://gitlab.suse.de/mslacken/sc-2019 Feel free to ping me, if you need any additional information.

  • 

    over 3 years ago by gboiko | Reply

    Hi @mslacken

    Thank you for the pointers. I will take them a quick look and then I will certainly ping you about it.

    Enjoy hackweek :)

  ×
  Edit Comment 5276
  # 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
  Hi [@mslacken](/users/mslacken) Thank you for the pointers. I will take them a quick look and then I will certainly ping you about it. Enjoy hackweek :)
   
  ×
  Reply to gboiko
  Hi @mslacken
  Thank you for the pointers. I will take them a quick look and then I will certainly ping you about it.
  Enjoy hackweek :)
  ---
  # 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 4910
# 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
I had the same idea last year, but did not really succeed. You might want to have a look at: https://github.com/mslacken/ml-bugs I also gave a talk at the Super Compute 2019: https://gitlab.suse.de/mslacken/sc-2019 Feel free to ping me, if you need any additional information.
 
×
Reply to mslacken
I had the same idea last year, but did not really succeed. You might want to have a look at: https://github.com/mslacken/ml-bugs I also gave a talk at the Super Compute 2019: https://gitlab.suse.de/mslacken/sc-2019 Feel free to ping me, if you need any additional information.
---
# 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