Minutes of the meeting 2021-10-14

[tarilabs]

We have synced on a number of general topics and PRs.

General topics

Circleweaver

The website works: https://s06.circleweaver.com/weaver/t/wfmc/dmn-reference-implementation/FrontPage.htm
but it appears still affacted by email delivery issues.
Will create a Google groups and send invite to existing members, to be used as mailing-list.

DecisionCamp

Shared impression with the group.
As a reminder, the presentation can be accessed here: https://decisioncamp2021.wordpress.com/program/
or on the DecisionCommunity youtube channel here: https://www.youtube.com/c/DecisionCAMP/videos
it could be worthy to note the Vendor's panel here: https://www.youtube.com/watch?v=8DnvuuWO3Ho

DecisionAutomation.org

Shared the presentation with the TCK group: https://www.youtube.com/watch?v=9yxmj7Ct_b8
They have asked about a TCK "About page" which was implemented here: https://dmn-tck.github.io/tck/about.html

TCK About page

Content about TCK Mission statement, goals, non-goals, and more detailed information is now refreshed and updated available:

• https://dmn-tck.github.io/tck/about.html
• https://github.com/dmn-tck/tck#scope-of-work

I've only valorised the already existing content, and augmented with previously existing material. If anything missing don't hesitate to let me know

Current Milestone

We went through the active milestone: https://github.com/dmn-tck/tck/milestone/7

• DMN 1.3 equality #389
  Merged one test case folder as we separated problematic code which we already reported at RTF
• TCK validator BKM typeRef #468
  Merged TCK Validator (TCK infra) check that would point out clearly wrong BKM type in the test.

Extras

• Need to clarify semantic of Optional GHA Runners #470 (comment)
  We went through the different perspectives; there seems to be consensus and covergence that:
  • We want to preserve the ability for a Vendor to report on all tests, and which tests are Ignored, Not supported, etc.
  • The TCK website already exposes clearly the information: how many reported-on globally, of which how many Passing, how many Ignored, how many "Missing out from the report"
  • The GitHub Action [OPTIONAL] runner should not report failed tests as Green
  • Maybe the best course of action would be for having some infrastructure capability so to report which JUnit tests (corresponding to test cases) should be Ignored

ref --> #470 (comment)

Next meeting

Next meeting likely will be ~around Thu, Nov 11.
Will follow usual invitation, but maybe repeated here on GitHub beyond the Mailing-List until we transition to stable email delivery.

/cc @opatrascoiu @StrayAlien @falko @vpellegrino