| Re: [openpass-sc] EMO | automotive.openpass 2024.06 (#527) |
|
Many thanks for providing this great example! Barbara worked for us (MB) last year on that subject, but we could not continue this activity in 2025. We will discuss the different options (who does what?) based on your explanation in our AC this Friday.
Can you get somebody to try to use the tool in the manner that I've described for one of your components?
NOTICE.md · main · Eclipse Projects
/ Eclipse openpass / opSimulation · GitLab NOTICE.md · main · Eclipse Projects / Eclipse openpass / opGUI
· GitLab NOTICE.md · main · Eclipse Projects / Eclipse openpass
/ openscenario1-engine · GitLab NOTICE.md · main · Eclipse Projects
/ Eclipse openpass / gt-gen-core · GitLab If there are further open questions after our discussion in the AC, we will come back to you. Take care, Jan Von: wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
Im Auftrag von Eclipse Management Office EMO [**EXTERNAL E-MAIL**]
I had been discussing this with Barbara Kohn late last year. I see that you've added version information to the spreadsheet since that discussion. We don't have a great answer for C/C++ code because the C/C++ doesn't have a good answer for identifying C/C++ content. AFAICT, there is no common build tool that can reveal the dependencies to us and so they need to be manually tracked.
If you are using a build tool that can reveal dependencies, please let me know and we'll try to work out how to leverage it. The short answer is that our new IPLab can be used in exactly the same manner as you used IPZilla. Your team can
create individual issues, provide a pointer or attach source code, and the IP Team can review them from there. This will be time consuming. There's more help in the
handbook. However, since you've identified the GitHub repository and version for many of your dependencies, we can use that information with the Eclipse Dash License Tool. I've used the Eclipse Dash License Tool to create
this issue, for example, by invoking the tool in this manner: $ echo "git/github/nlohmann/json/3.9.1" | java -jar org.eclipse.dash.licenses-1.1.1-SNAPSHOT.jar - -review -project automotive.openpass -token <token> It should be relatively easy to map each row of your spreadsheet into a form that IPLab will understand. e.g., "https://github.com/nlohmann/json, 3.9.1" becomes "git/github/nlohmann/json/3.9.1" So... you could use an Excel formula to make those conversions, move them into a text file named (for example)
dependencies.txt, and then give that file to the Eclipse Dash License Tool. $ cat dependencies.txt ... git/github/nlohmann/json/3.9.1 git/github/zaphoyd/websocketpp/2.8.2 ... $ java -jar org.eclipse.dash.licenses-1.1.1-SNAPSHOT.jar
dependencies.txt -review -project automotive.openpass -token <token> As I discussed with Barbara, it is our policy that we review specific versions of content. Version information is missing for some of the listed dependencies. We really need that information. And we really need to be able to review the
source. If a specific release version can't be identified, we can also work from a specific commit ref. There will be a few cases where the automation fails to find a matching release/tag in GitHub, and some manual intervention will be required. The IP Team can help you sort that out. Can you get somebody to try to use the tool in the manner that I've described for one of your components? And the, based on that experience, we can sort out the best path forward. Wayne On Wed, May 7, 2025 at 8:56 AM <jan.dobberstein@xxxxxxxxxxxxxxxxx> wrote:
The Eclipse Management Organization |
Eclipse Foundation |