Replies: 11 comments 7 replies
-
|
Beta Was this translation helpful? Give feedback.
-
That timing is fine by me @tarilabs - thank you. Sure beats 3am. :-) |
Beta Was this translation helpful? Give feedback.
-
For the occurence of the TCK meeting on April 15th, I revised the open PRs and I believe we can realistically converge on these: https://github.com/dmn-tck/tck/milestone/3 I would seize the chance to discuss a bit about:
as I believe some clarification would help for some of other open PRs |
Beta Was this translation helpful? Give feedback.
-
For the occurence of the TCK meeting on May 13th, we should try to converge regarding: Accordingly, a number of PRs can reflect and be merged accordingly if we can agree on the common ground suggested above:
then accordingly we should be able to finalize on: We might have as an opportunity to quickly discuss about:
as I believe some clarification would help for some of other open PRs |
Beta Was this translation helpful? Give feedback.
-
For the occurence of the TCK meeting on June 10th, we should try to converge regarding: I believe it has a fundamental basis to potentially affect other work, so is best we check we're all on the same page for this. I will amend this message to reflect if any additional items can be brought in. |
Beta Was this translation helpful? Give feedback.
-
For the occurence of the TCK meeting on July 15th, I am currently collecting topics. I've detected a potential (execution semantic) regression in non backward compatible change (1.2 -> 1.3) which I would prefer to iterate first in the TCK before anyway presenting it at the OMG RTF. |
Beta Was this translation helpful? Give feedback.
-
cc: @opatrascoiu @StrayAlien @falko @SimonRinguette @vpellegrino I am afraid there are problems with the email system of Circleweaver hence why tagged you on this thread. I am not even sure if a related #472 (comment) reached you in the previous month. The next scheduled meeting is:
in the Circleweaver calendar. Please let me know if the email from Circleweaver did reach you, or otherwise; I will take into account for email/communications considerations. I propose the following agenda:
don't worry if due to email non-notified you can't join the live meeting, as usual we will proceed only on items having explicit consensus. |
Beta Was this translation helpful? Give feedback.
-
Hi Mateo,
I can't find the meeting invite details? Could you send them over please?
Thanks On Tuesday, 12 October 2021, 22:15:05 BST, Matteo Mortari ***@***.***> wrote:
cc: @opatrascoiu @StrayAlien @falko @SimonRinguette @vpellegrino
I am afraid there are problems with the email system of Circleweaver hence why tagged you on this thread. I am not even sure if a related #472 (comment) reached you in the previous month.
The next scheduled meeting is:
14-Oct-2021
Shifted by default 1 our "earlier" in Northen emisphere to accomodate Australia shifted to DST.
Thursday 07:00am EDT(Toronto), 12:00 BST(London), 13:00 CEST(Milano), 22:00 AEDT(Melbourne).
in the Circleweaver calendar.
Please let me know if the email from Circleweaver did reach you, or otherwise; I will take into account for email/communications considerations.
I propose the following agenda:
- updates from DecisionCamp etc
- consider for merge previously passing tests and validator extension: https://github.com/dmn-tck/tck/milestone/7
- initial considerations on #470 (comment) or other open issues
- define scope for next milestone
don't worry if due to email non-notified you can't join the live meeting, as usual we will proceed only on items having explicit consensus.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Beta Was this translation helpful? Give feedback.
-
cc: @opatrascoiu @StrayAlien @falko @SimonRinguette @vpellegrino I am afraid there are problems with the email system of Circleweaver hence why tagged you on this thread, also reason for having created this mailing-list on google group: https://groups.google.com/g/dmn-community/about you should have received invite to join it. I propose the next scheduled meeting in line with North hemisphere not observing DST:
This appears to be the only possible schedule which does not include red slots by source. Feel free to counter-propose schedule timings. I propose the following agenda:
No worry if for any reasons you can't join the live meeting, as usual we will proceed only on items having explicit consensus. |
Beta Was this translation helpful? Give feedback.
-
I propose the next scheduled meeting in line with North hemisphere not observing DST and on Tuesdat following :
I propose the following agenda: anything finalised in https://github.com/dmn-tck/tck/milestone/9 stretch goal, if all the comments are actioned by then: discussion on: |
Beta Was this translation helpful? Give feedback.
-
Happy new 2022 everyone! 🗓️ New recurrent meeting instance I propose the next scheduled meeting in line with North hemisphere not observing DST and on Tuesday following :
I propose the following agenda: anything finalised in https://github.com/dmn-tck/tck/milestone/10 meaning: Stretch goals: We(colleagues and me) have some additional comments about #390 (review) which I count to submit by then No action needed, but worth noting about #488 Finally, we could start an informal poll about timing for planning the TCK migrating to DMNv1.4 No worry if for any reasons you can't join the live meeting, as usual we will proceed only on items having explicit consensus. |
Beta Was this translation helpful? Give feedback.
-
As previously anticipated in the previous monthly meeting, I am proposing a new monthly schedule, following Daylight Saving Time being now effective in the northern hemisphere,
FROM
TO
unfortunately with DST it is more difficult to find a good schedule covering worldwide, but as always feel free to counter-propose alternative schedule.
As a reminder, attending the meeting is OPTIONAL and we are striving to be as much inclusive to time differences and transparent in the proceedings, by making most of the work on the Pull Request and Milestones pages here on github.
Beta Was this translation helpful? Give feedback.
All reactions