Re: [tractusx-dev] [Discussion] How to keep track of 3rd-party IP issues

["Kristan Johannes (BD/PAD-COD2)" <Johannes.Kristan@xxxxxxxxx>]

Hi,

In order to have the possibility to track back from the gitlab ip issue to the respective tractusx-x repository it might be helpful to add a link to the created GitHub-issue also to the gitlab ip issue. Otherwise all GitHub tractusx issues need to be scrawled to find the one with a specific gitlab ip issue referenced.

Kind regards,

Johannes 

Am 09.03.2023 um 08:43 schrieb Angelika Wittek <angelika.wittek@xxxxxxxxxx>:



+1

Having the possibility to track from which repository the IP issues are coming from is a great benefit.

E.g.

• Tracking the issues with "Help Wanted"
  
• in the list of open issues [1] we have two versions of keycloak-spring-boot-starter: 21.0.0 and 20.0.3 and we cannot track down if the issues are coming from a repository where the dependency was updated or from separate repositories.
  

Best regards
Angelika

[1] https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/?search=automotive.tractusx&sort=created_date&state=opened&first_page_size=20

Am 08.03.23 um 18:15 schrieb Matthias Hub:

I second the proposal – which additionally also enables transparency and a history regarding the used libraries and versions for new developers. Do you plan to include this topic in this weeks’ office hours?

 

BR, Matthias

 

--
Matthias Hub | +49 170 9117038 | matthias.hub@porsche.digital | Porsche Digital | Forward31 | Stralauer Allee 12, 10245 Berlin

 

From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Kiermayer, Siegfried via tractusx-dev <tractusx-dev@xxxxxxxxxxx>
Date: Wednesday, 8. March 2023 at 17:31
To: tractusx developer discussions <tractusx-dev@xxxxxxxxxxx>
Cc: Kiermayer, Siegfried <siegfried.kiermayer@xxxxxxx>
Subject: Re: [tractusx-dev] [Discussion] How to keep track of 3rd-party IP issues created by Dash

Hey,

 

Good idea 😊

 

In the middle term we can also then reference potential IP issues in the changelog with a proper github filter.

 

Tx,

 

Sigi

 

From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of sebastian.bezold--- via tractusx-dev <tractusx-dev@xxxxxxxxxxx>
Date: Wednesday, 8. March 2023 at 16:50
To: tractusx-dev@xxxxxxxxxxx <tractusx-dev@xxxxxxxxxxx>
Cc: sebastian.bezold@xxxxxxxxxxxxxxxxx <sebastian.bezold@xxxxxxxxxxxxxxxxx>
Subject: [tractusx-dev] [Discussion] How to keep track of 3rd-party IP issues created by Dash

Internal

 

Hi all,

 

I want to discuss a topic with you, that we are currently seeing. It is concerning IP tickets for 3rd-party library checks created via the Eclipse Dash tool.

As you know, the automatic ticket creation process can only be used by committers, since you need an GitLab API key to use with the ‘-review’ option.

Most of the issues are handled by the Dash bot automatically, but some might stay open for a while longer or it is even asked to help out by providing source links for example.

 

For me, it is hard to keep track of which ticket I opened for which team. So If there is Help wanted, I struggle to find the right one to ping.

I want to ping the team, because even If I created the issues, it’s in the teams responsibility to keep track of them and it’s also easier for someone familiar with the language/build ecosystem to find the appropriate sources, if needed for the ticket.

To make keeping track easier for us, I would propose the following:

 

• Each time a committer is running Eclipse Dash and IP issues are automatically opened, the committer opens a GitHub issue on the repository the scan was done for
• Contents of the GitHub issue are all of the IP issue links that have been created. I think one ticket for all should be fine
• The GitHub issue is labeled with ‘3rd-party libraries’ or any other good suggestion, that would make it easy for us to find all issues across the eclipse-tractusx org.

 

What do you think about this proposal?

 

Best regards

Sebastian

 

 

Mit freundlichen Grüßen / Kind regards

 

Sebastian Bezold

Software Engineer

 

Mercedes-Benz Tech Innovation GmbH (ehemals/formerly Daimler TSS GmbH)

Wilhelm-Runge-Straße 11

89081 Ulm/Germany

 

Sebastian.Bezold@xxxxxxxxxxxxxxxxx

 

www.mercedes-benz-techinnovation.com

 

<image001.jpg>

<image002.png>

 

<image003.png>

 

<image004.png>

 

<image005.png>

 

<image006.png>

 

<image007.jpg>

 

 

Mercedes-Benz Tech Innovation GmbH

Sitz und Registergericht/Domicile and Register Court: Ulm, HRB-Nr./Commercial Register No.: 3844

Geschäftsführung/Management: Daniel Geisel (Vorsitzender/Chairperson), Isabelle Krautwald

 

If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.

 

Porsche Digital GmbH
Sitz der Gesellschaft: Ludwigsburg
Geschaeftsanschrift: Groenerstrasse 11/1, 71636 Ludwigsburg
Registergericht: Amtsgericht Stuttgart HRB-Nr. 756995
Geschaeftsfuehrer: Mattias Ulbrich, Stefan Zerweck, Dr. Rolf Zoeller

---

Die vorgenannten Angaben werden jeder E-Mail automatisch hinzugefügt.
Dies ist kein Anerkenntnis, dass es sich beim Inhalt dieser E-Mail um eine rechtsverbindliche Erklaerung der Porsche Digital GmbH handelt.
Erklaerungen, die die Porsche Digital GmbH verpflichten, beduerfen jeweils der Unterschrift durch zwei zeichnungs- berechtigte Personen der Porsche Digital GmbH.

_______________________________________________
tractusx-dev mailing list
tractusx-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org

_______________________________________________
tractusx-dev mailing list
tractusx-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org