Summary
resources/enhancedInspector/*.gs ships seven third-party MIT-licensed files verbatim in the VSIX (resources/** is not excluded via .vscodeignore), but THIRD-PARTY.md currently only has a section for the Pharo AST-Core (Refactoring Browser AST) vendored source. Each shipped .gs file's header only points readers out to "LICENSE in the origin repository" rather than including the MIT notice/permission text the way the existing AST-Core section does.
Where
THIRD-PARTY.md (needs a new section) and resources/enhancedInspector/README.md (could link to it once added).
Suggested change
Per gs-src/enhancedInspector/build/apply_jasper_transforms.sh, six files (Announcements.gs, STON.gs, patch-gemstone.gs, gtoolkit-wireencoding.gs, gt4gemstone.gs, gtoolkit-remote.gs) come from feenk-affiliated upstream repos, and RemoteServiceReplication.gs comes from GemTalk's own repo. A new section modeled on the existing AST-Core one (What/Where/Origin/Obtained via/License/Modifications, then the license text) could cover these.
This needs a careful pass rather than a copy of the existing per-file attribution table: the upstream gtoolkit-remote repo's LICENSE file names an individual feenk gmbh developer as the copyright holder rather than "feenk gmbh" directly, so each origin repo's actual LICENSE file should be checked individually instead of assuming uniform wording across all six feenk-affiliated files.
Summary
resources/enhancedInspector/*.gsships seven third-party MIT-licensed files verbatim in the VSIX (resources/**is not excluded via.vscodeignore), butTHIRD-PARTY.mdcurrently only has a section for the Pharo AST-Core (Refactoring Browser AST) vendored source. Each shipped.gsfile's header only points readers out to "LICENSE in the origin repository" rather than including the MIT notice/permission text the way the existing AST-Core section does.Where
THIRD-PARTY.md(needs a new section) andresources/enhancedInspector/README.md(could link to it once added).Suggested change
Per
gs-src/enhancedInspector/build/apply_jasper_transforms.sh, six files (Announcements.gs,STON.gs,patch-gemstone.gs,gtoolkit-wireencoding.gs,gt4gemstone.gs,gtoolkit-remote.gs) come from feenk-affiliated upstream repos, andRemoteServiceReplication.gscomes from GemTalk's own repo. A new section modeled on the existing AST-Core one (What/Where/Origin/Obtained via/License/Modifications, then the license text) could cover these.This needs a careful pass rather than a copy of the existing per-file attribution table: the upstream
gtoolkit-remoterepo'sLICENSEfile names an individual feenk gmbh developer as the copyright holder rather than "feenk gmbh" directly, so each origin repo's actualLICENSEfile should be checked individually instead of assuming uniform wording across all six feenk-affiliated files.