Open Supplychain Information Modeling TC

 View Only

  • 1.  2024-06-04 Meeting Minutes

    Posted 06-04-2024 15:33

    The intent is to put the meeting minutes in the GitHub repo. However we can't submit the form to OASIS to create the GitHub repo until we have meeting minutes that show we agreed to create the repo. So the following are the draft meeting minutes in markdown format. It does look a little squirrelly due to markdown not agreeing with Higher Logic. They'll look better in GitHub

    I will then use the link to this email to enter into the form for creating the repo. Once the repo is created, I will add these minutes to a minutes subdir on that repo. 

    If I missed anything, or any changes desired, please reply to this email with suggested improvements to the minutes.

    Sidenote: we need an OSIM logo to put as header to minutes and on webpages :-)

    Duncan

    --------------------------------


    # Open Supplychain Information Modeling (OSIM) Technical Committee Meeting

    - Meeting Date: June 4, 2024
    - Time: 18:00 UTC (19:00 CET, 13:00 EDT, 10:00 PST)

    ## Call to Order and Welcome

    Meeting called to order.
    Permission was asked to record meeting and there were no objections.

    ## Roll call

    Quorum was reached with 13 of 13 voting members present.
    13 members received voting rights at this meeting.
    No members are at risk of losing voting rights at next meeting.

    ### Participants

    | Given Name | Family Name | Affiliation | Role |
    |:-----------|:------------|:------------------------------------------------------------|:----------------------------|
    | Bret | Jordan | Afero | Voting Member |
    | Carol | Geyer | OASIS | OASIS Staff |
    | David | Kemp | National Security Agency | Voting Member |
    | Duncan | Sparrell | sFractal | Voting Member, Convener, Secretary |
    | Gururaj | Raman | SAP | Voting Member |
    | Holly | Petersen | OASIS | OASIS Staff |
    | Isaac | Hepworth | Google | Voting Member, Chair |
    | Jade | Stewart | National Security Agency | Voting Member |
    | Jay | White | Microsoft | Voting Member, Chair |
    | Jon | Ceanfaglione | IBM | Voting Member |
    | Jon | Kenny | Cisco | Voting Member |
    | Justin | Murphy | DHS Cybersecurity and Infrastructure Security Agency (CISA) | Voting Member |
    | Kelly | Cullinane | OASIS | OASIS Staff |
    | Patrick | Maroney | AT&T | Voting Member |
    | Robert | Martin | MITRE | Voting Member |
    | Stefan | Hagen | Individual | Voting Member |


    ### Observers present

    | Christoph | Plutte | Ericsson | Observer |

    Note: Observers of this committee that are ready to become Members should follow the specific instructions displayed 0n the OASIS Open Notices tab.

    ## Agenda

    • - Roll Call
    • - Overview of Voting Rights
    • - Nomination & Election of Co-Chairs
    • - Nomination & Election of Secretary
    • - OASIS TC Process Overiew
    • - New Business
    • - Adjourn

    ## Meeting Notes

    • - Isaac Hepworth (Google) and Jay White (Microsoft) were elected co-chairs
    • - Duncan Sparrell was elected Secretary
    • - The slides from the OASIS TC Process Overview will be made avaialable to the mailing list.
      •  + Action Item: Kelly to send slides to list
    • - The meeting voted to obtain a TC Github repo.
      •  + Action Item: Duncan to submit OASIS form
      • + The meeting agreed Isaac, Jay, Duncan, and Stefan would be maintainers
    • - The meeting agreed to work async between monthly meetings by:
      •    + Members would create GitHub Issues
      •    + Members would comment on GitHub
      •    + Members would prepare GitHub Pull Request (PR)
        • * and then send email to list with link making motion to accept PR
        • * someone else seconds
        • * If no comments/changes/objections for one week, maintainers would merge PR
    • - The meeting agreed to meet monthly on first Tuesday of the month at 1PM Eastern (10:00 Pacific, 18:00 UTC 19:00 CET)
      • + Action Item: Duncan to enter in TC calendar
      • + Action Item: Kelly to give Duncan, Isaac, Jay permission to enter TC calendar entries
    • - Homework for next meeting:
      • + Action Item: Dave Kemp to circulate text for discussion at next meeting on topic on process of information modeling
      • + Action Item: Duncan to create Issue and submit PR to create subdirectory for Meeting Minutes
      • + Action Item: Duncan to create Issue and submit PR to create subdirectory for Value Propositions and Practioner Use Cases
      • + Action Item: Duncan to create Issue and submit PR to create subdirectory for FAQs
        • * Everyone to consider FAQs - especially about relationships with other work going on
      • + Action Item: Everyone to reread TC Charter
      • + Action Item: Everyone to think about problem space and where to focus
    ## Adjourn

    - The meeting was adjourned


    ------------------------------
    Duncan Sparrell
    Chief Cyber Curmudgeion
    sFractal Consulting LLC
    Oakton VA
    703-828-8646
    ------------------------------


  • 2.  RE: 2024-06-04 Meeting Minutes

    Posted 06-05-2024 19:15

    I intend to make a meeting minutes template for future meeting minutes which I will put in the TC-Ops repo directory once we are up. The template will be a little more detailed than this first meeting since we'll have standing items to discuss (like PR's approved, github issues for discussion, members gaining/losing voting rights, etc). But my intent is to only record decisions reached and action items - not a blow-by-blow of who said what. In general it will be "no-attribution" unless a member specifically asks to have their view recorded in the minutes. In general it won't include discussion - just decisions and action items - but it may contain a pithy comment like "whether vi or emacs is better was discussed, but no decision reached". My intent is the minutes will be done in markdown and kept on GitHub once we are up and running. But I plan to experiment with keeping a 'running notes' google doc that has the template preloaded and I edit realtime in the meeting which allows anyone who wants to follow along to make sure I didn't miss anything or misportray anything and catch it in realtime instead of a month later.

    A different but related topic is recording the meeting. It is really useful for the Secretary if the meeting is recorded. The O is OASIS is for Open so I personally prefer all meetings be recorded. We should decide is (1) don't record at all (2) record but only for Chairs and Secretary (3) record and put up on a YouTube channel. I'm for at least #2 and preferably #3 but will follow the will of the group.



    ------------------------------
    Duncan Sparrell
    Chief Cyber Curmudgeion
    sFractal Consulting LLC
    Oakton VA
    703-828-8646
    ------------------------------

    Original Message


Related Content