Closed mcleo-d closed 3 years ago
Hi @mcleo-d , thanks for raising this bug! As you noticed, after introducing the new SIG
type, I forgot to change this logic.
I just pushed a commit to dev to address the bug, which is basically adding a new function that returns SIGs and projects, and use this function for the github meetings roster logic; this way no other logic is impacted.
If you're curious, you can check code on https://github.com/finos/metadata-tool/commit/1b893b0396b56463f2b05f018d4a1f9df133ec66 , should be quite straight-forward.
Thanks for the opportunity to review. I've now closed the issue.
Feature Request
Within GitHub Issue https://github.com/finos/metadata/issues/648#issuecomment-706807544 an automated script is being used to run a report that extracts FINOS project maintainers. However, this script currently excludes FINOS projects of type
SIG
.Special Interest Group Type
Including SIG Type
This issue requests
metadata-tool
is extended to include typeSIG
, potentially included in the code block below, or potentially as the new definitiondefn sigs-metadata
https://github.com/finos/metadata-tool/blob/d673b179f5d0f4bbc6fe47451b394c6f768d2d06/src/metadata_tool/sources/metadata.clj#L387-L390
Potential SIG Definition
The Ask
SIG
type potentially lead to unforeseen consequences when reporting against FINOS projects?