OASIS Common Security Advisory Framework (CSAF) TC

 View Only
  • 1.  Motion for #861

    Posted 01-31-2025 16:45

    Dear colleagues,
    regarding pull request #861 "Editor revision for TC meeting 2025-01-29" (https://github.com/oasis-tcs/csaf/pull/861):

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

    I, Thomas Schmidt, move to accept the Editor Revision 2025-01-29 as suggested in https://github.com/oasis-tcs/csaf/pull/861 into our master branch. This motion is independent of the potential generation of a rendered version of the document which will be located in the csaf_2.1/prose/share folder and any changes to the generation files located in csaf_2.1/prose/bin and csaf_2.1/prose/etc. It is also independent of the open question whether the title for the CVE as informative reference needs to be changed.

    Best wishes,
    Thomas



    ------------------------------
    Thomas Schmidt
    Subject Matter Expert
    Federal Office for Information Security (BSI) Germany
    ------------------------------


  • 2.  RE: Motion for #861

    Posted 01-31-2025 17:06
    Dear members,

    On Fri, Jan 31, 2025, at 22:45, Thomas Schmidt via OASIS wrote:
    > Dear colleagues,
    > regarding pull request #861 "Editor revision for TC meeting 2025-01-29" (github.com/oasis-tcs/csaf/pull/861):
    >
    >
    > I hereby submit the following motion and request that if seconded and no objection received per this list before one week has passed on 2025-02-07 23:00 UTC to automatically carry.
    > The Chair usually states the result per mail to this list when the period has passed.
    >
    > I, Thomas Schmidt, move to accept the Editor Revision 2025-01-29 as suggested in github.com/oasis-tcs/csaf/pull/861 into our master branch. This motion is independent of the potential generation of a rendered version of the document which will be located in the `csaf_2.1/prose/share` folder and any changes to the generation files located in `csaf_2.1/prose/bin` and `csaf_2.1/prose/etc`. It is also independent of the open question whether the title for the CVE as informative reference needs to be changed.
    >
    >
    > Best wishes,
    > Thomas [...]

    Stefan Hagen seconds the above motion to accept the Editor Revision 2025-01-29.

    Cheers,
    Stefan.