[dash-licenses] Add a IP Team Review request feature to automatically set up a review

[olexii4]

Is your enhancement related to a problem? Please describe

I'm always frustrated when I need to create IP Team review requests manually.

Describe the solution you'd like

Need to implement automatically set up a review request for IP Team

Describe alternatives you've considered

No response

Additional context

No response

[ibuziuk]

Since we are part of the Eclipse Foundation, we should fall back on the official tools and processes

• https://github.com/eclipse-dash/dash-licenses
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab
• https://www.eclipse.org/lists/eclipse.org-members-committers/msg01284.html

I'm always frustrated when I need to create IP Team review requests manually.

@olexii4 could you please clarify what was the last time IP team review was requested and what exactly was frustrating during this process?

[olexii4]

Since we are part of the Eclipse Foundation, we should fall back on the official tools and processes

• https://github.com/eclipse-dash/dash-licenses
• https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab
• https://www.eclipse.org/lists/eclipse.org-members-committers/msg01284.html

I'm always frustrated when I need to create IP Team review requests manually.

@olexii4 could you please clarify when the last time the IP team review was requested and what exactly was frustrating during this process?

@ibuziuk The last time I worked on this issue was Add a GitHub job to check licenses for using libraries for PRs for che-code. I spent a lot of time creating IP Team review requests and have not finished yet because of changing priorities. The PR https://github.com/che-incubator/che-code/pull/527 is still marked as draft, and it includes thousands of libraries in the list, and more than forty libraries need to IP team review request first. Now just 26 left:

UNRESOLVED Production dependencies

1. @vscode/[email protected]
2. @vscode/[email protected]
3. @vscode/[email protected]
4. @vscode/[email protected]
5. @vscode/[email protected]
6. @vscode/[email protected]
7. @vscode/[email protected]
8. @vscode/[email protected]
9. @xterm/[email protected]
10. @xterm/[email protected]
11. @xterm/[email protected]
12. @xterm/[email protected]
13. @xterm/[email protected]
14. @xterm/[email protected]
15. @xterm/[email protected]
16. @xterm/[email protected]
17. @xterm/[email protected]
18. @xterm/[email protected]

UNRESOLVED Development dependencies

1. @csstools/[email protected]
2. @ts-morph/[email protected]
3. @vscode/[email protected]
4. @vscode/[email protected]
5. @vscode/[email protected]
6. @vscode/[email protected]
7. [email protected]
8. [email protected]

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.