OASIS Common Security Advisory Framework (CSAF) TC

Dear members,

On Wed, Jun 26, 2024, at 22:00, Michael Reeder via OASIS wrote:
> Dear colleagues,
>
> As discussed in our last TC meeting (2024-06-26) regarding issue #662 "Add the fixed_planned option to the Category of the Remediation" (Add remediation category "fix_planned" · Issue #662 · oasis-tcs/csaf (github.com) <https: github.com/oasis-tcs/csaf/issues/662="">)
>
> I hereby submit the following motion and request that if seconded and no objection received per this list before one week has passed on 2024-07-03 21:00 UTC to automatically carry.
> The Chair usually states the result per mail to this list when the period has passed.
>
> I, Michael Reeder, move to add the `fix_planned` option as suggested in (Add remediation category "fix_planned" · Issue #662 · oasis-tcs/csaf (github.com) <https: github.com/oasis-tcs/csaf/issues/662=""> and include it into CSAF 2.1.
>
> Regards,
> Michael [...]

I, Stefan Hagen, second the motion. As a motion on a mailing list deserves
more lenience IMO, I propose we simply wait another week to then let this motion carry.

On my calendar that would make the motion carry if not objected on 2024-ß5-19 15:00 UTC
instead of the original 2024-07-03 21:00 UTC.

Thanks and cheers,
Stefan.


Original Message:
Sent: 7/11/2024 8:40:00 PM
From: Michael Reeder
Subject: Motion for #662

Dear colleagues,

As discussed in our last TC meeting (2024-06-26) regarding issue #662 "Add the fixed_planned option to the Category of the Remediation" (Add remediation category "fix_planned" · Issue #662 · oasis-tcs/csaf (github.com))

I hereby submit the following motion and request that if seconded and no objection received per this list before one week has passed on 2024-07-18 21:00 UTC to automatically carry. The Chair usually states the result per mail to this list when the period has passed.

I, Michael Reeder, move to add the `fix_planned` option as suggested in (Add remediation category "fix_planned" · Issue #662 · oasis-tcs/csaf (github.com) and include it into CSAF 2.1.

 

Regards,

Michael Reeder

 

Internal Use - Confidential

</https:></https:>