_Copy this template to the subdirectory for the current year and name the file `YYYY-MM-DD-TAC-meeting-record.md` (e.g., `2023-02-02-TOC-meeting-record.md`). Update the information above to change the `title` (e.g., `2023-02-16 TOC Meeting Record`, the `parent` to `YYYY` (e.g., 2023), the `grand_parent` to `Meeting Minutes`, and remove the `nav_exclude` line. Update the links below to reflect the appropriate image location (e.g., `../images/`). Text between `` are instructions. Please remove when section has been completed._

Announcements

  • _Put any announcements. Upcoming events, for example_

None

Presentation

_If there are any presentations from a WG, SIG, or project._

None

Decision

_If there are any items up for vote (this is not meant to be exclusive but meant to highlight items that are expected to be voted on)_

See Action items

Discussion

_Items for discussion, including items left over from the previous meetings, as well as items that have been added_

  1. Live review of the lifecycle document a. See comments in document b. See action items

Project Proposals

_include any project proposals that have been submitted and need discussion or decision._

None

Recordings

Upcoming TAC meetings

Please check the calendar


layout: default title: YYYY-MM-DD TAC Meeting Record parent: Meeting Minutes grand_parent: PQCA TAC nav_exclude: true — _Copy this template to the subdirectory for the current year and name the file `YYYY-MM-DD-TAC-meeting-record.md` (e.g., `2023-02-02-TOC-meeting-record.md`). Update the information above to change the `title` (e.g., `2023-02-16 TOC Meeting Record`, the `parent` to `YYYY` (e.g., 2023), the `grand_parent` to `Meeting Minutes`, and remove the `nav_exclude` line. Update the links below to reflect the appropriate image location (e.g., `../images/`). Text between `` are instructions. Please remove when section has been completed._

Announcements

  • _Put any announcements. Upcoming events, for example_

Presentation

_If there are any presentations from a WG, SIG, or project._

Decision

_If there are any items up for vote (this is not meant to be exclusive but meant to highlight items that are expected to be voted on)_

Discussion

_Items for discussion, including items left over from the previous meetings, as well as items that have been added_

Project Proposals

_include any project proposals that have been submitted and need discussion or decision._

Recordings

Action Items

Old

Nothing

New

  • Submit a request for vote to move contentious issues on the lifecycle doc to GH issues [Max]
  • Resolution to include recommendation of Apache, MIT, Berkeley as the preferred licenses [Nigel]
  • Common sections [Brian]
    1. Move the license section to top level of doc [Brian]
    2. Code of conduct should also move to top level section / recommendation [Brian]
    3. Include links to the templates of the common project files, e.g., CONTRIBUTING.md, GOVERNANCE.md, … [Brian]
    4. Check if the acceptance criteria are the same then move to common sectio
  • Move Healthy to separate GH issue / discussion [Max]
  • Add a section to indicate that this document itself will be reviewed annually for amendments [Max]

Attended by

  • Norman Ashley, Cisco
  • Michael (Max)imilien, IBM
  • Yarkin Doroz, NVIDIA
  • Sophie Schmieg, Google
  • Brian Jarvis, Amazon Web Services Inc.
  • Thomas Bailleux, SandboxAQ