OASIS Common Security Advisory Framework (CSAF) TC

 View Only
  • 1.  Motion to accept the new tech stack for csaf.io

    Posted 07-23-2025 05:24

    Dear colleagues,

    as contributed through https://groups.oasis-open.org/discussion/contribution-new-tech-stack-for-csafio-website there is a new tech stack suggested for the csaf.io website. It is based on Hugo which will allow all of us to easily contribute to the TC's website and add new content.

    A pull request has been open to bring the new tech stack to our website: https://github.com/oasis-open/csaf-documentation/pull/88

    Also, the current state is deployed at https://csaf.dev.

    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-07-30 10: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 replace the current website with the new tech stack as suggested in https://github.com/oasis-open/csaf-documentation/pull/88 and make main our new default branch for the csaf-documentation repo.



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


  • 2.  RE: Motion to accept the new tech stack for csaf.io

    Posted 07-23-2025 08:00

    I, Justin Murphy, second the motion to replace the current website with the new tech stack as suggested in PR#88 (of the csaf-documentation repo).



    ------------------------------
    Justin Murphy
    justin.murphy@cisa.dhs.gov
    ------------------------------