Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Discuss/potentially establish pull request monitoring workflow.

  • Review lead/vice-lead descriptions and approve to be add to TAC member documentation.

  • Discuss API endpoints authentication.

Descriptions to review

Lead position: The lead role will be in charge of organizing, managing, and facilitating monthly technical documents meetings. In conjunction with monthly sub-team meetings, the lead role will attend monthly TAC and joint TAC/UAC meetings and provide updates on the sub-team progress/accomplishments. This role will also be responsible for group onboarding, project management and end of year reports (with assistance when necessary). The lead position will also be responsible for pull requests during any interim period or where there are gaps in group coverage.

Vice-lead: The vice-lead will be responsible for assisting the lead with organizing, scheduling, and hosting monthly meetings in the event that the lead cannot attend. The vice-lead will also be responsible to share progress/accomplishments at monthly TAC meetings and joint TAC/UAC meetings. The individual in this role will cycle up to the lead position when that positions term is complete.

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

10 minutes

Lead/Vice-lead descriptions

Jenna

  • Review/edit/approve descriptions for lead descriptions.

    • Do we want to add bullet points of expectations to the descriptions? Is the above good enough?

20 minutes

Pull Request Monitoring Workflow

Group

  • Explore how to use confluence to manage pull request monitoring.

20 minutes

API Endpoints Authentication

Group

  • Discuss API endpoint authentication.

    • How to report bugs?

10 minutes

Review Action Items/questions

Group

  • Review any action items.

  • Brainstorm ideas for next month's meeting. A few I have thought for next month?

    • Finalize pull request workflow if we have not done so already.

    • Establish a workflow/procedure for regular links audit. Could mimic pull-request workflow.

    • Continue conversation on technical skills required to be on techdocs, how that corresponds with the developers.

✅ Action items

  •  

⤴ Decisions

  • No labels