Consider an alternative means of interacting with the IP Team to process third party content
This is an experiment.
The Dash License Tool can produce a list of content that needs review. The ultimate goal is to ensure that the Eclipse Foundation's IP Policy is properly implemented. The means of implementing this goal is to grow our data sets to cover identified cases so that the license tool (and future tools) can produce better results.
- In some cases, the content that is identified by the tool is actually Eclipse project content that doesn't actually require review. In these cases, the relationship between the Eclipse project and the content needs to be captured.
- In some cases, the content has been reviewed already, but is not mapped in manner that the license tool can identify it. In these cases, the mapping needs to be augmented.
- In some cases, we actually need to do some investigation of content.
The first step is sort through the content to determine which bucket it fits into and then move forward from there.
At the same time, we need to modernize our tools. The Eclipse Foundation's GitLab instance seems like a good place to do that. With a modern API, we have a fighting chance of possibly automating (or semi-automating) some part of the process of communicating dependency lists to the IP Team. Even simple features like checklists in an issue description will make keeping track of progress a lot easier. The ability to capture the tracking process in the same place where we can capture data (and have it all tracked) is a boon as well. Finally, the ability to just edit in directly in the interface means that we don't have to spend significant effort training the IP Team (but can lean on the sophistication of Git should we need that ability).
I've extended the license tool to produce output that is consistent with a GitLab issue description and used the output from running that extension on the license tool itself in issue iplab#1 (closed) as my first attempt at processing output.